linux-wlan won't work on kernel 2.6.22 (John)

Post by John
I narrowed down the issue to DHCP. In the ifcfg-wlan0,
I changed the bootproto to static and added the ip
netmask, etc and the device at least connected to the
local area network but I couldn't get it to share the
internet. I figured the device couldn't see the dhcp
server so I did a dhcping when I connected the device
via the static IP and I got an answer. I do not know
if it's a linux-wlan driver issue or a kernel issue.

Hi John,
I never saw any lockups when running FC6, but is udev seeing the card
insert? you can turn on more logging using udevcontrol.

udev by default will run ifup on a network interface if the right ifcfg
script exists. (/etc/sysconfig/network-scripts/ifcfg-wlan0 ?)
I wonder if that is causing your problem ? it shouldn't lock up but it
may be calling dhcp before the card gets fully enabled.

You should be able to use udev to get the card configured -- I wrote a
udev script for this and it's in <wlan_src>/etc/udev/rules.d. copy it
to /etc/usev/rules.d and it should call the standard /etc/wlan config
scripts. I did test it when I wrote it so it should still work, but now
I use NetworkManager to control the card.

if you want to try NM

* remove (or rename) the ifcfg-wlan0 script.

* add "options p80211 wlan_wext_write=1" to /etc/modprobe.conf

* copy the udev rules file from <src>/etc/udev/rules.d/40-prism2.rules
to /etc/udev/rules.d

* enable the NetworkManager & NetworkManagerDispatch services

Then NetworkManger will be able to control and configure your card.

NM will not automatically reconnect to a network with a hidden ssid,
because the prism2 card doesn't report them in the scan list. But you
can access them with the "connect to other wireless network" you just
have to fill in the details every time. and WEP works OK.

I'm currently running fedora 7 on 2.6.22.5 and it all works, WEP, dhcp,
routing etc all setup correctly.
My card is built into the laptop so I don't know how NM handles card
insert & removal, I think it should be OK but it may be interesting to
find out :)
HTH
cheers
Richard

John

2007-09-18 17:03:12 UTC

Thanks for the help. I get an error with the udev
rules on boot as it says.

add_rules invalid kernel operation.

Post by John
I narrowed down the issue to DHCP. In the

ifcfg-wlan0,

Post by John
I changed the bootproto to static and added the ip
netmask, etc and the device at least connected to

the

Post by John
local area network but I couldn't get it to share

the

Post by John
internet. I figured the device couldn't see the

dhcp

Post by John
server so I did a dhcping when I connected the

device

Post by John
via the static IP and I got an answer. I do not

know

Post by John
if it's a linux-wlan driver issue or a kernel

issue.

Date: Tue, 11 Sep 2007 09:44:28 -0700 (PDT)
Subject: Re: [lwlan-devel] linux-wlan won't work

kernel 2.6.22
Content-Type: text/plain; charset=iso-8859-1
Thanks for the help. I saw on the Gentoo Wiki

(I'm

using Fedora Core 6) that the hostapd won't work

I'll have to use linux-wlan in order for my

MA111

card
to work.
I looked at the ifup script and I noticed it has

call to ifup-pre-local with the statement.
if [-x /sbin/ifup-pre-local ]; then
/sbin/ifup-pre-local ${CONFIG} $2
fi
I looked in my sbin and I didn't see a
ifup-pre-local
bin file.
I also noticed in my ifcfg-wlan0 file I have

type as

ethernet. I wonder if this should be wireless.
John

Hi John,
I never saw any lockups when running FC6, but is
udev seeing the card
insert? you can turn on more logging using
udevcontrol.
udev by default will run ifup on a network interface
if the right ifcfg
script exists.
(/etc/sysconfig/network-scripts/ifcfg-wlan0 ?)
I wonder if that is causing your problem ? it
shouldn't lock up but it
may be calling dhcp before the card gets fully
enabled.
You should be able to use udev to get the card
configured -- I wrote a
udev script for this and it's in
<wlan_src>/etc/udev/rules.d. copy it
to /etc/usev/rules.d and it should call the standard
/etc/wlan config
scripts. I did test it when I wrote it so it should
still work, but now
I use NetworkManager to control the card.
if you want to try NM
* remove (or rename) the ifcfg-wlan0 script.
* add "options p80211 wlan_wext_write=1" to
/etc/modprobe.conf
* copy the udev rules file from
<src>/etc/udev/rules.d/40-prism2.rules
to /etc/udev/rules.d
* enable the NetworkManager & NetworkManagerDispatch
services
Then NetworkManger will be able to control and
configure your card.
NM will not automatically reconnect to a network
with a hidden ssid,
because the prism2 card doesn't report them in the
scan list. But you
can access them with the "connect to other wireless
network" you just
have to fill in the details every time. and WEP
works OK.
I'm currently running fedora 7 on 2.6.22.5 and it
all works, WEP, dhcp,
routing etc all setup correctly.
My card is built into the laptop so I don't know how
NM handles card
insert & removal, I think it should be OK but it may
be interesting to
find out :)
HTH
cheers
Richard

