As I read the comment, it seems to say that a link from host-to-host should be named usb0, and that locally generated MAC addresses are usually host-to-host.
I think our use cases shows that it's not always host-to-host though, since the XMs are just regular boards.
How can we fix this?
- well obvioiusly by seting a MAC address in all boards
- we could have another MAC address generation functions which doesn't use the "locally generated" space, but something else, perhaps some vendor space, or just plain random; it's kind of evil, but then the boards don't have a MAC
- we could rename the interface in userspace, as the comment suggests; it's a bit ugly to workaround in userspace though, I'd rather fix the kernel
- we could add a flag to net devices to indicate whether these are likely host-to-host or for use on a regular network, in which case usbnet would also use eth%d
Marcin had a similar issue in the past www.spinics. net/lists/ netdev/ msg95158. html
http://
As I read the comment, it seems to say that a link from host-to-host should be named usb0, and that locally generated MAC addresses are usually host-to-host.
I think our use cases shows that it's not always host-to-host though, since the XMs are just regular boards.
How can we fix this?
- well obvioiusly by seting a MAC address in all boards
- we could have another MAC address generation functions which doesn't use the "locally generated" space, but something else, perhaps some vendor space, or just plain random; it's kind of evil, but then the boards don't have a MAC
- we could rename the interface in userspace, as the comment suggests; it's a bit ugly to workaround in userspace though, I'd rather fix the kernel
- we could add a flag to net devices to indicate whether these are likely host-to-host or for use on a regular network, in which case usbnet would also use eth%d