From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Setting up an hotplug connection with USB dongles
Date: Sun, 02 Jan 2005 14:58:17 +0100 [thread overview]
Message-ID: <1104674297.8894.3.camel@pegasus> (raw)
In-Reply-To: <200501021451.09711.rdorsch@web.de>
Hi Rainer,
> > add a line with "auto bnep0" and it will bring up your interface when it
> > is available.
>
> From man interfaces
>
> Stanzas beginning with the word "auto" are used to identify the physical
> interfaces to be brought up when ifup is run with the -a option. (This
> option is used by the system boot scripts.) Physical interface names
> should follow the word "auto" on the same line. There can be multiple
> "auto" stanzas. ifup brings the named interfaces up in the order listed.
>
> From the ifup manpage
>
> -a, --all
> If given to ifup, affect all interfaces marked auto. Interfaces
> are brought up in the order in which they are defined in /etc/net-
> work/interfaces. If given to ifdown, affect all interfaces.
> Interfaces are brought down in the order in which they are currently listed
> in the state file.
if you use "auto bnep0" and hotplug is configured to deal also with the
network interface then bnep0 will be brought up at the time the kernel
created it. No need to run ifup/ifdown manually.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-01-02 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 20:32 [Bluez-users] Setting up an hotplug connection with USB dongles Rainer Dorsch
2004-11-29 1:38 ` Marcel Holtmann
2004-11-29 15:05 ` Erwin Authried
2004-12-19 22:23 ` Rainer Dorsch
2004-12-19 22:28 ` Marcel Holtmann
2004-12-23 22:43 ` Rainer Dorsch
2004-12-24 12:04 ` Marcel Holtmann
2005-01-02 13:51 ` Rainer Dorsch
2005-01-02 13:58 ` Marcel Holtmann [this message]
2005-01-02 17:37 ` Rainer Dorsch
2005-01-02 17:41 ` Marcel Holtmann
2005-01-03 10:14 ` Rainer Dorsch
2005-01-03 10:42 ` Rainer Dorsch
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=1104674297.8894.3.camel@pegasus \
--to=marcel@holtmann.org \
--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