bridge: control carrier based on ports online
This makes the bridge device behave like a physical device. In earlier releases the bridge always asserted carrier. This changes the behavior so that bridge device carrier is on only if one or more ports are in the forwarding state. This should help IPv6 autoconfiguration, DHCP, and routing daemons. I did brief testing with Network and Virt manager and they seem fine, but since this changes behavior of bridge, it should wait until net-next (2.6.39). Signed-off-by: Stephen Hemminger <shemminger@vyatta.com> Reviewed-by: Nicolas de Pesloüan <nicolas.2p.debian@free.fr> Tested-By: Adam Majer <adamm@zombino.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
committed by
David S. Miller
parent
942527634e
commit
1faa4356a3
@ -94,6 +94,7 @@ static void br_forward_delay_timer_expired(unsigned long arg)
|
||||
p->state = BR_STATE_FORWARDING;
|
||||
if (br_is_designated_for_some_port(br))
|
||||
br_topology_change_detection(br);
|
||||
netif_carrier_on(br->dev);
|
||||
}
|
||||
br_log_state(p);
|
||||
spin_unlock(&br->lock);
|
||||
|
Reference in New Issue
Block a user