RT-AX88U issues with DNS-O-Matic and System Log

[technet]

On a RT-AX88U running AsusWRT Merlin 386.3_2, we are getting the following output at system log:

Dec 13 18:12:00 inadyn[19644]: Fatal error in DDNS server response:
Dec 13 18:12:00 inadyn[19644]: [401 Unauthorized] badauth
Dec 13 18:12:00 inadyn[19644]: Error response from DDNS server, exiting!
Dec 13 18:12:00 inadyn[19644]: Error code 50: Authentication failure
Dec 13 18:12:04 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:04 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:04 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:04 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:04 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:04 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:04 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:04 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:05 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:05 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:11 kernel: protocol 0800 is buggy, dev eth6
Dec 13 18:12:11 kernel: protocol 0800 is buggy, dev eth6
Dec 13 18:12:13 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:13 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:13 kernel: protocol 0800 is buggy, dev eth7
Dec 13 18:12:16 kernel: protocol 86dd is buggy, dev eth6
Dec 13 18:12:16 kernel: protocol 86dd is buggy, dev eth6
Dec 13 18:12:16 kernel: protocol 86dd is buggy, dev eth6
Dec 13 18:12:16 kernel: protocol 86dd is buggy, dev eth6
Dec 13 18:12:16 kernel: protocol 86dd is buggy, dev eth6
Dec 13 18:12:20 kernel: protocol 86dd is buggy, dev eth6
Dec 13 18:12:33 kernel: protocol 0800 is buggy, dev eth7
Dec 13 18:12:34 kernel: protocol 0800 is buggy, dev eth6
Dec 13 18:12:34 kernel: protocol 86dd is buggy, dev eth6
Dec 13 18:12:36 kernel: protocol 86dd is buggy, dev eth6
Dec 13 18:12:40 kernel: protocol 0800 is buggy, dev eth6
Dec 13 18:12:40 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:40 kernel: protocol 0800 is buggy, dev eth6
Dec 13 18:12:41 kernel: protocol 0800 is buggy, dev eth6
Dec 13 18:12:41 kernel: protocol 0800 is buggy, dev eth6
Dec 13 18:12:41 kernel: protocol 0800 is buggy, dev eth6
Dec 13 18:12:42 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:42 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:42 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:42 kernel: protocol 86dd is buggy, dev eth7
Dec 13 18:12:47 kernel: protocol 86dd is buggy, dev eth7

The DNS-M-Matic badauth is being reported on this topic - still unsolved to us here.

How address those issues? Please let us know if more detail is needed.

 

[ColinTaylor]

Already reported here: http://www.snbforums.com/threads/dnsomatic-new-api-settings.76163/

 

[jsbeddow]

See my reply over here:

DNSOMATIC new API Settings

DNSOMATIC have recently switched to OpenDNS Authentication, and at the same time, my router AX86U stopped being able to authenticate with them. I think (guess) this needs a tweak to get it working again.

www.snbforums.com

 

[technet]

Is the system log issue related to that?

protocol 86dd is buggy, dev eth7

 

[donat76]

Turning off hardware acceleration (flowcache and runner) should take care of this issue.

(eth7 is the 5GHz WiFi and eth6 is the 2.4GHz Wi-Fi)

(Protocol 86dd is IPv6 and 0800 is IPv4)

IEEE 802 Numbers

Only happens when Trend micro module is loaded. (Shows in log) Module is loaded temporarily when clicking on some of the Adaptive QoS pages in GUI and unloads after leaving page OR stays loaded all the time if you have Adaptive QOS turned on.

Only shows errors if actively using device while Trend Micro deep packet inspection module is loaded. The device making it throw errors is an older device.