From: Dave Henriksen <dhenriksen@optibrand.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] pand Connection refused(111) when connecting to a Belkin NAP
Date: Wed, 21 Jan 2004 12:48:59 -0800 [thread overview]
Message-ID: <1074718139.2978.7.camel@linux.local> (raw)
Hi,
I'm wondering what may be causing a "Connection refused(111)" message
when I issue a "pand --connect 00:02:72:00:DC:F1" command to connect to
a Belkin NAP. The proper pins are setup, and I can l2ping the NAP, I
just can't get pand to connect to it. Any help would be greatly
appreciated. I know that when I do networking through this NAP on the
Windows side, I need to specify and id/password combination in addition
to a pin. I'm not sure how to do this in Linux.
Thanks,
Dave H
log info:
Jan 21 11:28:51 linux pand[2711]: PAN daemon ver 1.1
Jan 21 11:28:51 linux pand[2711]: Connecting to 00:02:72:00:DC:F1
Jan 21 11:28:53 linux hcid[2690]:
link_key_request(sba=00:0D:88:AC:BE:C5, dba=0 0:02:72:00:DC:F1)
Jan 21 11:28:54 linux pand[2711]: Connect to 00:02:72:00:DC:F1 failed.
Connection refused(111)
-------------------------------------------------------
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
next reply other threads:[~2004-01-21 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 20:48 Dave Henriksen [this message]
2004-01-21 19:56 ` [Bluez-devel] pand Connection refused(111) when connecting to a Belkin NAP Marcel Holtmann
[not found] ` <1074719150.2980.9.camel@linux.local>
2004-01-21 20:14 ` Marcel Holtmann
-- 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=1074718139.2978.7.camel@linux.local \
--to=dhenriksen@optibrand.com \
--cc=bluez-devel@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