Wireless and SuSE 9.1

[PaulLejean]

Hello ! Does somebody set up a wireless connection with SuSE Linux 9.1 ?
I cannot get it working. Could somebody help me ??

The Intel PRO/Wireless 2100 3B Mini PCI adapter is detected and the firmware is loaded, no error
messages. the 'iwlist scan' detects the access point but i cannot connect the computer to it.

Could somebody help me ??

Thank you very much in advance,

Paul

[PaulLejean]

Is there somebody to help me ?? Pleeeeeeaaaaaase heeeeeeelp...
I'm very disappointed...

[jdhurst]

The Intel 2100 card does not work very well in the best of circumstances. I discarded mine and installed the IBM 11a/b/g card and it is vastly superior. So your issue may be either SuSE or the card itself. Tough to tell.

Do you have / can you get / can you borrow a Windows machine with that Intel 2100 card in it? Then connect it to your wireless access point using Windows to manage the connect and definitely not using Access Connections. Then make a note of your settings (especially any encryption keys you had to use).

Then with these notes, try to replicate the settings in your SuSE machine. That's the best I can think of based on my Windows experience with Wireless Access, the Intel 2100 card, and now the IBM 11/a/b/g card.
... JDHurst

[PaulLejean]

Hello !

The Intel 2100 card does not work very well in the best of circumstances. I discarded mine and installed the IBM 11a/b/g card and it is vastly superior. So your issue may be either SuSE or the card itself. Tough to tell.

Do you have / can you get / can you borrow a Windows machine with that Intel 2100 card in it? Then connect it to your wireless access point using Windows to manage the connect and definitely not using Access Connections. Then make a note of your settings (especially any encryption keys you had to use).

On the X31 I have both WinXP Pro and SuSE 9.1 installed and both are working perfectly.
On WinXP, I've simply entered my wep key and the connection was ok, so the
card is fully functional. This card is perfectly detected by SuSE and the correct driver is loaded.
The wireless card is then labelled 'eth1'
The 'iwlist eth1 scan' command gives me

--------------- [ snip ] --------------------
eth1  Scan completed :
        Cell 01 - Address : 00:03:25:EF:6E:D4
             ESSID : "My-Wifi-Domain"
             Mode : Master
             Frequency : 2.457Ghz
             BitRate : 1 Mb/sec
             BitRate : 2 Mb/sec
             BitRate : 5.5 Mb/sec
             BitRate : 11 Mb/sec
             Quality : 36/100  Signal level : -62dBm  Noise Level : -98 dBm
             Encryption key : On
--------------- [ snip ] --------------------

Then, I type the following commands to connect the X31 to the access point :
        iwconfig eth1 ap 00:03:25:EF:6E:D4
        iwconfig eth1 key 523E653285 open
(i try with 'open' first. It's exactly the same problem with 'restricted')

and now, the output of the 'iwconfig' command is the following :
--------------- [ snip ] --------------------
eth0 IEEE 802.11b ESSID : "My-Wifi-Domain" Nickname : "linux"
     Mode : Managed    Channel : 0    Access Point : 00:00:00:00:00:00
     Bit Rate = 0Kb/s    Tx-Power=0 dBm
     Retry : on      RTS thr=2304 B     Fragment thr : 2332  B
     Encryption key : 523E-6532-85   Security mode : open
     Link quality : 0/100    Signal level : -98dBm    Noise Level : -98 dBm
     Rx invalid nwid : 0   Rx invalid crypt : 0   Rx invalid flag : 0
     Tx excessive retries : 0   Invalid misc : 0   Missed beacon : 0
--------------- [ snip ] --------------------

and the access point has not changed !!!!!

Somebody told me that it would certainly be an authentification problem and I should
add the word ''restricted' after the key in my /etc/sysconfig/network/ethx file.
So here is my /etc/sysconfig/network/ifcfg-wlan-bus-pci-### file :
        BOOTPROTO='dhcp'
        DHCLIENT_SET_DEFAULT_ROUTE='yes'
        MTU=''
        REMOTE_IP_ADDR=''
        SMARTMODE='onboot'
        UNIQUE='#######'
        WIRELESS_AP='any'
        WIRELESS_BITRATE='auto'
        WIRELESS_CHANNEL=''
        WIRELESS_ESSID='any'
        WIRELESS_KEY=''
        WIRELESS_MODE='managed'
        WIRELESS_NICK=''
        WIRELESS_NWID=''
        WIRELESS_POWER='yes'
        _nm_name='bus-pci-#####'
        WIRELESS_FREQUENCY=''
        WIRELESS_KEY_0='583E215395'
        WIRELESS_KEY_1=''
        WIRELESS_KEY_2=''
        WIRELESS_KEY_3=''
        WIRELESS_KEY_LENGTH='128'


Should I indicate my encryption key in WIRELESS_KEY ?
Like this :
        WIRELESS_KEY='583E215395 restricted'    
??????

Then with these notes, try to replicate the settings in your SuSE machine. That's the best I can think of based on my Windows experience with Wireless Access, the Intel 2100 card, and now the IBM 11/a/b/g card.
... JDHurst

Thank you very very much !

Paul

[jdhurst]

If you are using 128-bit encryption, then the key you are using is not long enough. The key generated for 128-bit encryption is 26 characters. Find that key in your router setup and try keying that in at the appropriate spot in your SuSE setup. ... JDHurst