RT-AC5300 Intense lag spike

[scareferatis]

Hello. Recently I've updated from 384.18_beta1 to 386.2_2. Since then I'm getting massive lag spike on my normal setup that shouldn't be there.

Setup: TCP OpenVPN with Strict Policy Rule that forbids internet access without VPN, Dual WAN (50/50 and 100/100), Cloudflare DNS.

After updating my dl/ul speed plummeted to 20KB/S, ping started to rocket up to 600, which isn't a problem on my VPN (checked it on my ISP router, then fully disabled VPN and switched to the second line - same issue).

Downgrade to 384.18 and full reset didn't solve a problem.

Here's a small portion of my log:

May 5 09:32:40 dnsmasq-dhcp[420]: DHCPREQUEST(br0) 10.4.4.54 28:f0:76:16:52:b8
May 5 09:32:40 dnsmasq-dhcp[420]: DHCPACK(br0) 10.4.4.54 28:f0:76:16:52:b8 DESKTOP-67R7JPN
May 5 17:00:57 ovpn-client1[1387]: VERIFY OK: depth=1, C=XX, ST=NV, L=xxx, O=xxx, CN=xxx, emailAddress=xxx
May 5 17:00:57 ovpn-client1[1387]: VERIFY OK: depth=0, C=XX, ST=NV, L=xxx, O=xxx, CN=xxx, emailAddress=xxx
May 5 17:01:02 ovpn-client1[1387]: Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
May 5 17:01:02 ovpn-client1[1387]: Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
May 5 17:01:02 ovpn-client1[1387]: Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
May 5 18:00:56 ovpn-client1[1387]: TLS: tls_process: killed expiring key
May 5 21:05:12 dnsmasq-dhcp[420]: DHCPREQUEST(br0) 10.4.4.54 28:f0:76:16:52:b8
May 5 21:05:12 dnsmasq-dhcp[420]: DHCPACK(br0) 10.4.4.54 28:f0:76:16:52:b8 DESKTOP-67R7JPN
May 5 23:58:52 kernel: nvram: consolidating space!

IIRC, when everything was OK, there was no dnsmasq and kernel inside the log. DNSMasq probably means DNSCrypt, but I don't have that enabled.

I'm struggling with this for a week now. Looking forward to a solution.

 

[john9527]

IIRC, when everything was OK, there was no dnsmasq and kernel inside the log. DNSMasq probably means DNSCrypt, but I don't have that enabled.

Those are all normal events....your desktop renewing it's lease, and the nvram statement performing housekeeping.
The TLS event should have been followed up with the openvpn client reconnecting (I'm assuming you filtered your post).