Skip to content

Commit 2634ad9

Browse files
authored
Merge pull request #17050 from chriswiggins/doc/vrrp-in-vm-bridge
Adds note about VRRP issues inside a VM with underlying bridge networking
2 parents d30fa81 + dbf39ad commit 2634ad9

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

doc/user/vrrp.rst

+19
Original file line numberDiff line numberDiff line change
@@ -519,6 +519,7 @@ Check:
519519
- Do you have unusual ``sysctls`` enabled that could affect the operation of
520520
multicast traffic?
521521
- Are you running in ESXi? See below.
522+
- Are you running in a linux VM with a bridged network? See below.
522523

523524

524525
My master router is not forwarding traffic
@@ -552,6 +553,24 @@ feature instead, explained `here
552553

553554
Issue reference: https://github.com/FRRouting/frr/issues/5386
554555

556+
My router is running in a linux VM with a bridged host network and VRRP has issues
557+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
558+
559+
Issues can arise with VRRP (especially IPv6) when you have a VM running on top
560+
of a linux host, where your physical network is in a bridge, and the VM
561+
has an interface attached to the bridge. By default, the linux bridge will
562+
snoop multicast traffic, and you will likely see sporadic VRRP advertisements failing
563+
to be received. IPv6 traffic was be particularly affected.
564+
565+
This was observed on a VM running on proxmox, and the solution was to disable
566+
multicast snooping on the bridge:
567+
568+
.. code-block:: console
569+
570+
echo 0 > /sys/devices/virtual/net/vmbr0/bridge/multicast_snooping
571+
572+
Issue reference: https://github.com/FRRouting/frr/issues/5386
573+
555574

556575
My router cannot interoperate with branded routers / L3 switches
557576
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

0 commit comments

Comments
 (0)