(Resending using "plain text mode due to misunderstanding Google settings to accomplish this.)
I can confirm that I have experienced this on a Debian Bookworm install but am unable to duplicate it at the moment. The kernel installed is ```text hbarta@sutyzam:~$ uname -a Linux sutyzam 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux hbarta@sutyzam:~$ ``` In addition to the changing MAC, I recall that the device name (presently `enx0050b6239f84`) was also changing. That seems to make sense as the device name was derived from the MAC address `00:50:b6:23:9f:84`. I was able to work around this using a .link file in `/etc/systemd/network` and matching on the driver, reported by `ethtool` as: ```text root@sutyzam:~# ethtool -i enx0050b6239f84 driver: ax88179_178a version: 6.1.0-18-amd64 firmware-version: expansion-rom-version: bus-info: 2-1.3:1.0 supports-statistics: no supports-test: no supports-eeprom-access: yes supports-register-dump: no supports-priv-flags: no root@sutyzam:~# ``` `lsusb` reports it as ```text root@sutyzam:~# ethtool -i enx0050b6239f84 driver: ax88179_178a version: 6.1.0-18-amd64 firmware-version: expansion-rom-version: bus-info: 2-1.3:1.0 supports-statistics: no supports-test: no supports-eeprom-access: yes supports-register-dump: no supports-priv-flags: no root@sutyzam:~# ``` And this is the "Amazon Basics" USB3/1Gb adapter. best, -- Beautiful Sunny Winfield
