From: "Peter B. West" <lists@pbw.id.au>
To: linux-hotplug@vger.kernel.org
Subject: Re: Advice on setting up USB ADSL modem
Date: Mon, 27 Jun 2005 00:07:44 +0000 [thread overview]
Message-ID: <42BF4350.90806@pbw.id.au> (raw)
In-Reply-To: <42BE0973.6000806@pbw.id.au>
Kay Sievers wrote:
> On Sun, Jun 26, 2005 at 11:48:35AM +1000, Peter B. West wrote:
>
>>I hope this it the right place to ask this question; my apologies if not.
>>
>>I have a USB ADSL modem which is currently running on a desktop system.
>> The modem uses the Nortek development version of the eciadsl driver.
>>It took me a while to get it working about 12 months ago on an FC3
>>system, and I currently use it by calling the startup script as root.
>>There are two phases to connecting. The first is to synchronize the
>>modem and create a tap interface; the second is to create a ppp link
>>using rp-pppoe. In my original script I added /sbin/ifup ppp0 after
>>tap0 was set up.
>>
>>What I would like to do on my current gentoo system is have the
>>synchronization and tap0 interface setup/pulled-down when the modem is
>>plugged/unplugged, and have an on-demand ppp0 setup using the normal
>>adsl network configuration scripts in gentoo.
>>
>>The /dev/net/tun device is, I believe, created outside the udev system.
>>
>>I am running 2.6.12-gentoo-r1, udev-058, hotplug-20040923,
>>coldplug-20040920. /proc/sys/kernel/hotplug is /sbin/udevsend.
>>
>>Should I be using udev rules to set this up?
>
>
> This will not work with the current released udev version, we are
> currently preparing something like that, but you better wait until we
> are ready with the current devel-version...
>
>
>>In either case, can you
>>point me to some documents that will explain the details. (The
>>documentation I have seen is keyed towards /dev setup and naming,
>>naturally.)
>
>
> Place a scrip in /etc/hotplug.d/usb/<name>.hotplug. You will be called
> for _every_ USB event. Check if the call is for your modem $PRODUCT and
> check $ACTION for add/remove and do whatever you need in that scipt.
Thanks Kay, that's what I needed to know. I assume that <name> is
irrelevant, with all scripts being called on every event?
Peter
--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>
<http://folio.bkbits.net/> <- the atTridged version
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2005-06-27 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 1:48 Advice on setting up USB ADSL modem Peter B. West
2005-06-26 18:14 ` Kay Sievers
2005-06-27 0:07 ` Peter B. West [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=42BF4350.90806@pbw.id.au \
--to=lists@pbw.id.au \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).