In short: The upgrade to kernel 4 could resolve for Realtek ethenet devices to be renamed and getting one or more connections of your Proxmox disconnected. I solved this by removing the mac addresses in the persistant-net rules and replacing them by KERNELS=="" where the value is the PCI address like you will find in the dmesg output and on the next reboot the adapters where back like they were after my initial install.
The long version:
I was having serious bandwidth issues between my workstation and my Proxmox server at home. After a while I found out all the other machines where connecting fine with and through the Proxmox (as it also runs the Sophos firewall). As they where using the quad Intel E1000 adapter I have. I got around 10mbit and a lot of stalling connections. After some looking around I found out on the Proxmox that one interface was missing from the bond (2 * 1Gbit onboard Realtek adapters) between my workstation and the server.
The solution:
https://wiki.debian.org/Bonding <- part on udev
The long version:
I was having serious bandwidth issues between my workstation and my Proxmox server at home. After a while I found out all the other machines where connecting fine with and through the Proxmox (as it also runs the Sophos firewall). As they where using the quad Intel E1000 adapter I have. I got around 10mbit and a lot of stalling connections. After some looking around I found out on the Proxmox that one interface was missing from the bond (2 * 1Gbit onboard Realtek adapters) between my workstation and the server.
The solution:
https://wiki.debian.org/Bonding <- part on udev
Last edited: