Hi Richard,
Tibbs, Richard wrote:
Could it be that the "magic" openvpn tries to do (figuring out the gateway for the route itself) could be causing this? Does it work if you actually spell it out, like: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.
(...) route 192.168.1.0 255.255.255.0 route 10.1.1.2
route 192.168.1.0 255.255.255.0 10.1.10.1 route 10.1.1.2 255.255.255.255 10.1.10.1
From reading the docs, the following should work too, requiring less hard-wiring of ip addresses:
route 192.168.1.0 255.255.255.0 vpn_gateway route 10.1.1.2 255.255.255.255 vpn_gateway
Just an idea
Martin
------------------------------------------------------- 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
