Linux wireless problem solve on D600 with 2200

Ok, I have found my solution, finally had time to look around for it.
Since, I had to "hack-it" thrue, here my solution for other who have
problem with that. Maybe, there is something that I don't do as I
should, but it work.

What I have:

- Dell d600 labtop;
- Intel 2200 B/G wireless card;
- Suse 9.1 (Kernel-stock: 2.6.5-7.95-default);
- D-Link DI-624, conf: dhcp

What I want:
- Connect to my wireless AP;
- Using WEP with shared keys;
- Connect on demand, not at bootup, but when I need to;

What I have done:

- I have used driverloader-0.7, the 0.8 version seen to crash my
keyboard input;
- I used the driver from the driverloarder website, the driver from Dell
didn't seen to work;
- Since the kernel was stock, I had to do a make cloneconfig and make
prepare-all, because when I was compiling driverloader I had a complain
about Module.symvers who wasn't found, I had to copy myself to place
where driverloader was looking for it, so do a find to find where it is
and copy it;

After this, I followed they driverloader instruction, but it wasn't
working out, sometime I was getting an IP but with no connection or I
wasn't getting anything.

What I have found is that, when you do an ifup it will lose your
wireless configuration? So if you IP is set, it doesn't have the key or
essid to communicate with your AP ...

Here what my system did:

modprobe ndiswrapper

iwconfig wlan0 mode Managed
iwconfig wlan0 key restricted yourkey
iwconfig wlan0 essid youressid

then if I were doing an iwconfig, I will see my conf, so I start my wireless

ifup wlan0

it gaved me and error, it did put my card up but with no IP

EmRROR: command 'iwconfig wlan0 key mykey' returned
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wlan0 ; Invalid argument.

if I do a iwconfig, I get all empty default option, I'm pretty sure that
when an error is seen in ifup it reset the conf (well doesn't touch the
/etc/sysconfig/network/ifcfg-wlan0) but reset in memory the conf

But, if I give the card conf again:

iwconfig wlan0 mode Managed
iwconfig wlan0 key restricted yourkey
iwconfig wlan0 essid youressid

the card does get an IP without any complain ...

But then, if I try to ping anything (except itself ) from the card
even localhost
(ping -I wlan0 localhost) it doesn't find it, if I look at iwconfig,
again I can see all my option reset. Even if it does have an IP, it
doesn't have what it need to speak with the AP, so nothing.

But , by setting my conf again, now it work ...

iwconfig wlan0 mode Managed
iwconfig wlan0 key restricted yourkey
iwconfig wlan0 essid youressid

now it work ...

So I have made a little script that made the stuff work, pretty basic one.

#/bin/sh

action=$1

if [ "$action" = "stop" ]; then
echo "WE SHUTDOWN THE WIRELESS"
ifdown wlan0

else
echo "WE START THE WIRELESS"
ifup wlan0

#display they error message
#bring they interface up but with no IP

#when it will be set, I will get an IP
iwconfig wlan0 mode Managed
iwconfig wlan0 key restricted yourkey
iwconfig wlan0 essid youressid

echo "SLEEP 10"
#get me an IP
sleep 10

#I got an IP, but lose my conf, so do it again
iwconfig wlan0 mode Managed
iwconfig wlan0 key restricted yourkey
iwconfig wlan0 essid youressid

#I do I'm wireless now
fi

The sleep give enough time to the dhcp server to give me an address and
then set my option again.

save it in something like rcwireless, when you do "wireless" it will
start it and "wireless stop" will stop it.

I hope it help you ...

One other things to do, is that on my system, I have a Fn-F2 that can
disable they hardware, I don't know why but before doing the conf, I
have to press it twice or it will not found my AP.

Francis Fillion wrote:
> Ok, I have found my solution, finally had time to look around for it.
> Since, I had to "hack-it" thrue, here my solution for other who have
> problem with that. Maybe, there is something that I don't do as I
> should, but it work.
>
> What I have:
>
> - Dell d600 labtop;
> - Intel 2200 B/G wireless card;
> - Suse 9.1 (Kernel-stock: 2.6.5-7.95-default);
> - D-Link DI-624, conf: dhcp
>
> What I want:
> - Connect to my wireless AP;
> - Using WEP with shared keys;
> - Connect on demand, not at bootup, but when I need to;
>
> What I have done:
>
> - I have used driverloader-0.7, the 0.8 version seen to crash my
> keyboard input;
> - I used the driver from the driverloarder website, the driver from Dell
> didn't seen to work;
> - Since the kernel was stock, I had to do a make cloneconfig and make
> prepare-all, because when I was compiling driverloader I had a complain
> about Module.symvers who wasn't found, I had to copy myself to place
> where driverloader was looking for it, so do a find to find where it is
> and copy it;
>
> After this, I followed they driverloader instruction, but it wasn't
> working out, sometime I was getting an IP but with no connection or I
> wasn't getting anything.
>
> What I have found is that, when you do an ifup it will lose your
> wireless configuration? So if you IP is set, it doesn't have the key or
> essid to communicate with your AP ...
>
> Here what my system did:
>
> modprobe ndiswrapper
>
> iwconfig wlan0 mode Managed
> iwconfig wlan0 key restricted yourkey
> iwconfig wlan0 essid youressid
>
> then if I were doing an iwconfig, I will see my conf, so I start my
> wireless
>
> ifup wlan0
>
> it gaved me and error, it did put my card up but with no IP
>
> EmRROR: command 'iwconfig wlan0 key mykey' returned
> Error for wireless request "Set Encode" (8B2A) :
> SET failed on device wlan0 ; Invalid argument.
>
> if I do a iwconfig, I get all empty default option, I'm pretty sure that
> when an error is seen in ifup it reset the conf (well doesn't touch the
> /etc/sysconfig/network/ifcfg-wlan0) but reset in memory the conf
>
> But, if I give the card conf again:
>
> iwconfig wlan0 mode Managed
> iwconfig wlan0 key restricted yourkey
> iwconfig wlan0 essid youressid
>
> the card does get an IP without any complain ...
>
> But then, if I try to ping anything (except itself ) from the card
> even localhost
> (ping -I wlan0 localhost) it doesn't find it, if I look at iwconfig,
> again I can see all my option reset. Even if it does have an IP, it
> doesn't have what it need to speak with the AP, so nothing.
>
> But , by setting my conf again, now it work ...
>
> iwconfig wlan0 mode Managed
> iwconfig wlan0 key restricted yourkey
> iwconfig wlan0 essid youressid
>
> now it work ...
>
> So I have made a little script that made the stuff work, pretty basic one.
>
> #/bin/sh
>
> action=$1
>
> if [ "$action" = "stop" ]; then
> echo "WE SHUTDOWN THE WIRELESS"
> ifdown wlan0
>
> else
> echo "WE START THE WIRELESS"
> ifup wlan0
>
> #display they error message
> #bring they interface up but with no IP
>
> #when it will be set, I will get an IP
> iwconfig wlan0 mode Managed
> iwconfig wlan0 key restricted yourkey
> iwconfig wlan0 essid youressid
>
> echo "SLEEP 10"
> #get me an IP
> sleep 10
>
> #I got an IP, but lose my conf, so do it again
> iwconfig wlan0 mode Managed
> iwconfig wlan0 key restricted yourkey
> iwconfig wlan0 essid youressid
>
> #I do I'm wireless now
> fi
>
> The sleep give enough time to the dhcp server to give me an address and
> then set my option again.
>
> save it in something like rcwireless, when you do "wireless" it will
> start it and "wireless stop" will stop it.
>
> I hope it help you ...
>
>
>
>
>
>
>
>
>
>
>

Francis Fillion wrote:
> One other things to do, is that on my system, I have a Fn-F2 that can
> disable they hardware, I don't know why but before doing the conf, I
> have to press it twice or it will not found my AP.
>
> Francis Fillion wrote:
>
>> Ok, I have found my solution, finally had time to look around for it.
>> Since, I had to "hack-it" thrue, here my solution for other who have
>> problem with that. Maybe, there is something that I don't do as I
>> should, but it work.
>>
>> What I have:
>>
>> - Dell d600 labtop;
>> - Intel 2200 B/G wireless card;
>> - Suse 9.1 (Kernel-stock: 2.6.5-7.95-default);
>> - D-Link DI-624, conf: dhcp
>>
>> What I want:
>> - Connect to my wireless AP;
>> - Using WEP with shared keys;
>> - Connect on demand, not at bootup, but when I need to;
>>
>> What I have done:
>>
>> - I have used driverloader-0.7, the 0.8 version seen to crash my
>> keyboard input;
>> - I used the driver from the driverloarder website, the driver from
>> Dell didn't seen to work;
>> - Since the kernel was stock, I had to do a make cloneconfig and make
>> prepare-all, because when I was compiling driverloader I had a
>> complain about Module.symvers who wasn't found, I had to copy myself
>> to place where driverloader was looking for it, so do a find to find
>> where it is and copy it;
>>
>> After this, I followed they driverloader instruction, but it wasn't
>> working out, sometime I was getting an IP but with no connection or I
>> wasn't getting anything.
>>
>> What I have found is that, when you do an ifup it will lose your
>> wireless configuration? So if you IP is set, it doesn't have the key
>> or essid to communicate with your AP ...
>>
>> Here what my system did:
>>
>> modprobe ndiswrapper
>>
>> iwconfig wlan0 mode Managed
>> iwconfig wlan0 key restricted yourkey
>> iwconfig wlan0 essid youressid
>>
>> then if I were doing an iwconfig, I will see my conf, so I start my
>> wireless
>>
>> ifup wlan0
>>
>> it gaved me and error, it did put my card up but with no IP
>>
>> EmRROR: command 'iwconfig wlan0 key mykey' returned
>> Error for wireless request "Set Encode" (8B2A) :
>> SET failed on device wlan0 ; Invalid argument.
>>
>> if I do a iwconfig, I get all empty default option, I'm pretty sure
>> that when an error is seen in ifup it reset the conf (well doesn't
>> touch the /etc/sysconfig/network/ifcfg-wlan0) but reset in memory the
>> conf
>>
>> But, if I give the card conf again:
>>
>> iwconfig wlan0 mode Managed
>> iwconfig wlan0 key restricted yourkey
>> iwconfig wlan0 essid youressid
>>
>> the card does get an IP without any complain ...
>>
>> But then, if I try to ping anything (except itself ) from the card
>> even localhost
>> (ping -I wlan0 localhost) it doesn't find it, if I look at iwconfig,
>> again I can see all my option reset. Even if it does have an IP, it
>> doesn't have what it need to speak with the AP, so nothing.
>>
>> But , by setting my conf again, now it work ...
>>
>> iwconfig wlan0 mode Managed
>> iwconfig wlan0 key restricted yourkey
>> iwconfig wlan0 essid youressid
>>
>> now it work ...
>>
>> So I have made a little script that made the stuff work, pretty basic
>> one.
>>
>> #/bin/sh
>>
>> action=$1
>>
>> if [ "$action" = "stop" ]; then
>> echo "WE SHUTDOWN THE WIRELESS"
>> ifdown wlan0
>>
>> else
>> echo "WE START THE WIRELESS"
>> ifup wlan0
>>
>> #display they error message
>> #bring they interface up but with no IP
>>
>> #when it will be set, I will get an IP
>> iwconfig wlan0 mode Managed
>> iwconfig wlan0 key restricted yourkey
>> iwconfig wlan0 essid youressid
>>
>> echo "SLEEP 10"
>> #get me an IP
>> sleep 10
>>
>> #I got an IP, but lose my conf, so do it again
>> iwconfig wlan0 mode Managed
>> iwconfig wlan0 key restricted yourkey
>> iwconfig wlan0 essid youressid
>>
>> #I do I'm wireless now
>> fi
>>
>> The sleep give enough time to the dhcp server to give me an address
>> and then set my option again.
>>
>> save it in something like rcwireless, when you do "wireless" it will
>> start it and "wireless stop" will stop it.
>>
>> I hope it help you ...
>>

ifup will do the necessary iwconfig settings for you if you provide the
necessary information in iwcfg-wlan0

Il m'a pris deux jours avant de realiser que le Fn-F2 n'était pas un gadget pour
µicro$oft Windoze, mais qu'il gérait bien le matériel. (Targa Visionary)

Gérard