bbroussard
read UDPv4 [EHOSTUNREACH]: No route to host (code=113)
I am testing openVPN to determine if it will fit our needs. I have a server (192.168.53.239) and a client (192.168.53.109) both running fedora 13 (2.6.33). both are connect to the same switch.
using the sample files for server and client and editing the remote on the client conf to remote 192.168.53.239 1194.
turn off fire walls (for right now)
start server all good.
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.8.0.2 * 255.255.255.255 UH 0 0 0 tun0
192.168.53.0 * 255.255.255.0 U 1 0 0 eth0
10.8.0.0 10.8.0.2 255.255.255.0 UG 0 0 0 tun0
default 192.168.53.1 0.0.0.0 UG 0 0 0 eth0
start client (not so good)
Thu Oct 14 16:13:46 2010 OpenVPN 2.1.1 i686-redhat-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] built on Jan 5 2010
Thu Oct 14 16:13:46 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Thu Oct 14 16:13:46 2010 LZO compression initialized
Thu Oct 14 16:13:46 2010 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
Thu Oct 14 16:13:46 2010 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Thu Oct 14 16:13:46 2010 Local Options hash (VER=V4): '41690919'
Thu Oct 14 16:13:46 2010 Expected Remote Options hash (VER=V4): '530fdded'
Thu Oct 14 16:13:46 2010 Socket Buffers: R=[112640->131072] S=[112640->131072]
Thu Oct 14 16:13:46 2010 UDPv4 link local: [undef]
Thu Oct 14 16:13:46 2010 UDPv4 link remote: 192.168.53.239:1194
Thu Oct 14 16:13:46 2010 read UDPv4 [EHOSTUNREACH]: No route to host (code=113)
Thu Oct 14 16:13:48 2010 read UDPv4 [EHOSTUNREACH]: No route to host (code=113)
Is there a step I have missed in the documentation?
Any help, thank brian
krzee
are these machines in the same lan?
Thu Oct 14 16:13:46 2010 UDPv4 link remote: 192.168.53.239:1194
this means you have
remote 192.168.53.239 1194
in your client config... this is the IP it is trying to connect to, but cant because it has no route
bbroussard
Hello thanks:
these were two brand new Fedora 13 boxes I found a crazy rule in the Iptables do not know how it made it to the top of the list.... removed it and is working now.
brian
Luis Vazquez
Hi, Brian.
I'm having a similar problem, with another device.
I've been trying different things, but nothing has worked.
I have almost null knowledge about "iptables", I just would like to know wich rule was the one you removed or modified to make it work, and check if it works for me too.
Thanks in advanced.
