summaryrefslogtreecommitdiffstats
path: root/net/bridge
diff options
context:
space:
mode:
authorstephen hemminger <shemminger@vyatta.com>2011-10-03 18:14:45 +0000
committerDavid S. Miller <davem@davemloft.net>2011-10-06 15:26:50 -0400
commitb64b73d7d0c480f75684519c6134e79d50c1b341 (patch)
tree4b8ecae0723a6149a0831fdcd7db9874e82fe8af /net/bridge
parent3458e21c0d384ca04b27a2ea24d9314c1b57530f (diff)
downloadlinux-b64b73d7d0c480f75684519c6134e79d50c1b341.tar.gz
linux-b64b73d7d0c480f75684519c6134e79d50c1b341.tar.bz2
linux-b64b73d7d0c480f75684519c6134e79d50c1b341.zip
bridge: leave carrier on for empty bridge
This resolves a regression seen by some users of bridging. Some users use the bridge like a dummy device. They expect to be able to put an IPv6 address on the device with no ports attached. Although there are better ways of doing this, there is no reason to not allow it. Note: the bridge still will reflect the state of ports in the bridge if there are any added. Signed-off-by: Stephen Hemminger <shemminger@vyatta.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bridge')
-rw-r--r--net/bridge/br_device.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/net/bridge/br_device.c b/net/bridge/br_device.c
index 32b8f9f7f79e..ff3ed6086ce1 100644
--- a/net/bridge/br_device.c
+++ b/net/bridge/br_device.c
@@ -91,7 +91,6 @@ static int br_dev_open(struct net_device *dev)
{
struct net_bridge *br = netdev_priv(dev);
- netif_carrier_off(dev);
netdev_update_features(dev);
netif_start_queue(dev);
br_stp_enable_bridge(br);
@@ -108,8 +107,6 @@ static int br_dev_stop(struct net_device *dev)
{
struct net_bridge *br = netdev_priv(dev);
- netif_carrier_off(dev);
-
br_stp_disable_bridge(br);
br_multicast_stop(br);