All of lore.kernel.org
 help / color / mirror / Atom feed
From: Diego Liziero <diego.liziero@unimore.it>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bluez-devel@lists.sourceforge.net, bridge@lists.osdl.org,
	Diego Liziero <liziero.diego@unimore.it>
Subject: Re: [Bridge] bridging bluetooth bnep devices with kernel 2.6.6-*
Date: Wed, 19 May 2004 11:34:05 +0200	[thread overview]
Message-ID: <1084959245.6454.34.camel@igno> (raw)
In-Reply-To: <20040518153310.6ca39ef5@dell_ss3.pdx.osdl.net>

Thanks for your help.

I forgot to mention the steps I did to setup the bridge.

I have 2 ethernet cards, eth0->to internet,
eth1->192.168.* natted lan.

I'm using a Debian with hotplug and in
/etc/network/interfaces I have the following lines:

iface pan0 inet static
        pre-up brctl addbr pan0
        pre-up brctl addif pan0 eth1
        pre-up ifconfig eth1 0.0.0.0
        address 192.168.111.1
        netmask 255.255.255.0
        up brctl setfd pan0 0
        up brctl stp pan0 disable
        up /etc/init.d/dhcp3-server restart
        post-down brctl delbr pan0
        post-down ifconfig eth1 192.168.111.1 netmask 255.255.255.0
        post-down /etc/init.d/dhcp3-server restart
                                                                                                                             iface bnep0 inet static
        address 192.168.111.70
        netmask 255.255.255.0
        pre-up brctl addif pan0 $IFACE
        up ifconfig $IFACE 0.0.0.0
        down brctl delif pan0 $IFACE

iface bnep1 inet static
        address 192.168.111.71
        netmask 255.255.255.0
        pre-up brctl addif pan0 $IFACE
        up ifconfig $IFACE 0.0.0.0
        down brctl delif pan0 $IFACE

When the first PDA is connected I get the following in the syslog:

net.agent[7222]: invoke ifup bnep0=hotplug
kernel: device bnep0 entered promiscuous mode
pand[7220]: New connection from 00:80:C8:1F:E3:77 bnep0
kernel: pan0: port 2(bnep0) entering learning state
kernel: pan0: topology change detected, propgating
kernel: pan0: port 2(bnep0) entering forwarding state
dhcpd: DHCPREQUEST for 192.168.111.171 from 00:80:c8:1f:e3:77 via pan0
dhcpd: DHCPACK on 192.168.111.171 to 00:80:c8:1f:e3:77 via pan0

When I connect the second one:

net.agent[7271]: invoke ifup bnep1=hotplug
pand[7269]: New connection from 00:40:05:60:5A:14 bnep1
kernel: device bnep1 entered promiscuous mode
kernel: pan0: port 3(bnep1) entering learning state
kernel: pan0: topology change detected, propgating
kernel: pan0: port 3(bnep1) entering forwarding state
dhcpd: DHCPDISCOVER from 00:40:05:60:5a:14 via pan0
dhcpd: DHCPOFFER on 192.168.111.172 to 00:40:05:60:5a:14 via pan0
dhcpd: DHCPREQUEST for 192.168.111.172 (192.168.111.1) from
00:40:05:60:5a:14 via pan0
dhcpd: DHCPACK on 192.168.111.172 to 00:40:05:60:5a:14 via pan0

When I disconnect the first one (bnep0) first:

net.agent[7299]: invoke ifdown bnep0
kernel: pan0: port 2(bnep0) entering disabled state
kernel: pan0: port 2(bnep0) entering disabled state
kernel: device bnep0 left promiscuous mode
  
# brctl showstp pan0
pan0
 STP is disabled for this interface

When I disconnect also the second one (bnep1): 

kernel: pan0: port 3(bnep1) entering disabled state
kernel: pan0: port 3(bnep1) entering disabled state
kernel: device bnep1 left promiscuous mode
net.agent[7319]: invoke ifdown bnep1

Regards,
Diego

On Wed, 2004-05-19 at 00:33, Stephen Hemminger wrote:
> Sounds like an issue with how the bnep does promiscious mode.
> Do you see messages on the console like:
> 	device bnep0 left promiscious mode
> 
> Also, the bnep driver seems to need BT_BNEP_MC_FILTER enabled
> to do multicast.  
> 
> When you remove bnep0 first, what does "brctl showstp pan0" show?



WARNING: multiple messages have this Message-ID (diff)
From: Diego Liziero <diego.liziero@unimore.it>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Diego Liziero <liziero.diego@unimore.it>,
	bridge@lists.osdl.org, bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: [Bridge] bridging bluetooth bnep devices with kernel 2.6.6-*
Date: Wed, 19 May 2004 11:34:05 +0200	[thread overview]
Message-ID: <1084959245.6454.34.camel@igno> (raw)
In-Reply-To: <20040518153310.6ca39ef5@dell_ss3.pdx.osdl.net>

