public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [Bluez-devel] PAN and bridge problem when bnep0 disconnects before bnep1
@ 2004-05-13 12:51 Christoph Scholz
  2004-05-13 14:07 ` Diego Liziero
  2004-05-13 14:09 ` Matthias Thomae
  0 siblings, 2 replies; 7+ messages in thread
From: Christoph Scholz @ 2004-05-13 12:51 UTC (permalink / raw)
  To: bluez-devel

[-- Attachment #1: Type: text/plain, Size: 352 bytes --]

Hi,

I experienced the same problem as Matthias Thomae. I already posted this
to the mailing-list some time ago (see attached mail). It is actually a
problem with the Linux bridge code. It does not seem to be able to cope
with multiple interfaces using the same MAC-Address.

Unfortunately, I have no real solution to the problem.

Regards,

Christoph

[-- Attachment #2: Forwarded message - Problems with Bridging and PAN Profile --]
[-- Type: message/rfc822, Size: 2101 bytes --]

From: Christoph Scholz <scholz@cs.uni-bonn.de>
To: bluez-users@lists.sourceforge.net
Subject: Problems with Bridging and PAN Profile
Date: Fri, 09 Jan 2004 14:49:02 +0100
Message-ID: <1073656142.3037.32.camel@willie.informatik.uni-bonn.de>

Hi all,

I am experiencing problems with the Linux transparent bridge
implementation combined with BlueZ. Probably it is not BlueZ' fault but
related. Just wanted to know if someone else knows about this problem.

I used a very simple PAN scenario with one master (GN) and two slaves
(PANU). The GN runs a Linux bridge and the individual devices for the
slaves are added to the bridge by using the "/etc/bluetooth/pan/dev-up"
script. All similar to the PAN Howto.

After establishing the two connections everything works fine. But after
disconnecting the first slave (the one that was connected to the master
first) communication between the master and the remaining slave does not
work any more. Closer investigation shows that the failure is found in
the bridge device that does not accept the received frames any more.
Interestingly, when runing tcpdump on the bridged device everything
seems to work fine again. This is probably due to the bridge device
entering promiscuous mode. Probably, the problem is related to the
following message found in /var/log/messages:

"bnep1: attempt to add interface with same source address."

This is due to the fact that all the bnep interfaces own the same MAC
address (= BD_ADDR of the Bluetooth device).

It seems the Linux bridge does not work reliably with duplicate mac
addresses on its interface. 

Does anyone of you experienced similar problems? Any ideas on how to
resolve this?

Thanks.


Regards,

Christoph
-- 
Christoph Scholz <scholz@cs.uni-bonn.de>
University of Bonn, Institut of Computer Science IV
Römerstraße 164,
D-53117 Bonn, Germany
Phone: +49 228 73 4117
Fax: +49 228 73 4571
http://web.informatik.uni-bonn.de/IV/Mitarbeiter/scholz/

^ permalink raw reply	[flat|nested] 7+ messages in thread
* [Bluez-devel] PAN and bridge problem when bnep0 disconnects before bnep1
@ 2004-05-12 19:26 Matthias Thomae
  2004-05-12 21:42 ` Marcel Holtmann
  0 siblings, 1 reply; 7+ messages in thread
From: Matthias Thomae @ 2004-05-12 19:26 UTC (permalink / raw)
  To: bluez-devel

Hello,

I have a BlueZ NAP setup with bridging (essentially following the PAN
HOWTO), which works quite nicely (thanks to all developers :) except
when the first connected bnep0 client is killed before the 2nd client
(bnep1).

I am running a DHCP server on the server's bridge (pan0), and eth0 is
NOT part of the bridge, I use IP forwarding instead.

The problem is, that after bnep0 is removed (by killing it on the
respective client with 'pand -K'), bnep1 doesn't 'work' any longer,
meaning ping etc. don't work any more. And I couldn't find anything in
the syslogs, except that after a while the client's DHCP client starts
to issue DHCPDISCOVERs.

ifdown/ifup on bnep1 don't seem to help either, the only way I could
find to make it work again was to issue 'pand -K' on the server and
reconnect the clients.

If bnep1 disconnects before bnep0, no problem.

I'm using quite late BlueZ versions on all machines (at least kernel
2.6.5-mh3 and the latest Debian bluez-utils 2.6-1 and bluez-pan
1.1rel-4), and I can reproduce the behaviour also with a Windows client
on bnep0.

Any clues?

Regards.
Matthias



-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2004-05-14 13:57 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox