centrino wlan with linuxant driverloader

Dear all,

I have a Dell Latitude D600 with the Centrino Intel Pro 2100 WLAN adapter.
The laptop is a dualboot with XP and Suse 8.1 with a custom compiled kernel
2.4.24 for ACPI support.

I tried to get WLAN to work with both the free ndiswrapper and the
commercial linuxant driverloader. With the diverloader, I got pretty far,
however, the crucial thing namely establishing a connection to the AP was
not successful yet. :(

I installed the driverloader without problems following the install
instructions. The driverloader module is loaded correctly at starttime as
confirmed by lsmod. Also, the configuration seems to be working smoothly
from including the driver and configuring the wlan adapter using either
iwconfig or Suse yast.

This is what I get for the driverloder config:

dldrconfig --info
Linuxant DriverLoader for Wireless LAN devices, version 1.57

Current parameters: ("dldrconfig --info")

Wireless interface name: eth1
MAC address : my-mac-address
Device instance: PCI-0000:02:03.0-8086:1043-8086:2561
Device driver : w70n51
Driver Version : 1.2.1.1
Description : Intel(R) PRO/Wireless 7100 LAN Card Driver
Adapter model : PRO/Wireless LAN 2100 3A Mini PCI Adapter
License owner : my-email
License key : my license
License status : OK (Expires 2004-03-01)

iwconfig tells me the following:

> iwconfig eth1
Warning : Device eth1 has been compiled with version 16
of Wireless Extension, while we are using version 13.
Some things may be broken...

eth1 IEEE 802.11-DS ESSID:"MyESSID" Nickname:"linux"
Mode:Managed Channel:0 Bit Rate=54Mb/s
RTS thr=1600 B Fragment thr=2344 B
Encryption key: "my 128-bit key here"
Encryption mode:open Power Management:off
Link Quality:1/0 Signal level:-98 dBm Noise level:-200 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

However, I never get an connection to the access point neither at work nor
at home, both of which are configured the same as far as ESSID and wep key
goes.

Does anybody have any experience with this driverloader module and can give
me some hints on what to try? I do NOT consider myself an expert in setting
up wlan connection, but so far when the interface was there, configuring it
with yast always worked.

Thanks and cheers,

Riko

Hi again,

ok, so this was apparently a stupid mistake :) When I booted the machine
into XP today, I noticed that the WLAN card is turned off (radio off),
which it was never before. (?? something happened when installing and
configuring the card with the driverloader??)

Anyway, after rebooting, hitting F2 to get into the bios, I indeed found the
card powered off. After turning it back on and booting into Linux, ta-ta!,
I had a IP address and the card was registered at the DSL WLAN router.

However, now I have a new problem: I can connect to another PC in the home
network (and to the router), but I cannot leave the home network, neither
using name service (for example just using a bookmark in the browser) nor
by directly using the IP (via ssh).

I compared all the config files I could think off (dhcp, ifcg-eth1 etc)
between my two linux notebooks running Suse 8.1 and they seem to be the
same. Except one connects, the other doesn't ... also a PDA connects. Any
idea where I should look? I somehow suspect the DCHP service, but have no
idea how to check that ...

Thanks,

Riko





Riko Wichmann wrote:

> Dear all,
>
> I have a Dell Latitude D600 with the Centrino Intel Pro 2100 WLAN adapter.
> The laptop is a dualboot with XP and Suse 8.1 with a custom compiled
> kernel 2.4.24 for ACPI support.
>
> I tried to get WLAN to work with both the free ndiswrapper and the
> commercial linuxant driverloader. With the diverloader, I got pretty far,
> however, the crucial thing namely establishing a connection to the AP was
> not successful yet. :(
>
> I installed the driverloader without problems following the install
> instructions. The driverloader module is loaded correctly at starttime as
> confirmed by lsmod. Also, the configuration seems to be working smoothly
> from including the driver and configuring the wlan adapter using either
> iwconfig or Suse yast.
>
> This is what I get for the driverloder config:
>
> dldrconfig --info
> Linuxant DriverLoader for Wireless LAN devices, version 1.57
>
> Current parameters: ("dldrconfig --info")
>
> Wireless interface name: eth1
> MAC address : my-mac-address
> Device instance: PCI-0000:02:03.0-8086:1043-8086:2561
> Device driver : w70n51
> Driver Version : 1.2.1.1
> Description : Intel(R) PRO/Wireless 7100 LAN Card Driver
> Adapter model : PRO/Wireless LAN 2100 3A Mini PCI Adapter
> License owner : my-email
> License key : my license
> License status : OK (Expires 2004-03-01)
>
> iwconfig tells me the following:
>
>> iwconfig eth1
> Warning : Device eth1 has been compiled with version 16
> of Wireless Extension, while we are using version 13.
> Some things may be broken...
>
> eth1 IEEE 802.11-DS ESSID:"MyESSID" Nickname:"linux"
> Mode:Managed Channel:0 Bit Rate=54Mb/s
> RTS thr=1600 B Fragment thr=2344 B
> Encryption key: "my 128-bit key here"
> Encryption mode:open Power Management:off
> Link Quality:1/0 Signal level:-98 dBm Noise level:-200 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> However, I never get an connection to the access point neither at work nor
> at home, both of which are configured the same as far as ESSID and wep key
> goes.
>
> Does anybody have any experience with this driverloader module and can
> give me some hints on what to try? I do NOT consider myself an expert in
> setting up wlan connection, but so far when the interface was there,
> configuring it with yast always worked.
>
> Thanks and cheers,
>
> Riko