An additional response to your reply to my original e-mail. I went into Diagnostics->Ping and pinged 192.168.1.3 over both LAN and WAN interfaces, and got no response back. This suggests to me that the network interface created for the OpenVPN client exists, but the web UI doesn't let me talk to it in any way. I also tried pinging the 172.16 IPs, and the only one that was pingable was the one that was assigned by the OpenVPN client to the local interface on the pfSense firewall. That IP is pingable from both WAN and LAN.
Perhaps pfSense 2.0 BETA5 is not allowing me to create a necessary route between existing, but hidden, interfaces? Thanks! On Jan 27, 2011, at 4:43 PM, Joseph L. Casale wrote: >> In the OpenVPN Status page the client instances section shows that the >> connection is up, >> but in the list of routes, I don't see a route for my remote network. > > In that case, you almost certainly haven't used the right parameters, or > clicked the right options > in the gui (I haven't played much with 2.0 yet). > > Post your config, probably easy to figure out once we know the setup... > jlc > > --------------------------------------------------------------------- > To unsubscribe, e-mail: support-unsubscr...@pfsense.com > For additional commands, e-mail: support-h...@pfsense.com > > Commercial support available - https://portal.pfsense.org > --------------------------------------------------------------------- To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
