Additional information:

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            a.b.c.129       UGS         0     3317    em1
4.2.2.2            a.b.c.129       UGHS        0     1401    em1
8.8.8.8            a.b.c.129       UGHS        0     1394    em1
10.23.45.0/24       link#1             U           0   282551    em0
10.23.45.1          link#1             UHS         0        3    lo0
24.29.99.35        d.e.f.85       UGHS        0     1394    em2
24.29.99.36        d.e.f.85       UGHS        0     1394    em2
a.b.c.128/27    link#2             U           0     6268    em1
a.b.c.130       link#2             UHS         0        3    lo0
a.b.c.138       link#2             UHS         0        0    lo0 =>
a.b.c.138/32    link#2             U           0        0    em1
d.e.f.84/30    link#3             U           0     6268    em2
d.e.f.86       link#3             UHS         0        0    lo0
127.0.0.1          link#4             UH          0      282    lo0
172.16.1.1/32    172.16.1.5       UGS         0        6 ovpnc2
172.16.1.5       link#13            UH          0        6 ovpnc2
172.16.1.6       link#13            UHS         0        6    lo0
192.168.1.0/24     172.16.1.5       UGS         0       39 ovpnc2

I have no way of adding new routes by hand in the web interface.  The method of 
adding a route in the web interface is restricted.

Thanks!

On Jan 30, 2011, at 4:10 PM, Mark P Hennessy wrote:

> 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: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
>> Commercial support available - https://portal.pfsense.org
>> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Commercial support available - https://portal.pfsense.org

Reply via email to