Problems connecting to AP after reinstalling linux and driver

Henrik Gütle henrikg at fys.ku.dk
Mon Mar 22 04:57:21 EST 2004


After a lot of work I'm still unable to log on to any AP. Last time -
before 
reinstalling - I used hostap-diver-0.2.0 and I am pretty sure that the
"wifi 
device" didn't existed - just as it is the case for the 0.1.3 version.
So I 
thought that the 0.2.0 tarball has been modified since then. After
downloading older "0.2.0 branch" files, I still have this wifi device.
So it seems that this allways has been a part of the 0.2 branch, and so
this can't be the problem. 
Maybe my configuration file is wrong (see below). I don't use a key, but
this worked fine the last time (the APs aren't connected to the
network). 
Does someone have an idea, I'm running out of options...

\Henrik 

ifcfg-wlan0:
BOOTPROTO='dhcp'
DHCLIENT_SET_DOWN_LINK='yes'
MTU=''
REMOTE_IPADDR=''
STARTMODE='hotplug'
UNIQUE='K1pk.jrBDbmL7DWA'
WIRELESS_ESSID='Wireless DIKU'
WIRELESS_KEY=''
WIRELESS_MODE='Managed'
WIRELESS_NICK='Henrik'
WIRELESS_NWID=''
DHCLIENT_MODIFY_RESOLV_CONF='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'

iwconfig:
wlan0     IEEE 802.11b  ESSID:"Wireless DIKU"  Nickname:"Henrik"
          Mode:Managed  Frequency:2.467GHz  Access Point:
44:44:44:44:44:44  
          Bit Rate:2Mb/s   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0/92  Signal level:-69 dBm  Noise level:-90 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:54   Missed beacon:0

henrikg at fys.ku.dk said:

> After reinstalling my Suse 9.0 distribution, my Linksys WPC11
(firmware 
> 1.7.4) with hostap-driver 0.2.0 can't connect to any AP. The driver is

> loaded (se dmesg below), and iwconfig shows wlan0 and wifi. What is
wifi? 
> Befor reinstalling linux this interface wasn't there. Furthermore I
can't 
> find any configuration files for wifi, so how can it be "created"? But
maybe 
> this has nothing to do with my problem. I also tried hostap-driver
0.1.3 - 
> same result. Trying to change the AP manually didn't help.
> 
> \Henrik
> -------
> ifcfg-wlan0:
> BOOTPROTO='dhcp'
> DHCLIENT_SET_DOWN_LINK='yes'
> MTU=''
> REMOTE_IPADDR=''
> STARTMODE='hotplug'
> UNIQUE='K1pk.jrBDbmL7DWA'
> WIRELESS_ESSID='Wireless DIKU'
> WIRELESS_KEY=''
> WIRELESS_MODE='Managed'
> WIRELESS_NICK='Henrik'
> WIRELESS_NWID=''
> DHCLIENT_MODIFY_RESOLV_CONF='yes'
> DHCLIENT_SET_DEFAULT_ROUTE='yes'
> 
> -------
> dmesg:
> cs: memory probe 0xa0000000-0xa0ffffff: clean.
> hostap_crypt: registered algorithm 'NULL'
> hostap_cs: 0.2.0 - 2004-02-15 (Jouni Malinen <jkmaline at cc.hut.fi>)
> hostap_cs: setting Vcc=33 (constant)
> hostap_cs: CS_EVENT_CARD_INSERTION
> hostap_cs: setting Vcc=50 (from config)
> Checking CFTABLE_ENTRY 0x01 (default 0x01)
> IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
> io->flags = 0x0046, io.base=0x0000, len=64
> hostap_cs: Registered netdevice wifi0
> hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
> prism2_hw_init: initialized in 194 ms
> wifi0: NIC: id=0x801b v1.0.0
> wifi0: PRI: id=0x15 v1.1.1
> wifi0: STA: id=0x1f v1.7.4
> wifi0: registered netdevice wlan0
> wlan0 unsupported ioctl(0x89f1)
> prism2: wlan0: operating mode changed 3 -> 2
> wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
>    retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
>    A1=00:00:00:00:00:00 A2=00:06:25:16:c3:73 A3=ff:ff:ff:ff:ff:ff 
> A4=00:00:00:
> 00:00:00
> -----------
> 
> 
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 



-- 







More information about the HostAP mailing list