From: Marcel Holtmann <marcel@holtmann.org>
To: Stephan Cremer <cremer.stephan@web.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] rfcomm device disappears
Date: Thu, 10 Jun 2004 12:28:02 +0200 [thread overview]
Message-ID: <1086863282.1607.41.camel@pegasus> (raw)
In-Reply-To: <540644453@web.de>
Hi Stephan,
> I have been observing a strange and reproduceable problem trying
> to setup a PPP server for my Nokia 3650. Briefly, the scenario is
> as follows:
>
> First, a serial Port is registered: "sdptool add --channel=2 SP"
> After that, dund is started and waits for incoming PPP requests:
> "dund -n --listen --channel=2 call dun"
> When an application - e.g. a web browswer is started on the phone,
> using a bluetooth access point configured via gnubox, the PPP link
> is fired up and the app works perfectly.
>
> Unfortunately, this works excactly once, because for some reason,
> the rfcomm device that was used for the PPP link disappears, which
> on the connection request makes dund complain
> "RFCOMM TTY creation failed. No such file or directory(2)" - I
> tried to (re-)create the device in /etc/ppp/ip-down but no avail...
>
> Here is the output of "hcidump -x" starting right before the
> application is closed on the phone:
>
> ---------- snip -----------
> HCIDump - HCI packet analyzer ver 1.5 device: hci0 snap_len: 1028
> filter: 0xffffffff > ACL data: handle 0x0029 flags 0x02 dlen 20
> L2CAP(d): cid 0x41 len 16 [psm 0]
> 13 EF 19 7E FF 03 C0 21 05 03 00 04 85 72 7E 65 < ACL data:
> handle 0x0029 flags 0x02 dlen 25
> L2CAP(d): cid 0x59 len 21 [psm 0]
> 11 EF 23 7E FF 7D 23 C0 21 7D 26 7D 23 7D 20 7D 24 48 57 7E
> BF > HCI Event: Number of Completed Packets(0x13) plen 5
> 01 29 00 01 00 < ACL data: handle 0x0029 flags 0x02 dlen 8
> L2CAP(d): cid 0x59 len 4 [psm 0]
> 11 53 01 16 > HCI Event: Number of Completed Packets(0x13)
> plen 5
> 01 29 00 01 00 > ACL data: handle 0x0029 flags 0x02 dlen 8
> L2CAP(d): cid 0x41 len 4 [psm 0]
> 11 73 01 3C > ACL data: handle 0x0029 flags 0x02 dlen 12
> L2CAP(s): Disconn req: dcid 0x0041 scid 0x0059 < ACL data:
> handle 0x0029 flags 0x02 dlen 12
> L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0059 > HCI Event:
> Number of Completed Packets(0x13) plen 5
> 01 29 00 01 00
> ---------- snip -----------
>
>
> And here are some notes on my configuration:
>
> - Gentoo Linux, Kernel 2.6.6 / patch-2.6.6-mh3.gz
> - Epox bt-dg02a USB BT dongle
> - bluez: kernel 2.3, libs 2.5, pan 1.1, sdp 1.5, utils 2.3-r1, hcidump 1.5
first don't use kernel-2.3, because you use 2.6.6-mh3. Second uninstall
the other tools and install the latest versions of it. Make use of udev
and everything should be fine.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-06-10 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 22:03 [Bluez-users] rfcomm device disappears Stephan Cremer
2004-06-10 10:28 ` Marcel Holtmann [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=1086863282.1607.41.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=cremer.stephan@web.de \
/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