Micro disconnects, cant find source

[saeris]

We started since a few weeks get random DCs and I'm not sure what the issue could be.
When it happens, I can't even connect to the router at all, neither on LAN or WIFI.


Here are a few snippets from the log.

First snippet is when I know it happend 100%. I can't pin point more spots in the log, as I didn't track the time properly. Maybe one of you can see an issue?

Feb 26 18:37:16 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2 --> 5 ] [ 3, 7 --> 8 ]
Feb 26 18:37:16 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
Feb 26 18:37:44 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 1000 mbps full duplex
Feb 26 18:37:45 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
Feb 26 18:37:47 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 1000 mbps full duplex
Feb 26 18:37:59 miniupnpd[2866]: Failed to add NAT-PMP 10188 tcp->192.168.1.67:32400 'NAT-PMP 10188 tcp'
Feb 26 18:38:18 miniupnpd[2866]: Failed to add NAT-PMP 16620 tcp->192.168.1.67:32400 'NAT-PMP 16620 tcp'

Feb 21 02:15:53 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Feb 21 02:15:53 miniupnpd[1648]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Feb 21 02:15:53 dhcp_client: bound 192.168.178.20/255.255.255.0 via 192.168.178.1 for 864000 seconds.
Feb 21 02:15:53 FlexQoS: /jffs/addons/flexqos/flexqos.sh (pid=1729) called in unattended mode with 1 args: -start
Feb 21 02:15:53 FlexQoS: Adaptive QoS is not enabled. Skipping FlexQoS startup.
Feb 21 02:36:18 roamast: [EXAP]Deauth old sta in 0 0: 10:52:1C:45:B1:45
Feb 21 02:36:18 roamast: eth6: disconnect weak signal strength station [10:52:1c:45:b1:45]
Feb 21 02:36:18 roamast: eth6: remove client [10:52:1c:45:b1:45] from monitor list
Feb 21 02:36:19 kernel: wl0: random key value: BE24959C9A00B3AD537900DC8EC9F6F7B1A9CCB42C9A077DCE7E26444ABA7728
Feb 21 02:41:16 roamast: [EXAP]Deauth old sta in 0 0: 10:52:1C:45:B1:45
Feb 21 02:41:16 roamast: eth6: disconnect weak signal strength station [10:52:1c:45:b1:45]
Feb 21 02:41:16 roamast: eth6: remove client [10:52:1c:45:b1:45] from monitor list
Feb 21 02:41:17 kernel: wl0: random key value: C3A0411F7074C06471090256F82224EB88D950422D94048557026402E649A46B
Feb 21 02:46:11 kernel: wl0: random key value: 70C02B8A48D2887F799E00903BAC0CD05766ABCE8D7507D9D090DA1DD6BDD14A
Feb 21 02:47:33 awsiot[23975]: awsiot init : basic data publish success
Feb 21 02:54:56 miniupnpd[1648]: Failed to add NAT-PMP 15368 tcp->192.168.1.67:32400 'NAT-PMP 15368 tcp'
Feb 21 02:57:24 kernel: wl0: random key value: 289871E3669376A574460176F6423E52D706127FCDA60B2C02ACC83BB4B7AC1D
Feb 21 02:57:47 kernel: wl0: random key value: 727494F1CB16DDAA79E10323236F7882D117347623FD04B1B8291B3E85B15CCD
Feb 21 03:07:00 miniupnpd[1648]: Failed to add NAT-PMP 24562 tcp->192.168.1.67:32400 'NAT-PMP 24562 tcp'
Feb 21 03:30:00 FlexQoS: /jffs/addons/flexqos/flexqos.sh (pid=11216) called in unattended mode with 1 args: -check
Feb 21 03:30:00 FlexQoS: Adaptive QoS is not enabled. Skipping FlexQoS startup.
Feb 21 03:39:03 kernel: wl0: random key value: E6DDBB608361386B5C36028077ABE96A61CEB8BA6D8401064BB6B8EF99F0DC83
Feb 21 03:41:26 kernel: wl0: random key value: A38A83FB98F7147273B2032BFCCF2979B113AECB26570F0C8CE497722A901EE2
Feb 21 03:51:49 kernel: wl0: random key value: 1BD4DBE2333A92C13A2003BBB090CD8FB07241C7F90C0937DCE8C29FA136C22E
Feb 21 04:07:00 miniupnpd[1648]: Failed to add NAT-PMP 24053 tcp->192.168.1.67:32400 'NAT-PMP 24053 tcp'
Feb 21 04:58:59 kernel: wl0: random key value: 5A99821AABCF7C55117A03B4E8041F0E71971A37C7320218FFE7564883A8AFB8
Feb 21 05:07:01 miniupnpd[1648]: Failed to add NAT-PMP 27892 tcp->192.168.1.67:32400 'NAT-PMP 27892 tcp'
Feb 21 06:07:02 miniupnpd[1648]: Failed to add NAT-PMP 24362 tcp->192.168.1.67:32400 'NAT-PMP 24362 tcp'
Feb 21 07:07:03 miniupnpd[1648]: Failed to add NAT-PMP 15414 tcp->192.168.1.67:32400 'NAT-PMP 15414 tcp'
Feb 21 08:07:04 miniupnpd[1648]: Failed to add NAT-PMP 15563 tcp->192.168.1.67:32400 'NAT-PMP 15563 tcp'
Feb 21 09:07:05 miniupnpd[1648]: Failed to add NAT-PMP 22673 tcp->192.168.1.67:32400 'NAT-PMP 22673 tcp'
Feb 21 10:07:06 miniupnpd[1648]: Failed to add NAT-PMP 28722 tcp->192.168.1.67:32400 'NAT-PMP 28722 tcp'
Feb 21 11:07:09 miniupnpd[1648]: Failed to add NAT-PMP 21662 tcp->192.168.1.67:32400 'NAT-PMP 21662 tcp'
Feb 21 12:07:10 miniupnpd[1648]: Failed to add NAT-PMP 19582 tcp->192.168.1.67:32400 'NAT-PMP 19582 tcp'
Feb 21 13:07:11 miniupnpd[1648]: Failed to add NAT-PMP 23797 tcp->192.168.1.67:32400 'NAT-PMP 23797 tcp'
Feb 21 14:07:13 miniupnpd[1648]: Failed to add NAT-PMP 21060 tcp->192.168.1.67:32400 'NAT-PMP 21060 tcp'
Feb 21 15:07:14 miniupnpd[1648]: Failed to add NAT-PMP 18294 tcp->192.168.1.67:32400 'NAT-PMP 18294 tcp'
Feb 21 15:52:49 roamast: [EXAP]Deauth old sta in 1 0: DE:5C:10:B8:A0:F5
Feb 21 15:52:49 roamast: eth7: disconnect weak signal strength station [de:5c:10:b8:a0:f5]
Feb 21 15:52:49 roamast: eth7: remove client [de:5c:10:b8:a0:f5] from monitor list
Feb 21 15:54:55 kernel: wl0: random key value: 9652B76F20661D055B1D0201241F66F79E5F8718011F0104A95A41CB1BAC7461
Feb 21 16:07:15 miniupnpd[1648]: Failed to add NAT-PMP 10429 tcp->192.168.1.67:32400 'NAT-PMP 10429 tcp'
Feb 21 16:21:09 kernel: wl0: random key value: AE918198B86AA5A0707D0351D10728BB0D866E0BB4790343908A8CD9C52106CA
Feb 21 17:07:16 miniupnpd[1648]: Failed to add NAT-PMP 13124 tcp->192.168.1.67:32400 'NAT-PMP 13124 tcp'
Feb 21 17:46:45 roamast: [EXAP]Deauth old sta in 1 0: 20:28:BC:7F:D6:28
Feb 21 17:46:45 roamast: eth7: disconnect weak signal strength station [20:28:bc:7f:d6:28]
Feb 21 17:46:45 roamast: eth7: remove client [20:28:bc:7f:d6:28] from monitor list
Feb 21 18:07:19 miniupnpd[1648]: Failed to add NAT-PMP 20854 tcp->192.168.1.67:32400 'NAT-PMP 20854 tcp'
Feb 21 18:52:51 kernel: wl0: random key value: C432CA5014B18F7252A902875251C4BBE003927054E50836FB00CBFE6138E269
Feb 21 18:52:51 roamast: [EXAP]Deauth old sta in 0 0: 58:24:29:E1:46:7F
Feb 21 18:52:51 roamast: eth6: disconnect weak signal strength station [58:24:29:e1:46:7f]
Feb 21 18:52:51 roamast: eth6: remove client [58:24:29:e1:46:7f] from monitor list
Feb 21 19:07:20 miniupnpd[1648]: Failed to add NAT-PMP 13081 tcp->192.168.1.67:32400 'NAT-PMP 13081 tcp'
Feb 21 20:07:21 miniupnpd[1648]: Failed to add NAT-PMP 16395 tcp->192.168.1.67:32400 'NAT-PMP 16395 tcp'
Feb 21 21:07:23 miniupnpd[1648]: Failed to add NAT-PMP 16859 tcp->192.168.1.67:32400 'NAT-PMP 16859 tcp'
Feb 21 21:23:43 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2 --> 5 ] [ 3, 7 --> 8 ]
Feb 21 21:23:43 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
Feb 21 21:23:46 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2, 3 --> 5 ] [ 7 --> 8 ]
Feb 21 21:23:46 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 2500 mbps full duplex
Feb 21 21:24:00 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2 --> 5 ] [ 3, 7 --> 8 ]
Feb 21 21:24:00 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
Feb 21 21:24:03 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2, 3 --> 5 ] [ 7 --> 8 ]
Feb 21 21:24:03 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 2500 mbps full duplex
Feb 21 21:24:53 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2 --> 5 ] [ 3, 7 --> 8 ]
Feb 21 21:24:53 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
Feb 21 21:24:57 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2, 3 --> 5 ] [ 7 --> 8 ]
Feb 21 21:24:57 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 2500 mbps full duplex
Feb 21 21:24:58 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2 --> 5 ] [ 3, 7 --> 8 ]
Feb 21 21:24:58 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
Feb 21 21:25:02 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2, 3 --> 5 ] [ 7 --> 8 ]
Feb 21 21:25:02 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 2500 mbps full duplex
Feb 21 21:25:19 miniupnpd[1648]: Failed to add NAT-PMP 10047 tcp->192.168.1.67:32400 'NAT-PMP 10047 tcp'
Feb 21 22:07:23 miniupnpd[1648]: Failed to add NAT-PMP 29058 tcp->192.168.1.67:32400 'NAT-PMP 29058 tcp'
Feb 21 23:07:24 miniupnpd[1648]: Failed to add NAT-PMP 27195 tcp->192.168.1.67:32400 'NAT-PMP 27195 tcp'
Feb 22 00:07:25 miniupnpd[1648]: Failed to add NAT-PMP 10311 tcp->192.168.1.67:32400 'NAT-PMP 10311 tcp'
Feb 22 01:07:25 miniupnpd[1648]: Failed to add NAT-PMP 18153 tcp->192.168.1.67:32400 'NAT-PMP 18153 tcp'
Feb 22 02:07:26 miniupnpd[1648]: Failed to add NAT-PMP 14019 tcp->192.168.1.67:32400 'NAT-PMP 14019 tcp'

 

