public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Florian <Kimpenhaus@gmx.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl
Date: Fri, 27 Feb 2004 16:30:48 +0100	[thread overview]
Message-ID: <1077895848.2843.50.camel@pegasus> (raw)
In-Reply-To: <opr31ccpcoqdj9uv@mail.gmx.de>

Hi Florian,

> This is how far I get at the moment but I do not know how to
> configure the ppp connection to authenticate my system.
> 
> bash-2.05b# dund --nodetach --connect 00:0B:CE:00:01:8E --msdun
> dund[4386]: DUN daemon ver 1.1
> dund[4386]: Searching for LAP on 00:0B:CE:00:01:8E
> dund[4386]: Connecting to 00:0B:CE:00:01:8E channel 1
> dund[4386]: Connection established
> bash-2.05b# Using interface ppp0
> Connect: ppp0 <--> /dev/rfcomm0
> LCP terminated by peer (peer refused to authenticate)
> Connection terminated.

you can use

	dund --nodetach --connect 00:0B:CE:00:01:8E --msdun call lap

and create a /etc/ppp/peers/lap file with your PPP settings. But that is
now up to you, because I don't know what your AP is expecting.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2004-02-27 15:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25 15:23 [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl Florian
2004-02-25 16:18 ` Marcel Holtmann
2004-02-25 18:11   ` Florian
     [not found]   ` <opr3xs5louqdj9uv@mail.gmx.de>
2004-02-25 18:42     ` Marcel Holtmann
     [not found]       ` <opr3xydd1hqdj9uv@mail.gmx.de>
2004-02-25 20:28         ` Marcel Holtmann
     [not found]           ` <opr3x23lc1qdj9uv@mail.gmx.de>
2004-02-25 22:12             ` Marcel Holtmann
     [not found]               ` <opr3x77rphqdj9uv@mail.gmx.de>
2004-02-25 23:51                 ` Marcel Holtmann
     [not found]                   ` <opr3x8uqadqdj9uv@mail.gmx.de>
2004-02-26  0:58                     ` Marcel Holtmann
     [not found]                       ` <opr3yb4dsoqdj9uv@mail.gmx.de>
2004-02-26  1:18                         ` Marcel Holtmann
     [not found]                           ` <opr3y5uonaqdj9uv@mail.gmx.de>
2004-02-26 13:25                             ` Marcel Holtmann
     [not found]                           ` <opr31ccpcoqdj9uv@mail.gmx.de>
2004-02-27 15:30                             ` Marcel Holtmann [this message]
     [not found]                               ` <opr4anrqloqdj9uv@mail.gmx.de>
2004-03-03 17:24                                 ` Marcel Holtmann

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=1077895848.2843.50.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=Kimpenhaus@gmx.de \
    --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