____________________________________________________________________________________
Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7

richard kennedy

2007-09-18 21:05:26 UTC

Oh sorry about that! it must be the change in udevd version.
the rules file contains 2 versions of the rule :-

#ACTION=="add",BUS=="usb",DRIVER=="prism2_usb" ,RUN+="/etc/wlan/wlan-udev.sh %k"
KERNEL="wlan*",ACTION=="add",DRIVERS=="prism2_usb" ,RUN+="/etc/wlan/wlan-udev.sh %k"

You could try using the ACTION== one instead -- just uncomment it and
comment out the KERNEL== line. udevd should spot that the rules file has
changed and reload it immediately.

Richard

Post by John
Thanks for the help. I get an error with the udev
rules on boot as it says.
add_rules invalid kernel operation.

Post by John
I narrowed down the issue to DHCP. In the

ifcfg-wlan0,

Post by John
I changed the bootproto to static and added the ip
netmask, etc and the device at least connected to

the

Post by John
local area network but I couldn't get it to share

the

Post by John
internet. I figured the device couldn't see the

dhcp

Post by John
server so I did a dhcping when I connected the

device

Post by John
via the static IP and I got an answer. I do not

know

Post by John
if it's a linux-wlan driver issue or a kernel

issue.

Date: Tue, 11 Sep 2007 09:44:28 -0700 (PDT)
Subject: Re: [lwlan-devel] linux-wlan won't work

kernel 2.6.22
Content-Type: text/plain; charset=iso-8859-1
Thanks for the help. I saw on the Gentoo Wiki

(I'm

using Fedora Core 6) that the hostapd won't work

I'll have to use linux-wlan in order for my

MA111

card
to work.
I looked at the ifup script and I noticed it has

type as

ethernet. I wonder if this should be wireless.
John

Hi John,
I never saw any lockups when running FC6, but is
udev seeing the card
insert? you can turn on more logging using
udevcontrol.
udev by default will run ifup on a network interface
if the right ifcfg
script exists.
(/etc/sysconfig/network-scripts/ifcfg-wlan0 ?)
I wonder if that is causing your problem ? it
shouldn't lock up but it
may be calling dhcp before the card gets fully
enabled.
You should be able to use udev to get the card
configured -- I wrote a
udev script for this and it's in
<wlan_src>/etc/udev/rules.d. copy it
to /etc/usev/rules.d and it should call the standard
/etc/wlan config
scripts. I did test it when I wrote it so it should
still work, but now
I use NetworkManager to control the card.
if you want to try NM
* remove (or rename) the ifcfg-wlan0 script.
* add "options p80211 wlan_wext_write=1" to
/etc/modprobe.conf
* copy the udev rules file from
<src>/etc/udev/rules.d/40-prism2.rules
to /etc/udev/rules.d
* enable the NetworkManager & NetworkManagerDispatch
services
Then NetworkManger will be able to control and
configure your card.
NM will not automatically reconnect to a network
with a hidden ssid,
because the prism2 card doesn't report them in the
scan list. But you
can access them with the "connect to other wireless
network" you just
have to fill in the details every time. and WEP
works OK.
I'm currently running fedora 7 on 2.6.22.5 and it
all works, WEP, dhcp,
routing etc all setup correctly.
My card is built into the laptop so I don't know how
NM handles card
insert & removal, I think it should be OK but it may
be interesting to
find out :)
HTH
cheers
Richard

John

2007-09-19 01:36:21 UTC

Thanks for the help.

I was able to connect to the local network but I was
unable to get a connection to the internet. I could
ping other computers on the network but no internet
also I had to do this with WEP encryption turned off.

