Lots of network-related syslog noise

Discussion in 'Linux Guest OS Discussion' started by nedkonz, Mar 24, 2021.

  1. nedkonz

    nedkonz Bit Poster

    Messages:
    6
    I have lots of network-related messages being added constantly to my syslog.
    I'm running Ubuntu 20.04.02 LTS (kernel 5.8.0-45-generic).
    I've tried both bridged and shared network modes, with the same result in both.
    How can I quiet this noise?
    Code:
    Mar 24 08:42:30 ubuntu20-04 kernel: [142708.319179] device veth6c856cb entered promiscuous mode
    Mar 24 08:42:30 ubuntu20-04 kernel: [142708.319413] br-2cde75b6da24: port 3(veth6c856cb) entered blocking state
    Mar 24 08:42:30 ubuntu20-04 kernel: [142708.319414] br-2cde75b6da24: port 3(veth6c856cb) entered forwarding state
    Mar 24 08:42:30 ubuntu20-04 kernel: [142708.748873] eth0: renamed from veth0222ee2
    Mar 24 08:42:31 ubuntu20-04 kernel: [142708.773031] IPv6: ADDRCONF(NETDEV_CHANGE): veth6c856cb: link becomes ready
    Mar 24 08:42:31 ubuntu20-04 kernel: [142709.227722] br-2cde75b6da24: port 4(vethb9bee6d) entered disabled state
    Mar 24 08:42:31 ubuntu20-04 kernel: [142709.227994] veth3ad5aa2: renamed from eth0
    Mar 24 08:42:31 ubuntu20-04 kernel: [142709.266605] br-2cde75b6da24: port 4(vethb9bee6d) entered disabled state
    Mar 24 08:42:31 ubuntu20-04 kernel: [142709.270762] device vethb9bee6d left promiscuous mode
    Mar 24 08:42:31 ubuntu20-04 kernel: [142709.270766] br-2cde75b6da24: port 4(vethb9bee6d) entered disabled state
    Mar 24 08:42:31 ubuntu20-04 kernel: [142709.340256] br-2cde75b6da24: port 4(vethfcc6c9c) entered blocking state
    Mar 24 08:42:31 ubuntu20-04 kernel: [142709.340257] br-2cde75b6da24: port 4(vethfcc6c9c) entered disabled state
    Mar 24 08:42:31 ubuntu20-04 kernel: [142709.340392] device vethfcc6c9c entered promiscuous mode
    Mar 24 08:42:31 ubuntu20-04 kernel: [142709.342719] br-2cde75b6da24: port 4(vethfcc6c9c) entered blocking state
    Mar 24 08:42:31 ubuntu20-04 kernel: [142709.342720] br-2cde75b6da24: port 4(vethfcc6c9c) entered forwarding state
    Mar 24 08:42:32 ubuntu20-04 kernel: [142709.755554] eth0: renamed from vethaf5d987
    Mar 24 08:42:32 ubuntu20-04 kernel: [142709.768404] IPv6: ADDRCONF(NETDEV_CHANGE): vethfcc6c9c: link becomes ready
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.318092] br-2cde75b6da24: port 1(vethc88de49) entered disabled state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.319818] veth60e5fa0: renamed from eth0
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.372895] br-2cde75b6da24: port 1(vethc88de49) entered disabled state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.379259] device vethc88de49 left promiscuous mode
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.379262] br-2cde75b6da24: port 1(vethc88de49) entered disabled state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.497183] br-2cde75b6da24: port 1(veth7c72e5f) entered blocking state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.497184] br-2cde75b6da24: port 1(veth7c72e5f) entered disabled state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.497382] device veth7c72e5f entered promiscuous mode
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.511649] br-2cde75b6da24: port 1(veth7c72e5f) entered blocking state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.511650] br-2cde75b6da24: port 1(veth7c72e5f) entered forwarding state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.546261] br-2cde75b6da24: port 1(veth7c72e5f) entered disabled state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.546471] br-2cde75b6da24: port 2(vethee8f7a7) entered disabled state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.547332] vethfaeabaf: renamed from eth0
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.596136] br-2cde75b6da24: port 2(vethee8f7a7) entered disabled state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.622622] device vethee8f7a7 left promiscuous mode
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.622625] br-2cde75b6da24: port 2(vethee8f7a7) entered disabled state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.728842] br-2cde75b6da24: port 2(veth0fb7676) entered blocking state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.728843] br-2cde75b6da24: port 2(veth0fb7676) entered disabled state
    Mar 24 08:42:34 ubuntu20-04 kernel: [142712.729763] device veth0fb7676 entered promiscuous mode
    Mar 24 08:42:35 ubuntu20-04 kernel: [142712.752250] br-2cde75b6da24: port 2(veth0fb7676) entered blocking state
    Mar 24 08:42:35 ubuntu20-04 kernel: [142712.752251] br-2cde75b6da24: port 2(veth0fb7676) entered forwarding state
    Mar 24 08:42:35 ubuntu20-04 kernel: [142713.348163] br-2cde75b6da24: port 2(veth0fb7676) entered disabled state
    Mar 24 08:42:35 ubuntu20-04 kernel: [142713.530855] eth0: renamed from vethdf53743
    Mar 24 08:42:35 ubuntu20-04 kernel: [142713.558644] IPv6: ADDRCONF(NETDEV_CHANGE): veth0fb7676: link becomes ready
    Mar 24 08:42:35 ubuntu20-04 kernel: [142713.558729] br-2cde75b6da24: port 2(veth0fb7676) entered blocking state
    Mar 24 08:42:35 ubuntu20-04 kernel: [142713.558730] br-2cde75b6da24: port 2(veth0fb7676) entered forwarding state
    Mar 24 08:42:35 ubuntu20-04 kernel: [142713.634760] eth0: renamed from veth676f8f5
    Mar 24 08:42:35 ubuntu20-04 kernel: [142713.660510] IPv6: ADDRCONF(NETDEV_CHANGE): veth7c72e5f: link becomes ready
    Mar 24 08:42:35 ubuntu20-04 kernel: [142713.660566] br-2cde75b6da24: port 1(veth7c72e5f) entered blocking state
    Mar 24 08:42:35 ubuntu20-04 kernel: [142713.660568] br-2cde75b6da24: port 1(veth7c72e5f) entered forwarding state
    
     
  2. (GalaxyMaster)

    (GalaxyMaster) Kilo Poster

    Messages:
    90
    Well, changing the networking mode does _nothing_ to the way how the interface is exposed to the VM. Instead, go into the VM settings to the Hardware tab, click on Network, expand "Advanced Settings" and change the Type of the adapter presented to the VM. I am running "Virtio network adapter" for the last, I think, year and don't have any issues in my Linux VMs.
     

Share This Page