Traffic not shown on network page for some devices which are shown on Metrics page

[ne20002]

Page: Network

I found that traffic is not shown on network page for some devices whereas it is shown in details page.

compared to

vnet devices are ports on openvswitch used for connection kvm virtual machines.

[martinpitt]

This is some impedance mismatch. The Metrics page shows all raw network interfaces, whereas Networking shows the interfaces as "filtered" by NetworkManager. It apparently considers e.g. vnet4 as "inactive" while it does transmit data. Can you please give the output of the following commands, to get a first impression what happens here?

ip a show vnet4
nmcli d
nmcli d show vnet4

feel free to replace IP addesses and such with XXX -- I'm mostly interested in up/down and whether these have valid IPs at all.

[ne20002]

Here y go

pi@u-nas0: ~$ ip a show vnet3
9: vnet3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master ovs-system state UNKNOWN group default qlen 1000
    link/ether fe:54:00:25:da:46 brd ff:ff:ff:ff:ff:ff
pi@u-nas0: ~$ nmcli d
DEVICE      TYPE         STATE         CONNECTION         
enp2s0      ethernet     connected     Wired connection 2 
vnet0       tun          disconnected  --                 
vnet1       tun          disconnected  --                 
vnet2       tun          disconnected  --                 
vnet3       tun          disconnected  --                 
eno1        ethernet     unmanaged     --                 
lo          loopback     unmanaged     --                 
br0         openvswitch  unmanaged     --                 
ovs-system  openvswitch  unmanaged     --

pi@u-nas0: ~$ nmcli d show vnet3
GENERAL.DEVICE:                         vnet3
GENERAL.TYPE:                           tun
GENERAL.HWADDR:                         FE:54:00:25:DA:46
GENERAL.MTU:                            1500
GENERAL.STATE:                          30 (disconnected)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --

[martinpitt]

Thanks -- so this is not actually "wrong" -- the interface is really "inactive" in the sense that it does not have any IPs and is down. That it gets traffic routed through it is likely because it's some kind of backend thing for a compound bridge, or being attached to a VM?

[garrett]

Should we show the inactive interfaces, but possibly collapsed down as they're usually irrelevant?

Something like this: "...and 4 inactive interfaces. (Show all)"

This could apply to both views.

Or should we make the two views similar by just hiding the inactive ones in the metrics view too?

WDYT?

[ne20002]

I don't want to have the information hidden. It gives me a view on what's going on on my virtual machines. ;)

The facinating thing is, that even that the 'inactive' interfaces are shown without down/upload rate on network page, the graphs for the interfaces are working (should have that in the picture as well).

The 'inactive' interfaces are ports of a openvswitch bridge and are created/attached when a kvm virtual machine is started (and removed when the vm shuts down). eno1 is the uplink interface for the ovs bridge where enp2s0 is the managment interface of my host.

[mvrk69]

I have similar issue, seems network page is not able to show openvswitch interfaces

On the metrics page i can see the interfaces and if i click on the interface on the metrics page, sends me to network -> interface, and i get this info:

br0 Unknown "ovs_interface" XX:XX:XX:XX:XX:XX