USB net interface changes (Android tethering)

[patient0]

Hi,

I’m using a small fanless device with VyOS 1.5-rolling on as my travel router, with an Android phone in USB tethering mode connected to it.
So far so good, it’s working with Technitium DNS in a container and a Wireguard tunnel to my (pfSense) router at home.

The fanless device has two Intel I211 1Gbit NICs configured as eth0 (WAN) and eth1 as part of the LAN bridge br0 (the bridge’s other member is wlan0).

The issue is that if I connect the Android phone right after I switch on the device the interface name is eth3. If I disconnect the phone while the device is on and reconnect it, the interface name is eth2.

One option would be to wait for VyOS to boot up completely and only then connect the phone. But then VyOS is not happy since the ethernet config for eth2 is invalid since it didn’t exist during boot.

The MAC address changes all time, of course, it being Android USB tethering. Setting the hw-id is therefore not an option either.

Playing around with udev rules didn’t help, but that is maybe because my limited knowledge of udev rules.

Does someone have an idea how I could fix it?

Are custom udev rules supposed to work? I did try adding a renaming rule like the following without success:

SUBSYSTEM=="net", ACTION=="add", ENV{ID_NET_NAME_PATH}=="eth3", NAME="ethUSB0"

[patient0]

Good Morning, Sorry I can’t reply to everyone, just too many replies .

udev rules do work, the renaming does not. Also calling a script triggered by subsystem==net and device specific environments variables doesn’t work either.

I assume it’s too early and interfering with VyOS scripts or udev rules. If I call the script manually it does work beautifully. To bad no hook for USB events.

I’ll keep you all updated