Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net: 15.4 MAC addresses are shown differently between shell "net iface" and "ieee15_4 get_ext_addr" #4936

Closed
pfalcon opened this issue Nov 14, 2017 · 1 comment
Assignees

Comments

@pfalcon
Copy link
Contributor

pfalcon commented Nov 14, 2017

One of them is shown reversed comparing to another. E.g. 11:22:...:88 vs 88:...:22:11.

@tbursztyka
Copy link
Collaborator

net iface is showing you the mac address, which is used by default to create the extended address.
But the extended address could be something else, it's possible to change it.

Extended address is taken from iface's 15.4 context, and that one has to be in little endian as 15.4 frames requires it.
Shell could show it the same way as mac, why not. I'll make sure the set ext addr assumes this same order so it will reverse it.

tbursztyka pushed a commit to tbursztyka/zephyr that referenced this issue Nov 14, 2017
802.15.4, as other radio tech, works in little endian on network level.
To keeps things simple, the inner context per-interface, stores the
extended address that way. But it can be confusing in shell then, so
let's work handle these addreses through EUI-64 format there.

Fixes zephyrproject-rtos#4936

Signed-off-by: Tomasz Bursztyka <[email protected]>
nashif pushed a commit that referenced this issue Nov 14, 2017
802.15.4, as other radio tech, works in little endian on network level.
To keeps things simple, the inner context per-interface, stores the
extended address that way. But it can be confusing in shell then, so
let's work handle these addreses through EUI-64 format there.

Fixes #4936

Signed-off-by: Tomasz Bursztyka <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants