All of lore.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] Re: Toshiba and BT (SuSE 9.2)
Date: Tue, 14 Dec 2004 11:32:05 +0100	[thread overview]
Message-ID: <1103020326.2143.148.camel@pegasus> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAosiAEZOtxUiHqgChZUVmh8KAAAAQAAAAB+zXWiodQU+C/XbHBBtz8gEAAAAA@t-online.de>

Hi Peter,

> ##>maybe it is not a good idea to configure bnep0 with YaST at 
> ##>the moment and actually I never tried this. If your AP is 
> ##>configured in router mode then you should simply run "pand 
> ##>-n -c <bdadd>" and then "dhcpcd bnep0".
> 
> and here is the result
> 
> Linux-Notebook:~ # hcitool scan
> Scanning ...
>         00:0B:CE:00:01:8F       Bluetooth-Modul
> Linux-Notebook:~ # pand -n -c 00:0B:CE:00:01:8F
> pand[8102]: Bluetooth PAN daemon
> pand[8102]: Connecting to 00:0B:CE:00:01:8F
> pand[8102]: Connect to 00:0B:CE:00:01:8F failed. Connection refused(111)
> Linux-Notebook:~ #
> 
> What means this, espacially refused(111)?

in most cases this is PIN or link key problem. Check with "hcidump -x"
to be sure.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-12-14 10:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13 19:00 Toshiba and BT (SuSE 9.2) Peter K. Martin
2004-12-13 20:03 ` [Bluez-users] " Marcel Holtmann
2004-12-14 10:28   ` AW: " Peter K. Martin
2004-12-14 10:32     ` Marcel Holtmann [this message]
2004-12-14 10:59       ` Peter K. Martin
2004-12-14 11:09         ` Marcel Holtmann
2004-12-14 11:37           ` AW: " Peter K. Martin
2004-12-14 11:47             ` Marcel Holtmann
2004-12-14 13:39               ` AW: " Peter K. Martin
2004-12-15 10:46                 ` Marcel Holtmann
2004-12-15 11:08                   ` AW: " Peter K. Martin
2004-12-15 11:13                     ` Marcel Holtmann
2004-12-15 12:37                       ` AW: " Peter K. Martin
2004-12-15 13:44                         ` Marcel Holtmann
2004-12-15 15:58                           ` AW: " Peter K. Martin
2004-12-15 17:05                           ` Peter K. Martin
2004-12-15 17:28                             ` Marcel Holtmann
2004-12-16 10:49                               ` AW: [Bluez-users] " Peter K. Martin
2004-12-16 11:09                                 ` Marcel Holtmann
2004-12-16 14:21                                   ` AW: " Peter K. Martin
2004-12-16 19:53                                     ` Marcel Holtmann
2004-12-17 10:04                                       ` AW: " Peter K. Martin
2004-12-17 14:47                                         ` Marcel Holtmann
2004-12-15  8:33               ` AW: [Bluez-users] " Peter K. Martin
2004-12-15 10:48                 ` 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=1103020326.2143.148.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 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.