2
1
I have a homenetwork 192.168.1.0/24 with gateway 192.168.1.1 and a remote network with the same parameters. Now I want to create a OpenVPN tunnel between those networks.
I have no problems with Windows, because Windows routes everything to 192.168.1.0/24 except 192.168.1.1 throught the tunnel.
On Mac OS X however I see the following line in the Details window:
2010-05-10 09:13:01 WARNING: potential route subnet conflict between local LAN [192.168.1.0/255.255.255.0] and remote VPN [192.168.1.0/255.255.255.0]
When I list the routes I get the following:
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGSc 13 3 en1
127 localhost UCS 0 0 lo0
localhost localhost UH 12 3589 lo0
169.254 link#5 UCS 0 0 en1
192.168.1 link#5 UCS 1 0 en1
192.168.1.1 0:1e:e5:f4:ec:7f UHLW 13 17 en1 1103
192.168.1.101 localhost UHS 0 0 lo0
192.168.6 192.168.6.5 UGSc 0 0 tun0
192.168.6.5 192.168.6.6 UH 1 0 tun0
My Interfaces are
en1 - My local Wifi network
tun0 - The tunnel interface
As can be seen from the routes above there is no entry for 192.168.1.0/24 that routes the traffic through the tunnel interface.
When I manually route a single IP like 192.168.1.16 over the tunnel gateway 192.168.6.6, this works.
Q: How do I set up my routes in MacOS X for the same behaviour as on windows, to route everything except 192.168.1.1 through the tunnel, but leave the default gateway to be my local 192.168.1.1 ?
EDIT: I reopened the question because it could not be fully answered the first time.
The VPN-Client machine does not need to access its own subnet, except for the router, and TCP packages should take the tunnel except for the tunnelled packages themselves.
don't feel like you have to accept an answer if it doesn't really solve your problem. i think our comment discussion on my answer clarified what you're attempting to do; consider refining your question post from that discussion. that will bump it back to the front page and perhaps get some fresh eyes on the problem. – quack quixote – 2010-05-13T19:33:20.220