search

openvswitch / ovs-issues

Issue tracker repo for Open vSwitch
10 stars 3 forks source link

Woes with RSTP and internal interface #227

Open docbobo opened 3 years ago

docbobo commented 3 years ago

I am running OVS 2.15.0 on two different machines with RSTP enabled. In general, things seemed to work as expected.

Machine A

a5e90ae4-e89a-4720-8d09-f601bddb2af5
    Bridge vmbr0
        Port eno2
            Interface eno2
        Port eno3
            Interface eno3
        Port veth8101i1
            Interface veth8101i1
        Port eno4
            Interface eno4
        Port veth8101i0
            tag: 128
            Interface veth8101i0
        Port vlan128
            tag: 128
            Interface vlan128
                type: internal
        Port vmbr0
            Interface vmbr0
                type: internal
        Port tap9000i0
            tag: 97
            Interface tap9000i0
        Port vlan1
            Interface vlan1
                type: internal
        Port eno1
            Interface eno1
    ovs_version: "2.15.0"

Machine B

5d28de10-2c4e-44b2-9381-3112662efebd
    Bridge vmbr0
        Port enp1s0f0
            Interface enp1s0f0
        Port vlan128
            tag: 128
            Interface vlan128
                type: internal
        Port vlan1
            Interface vlan1
                type: internal
        Port ens9
            Interface ens9
        Port vmbr0
            Interface vmbr0
                type: internal
    ovs_version: "2.15.0"

As you can see, Machine A has two ports tagged for vlan 128. Machine B can ping anything on veth8101i0, pinging the IP on vlan128 does not work.

I've noticed that veth8101i0 is reporting rstp_status while vlan128 isn't, but I suspect that might be a red herring. Help would be appreciated.

docbobo commented 3 years ago

BTW, once RSTP is disabled on vmbr0, everything works fine (well, except the things I want to get out of RTSP). Plus, it's sufficient to disable it on one of the hosts.

Another "fun fact": enabling rstp on the bridge after the two hosts could see each other, the connectivity stays alive.

docbobo commented 3 years ago

Okay, I can get the two systems to communicate properly, even with RTSP enabled, when I manually update the ARP table.

But shouldn’t that work automatically? It certainly does for the virtual Ethernet interfaces…

virtualbitzz commented 2 years ago

Having the exact same issue, identical in every way. If I ping an external host from the OVSInt port, then OVS get's an ARP entry and everything works, until the ARP timer expires.

virtualbitzz commented 2 years ago

https://forum.proxmox.com/threads/ovs-intport-you-cant-ping-me-unless-i-ping-you-first.104828/#post-480080