All of lore.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: Tue, 11 Jan 2005 13:06:48 +0100	[thread overview]
Message-ID: <1105445208.8056.17.camel@pegasus> (raw)
In-Reply-To: <IA5EZL$515602A938C639AD7C0D84FB93EBFF70@libero.it>

Hi Jers,

> I'm still trying to create a simple piconet with a master and two slaves. I upgrated my bluez and, on your website, I red the firmware of my dongles (Digicom Palladio CSR) is fit for my aims.
> Now the situation is as follows:
> 
> On the three sides I type
> 
> # modprobe bnep
> 
> On the master side:
> 
> # brctl addbr pan0
> # ifconfig pan0 10.0.0.1
> # brctl setfd pan0 0
> # brctl stp pan0 off
> # pand  --listen --master --role GN
> 
> On the slave1 side:
> # pand --connect <master bt_addr>
> # ifconfig bnep0 10.0.0.2
> 
> In most cases I obtain the following error:
> 
> SIOCSIFADDR: No such device
> bnep0: unknown interface: No such device
> 
> even if the command
> #hcitool con
> shows me an active connection.
> 
> When I obtain the connection I continue:
> 
> On the slave1 side:
> # route add default gw 10.0.0.1
> 
> On the master side:
> # brctl addif pan0 bnep0
> # ifconfigt bnep0 0.0.0.0
> 
> On the slave2 side:
> # pand --connect <master bt_addr>
> # ifconfig bnep0 10.0.0.3
> 
> and I always obtain the same error:
> 
> SIOCSIFADDR: No such device
> bnep0: unknown interface: No such device
> 
> even if the command
> #hcitool con
> shows me an active connection.
> 
> You pointed me out there is no link policy set  but  my file /etc/Bluetooth/hcid.conf is:
> 
> # Default settings for HCI devices
> device {
> 	# Local device name
> 	#   %d - device id
> 	#   %h - host name
> 	name "BlueZ (%d)";
> 
> 	# Local device class
> 	class 0x3e0100;
> 
> 	# Default packet type
> 	#pkt_type DH1,DM1,HV1;
> 
> 	# Inquiry and Page scan
> 	iscan enable; pscan enable;
> 
> 	# Default link mode
> 	#   none   - no specific policy 
> 	#   accept - always accept incoming connections
> 	#   master - become master on incoming connections,
> 	#            deny role switch on outgoing connections
> 	#
> 	lm accept,master;
> 	#
> 	#lm accept;

you changed this. Why? There can't be two device with a master role in
the same a piconet.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2005-01-11 12:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 10:40 [Bluez-users] Piconet problems jers
2005-01-11 10:52 ` Benoit Panizzon
2005-01-11 12:06 ` 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-20 11:33 jers
2005-01-20 12:52 ` 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
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=1105445208.8056.17.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 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.