All of lore.kernel.org
 help / color / mirror / Atom feed
From: "D.W." <sword@gmx.de>
To: <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Network Access Point - pairing problem
Date: Wed, 3 Nov 2004 20:24:12 +0100	[thread overview]
Message-ID: <002901c4c1da$b4d3fec0$0300a8c0@supercomputer> (raw)

[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]

Hi Marcel,
Thank you for your reply.
I use kernel 2.4.22 on an axis devboard82. The bluez stack is not the latest(PAN, SDP, utils, libs are still seperate packages), because I had problems porting later versions to the devboard.
But except the pairing problem at first contact it works perfectly.
Except the PIN (it's a static one at server side) there is no further authentification necessary.
Security mode 2 or 3? What do you mean? Can I check it?
When I try to connect to the server at first contact, I have to enter the PIN(client side) and after entering the right pin I get the message :"Authentification failed." 
Regards Daniel


 
> Hi Daniel,
> 
> > I want to use bluez for a standalone network access point. All works
> > fine(pand or dund), the thing is that the pairing doesn't work at
> > first contact (client is a windows-pc). 
> > 
> > So I have to establish a rfcomm-connection manually(from the server
> > side rfcomm connect 0 btad) first. This pairing works,  I disconnect
> > and then I am able to connect the client to the NAT.
> > 
> > Does anybody know what's wrong and what I can do to make the pairing
> > work without this manually initiated rfcomm-connnection ?
> 
> are we talking about security mode 2 or security mode 3? What kernel do
> you use?
> 
> Regards
> 
> Marcel
> 
> 

[-- Attachment #2: Type: text/html, Size: 2350 bytes --]

             reply	other threads:[~2004-11-03 19:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 19:24 D.W. [this message]
2004-11-03 20:15 ` [Bluez-users] Network Access Point - pairing problem Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2004-11-04 10:22 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-04 12:59 ` D.W.
2004-11-04 13:36   ` Marcel Holtmann
2004-11-02 22:07 D.W.
2004-11-03  0:07 ` 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='002901c4c1da$b4d3fec0$0300a8c0@supercomputer' \
    --to=sword@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 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.