3 ms·
> Android's EthernetTracker service only acknowledges interfaces that are named ethX If this is true, this is the stupidest goddamn thing I have ever heard of.
by 0xbadcafebee 1y ago
> Android's EthernetTracker service only acknowledges interfaces that are named ethX
If this is true, this is the stupidest goddamn thing I have ever heard of. We fixed this with linux distributions in the 2000s. It was obvious even back then that some device drivers just made up their own device name prefix, so you had to probe the system to find what kind of device it was. (I know the wifi stack has changed a lot over the years, but there's always been a way to detect if a device was wireless or not)
Because consistency is kind of useful, there are also multiple tools which can rename an interface, and I think most linux distros today use udev to make this automatic. Under the hood it's just calling the kernel's SIOCSIFNAME ioctl. Modern kernels even have a fancy feature so you can change the name to "wlan*" (actually "wlan%d") and it will just assign a new number after "wifi".
- preisschild 1y agoI wonder if it would make sense to use NetworkManager on Android (with the Android Wireless Settings UI acting as the NetworkManager GUI)
- literalAardvark 1y agoIt's because some usbX devices must be used by other modules, and managing the list is something they didn't want to do. So ethX it is.