Wired device shown as 5 GHz wireless device

[man_with_the_stick]

Hi.

I have a RT-AX86S router with the Asuswrt-Merlin firmware (version 3004.388.8_4) and a computer connected to the first ethernet port of the router. It wasn't my intention to connect it there, it just happened. In the Network Map page, when I click on the View List and group the devices according to the interface, the wired computer is not shown in the Wired device group. It is shown in the 5 GHz wireless group. I have used ifconfig on the computer to find out the MAC address and the IP address of the ethernet interface and then searched them in the connected client list on the router.
I have searched on this forum for similar issues. I have found issues where the wireless devices were shown as wired ones and only one issue where the wired device was shown as 2.4 GHz wireless device (https://www.snbforums.com/threads/wired-shows-as-wireless.88216/ and js28194 didn't mention the ethernet port where the wired devices was connected).
Is this issue a known one? Can it be solved?

Regards,
Alexandru.

 

[Tech9]

Is this issue a known one?

Known Client List quirks. Not accurate, disregard. Comes from Asuswrt upstream, never fixed.

 

[OzarkEdge]

Known Client List quirks. Not accurate, disregard. Comes from Asuswrt upstream, never fixed.

Agreed, although my Client List(s) have been accurate in the recent past... instills a bit of confidence of late.

OE

 

[Tech9]

There is a fix for this, but not worth the time. Next time a client with the same MAC on different interfaces connects the last one used will stuck again.

 

[soccerjoshj07]

Is this a problem also in reverse, where I have a client connected to the 2.4ghz band but it shows up in router network list as ethernet?

 

[OzarkEdge]

Is this a problem also in reverse, where I have a client connected to the 2.4ghz band but it shows up in router network list as ethernet?

No, it's just a 'cosmetic' error.

OE

 

[soccerjoshj07]

Got it. Earlier today I was seeing one of my Nest CO/smoke detectors (that's wireless 2.4ghz) show up as Ethernet in the network list. Chalking it up to a random bug.

No, it's just a 'cosmetic' error.

OE

 

[scootertramp]

Understanding this is considered to be a cosmetic error. If one wanted to is there a process that could be used to
clear the offending device listing and see if it comes back or not?


Router: AX92U
Firmware: 3004.388.8_4-gnuton1

 

[scootertramp]

Understanding this is considered to be a cosmetic error. If one wanted to is there a process that could be used to
clear the offending device listing and see if it comes back or not?


Router: AX92U
Firmware: 3004.388.8_4-gnuton1

Due to the overwhelming response to this question I decided to see if a basic group of steps could correct
a wired device showing partially as a wireless device.

1) Shutdown the offending device.
Results: No longer showing in aimesh page, but still in network map client list and lan dhcp server offline host list.
Cleared host from offline host list and waited about an hour. Still shows in network map client list.
2) Cleared from offline host list a second time and restarted dnsmasq process on the router.
Results: No longer in network map client list or offline host list.
3) Waited about a half-hour then started the device.
Results: After two hours there still was still no sign of the device on any router page.
The application running on the device is running fine. I can check it's status using the application web GUI.
Samba and nfs shares managed by this host are available on other devices.
4) Rebooted router.
Results: Device now shows correctly.

Just a side note I had rebooted the router prior to my initial post of this question. So a reboot by its self did nothing to resolve.
Given this is the first time I have seen this issue after running this router for several years and this router has been on the end of life list
for awhile. I will most likely be on a different router before too long. I do question why ASUS is still pushing this model.


Thanks Alan

 

[Tech9]

You can't fix the buggy client list on your end. It's the way it works on Asus routers. After router reset it may show the connected devices correctly for some time, then it messes up itself again. Not worth the troubleshooting time.

 

[sfx2000]

You can't fix the buggy client list on your end. It's the way it works on Asus routers. After router reset it may show the connected devices correctly for some time, then it messes up itself again. Not worth the troubleshooting time.

Not sure it is the client - Broadcom's WL drivers are a bit odd - they show up to the host OS as ethernet with special flavor... Mediatek and Qualcomm/Atheros use the mac80211 linux stack, so they are a bit more predictable here...

that, and as mentioned, AsusWRT and the network map functionality has been buggy for some time.....

 

[scootertramp]

Not sure it is the client - Broadcom's WL drivers are a bit odd - they show up to the host OS as ethernet with special flavor... Mediatek and Qualcomm/Atheros use the mac80211 linux stack, so they are a bit more predictable here...

that, and as mentioned, AsusWRT and the network map functionality has been buggy for some time.....

Thanks for your response.

This client is using Realtek.
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
Kernel driver in use: r8169

Alan