I tried with WEP on and I got a wlan0 listed when I
did ifconfig wlan0 <I.P.> but I couldn't ping the
network nor could I get an internet connection. When I
brought the network up, I did the wlanctl-ng with
authtype set to sharedkey instead of opensystem. They
must've made big changes to the kernel because I got
the other kernel to work fairly quickly.

Thanks again,
John

Post by richard kennedy
Oh sorry about that! it must be the change in udevd
version.
the rules file contains 2 versions of the rule :-
#ACTION=="add",BUS=="usb",DRIVER=="prism2_usb"
,RUN+="/etc/wlan/wlan-udev.sh %k"
KERNEL="wlan*",ACTION=="add",DRIVERS=="prism2_usb"
,RUN+="/etc/wlan/wlan-udev.sh %k"
You could try using the ACTION== one instead -- just
uncomment it and
comment out the KERNEL== line. udevd should spot
that the rules file has
changed and reload it immediately.
Richard

Post by John
Thanks for the help. I get an error with the udev
rules on boot as it says.
add_rules invalid kernel operation.

Post by John
I narrowed down the issue to DHCP. In the

ifcfg-wlan0,

Post by John
I changed the bootproto to static and added

the ip

Post by John
netmask, etc and the device at least connected

Post by John
the

Post by John
local area network but I couldn't get it to

Post by John
the

Post by John
internet. I figured the device couldn't see

the

Post by John
dhcp

Post by John
server so I did a dhcping when I connected the

device

Post by John
via the static IP and I got an answer. I do

not

Post by John
know

Post by John
if it's a linux-wlan driver issue or a kernel

issue.

Date: Tue, 11 Sep 2007 09:44:28 -0700 (PDT)
Subject: Re: [lwlan-devel] linux-wlan won't

work

Post by John
on

kernel 2.6.22
Content-Type: text/plain; charset=iso-8859-1
Thanks for the help. I saw on the Gentoo

Wiki

Post by John
(I'm

using Fedora Core 6) that the hostapd won't

work

Post by John
so

I'll have to use linux-wlan in order for my

MA111

card
to work.
I looked at the ifup script and I noticed it

has

Post by John
a

type as

ethernet. I wonder if this should be

wireless.

John

Hi John,
I never saw any lockups when running FC6, but is
udev seeing the card
insert? you can turn on more logging using
udevcontrol.
udev by default will run ifup on a network

interface

Post by John
if the right ifcfg
script exists.
(/etc/sysconfig/network-scripts/ifcfg-wlan0 ?)
I wonder if that is causing your problem ? it
shouldn't lock up but it
may be calling dhcp before the card gets fully
enabled.
You should be able to use udev to get the card
configured -- I wrote a
udev script for this and it's in
<wlan_src>/etc/udev/rules.d. copy it
to /etc/usev/rules.d and it should call the

standard

Post by John
/etc/wlan config
scripts. I did test it when I wrote it so it

should

Post by John
still work, but now
I use NetworkManager to control the card.
if you want to try NM
* remove (or rename) the ifcfg-wlan0 script.
* add "options p80211 wlan_wext_write=1" to
/etc/modprobe.conf
* copy the udev rules file from
<src>/etc/udev/rules.d/40-prism2.rules
to /etc/udev/rules.d
* enable the NetworkManager &

NetworkManagerDispatch

Post by John
services
Then NetworkManger will be able to control and
configure your card.
NM will not automatically reconnect to a network
with a hidden ssid,
because the prism2 card doesn't report them in

the

Post by John
scan list. But you
can access them with the "connect to other

wireless

Post by John
network" you just
have to fill in the details every time. and WEP
works OK.
I'm currently running fedora 7 on 2.6.22.5 and

Post by John
all works, WEP, dhcp,
routing etc all setup correctly.
My card is built into the laptop so I don't know

how

Post by John
NM handles card
insert & removal, I think it should be OK but it

may

Post by John
be interesting to
find out :)
HTH
cheers
Richard

____________________________________________________________________________________

Post by John
Fussy? Opinionated? Impossible to please? Perfect.

Join Yahoo!'s user panel and lay it on us.

http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
____________________________________________________________________________________
Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games.
http://sims.yahoo.com/

richard kennedy

2007-09-19 08:55:15 UTC

that sounds like the routing got setup ok, does the output
from /sbin/route look reasonable?
I think dns didn't get setup. what does dig say?

If you're using a static IP you'll need to set the nameserver entry
in /etc/resolv.conf too.

I would expect dhcp to work and it will set all that for you, so you
could try that instead.

