Network traffic graph is empty?

[Giovanni]

I'm running 5.0 beta2, I am trying to understand why the network traffic graph when looking at the host itself is empty?

default network configuration (for the most part) so I was expecting to see this graph be polling vmbr0 traffic. Currently iftop -i vmbr0 sees the traffic just fine.

is the network graph configurable somewhere? Example scenarios if my traffic comes in from another bridge or if I wanted to monitor all the physical NICs in the machine it would be helpful if the feature existed.

 

[dcsapak]

no we do not count traffic of bridges, but of physical network cards (e.g. ethX, enY, etc.)

 

[fabian]

this is fixed in git already, but not yet released in package form: https://git.proxmox.com/?p=pve-manager.git;a=commit;h=939b71ab48294f3a506e2cdd3037f33ea4435ad4

 

[Giovanni]

this is fixed in git already, but not yet released in package form: https://git.proxmox.com/?p=pve-manager.git;a=commit;h=939b71ab48294f3a506e2cdd3037f33ea4435ad4

thanks.
how long does it usually take for a git commit to make it all the way upstream where I may be able to apt-get upgrade ?

 

[fabian]

thanks.
how long does it usually take for a git commit to make it all the way upstream where I may be able to apt-get upgrade ?

normally, not very long until it hits at least the pvetest repository. at the moment, a bit longer than usual as we are integrating a rather big changeset across multiple repositories/packages. as a workaround you can rename your physical devices to the old "ethX" names (see https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ and https://www.freedesktop.org/software/systemd/man/systemd.link.html , I'd recommend testing it in a PVE VM first before potentially locking yourself out of a production machine).

 

[Giovanni]

normally, not very long until it hits at least the pvetest repository. at the moment, a bit longer than usual as we are integrating a rather big changeset across multiple repositories/packages. as a workaround you can rename your physical devices to the old "ethX" names (see https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ and https://www.freedesktop.org/software/systemd/man/systemd.link.html , I'd recommend testing it in a PVE VM first before potentially locking yourself out of a production machine).

thanks, I appreciate you guys being so responsive on your open source project as you always are... to think I started using pve in 2008 and the project keeps going strong thanks to you.