Hi all,

I'm using SuSE 8.2 with a WPC11 v.3 card that is supposed to work.. ( My laptop see it ) But when it comes the time to connect to the wireless router, there's nothing. I downloaded kwifimanager, the connection to my wireless is ultimate but I don't have a local IP, they say it's unavailable. And my access point is unknown. Do this problem is due to the fact that I did'nt know what to write in the wireless settings ? (Operating mode : ad-hoc, ESSID: nothing, NWID: nothing, Encryption key:nothing, Nickname: nothing) or is it because my card is a linksys and my router a networkeverywhere ? Don't forget that I am a newbie

Thanks in advance,

Alex Jacobson

Oh I forgot, my card and router use DHCP

I currently use D-Link, Belkin and SMC cards in conjunction with my SMC wireless router, all work correctly, WEP included.

So, I would guess the manufacturer mismatch is not the problem. Seems to me your problem is either with the hardware setup of your card or the configuration of it. If you'd like, I'd be interested in seeing the output from ifconfig -a and iwconfig.

Also, typically "ad-hoc" mode is for use when no router/access point is present, for use with an access point or router, you should use "managed" mode.

That's the output of ifconfig -a


eth0 Link encap:Ethernet HWaddr 00:B0:D0:A4:9B:36
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::2b0:d0ff:fea4:9b36/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:381 errors:0 dropped:0 overruns:0 frame:0
TX packets:436 errors:0 dropped:0 overruns:0 carrier:205
collisions:0 txqueuelen:100
RX bytes:142680 (139.3 Kb) TX bytes:60150 (58.7 Kb)
Interrupt:9 Base address:0xfc00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:60 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3912 (3.8 Kb) TX bytes:3912 (3.8 Kb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0 Link encap:Ethernet HWaddr 00:06:25:18:79:79
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:5 Base address:0x100


and for iwconfig,

lo no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.

wlan0 IEEE 802.11-b ESSID:""
Mode:Managed Frequency:2.462GHz Access Point: 00:06:25:07:68:7B
Bit Rate:2Mb/s Tx-Power:2346 dBm
Retry min limit:8 RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:92/92 Signal level:-40 dBm Noise level:-98 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

does someone can help me ?

OK, does your router have an ESSID? Have you enabled WEP on the router? If you don't have either of these set properly, you won't get an IP address.

When I boot up Knoppix on my desktop machine (normally it runs XP), I have to do the following:

iwconfig eth0 essid "ESSID NAME"
iwconfig eth0 key keyvalue

After that, I have wireless, no problem. You'll probably have to subsitute wlan0 for eth0.

Does'nt work either,

it says : SET failed on device wlan0 ; Function not implemented

Are you root when you try to use iwconfig?

Yup

Are you using the linux-wlan.net driver set? If so, if I remember right they still work by manipulating the setting in /etc/wlan/ and then hard restarting pcmcia. I don't think they've got wireless extensions support yet, am I wrong?

Cheers,

Finegan

That might explain it finegan. On my desktop, the wireless card is in a PCI slot, not pcmcia.

The important thing is, are you using the linux-wlan.net drivers? I'm assuming so, they're the only ones that come with SuSe and identify a wireless device as wlan0. If I remember this stuff right you have to modify the settings in /etc/wlan/wlan.conf and/or use wlanctl-ng, the linux-wlan drivers are, last I checked, still not compliant with wireless extensions and therefore don't work with "iwconfig" and its friends. Check through the documentation in /etc/wlan, its probably explained there.

Also, there are the orinoco drivers which also cover prism2 chipsets and work with normal "iwconfig" commands.

Cheers,

Finegan