Recent content by jemico

I had the same problem on Proxmox 5.4 (firewall running, 4 levels activates, communication between containers on a internal bridge, added IN DROP on top of container rules, but still accessible). pve-firewall compile didn't help pve-firewall restart solved the problem and finally apply the...

Hi all, After solving the hardware crash (motherboard changed), I always had the same network behavior. Finally, I found a solution : Explanation : The server is OVH and their Proxmox 5 ZFS image start both networking.service and systemd-networkd.service. The default OVH configuration is...

Hello, Since last time, we started server with another OS (rescue mode) and ..... had the very same kind of crash ! It seems to be a hardware problem and not a proxmox config one. Regards, Jean-Michel

Hello Wolfgang, root@bks:~# journalctl -u networking.service -- Logs begin at Wed 2020-04-22 22:34:13 CEST, end at Thu 2020-04-23 06:46:00 CEST. -- avril 22 22:34:19 bks systemd[1]: Starting Raise network interfaces... avril 22 22:34:20 bks ifup[2064]: Waiting for vmbr0 to get ready (MAXWAIT is...

Hello, Today I had no more network on the serveur, and the provider did an down/up on the NIC, with success. I wished that it solved my problem .... but no : networking.service always failed with same error. Here is the result of journalctl -p err : avril 22 20:54:27 bks kernel: Couldn't get...

Hello, Sorry for the delay : I didn't find anything for now. Multiple reboots happens on this machine without any log, and now I've got no more network with the same config => as is, I've open an incident to the provider (OVH) because at first sight, I've got the impression of a hardware...

Hi, Networking seems all fine (ping google, ssh connect) but host totally disconnect from time to time (quite every 2 days ... :( )and we have to reboot it, and networking.service fail to start .... I'm running 4.15.18-27-pve with this kind of network config : root@bks:~# ip link 1: lo...