Linux bluetooth development
 help / color / mirror / Atom feed
From: Andy <andy@thebmwz3.co.uk>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] pand, bnep0 and no traffic flow
Date: Wed, 07 Mar 2007 22:20:04 +0000	[thread overview]
Message-ID: <45EF3A94.4040007@thebmwz3.co.uk> (raw)
In-Reply-To: <CE5216C10C83944D9FD37B65CD33F3970CF48D@mplex01.mpl.access-company.com>

Thanks for the hint Frederic, but yep its allowing ICMP ping's as it 
does on all other interfaces.

cat /proc/sys/net/ipv4/icmp_echo_ignore_all
0

(I also try SSH and HTTP to be sure and nothing passes the bluetooth link)

Regards,
-- 
Andy
e: andy@thebmwz3.co.uk
e: andy@broadcast-tech.co.uk

w: http://www.thebmwz3.co.uk
w: http://www.broadcast-tech.co.uk



Frederic Dalleau wrote:
> Your kernel is probably configured to not answer ping incoming request.
> look in /proc/sys/net/ipv4/
> 
> -----Original Message-----
> From: bluez-users-bounces@lists.sourceforge.net on behalf of Andy
> Sent: Wed 3/7/2007 12:47 PM
> To: bluez-users@lists.sourceforge.net
> Subject: [Bluez-users] pand, bnep0 and no traffic flow
>  
> Hi all,
> I'm trying to figure out where things are going wrong with my connection 
> here.
> Server A has /usr/bin/pand --listen -M --role=NAP
> Server B has pand --connect 00:02:72:B2:EF:21
> 
> The two initiate the connection, and create the bnep0 interface. I set 
> the IP addresses
> ifconfig bnep0 10.0.0.1 netmask 255.255.255.0
> ifconfig bnep0 10.0.0.2 netmask 255.255.255.0
> respectively, and neither can ping each other.
> 
> Checking the interface on server B, I see TX packets (pinging to server 
> A) but no RX packets. And on server A I see RX packets and no TX packets.
> 
> I started to think this was networking related, so disabled all iptables 
> firewalls (flushed, then all rules set to PERMIT) but still nothing
> When pings are running from B to A I see this (hcidump on server A):
>  > ACL data: handle 41 flags 0x02 dlen 17
>  > ACL data: handle 41 flags 0x01 dlen 17
>  > ACL data: handle 41 flags 0x01 dlen 7
>      L2CAP(d): cid 0x0040 len 37 [psm 0]
>  > ACL data: handle 41 flags 0x02 dlen 17
>  > ACL data: handle 41 flags 0x01 dlen 17
>  > ACL data: handle 41 flags 0x01 dlen 7
>      L2CAP(d): cid 0x0040 len 37 [psm 0]
>  > ACL data: handle 41 flags 0x02 dlen 17
>  > ACL data: handle 41 flags 0x01 dlen 17
>  > ACL data: handle 41 flags 0x01 dlen 7
>      L2CAP(d): cid 0x0040 len 37 [psm 0]
> 
> 
> Server A:
> hciconfig -a
> hci0:   Type: USB
>          BD Address: 00:02:72:B2:EF:DF ACL MTU: 192:8 SCO MTU: 64:8
>          UP RUNNING PSCAN
>          RX bytes:3347915 acl:39829 sco:0 events:100518 errors:0
>          TX bytes:1048399 acl:24626 sco:0 commands:34394 errors:0
>          Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>          Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>          Link policy: RSWITCH HOLD SNIFF PARK
>          Link mode: SLAVE ACCEPT
>          Name: 'geostat'
>          Class: 0x3e0100
>          Service Classes: Networking, Rendering, Capturing, Object 
> Transfer, Audio
>          Device Class: Computer, Uncategorized
>          HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP 
> Subver: 0x20d
>          Manufacturer: Cambridge Silicon Radio (10)
> 
> ip route
> 192.168.55.0/24 dev eth0  proto kernel  scope link  src 192.168.55.1
> 10.0.0.0/24 dev bnep0  proto kernel  scope link  src 10.0.0.2
> default via 192.168.55.252 dev eth0
> 
> 
> 
> Server B:
>   hciconfig -a
> hci0:   Type: USB
>          BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU: 64:10
>          UP RUNNING PSCAN ISCAN
>          RX bytes:17351 acl:251 sco:0 events:569 errors:0
>          TX bytes:24822 acl:464 sco:0 commands:37 errors:0
>          Features: 0xbf 0xfe 0x8d 0x78 0x08 0x18 0x00 0x00
>          Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>          Link policy:
>          Link mode: SLAVE ACCEPT
>          Name: 'ISSCBTA'
>          Class: 0x000000
>          Service Classes: Unspecified
>          Device Class: Miscellaneous,
>          HCI Ver: 1.2 (0x2) HCI Rev: 0x1fe LMP Ver: 1.2 (0x2) LMP 
> Subver: 0x1fe
>          Manufacturer: Integrated System Solution Corp. (57)
> 
> ip route
> 192.168.55.0/24 dev eth0  proto kernel  scope link  src 192.168.55.71
> 10.0.0.0/24 dev bnep0  proto kernel  scope link  src 10.0.0.1
> default via 192.168.55.1 dev eth0
> 
> (they are both linked via ethernet at present also, so disregard the 
> eth0 links)
> 
> Can anyone suggest what I can try to get this working please? It seems 
> almost there!
> 
> Thanks in advance


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-03-07 22:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 20:47 [Bluez-users] pand, bnep0 and no traffic flow Andy
2007-03-07 21:54 ` Frederic Dalleau
2007-03-07 22:20   ` Andy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-03-07 20:46 Andy
2007-03-08  7:13 ` "Hans-Jürgen Lange"
2007-03-08  8:43   ` Andy Brown
2007-03-24 12:57 ` Benjamin Hase

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=45EF3A94.4040007@thebmwz3.co.uk \
    --to=andy@thebmwz3.co.uk \
    --cc=bluez-users@lists.sourceforge.net \
    /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