Network will not reconnect

Tue-A · Apr 9, 2022

I'm using my laptop as a proxmox server, it works like a charm, I just have one problem. When network cable is disconnected and reconnected I cannot get acces to the server again, it seams like the network do not reconnect? If I do a reboot it comes up running fine again, any good ideas?

BR

Tue

PS. complety newbee to proxmox

when I remove the powercord and til laptop runs on battery, I get attached error message, do that help anybody?

Dunuin · Apr 9, 2022

First you should show us your network config: cat /etc/network/interfaces
And what network chipsets does that laptop got?

PS: There is no attached error message.

Tue-A · Apr 9, 2022

Dunuin said:
First you should show us your network config: cat /etc/network/interfaces
And what network chipsets does that laptop got?

It is a USB-C netcard, not sure what chip i inside, The only thing I can find on it is it works under: Windows XP/Vista/7/8/10, Mac 10.6-10.8/ Linux 2.6. and that do not tell much I know.... And now picture attached above and here it is of the network card

Code:

# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface enxd481d72d367a inet manual

iface wlp60s0 inet manual

iface enx000202044d76 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.86.2/24
        gateway 192.168.86.1
        bridge-ports enx000202044d76
        bridge-stp off
        bridge-fd 0

Dunuin · Apr 9, 2022

You could unplug and plug that ethernet cable and then look at the syslog ("/var/log/syslog" and "/var/log/syslog.1) if you see suspicious error messages at that time.

Tue-A · Apr 9, 2022

Dunuin said:
You could unplug and plug that ethernet cable and then look at the syslog ("/var/log/syslog" and "/var/log/syslog.1) if you see suspicious error messages at that time.

stupid question, how do I acces those files from shell? what is the command? I cannot get on the web interface since that is the problem

Tue-A · Apr 9, 2022

This happens when PSU is removed:


Apr 09 22:17:29 proxmox kernel: ACPI Error: Thread 1319141376 cannot release Mutex [PATM] acquired by thread 1115009408 (20210331/exmutex-378)
Apr 09 22:17:29 proxmox kernel: 
Apr 09 22:17:29 proxmox kernel: No Local Variables are initialized for Method [_Q66]
Apr 09 22:17:29 proxmox kernel: 
Apr 09 22:17:29 proxmox kernel: No Arguments are initialized for method [_Q66]
Apr 09 22:17:29 proxmox kernel: 
Apr 09 22:17:29 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20210331/psparse-529)
Apr 09 22:17:33 proxmox kernel: ACPI Error: Thread 1132284480 cannot release Mutex [PATM] acquired by thread 1115009408 (20210331/exmutex-378)
Apr 09 22:17:33 proxmox kernel: 
Apr 09 22:17:33 proxmox kernel: No Local Variables are initialized for Method [_Q66]
Apr 09 22:17:33 proxmox kernel: 
Apr 09 22:17:33 proxmox kernel: No Arguments are initialized for method [_Q66]
Apr 09 22:17:33 proxmox kernel: 
Apr 09 22:17:33 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20210331/psparse-529)

And then power is reconnected:

Apr 09 22:17:35 proxmox kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
Apr 09 22:17:35 proxmox kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Apr 09 22:17:35 proxmox kernel: pcieport 0000:00:1c.0: device [8086:9d10] error status/mask=00000001/00002000
Apr 09 22:17:35 proxmox kernel: pcieport 0000:00:1c.0: [ 0] RxErr
Apr 09 22:17:35 proxmox kernel: ACPI Error: Cannot release Mutex [PATM], not acquired (20210331/exmutex-357)
Apr 09 22:17:35 proxmox kernel:
Apr 09 22:17:35 proxmox kernel: No Local Variables are initialized for Method [_Q66]
Apr 09 22:17:35 proxmox kernel:
Apr 09 22:17:35 proxmox kernel: No Arguments are initialized for method [_Q66]
Apr 09 22:17:35 proxmox kernel:
Apr 09 22:17:35 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_MUTEX_NOT_ACQUIRED) (20210331/psparse-529)

Tue-A · Apr 9, 2022

When network disconnected:
Apr 09 22:20:07 proxmox kernel: vmbr0: port 1(enx000202044d76) entered disabled state

Reconnected:
There is nothing new in log at all

Tue-A · Jun 21, 2022

Nobody able to give me a clue here?

I get this in log when disconnect network cable:

Jun 21 09:31:01 proxmox kernel: vmbr0: port 1(enx000202044d76) entered disabled state

When I plug in the cable again, there are NO messages in log?

gfgjs · Feb 1, 2024

