Wiederkehrende Verbindungsprobleme und ungewöhnliche Kernel Nachrichten

Wollte gerade wieder auf das WebInteface zugreifen - Ausfall - beruhigt sich aber seit der Änderung mit ethtool nach ca. 1 bis 2 Minuten, aber hier nun die Link Infos:
Code: 
root@pve:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether b4:96:91:91:9c:08 brd ff:ff:ff:ff:ff:ff
3: enp1s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether b4:96:91:91:9c:09 brd ff:ff:ff:ff:ff:ff
4: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether d4:5d:64:27:5c:84 brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether d4:5d:64:27:5c:84 brd ff:ff:ff:ff:ff:ff
6: veth105i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr105i0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:82:28:7f:f9:8c brd ff:ff:ff:ff:ff:ff link-netnsid 0
7: fwbr105i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 62:9a:c1:dd:d7:23 brd ff:ff:ff:ff:ff:ff
8: fwpr105p0@fwln105i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 3e:39:54:e0:a2:93 brd ff:ff:ff:ff:ff:ff
9: fwln105i0@fwpr105p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr105i0 state UP mode DEFAULT group default qlen 1000
    link/ether 62:9a:c1:dd:d7:23 brd ff:ff:ff:ff:ff:ff
10: veth109i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr109i0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:cb:e1:bf:0c:f9 brd ff:ff:ff:ff:ff:ff link-netnsid 1
11: fwbr109i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 12:2c:87:63:93:ca brd ff:ff:ff:ff:ff:ff
12: fwpr109p0@fwln109i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 3e:6b:bf:36:b7:ad brd ff:ff:ff:ff:ff:ff
13: fwln109i0@fwpr109p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr109i0 state UP mode DEFAULT group default qlen 1000
    link/ether 12:2c:87:63:93:ca brd ff:ff:ff:ff:ff:ff
14: veth104i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:b9:fd:17:3c:55 brd ff:ff:ff:ff:ff:ff link-netnsid 2
15: fwbr104i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 76:8b:f8:5e:0c:37 brd ff:ff:ff:ff:ff:ff
16: fwpr104p0@fwln104i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 7a:e2:9f:9c:e4:4a brd ff:ff:ff:ff:ff:ff
17: fwln104i0@fwpr104p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i0 state UP mode DEFAULT group default qlen 1000
    link/ether 76:8b:f8:5e:0c:37 brd ff:ff:ff:ff:ff:ff
18: veth100i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:c8:cb:50:06:fa brd ff:ff:ff:ff:ff:ff link-netnsid 3
19: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 76:c1:14:12:0a:4b brd ff:ff:ff:ff:ff:ff
20: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 3e:f7:50:62:f3:0d brd ff:ff:ff:ff:ff:ff
21: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP mode DEFAULT group default qlen 1000
    link/ether 76:c1:14:12:0a:4b brd ff:ff:ff:ff:ff:ff
22: veth107i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr107i0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:d3:c3:8d:80:fe brd ff:ff:ff:ff:ff:ff link-netnsid 4
23: fwbr107i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 1a:aa:d4:95:eb:2f brd ff:ff:ff:ff:ff:ff
24: fwpr107p0@fwln107i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 9a:eb:29:f5:e9:06 brd ff:ff:ff:ff:ff:ff
25: fwln107i0@fwpr107p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr107i0 state UP mode DEFAULT group default qlen 1000
    link/ether 1a:aa:d4:95:eb:2f brd ff:ff:ff:ff:ff:ff
26: veth101i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:a3:47:34:c1:5a brd ff:ff:ff:ff:ff:ff link-netnsid 5
27: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 4a:ba:60:ab:39:6b brd ff:ff:ff:ff:ff:ff
28: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether f2:bf:e2:55:05:b7 brd ff:ff:ff:ff:ff:ff
29: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP mode DEFAULT group default qlen 1000
    link/ether 4a:ba:60:ab:39:6b brd ff:ff:ff:ff:ff:ff