are you see any useful/informative messages in the log ?

Richard

Thanks for the help.
I was able to connect to the local network but I was
unable to get a connection to the internet. I could
ping other computers on the network but no internet
also I had to do this with WEP encryption turned off.
I tried with WEP on and I got a wlan0 listed when I
did ifconfig wlan0 <I.P.> but I couldn't ping the
network nor could I get an internet connection. When I
brought the network up, I did the wlanctl-ng with
authtype set to sharedkey instead of opensystem. They
must've made big changes to the kernel because I got
the other kernel to work fairly quickly.
Thanks again,
John

Post by John
Thanks for the help. I get an error with the udev
rules on boot as it says.
add_rules invalid kernel operation.

Post by John
I narrowed down the issue to DHCP. In the

ifcfg-wlan0,

Post by John
I changed the bootproto to static and added

the ip

Post by John
netmask, etc and the device at least connected

Post by John
the

Post by John
local area network but I couldn't get it to

Post by John
the

Post by John
internet. I figured the device couldn't see

the

Post by John
dhcp

Post by John
server so I did a dhcping when I connected the

device

Post by John
via the static IP and I got an answer. I do

not

Post by John
know

Post by John
if it's a linux-wlan driver issue or a kernel

issue.

Date: Tue, 11 Sep 2007 09:44:28 -0700 (PDT)
Subject: Re: [lwlan-devel] linux-wlan won't

work

Post by John
on

kernel 2.6.22
Content-Type: text/plain; charset=iso-8859-1
Thanks for the help. I saw on the Gentoo

Wiki

Post by John
(I'm

using Fedora Core 6) that the hostapd won't

work

Post by John
so

I'll have to use linux-wlan in order for my

MA111

card
to work.
I looked at the ifup script and I noticed it

has

Post by John
a

type as

ethernet. I wonder if this should be

wireless.

John

Hi John,
I never saw any lockups when running FC6, but is
udev seeing the card
insert? you can turn on more logging using
udevcontrol.
udev by default will run ifup on a network

interface

standard

Post by John
/etc/wlan config
scripts. I did test it when I wrote it so it

should

NetworkManagerDispatch

the

Post by John
scan list. But you
can access them with the "connect to other

wireless

Post by John
network" you just
have to fill in the details every time. and WEP
works OK.
I'm currently running fedora 7 on 2.6.22.5 and

Post by John
all works, WEP, dhcp,
routing etc all setup correctly.
My card is built into the laptop so I don't know

how

Post by John
NM handles card
insert & removal, I think it should be OK but it

may

Post by John
be interesting to
find out :)
HTH
cheers
Richard

____________________________________________________________________________________

Post by John
Fussy? Opinionated? Impossible to please? Perfect.

Join Yahoo!'s user panel and lay it on us.

John

2007-09-20 06:15:54 UTC

Thanks for the help.

I did a route on the old kernel where everything works
and on the new kernel where it doesn't work. This is
what I get.

old kernel:

Kernel IP routing table
Destination Gateway Genmask Flags
Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U
0 0 0 wlan0
169.254.0.0 * 255.255.0.0 U
0 0 0 wlan0
default 192.168.0.1 0.0.0.0 UG
0 0 0 wlan0

new kernel:

Kernel IP routing table
Destination Gateway Genmask Flags
Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U
0 0 0 wlan0

What I don't get is with the new kernel, I have to run

ifconfig wlan0 <IP>

It would seem to make sense that all I need to do is
run ifconfig wlan0 up and the dhcp would automatically
assign the address but in my case I have to add an IP
address.

I'm at a loss as to what's changed in the new kernel
to cause such a dramatic issue in my case.

Post by richard kennedy
that sounds like the routing got setup ok, does the
output
from /sbin/route look reasonable?
I think dns didn't get setup. what does dig say?
If you're using a static IP you'll need to set the
nameserver entry
in /etc/resolv.conf too.
I would expect dhcp to work and it will set all that
for you, so you
could try that instead.
are you see any useful/informative messages in the
log ?
Richard

Thanks for the help.
I was able to connect to the local network but I

was

unable to get a connection to the internet. I

could

ping other computers on the network but no

internet

also I had to do this with WEP encryption turned

off.

I tried with WEP on and I got a wlan0 listed when

did ifconfig wlan0 <I.P.> but I couldn't ping the
network nor could I get an internet connection.

When I

