From: David Woodhouse <dwmw2@infradead.org>
To: Matthias Thomae <bluez@thomae-privat.de>
Cc: Christoph Scholz <scholz@cs.uni-bonn.de>,
bluez-devel@lists.sourceforge.net, marcel@holtmann.org
Subject: Re: [Fwd: Re: [Bluez-devel] PAN and bridge problem when bnep0 disconnects before bnep1]
Date: Fri, 14 May 2004 14:04:51 +0100 [thread overview]
Message-ID: <1084539891.6181.68.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <40A480B8.2050400@thomae-privat.de>
On Fri, 2004-05-14 at 10:18 +0200, Matthias Thomae wrote:
> > I have not written to to the bridge people. My personal opinion is that
> > BlueZ should do the forwarding (like Affix does). You can argue about
> > that of course.
>
> I don't have a competent opinion about that (except: it's not only the
> forwarding problem, but also DHCP, right?), and don't know what Affix does.
I don't think it makes sense to do the bridging in our BNEP code. We
already _have_ bridging code in the kernel, and there's no sense in
duplicating it. Using the existing code allows us to do things like
bridging directly onto real Ethernet, too.
> Marcel, what do you think? Is there any sense to contact the bridge people?
The mail at http://lists.osdl.org/pipermail/bridge/2004-May/000321.html
to which Diego referred was from the 'bridge people', and says:
"The bridge code was being to picky. The bridge will still work fine
when there are two interfaces with the same local address, because it is
only used for setting the source address on the outgoing bridge
packets."
It seems that we can read 'should still work fine' instead of 'will
still work fine' in the above, given your report -- so yes, you should
report it as a bug in the bridging code if you still can't get it to
work on 2.6.6 + Stephen's patch.
--
dwmw2
prev parent reply other threads:[~2004-05-14 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 17:00 [Fwd: Re: [Bluez-devel] PAN and bridge problem when bnep0 disconnects before bnep1] Christoph Scholz
2004-05-14 8:18 ` Matthias Thomae
2004-05-14 13:04 ` David Woodhouse [this message]
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=1084539891.6181.68.camel@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez@thomae-privat.de \
--cc=marcel@holtmann.org \
--cc=scholz@cs.uni-bonn.de \
/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