[PVE-User] Openvswicth conflict with network manager on host boot [was Multiple bridge on single physical interface]

Jean-mathieu CHANTREIN jean-mathieu.chantrein at univ-angers.fr
Mon Sep 25 12:41:21 CEST 2017


Hello.

----- Mail original -----
> De: "Yannis Milios" <yannis.milios at gmail.com>
> À: "pve-user" <pve-user at pve.proxmox.com>
> Envoyé: Jeudi 21 Septembre 2017 12:24:48
> Objet: Re: [PVE-User] Multiple bridge on single physical interface

>>
>> VM in subnetwork1(resp.2) on host1 must be communicate with VM in
>> subnetwork1(resp.2) on host2 via just one single interface and my host must
>> be not reacheable by subnetwork.
>>
>> How I can make this ?
>>
>>
>>
> Isolation at layer 2 can be achieved either by using 2 separate physical
> network cards or by utilising VLANs.
> I have done something similar by using openvswitch on pve. You can have a
> look if you want:
> 
> https://pve.proxmox.com/wiki/Open_vSwitch

Thanks for you reply. 

I was a little afraid to put my hands in openvswitch... I have tried and it's totally answer to my problematic. However, I think that there is a conflict between network-manager and openvswitch at the boot of host: Network manager fails with a timeout (5 minutes) to active interfaces and virtual bridges. 

Once logged on host, I have to make this to active all interfaces:
systemctl start networking.service # No time out anymore..., active all "regular" interface and "classic" bridge linux
systemctl stop networking.service 
systemctl start networking.service # No time out again, active all interfaces!

I have install net-tools package (apparently ifconfig is need by OVS...) and I have enable openvswitch-switch.service with systemctl:
systemctl enable openvswitch-switch.service

Is anyone ever encountering that?

Best regards.

Jean-Mathieu


More information about the pve-user mailing list