brought the network up, I did the wlanctl-ng with
authtype set to sharedkey instead of opensystem.

They

must've made big changes to the kernel because I

got

the other kernel to work fairly quickly.
Thanks again,
John

Post by richard kennedy
Oh sorry about that! it must be the change in

udevd

Post by richard kennedy
version.
the rules file contains 2 versions of the rule

Post by richard kennedy
#ACTION=="add",BUS=="usb",DRIVER=="prism2_usb"
,RUN+="/etc/wlan/wlan-udev.sh %k"

KERNEL="wlan*",ACTION=="add",DRIVERS=="prism2_usb"

Post by richard kennedy
,RUN+="/etc/wlan/wlan-udev.sh %k"
You could try using the ACTION== one instead --

just

Post by richard kennedy
uncomment it and
comment out the KERNEL== line. udevd should spot
that the rules file has
changed and reload it immediately.
Richard

Post by John
Thanks for the help. I get an error with the

udev

Post by John
rules on boot as it says.
add_rules invalid kernel operation.

On Sat, 2007-09-15 at 11:04 -0700, John

Post by John
I narrowed down the issue to DHCP. In the

ifcfg-wlan0,

Post by John
I changed the bootproto to static and

added

Post by richard kennedy
the ip

Post by John
netmask, etc and the device at least

connected

Post by richard kennedy
to

the

Post by John
local area network but I couldn't get it

Post by richard kennedy
share

the

Post by John
internet. I figured the device couldn't

see

Post by richard kennedy
the

dhcp

Post by John
server so I did a dhcping when I connected

the

device

Post by John
via the static IP and I got an answer. I

Post by richard kennedy
not

know

Post by John
if it's a linux-wlan driver issue or a

kernel

issue.

Date: Tue, 11 Sep 2007 09:44:28 -0700

(PDT)

Subject: Re: [lwlan-devel] linux-wlan

won't

Post by richard kennedy
work

kernel 2.6.22
Content-Type: text/plain;

charset=iso-8859-1

Thanks for the help. I saw on the Gentoo

Wiki

(I'm

using Fedora Core 6) that the hostapd

won't

Post by richard kennedy
work

I'll have to use linux-wlan in order for

MA111

card
to work.
I looked at the ifup script and I

noticed it

Post by richard kennedy
has

call to ifup-pre-local with the

statement.

if [-x /sbin/ifup-pre-local ]; then
/sbin/ifup-pre-local ${CONFIG} $2
fi
I looked in my sbin and I didn't see a
ifup-pre-local
bin file.
I also noticed in my ifcfg-wlan0 file I

have

type as

ethernet. I wonder if this should be

wireless.

John

Hi John,
I never saw any lockups when running FC6,

but is

udev seeing the card
insert? you can turn on more logging using
udevcontrol.
udev by default will run ifup on a network

interface

if the right ifcfg
script exists.
(/etc/sysconfig/network-scripts/ifcfg-wlan0

I wonder if that is causing your problem ?

shouldn't lock up but it
may be calling dhcp before the card gets

fully

enabled.
You should be able to use udev to get the

card

configured -- I wrote a
udev script for this and it's in
<wlan_src>/etc/udev/rules.d. copy it
to /etc/usev/rules.d and it should call the

standard

/etc/wlan config
scripts. I did test it when I wrote it so it

should

still work, but now
I use NetworkManager to control the card.
if you want to try NM
* remove (or rename) the ifcfg-wlan0 script.

=== message truncated ===

____________________________________________________________________________________
Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos.
http://autos.yahoo.com/index.html

FeRD

2007-09-20 08:21:59 UTC

Post by John
What I don't get is with the new kernel, I have to run
ifconfig wlan0 <IP>
It would seem to make sense that all I need to do is
run ifconfig wlan0 up and the dhcp would automatically
assign the address but in my case I have to add an IP
address.

Actually, no. ifconfig triggers no outside operations to set up your
networking, it's strictly a low-level tool to configure parameters of
the network interface itself. That's also why you're not seeing a
default route set in the "new kernel" scheme, because the routing table
isn't being updated either. (This isn't any direct consequence of the
kernel issue, whatever it is -- I haven't been following that. Most
likely, it's fallout from the fact that said kernel change tripped up
udev and prevented all of its normal device-setup wizardry from properly
executing.)

Honestly, running ifconfig itself "by hand" is almost unheard of these
days, and certainly only as part of a debugging/testing/development
process -- "normal use" wouldn't involve anything so low-level as a
manual ifconfig. (...Not in the past decade, at least.)

