All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anderson Rodrigues <rodrigues.anderson@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] creating the bnep0 device
Date: Mon, 28 Mar 2005 08:51:41 -0800	[thread overview]
Message-ID: <d1f423d3050328085166da3261@mail.gmail.com> (raw)
In-Reply-To: <1112006473.9016.0.camel@pegasus>

Hi Jonathan,


As Marcel has menssioned you should connect the devices using PAND
first. When the connection is ok the bnep0 is created automatically by
PAND. Ex:

GN side

pand --listen --role GN

PANU side:
pand --connect <bdaddr> --role PANU

If everything got OK you can apply an IP address at both sides

GN side:
#ifconfig bnep0 10.0.0.1

PANU side:
#ifconfig bnep0 10.0.0.2

so you can try ping one of these addresses 

hope it helps.

all the best

On Mon, 28 Mar 2005 12:41:13 +0200, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Jonathan,
> 
> > I have a pretty remedial question involving setting up bluettoth in
> > Linux, but I don't think that I've seen any answers in the documentation
> > or mailing list.
> >
> > I'm using kernel 2.6.11 with a LinkSys USBBT100 adaptor.  The adaptor
> > can scan and ping other bluetooth devices with l2ping, but I'm having
> > problems getting bnep0 recognized as a network interface.
> >
> > ifconfig bnep0 returns
> > bnep0: error fetching interface information: Device not found
> >
> > The fedora utility sees bnep0, but cannot activate it and returns
> > SIOCGIFFLAGS: No such device
> > when I try to deactivate it.
> >
> > I get the same results when I use bluez/benp compiled into the kernel or
> > loading them as modules.  /var/log/messages has the bluetooth messages:
> > Mar 27 12:30:11 ma-jbredin kernel: Bluetooth: L2CAP ver 2.7
> > Mar 27 12:30:11 ma-jbredin kernel: Bluetooth: L2CAP socket layer initialized
> > Mar 27 12:30:11 ma-jbredin kernel: Bluetooth: RFCOMM ver 1.5
> > Mar 27 12:30:11 ma-jbredin kernel: Bluetooth: RFCOMM socket layer
> > initialized
> > Mar 27 12:30:11 ma-jbredin kernel: Bluetooth: RFCOMM TTY layer initialized
> > Mar 27 12:30:11 ma-jbredin kernel: Bluetooth: BNEP (Ethernet Emulation)
> > ver 1.2
> > Mar 27 12:30:11 ma-jbredin kernel: Bluetooth: BNEP filters: protocol
> > multicast
> > Mar 27 12:30:11 ma-jbredin kernel: Bluetooth: HIDP (Human Interface
> > Emulation) ver 1.1
> >
> > Does anyone have suggestions to get bnep0 off the ground?
> 
> what about using "pand --connect" before you try to use "ifconfig".
> 
> 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
> 


-- 
Anderson Clayton B. Rodrigues
Eng. de Software
Instituto Nokia de Tecnologia - INdT


-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-03-28 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28  3:57 [Bluez-users] creating the bnep0 device Jonathan Bredin
2005-03-28 10:41 ` Marcel Holtmann
2005-03-28 16:51   ` Anderson Rodrigues [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=d1f423d3050328085166da3261@mail.gmail.com \
    --to=rodrigues.anderson@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 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.