public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Diego Liziero <liziero.diego@unimore.it>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bridge@lists.osdl.org, bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: [Bridge] bridging bluetooth bnep devices with kernel 2.6.6-*
Date: Mon, 17 May 2004 12:02:58 +0200	[thread overview]
Message-ID: <1084788177.21864.54.camel@igno> (raw)
In-Reply-To: <1084472140.3354.9.camel@igno>

Thanks for your support.

I'm back with the "brige freezes when bluetooth bnep0 disconnects
before bnep1" issue.

As reported in the bluez-devel mailing list, in a bridge
called pan0 with the interfaces bnep0, bnep1, .. bnep6
connected, if the interface bnep6 is disconnected first,
everything works fine, but if bnep0 is disconnected before
the others, the bridge stops to work.

Arping from bnep1 to the brige results in just the first
answer received.

To make it work again I have to use the following dirty hack:
 brctl delif pan0 bnep1
 brctl addif pan0 bnep1

Someone in the bluez-devel mailing list told that also setting the
bridge in promiscuous mode with tcpdump makes the bridge
back to work.

Now I'm removing and re-adding all the bridge components
when hotplug detects that a "bnep?" device ceases to exist.

Any better solution?

Regards,
Diego

On Thu, 2004-05-13 at 20:15, Diego Liziero wrote:
> Sorry, I've been too quick in writing without realizing
> that the patch had been already posted to this mailing list.
> 
> This patch solved everything.
> 
> Thank you.
> 
> BTW, there is another issue that may be related to the bridge
> that is being discussed on bluez-devel mailing list:
> 
> http://thread.gmane.org/gmane.linux.bluez.devel/2160
> 
> Regards,
> 
> Diego
> 
> On Thu, 2004-05-13 at 19:28, Stephen Hemminger wrote:
> > 2.6.6 got too picky about multiple interfaces with the same
> > address. This patch has been already integrated for later releases.
> 



-------------------------------------------------------
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

  parent reply	other threads:[~2004-05-17 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1084467136.3083.27.camel@igno>
     [not found] ` <20040513102829.5d5e1484@dell_ss3.pdx.osdl.net>
     [not found]   ` <1084472140.3354.9.camel@igno>
     [not found]     ` <20040513111904.6001c62a@dell_ss3.pdx.osdl.net>
2004-05-14  9:27       ` [Bluez-devel] Re: [Bridge] bridging bluetooth bnep devices with kernel 2.6.6-* Diego Liziero
2004-05-17 10:02     ` Diego Liziero [this message]
2004-05-18 22:33       ` Stephen Hemminger
2004-05-19  9:34         ` Diego Liziero
2004-05-18 22:36       ` Stephen Hemminger
2004-05-19 17:00         ` David Woodhouse

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=1084788177.21864.54.camel@igno \
    --to=liziero.diego@unimore.it \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=bridge@lists.osdl.org \
    --cc=shemminger@osdl.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