Thanks for your help.

I forgot to mention the steps I did to setup the bridge.

I have 2 ethernet cards, eth0->to internet,
eth1->192.168.* natted lan.

I'm using a Debian with hotplug and in
/etc/network/interfaces I have the following lines:

iface pan0 inet static
        pre-up brctl addbr pan0
        pre-up brctl addif pan0 eth1
        pre-up ifconfig eth1 0.0.0.0
        address 192.168.111.1
        netmask 255.255.255.0
        up brctl setfd pan0 0
        up brctl stp pan0 disable
        up /etc/init.d/dhcp3-server restart
        post-down brctl delbr pan0
        post-down ifconfig eth1 192.168.111.1 netmask 255.255.255.0
        post-down /etc/init.d/dhcp3-server restart
                                                                                                                             iface bnep0 inet static
        address 192.168.111.70
        netmask 255.255.255.0
        pre-up brctl addif pan0 $IFACE
        up ifconfig $IFACE 0.0.0.0
        down brctl delif pan0 $IFACE

iface bnep1 inet static
        address 192.168.111.71
        netmask 255.255.255.0
        pre-up brctl addif pan0 $IFACE
        up ifconfig $IFACE 0.0.0.0
        down brctl delif pan0 $IFACE

When the first PDA is connected I get the following in the syslog:

net.agent[7222]: invoke ifup bnep0=hotplug
kernel: device bnep0 entered promiscuous mode
pand[7220]: New connection from 00:80:C8:1F:E3:77 bnep0
kernel: pan0: port 2(bnep0) entering learning state
kernel: pan0: topology change detected, propgating
kernel: pan0: port 2(bnep0) entering forwarding state
dhcpd: DHCPREQUEST for 192.168.111.171 from 00:80:c8:1f:e3:77 via pan0
dhcpd: DHCPACK on 192.168.111.171 to 00:80:c8:1f:e3:77 via pan0

When I connect the second one:

net.agent[7271]: invoke ifup bnep1=hotplug
pand[7269]: New connection from 00:40:05:60:5A:14 bnep1
kernel: device bnep1 entered promiscuous mode
kernel: pan0: port 3(bnep1) entering learning state
kernel: pan0: topology change detected, propgating
kernel: pan0: port 3(bnep1) entering forwarding state
dhcpd: DHCPDISCOVER from 00:40:05:60:5a:14 via pan0
dhcpd: DHCPOFFER on 192.168.111.172 to 00:40:05:60:5a:14 via pan0
dhcpd: DHCPREQUEST for 192.168.111.172 (192.168.111.1) from
00:40:05:60:5a:14 via pan0
dhcpd: DHCPACK on 192.168.111.172 to 00:40:05:60:5a:14 via pan0

When I disconnect the first one (bnep0) first:

net.agent[7299]: invoke ifdown bnep0
kernel: pan0: port 2(bnep0) entering disabled state
kernel: pan0: port 2(bnep0) entering disabled state
kernel: device bnep0 left promiscuous mode
  
# brctl showstp pan0
pan0
 STP is disabled for this interface

When I disconnect also the second one (bnep1): 

kernel: pan0: port 3(bnep1) entering disabled state
kernel: pan0: port 3(bnep1) entering disabled state
kernel: device bnep1 left promiscuous mode
net.agent[7319]: invoke ifdown bnep1

Regards,
Diego

On Wed, 2004-05-19 at 00:33, Stephen Hemminger wrote:
> Sounds like an issue with how the bnep does promiscious mode.
> Do you see messages on the console like:
> 	device bnep0 left promiscious mode
> 
> Also, the bnep driver seems to need BT_BNEP_MC_FILTER enabled
> to do multicast.  
> 
> When you remove bnep0 first, what does "brctl showstp pan0" show?




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

  reply	other threads:[~2004-05-19  9:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 16:52 [Bridge] bridging bluetooth bnep devices with kernel 2.6.6-* Diego Liziero
2004-05-13 17:28 ` Stephen Hemminger
2004-05-13 18:15   ` Diego Liziero
2004-05-13 18:19     ` Stephen Hemminger
2004-05-14  9:27       ` Diego Liziero
2004-05-14  9:27         ` [Bluez-devel] " Diego Liziero
2004-05-17 10:02     ` Diego Liziero
2004-05-17 10:02       ` [Bluez-devel] " Diego Liziero
2004-05-18 22:33       ` Stephen Hemminger
2004-05-18 22:33         ` [Bluez-devel] " Stephen Hemminger
2004-05-19  9:34         ` Diego Liziero [this message]
2004-05-19  9:34           ` Diego Liziero
2004-05-18 22:36       ` Stephen Hemminger
2004-05-18 22:36         ` [Bluez-devel] " Stephen Hemminger
2004-05-19 17:00         ` David Woodhouse
2004-05-19 17:00           ` David Woodhouse
2004-05-21 15:59       ` [Bridge] locking Rajashekhar Mansanpally

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