OVS IntPort Gateway not working

crispyduck

New Member
Feb 17, 2022
16
0
1
40
Hi,

I tried to switch my config to OVS, but have now the issue that the GW configured on a OVS IntPort for Mgmt is not working.

here the related config. There is no other GW configured:

Code:
auto mgmt1708
iface mgmt1708 inet static
        address 10.17.8.61/24
        gateway 10.17.8.1
        ovs_type OVSIntPort
        ovs_bridge vmbr1
        ovs_mtu 1500
        ovs_options tag=1708
        
auto bond2
iface bond2 inet manual
        ovs_bonds enp8s0f0 enp8s0f1 ens2f0 ens2f1
        ovs_type OVSBond
        ovs_bridge vmbr1
        ovs_mtu 9000
        ovs_options bond_mode=active-backup

auto vmbr1
iface vmbr1 inet manual
        ovs_type OVSBridge
        ovs_ports bond2 mgmt1708
        ovs_mtu 9000

ip a output:

Code:
14: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ce:d9:8e:46:43:16 brd ff:ff:ff:ff:ff:ff
15: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 00:19:99:83:ea:04 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::f4c5:29ff:fe16:b549/64 scope link
       valid_lft forever preferred_lft forever
16: mgmt1708: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 32:d0:aa:52:d7:72 brd ff:ff:ff:ff:ff:ff
    inet 10.17.8.61/24 scope global mgmt1708
       valid_lft forever preferred_lft forever
    inet6 fe80::30d0:aaff:fe52:d772/64 scope link
       valid_lft forever preferred_lft forever
19: bond2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 76:5b:75:c6:cd:45 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::745b:75ff:fec6:cd45/64 scope link
       valid_lft forever preferred_lft forever

even after a restart mgmt1708 does not show a GW.

Br
 
Hi! Sorry I totally forgot to look on the routs.
Now I already totally reconfiguered the network and I am actually no more using OVS.

At the moment I can only tell how it behaved.
Before my post I tried several times switching between a Linux br with the IP and GW configured and a OVS with IntPort as posted.
And it was/looked alwas as the GW is ignored on the OVS IntPort.

Later switching to back to native Linux br and bond and vlan I had als some other strange behaviours.
For sure there was no was no wrong network/interface config, but as you also requested, maybe some routes where not cleaned up,...

I did many things via the GUI, had there also some other issues. Seems it is better to configure networking directly, or at least don't use the only the GUI and Apply to try different configs without reboot or network restart in between.

At the moment I have no possibility to retry/reproduce it.
For sure there where several problems, or at least strange behaviors.

I don't know, should I close this topic and mark it as solved for now?
For sure with the next cluster I will again try to configure it with OVS, but on the actuall one I don't have time to try this again.

Br
cb
 

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!

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!