All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Till Harbaum <harbaum@beecon.de>
Cc: "Williams, Richard" <Richard.Williams@VITRONICS.com>,
	blookk - <blookk@hotmail.com>,
	bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] PAN profile of bluetooth
Date: Mon, 30 Aug 2004 18:08:30 +0200	[thread overview]
Message-ID: <1093882109.5620.89.camel@pegasus> (raw)
In-Reply-To: <200408301756.14723.harbaum@beecon.de>

Hi Till,

> > Did you make sure the /etc/bluetooth/pan/dev-up file is correct and present
> > on both your devices, master and slave ? If this file isn't there, you
> > won't get the bnep process started.
> Are you sure? I never heard of that file, but have successfully been using 
> bnep without even having a /etc/bluetooth/pan directory on my pc.

this depends on your system. Actually on every new system that uses
hotplug, there is no need for using dev-up. The bnep0 is like every
other network card in your machine and hotplug takes care of it.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-08-30 16:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 15:51 [Bluez-devel] PAN profile of bluetooth Williams, Richard
2004-08-30 15:56 ` Till Harbaum
2004-08-30 16:08   ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-06 14:59 blookk -
2004-08-30 15:18 blookk -
2004-08-30 15:34 ` Marcel Holtmann
2004-08-30 15:45 ` GUILLON Gabriel
2004-08-30 16:49   ` Marcel Holtmann
2004-08-30 11:19 blookk -
2004-08-30 11:30 ` 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=1093882109.5620.89.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=Richard.Williams@VITRONICS.com \
    --cc=blookk@hotmail.com \
    --cc=bluez-devel@lists.sf.net \
    --cc=harbaum@beecon.de \
    /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.