public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michał Majchrowicz" <mmajchrowicz@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Fwd:  Problem with PAN. Bnep doesn't work ?
Date: Tue, 27 Feb 2007 22:54:07 +0100	[thread overview]
Message-ID: <3d3168e50702271354k38405a87kb464eff0ccabfa5e@mail.gmail.com> (raw)
In-Reply-To: <3d3168e50702271202i719f1f7fjd2fb22b105f951f8@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1582 bytes --]

---------- Forwarded message ----------
From: Michał Majchrowicz <mmajchrowicz@gmail.com>
Date: 2007-02-27 21:02
Subject: Re: [Bluez-users] Problem with PAN. Bnep doesn't work ?
To: "robert@infotility.com" <robert@infotility.com>

There is no error in /var/log/messages
l2ping MAC addres of machine works
hcitool scan works perfecly
sdptool browse show this:
Browsing 66:55:44:33:22:11 ...
Service Name: Network Access Point
Service RecHandle: 0x10000
Service Class ID List:
  "Network Access Point" (0x1116)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 15
  "BNEP" (0x000f)
    Version: 0x0100
    SEQ16: 800 806
Profile Descriptor List:
  "Network Access Point" (0x1116)
    Version: 0x0100
As I said before. There is no indication of error, but there has to be some
error :(
Regards Michael.

2007/2/27, robert@infotility.com <robert@infotility.com>:
>
> Quoting Micha³ Majchrowicz <mmajchrowicz@gmail.com>:
>
> > Hi I have a problem with PAN.
> > I have succesfully configured pand connection
> > on sever:
> >  pand -l
> > bnep0 11:22:33:44:55:66 NAP
> > on client:
> > pand -l
> > bnep0 66:55:44:33:22:11 NAP
> > where 66:55.... is MAC of server and 11:22.... is MAC of client.
>
> Michael, the problem could be any one of a number of things...
> To help with tracking down the source of the error, try these programs:
> sdptool browse
> l2ping xx.xx.xx.xx
> hcitool scan
>
> should all show something.
> Also try tail -f /var/log/messages
> to see if the kernel writes something there.
>
> Sorry I can't be more helpful. Let us know how it goes.
>
> Robert Dodier
>

[-- Attachment #1.2: Type: text/html, Size: 2697 bytes --]

[-- Attachment #2: Type: text/plain, Size: 345 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      parent reply	other threads:[~2007-02-27 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 16:53 [Bluez-users] Problem with PAN. Bnep doesn't work ? Michał Majchrowicz
2007-02-27 19:22 ` robert
     [not found]   ` <3d3168e50702271202i719f1f7fjd2fb22b105f951f8@mail.gmail.com>
2007-02-27 21:54     ` Michał Majchrowicz [this message]

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=3d3168e50702271354k38405a87kb464eff0ccabfa5e@mail.gmail.com \
    --to=mmajchrowicz@gmail.com \
    --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