![](https://seccdn.libravatar.org/avatar/c0357c4dae904473156360505aa76252.jpg?s=120&d=mm&r=g)
Hiya, I did reply to that message .. .. it'd help if you could tell me a little about the network you're trying to connect to. Does it use WEP? DHCP? sjb ------------------------------------------------------------------- My Network is a Netgear MR314 AP running Wep & Dhcp addressing, to a pcmcia MA401 wireless adapter. I use a 26 bit key for wep. Dre :-)
![](https://seccdn.libravatar.org/avatar/b91e6124f42121718bdabacefd040ed7.jpg?s=120&d=mm&r=g)
arawak wrote:
My Network is a Netgear MR314 AP running Wep & Dhcp addressing, to a pcmcia MA401 wireless adapter.
I use a 26 bit key for wep.
OK .. so the first part of your problem is to get an IP on wlan0. If DHCP isn't working for you, but for everybody else - I guess your WLAN card is using the wrong SSID, encryption key, channel, mode or combination thereof. Try iwconfig wlan0 essid "WLANName" channel 6 mode Managed rate auto enc KEY Replace the relavent bits above with the right values for your WLAN ;-) Then try "dhcpcd wlan0" If you still don't get an IP .. try setting one by hand using reasonable values for you WLAN .. e.g. ifconfig wlan0 192.168.0.2 netmask 255.255.255.0 If you're still geting nowhere, speak to whoever looks after the AP and ask them if it has a list of allowed MAC addresses or some other access mechanism enabled on it. After that, I'm out of ideas *8-) sjb
![](https://seccdn.libravatar.org/avatar/c0357c4dae904473156360505aa76252.jpg?s=120&d=mm&r=g)
OK .. so the first part of your problem is to get an IP on wlan0. If DHCP isn't working for you, but for everybody else - I guess your WLAN card is using the wrong SSID, encryption key, channel, mode or combination thereof. Try iwconfig wlan0 essid "WLANName" channel 6 mode Managed rate auto enc KEY Replace the relavent bits above with the right values for your WLAN ;-) Then try "dhcpcd wlan0" If you still don't get an IP .. try setting one by hand using reasonable values for you WLAN .. e.g. ifconfig wlan0 192.168.0.2 netmask 255.255.255.0 If you're still geting nowhere, speak to whoever looks after the AP and ask them if it has a list of allowed MAC addresses or some other access mechanism enabled on it. After that, I'm out of ideas *8-) sjb ------------------------------------------------------------------------ -- Tried the iwconfig stuff see below; linux:~ # iwconfig wlan0 essid Fireless channel 1 mode Managed rate auto enc £kings$6..,. Error for wireless request "Set ESSID" (8B1A) : SET failed on device wlan0 ; Function not implemented. ifconfig wlan0 192.168.0.2 netmask 255.255.255.0 worked but when I ping the gw 192.168.0.1 it failed with 'destination unreachable' What could I try now... Do you know what this means? Please don't give up on this as I can't ...;) Dre :)
![](https://seccdn.libravatar.org/avatar/8cf53a3d0edae578a2cb0d7c5e9cba69.jpg?s=120&d=mm&r=g)
On Wed, Oct 16, 2002 at 12:26:03AM +0100, arawak wrote: : : Tried the iwconfig stuff see below; : : linux:~ # iwconfig wlan0 essid Fireless channel 1 mode Managed rate auto : enc £kings$6..,. : Error for wireless request "Set ESSID" (8B1A) : : SET failed on device wlan0 ; Function not implemented. : : ifconfig wlan0 192.168.0.2 netmask 255.255.255.0 : : worked but when I ping the gw 192.168.0.1 it failed with : 'destination unreachable' : : What could I try now... : : Do you know what this means? : : Please don't give up on this as I can't ...;) I don't believe that prism2_cs implements all the wireless extensions, and thus iwconfig won't work. However, the fix is rather easy. Edit /etc/pcmcia/wlang-ng.opts. In the "INFRASTRUCTURE STATION START", change "DesiredSSID" to "" so that you can associate to *any* AP. Then you should be able to do a "./wlan-ng start wlan0" and have the card associate. From there set the ip address via DHCP or ifconfig. To have the interface start automagically, you'll need to create a "/etc/sysconfig/network/ifcfg-wlan-pcmcia-0" by hand (as far as I can tell YaST2 doesn't config wlan cards). Oh, and don't forget to create the symlink to "ifcfg-wlan-pcmcia". Mine reads as such: ---begin /etc/sysconfig/network/ifcfg-wlan-pcmcia-0 BOOTPROTO='dhcp' DHCLIENT_SET_DOWN_LINK='yes' REMOTE_IPADDR='' STARTMODE='hotplug' UNIQUE='' WIRELESS='yes' WIRELESS_ESSID='' WIRELESS_KEY='' WIRELESS_MODE='Automatic' WIRELESS_NICK='' WIRELESS_NWID='nomad' ---end /etc/sysconfig/network/ifcfg-wlan-pcmcia-0 This is based on the config for eth0 (orinoco_cs) that YaST2 did. I don't believe that the "WIRELESS*" stuff is needed since those are passed to iwconfig. But I'm too lazy to rip them out and verify. Hope this helps. --Jerry Open-Source software isn't a matter of life or death... ...It's much more important than that!
![](https://seccdn.libravatar.org/avatar/b91e6124f42121718bdabacefd040ed7.jpg?s=120&d=mm&r=g)
arawak wrote:
linux:~ # iwconfig wlan0 essid Fireless channel 1 mode Managed rate auto enc £kings$6..,. Error for wireless request "Set ESSID" (8B1A) : SET failed on device wlan0 ; Function not implemented.
Huh? OK, try (as a long shot) iwconfig wlan0 essid "Any" channel 1 mode Managed rate auto enc £kings$6..,. You're using the prism2 driver, yes? Do you have a wlan.conf file knocking around in /etc/pcmcia? I did mess around with the prism drivers a while ago, but I can't remember exactly how they set things up. Hang on .. .. I'm just looking at the latest wlan drivers. In the PCMCIA directory there are 3 files .. wlan-ng, wlan-ng.conf and wlan-ng.opts .. do you have those? sjb
participants (3)
-
arawak
-
Jerry A!
-
sjb