Most (all?) Linux distros provide the /sbin/ifup utility script to
manage all of the steps that go into configuring various types of
network interfaces and connecting them to the varied types of networks
they may need to access. It's ifup that takes charge of executing (based
on hardware information and configuration supplied in /etc/sysconfig/)
the steps needed to make wlan0 live.

So, really, assuming your network configuration in
/etc/sysconfig/network/ is correct (set up via system-config-network, at
least on my Fedora machines), bringing up wlan0 should be as simple as
running:

/sbin/ifup wlan0

...Which will trigger various steps, INCLUDING but in no way limited to:

dhclient wlan0
ifconfig wlan0 <some_ip> {<various_other_settings>...}
route add default <some_gateway> {<various...>}

...Now, all that being said, ifup has some "issues" (oh, screw it,
they're problems[*]) -- it takes NO parameters other than the name of a
network interface, is completely monolithic, and requires that
/etc/sysconfig/networking-scripts fully understand and support your
interface and its configuration to your network. So, what happens when
(say) there are wlanctl-ng commands you need to run YOURSELF (for
whatever reason), somewhere in between (say) steps 3 and 4 of ifup's
magic? Bad news. You can't. (You have to teach them to ifup via
/etc/sysconfig/networking-scripts, or not use it.)

In your case, tho, for testing purposes -- throwing out DHCP since, if
you're going manual, why bother? -- after ifconfig'ing the interface
with an IP address (and netmask, if it's other than the standard
255.255.255.0 -- but it almost certainly isn't), you'd need to add a
default route thru the gateway of that interface, which takes the form:

/sbin/route add default gw <gateway_ip> dev wlan0

At THAT point you should be able to ping computers outside of your local
network... but only by IP address. If you want DNS, you'll also have to
add a couple of lines to /etc/resolv.conf like:

nameserver ip.the.first.here
nameserver ip.the.second.here

(Hey, I never said there wasn't a lot going on behind a "simple" ifup!)

BTW, in taking the "by hand" approach to this stuff, you CAN get a bit
of help, simply by cheating off of ifup's test paper for the answers.

Because ifup is simply a (complex) shell script that triggers a whole
twisty mess of other shell scripts, those operations can be handily
traced using the Bourne shell's -x flag. Thus, a nifty
debugging/sanity-checking trick is to run ifup like so:

/bin/bash -x /sbin/ifup wlan0

...And you'll get a long, mostly-boring, but ultimately enlightening
play-by-play of everything ifup goes through in attempting to make wlan0
ready for prime time. Lines preceded with a "+" sign are script
operations. Anything else is actual output of the script. The two are
intermingled, so you get to see lots of redundancies like:

+ echo "Sorry, Dave, I'm afraid I can't do that."
Sorry, Dave, I'm afraid I can't do that.

C'est la vie.

-FeRD

P.S> [*] - Why am I unkind in my comments about ifup, despite it being a
very useful tool? Because it reminds me way too much of using an Apple
Mac (especially pre-OS X) -- works fine-n-dandy when it works, and
/ususally/ does indeed work, but everything happens automagically with a
big flourish of "pay no attention to the man behind the curtain"
mystique. Minimal user input (just the name of the interface) needed but
absolutely NOTHING MORE _accepted_, the same zero lines of output
whether the result is success or failure, and there's a great yawning
chasm of a difference between a philosophy of not "bothering" the user
with lots of narrative logging, and giving the user absolutely NOTHING
in the way of operations tracing should one _ASK_ to be "bothered" with it!

John

2007-09-20 18:37:22 UTC

Thanks for the help. Actually my issue is that ifup
crashes my system so this is why I couldn't use ifup.
I think I resolved the ifup crash as I took a look at
the wlan-udev.sh file and I'm starting to see the
purpose of the udev rule as this script takes care of
loading the module and running ifup which I was doing
in my rc.local. Thanks for the tip on running bash in
debug mode as I did this and I noticed an issue.

return 1
++ /sbin/wlanctl-ng lnxreq_hostwep decrypt=false
encrypt=false
+ result='The cmd '\''decrypt=false'\'' is invalid'
+ '[' 255 '!=' 0 ']'
+ echo 'Cannot enable wep The cmd
'\''decrypt=false'\'' is invalid'
Cannot enable wep The cmd 'decrypt=false' is invalid
+ exit 1