En local : ⚙️ Using Default Settings on node balkany 🆔 Container ID: 112 🖥️ Operating System: debian (13) 📦 Container Type: Unprivileged 💾 Disk Size: 2 GB 🧠 CPU Cores: 1 🛠️ RAM Size: 512 MiB 🚀 Creating a MQTT LXC using the above default settings ✔️ Storage local (Free: 51.5GB Used: 35.7GB) [Template] ✔️ Storage datastore2 (Free: 801.6GB Used: 3.0TB) [Container] ✔️ Template debian-13-standard_13.1-2_amd64.tar.zst [online] 💡 Template debian-13-standard_13.1-2_amd64.tar.zst is missing or corrupted. Re-downloading. ✔️ Template download successful. ✔️ LXC Container 112 was successfully created. ✔️ Started LXC Container ✔️ Network in LXC is reachable (ping) ⠴ Customizing LXC Containerbash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory ⠸ Customizing LXC Containerbash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.1.56 ✔️ IPv4 Internet Connected ✔️ IPv6 Internet Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) ✔️ Updated Container OS ✔️ Installed Mosquitto MQTT Broker ✔️ Customized Container ✔️ Cleaned ✔️ Completed Successfully! 🚀 MQTT setup has been successfully initialized! 💡 Access it using the following IP: 🌐 192.168.1.56:1883

Toujours pas de crash … # wc -l /etc/pve/firewall/cluster.fw 10288 /etc/pve/firewall/cluster.fw # grep "# CCBot" /etc/pve/firewall/cluster.fw > iptables-CCbot.txt # wc -l iptables-CCbot.txt 8994 iptables-CCbot.txt Le gros est la pollution de CCBot ( Brésil, Argentine, Vietnam, … )

Huawei devant ccbot : # cat /var/log/pve-firewall.log | awk '{print $3}' | sort -n | uniq -c 867 GROUP-attack-IN 721 GROUP-attackmail-IN 3452 GROUP-ccbot-IN 12 GROUP-honeypot-IN 6027 GROUP-huawei-IN 47 GROUP-russian-IN

J’ai 120 IP … # zgrep "/.well-known/acme-challenge/" /var/log/apache2/acces*gz | grep " 200 " | grep "www.letsencrypt.org" | sed 's/:/ /g' | awk '{print $2}' | sort | uniq -c | wc -l 120

Je viens de finir le gros ménage … # wc -l /etc/pve/firewall/*.fw 12 /etc/pve/firewall/104.fw 9 /etc/pve/firewall/116.fw 42 /etc/pve/firewall/124.fw 20 /etc/pve/firewall/126.fw 9 /etc/pve/firewall/127.fw 13 /etc/pve/firewall/129.fw 5850 /etc/pve/firewall/cluster.fw

Nouveau affichage : [image: 1759479392120-e62c0f9a-0b45-4393-9744-b3f0058abfd5-image.png]

Bref pas de problème, et fait en moins de 1h. Par contre j’ai pas fait de reboot.

J’ai supprimé les commandes hostpci : # grep "hostpci" /etc/pve/qemu-server/*.conf /etc/pve/qemu-server/100.conf:#hostpci0: 0000:01:00.0,rombar=0 /etc/pve/qemu-server/100.conf:#hostpci1: 0000:01:00.1,rombar=0 Et maintenant j’ai plus de suppression du drivers : # networkctl | grep "enp" systemd-networkd is not running, output might be incomplete. 2 enp1s0f0 ether - unmanaged 3 enp0s31f6 ether - unmanaged 4 enp1s0f1 ether - unmanaged # dmesg | grep "igb" [ 1.695998] igb: Intel(R) Gigabit Ethernet Network Driver [ 1.695999] igb: Copyright (c) 2007-2014 Intel Corporation. [ 1.696010] igb 0000:01:00.0: enabling device (0000 -> 0002) [ 1.878837] igb 0000:01:00.0: added PHC on eth0 [ 1.878861] igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection [ 1.878862] igb 0000:01:00.0: eth0: (PCIe:2.5Gb/s:Width x4) 90:e2:ba:08:85:50 [ 1.879161] igb 0000:01:00.0: eth0: PBA No: G18758-003 [ 1.879162] igb 0000:01:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [ 1.879174] igb 0000:01:00.1: enabling device (0000 -> 0002) [ 2.061778] igb 0000:01:00.1: added PHC on eth2 [ 2.061797] igb 0000:01:00.1: Intel(R) Gigabit Ethernet Network Connection [ 2.061798] igb 0000:01:00.1: eth2: (PCIe:2.5Gb/s:Width x4) 90:e2:ba:08:85:51 [ 2.062101] igb 0000:01:00.1: eth2: PBA No: G18758-003 [ 2.062102] igb 0000:01:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [ 2.292065] igb 0000:01:00.1 enp1s0f1: renamed from eth2 [ 2.292529] igb 0000:01:00.0 enp1s0f0: renamed from eth0 [ 7.030374] igb 0000:01:00.0 enp1s0f0: entered allmulticast mode [ 7.030413] igb 0000:01:00.0 enp1s0f0: entered promiscuous mode [ 9.314164] igb 0000:01:00.0 enp1s0f0: igb: enp1s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 121.086711] igb 0000:01:00.0 enp1s0f0: igb: enp1s0f0 NIC Link is Down [ 155.491157] igb 0000:01:00.0 enp1s0f0: igb: enp1s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

la liste des boot : # journalctl --list-boots IDX BOOT ID FIRST ENTRY LAST ENTRY -5 88ae0c94ba2d43e5b8d9a267b98294bd Tue 2025-09-02 11:47:22 CEST Tue 2025-09-02 17:15:16 CEST -4 2a36753b78e84e0e95da8535eba3ce82 Tue 2025-09-02 17:17:49 CEST Tue 2025-09-02 17:53:09 CEST -3 54824c1389ea444cbfcca0bad6673089 Tue 2025-09-02 17:56:44 CEST Wed 2025-09-03 10:39:07 CEST -2 02ad30ec878c4d0a9227f289e1670640 Wed 2025-09-03 10:46:39 CEST Wed 2025-09-03 11:17:01 CEST -1 f6b43c6cabce4fd1bd5512764e53fbc6 Wed 2025-09-03 11:43:05 CEST Wed 2025-09-03 15:45:24 CEST 0 027e7dacbfba4f5fb3e3c55a3f766a09 Wed 2025-09-03 15:46:30 CEST Thu 2025-09-04 10:46:39 CEST

La suite dans https://lemmy.cyber-neurones.org/topic/47/proxmox-e1000e-detected-hardware-unit-hang