30: veth102i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:99:52:4e:55:32 brd ff:ff:ff:ff:ff:ff link-netnsid 6
31: fwbr102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether ce:6c:8f:2e:db:4f brd ff:ff:ff:ff:ff:ff
32: fwpr102p0@fwln102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 62:db:ec:a5:b7:90 brd ff:ff:ff:ff:ff:ff
33: fwln102i0@fwpr102p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i0 state UP mode DEFAULT group default qlen 1000
    link/ether ce:6c:8f:2e:db:4f brd ff:ff:ff:ff:ff:ff
34: veth108i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr108i0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:ab:32:dc:42:c1 brd ff:ff:ff:ff:ff:ff link-netnsid 7
35: fwbr108i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 96:b1:6a:80:e0:c0 brd ff:ff:ff:ff:ff:ff
36: fwpr108p0@fwln108i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 7e:da:e1:13:19:bc brd ff:ff:ff:ff:ff:ff
37: fwln108i0@fwpr108p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr108i0 state UP mode DEFAULT group default qlen 1000
    link/ether 96:b1:6a:80:e0:c0 brd ff:ff:ff:ff:ff:ff
38: tap110i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr110i0 state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 32:88:8e:f0:5c:6d brd ff:ff:ff:ff:ff:ff
39: fwbr110i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether f2:7a:96:7c:ef:43 brd ff:ff:ff:ff:ff:ff
40: fwpr110p0@fwln110i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 66:68:74:e5:52:42 brd ff:ff:ff:ff:ff:ff
41: fwln110i0@fwpr110p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr110i0 state UP mode DEFAULT group default qlen 1000
    link/ether f2:7a:96:7c:ef:43 brd ff:ff:ff:ff:ff:ff
42: veth111i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr111i0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:0f:49:cb:11:e6 brd ff:ff:ff:ff:ff:ff link-netnsid 8
43: fwbr111i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether d2:5c:c6:de:3c:09 brd ff:ff:ff:ff:ff:ff
44: fwpr111p0@fwln111i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 46:cb:47:73:26:18 brd ff:ff:ff:ff:ff:ff
45: fwln111i0@fwpr111p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr111i0 state UP mode DEFAULT group default qlen 1000
    link/ether d2:5c:c6:de:3c:09 brd ff:ff:ff:ff:ff:ff
 
stkw said:
Dec 06 10:00:24 pve kernel: br-ecacd9f68f57: port 2(vethc123a7c) entered blocking state
Click to expand...

stkw said:
Dec 06 10:00:24 pve kernel: br-ecacd9f68f57: port 2(vethc123a7c) entered disabled state
Click to expand...

stkw said:
Dec 06 10:00:24 pve kernel: device vethc123a7c entered promiscuous mode
Click to expand...
Beantwortet leider nicht die frage woher die oben zitierten interfaces (br-ecacd9f68f57 und vethc123a7c) kommen?
 
Mit den genannten Änderungen durchs ethtool haben sich die Netzwerkeigenschaften geändert. Nachdem ich den Befehl abgesetzt hatte war auch plötzlich im Check_MK einiges los weil die erkannten Netzwerkeinstellungen nicht zusammenpassten. Wenn wir das genauer untersuchen möchten müsste ich die Einstellungen rückgängig machen und dann warten bis die Probleme wieder auftreten.

Wo kann ich denn noch nachsehen wenn gerade das Webinterface nicht erreichbar ist - das Syslog gibt aktuell wenig Auskunft über Probleme - Jetzt gerade war das Webinterface wieder weg und für 10 Minuten nicht erreichbar.
Wenn ich mich in der Zeit per KVM auf die Maschine verbinde und prüfe ob alle Dienst laufen wird mir alles als OK angezeigt. Auch ein Neustart des PVEProxy hilft an der Stelle nicht. Mit der Zeit (in dem Fall nach 10 Minuten) geht es dann von selbst wieder.
Das Problem habe ich erst seit den letzten drei Kernel Updates.
 
