public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "jers@inwind.it" <jers@inwind.it>
To: "bluez-users" <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Piconet problems
Date: Tue, 21 Dec 2004 12:02:14 +0100	[thread overview]
Message-ID: <I92JZQ$4438CF5CD46EDB224256583706BE5074@libero.it> (raw)

Hi, 
 
I'm trying to create a simple piconet consisting of a master and=
 two slaves. I'm using three Digicom Palladio 
dongles. 
My packages li=
st is: 
 - bluez-libs-2.8-1.i386.rpm 
 - bluez-bluefw-1.0-1.i386.rpm =0D
=
 - bluez-hcidump-1.10-1.i386.rpm 
 - bluez-sdp-1.5-1.i386.rpm 
 - bluez=
-pan-1.1-1.i386.rpm 
 - bluez-utils-2.8-1.i386.rpm 
 - bridge-utils-0.9=
.6-1.i386.rpm 
 
 On master side I type: 
 # hciconfig hci0 up 
 # pa=
nd --listen --master --role GN 
 
 On the first slave I type: 
 # hcic=
onfig hci0 up 
 # hcitool inq 
 # pand --connect <master_bt_addr> 
 # =
ifconfig bnep0 10.10.10.2 broadcast 10.10.10.255 netmask 255.255.255.0 =0D
=
 
 if I type 
 # hcitool inq 
 I obtain: 
 
 Inquiry failed.: Device=
 or resource busy 
 
 On the second slave I type: 
 # hciconfig hci0 u=
p 
 # hcitool inq 
 I only obtain the master bt_addr. 
 # pand --conne=
ct <master_bt_addr> 
 
 and 
 # ifconfig bnep0 10.10.10.3 broadcast 10=
.10.10.255 netmask 255.255.255.0 
 
 Unfortunally I obtain: 
 
 SIOCS=
IFADDR: No such device 
 bnep0: unknown interface: No such device 
 SIO=
CSIFBRDADDR: No such device 
 bnep0: unknown interface: No such device =0D
=
 SIOCSIFNETMASK: No such device 
 
 Can someone tell me what is wrong? =
Thanks. 
 Jers 
 =0A=0A=0A=0A__________________________________________=
__________________=0ARegala e regalati Libero ADSL: 3 mesi gratis e navig=
hi veloce. 1.2 Mega di musica, film, video e sport. =0AAbbonati subito se=
nza costi di attivazione su http://www.libero.it=0A=0A



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2004-12-21 11:02 UTC|newest]

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

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='I92JZQ$4438CF5CD46EDB224256583706BE5074@libero.it' \
    --to=jers@inwind.it \
    --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