[Bhoot®]

UPnP issue, I've always disabled it on Asus routers.

 

[drinkingbird]

We started since a few weeks get random DCs and I'm not sure what the issue could be.
When it happens, I can't even connect to the router at all, neither on LAN or WIFI.


Here are a few snippets from the log.

First snippet is when I know it happend 100%. I can't pin point more spots in the log, as I didn't track the time properly. Maybe one of you can see an issue?

Feb 26 18:37:16 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2 --> 5 ] [ 3, 7 --> 8 ]
Feb 26 18:37:16 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
Feb 26 18:37:44 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 1000 mbps full duplex
Feb 26 18:37:45 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
Feb 26 18:37:47 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 1000 mbps full duplex
Feb 26 18:37:59 miniupnpd[2866]: Failed to add NAT-PMP 10188 tcp->192.168.1.67:32400 'NAT-PMP 10188 tcp'
Feb 26 18:38:18 miniupnpd[2866]: Failed to add NAT-PMP 16620 tcp->192.168.1.67:32400 'NAT-PMP 16620 tcp'

'
[/CODE]

What is connected to port 7? Is that the only thing that goes down? Could be an issue with that device or cabling. May be related to UPNP as the other poster said too, as you have a lot of log messages related to that (though that is not necessarily abnormal, but if you don't specifically need uPNP it should be disabled anyway).

 

[saeris]

Thanks for the insights.
If I disable UPnP, should I the manually open ports for apps that need them?

 

[Tech9]

Your router is in double NAT and UPnP is not working anyway:

Feb 21 02:15:53 miniupnpd[1648]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping

If manual port forwarding is used - you have to open the ports on the upstream router as well. If it's yours - probably lucky (access to the WebUI needed). If it's not yours and your ISP DHCP assigns CG-NAT addresses - not lucky (IPv6 access as potential option).

 

[saeris]

Oddly enough, I did set my actual modem (it's a FritzBox, provided by the ISP) to "Exposed Host" the Asus Router one, so I'd have to only take care of the Ports on the Asus one

 

[saeris]

What is connected to port 7? Is that the only thing that goes down? Could be an issue with that device or cabling. May be related to UPNP as the other poster said too, as you have a lot of log messages related to that (though that is not necessarily abnormal, but if you don't specifically need uPNP it should be disabled anyway).

Not sure what Port 7 could be, since the router only has 4 Physical ports

Edit:
saw that the Log says eth5, which is the 2.5 Gbe port, connected to a 2.5Gbe switch, but even that one has only 5 ports, Port 5 is connected to a Synology NAS, could be Docker Containers doing weird stuff?

 

[drinkingbird]

Not sure what Port 7 could be, since the router only has 4 Physical ports

Edit:
saw that the Log says eth5, which is the 2.5 Gbe port, connected to a 2.5Gbe switch, but even that one has only 5 ports, Port 5 is connected to a Synology NAS, could be Docker Containers doing weird stuff?

Yeah the "port grouping" in the log shows that they are grouping multiple internal switch ports into one external port, probably to get the 2.5G. Your 2.5G port is only coming up at 1G so maybe there is some sort of cabling or setting mismatch going on. If that port is connected to a 2.5G switch and is bouncing, everything on that switch will disconnect every time it bounces. Maybe it keeps trying to come up at 2.5 and is failing.

Not exactly sure what your setup is, if you can't connect via wifi, that is odd as I'm assuming that is not running via the switch/2.5G port. Maybe the internal switching hardware (which includes the wifi bridge) is starting to fail. I guess try disabling the uPNP since it isn't doing anything for you anyway and see if anything improves, but that bouncing port seems odd, especially since it is not negotiating to the correct speed.

 

[saeris]

Aye, did that - maybe I should do a clean reset of the Router. Haven't done that since setting it up and updating

 

[drinkingbird]

Aye, did that - maybe I should do a clean reset of the Router. Haven't done that since setting it up and updating

Yeah after updating firmware especially if it is a big update, factory reset with WPS button and configure from scratch. If that doesn't fix it, you may be having hardware failure.

 

[drinkingbird]

Oddly enough, I did set my actual modem (it's a FritzBox, provided by the ISP) to "Exposed Host" the Asus Router one, so I'd have to only take care of the Ports on the Asus one

But if you aren't getting a Public IP, how does that work - or are you using IPv6 for inbound?

 

[saeris]

But if you aren't getting a Public IP, how does that work - or are you using IPv6 for inbound?

No, I do get a public IP from my ISP router, hence the confusion I guess.