Wireless USB Linksys Network Adapter with SUSE 9.2
 

Have problems accessing the network and the internet.

Have a Linksys wireless system with a router, a couple of usb wireless network adapters and a network PC card (for my laptop). The system is configured as a managed network, with a WEP autentication, and statically assigned IP addressess on each computer. When in Windows XP it is working well.

I had now just installed Linux 9.2. The linksys usb network adapter was recognized and the adapter was intalled automatically. I also disabled the eth0. Both lights on the adapter are lighten (one blinking), indicating the adapter is working. However, I have no signal and no internet connection. iwconfig results in the following:

wlan0 IEEE 802.11-DS ESSID:"XXXXXX" Nickname:"linux"
Mode:Managed Frequency:2.457 GHz Access Point: 00:00:00:00:00:00
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:8 RTS thr=1536 B Fragment thr=1536 B
Encryption key:XXXXXXXXXXXXXXXXXXXX Security mode:open
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

I did not specify the access point because i have only one router. is this correct? Should i specify the MAC of the router or the MAC of the Network adapter?

Since I have installed the network on the XP system, I am somewhat familiar with the settings (IP, Sub net Mask, default gateway, WEP ,etc).

How should I proceed from here?

Kachaturian

Moved: This thread is more suitable in Wireless Networking and has been moved accordingly to help your thread/question get the exposure it deserves.

Hello there!

ifconfig will give you your card's mac address whereas iwconfig shows the mac address of the router you are connected to. Specifying the ssid will therefore associate it to the router and should not result in MAC address specification being required. If the ssid has been set then
dhclient wlan0
should get you an IP address. Check ifconfig to see if you have been allocated one by the router.
Regards
Chris

Thanks,
typing "dhclient wlan0 " I got a " dhclient comand does not exists" reply.

Typing route -n I get
linux:~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.xxx.0.0 0.0.0.0 255.xxx.xxx.0 U 0 0 0 wlan0
169.xxx.0.0 0.0.0.0 255.xxx.0.0 U 0 0 0 wlan0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.xxx.0.xx 0.0.0.0 UG 0 0 0 wlan0
linux:~ #
where 192.xxx.0.xx is the IP adress of the router
and
255.xxx.xxx.0 is the default gateway

the computer has a preassigned IP adress 192.xxx.0.yy

How do I see this in the comand line (i.e., what is the equivalent to the ipconfig all in windows XP?)

Under mesages, I obtain the following, suggesting that there is no connection to the router

:44 linux kernel: wlan0: no IPv6 routers present
Jan 22 19:02:44 linux SuSEfirewall2: Firewall rules successfully set from /etc/sysconfig/SuSEfirewall2

Is it the firewall that is preventing acess to the network. As I mentioned before, the Lynksis router requires a WEP key. I have set this in the copmputer via YAST.

using ping and an the IP address of the router I get "No network found"

Roberto

Following my previous, the boot log shows the following:

Master Resource Control: previous runlevel: N, switching to runlevel: 5
<notice>start services (random isdn SuSEfirewall2_init)
Initializing random number generatordone
Starting Firewall Initialization (phase 1 of 3) done
<notice>exit status of (random isdn SuSEfirewall2_init) is (0 0 0)
<notice>start services (network)
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8
done eth0 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
eth0 configuration: eth-id-00:e0:18:a0:a6:a2
eth0 Startmode is 'off'
skippedWaiting for mandatory devices: wlan-id-00:06:25:0d:9d:2d
19 17 13 9 6 5 3 2 1
wlan0 interface could not be set up
failedSetting up service network . . . . . . . . . . . . . . . .failed
<notice>exit status of (network) is (7)
<notice>start services (syslog)


by the way, I tried route -n again, this time I got a blank line (I can not think of anything I did to change the status from the previous)