[SOLVED] No network on server unless i ifdown / ifup vmbr0

spirit said:
@CLE : ok networking is enabled. I'm going to test your config today.

also, could you replace:

allow-hotplug eno1

by

iface eno1 inet manual

?
Click to expand...

Replacing this line seems to have done the trick?!

I've rebooted the server and the server as well as my VM and Container do have networking without a manual intervention!

@spirit thank you very much - if you need anything from me to further test this, let me know! For now i just have to remember to not touch the networking configuration from the GUI, right?

Everyone else chiming in (@jrshaw , @Homercles , @syfy323 ) Thank you as well!
 
CLE said:
@spirit thank you very much - if you need anything from me to further test this, let me know! For now i just have to remember to not touch the networking configuration from the GUI, right?
Click to expand...

Was the "allow-hotplug eno1" setup by gui ?
or maybe by the proxmox installer cd iso ?
 
CLE said:
Replacing this line seems to have done the trick?!

I've rebooted the server and the server as well as my VM and Container do have networking without a manual intervention!

@spirit thank you very much - if you need anything from me to further test this, let me know! For now i just have to remember to not touch the networking configuration from the GUI, right?

Everyone else chiming in (@jrshaw , @Homercles , @syfy323 ) Thank you as well!
Click to expand...

Are you sure your connection lasts more than an hour?
Using the latest kernel causes a lot of issues with OVS an Proxmox for me (where CentOS and Debian stock work perfectly fine).
 
also, normally, the correct config should be only:

allow-vmbr0 eno1

without any "auto eno1", or "allow-hotplug eno1".

This is because it's racing between ovs init script, and ifupdown init script.

I'm pretty sure that proxmox gui is doing it fine, but I need to verify that.
 
spirit said:
Was the "allow-hotplug eno1" setup by gui ?
or maybe by the proxmox installer cd iso ?
Click to expand...
The Server has been set up with a bare Debian (due to software RAID) and Proxmox after that according to the Wiki entry.

I‘m actually not sure if the entry was a leftover from the default install or if that was set by Proxmox.


syfy323 said:
Are you sure your connection lasts more than an hour?
Using the latest kernel causes a lot of issues with OVS an Proxmox for me (where CentOS and Debian stock work perfectly fine).
Click to expand...

I‘m not yet sure about that - server is powered down at the moment but i‘ll try and let you know!
 
CLE said:
The Server has been set up with a bare Debian (due to software RAID) and Proxmox after that according to the Wiki entry.
I‘m actually not sure if the entry was a leftover from the default install or if that was set by Proxmox.
Click to expand...

mmm,ok. I'll try to check if gui&&api could be improve to remove allow-hotplug when ovs is used
 
spirit said:
Systemctl status networking ? (I have see some case where service was not enabled After ifupdown2 install )
Click to expand...

You are right! systemctl status networking was not enable and not running. I went ahead and just enabled the service and started it, I will try to reboot the server later when I have physical access to it.

Thank you sir!
 
Awesome, thank you @spirit !

syfy323 said:
Are you sure your connection lasts more than an hour?
Using the latest kernel causes a lot of issues with OVS an Proxmox for me (where CentOS and Debian stock work perfectly fine).
Click to expand...

Server is up for around 2 hours now, networking still is fine (for VM/Containers as well as the host).

Output of uname -a

Linux servername 5.3.13-1-pve #1 SMP PVE 5.3.13-1 (Thu, 05 Dec 2019 07:18:14 +0100) x86_64 GNU/Linux
Click to expand...

@syfy323: if you want to know something else about my setup (like package versions and such) just let me know the commands to run!
 
CLE said:
@syfy323: if you want to know something else about my setup (like package versions and such) just let me know the commands to run!
Click to expand...

Thank you for the feedback. Did you enable the firewall option for your VM network interface (right there were you can set the hwaddr)?
I was only able to reproduce this when the firewall option is not enabled.
 
Just adding to the discussion though a different thread might be more appropriate.
I was having to issue the 'ifup vmbr0' command following each reboot to bring up the network on one of my 3 servers. All 3 servers are running a recent PVE kernel - SMP PVE 5.3.13-1 - and openvswitch-common/switch v2.10 with OVS bonds.
On the one server where I need to bring up the bridge following each reboot, I has installed ifupdown2 at the time when I was using the Linux bonds. When I installed the OVS bridge and bonds, I all of a sudden had the no-networking issue following reboot.
The solution was to uninstall the ifupdown2 package, reinstall the ifupdown package, and networking started coming up automatically following a reboot.
 
pkuwik said:
Just adding to the discussion though a different thread might be more appropriate.
I was having to issue the 'ifup vmbr0' command following each reboot to bring up the network on one of my 3 servers. All 3 servers are running a recent PVE kernel - SMP PVE 5.3.13-1 - and openvswitch-common/switch v2.10 with OVS bonds.
On the one server where I need to bring up the bridge following each reboot, I has installed ifupdown2 at the time when I was using the Linux bonds. When I installed the OVS bridge and bonds, I all of a sudden had the no-networking issue following reboot.
The solution was to uninstall the ifupdown2 package, reinstall the ifupdown package, and networking started coming up automatically following a reboot.
Click to expand...
please provide your /etc/network/interfaces.
 
Here it is as requested:

Code: 
allow-vmbr0 bond0
iface bond0 inet manual
    ovs_bonds eno1 eno2 eno3 eno4
    ovs_type OVSBond
    ovs_bridge vmbr0
    ovs_options bond_mode=balance-tcp lacp=active

auto lo
iface lo inet loopback

iface eno3 inet manual

iface eno1 inet manual

iface eno2 inet manual

iface eno4 inet manual

allow-ovs vmbr0
iface vmbr0 inet static
    address  192.168.1.20
    netmask  24
    gateway  192.168.1.1
    ovs_type OVSBridge
    ovs_ports bond0
 
@spirit I uninstalled the ifupdown2 to get my OVS working again, so can not tell you what version it was exactly, but I am using the pvetest repo, and not the enterprise one
 
pkuwik said:
@spirit I uninstalled the ifupdown2 to get my OVS working again, so can not tell you what version it was exactly, but I am using the pvetest repo, and not the enterprise one
Click to expand...
ok thanks. it's indeed ifupdown 2.0 in pvetest. I have found the bug (introduced in ifupdown2 2.0, it was working fine in 1.28).
I have send a patch, it should be fixed soon in pvetest repo.

Thanks for reporting !
 
  • Like
Reactions: pkuwik
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