diff options
author | Niels Boehm <blubberdiblub@gmail.com> | 2013-02-04 18:05:17 +0000 |
---|---|---|
committer | Jo-Philipp Wich <jow@openwrt.org> | 2013-04-23 16:00:13 +0200 |
commit | 2008ae9a80fb82b0018fd510043c291b58e7cc46 (patch) | |
tree | 694ac0ac18e5c41286b4c9d0704d9883d10f07c9 /system.h | |
parent | cbb2b3270ad59ca91a04aba94eee0c73e24ce80b (diff) |
add bridge priority option
[netifd] add bridge priority option
Using the bridge priority (lower numbers are higher in the
hierarchy), one can ensure that the router is chosen as root
bridge in a setup with spanning tree protocol.
For instance, one can set the priority of network lan to 32767,
causing the router to win over all directly and indirectly
connected nodes that have a default priority of 32768.
The reason for doing that is that otherwise it has a default
priority 32768 as well and any other connected node could win and
get root bridge. In a home setup, those nodes are often desktop
or laptop boxes and get switched off from time to time. As a
consequence, root bridges vanish or new root bridges get chosen
relatively often, resulting in frequent topology changes to the
STP network. While the new topology has not settled, packets can
get lost, causing noticeable interruptions of network traffic.
Setting the router's bridge on a lower numbered priority (and thus
higher in the selection hierarchy) solves the problem in the vast
majority of the cases by ensuring that the device that is most
likely powered on 24/7 gets chosen as root and prevents topology
changes.
Signed-off-by: Niels Boehm <blubberdiblub@gmail.com>
Diffstat (limited to 'system.h')
-rw-r--r-- | system.h | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -38,12 +38,14 @@ enum bridge_opt { BRIDGE_OPT_AGEING_TIME = (1 << 0), BRIDGE_OPT_HELLO_TIME = (1 << 1), BRIDGE_OPT_MAX_AGE = (1 << 2), + BRIDGE_OPT_PRIORITY = (1 << 3), }; struct bridge_config { enum bridge_opt flags; bool stp; bool igmp_snoop; + unsigned short priority; int forward_delay; int ageing_time; |