Merge pull request #17050 from chriswiggins/doc/vrrp-in-vm-bridge

Adds note about VRRP issues inside a VM with underlying bridge networking
This commit is contained in:
Donatas Abraitis 2024-10-10 12:45:49 +03:00 committed by GitHub
commit 2634ad94c6
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -519,6 +519,7 @@ Check:
- Do you have unusual ``sysctls`` enabled that could affect the operation of
multicast traffic?
- Are you running in ESXi? See below.
- Are you running in a linux VM with a bridged network? See below.
My master router is not forwarding traffic
@ -552,6 +553,24 @@ feature instead, explained `here
Issue reference: https://github.com/FRRouting/frr/issues/5386
My router is running in a linux VM with a bridged host network and VRRP has issues
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Issues can arise with VRRP (especially IPv6) when you have a VM running on top
of a linux host, where your physical network is in a bridge, and the VM
has an interface attached to the bridge. By default, the linux bridge will
snoop multicast traffic, and you will likely see sporadic VRRP advertisements failing
to be received. IPv6 traffic was be particularly affected.
This was observed on a VM running on proxmox, and the solution was to disable
multicast snooping on the bridge:
.. code-block:: console
echo 0 > /sys/devices/virtual/net/vmbr0/bridge/multicast_snooping
Issue reference: https://github.com/FRRouting/frr/issues/5386
My router cannot interoperate with branded routers / L3 switches
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^