Wireless network, Suse 10, Not getting IP addresse
 

Hi,

Using the kwifimanager I can see the name of the desired accesspoint, I can see the network, I can see a "blue square thing with computer image", I have an excellent signal strength, I have written the correct key in the configuration... still I get no ip address, this is what I get from ifconfig:

eth0 Link encap:Ethernet HWaddr 00:12:F0:E5:8B:D4
inet6 addr: fe80::212:f0ff:fee5:8bd4/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:282 errors:217 dropped:218 overruns:0 frame:0
TX packets:36 errors:0 dropped:90 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:864 (864.0 b)
Interrupt:10 Memory:b0106000-b0106fff

Please help :-)

I'm a total newbie at this too. I got wireless working on Suse 10.0 about an hour ago.

Here's what I did:

I got the firmware for my card (ipw2100) from SourceForge. All that was needed was the firmware. Ignore the rest of the instructions on the site.

I extracted the firmware into /lib/firmware and just let it sit there.

I then did "modprobe ipw2100" I don't know why, I just did. On previous failed setups, I would get an error message and then check dmesg to see what happened.

Go into yast2, and for the wireless network card (Network Devices -> Network Card -> [choose your wireless card].) There is a drop-down button on the bottom of the screen called "Advanced", click it and select "Detailed Settings". Set device activation to "On Cable Connection" Save everything and get out of yast.

Reboot.

That worked for me, but I'm not exactly sure why.

My ifconfig looked a lot like yours both before and after, but when I did iwconfig I keep getting "No wireless extensions" before this, now I get some info for the wireless adapter.

Good luck,
Bruce.

Im guessing it now works for you because you have installed the driver ... :-)

Driver seems fine at this computer - it simply just wont connect :( I have full signal strength - but no ip address, and I have tried all encryption modes possible :|

One thought -- I had to change the WEP encryption for 128 bit to 64 bit.

My next step would have been to open up the router and see what happened.

Good luck.
Bruce.

Thanks for the heads up on the 64/128, already tried it though ...

Dont have access to the router ... will try to get it. Thanks.

What is the output of iwconfig? From the sounds of it, it may be that you need to start DHCP on the wireless interface, eg
assuming eth0 is your wireless interface

eth0 IEEE 802.11b ESSID:"SPACE7"
Mode:Managed Frequency:2.442 GHz Access Point: 00:07:40:F1:B1:20
Bit Rate=11 Mb/s Tx-Power=20 dBm
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:3030-3030-3030-3030-3030-3030-3030-3030 Security mode:open
Power Management:off
Link Quality=94/100 Signal level=-28 dBm Noise level=-76 dBm
Rx invalid nwid:0 Rx invalid crypt:543 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:1208 Missed beacon:6


thanks

I have tried ifdown / ifup many times

This worked !!!

Right click the "KInternet - Internet Tool",
Choose "Wireless connection",
Click second tab - "scan for wireless networks
left click on the network you wish to use,
choose connect
insert wep key,

now you get the ip address :-) :-)

weeeeeeeeeeee