View Single Post
Old 07-19-2018, 04:37 PM   #428
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@CH23: Fantastic! Thanks for your tests .

FWIW, by default, the MAC you see in ifconfig (on the device's side) is the dev_addr bit of the g_ether arguments.

I have a K4 connected right now:
Code:
usb0      Link encap:Ethernet  HWaddr EE:19:00:0E:10:CB
(Granted, that's far from the best example, since I have my USBNet script configured to generate a device-specific NIC to be able to plug multiple devices concurrently, so, the OUI (EE:19:00) matches the module arguments, but the NIC (0E:10:CB) is tweaked)).

You can tweak it after the fact w/
Code:
ifconfig usb0 hw ether xx:xx:xx:xx:xx:xx
if you really want to, but it's basically only of interest if you need to plug multiple devices concurrently, otherwise, you're fine with the defaults.

On the computer's side, I'm seeing the host_addr, as expected:
Code:
ether ee:49:00:0e:10:cb  txqueuelen 1000  (Ethernet)
EDIT: In fact, it's the host_addr that needs to be tweaked to be able to plug multiple things concurrently, so, yeah, setting the MAC on the Kobo's side serves zero purpose.

Last edited by NiLuJe; 07-19-2018 at 04:40 PM.
NiLuJe is offline   Reply With Quote