diff options
| author | Linus Lüssing <linus.luessing@c0d3.blue> | 2015-08-23 17:19:28 +0200 |
|---|---|---|
| committer | Felix Fietkau <nbd@openwrt.org> | 2015-08-25 08:48:36 +0200 |
| commit | e057fcb4a260c70f0271f8fdcd7140775a09791f (patch) | |
| tree | dce1a7e96e814543c693f1b660de3f12ef823958 /device.h | |
| parent | 1488a64acb77f721fc10d90b0453d95b488460e1 (diff) | |
bridge: Allow setting multicast_router option
The multicast_router option of a bridge allows to control the forwarding
behaviour of multicast packets independant of the listener state:
* 0: Only forward if specific listener is present
* 1 (default): Forward if specific listener or a multicast router
was detected (currently only learned via query messages, no MRD
support yet)
* 2: Always forward any multicast traffic on this port
Since MRD is not mandated you might end up with silent multicast routers
(e.g. if your link has more than one multicast router; only one can
become the selected, "noisy" querier). Here you might need a manual
configuration option like the "multicast_router" option.
Other scenarios where this can be useful are for instance:
* Segmentation of IGMP/MLD domains together with ebtables
* Dedicated bridge port for monitoring/debugging purposes
Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
Diffstat (limited to 'device.h')
| -rw-r--r-- | device.h | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -43,6 +43,7 @@ enum { DEV_ATTR_XPS, DEV_ATTR_DADTRANSMITS, DEV_ATTR_MULTICAST_TO_UNICAST, + DEV_ATTR_MULTICAST_ROUTER, __DEV_ATTR_MAX, }; @@ -86,6 +87,7 @@ enum { DEV_OPT_MTU6 = (1 << 12), DEV_OPT_DADTRANSMITS = (1 << 13), DEV_OPT_MULTICAST_TO_UNICAST = (1 << 14), + DEV_OPT_MULTICAST_ROUTER = (1 << 15), }; /* events broadcasted to all users of a device */ @@ -144,6 +146,7 @@ struct device_settings { bool xps; unsigned int dadtransmits; bool multicast_to_unicast; + unsigned int multicast_router; }; /* |