[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-wlan-user
Subject:    Re: [lwlan-user] (no subject)
From:       fmml () cedval ! org
Date:       2003-12-30 17:32:00
Message-ID: 62387.192.168.41.195.1072805520.squirrel () whoami3
[Download RAW message or body]

Hi TG,
When I put my AP in "Open" mode, I can connect no problem, the Wep is
giving me problems...

Seem that Suse has the configuration laid out differently, did put wep
related config in /etc/wlan/wlan.conf but that had no effect.  My feeling
is that Wep related config must be put in
/etc/sysconfig/network/ifcfg-wlan-pcmcia but I am not sure of the syntax.

I'll keep digging...

Thanks for your help,

Francois

> I think the problem is the name of the options (note the wlan_ng_zzz vs.
> wireless_zzz) ... below is from *Joey Hess* posted in Aug 2002.
>
> The specific instructions are for Debian, but hopefully it is obvious
> how to translate for SUSE.
>
> The options work for me using wlan-ng pre14 with 128bit wep.
>
>
> Tom Gordon
>
>
> Configuring a PCI device (or a pcmcia device) with
> /etc/network/interfaces:
> --------------------------------------------------------------------------
>
> Edit /etc/network/interfaces, and add a stanza for your network device.
> Here is a sample stanza, for the simplest possible configuration -- bring
> the device up, associating with any available wireless access point, and
> use dhcp to get on the network:
>
> auto wlan0
> iface wlan0 inet dhcp
> wireless_mode managed
> wireless_nick mylaptop
>
> Once you've edited this into /etc/network/interfaces, the command "ifup
> wlan0" should bring up your wireless.
>
> More complex configurations are of course possible. For a ad-hoc network,
> using static IP addresses:
>
> auto wlan0
> iface wlan0 inet static
> address 192.168.1.5
> gateway 192.168.1.1
> netmask 255.255.255.0
> wireless_mode ad_hoc
> wireless_essid mywlan
> wireless_nick mylaptop
> wireless_channel 1
>
> Here is an annotated list of all the available options (also see
> interfaces(5) for more details):
>
> # Should be either ad_hoc or managed. Used managed if you have an AP.
> wireless_mode managed
> # Leave this unset to associate with any access point. Set to pick an
> # access point, or in ad-hoc mode.
> # wireless_essid
> # A name for your machine. Required.
> wireless_nick mylaptop
> # For ad-hoc mode, you must specify a channel.
> # wireless_channel 1
> #
> # To enable WEP, uncomment the next line.
> # wireless_enc on
> # To set a WEP key, either use a string, which will be converted to a key:
> # wlan_ng_priv_genstr foo
> # (Using the specified key length.)
> # wlan_ng_priv_key128 false
> # Or give a file that contains such a string:
> # wlan_ng_keyfile /etc/network/wlan
> # Or set keys explicitly.
> # wlan_ng_key0 xx:xx:xx:xx:xx
> # wlan_ng_key1 xx:xx:xx:xx:xx
> # wlan_ng_key2 xx:xx:xx:xx:xx
> # wlan_ng_key3 xx:xx:xx:xx:xx
> # If you set a key, remember to make the file mode 600!
> #
> # In managed mode, set to "sharedkey" if a shared key is required.
> # wlan_ng_authtype opensystem
> # If you are serving as an AP, uncommnent this to require WEP for all
> STAs.
> # wlan_ng_exclude_unencrypted true
> #
> # Some extra ah-hoc mode settings:
> # Beacon interval (in Kus)
> # wlan_ng_bcint 100
> # Rates for mgmt&ctl frames (in 500Kb/s)
> # wlan_ng_basicrates 2 4
> # Supported rates in BSS (in 500Kb/s)
> # wlan_ng_oprates 2 4 11 22
> #
> # You can set arbitrary MIB items with this directive, separated by
> # whitespace. Each will then be set.
> # wlan_ng_user_mibs p2CnfRoamingMode=1
>
>
> fmml@cedval.org wrote:
>
>>Hi,
>>
>>I have just installed Suse 9 on a new laptop. I have a wireless network,
>>requiring 128 bit encryption with HEX key, a D-link Di-624 access point.
>>The Wifi net is of "Managed" type. I have 3 windoze station working on it
>>no problems.
>>
>>On the laptop, I have a PCMCIA D-Link (DWL-G650) card, that seems to
>> work,
>>respond to some iwconfig commands but won't connect.
>>
>>I see the following error in /var/log/messages:
>>
>>Dec 23 21:43:14 linux kernel: wlan0: authentication failed (reason 13)
>> for
>>00:05:5d:fa:ee:5e
>>
>>00:05:5d:fa:ee:5e is my access point address, so at least that works :-)
>>
>>Here is the content of /etc/sysconfig/network/ifcfg-wlan-pcmcia (key :
>>
>>BOOTPROTO='dhcp'
>>DHCLIENT_SET_DOWN_LINK='yes'
>>MTU=''
>>REMOTE_IPADDR=''
>>STARTMODE='hotplug'
>>UNIQUE='B35A.JnyZfOi_o6B'
>>WIRELESS_ESSID='alarm07'
>>WIRELESS_KEY='shared 72ed847ce25cc8667bb87a4d7c'  **
>>WIRELESS_MODE='Managed'
>>WIRELESS_NICK='whoami5'
>>WIRELESS_NWID=''
>>WIRELESS_FREQ=''
>>WIRELESS_CHANNEL="9"
>>WIRELESS_PEERDNS='no'
>>
>>** that is not my real key...
>>
>>Tried to force that config manually with iwconfig commands, same
>> results...
>>
>>
>>Any ideas?
>>
>>
>>Francois Meehan
>>
>>
>>_______________________________________________
>>Linux-wlan-user mailing list
>>Linux-wlan-user@lists.linux-wlan.com
>>http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user
>>
>>
>>
>
>
>
> _______________________________________________
> Linux-wlan-user mailing list
> Linux-wlan-user@lists.linux-wlan.com
> http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user
>
>
>

_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-user@lists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic