Hi, On Tue, Oct 21, 2025 at 06:47:07AM -0500, Richard Owlett wrote: > On 10/19/25 4:46 PM, Andy Smith wrote: > > So, Richard, can you just: > > > > 1) Show us the output of "ip link show" that shows two different names > > for "enx…" (i.e. do it at least twice, showing different name after > > you've re-plugged it or whatever), and; > > 9: enxf6c0d1541b3e: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc > fq_codel state UNKNOWN mode DEFAULT group default qlen 1000 > link/ether f6:c0:d1:54:1b:3e brd ff:ff:ff:ff:ff:ff > > *POWER DEVICE OFF/ON* > > 10: enx424c8f375f4c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc > fq_codel state UNKNOWN mode DEFAULT group default qlen 1000 > link/ether 42:4c:8f:37:5f:4c brd ff:ff:ff:ff:ff:ff
Thank you! That's fun. > > 2) tell us where you are stuck with vnstat? > > Basically I don't know *what* "I don't know". > This morning I found a Debian aware tutorial for vnstat: > > https://www.linuxbabe.com/monitoring/install-vnstat-debian-8ubuntu-16-04-server-monitor-network-traffic > > I'll see if I can reproduce their examples. Possibly it doesn't even matter that your network device changes name. If it *does* end up mattering, you can look back through this thread where people have posted various suggestions on how to deal with that. I don't think I saw possibly the simplest one, which would be to disable "predictable naming" with a kernel command line option: Edit /etc/default/grub and add "net.ifnames=0" to the GRUB_CMDLINE_LINUX_DEFAULT line, update-grub, and then reboot. I expect then that your motherboard's Ethernet will be eth0 and your modem will always be eth1. Personally I find this less elegant than picking a name for the interface with a systemd .link file, but it is a lot simpler. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
