Hm,
isn't it better to keep that setup in ifconfig.iwi ?

I had it there and that worked fine.
At least that would keep things consistent (I think).
And I guess, that nfs-booting from the iwi, won't work because
thats before init.

am I wrong?

cheers thilo

Curt Sampson wrote:

This is going to the current-users list because I feel that the people
here are probably best qualified to answer this. But please cc me on
responses if you wouldn't normally, as I'm not on the list itself.

I'm consing up an rc.d script to load up the firmware for an iwi network
interface, so that dhclient can work immediately on boot. However, I need
a name for the darn thing. I'm thinking "iwisetup," but does anybody have
a better idea?

For anybody interested, I've appended a quick (and as yet entirely
untested)
sketch of the script; comments are welcome.

, I'm developing this on a 3.0_BETA system, if there's some reason
this wouldn't work on -current, can someone let me know? I can't
off-hand think of any obvious way to be able to easily switch between
netbsd-3 and current on my laptop.

cjs

Curt Sampson wrote:

Sat, 3 Dec 2005, thilo wrote:
>
>isn't it better to keep that setup in ifconfig.iwi ?
>
>
Possibly. Does this work with dhclient? (I.e., will ifconfig.iwi load
all the right stuff, and then dhclient will be able to use it?) I had
assumed you do one or the other.

I had no issues using dhclient,
/etc/rc.d/network comes first (which does the ifconfig.xxx stuft
dhcp client is later. and would ( i belive ) only modify the
mask/ip-address.

ifconfig.iwi can contain arbritary commands: (mine is:)

#Set up the iwi0 interface
!iwictl -i iwi0 -d /etc/firmware
192.168.0.99 netmask 255.255.255.0 ssid HERE nwkey
2:0x,0x,0x0,0x0 up

And even so, it might be easier for users simply to install the firmware
package and change an option in rc.conf to "yes". But maybe not that
much easier.

I do see this argument! (it did cost me some time to understand the
"firmware" load bit,
and I guess it's quite unusual )
btw. this is IMH -- so not necessary some-one elses :-(

thilo

Hello,

I'm consing up an rc.d script to load up the firmware for an iwi
network interface, so that dhclient can work immediately on boot.
However, I need a name for the darn thing. I'm thinking "iwisetup,"
but does anybody have a better idea?

Maybe, for consistency's sake, have a look what the rest of the bunch
uses ( not that there is a lot though ) - for afb-based graphics boards
( like the Sun Elite3D series ) there's afbinit which loads the firmware
image. No idea if that conforms to anything but it's the only standalone
firmware loader I can think of right now.

have fun
Michael

In article <@angelic.cynic.net>,
Curt Sampson <cjs (AT) cynic (DOT) netwrote:
>
>This is going to the current-users list because I feel that the people
>here are probably best qualified to answer this. But please cc me on
>responses if you wouldn't normally, as I'm not on the list itself.
>
>I'm consing up an rc.d script to load up the firmware for an iwi network
>interface, so that dhclient can work immediately on boot. However, I need
>a name for the darn thing. I'm thinking "iwisetup," but does anybody have
>a better idea?
>
>For anybody interested, I've appended a quick (and as yet entirely untested)
>sketch of the script; comments are welcome.
>
>, I'm developing this on a 3.0_BETA system, if there's some reason
>this wouldn't work on -current, can someone let me know? I can't
>off-hand think of any obvious way to be able to easily switch between
>netbsd-3 and current on my laptop.

I put my firmware load commands in ifconfig.iwi0.

christos

2005.12.03 18:44:26 +0900, Curt Sampson wrote:
|
| This is going to the current-users list because I feel that the people
| here are probably best qualified to answer this. But please cc me on
| responses if you wouldn't normally, as I'm not on the list itself.
|
| I'm consing up an rc.d script to load up the firmware for an iwi network
| interface, so that dhclient can work immediately on boot. However, I need
| a name for the darn thing. I'm thinking "iwisetup," but does anybody have
| a better idea?
|
| For anybody interested, I've appended a quick (and as yet entirely untested)
| sketch of the script; comments are welcome.
|
| , I'm developing this on a 3.0_BETA system, if there's some reason
| this wouldn't work on -current, can someone let me know? I can't
| off-hand think of any obvious way to be able to easily switch between
| netbsd-3 and current on my laptop.

I think that instead of creating a rc.d script for every firmware, we
should try to let the kernel do that automatically like Linux does
with hotplug. And this should work for every driver.

What do you think ?
-- Rui Paulo

PGP SIGNATURE
Version: GnuPG v1.4.2 (NetBSD)

aRZ1yhT2IbUWP9xB0fQn+9A=
=fptN
PGP SIGNATURE

Rui Paulo wrote:

2005.12.03 18:44:26 +0900, Curt Sampson wrote:
>|
>| This is going to the current-users list because I feel that the people
>| here are probably best qualified to answer this. But please cc me on
>| responses if you wouldn't normally, as I'm not on the list itself.
>|
>| I'm consing up an rc.d script to load up the firmware for an iwi network
>| interface, so that dhclient can work immediately on boot. However, I need
>| a name for the darn thing. I'm thinking "iwisetup," but does anybody have
>| a better idea?
>|
>| For anybody interested, I've appended a quick (and as yet entirely untested)
>| sketch of the script; comments are welcome.
>|
>| , I'm developing this on a 3.0_BETA system, if there's some reason
>| this wouldn't work on -current, can someone let me know? I can't
>| off-hand think of any obvious way to be able to easily switch between
>| netbsd-3 and current on my laptop.
>
>I think that instead of creating a rc.d script for every firmware, we
>should try to let the kernel do that automatically like Linux does
>with hotplug. And this should work for every driver.
>
>What do you think ?
>
>-- Rui Paulo

The advantage would be, that nfs-root fs would be possible.
(even w/o firmware load, nw-keys would be missing (in the best case it
would an open system))

Isn't there a mechanism to set things via a db in the kernel? (I think
I've seen it but don't know where).
-- would/could properties(9) be the thing to use?

thilo

Sun, Dec 04, 2005 at 10:10:51PM -0500, Steven M. Bellovin wrote:
In message <@angelic.cynic.net>, Curt Sampson
writes:

>
>, I see. So the basic value of an rc.d script would just be that it
>would make setup a little more obvious to newbies. Is this worthwhile,
>do you think? would it be better just to drop the idea and let users
>who don't know how to do this learn about ifconfig.iwi0 some other way?
>

Is there any way to do such initialization in a dhclient.conf file?
That's how I set nwid and nwkey for my wireless cards. It also has the
advantage of loading firmware even for PCMCIA cards that might need
such treatment.

Hmm, it should be possible to do that in /etc/dhclient-enter-hooks.
See the manpage for dhclient-script(8).

Bernd