Wireless Router Login

[jamjoen]

Hi:
Installed SUSE Linux Desktop 10 today. Really like it but cant get my laptop to authenticate with my BTVoyager2091 Router.

SUSE sees the wireless network but then prompts for:
Wireless Security: WEP 64/128-bit ASCII
Key: [I enter the wireless key on bottom of BT router]
Authentication: Open System

Are the foregoing options I am setting correct?I have also tried all the other options to no avail.

I have tried setting a static ip address, subnet, default gateway and also disabling the ethernet LAN card in the laptop to no avail. Searched this forum and a few others but lack of info on BT Voyager routers and linux even on BT site.
Despite this I dont think it is a wireless card setup problem as the Laptop sees the wireless network.

Is there something else I am missing?!?!? Is there a log file that I could look at to maybe give a few hints?

Thanks in advance, jamjoen

[valemon]

Welcome to LF

In the konsole type "su" and your password. Then type "lspci" and "iwconfig" and post the output.

[jamjoen]

Thanks Valemon...Here is the output any advice would be greatly appreciated.

james


JamesTosh:/etc/sysconfig/network # lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
0a:04.0 CardBus bridge: Texas Instruments Unknown device 8039
0a:04.1 FireWire (IEEE 1394): Texas Instruments Unknown device 803a
0a:04.2 Mass storage controller: Texas Instruments Unknown device 803b
0a:04.3 Class 0805: Texas Instruments Unknown device 803c
0a:08.0 Ethernet controller: Intel Corporation Intel(R) PRO/100 VE Network Connection (rev 02)

JamesTosh:/etc/sysconfig/network # iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 unassociated ESSID: off/any
Mode:Managed Frequency=nan kHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm
Retry limit: 15 RTS thr: off Fragment thr: off
Encryption key: off
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:274 Missed beacon: 0

sit0 no wireless extensions

[valemon]

This is exactly copied from oxygen's how to

Connecting

Assuming the driver works (Check for lights) then all we need to do is connect to the access point. You can use GUI tools like KNetworkManager to set-up the connection, this is recommended if you're likely to connect to more than one access point. However I'm going to show you IWconfig, IWconfig is part of Wireless Tools for Linux and will let us connect to the access point by running these commands (As root):

iwconfig <device name> essid <essid of ap> 
iwconfig <device name> key s:”<key>”

So something like:


iwconfig eth0 essid 13cliff iwconfig eth0 key s:“myaccesspoint”

Finally, we start DHCP. There are several ways of starting DHCP with different commands, try all of these until you get one that works (As root):

dhclient <device name> dhcpcd <device name>

And that should be it. Enjoy your new connection!

[jamjoen]

Hi Valemon,

Thanks for this - I tried the following based upon details that eth1 was the wireless card using iwconfig

> su - root
> iwconfig eth1 essid BTVOYAGER2091-XX
> iwconfig eth2 key s:BTVOYAGER2091-XX

> dhclient eth1

I am not sure that the essid I entered is correct as I think this should be the client name and not the router/network name.
Also the dhclient command that I issued didnt find any dhcpoffers.

However on running the "Network Card" option under the YaST control center again y BTVOYAGER2091-XX was again displayed. This time when I went to enter the following options:
> wireless key
> open connect
> WEP 64/128bit - ASCII

The connection was made - I am not sure what the first two iwconfig commands did but I suspect enabling the dhcp might have solved the problem?!?!?!

If you have a moment would you maybe explain the iwconfig commands.
I am guessing that the first line gives the device/wireless card a name. The second then links that to the router/network name. Finally, once dhcp is enabled then the two can talk?!?!?!

Appreciate your guidance. Also what are the equivalent linux commands to:
> ping
> ipconfig
> tracert
> nslookup

Thanks again for your help - really appreciated as now I am online I can get all the other tools i need for the dual boot and sounds card.

cheers again, james (a happy linux newbie)

[gogalthorp]

You can always get info on any Linux command by typing

info command

into a console

in this case

info iwconfig

[valemon]

Also what are the equivalent linux commands to:
> ping
> ipconfig
> tracert
> nslookup

ping->ping
tracert->traceroute
ipconfig->ifconfig
And here is a how to for the nslookup coomand