Something strange is happening on my RT-AC86U with Merlin 384.19.
I set up a VPN client and created a couple of rules to transmit all traffic from 2 devices through a VPN.
The configuration worked perfectly for a year, until now. Both clients can't connect to the nework.
The weird thing is that I tried to switch off the VPN and it does not disconnect.
The router pops up the "Applying settings" dialog but, after it reaches 100%, it goes back to Service State "ON".
I have also tried to reset the VPN to Default, but the VPN settings are not reset.
Another strange thing I noticed is that the Network Map tab shows the router is disconnected from the WAN, but all clients are indeed connected and can access the Internet.
How can I kill this VPN?
What I find in the log after I try to switch off and on:
Jan 30 17:12:58 ovpn-client5[31508]: TLS: tls_process: killed expiring key
Jan 30 17:12:59 ovpn-client5[31508]: TLS: soft reset sec=0 bytes=68180/-1 pkts=958/0
Jan 30 17:12:59 ovpn-client5[31508]: VERIFY OK: depth=1, CN=VPNNAME
Jan 30 17:12:59 ovpn-client5[31508]: VERIFY X509NAME OK: CN=vpn.server.com
Jan 30 17:12:59 ovpn-client5[31508]: VERIFY OK: depth=0, CN=vpn.server.com
Jan 30 17:12:59 ovpn-client5[31508]: Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Jan 30 17:12:59 ovpn-client5[31508]: Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Jan 30 17:12:59 ovpn-client5[31508]: Control Channel: TLSv1.2, cipher SSLv3 DHE-RSA-AES256-SHA, 4096 bit RSA
Jan 30 17:16:09 wlceventd: WLCEVENTD wlceventd_proc_event(481): eth5: Disassoc 6C:AD:F8:9C:26:E9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 30 17:16:09 wlceventd: WLCEVENTD wlceventd_proc_event(500): eth5: Auth 6C:AD:F8:9C:26:E9, status: Successful (0)
Jan 30 17:16:09 wlceventd: WLCEVENTD wlceventd_proc_event(529): eth5: Assoc 6C:AD:F8:9C:26:E9, status: Successful (0)
Jan 30 17:20:49 wlceventd: WLCEVENTD wlceventd_proc_event(481): eth5: Disassoc 6C:AD:F8:9C:26:E9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 30 17:20:49 wlceventd: WLCEVENTD wlceventd_proc_event(500): eth5: Auth 6C:AD:F8:9C:26:E9, status: Successful (0)
Jan 30 17:20:49 wlceventd: WLCEVENTD wlceventd_proc_event(529): eth5: Assoc 6C:AD:F8:9C:26:E9, status: Successful (0)
Jan 30 17:21:16 wlceventd: WLCEVENTD wlceventd_proc_event(481): eth5: Disassoc 6C:AD:F8:9C:26:E9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
(more logs like these)
I set up a VPN client and created a couple of rules to transmit all traffic from 2 devices through a VPN.
The configuration worked perfectly for a year, until now. Both clients can't connect to the nework.
The weird thing is that I tried to switch off the VPN and it does not disconnect.
The router pops up the "Applying settings" dialog but, after it reaches 100%, it goes back to Service State "ON".
I have also tried to reset the VPN to Default, but the VPN settings are not reset.
Another strange thing I noticed is that the Network Map tab shows the router is disconnected from the WAN, but all clients are indeed connected and can access the Internet.
How can I kill this VPN?
What I find in the log after I try to switch off and on:
Jan 30 17:12:58 ovpn-client5[31508]: TLS: tls_process: killed expiring key
Jan 30 17:12:59 ovpn-client5[31508]: TLS: soft reset sec=0 bytes=68180/-1 pkts=958/0
Jan 30 17:12:59 ovpn-client5[31508]: VERIFY OK: depth=1, CN=VPNNAME
Jan 30 17:12:59 ovpn-client5[31508]: VERIFY X509NAME OK: CN=vpn.server.com
Jan 30 17:12:59 ovpn-client5[31508]: VERIFY OK: depth=0, CN=vpn.server.com
Jan 30 17:12:59 ovpn-client5[31508]: Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Jan 30 17:12:59 ovpn-client5[31508]: Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Jan 30 17:12:59 ovpn-client5[31508]: Control Channel: TLSv1.2, cipher SSLv3 DHE-RSA-AES256-SHA, 4096 bit RSA
Jan 30 17:16:09 wlceventd: WLCEVENTD wlceventd_proc_event(481): eth5: Disassoc 6C:AD:F8:9C:26:E9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 30 17:16:09 wlceventd: WLCEVENTD wlceventd_proc_event(500): eth5: Auth 6C:AD:F8:9C:26:E9, status: Successful (0)
Jan 30 17:16:09 wlceventd: WLCEVENTD wlceventd_proc_event(529): eth5: Assoc 6C:AD:F8:9C:26:E9, status: Successful (0)
Jan 30 17:20:49 wlceventd: WLCEVENTD wlceventd_proc_event(481): eth5: Disassoc 6C:AD:F8:9C:26:E9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 30 17:20:49 wlceventd: WLCEVENTD wlceventd_proc_event(500): eth5: Auth 6C:AD:F8:9C:26:E9, status: Successful (0)
Jan 30 17:20:49 wlceventd: WLCEVENTD wlceventd_proc_event(529): eth5: Assoc 6C:AD:F8:9C:26:E9, status: Successful (0)
Jan 30 17:21:16 wlceventd: WLCEVENTD wlceventd_proc_event(481): eth5: Disassoc 6C:AD:F8:9C:26:E9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
(more logs like these)