Ich habe die Ursache für meine WebInterface Probleme gefunden - meine Firewallregeln für den Host waren zu scharf eingestellt.
Spannend trotzdem dass es zwischenzeitlich trotzdem funktioniert hat.

Auf jeden Fall habe ich nun auch, nach Rückbau meiner Netzwerkconfig auch wieder die Meldungen im Syslog gefunden, allerdings tauchen diese nur nach einem Reboot auf:
Code: 
Dec 22 21:19:08 pve kernel: br-ecacd9f68f57: port 1(veth5c63ba1) entered blocking state
Dec 22 21:19:08 pve kernel: br-ecacd9f68f57: port 1(veth5c63ba1) entered disabled state
Dec 22 21:19:08 pve kernel: device veth5c63ba1 entered promiscuous mode
Dec 22 21:19:08 pve kernel: br-ecacd9f68f57: port 1(veth5c63ba1) entered blocking state
Dec 22 21:19:08 pve kernel: br-ecacd9f68f57: port 1(veth5c63ba1) entered forwarding state
Dec 22 21:19:08 pve kernel: br-ecacd9f68f57: port 1(veth5c63ba1) entered disabled state
Dec 22 21:19:08 pve kernel: br-46044e73f2c7: port 1(veth6aec0d0) entered blocking state
Dec 22 21:19:08 pve kernel: br-46044e73f2c7: port 1(veth6aec0d0) entered disabled state
Dec 22 21:19:08 pve kernel: device veth6aec0d0 entered promiscuous mode
Dec 22 21:19:08 pve kernel: br-46044e73f2c7: port 1(veth6aec0d0) entered blocking state
Dec 22 21:19:08 pve kernel: br-46044e73f2c7: port 1(veth6aec0d0) entered forwarding state
Dec 22 21:19:08 pve kernel: br-46044e73f2c7: port 1(veth6aec0d0) entered disabled state
Dec 22 21:19:09 pve kernel: eth0: renamed from vethff136ab
Dec 22 21:19:09 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5c63ba1: link becomes ready
Dec 22 21:19:09 pve kernel: br-ecacd9f68f57: port 1(veth5c63ba1) entered blocking state
Dec 22 21:19:09 pve kernel: br-ecacd9f68f57: port 1(veth5c63ba1) entered forwarding state
Dec 22 21:19:09 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-ecacd9f68f57: link becomes ready
Dec 22 21:19:09 pve kernel: br-ecacd9f68f57: port 2(vethb1cd92f) entered blocking state
Dec 22 21:19:09 pve kernel: br-ecacd9f68f57: port 2(vethb1cd92f) entered disabled state
Dec 22 21:19:09 pve kernel: device vethb1cd92f entered promiscuous mode
Dec 22 21:19:09 pve kernel: br-ecacd9f68f57: port 3(veth75c35c0) entered blocking state
Dec 22 21:19:09 pve kernel: br-ecacd9f68f57: port 3(veth75c35c0) entered disabled state
Dec 22 21:19:09 pve kernel: device veth75c35c0 entered promiscuous mode
Dec 22 21:19:09 pve kernel: br-ecacd9f68f57: port 3(veth75c35c0) entered blocking state
Dec 22 21:19:09 pve kernel: br-ecacd9f68f57: port 3(veth75c35c0) entered forwarding state
Dec 22 21:19:10 pve kernel: eth0: renamed from veth6e16976
Dec 22 21:19:10 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth75c35c0: link becomes ready
Dec 22 21:19:10 pve systemd[1]: systemd-fsckd.service: Succeeded.
Dec 22 21:19:10 pve kernel: br-ecacd9f68f57: port 4(veth83f5cdf) entered blocking state
Dec 22 21:19:10 pve kernel: br-ecacd9f68f57: port 4(veth83f5cdf) entered disabled state
Dec 22 21:19:10 pve kernel: device veth83f5cdf entered promiscuous mode
Dec 22 21:19:10 pve kernel: br-ecacd9f68f57: port 4(veth83f5cdf) entered blocking state
Dec 22 21:19:10 pve kernel: br-ecacd9f68f57: port 4(veth83f5cdf) entered forwarding state
Dec 22 21:19:10 pve kernel: eth0: renamed from vethd6d5cd6
Dec 22 21:19:10 pve kernel: br-ecacd9f68f57: port 4(veth83f5cdf) entered disabled state
Dec 22 21:19:10 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb1cd92f: link becomes ready
Dec 22 21:19:10 pve kernel: br-ecacd9f68f57: port 2(vethb1cd92f) entered blocking state
Dec 22 21:19:10 pve kernel: br-ecacd9f68f57: port 2(vethb1cd92f) entered forwarding state
Dec 22 21:19:11 pve kernel: eth0: renamed from veth9b905ea
Dec 22 21:19:11 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth83f5cdf: link becomes ready
Dec 22 21:19:11 pve kernel: br-ecacd9f68f57: port 4(veth83f5cdf) entered blocking state
Dec 22 21:19:11 pve kernel: br-ecacd9f68f57: port 4(veth83f5cdf) entered forwarding state
Dec 22 21:19:11 pve kernel: eth0: renamed from vethbe5979f
Dec 22 21:19:11 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6aec0d0: link becomes ready
Dec 22 21:19:11 pve kernel: br-46044e73f2c7: port 1(veth6aec0d0) entered blocking state
Dec 22 21:19:11 pve kernel: br-46044e73f2c7: port 1(veth6aec0d0) entered forwarding state
Dec 22 21:19:11 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-46044e73f2c7: link becomes ready
Dec 22 21:19:11 pve kernel: sctp: Hash tables configured (bind 2048/2048)
Dec 22 21:19:11 pve kernel: br-ecacd9f68f57: port 5(veth225b931) entered blocking state
Dec 22 21:19:11 pve kernel: br-ecacd9f68f57: port 5(veth225b931) entered disabled state
Dec 22 21:19:11 pve kernel: device veth225b931 entered promiscuous mode
Dec 22 21:19:12 pve kernel: eth0: renamed from vethbc66f02
Dec 22 21:19:12 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth225b931: link becomes ready
Dec 22 21:19:12 pve kernel: br-ecacd9f68f57: port 5(veth225b931) entered blocking state
Dec 22 21:19:12 pve kernel: br-ecacd9f68f57: port 5(veth225b931) entered forwarding state
Dec 22 21:19:12 pve kernel: br-ecacd9f68f57: port 6(veth8f68dc2) entered blocking state
Dec 22 21:19:12 pve kernel: br-ecacd9f68f57: port 6(veth8f68dc2) entered disabled state
Dec 22 21:19:12 pve kernel: device veth8f68dc2 entered promiscuous mode
Dec 22 21:19:12 pve kernel: br-ecacd9f68f57: port 6(veth8f68dc2) entered blocking state
Dec 22 21:19:12 pve kernel: br-ecacd9f68f57: port 6(veth8f68dc2) entered forwarding state
Dec 22 21:19:12 pve systemd-timesyncd[1832]: Synchronized to time server for the first time 137.190.2.4:123 (2.debian.pool.ntp.org).
Dec 22 21:19:12 pve kernel: br-ecacd9f68f57: port 6(veth8f68dc2) entered disabled state
Dec 22 21:19:13 pve kernel: eth0: renamed from veth8a21e7c
Dec 22 21:19:13 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8f68dc2: link becomes ready
Dec 22 21:19:13 pve kernel: br-ecacd9f68f57: port 6(veth8f68dc2) entered blocking state
Dec 22 21:19:13 pve kernel: br-ecacd9f68f57: port 6(veth8f68dc2) entered forwarding state
Dec 22 21:19:13 pve kernel: br-ecacd9f68f57: port 7(vethf59eace) entered blocking state
Dec 22 21:19:13 pve kernel: br-ecacd9f68f57: port 7(vethf59eace) entered disabled state
Dec 22 21:19:13 pve kernel: device vethf59eace entered promiscuous mode
Dec 22 21:19:13 pve kernel: br-ecacd9f68f57: port 7(vethf59eace) entered blocking state
Dec 22 21:19:13 pve kernel: br-ecacd9f68f57: port 7(vethf59eace) entered forwarding state
Dec 22 21:19:13 pve kernel: br-ecacd9f68f57: port 7(vethf59eace) entered disabled state
Dec 22 21:19:14 pve kernel: eth0: renamed from veth451b4b6
Dec 22 21:19:14 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf59eace: link becomes ready
Dec 22 21:19:14 pve kernel: br-ecacd9f68f57: port 7(vethf59eace) entered blocking state
Dec 22 21:19:14 pve kernel: br-ecacd9f68f57: port 7(vethf59eace) entered forwarding state
Dec 22 21:19:15 pve kernel: br-ecacd9f68f57: port 8(veth61d0d07) entered blocking state
Dec 22 21:19:15 pve kernel: br-ecacd9f68f57: port 8(veth61d0d07) entered disabled state
Dec 22 21:19:15 pve kernel: device veth61d0d07 entered promiscuous mode
Dec 22 21:19:16 pve kernel: eth0: renamed from veth30eb78b
Dec 22 21:19:16 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth61d0d07: link becomes ready
Dec 22 21:19:16 pve kernel: br-ecacd9f68f57: port 8(veth61d0d07) entered blocking state
Dec 22 21:19:16 pve kernel: br-ecacd9f68f57: port 8(veth61d0d07) entered forwarding state
Dec 22 21:19:16 pve kernel: br-ecacd9f68f57: port 9(veth5bb73f6) entered blocking state
Dec 22 21:19:16 pve kernel: br-ecacd9f68f57: port 9(veth5bb73f6) entered disabled state
Dec 22 21:19:16 pve kernel: device veth5bb73f6 entered promiscuous mode
Dec 22 21:19:16 pve kernel: br-ecacd9f68f57: port 10(vethd7cab4e) entered blocking state
Dec 22 21:19:16 pve kernel: br-ecacd9f68f57: port 10(vethd7cab4e) entered disabled state
Dec 22 21:19:16 pve kernel: device vethd7cab4e entered promiscuous mode
Dec 22 21:19:16 pve kernel: br-ecacd9f68f57: port 10(vethd7cab4e) entered blocking state
Dec 22 21:19:16 pve kernel: br-ecacd9f68f57: port 10(vethd7cab4e) entered forwarding state
Dec 22 21:19:17 pve kernel: eth0: renamed from vethb3631d4
Dec 22 21:19:17 pve kernel: br-ecacd9f68f57: port 10(vethd7cab4e) entered disabled state
Dec 22 21:19:17 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5bb73f6: link becomes ready
Dec 22 21:19:17 pve kernel: br-ecacd9f68f57: port 9(veth5bb73f6) entered blocking state
Dec 22 21:19:17 pve kernel: br-ecacd9f68f57: port 9(veth5bb73f6) entered forwarding state
Dec 22 21:19:17 pve kernel: eth0: renamed from veth483aea3
Dec 22 21:19:17 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd7cab4e: link becomes ready
Dec 22 21:19:17 pve kernel: br-ecacd9f68f57: port 10(vethd7cab4e) entered blocking state
Dec 22 21:19:17 pve kernel: br-ecacd9f68f57: port 10(vethd7cab4e) entered forwarding state
Dec 22 21:19:21 pve pvedaemon[2363]: <root@pam> successful auth for user 'root@pam'
Dec 22 21:19:21 pve kernel: br-ecacd9f68f57: port 11(veth764ef0a) entered blocking state
Dec 22 21:19:21 pve kernel: br-ecacd9f68f57: port 11(veth764ef0a) entered disabled state
Dec 22 21:19:21 pve kernel: device veth764ef0a entered promiscuous mode
Dec 22 21:19:22 pve kernel: eth0: renamed from veth32dc258
Dec 22 21:19:22 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth764ef0a: link becomes ready
Dec 22 21:19:22 pve kernel: br-ecacd9f68f57: port 11(veth764ef0a) entered blocking state
Dec 22 21:19:22 pve kernel: br-ecacd9f68f57: port 11(veth764ef0a) entered forwarding state
Dec 22 21:19:24 pve kernel: br-ecacd9f68f57: port 11(veth764ef0a) entered disabled state
Dec 22 21:19:24 pve kernel: veth32dc258: renamed from eth0
Dec 22 21:19:24 pve kernel: br-ecacd9f68f57: port 11(veth764ef0a) entered disabled state
Dec 22 21:19:24 pve kernel: device veth764ef0a left promiscuous mode
Dec 22 21:19:24 pve kernel: br-ecacd9f68f57: port 11(veth764ef0a) entered disabled state
Dec 22 21:19:24 pve kernel: br-ecacd9f68f57: port 11(vethd4294ae) entered blocking state
Dec 22 21:19:24 pve kernel: br-ecacd9f68f57: port 11(vethd4294ae) entered disabled state
Dec 22 21:19:24 pve kernel: device vethd4294ae entered promiscuous mode
Dec 22 21:19:24 pve kernel: br-ecacd9f68f57: port 11(vethd4294ae) entered blocking state
Dec 22 21:19:24 pve kernel: br-ecacd9f68f57: port 11(vethd4294ae) entered forwarding state
Dec 22 21:19:25 pve kernel: br-ecacd9f68f57: port 11(vethd4294ae) entered disabled state
Dec 22 21:19:25 pve kernel: br-ecacd9f68f57: port 12(veth064b6ac) entered blocking state
Dec 22 21:19:25 pve kernel: br-ecacd9f68f57: port 12(veth064b6ac) entered disabled state
Dec 22 21:19:25 pve kernel: device veth064b6ac entered promiscuous mode
Dec 22 21:19:25 pve kernel: br-ecacd9f68f57: port 12(veth064b6ac) entered blocking state
Dec 22 21:19:25 pve kernel: br-ecacd9f68f57: port 12(veth064b6ac) entered forwarding state
Dec 22 21:19:25 pve kernel: eth0: renamed from vethd55ec92
Dec 22 21:19:25 pve kernel: br-ecacd9f68f57: port 12(veth064b6ac) entered disabled state
Dec 22 21:19:25 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd4294ae: link becomes ready
Dec 22 21:19:25 pve kernel: br-ecacd9f68f57: port 11(vethd4294ae) entered blocking state
Dec 22 21:19:25 pve kernel: br-ecacd9f68f57: port 11(vethd4294ae) entered forwarding state
Dec 22 21:19:25 pve kernel: eth0: renamed from vethdbc4fd8
Dec 22 21:19:25 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth064b6ac: link becomes ready
Dec 22 21:19:25 pve kernel: br-ecacd9f68f57: port 12(veth064b6ac) entered blocking state
Dec 22 21:19:25 pve kernel: br-ecacd9f68f57: port 12(veth064b6ac) entered forwarding state
Dec 22 21:19:33 pve kernel: br-ecacd9f68f57: port 13(veth0cc3f0f) entered blocking state
Dec 22 21:19:33 pve kernel: br-ecacd9f68f57: port 13(veth0cc3f0f) entered disabled state
Dec 22 21:19:33 pve kernel: device veth0cc3f0f entered promiscuous mode
Dec 22 21:19:33 pve kernel: eth0: renamed from vethd3cb8c3
Dec 22 21:19:33 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0cc3f0f: link becomes ready
Dec 22 21:19:33 pve kernel: br-ecacd9f68f57: port 13(veth0cc3f0f) entered blocking state
Dec 22 21:19:33 pve kernel: br-ecacd9f68f57: port 13(veth0cc3f0f) entered forwarding state
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back