From: Marcel Holtmann <marcel@holtmann.org>
To: "Fredrik Hallgårde" <fredrik@libcon.net>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Anyone using a NEC e606 and BlueZ?
Date: 16 Sep 2003 13:13:16 +0200 [thread overview]
Message-ID: <1063710802.22723.18.camel@pegasus> (raw)
In-Reply-To: <3F66141E.6050201@libcon.net>
Hi Fredrik,
> I have serious problems keeping the ppp-connection via bluetooth.
> The system is as follows:
> mh3-patched Linux 2.4.21
> IOGEAR GBU-301 (USB BC2033)
> NEC e606 (3G/UMTS) Mobile
>
> Using bluefw I get hci0 working.
> Binding with rfcomm works.
> I connect with rp3-config (RedHat ppp-dialer config)
> the connection comes up, setting routing etc.
> after a few moments (10-30 sec) te connection dies.
>
> After that the bluetooth device seems stop working...
first, give us some infos about your devices.
hciconfig -a
hcitool info <nec-e606-addr>
sdptool browse --tree <nec-e606-addr>
> Any ideas? Any part of BlueZ kernelpatches I must have? (I think I
> didn't put i zero-packets) Should I post any specific dumps/logfiles?
Using 2.4.22-mh1 should be fine. A "hcidump -w <file>" and the pppd logs
will maybe help.
Have your tried other programs like "attest" from bluez-utils/test/
directory to verify that some stuff is working.
What is your data layer? GPRS? Do have special AT commands for the PPP
setting?
What happens if you use "rfcomm connect ..."? Is the RFCOMM connection
also closed or did only the PPP part dies.
Regards
Marcel
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2003-09-16 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 19:33 [Bluez-users] Anyone using a NEC e606 and BlueZ? Fredrik Hallgårde
2003-09-16 11:13 ` 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=1063710802.22723.18.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=fredrik@libcon.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.