From: Diego Liziero <liziero.diego@unimore.it>
To: Christoph Scholz <scholz@cs.uni-bonn.de>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] PAN and bridge problem when bnep0 disconnects before bnep1
Date: Thu, 13 May 2004 20:22:43 +0200 [thread overview]
Message-ID: <1084472563.3354.17.camel@igno> (raw)
In-Reply-To: <1084457228.6449.11.camel@igno>
I've solved my issue.
Mine was just a bridge bug introduced in 2.6.6
and already solved.
http://lists.osdl.org/pipermail/bridge/2004-May/000321.html
Regards,
Diego.
On Thu, 2004-05-13 at 16:07, Diego Liziero wrote:
> Maybe I'm hitting a related bug.
> I'm trying to setup a PAN bridge with kernel 2.6.6-rc3-mm2
> with ipv6 enabled (same result with other 2.6 kernels) and when I try
> to add bnep1 to the bridge I got the following error:
>
> # brctl addif pan0 bnep1
> br_add_interface: File exists
>
> Everything works fine with 2.4.* kernels (without ipv6).
>
> It seems like in linux-2.6.* + ipv6 it's impossible to have
> two bnep interfaces in the same bridge.
>
> Any suggestion?
>
> Regards,
>
> Diego.
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-05-13 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 12:51 [Bluez-devel] PAN and bridge problem when bnep0 disconnects before bnep1 Christoph Scholz
2004-05-13 14:07 ` Diego Liziero
2004-05-13 18:22 ` Diego Liziero [this message]
2004-05-13 14:09 ` Matthias Thomae
-- strict thread matches above, loose matches on Subject: below --
2004-05-12 19:26 Matthias Thomae
2004-05-12 21:42 ` Marcel Holtmann
2004-05-14 13:57 ` Paulo Marques
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=1084472563.3354.17.camel@igno \
--to=liziero.diego@unimore.it \
--cc=bluez-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.