New here, been having issues.

[Andromendous]

Hello all, new to the forum, wonding if any of you could help..
Been on the AX86u Pro for a while now. Have had some lag and packet loss for a while, had ISP come out at least 10 times no bs. They swear up and down my lines are the best in my whole town.

I keep seeing these messages on the newest merlin, I switched back to stock for a while and never saw any. so switched back and now I got this again.
Any ideas? I tried a new modem, no change, new cables, tried a new BE router and seemed like it worked great but the wifi kept dropping.


Thanks for any help.

Jan 7 17:31:52 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Jan 7 17:31:52 kernel: br0: port 1(eth1) entered disabled state
Jan 7 17:31:54 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 10 mbps full duplex
Jan 7 17:31:54 kernel: br0: port 1(eth1) entered blocking state
Jan 7 17:31:54 kernel: br0: port 1(eth1) entered forwarding state
Jan 7 18:34:46 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Jan 7 18:34:46 kernel: br0: port 1(eth1) entered disabled state
Jan 7 18:34:48 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 1000 mbps full duplex
Jan 7 18:34:48 kernel: br0: port 1(eth1) entered blocking state
Jan 7 18:34:48 kernel: br0: port 1(eth1) entered forwarding state
Jan 7 19:19:05 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Jan 7 19:19:05 kernel: br0: port 1(eth1) entered disabled state
Jan 7 19:19:07 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 10 mbps full duplex
Jan 7 19:19:07 kernel: br0: port 1(eth1) entered blocking state
Jan 7 19:19:07 kernel: br0: port 1(eth1) entered forwarding state
Jan 7 19:20:13 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Jan 7 19:20:13 kernel: br0: port 1(eth1) entered disabled state
Jan 7 19:20:15 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 1000 mbps full duplex
Jan 7 19:20:15 kernel: br0: port 1(eth1) entered blocking state
Jan 7 19:20:15 kernel: br0: port 1(eth1) entered forwarding state
Jan 7 20:27:35 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Jan 7 20:27:35 kernel: br0: port 1(eth1) entered disabled state
Jan 7 20:27:37 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 10 mbps full duplex
Jan 7 20:27:37 kernel: br0: port 1(eth1) entered blocking state
Jan 7 20:27:37 kernel: br0: port 1(eth1) entered forwarding state
Jan 7 20:27:56 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Jan 7 20:27:56 kernel: br0: port 1(eth1) entered disabled state
Jan 7 20:28:08 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 1000 mbps full duplex
Jan 7 20:28:08 kernel: br0: port 1(eth1) entered blocking state
Jan 7 20:28:08 kernel: br0: port 1(eth1) entered forwarding state



Jan 7 20:35:46 kernel: device eth6 left promiscuous mode
Jan 7 20:35:46 kernel: br0: port 6(eth6) entered disabled state
Jan 7 20:35:46 kernel: CFG80211-ERROR) wl_dfs_cac_notify_status :
Jan 7 20:35:46 kernel: In wl_dfs_cac_notify_status chanspec 0xe12a DFS state 0
Jan 7 20:35:46 kernel: device eth7 left promiscuous mode
Jan 7 20:35:46 kernel: br0: port 7(eth7) entered disabled state
Jan 7 20:35:46 get_ext_phy_id: 0/1/0/0
Jan 7 20:35:46 kernel: CFG80211-ERROR) wl_allocate_wowl_config :
Jan 7 20:35:46 kernel: Wowl not supported (-23)
Jan 7 20:35:46 kernel: br0: port 6(eth6) entered blocking state
Jan 7 20:35:46 kernel: br0: port 6(eth6) entered disabled state
Jan 7 20:35:46 kernel: device eth6 entered promiscuous mode
Jan 7 20:35:46 kernel: br0: port 6(eth6) entered blocking state
Jan 7 20:35:46 kernel: br0: port 6(eth6) entered forwarding state
Jan 7 20:35:46 kernel: CFG80211-ERROR) dhd_config_dongle :
Jan 7 20:35:46 kernel: Dongle is already up
Jan 7 20:35:46 kernel: CFG80211-ERROR) wl_allocate_wowl_config :
Jan 7 20:35:46 kernel: Wowl not supported (-23)
Jan 7 20:35:46 kernel: CFG80211-ERROR) wl_dfs_cac_notify_status :
Jan 7 20:35:46 kernel: In wl_dfs_cac_notify_status chanspec 0xe12a DFS state 0
Jan 7 20:35:46 kernel: br0: port 7(eth7) entered blocking state
Jan 7 20:35:46 kernel: br0: port 7(eth7) entered disabled state
Jan 7 20:35:46 kernel: device eth7 entered promiscuous mode
Jan 7 20:35:46 kernel: br0: port 7(eth7) entered blocking state
Jan 7 20:35:46 kernel: br0: port 7(eth7) entered forwarding state
Jan 7 20:35:49 kernel: CFG80211-ERROR) wl_dfs_cac_notify_status :
Jan 7 20:35:49 kernel: In wl_dfs_cac_notify_status chanspec 0xe12a DFS state 0

 

