Thanks very much, Tom. That route on officefw was all that was needed.
One additional note:
Although I tried this command in the winxp openvpn.conf
route 192.168.10.0 255.255.255.0
It did not insert a route into winxp's table (see below)
I had to do that by hand.
Still mysterious on that one.
Rick.
office fw openvpn.conf is now
# Use a dynamic tun device.
dev tun
# For compatability with 2.x openvpn clients/servers
tun-mtu 1500
tun-mtu-extra 32
mssfix 1450
port 50001
# When using TLS-security (tls-server) uncomment this for 2.x
#key-method 2
disable-occ
local 137.p.q.r
remote 216.x.y.z
ifconfig 10.1.10.2 10.1.10.1
route 192.168.1.0 255.255.255.0
#extra route for linkage to wlan openvpn inside homefw.
route 10.1.1.2
# Our pre-shared static key
secret static.key
The hard evidence...
C:ping 192.168.10.13
Pinging 192.168.10.13 with 32 bytes of data:
Reply from 192.168.10.13: bytes=32 time=94ms TTL=62
Reply from 192.168.10.13: bytes=32 time=92ms TTL=62
Reply from 192.168.10.13: bytes=32 time=93ms TTL=62
Reply from 192.168.10.13: bytes=32 time=94ms TTL=62
Ping statistics for 192.168.10.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 92ms, Maximum = 94ms, Average = 93ms
C:\tracert 192.168.10.13
Tracing route to 192.168.10.13 over a maximum of 30 hops
1 10 ms 15 ms 3 ms 10.1.1.1
2 92 ms 94 ms 93 ms 10.1.10.2
3 98 ms 93 ms 92 ms 192.168.10.13
Trace complete.
C:\Documents and Settings\rwtibbs>route print
========================================================================
===
Interface List
========================================================================
===
========================================================================
===
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.3
2
10.1.1.0 255.255.255.252 10.1.1.2 10.1.1.2
30
10.1.1.2 255.255.255.255 127.0.0.1 127.0.0.1
30
10.255.255.255 255.255.255.255 10.1.1.2 10.1.1.2
30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.3 192.168.1.3
2
192.168.1.3 255.255.255.255 127.0.0.1 127.0.0.1
2
192.168.1.255 255.255.255.255 192.168.1.3 192.168.1.3
2
192.168.10.0 255.255.255.0 10.1.1.1 10.1.1.2
1
224.0.0.0 240.0.0.0 10.1.1.2 10.1.1.2
30
224.0.0.0 240.0.0.0 192.168.1.3 192.168.1.3
2
255.255.255.255 255.255.255.255 10.1.1.2 10.1.1.2
1
255.255.255.255 255.255.255.255 192.168.1.3 192.168.1.3
1
Default Gateway: 192.168.1.254
========================================================================
===
Persistent Routes:
None
-----Original Message-----
From: Tom Eastep [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 23, 2005 2:00 PM
To: Tibbs, Richard
Cc: [email protected]
Subject: Re: [leaf-user] please help: two openvpn tunnels.
Tibbs, Richard wrote:
>
>
> firewall: -root-
> # ip route
> 10.1.10.1 dev tun0 proto kernel scope link src 10.1.10.2
> 192.168.1.0/24 via 10.1.10.1 dev tun0
> 192.168.10.0/24 dev eth1 proto kernel scope link src 192.168.10.254
> 137.x.y.0/24 dev eth0 proto kernel scope link src 137.x.y.z
> 137.x.y.0/24 dev ipsec0 proto kernel scope link src 137.x.y.z
> default via 137.x.y.55 dev eth0
>
>
The winxp system has IP address 10.1.1.2 -- that isn't routed through
your tunnel.
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ [EMAIL PROTECTED]
PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
