Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 2901

General Debian • Re: Building the nest

$
0
0
Bugs in the nest!
notice the available net interfaces:

Code:

$ ls /sys/class/netenp10s0  enp1s0  enp8s0  enp9s0  Glan  lo
and when asking to explain itself:

Code:

$  udevadm test-builtin net_setup_link /sys/class/net/enp10s0.....Created link configuration context.enp10s0: Device has name_assign_type=4enp10s0: Device has addr_assign_type=0ID_NET_DRIVER=virtio_netenp10s0: Config file /etc/systemd/network/10-nested-Wlan.link is appliedenp10s0: Using static MAC address.enp10s0: Policies didn't yield a name, using specified Name=Wlan.ID_NET_LINK_FILE=/etc/systemd/network/10-nested-Wlan.linkID_NET_NAME=Wlan
and the desktop panel indicator says Wlan is dead, even though it is working...not as Wlan, but working

Let's ask someone else:

Code:

# vnstat --add -i WlanError: Unable to get interface "Wlan" statistics.Only available interfaces can be added for monitoring.The following interfaces are currently available:    enp1s0 Glan enp10s0 enp8s0 enp9s0 
The interface is working because of a redundant declaration in /etc/network/interfaces.d/ defining enp10s0. Without it the interface does not work while the name is still confused - it was the last addition.

Initial boot is always wrong, restarts often rename correctly.
This is a middle layer VM, using libvirt and virt-manager.
enp10s0 is a macvtap of the host MB port, also Wlan, and serving multiple vm's, all working
enp1s0, enp8s0, enp9s0 are not configured in the host and vfio passed to this guest,
declared as vfio in this guest, they pass again to the next layer and work fine.
Glan is the 4th of the quad vfio passed to this vm, however it is not passed but rather a macvtap.

Yes, I still like systemd, and will keep trying.

Statistics: Posted by CwF — 2024-04-21 02:02



Viewing all articles
Browse latest Browse all 2901

Trending Articles