Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Problem with dund and LG 325 phone.
Date: Thu, 26 May 2005 23:43:04 +0200	[thread overview]
Message-ID: <1117143784.12036.78.camel@pegasus> (raw)
In-Reply-To: <42962705.9010902@fnal.gov>

Hi Eric,

> I have an LG PM-325 which I am trying to get DUN working with. It works under
> Windows, but I want to use linux.
> 
> I think the two devices are paired since I can do l2ping and get responses,
> but I still seem to be a few steps away from being able to do DUN.
> 
> When I type this, I expect to get a success message back, right? Instead I get 
> nothing:
> 
> [root@a122077 root]# dund -c 08:00:37:13:A1:C7 -n
> dund[5586]: Bluetooth DUN daemon
> dund[5586]: Searching for LAP on 08:00:37:13:A1:C7
> [root@a122077 root]#
> 
> I don't have to do anything with rfcomm before this, right? I also don't need 
> to run pand, right, since my device only supports DUN.
> 
> When I try to do a pppd call command, I get this in syslog:
> May 26 14:43:02 a122077 kernel: PPP generic driver version 2.4.2
> May 26 14:43:02 a122077 pppd[5708]: pppd 2.4.3 started by root, uid 0
> May 26 14:43:03 a122077 hcid[3602]: link_key_request (sba=00:10:60:AA:5C:CE, 
> dba=08:00:37:13:A1:C7)
> May 26 14:43:03 a122077 pppd[5708]: Failed to open /dev/rfcomm0: Connection 
> refused
> May 26 14:43:03 a122077 pppd[5708]: Exit.
> 
> which isn't surprising.

using dund for Dialup-Networking is the wrong way. The dund is for LAN
access using PPP. And yes, I know that the name is confusing.

What you need is to find the RFCOMM channel number for Dialup-Networking
with the help of

	sdptool search --bdaddr <bdaddr> dun

and then you bind a RFCOMM TTY port to that channel with

	rfcomm bind 0 <bdaddr> <channel>

After that you can use any dialer (for example wvdial) to setup your
dialup connection through /dev/rfcomm0.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-05-26 21:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 19:44 [Bluez-users] Problem with dund and LG 325 phone Eric Vaandering
2005-05-26 21:43 ` Marcel Holtmann [this message]
2005-05-27  1:44   ` Eric Vaandering
2005-05-27  7:07     ` Marcel Holtmann
2005-05-27 15:04       ` Eric Vaandering
2005-06-10  2:25         ` John H.
2005-06-10  5:04       ` [Bluez-users] download link for bluez-pin is broken John H.
2005-06-10  5:34         ` Marcel Holtmann
2005-06-10  5:38           ` John H.
2005-06-10  5:57         ` [Bluez-users] hcid error on pair attempt John H.
2005-06-14 10:05       ` [Bluez-users] Problem with dund and LG 325 phone-fixed John H.
2005-06-15 21:28   ` [Bluez-users] Problem with dund and LG 325 phone John H.
  -- strict thread matches above, loose matches on Subject: below --
2005-05-27  8:41 John H.

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=1117143784.12036.78.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox