On 06.09.17 18:14, Ray via luv-main wrote:
On 06.09.2017 10:27, Ray via luv-main wrote:
I ran the command "nmcli connection show" to see what was happening and was stunned to find the following report........... ---------------------------------------------------------------- enx0c5b8f279a64: connected to Wired connection 3 "HUAWEI MOBILE" ethernet (rndis_host), 0C:5B:8F:27:9A:64, hw, mtu 1500 ip4 default inet4 192.168.8.100/24 inet6 fe80::4636:a274:6574:96fa/64
enp5s0: unavailable ...
enx0c5b8f279a64 is NOT random 0c5.......64 is the MAC address of the 4G dongle so will only change if the dongle changes. Why it does not use a USB ethernet naming convention (if there is one) I do not know.
OK, I could buy that for a hotplug dongle, but enp5s0 looks awfully short for a MAC? (Mine came out as enp2s0, before I gave it the flick.)
I was wondering though about some of these weird device id's
The excuse made for the obfuscated interface names at the user level is that they "avoid name volatility in the event of NIC replacement". However, if it's the MAC address which provides the enx0c5b8f279a64 and enp5s0 hoo-ha, then that instead _causes_ name volatility as soon as a NIC is replaced. It is difficult to recognise that funny way of doing things as a solution. Erik