All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Dave Henriksen <dhenriksen@optibrand.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] pand Connection refused(111) when connecting to a Belkin NAP
Date: Wed, 21 Jan 2004 21:14:22 +0100	[thread overview]
Message-ID: <1074716061.7263.37.camel@pegasus> (raw)
In-Reply-To: <1074719150.2980.9.camel@linux.local>

Hi Dave,

> Here is the file from the hcidump.

	> ACL data: handle 0x0029 flags 0x02 dlen 16
	    L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0040 result 2 status 0

The result code 2 means "Connection refused - PSM not supported". Are
you sure this AP supports the PAN Profile. Try using dund instead.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2004-01-21 20:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 20:48 [Bluez-devel] pand Connection refused(111) when connecting to a Belkin NAP Dave Henriksen
2004-01-21 19:56 ` Marcel Holtmann
     [not found]   ` <1074719150.2980.9.camel@linux.local>
2004-01-21 20:14     ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-08 23:42 lta
2005-02-09  0:13 ` Marcel Holtmann
     [not found]   ` <420F483D.20802@creativemonsters.com>
2005-02-22  0:15     ` 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=1074716061.7263.37.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=dhenriksen@optibrand.com \
    /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.