Jump to content
  • 0

Wi-Fi clients on Mesh Wi-Fi System extenders shown as "Wired" in Registered Clients list since 5.1.1


Question

Posted

Hi,

Setup: Hero DSL (KN-2410) as Mesh Wi-Fi System controller, with 2x Keenetic Giga extenders connected via wired Ethernet backhaul.

Before updating to the 5.1.x branch, the Registered Clients list correctly showed the connection type (Wi-Fi vs. Wired) for each client, including devices connected wirelessly to the extenders (Meross plugs, Sonoff switches, phones, etc.).

After updating to 5.1.1, most of these Wi-Fi-only clients are now shown as "Wired" with a port number (e.g. "Port 1" on the extender), even though they have no Ethernet connection at all and are only ever connected via Wi-Fi. The behavior is inconsistent — some clients still show correctly as Wi-Fi, while others (the majority) now show as wired.

I noticed the 5.1 Beta 2 changelog includes: "MWS: enabled the display of connection details for client devices connected to Wi-Fi System Extenders via Ethernet [NDM-4429]". Could this change be related to the misclassification I'm seeing? Is this a known issue, and is there an ETA for a fix?

Screenshot attached showing the Registered Clients list — devices like "Meross Priz 1", "Sonoff Bora Anahtar", "Bora iPhone'u" etc. are Wi-Fi-only devices but are shown as "Kablolu" (Wired) / Port 1 on the Giga extender.

Router: Hero DSL (KN-2410), KeeneticOS 5.1.1
Extenders: 2x Keenetic Giga, also on 5.1.1

Thanks!

clients.png

mesh.png

1 answer to this question

Recommended Posts

  • 0
Posted
3 hours ago, Atalante said:

Hi,

Setup: Hero DSL (KN-2410) as Mesh Wi-Fi System controller, with 2x Keenetic Giga extenders connected via wired Ethernet backhaul.

Before updating to the 5.1.x branch, the Registered Clients list correctly showed the connection type (Wi-Fi vs. Wired) for each client, including devices connected wirelessly to the extenders (Meross plugs, Sonoff switches, phones, etc.).

After updating to 5.1.1, most of these Wi-Fi-only clients are now shown as "Wired" with a port number (e.g. "Port 1" on the extender), even though they have no Ethernet connection at all and are only ever connected via Wi-Fi. The behavior is inconsistent — some clients still show correctly as Wi-Fi, while others (the majority) now show as wired.

I noticed the 5.1 Beta 2 changelog includes: "MWS: enabled the display of connection details for client devices connected to Wi-Fi System Extenders via Ethernet [NDM-4429]". Could this change be related to the misclassification I'm seeing? Is this a known issue, and is there an ETA for a fix?

Screenshot attached showing the Registered Clients list — devices like "Meross Priz 1", "Sonoff Bora Anahtar", "Bora iPhone'u" etc. are Wi-Fi-only devices but are shown as "Kablolu" (Wired) / Port 1 on the Giga extender.

Router: Hero DSL (KN-2410), KeeneticOS 5.1.1
Extenders: 2x Keenetic Giga, also on 5.1.1

Thanks!

clients.png

mesh.png

UPDATE — CLI-level evidence:

My topology: Hero (controller) → Giga 1 (extender, wired, first hop) → Giga 2 (extender, wired, second hop, connected via its Port0/WAN into Giga 1's Port1/LAN).

I ran `show associations` via SSH on all three devices (Hero, Giga 1, Giga 2) to check the real wireless association tables:

- All the clients that are misdisplayed as "Wired/LAN" under Giga 1 in the Web Interface (Sonoff switches, Meross plugs, a Tapo plug, and an Aqara Hub) are correctly and exclusively listed as authenticated Wi-Fi stations on Giga 2's own radio (WifiMaster0/AccessPoint0) in Giga 2's `show associations` output.

- None of these MACs appear at all in the `show associations` output of Giga 1 or Hero — confirming Giga 1 has no real wired or wireless connection to these devices, and this isn't a case of them roaming or being genuinely reachable from Giga 1.

This confirms the underlying wireless association data is correct and available at the CLI level, but the Web Interface's client list / Mesh Wi-Fi System dashboard misattributes second-hop extender clients (Giga 2) as wired clients grouped under the first-hop extender (Giga 1). The bug appears to be purely in the controller-side aggregation/display logic, not in the actual mesh networking or association data.

Let me know if a support ticket / diagnostic log capture would help — happy to provide more data.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...