Allowing server to see computers connected to client, when the client is a router and the server is not

chasem12345

I sincerely hope the above title makes sense. Here is my situation.

I have a windows server ec2 instance on AWS that hosts an openvpn server with this config:

port 1194
proto udp4
tun-mtu 1500
topology subnet
float
persist-key
persist-tun
client-to-client
dev tun
server 172.31.90.0 255.255.255.0

Client (Pfsense router) can connect to it just fine. No errors on either side, no red lines whatsoever. pfsense gets an IP of 172.31.90.2

Clients connected to the pfsense box get an IP in the range of 10.16.15.0/24

From the server, I can ping the VPN interface on pfsense, as expected (ping 172.31.90.2)

I can not ping my computer, connected to the pfsense router (IP of 10.16.15.103)

BUT I can ping the openvpn server FROM my computer (ping 172.31.90.1 from 10.16.15.103) so it appears the tunnel works fine FROM pfsense TO the vpn server, but not the other way around.

I have tried several different route configs and I'm not sure I quite understand it, or if my configuration is just unique. I'd really appreciate if anyone can help me out here

I'll also add, all firewalls have been disabled for testing purposes.

300000

you need set up site to sit connection to make it work as you like , server dont know how to find client computer , no routing table info so no go.

you need to use ccd and client certificate name info to make site to site work and after that you can ping to client computer behide pfsense firewall.