[degrub]

What exact Merlin firmware version ?
What exact stock firmware version ?
Roll back to the previous Merlin and see if it goes away.

 

[RMerlin]

A link dropping to 10 Mbps usually indicates a device going into sleep mode, so nothing abnormal there. It goes to the lowest possible speed as it doesn`t need more than that to just listen for WOL packets.

 

[Andromendous]

A link dropping to 10 Mbps usually indicates a device going into sleep mode, so nothing abnormal there. It goes to the lowest possible speed as it doesn`t need more than that to just listen for WOL packets.

Ok, so nothing seems abnormal to you. Thats good news. Interesting though because I disable all power saving modes, green ethernet etc. on my computer. Thank you for your input.

 

[Andromendous]

A link dropping to 10 Mbps usually indicates a device going into sleep mode, so nothing abnormal there. It goes to the lowest possible speed as it doesn`t need more than that to just listen for WOL packets.

Also whats weird is every time I go back and look at logs, the times are all different, even the logs are completely different, like, I just made this post, turned off my computer for less than an hour, came back and checked the logs again, and the ones I just posted are completely gone and all the time stamps are different, everything is different.

 

[Andromendous]

What exact Merlin firmware version ?
What exact stock firmware version ?
Roll back to the previous Merlin and see if it goes away.

Merlin - RT-AX86U_PRO_3006_102.6_0

Stock - ASUS RT-AX86U Pro Firmware version 3.0.0.6.102_34406

 

[Tech9]

Also whats weird is every time I go back and look at logs, the times are all different, even the logs are completely different

System Log contains messages for multiple events. In less than an hour it can log a full page of new messages. This by itself doesn't indicate presence of issues.

I keep seeing these messages on the newest merlin, I switched back to stock for a while and never saw any.

May be related to different log level in Asuswrt and Asuswrt-Merlin. Log level in Asuswrt-Merlin is customizable. Also by itself doesn't indicate presence of issues.

 

[kstamand]

@Andromendous - Your initial concern was about packet loss, but the logs provided only seem to indicate a wired device (eth1) and possibly some wireless devices (eth6 and eth7) dropping LAN side connections. Nothing in the log indicates WAN link issues, so not sure why you are involving the ISP - unless there are other issues not noted in the initial post

Based on the log records in posted, have a look at whatever is plugged into the ETH1 port on the router. As RMerlin noted, it appears that device is going into sleep mode almost every hour. Assuming eth6 and eth7 are for wireless clients, those devices could also be going into sleep mode or power saving mode as well.

I hope this helps

 

[bbunge]

If your network is working well and looking at the log bothers you, don't look at the log!

 

[Tech9]

I keep seeing these messages on the newest merlin, I switched back to stock for a while and never saw any.

In general my recommendation to people who can't do basic networking troubleshooting themselves is to stick to ISP provided equipment (their responsibility to maintain). In case it was replaced with own equipment for whatever reason (own responsibility to maintain) - run original firmware with close to default settings.

 

[Viktor Jaep]

Have had some lag and packet loss for a while, had ISP come out at least 10 times no bs. They swear up and down my lines are the best in my whole town.

I guess my question to the OP is... what tools or methods did you use to determine that you actually are still experiencing "lag and packet loss for a while"? Do you have any data to back this up? If so, please share. Also, did your ISP provide any data about why your "lines" are considered "the best in my whole town"? And what was this in comparison to?