RT-AX88U wan connection problems and mcast errors

[Gravityz]

i am running 41700 firmware for a while now(did a clean setup, no config restores)

now i experienced something what looks like a WAN reset which happened a couple of times in a row.
googling the error shows that this might be an old bug reappearing again.

anbody knows what is happening
i do not have services like vpn running.
I do have ddns enabled

Feb 4 16:35:02 rc_service: httpd 1336:notify_rc restart_net_and_phy
Feb 4 16:35:04 iTunes: daemon is stoped
Feb 4 16:35:04 FTP Server: daemon is stoped
Feb 4 16:35:04 Samba Server: smb daemon is stoped
Feb 4 16:35:10 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: sched: RT throttling activated
Feb 4 16:35:10 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) (phyId: 8) Link DOWN.
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link DOWN.
Feb 4 16:35:10 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:10 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:11 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link UP at 1000 mbps full duplex
Feb 4 16:35:11 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:11 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 22 could not be found^[[0m
Feb 4 16:35:11 avahi-daemon[13859]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Feb 4 16:35:11 wan: finish adding multi routes
Feb 4 16:35:12 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Feb 4 16:35:12 ddns update: ez-ipupdate: starting...
Feb 4 16:35:12 ddns update: asus_private() interface =eth0
Feb 4 16:35:12 ddns update: g_asus_ddns_mode == 2
Feb 4 16:35:13 ddns update: connected to nwsrv-ns1.asus.com (52.250.42.40) on port 443.
Feb 4 16:35:13 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Thu, 04 Feb 2021 15:35:13 GMT^M Server: Apache^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Feb 4 16:35:13 ddns update: retval= 0, ddns_return_code (,200)
Feb 4 16:35:13 ddns update: asusddns_update: 0
Feb 4 16:35:13 ddns: ddns update ok
Feb 4 16:35:13 ddns update: exit_main
Feb 4 16:35:13 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) (phyId: 8) Link UP at 1000 mbps full duplex
Feb 4 16:35:13 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link UP at 1000 mbps full duplex
Feb 4 16:35:13 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
Feb 4 16:35:14 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link UP at 10 mbps half duplex
Feb 4 16:35:15 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Feb 4 16:35:16 RT-AX88U: start https:8443
Feb 4 16:35:16 RT-AX88U: start httpd:80
Feb 4 16:35:16 httpd: Save SSL certificate...8443
Feb 4 16:35:16 httpd: mssl_cert_key_match : PASS
Feb 4 16:35:16 httpd: Succeed to init SSL certificate...8443
Feb 4 16:35:16 httpd: Succeed to init SSL certificate...80
Feb 4 16:35:17 BWDPI: fun bitmap = 57f
Feb 4 16:35:17 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link UP at 100 mbps full duplex
Feb 4 16:35:18 dhcp client: bound 178.85.113.146/255.255.255.0 via 178.85.113.1 for 135146 seconds.
Feb 4 16:35:21 WAN Connection: WAN was restored.

 

[Mikesigen]

Hi!

Something like that for me 2 >-|
Misery Loves Company!

I have a set of two ZenWIFI AX 8 AiMesh products also known as AX8 or AX6600 in default "Wireless router mode / AiMesh Router mode." The Primary unit connected via a ca 5m long Ethernet cat 7 cable direct to a bridged 4g Router.

My WAN connection goes up and down... or down and up... once a minute, or 109 times in the last 150 minutes.
Having my WAN connection go down then up once a minute is not appreciated! Any insights would be appreciated, and getting back the stable Internet connection we had a week ago would be especially appreciated
Having my Internt connection go down every minute is making both work and play almost impossible.

Is the ASUS DDNS updater function messing with my WAN connection? Or is it WAN syncing problems?
Activated DDNS, No VPN.

Anyway, updated the firmware on the unit (to 3.0.0.4.386_41793), factory reset the device. Rebooted. NOT loaded a backup config, but setup modem from scratch after reset. That usually fixes issues!
109 times: WAN Connection: WAN was restored


Very often:
Feb 12 20:12:38 ddns update: asus_private() interface =eth0
Feb 12 20:12:38 WAN Connection: WAN was restored.

Also often:
Feb 12 20:33:09 miniupnpd[12248]: shutting down MiniUPnPd
Feb 12 20:33:09 WAN Connection: WAN was restored.

Also Feb 12 21:59:46 WAN Connection: ISP's DHCP did not function properly.
Seems to be related to: DDNS, " dhcp_client: bound ....."

Super interesting:
Feb 12 19:25:52 dhcp client: bound 2.67.171.183/255.0.0.0 via 2.0.0.1 for 3600 seconds.
Feb 12 19:26:57 kernel: eth0 (Int switch port: 1) (Logical Port: 1) (phyId: 1f) Link DOWN.
Feb 12 19:27:00 WAN Connection: ISP's DHCP did not function properly.
Feb 12 19:27:00 kernel: eth0: sysport_tm port shaper set to 999000 kbps (phy speed 1000000 kbps)
Feb 12 19:27:00 kernel: eth0 (Int switch port: 1) (Logical Port: 1) (phyId: 1f) Link Up at 1000 mbps full duplex
Feb 12 19:27:06 WAN Connection: WAN(0) link up.

Some suggest swapping out the Ethernet cable between Internet Modem and the AX8. Why Not?
Others suggest manually locking the speed of the Interfaces (1 Gb/s) if possible.

Detailed log in the attached txt file....

Similar experiences... (don't read all of these!)

WAN Connection: WAN was restored. at DuckDuckGo

DuckDuckGo. Privacy, Simplified.

duckduckgo.com

WAN Disconnects · Issue #23 · padavanfirmware/rt-n56u

What steps will reproduce the problem? 1. Configure router 2. Use router for some time (30 - 40 minutes) 3. Start clicking on links and notice that the internet is no longer working. 4. Wait 20-30 ...

github.com

ASUS RT66 router keeps dropping connection daily

I've been at this for weeks I've even flashed merlin firmware, changed the cables, factory reset. Maybe there is an issue I'm not seeing here? Here is the system log, for some reason the date keeps changing back to Jul 31 2010. It drops connection for around 30 seconds. Jan 28 22:23:14...

arstechnica.com

ASUS DSL AC68U - ISP DHCP issue - Asus

forums.whirlpool.net.au

Old school, talks of EMI and living near a RADAR station!
https://forum.kitz.co.uk/index.php?topic=17185.0

AX-50 WAN Disconnects - Home Network Community

Hi, about 3 months ago I replaced my router with an AX50 and was pleased with its performance. It has Firmware 1.0.9 Build 20200708 rel.55037(5553) Hardware Archer AX50 v1.0 About 4 weeks ago I would loose internet access most nights whic

community.tp-link.com

 

[Mikesigen]

Strongly Recommended:​

"Correlation does not imply causation."
Strangely, no the WAN connection problem after optimising DNS servers.

Setting Manual DNS servers has greatly helped my clients.
Testing DNS servers with Domain Name Speed Benchmark is HIGHLY recommended!

8 hours of good function after 1 week of problems.