From: Paulo Marques <pmarques@grupopie.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Matthias Thomae <bluez@thomae-privat.de>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] PAN and bridge problem when bnep0 disconnects before bnep1
Date: Fri, 14 May 2004 14:57:17 +0100 [thread overview]
Message-ID: <40A4D03D.3060701@grupopie.com> (raw)
In-Reply-To: 1084398131.25099.115.camel@pegasus
>>
>>If bnep1 disconnects before bnep0, no problem.
>>
I had a similar problem a while ago (it was a 2.4.xx kernel, didn't try a 2.6
kernel yet).
The problem was that the bridge interface borrowed the mac address from one of
the interfaces attached to it.
When this interface disconnected, the bridge would start using the MAC from some
other interface. Because of this, other computers on the network, relying on
their arp cache, could not contact the bridge any more.
I tried "arp-pinging" the network to announce the new mac, but couldn't make it
work. (maybe I was doing something wrong)
I eventually gave up, without finding any solution.
As I said, I didn't try kernel 2.6. I remember reading somewhere that there was
a new kernel internal API to get a "valid" random MAC address and that the
bridging code was using it, but I'm not sure I didn't got it wrong.
Just my 2 cents,
--
Paulo Marques - www.grupopie.com
"In a world without walls and fences who needs windows and gates?"
next prev parent reply other threads:[~2004-05-14 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 19:26 [Bluez-devel] PAN and bridge problem when bnep0 disconnects before bnep1 Matthias Thomae
2004-05-12 21:42 ` Marcel Holtmann
2004-05-14 13:57 ` Paulo Marques [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-13 12:51 Christoph Scholz
2004-05-13 14:07 ` Diego Liziero
2004-05-13 18:22 ` Diego Liziero
2004-05-13 14:09 ` Matthias Thomae
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=40A4D03D.3060701@grupopie.com \
--to=pmarques@grupopie.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez@thomae-privat.de \
--cc=marcel@holtmann.org \
/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