From: "Claudio Takahasi" <cktakahasi@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] pand Connection failed. Permission denied(13) BlueZ 3.28
Date: Thu, 3 Apr 2008 19:23:56 -0300 [thread overview]
Message-ID: <e1effdeb0804031523h16862892x3de16fab5cc0c257@mail.gmail.com> (raw)
In-Reply-To: <47F4D47A.1070107@kameleon-media.com>
[-- Attachment #1: Type: text/plain, Size: 4149 bytes --]
On Thu, Apr 3, 2008 at 9:58 AM, Laurent BARBIER
<lbarbier@kameleon-media.com> wrote:
> root ?
>
> 李田 a écrit :
>
>
> > Hello,guys:
> >
> > I use the newest 3.28 version of BlueZ and two bluetooth devices to
> > setup the PAN network on two different Linux box.
> >
> > the SERVER side running dbus-daemon,hcid and pand daemon like that:
> >
> > 8180 ? Ss 0:00 /sbin/hcid -s -f /etc/bluetooth/hcid.conf
> > 8183 ? S 0:00 /lib/bluetooth/bluetoothd-service-input
> > 8184 ? S 0:00 /lib/bluetooth/bluetoothd-service-network
> > 8185 ? S 0:00 /lib/bluetooth/bluetoothd-service-serial
> > 8189 ? Ss 0:00 pand --listen --master --role NAP --ethernet bnep0
> > --device 00:A0:B0:E0:48:25
> >
> >
> > and then,the CLIENT side run in a simple way like this:
> > pand --connect 00:A0:B0:E0:48:25
> >
> > the ERROR is : pand[8191]: Connection failed. Permission denied(13)
> >
> > the sys LOG is list below:
> >
> > Apr 3 17:15:05 bip313 hcid[8180]: Bluetooth HCI daemon
> > Apr 3 17:15:05 bip313 hcid[8180]: HCI dev 0 registered
> > Apr 3 17:15:05 bip313 hcid[8180]: HCI dev 0 already up
> > Apr 3 17:15:05 bip313 hcid[8180]: Device hci0 has been added
> > Apr 3 17:15:05 bip313 hcid[8180]: Starting security manager 0
> > Apr 3 17:15:05 bip313 hcid[8180]: Device hci0 has been activated
> > Apr 3 17:15:05 bip313 hcid[8180]: Starting SDP server
> > Apr 3 17:15:05 bip313 hcid[8180]: Created local server at
> > unix:abstract=/var/run/dbus-BBAibFkMvI,guid=a5abffc66b1d327133d76e3847f49209
> > Apr 3 17:15:05 bip313 input[8183]: Bluetooth Input daemon
> > Apr 3 17:15:05 bip313 input[8183]: Registered input manager
> > path:/org/bluez/input
> > Apr 3 17:15:05 bip313 network[8184]: Bluetooth Network daemon
> > Apr 3 17:15:05 bip313 serial[8185]: Bluetooth Serial Port daemon
> > Apr 3 17:15:05 bip313 serial[8185]: Registered manager
> > path:/org/bluez/serial
> > Apr 3 17:15:05 bip313 network[8184]: Registered manager
> > path:/org/bluez/network
> > Apr 3 17:15:05 bip313 network[8184]: Registered server
> > path:/org/bluez/network/nap
> > Apr 3 17:15:05 bip313 network[8184]: Registered server
> > path:/org/bluez/network/gn
> > Apr 3 17:15:05 bip313 network[8184]: Registered server
> > path:/org/bluez/network/panu
> > Apr 3 17:17:33 bip313 pand[8189]: Bluetooth PAN daemon version 3.28
> > Apr 3 17:18:16 bip313 pand[8191]: Connection failed. Permission denied(13)
> >
> > Please give me some idea, or I'm going to look into the souce code of
> > bnep_accept_connection to try to find what has happened.
> >
> > Thanks ,everyone.
> >
> > ------------------------------------------------------------------------
> >
> > -------------------------------------------------------------------------
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Bluez-users mailing list
> > Bluez-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-users
> >
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
Hi leetand,
Another comment, try use the network service. You can find a HOWTO at:
http://wiki.bluez.org/wiki/HOWTO/NetworkConnections
You can't run pand and the network service at same time if you have a
server enabled.
Regards,
Claudio.
--
---------------------------------------------------------
Claudio Takahasi (krau)
Instituto Nokia de Tecnologia - INdT
jabber: claudio.takahasi@gmail.com
Mobile: +55 81 88864779
[-- Attachment #2: Type: text/plain, Size: 278 bytes --]
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2008-04-03 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 8:32 [Bluez-users] pand Connection failed. Permission denied(13) BlueZ 3.28 李田
2008-04-03 12:58 ` Laurent BARBIER
2008-04-03 22:23 ` Claudio Takahasi [this message]
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=e1effdeb0804031523h16862892x3de16fab5cc0c257@mail.gmail.com \
--to=cktakahasi@gmail.com \
--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