public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users]  Again dund
Date: Mon, 08 Nov 2004 19:38:29 +0100	[thread overview]
Message-ID: <1099939109.29330.17.camel@pegasus> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAosiAEZOtxUiHqgChZUVmh8KAAAAQAAAAT2mvzXDViU6RxBXLMLKoFgEAAAAA@t-online.de>

Hi Peter,

> I'm not yet able to tell linux, that my bluetooth-connection is a
> ethernet-connection. I have no idea how to manage this with PPP. With YaST I
> tried to define the bt-connection as a networkcard - but it doesn't realy
> work.

I don't get your point. The ppp0 interface can be used and when the
routing information are right then this works. It is not different from
dialin with a modem.

> Linux-Notebook:~ # sdptool search --bdaddr 00:0B:CE:00:01:8F lan
> Searching for lan on 00:0B:CE:00:01:8F ...
> Service Name: Netzwerkzugang
> Service RecHandle: 0x10000
> Service Class ID List:
>   "LAN Access Using PPP" (0x1102)
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 1
> Language Base Attr List:
>   code_ISO639: 0x656e
>   encoding:    0x6a
>   base_offset: 0x100
> 
> What can I do - ? - perhaps I have to install SuSE 9.2 ??!

The SuSE 9.2 will improve things, because the kernel, libs and utils are
up to date. However I don't know if that is the problem here. You should
remember that "LAN access using PPP" is deprecated and this stuff is all
PPP related. Look on the internet for more information.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users/listinfo/bluez-users

  reply	other threads:[~2004-11-08 18:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-04 10:22 [Bluez-users] Network Access Point - pairing problem D.W.
2004-11-04 11:05 ` Marcel Holtmann
2004-11-04 13:43   ` Jouni.Lohikoski@iki.fi
2004-11-04 14:22     ` Marcel Holtmann
2004-11-05 14:00       ` [Bluez-users] AW: Re: Again dund Peter K. Martin
2004-11-05 14:27         ` Marcel Holtmann
2004-11-05 17:46           ` AW: [Bluez-users] " Peter K. Martin
2004-11-05 20:18             ` Marcel Holtmann
2004-11-08  8:50               ` AW: " Peter K. Martin
2004-11-08 11:29                 ` Marcel Holtmann
2004-11-08 14:37                   ` AW: " Peter K. Martin
2004-11-08 14:54                     ` Marcel Holtmann
2004-11-08 18:09                       ` AW: " Peter K. Martin
2004-11-08 18:38                         ` Marcel Holtmann [this message]
2004-11-09  9:01                           ` Peter K. Martin
2004-11-04 12:59 ` [Bluez-users] Network Access Point - pairing problem D.W.
2004-11-04 13:36   ` 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=1099939109.29330.17.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