From: Sven-Haegar Koch <haegar@sdinet.de>
To: Marc Haber <mh+netdev@zugschlus.de>
Cc: Stephen Hemminger <shemminger@vyatta.com>, netdev@vger.kernel.org
Subject: Re: Bridge stays down until a port is added
Date: Fri, 12 Aug 2011 14:22:27 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1108121418090.11637@aurora> (raw)
In-Reply-To: <20110811205429.GB21307@torres.zugschlus.de>
On Thu, 11 Aug 2011, Marc Haber wrote:
> On Thu, Aug 11, 2011 at 08:17:06AM -0700, Stephen Hemminger wrote:
> > On Thu, 11 Aug 2011 09:06:59 +0200
> > Marc Haber <mh+netdev@zugschlus.de> wrote:
> > > Is that a feature? If so, why does the interface stay pingable after
> > > removing the dummy0 interface from the bridge?
> >
> > Yes, there are no links to send a packet so it seems logical
> > that there would be no carrier.
>
> Yes, but if I can configure an IP address to the bridge I would expect
> it to be reachable even if there are no interfaces in the bridge.
> "Older" kernels used to behave like that.
For me (using kernel 3.0.0) it seems to work as I expect it:
aurora:~# brctl addbr br0
aurora:~# ifconfig br0 192.168.254.1 netmask 255.255.255.0 up
aurora:~# ping 192.168.254.1
PING 192.168.254.1 (192.168.254.1) 56(84) bytes of data.
64 bytes from 192.168.254.1: icmp_req=1 ttl=64 time=0.087 ms
aurora:~# ifconfig br0
br0 Link encap:Ethernet HWaddr 96:e1:ba:9f:91:f9
inet addr:192.168.254.1 Bcast:192.168.254.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
The br0 interface has no carrier / is not "running", exactly like an
ethernet port without a cable.
c'ya
sven-haegar
--
Three may keep a secret, if two of them are dead.
- Ben F.
next prev parent reply other threads:[~2011-08-12 12:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 7:06 Bridge stays down until a port is added Marc Haber
2011-08-11 15:17 ` Stephen Hemminger
2011-08-11 20:54 ` Marc Haber
2011-08-11 22:41 ` Stephen Hemminger
2011-08-12 12:22 ` Sven-Haegar Koch [this message]
2011-08-20 9:47 ` Marc Haber
2011-08-20 16:30 ` Stephen Hemminger
2011-08-21 12:13 ` Marc Haber
2011-08-22 15:57 ` Stephen Hemminger
2011-09-17 20:42 ` Marc Haber
2011-09-20 20:20 ` Dan Williams
2011-09-25 8:25 ` Marc Haber
2011-09-26 15:47 ` Stephen Hemminger
2011-09-26 20:02 ` Nicolas de Pesloüan
2011-09-26 20:05 ` Stephen Hemminger
2011-09-26 20:56 ` Ben Hutchings
2011-09-26 22:12 ` Nicolas de Pesloüan
2011-09-26 22:42 ` Stephen Hemminger
2011-09-27 0:28 ` Sven-Haegar Koch
2011-09-27 0:43 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1108121418090.11637@aurora \
--to=haegar@sdinet.de \
--cc=mh+netdev@zugschlus.de \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox