[driverloader] Not connecting at boot

[Linuxant support (Jean-Simon)]

Hi,

some NDIS drivers/wifi adapters are sensitive with the order that the
settings are done.

You could try to add "iwconfig eth0 essid myessid" to '/etc/rc.local'. The
commands in this file are usually run at the very end of the boot process.

Regards,

Jean-Simon
Technical specialist / Linuxant
www.linuxant.com
support at linuxant.com


----- Original Message ----- 
From: "Jeff" <jm_cct at shaw.ca>
To: <driverloader at lists.linuxant.com>
Sent: Tuesday, February 03, 2004 12:45 AM
Subject: [driverloader] Not connecting at boot


I'm still having problems getting my wireless card to connect at boot
up.  I'm using debian, which uses the /etc/network/interfaces. Mine is
set up as shown (encryption key is Xed).

iface eth0 inet static
        address 192.168.1.150
        netmask 255.255.0.0
        network 192.168.1.0
        wireless_mode managed
        wireless_key XXXX-XXXX-XX
        wireless_freq 2.437G
        wireless_rate 54M
        wireless_essid myessid
        gateway 192.168.1.1
auto eth0

When I boot up and do an iwconfig I get:

eth0      IEEE 802.11g  ESSID:"myessid"  Nickname:"unknown"
          Mode:Managed  Frequency:2.437GHz  Bit Rate=48Mb/s  Tx-Power=13
dBm
          RTS thr:off   Fragment thr:off
          Encryption key:XXXX-XXXX-XX
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Where you can see that the access point is missing
If I run 'iwconfig eth0 essid myessid' and this shows up in my logs:
eth0: New link status: Connected (0001)

It connects and the output is as follows:

eth0      IEEE 802.11g  ESSID:"myessid"  Nickname:"unknown"
          Mode:Managed  Frequency:2.437GHz  Access Point:
00:06:25:D8:FC:D2
          Bit Rate=54Mb/s   Tx-Power=13 dBm
          RTS thr:off   Fragment thr:off
          Encryption key:XXXX-XXXX-XX
          Power Management:off
          Link Quality:1/1  Signal level:-61 dBm  Noise level:-57 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

The only thing that is changed is the AP.  Since the essid is already
known, why do I have to set it again to get the AP?  I have to run that
command every time at boot in order to have it connect, which is a real
pain.  It doesn't even work with an init script.

Driverloader 1.58 (same problem 1.54)
Kernel 2.6.1 (same problem 2.4)
Linksys WMP54G PCI (various driver versions)


-- 
Jeff <jm_cct at shaw.ca>