I have identified the issue ，try turn off the 'network wake-up' option in the motherboard BIOS settings.

xelar · Mar 5, 2024

I have the same exact issue on 3 Proxmox nodes and it is driving me up the wall. @gfgjs what is `network wake-up`? Are you referring to WOL settings?

novice4ever · Jun 17, 2024

xelar said:
I have the same exact issue on 3 Proxmox nodes and it is driving me up the wall. @gfgjs what is `network wake-up`? Are you referring to WOL settings?

I would think so, has this sorted your issue ?

McFly83 · Jun 24, 2024

Hi, i have the same Problem. WOL is deactivated. after rebooting my Router or unplugging the LAN Cable, i cant access the Host. Are there further Information or Workarounds regarding this Problem?

eejay · Jun 28, 2024

Has anyone resolved this issue? I'm also having this problem right now.
I made a sophos installation, after unplugging the cable, the gateway cannot be reached anymore unless I restart the proxmox server.

Code:

auto lo
iface lo inet loopback

iface eno2 inet manual

iface eno1 inet manual

iface enp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.50.2/24
        gateway 192.168.50.1
        bridge-ports eno2
        bridge-stp off
        bridge-fd 0
#Management NIC

auto vmbr1
iface vmbr1 inet manual
        bridge-ports enp3s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094
#LAN

auto vmbr2
iface vmbr2 inet manual
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
#WAN

McFly83 · Jun 28, 2024

eejay said:

Has anyone resolved this issue? I'm also having this problem right now.
I made a sophos installation, after unplugging the cable, the gateway cannot be reached anymore unless I restart the proxmox server.

Code:

auto lo
iface lo inet loopback

iface eno2 inet manual

iface eno1 inet manual

iface enp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.50.2/24
        gateway 192.168.50.1
        bridge-ports eno2
        bridge-stp off
        bridge-fd 0
#Management NIC

auto vmbr1
iface vmbr1 inet manual
        bridge-ports enp3s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094
#LAN

auto vmbr2
iface vmbr2 inet manual
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
#WAN

I have just updated to the latest kernel. The first entry in the changelog describes a fix regarding „stability issue reconnecting with e1000e after replug“.

I cant test this right now, but i think thats it…

McFly83 · Jun 28, 2024

McFly83 said:
I have just updated to the latest kernel. The first entry in the changelog describes a fix regarding „stability issue reconnecting with e1000e after replug“.

I cant test this right now, but i think thats it…

Just unpluged/replug my Node and also rebooted my Router - everything is working fine now!

un 28 09:34:08 proxmox kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Down
Jun 28 09:34:08 proxmox kernel: vmbr0: port 1(eno1) entered disabled state

Jun 28 09:34:30 proxmox kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Jun 28 09:34:30 proxmox kernel: vmbr0: port 1(eno1) entered blocking state
Jun 28 09:34:30 proxmox kernel: vmbr0: port 1(eno1) entered forwarding state

Rework1415 · Jul 3, 2024

I had a similar issue with a USB-Ethernet adapter that I was using with a desktop computer.

Initially, my /etc/network/interfaces contained the following:

Code:

auto enx000ec6ec4728
iface enx000ec6ec4728 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.23/24
        gateway 192.168.1.1
        bridge-ports enx000ec6ec4728
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

After being shown this article about auto vs allow-hotplug, I changed the interfaces file to this:

Code:

allow-hotplug enx000ec6ec4728
iface enx000ec6ec4728 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.23/24
        gateway 192.168.1.1
        bridge-ports enx000ec6ec4728
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

Now, if I disconnect/reconnect the ethernet, it will automatically re-establish the connection.

FStefanni · Jul 14, 2024

Hi,

I have a similar issue. I have a LAN, and I want to plug/unplug a PC to Proxmox LAN NIC/bridge.
Adding allow-hotplug seems fine, as long as I set a static IP to my PC.
For the dynamic IP assignment, I have an instance of OPNSense in Proxmox, but if I unplug and then plug-in back, the PC says "IP configuration was unavailable".
Not clear to me why this happens...

Any hint?

Regards

Search

Search

Network will not reconnect

Tue-A

New Member

Attachments

Dunuin

Distinguished Member

Tue-A

New Member

Attachments

Dunuin

Distinguished Member

Tue-A

New Member

Tue-A

New Member

Tue-A

New Member

Attachments

Tue-A

New Member

gfgjs

New Member

xelar

New Member

novice4ever

New Member

McFly83

New Member

eejay

New Member

McFly83

New Member

McFly83

New Member

Rework1415

New Member

FStefanni

New Member