I have a very odd situation going on here
My tunnels have worked for the longest time. Of course everyone denies
changing anything. But all the sudden it stopped working.
Whereas before the tunnel would establish and the client's vpn address
could ping the server's vpn address......
Now the openvpn client connects, and the client's vpn address cannot ping
the server's vpn address.
Additionally the client's physical IP can ping the server's physical IP
BEFORE the tunnel goes up, but not WHILE the tunnel is up.
I tracked it down to one route statement in the client's route table.
It sends 1.2.3.4/32 to 10.0.0.11 via interface 10.0.0.12
1.2.3.4 is the server's public ip address
10.0.0.12 is the address that the client happens to get from the server's
client address pool
10.0.0.11 is the adjacent server address from that pool. (I hand out /2's
because I have windows clients.)
So of course this route breaks things, because as soon as the tunnel is
up,. the client's kernel starts trying to sent the tunnel through itself.
To verify my theory, I had cmd.exe ready to press enter on "route delete
1.2.3.4", and retried the connection, and as soon as it came up I deleted
that route. Then it worked as normal.
My question is WHY would openvpn do that? What could cause such a peculiar
and self-destructive behavior?
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users
