Incorrect MAC address

[Vic-s]

Maybe it is a KEF bug, but if I query the MAC address it is different from what I get when reaching over the network.
The last 2 bytes differ.
Python

from pykefcontrol.kef_connector import KefConnector
my_speaker = KefConnector("192.168.2.190")
my_speaker.mac_address
'84:17:15:15:YY:ZZ'

Or browser
http://192.168.2.190/api/getData?path=settings:/system/primaryMacAddress&roles=value
[
{
"type": "string_",
"string_": "84:17:15:15:YY:ZZ"
}
]

But from the terminal

ping 192.168.2.190
<...>
arp -a
(192.168.2.190) at 84:17:15:15:WW:XX [ether] on eno1

This is also reported by the fing app on my smartphone

Anyone else experiencing this?

[Vic-s]

Ok I found the MAC returned is for the physical interface while I am using the wireless interface.
This makes sense.
See:
http:///api/getData?path=network:info&roles=value

[mjbrands]

I see the same thing on my LSX 2 speakers (firmware LSXII_V1453), but it is not just the API returning the wrong data; the web page (/index.fcgi) shows the wrong MAC address as well.

So to be clear: both the API and the index.fcgi return the MAC of the Ethernet port, regardless of whether LAN or WiFi is being used.

For the API you could imagine that the LAN interface is simply always referred to as 'primary', but the index.fcgi shows a bunch of WiFi related settings (such as SSID, BSSID and Encryption) but then shows the LAN MAC instead of the WiFi one.

I (attempted) to create a bug report for KEF - probably it will end up in some marketing mailbox, where it will not neatly fit into one of the available categories and get discarded.

[N0ciple]

@Vic-s and @mjbrands,

Thank you for bringing up this issue! As I primarily use my LS50W2 via Ethernet, I wasn't aware of this behavior. While there might be a straightforward method to identify the wireless interface MAC address from the wired MAC address, I haven't yet searched how to determine the active interface.

Please inform me if this issue is crucial for you and I will have a look. On the contrary, at the moment, I am not planning to invest time in debugging this.

[mjbrands]

Hi Robin, To be honest, I think this is a bug in the firmware and not your firmware. My reason for saying this is that the web page also shows the wrong MAC address. If KEF (ever) fixes this, then your library already does the right thing. For me this is not an issue, more of an annoyance (with the speaker). I my case, the two MAC addresses differ in the last two octets - they're not subsequent like you often see in switches and they also don't have a different vendor ID (which you see often on laptops - LAN MAC has Dell as the vendor and WiFi MAC has Intel). Cheers, Mathijs

…

On Sun, 12 Mar 2023, 17:56 Robin Dupont, ***@***.***> wrote: @Vic-s <https://github.com/Vic-s> and @mjbrands <https://github.com/mjbrands>, Thank you for bringing up this issue! As I primarily use my LS50W2 via Ethernet, I wasn't aware of this behavior. While there might be a straightforward method to identify the wireless interface MAC address from the wired MAC address, I haven't yet searched how to determine the active interface. Please inform me if this issue is crucial for you and I will have a look. On the contrary, at the moment, I am not planning to invest time in debugging this. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5AVK6RUWOBNBEZSDUGVQLW3X55XANCNFSM6AAAAAATP4W4TI> . You are receiving this because you were mentioned.Message ID: ***@***.***>