Is anyone else having a problem with OpenVPN after upgrading to Core 156. Mine just won’t start now and has the following error message in the logs
/sbin/ip link set dev tun1 up
/sbin/ip addr add dev tun1 local 10.110.26.1 peer 10.110.26.2
/sbin/ip route add 10.110.26.0/24 via 10.110.26.2
/sbin/ip route add 10.110.26.0/24 via 10.110.26.2
ERROR: Linux route add command failed: external program exited with error status: 2
Data Channel MTU parms [ L:1621 D:1621 EF:121 EB:406 ET:0 EL:3 ]
Could not determine IPv4/IPv6 protocol. Using AF_INET
Socket Buffers: R=[212992->212992] S=[212992->212992]
TCP/UDP: Socket bind failed on local address [AF_INET][undef]:1194: Address already in use (errno=98)
Exiting due to fatal error
/sbin/ip route del 10.110.26.0/24
/sbin/ip route del 10.110.26.0/24
ERROR: Linux route delete command failed: external program exited with error status: 2
Closing TUN/TAP interface
/sbin/ip addr del dev tun1 local 10.110.26.1 peer 10.110.26.2
Nothing in the OpenVPN was changed and it was working fine in Core 155.
I also had no problems with OpenVPN in the Core 156 Testing.
my question is:
why can i see
“ip route add” and also “ip route del” two times with the same parameters in your log.
In my log:
May 7 09:04:39 ipfire openvpnserver[3192]: /sbin/ip route add 10.251.150.0/24 via 10.251.150.2
May 7 09:04:39 ipfire openvpnserver[3192]: Could not determine IPv4/IPv6 protocol. Using AF_INET
May 7 09:04:39 ipfire openvpnserver[3192]: Socket Buffers: R=[87380->87380] S=[16384->16384]
May 7 09:04:39 ipfire openvpnserver[3192]: Listening for incoming TCP connection on [AF_INET][undef]:1194
Hi @silvio
That’s a good question. Hopefully someone knowledgeable will be able to help.
If we don’t hear anything my backstop will be to re-install Core 155, confirm everything works again and redo the upgrade again and see what happens then.
Have you checked if you have the 50-ovpn init file under /etc/init.d/networking/red.up/ more then once or if the startup command is inserted a second time in this file?
I was looking at a similar thing. I found that there was an existing route already set which was stopping OpenVPN starting. I deleted the route but that was not enough. I rebooted and now OpenVPN is working again.
Just rebooting was not enough to clear that route but deleting the route and rebooting worked.
Something must have hiccuped during the upgrade.
Thanks for your input and advice. Always good to discuss these things with other people. That can trigger what needs to be looked at. Thanks very much.