public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Piconet problems
Date: Thu, 20 Jan 2005 13:52:13 +0100	[thread overview]
Message-ID: <1106225533.8190.178.camel@pegasus> (raw)
In-Reply-To: <IAM5FF$26988C38C1B7C74AE27C3AE78F151AF6@libero.it>

Hi Jers,

> I thank you for your time but, I'm sorry,  I can't display any packet. 
>  
> I changed my dongles. Their firmware is HCI 16.14: 
>  
> hci0:   Type: USB 
>         BD Address: 00:08:E0:01:9E:86 ACL MTU: 192:8 SCO MTU: 64:8 
>         UP RUNNING PSCAN ISCAN 
>         RX bytes:2508 acl:0 sco:0 events:60 errors:0 
>         TX bytes:465 acl:0 sco:0 commands:47 errors:0 
>         Features: 0xff 0xff 0x0b 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: 'pcB' 
>         Class: 0x000000 
>         Service Classes: Unspecified 
>         Device Class: Miscellaneous, 
>         HCI Ver: 1.1 (0x1) HCI Rev: 0x33c LMP Ver: 1.1 (0x1) LMP Subver: 0x33c 
>         Manufacturer: Cambridge Silicon Radio (10) 
>  
> I installed linux again (Mandrake 9.1, kernel 2.4.21) and the upgrated BlueZ packages in accordance with readme 
> files of each packages. I tried to create a simple connection. 
>  
> On the master side, I run: 
>  
> modprobe bnep 
> modprobe l2cap 
> hciconfig hci0 up 
> pand --listen --role GN 
>  
> On the slave side, I run; 
>  
> modprobe bnep 
> modprobe l2cap 
> hciconfig hci0 up 
> pand -c <master_addr> 
>  
> At first, "hcidump -x" dispayed packets sent by the pand command. Trying several times, it showed L2CAP and in 
> only one case I showed BNEP. However, no connection was create. 
> Then, maybe after a reboot or a logout, hcidump shows again that pand does not send any packet,. 
> I can't obtain again the same situation and I don't realize why.

show us the hcidump output and leave it to us to interpret it. And btw
what about using a 2.6.10 kernel? I can't tell you anything about any
vendor kernel.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-01-20 12:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 11:33 [Bluez-users] Piconet problems jers
2005-01-20 12:52 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-18 18:27 Arlen Nascimento
2005-07-18 18:36 ` Marcel Holtmann
2005-01-24 11:14 jers
2005-01-24 12:25 ` Marcel Holtmann
2005-01-20 15:49 jers
2005-01-21  0:42 ` Marcel Holtmann
2005-01-17  8:36 jers
2005-01-17 11:21 ` Marcel Holtmann
2005-01-14 10:21 jers
2005-01-14 21:18 ` Marcel Holtmann
2005-01-13 13:13 jers
2005-01-13 14:39 ` Marcel Holtmann
2005-01-13  9:22 jers
2005-01-13 10:46 ` Marcel Holtmann
2005-01-11 11:19 jers
2005-01-11 10:40 jers
2005-01-11 10:52 ` Benoit Panizzon
2005-01-11 12:06 ` Marcel Holtmann
2004-12-21 13:28 jers
2004-12-21 13:56 ` Marcel Holtmann
2004-12-21 11:02 jers
2004-12-21 11:16 ` Marcel Holtmann
2004-12-21 20:21 ` blookk -

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=1106225533.8190.178.camel@pegasus \
    --to=marcel@holtmann.org \
    --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