Router RT-AC56U apparently hangs itself up after "ohci_hcd ... bad entry" in log, leaving OpenVPN server working but unusable, while disabling WLAN access too at the same time. But OpenVPN has some strange entries indicating routing problems prior to that. So, who is to blame?
On an Asus RT-AC56U (192.168.2.1) remote router there is an OpenVPN server. Local router, an Asus RT-AC68U (192.168.1.1) connects to it using a VPN client. Only the other segment traffic (to 192.168.2.1/24) is routed through the VPN. Normally, VPN client connects only as needed, for short period of time (minutes, never hours), does what it needs and logs out. RT-AC56U worked perfectly for some 2 months with several various client connections made daily to its OpenVPN server. Both routers are RT-380.59_0 now, previously it was .58. Bi-directional HMAC authorisation is activated.
I was doing several things:
1) Asus RT-AC68U had client 1 connected to AC56U (for 4 hours) without any payload trafic toward RT-AC56U.
2) testing some port forwarding on RT-AC68U using both GUI and command line - iptables -t nat -I VSERVER 1 ...
3) Asus RT-AC68U had running second OpenVPN client 3 connected to VPN server in Romania.
My poking around local firewall for a short time should not have impacted remote VPN server on AC56U as its tunnel remained unused the entire time. But... I finished, ended client 3. I disconnected Client 1 to RT-AC56U after 4 hours, and went away.
Later that evening, I was not able to connect VPN client to my remote server. Router is UP, VPN server is up, Inet access is up. I used different devices, different OS-s, I could not connect to my remote VPN server.
Problem 1. Remote Asus RT-AC56U log shows one line I can not explain and is likely related:
The only USB device on a remote router is USB 3G modem, but there were no further log activity related to remote modem or its IP link in any way, shape or form.
Problem 2. Immediatelly following the above line, the remote log shows me trying, but failing to connect with:
When I tried connecting a Client from another device (another IP address) I got the following, which at later time also was logged for 5.5.5.5 address:
Another thing that should not have happend: after my last try I went to sleep. But, my remote RT-AC56U shows my IP address retries again, 2h03m later / after my actuall last try!
Problem 3. LEDs on it looked normal. (edit: removed rest of this point as it turned out it was not related to the issue). That suggests to me my RT-AC56U was hung up somehow.
Turning the RT-AC56U manually off and back on solved everything. But, it takes a person to do so
Problem 4. Stil not an end of it! In the remote log, there was something that should not have been there. I was using Client 3 to connect to another VPN server at the same time. Remote server address is: 176.126.237.214. Lets say mine is 5.5.5.5. I do not think 176.126.237.214 should ever appear on my private remote server! Log shows it and that I was again connected after that incindent to remote RT-AC56U.
On an Asus RT-AC56U (192.168.2.1) remote router there is an OpenVPN server. Local router, an Asus RT-AC68U (192.168.1.1) connects to it using a VPN client. Only the other segment traffic (to 192.168.2.1/24) is routed through the VPN. Normally, VPN client connects only as needed, for short period of time (minutes, never hours), does what it needs and logs out. RT-AC56U worked perfectly for some 2 months with several various client connections made daily to its OpenVPN server. Both routers are RT-380.59_0 now, previously it was .58. Bi-directional HMAC authorisation is activated.
I was doing several things:
1) Asus RT-AC68U had client 1 connected to AC56U (for 4 hours) without any payload trafic toward RT-AC56U.
2) testing some port forwarding on RT-AC68U using both GUI and command line - iptables -t nat -I VSERVER 1 ...
3) Asus RT-AC68U had running second OpenVPN client 3 connected to VPN server in Romania.
My poking around local firewall for a short time should not have impacted remote VPN server on AC56U as its tunnel remained unused the entire time. But... I finished, ended client 3. I disconnected Client 1 to RT-AC56U after 4 hours, and went away.
Later that evening, I was not able to connect VPN client to my remote server. Router is UP, VPN server is up, Inet access is up. I used different devices, different OS-s, I could not connect to my remote VPN server.
Problem 1. Remote Asus RT-AC56U log shows one line I can not explain and is likely related:
Code:
Jun 9 16:42:29 openvpn[32521]: ...
Jun 9 22:19:46 kernel: ohci_hcd 0000:00:0b.0: bad entry 9c24e040The only USB device on a remote router is USB 3G modem, but there were no further log activity related to remote modem or its IP link in any way, shape or form.
Problem 2. Immediatelly following the above line, the remote log shows me trying, but failing to connect with:
Code:
Jun 10 02:41:56 openvpn[32521]: 5.5.5.5:60127 TLS: Initial packet from [AF_INET]5.5.5.5:60127, sid=3b3aa30b 8d6e0cd7
Jun 10 02:42:56 openvpn[32521]: 5.5.5.5:60127 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Jun 10 02:42:56 openvpn[32521]: 5.5.5.5:60127 TLS Error: TLS handshake failed
Jun 10 02:42:56 openvpn[32521]: 5.5.5.5:60127 SIGUSR1[soft,tls-error] received, client-instance restartingWhen I tried connecting a Client from another device (another IP address) I got the following, which at later time also was logged for 5.5.5.5 address:
Code:
Jun 10 02:45:26 openvpn[32521]: 10.218.57.123:54390 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1 / time = (1465519520) Fri Jun 10 02:45:20 2016 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warningsAnother thing that should not have happend: after my last try I went to sleep. But, my remote RT-AC56U shows my IP address retries again, 2h03m later / after my actuall last try!
Problem 3. LEDs on it looked normal. (edit: removed rest of this point as it turned out it was not related to the issue). That suggests to me my RT-AC56U was hung up somehow.
Turning the RT-AC56U manually off and back on solved everything. But, it takes a person to do so
Problem 4. Stil not an end of it! In the remote log, there was something that should not have been there. I was using Client 3 to connect to another VPN server at the same time. Remote server address is: 176.126.237.214. Lets say mine is 5.5.5.5. I do not think 176.126.237.214 should ever appear on my private remote server! Log shows it and that I was again connected after that incindent to remote RT-AC56U.
Code:
Jun 9 12:48:18 openvpn[32521]: 5.5.5.5:57060 TLS: Initial packet from [AF_INET]5.5.5.5:57060, sid=a89fd0d9 e555d62a
Jun 9 12:48:20 openvpn[32521]: 5.5.5.5:57060 VERIFY OK: ...
Jun 9 12:48:20 openvpn[32521]: 5.5.5.5:57060 VERIFY OK: ...
...
...
Jun 9 12:50:06 openvpn[32521]: pila_pc/5.5.5.5:53786 [pila_pc] Inactivity timeout (--ping-restart), restarting
Jun 9 12:50:06 openvpn[32521]: pila_pc/5.5.5.5:53786 SIGUSR1[soft,ping-restart] received, client-instance restarting
Jun 9 13:05:27 openvpn[32521]: pila_pc/5.5.5.5:57060 [pila_pc] Inactivity timeout (--ping-restart), restarting
Jun 9 13:05:27 openvpn[32521]: pila_pc/5.5.5.5:57060 SIGUSR1[soft,ping-restart] received, client-instance restarting
Jun 9 13:06:17 openvpn[32521]: 176.126.237.214:42274 TLS: Initial packet from [AF_INET]176.126.237.214:42274, sid=dc228dd7 f691381c
Jun 9 13:07:17 openvpn[32521]: 176.126.237.214:42274 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Jun 9 13:07:17 openvpn[32521]: 176.126.237.214:42274 TLS Error: TLS handshake failed
Jun 9 13:07:17 openvpn[32521]: 176.126.237.214:42274 SIGUSR1[soft,tls-error] received, client-instance restarting
Jun 9 13:07:20 openvpn[32521]: 5.5.5.5:51662 TLS: Initial packet from [AF_INET]5.5.5.5:51662, sid=6abc56e2 3bc311bd
Jun 9 13:07:22 openvpn[32521]: 5.5.5.5:51662 VERIFY OK: ...
Jun 9 13:07:22 openvpn[32521]: 5.5.5.5:51662 VERIFY OK: ...
...
Last edited:
