Re: [SLE] Wireless problems...

fmml_at_cedval.org
Date: 12/30/03

  • Next message: Russ: "Re: [SLE] Continuous Boot Loop" 
    Date: Tue, 30 Dec 2003 12:22:47 -0500 (EST)
To: suse-linux-e@suse.com

    Hi,

    I have configured my AP as open, then I could connect no problem. Seems
    that my problem is when I use wep and shared keys. Put my AP back with
    Wep, did the following mod to /etc/wlan/wlan.conf (configured my AP with
    new ascii key):

    #=======WEP===========================================
    # [Dis/En]able WEP. Settings only matter if PrivacyInvoked is true
    lnxreq_hostWEPEncrypt=true # true|false
    lnxreq_hostWEPDecrypt=true # true|false
    dot11PrivacyInvoked=true # true|false
    dot11WEPDefaultKeyID=0 # 0|1|2|3
    dot11ExcludeUnencrypted=true # true|false, in AP this means WEP is
    required.

    # If PRIV_GENSTR is not empty, use PRIV_GENTSTR to generate
    # keys (just a convenience)
    # add-ons/ in the tarball contains other key generators.
    PRIV_GENERATOR=/sbin/nwepgen # nwepgen, Neesus compatible
    PRIV_KEY128=false # keylength to generate
    PRIV_GENSTR=""

    # or set them explicitly. Set genstr or keys, not both.
    dot11WEPDefaultKey0=02:07:08:09:01:04:02:08:09:09:02:06:07
    dot11WEPDefaultKey1=
    dot11WEPDefaultKey2= # e.g. 01:20:03:40:05 or
    dot11WEPDefaultKey3= #
    01:02:03:04:05:06:07:08:09:0a:0b:0c:0d
    #=======SELECT STATION MODE===================
    IS_ADHOC=n # y|n, y - adhoc, n - infrastructure

    #======= INFRASTRUCTURE STATION ===================
    # What kind of authentication?
    AuthType="sharedkey" # opensystem | sharedkey (requires WEP)

    #======= ADHOC STATION ============================
    #BCNINT=100 # Beacon interval (in Kus)
    #CHANNEL=6 # DS channel for BSS (1-14, depends
                                    # on regulatory domain)
    #BASICRATES="2 4" # Rates for mgmt&ctl frames (in 500Kb/s)
    #OPRATES="2 4 11 22" # Supported rates in BSS (in 500Kb/s)

    But it does not seem to be in effect after I restart pcmcia and network,
    still iwconfig shows "Security mode:open", and I still have the following
    error in system log:

    Dec 30 12:15:59 linux kernel: wlan0: authentication failed (reason 13) for
    00:05:5d:fa:ee:5e

    Do I have to put Wep related statements in
    /etc/sysconfig/network/ifcfg-wlan-pcmcia to make it work and if so, what
    is the syntax? Can someone send me a configuration example?

    Thanks in advance,

    Francois

    > 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 72ed847ce25cc8667bb87a4d2d'
    > WIRELESS_MODE='Managed'
    > WIRELESS_NICK='whoami5'
    > WIRELESS_NWID=''
    > WIRELESS_FREQ=''
    > WIRELESS_CHANNEL="9"
    > WIRELESS_PEERDNS='no'
    >
    > Tried to force that config manually with iwconfig commands, same results...
    >
    >
    > Any ideas?
    >
    >
    > Francois Meehan
    >
    > --
    > Check the headers for your unsubscription address
    > For additional commands send e-mail to suse-linux-e-help@suse.com Also
    check the archives at http://lists.suse.com
    > Please read the FAQs: suse-linux-e-faq@suse.com
    >
    >
    >
    >
    > 

    -- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: Russ: "Re: [SLE] Continuous Boot Loop"

    Relevant Pages

    • [SLE] Ensuring wlan connection is encrypted
      ... use WEP encryption, just so that traffic between the machines has some form ... the pcs - details below with keys altered... ... if WEP is enabled? ...
      (SuSE)
    • Re: ath(4) driver problems with WEP...
      ... that the WEP key is correct. ... I just committed a fix to ifconfig to correctly handle ... 128-bit WEP keys. ... FWIW I enabled turbo mode with: ...
      (freebsd-current)
    • Re: Is Dynamic WEP Secure Enough?
      ... Forgive me for my ignorance and please correct me if I am wrong OR if I have wrongly understood these/ any of the replies to the Dynamic WEP question ... different users changing their keys at different points in time ... The physical security that is existing on the ground that can contribute and hence the probability of finding out a parking lot hacker ... WEP can be cracked in less than ten minutes (even on a network without ...
      (Security-Basics)
    • Re: how do I secure my Wi-Fi network
      ... The older standard, 802.11b has an encryption scheme called WEP, ... which uses keys of either 64bit or 128bit. ... > I want to switch my network from cable to wireless. ... > wireless networks to log on, ...
      (microsoft.public.windowsxp.network_web)
    • Re: Astaro <-> CyberGuard VPN connection
      ... The Keys can be pre-shared or RSA keys - I have tried both w/o sucess. ... but have probably confused something because the configuration differs ... ISAKMP Settings ... Key lifetime: 7800 ...
      (comp.security.firewalls)