[Linux-wlan-ng-devel] Re: [Fwd: [lwlan-user] errors while attempting to run "make"]

[Dan Finn]

I setup the following in my /etc/network/interfaces file:

auto wlan0
iface wlan0 inet dhcp
         wireless_mode managed
         wireless_essid linksys
         wireless_rate 11M

and then when I run "ifup wlan0" I get the following errors:

Failed to enable the device, resultcode= implementation_failure .
run-parts: /etc/network/if-pre-up.d/linux-wlan-ng-pre-up exited with 
return code 1
Error for wireless request "Set Mode" (8B06) :
     SET failed on device wlan0 ; Operation not supported.
Error for wireless request "Set Bit Rate" (8B20) :
     SET failed on device wlan0 ; Function not implemented.
Error for wireless request "Set ESSID" (8B1A) :
     SET failed on device wlan0 ; Operation not supported.
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

sit0: unknown hardware address type 776
eth1: unknown hardware address type 24
SIOCSIFFLAGS: No such device
sit0: unknown hardware address type 776
eth1: unknown hardware address type 24
Listening on LPF/wlan0/00:00:00:00:00:00
Sending on   LPF/wlan0/00:00:00:00:00:00
Sending on   Socket/fallback/fallback-net
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
send_packet: Network is down
No DHCPOFFERS received.
No working leases in persistent database.

Exiting.


When I was asking about scanning I was asking about the ability of the 
card to be able to list what networks are available.

Robert Chéramy wrote:
> Hi,
> 
> (I maintain linux-wlan-ng-devel in Cc as it may interest other people.)
> 
> Dan Finn wrote:
> 
>>Do you know where I could find insturctions on setting my
>>/etc/network/interfaces file, or perhaps could you show me yours so that
>>I could get this card working.  Is there any way to do scanning with
>>this driver?
> 
> 
> Sure!
> 
> My config looks like this:
> 
> auto wlan0
> #iface wlan0 inet dhcp
> iface wlan0 inet static
>         address 192.168.0.10
>         netmask 255.255.255.0
>         gateway 192.168.0.1
>         wireless_mode managed
>         wireless_essid tibob
> #       wireless_enc off
>         wireless_enc on
>         wlan_ng_priv_key128 true
>         metric 5
> #       wlan_ng_priv_genstr 1234567890123
>         wlan_ng_key0 31:32:33:34:35:36:37:38:39:30:31:32
> 
> Some explanations here:
> - The config format is explained in
> /usr/share/doc/linux-wlan-ng/README.Debian.gz
> - I use an Access Point (use "ad-hoc" instread of managed if you make a
> p2p conection. And notice:
> # For ad-hoc mode, you must specify a channel.
> #       wireless_channel 1
> )
> - Getting WEP encryption to work was a big problem until I found out
> that linux-wlan-ng uses another encoding for the passkey (defined in
> wlan_ng_priv_genstr 1234567890123) that windows XP and my AP do.
> You can switch to the 13 digits (and define them using wlan_ng_key0).
> You can generate them using wepenc.c from the patch in
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=280013 . Avoid
> non-ascii caracters in the passkey as every OS encode them in another way...
> 
> Well, I hope it helps :-)
> 
> tibob
> 
> PS: I have no idea what scanning is...

-- 
Dan Finn
Unix System Administrator
Twelve Horses North America
Cell : 530.386.2618
Desk : 775.337.3336