From p.kral  Sun Dec  1 12:29:39 2002
From: p.kral (=?iso-8859-2?Q?Pavel_Kr=E1l?=)
Date: Sun, 1 Dec 2002 21:29:39 +0100
Subject: HostAp <-> Atmel AP
Message-ID: <007201c29978$60015320$18762093@wintermute>

Hi,

this week I tried to manage connection between HostAP and Atmel based
hw AP. Configuration was

kernel 2.4.19-pre11 with latest wireless extension patch (25)
latest hostap from cvs
PCI card SparcLan WL-360F with PRI 1.0.0, SEC 1.5.6
AP SparcLan WX-1590 with atmel fw 1.4j1

Setup hostap to Managed mode and SparcAP to Master worked correctly,
but it's not interresting, isn't it ? :) Well, I tried hostap in
Master(hostap) mode and SparcAP in Managed mode or set up wireless
bridge between them
(ie prism2_param wds_type 4, iwpriv add_wds, brctl ... on hostap side
and 'wireless bridge' option on sparc_ap side) with same result:

hostap wlan0 has 192.168.5.200
sparc_ap has 192.168.5.100
host connected thought wired link to sparc_ap has 192.168.5.2

ping from host -> sparc_ap went ok (wired),
ping from hostap -> sparc_ap went ok (wireless),
however ping from hostap -> host (or reverse) din't work (even thought
'link' LED on SparcAP (and LED on host PCI LAN card) blink
concurrently with ICMP packet sending)

It is probably firmware problem, however could somebody give me point,
how to dig in and try debug what can be wrong?

Regards,
Pavel




From behroozi  Sun Dec  1 16:54:15 2002
From: behroozi (Cyrus Behroozi)
Date: 01 Dec 2002 16:54:15 -0800
Subject: [PATCH] HostAP/Cisco VPN compatibility
Message-ID: <1038790455.7681.19.camel@daim>

I finally discovered why my laptop could connect fine to our VPN using
Cisco and Lucent wireless cards but not with its built-in PRISM card
running HostAP. The Cisco-supplied VPN client was objecting to devices
that weren't named "ethX"!

Attached is a patch for the 2002-12-01 CVS driver. I added a module
parameter called device_name, similar to the eth parameter in wvlan_cs.
If device_name = 0 (default), the device is called "wlanX"; if it's 1
the device is called "ethX". I haven't tested the patched driver with
anything except a MiniPCI card.

The working setup:
Cisco 3000 series VPN concentrator
IBM ThinkPad X22 with Actiontec 802.11b MiniPCI card
Cisco Systems VPN Client Version 3.7 (vpnclient-linux-3.7.Rel-k9.tar.gz)
Kernel 2.4.20
HostAP driver from CVS, patched

--Cyrus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: device_name.diff
Type: text/x-patch
Size: 1155 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20021201/6833c7a0/attachment.bin 


From muditgoel  Sun Dec  1 17:03:41 2002
From: muditgoel (Mudit Goel)
Date: Sun, 1 Dec 2002 17:03:41 -0800 (PST)
Subject: Cannot detect hostap based AP
Message-ID: <20021202010341.81092.qmail@web13104.mail.yahoo.com>

I am trying to run hostap on a linux based laptop with
a proxim RangeLAN-DS/LAN pc card; but my other windows
based laptop with a 3Com 3CRWE62092A pcmcia card does
not detect the network.

I donot get any errors (that I know of) when I insert
the proxim card. Also an iwconfig wlan0 returns:

wlan0     IEEE 802.11-b  ESSID:"test"
Mode:Master  Frequency:2.422GHz  Access Point:
00:60:B3:67:2E:77
Bit Rate:11Mb/s   Tx-Power:-7 dBm   Sensitivity=1/3
Retry min limit:8   RTS thr:off   Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0  Signal level:0  Noise level:0
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid
frag:0
Tx excessive retries:0  Invalid misc:0   Missed
beacon:0


As far as I know I dont see any problems here either.

Can anyone please tell me how to troubleshoot it?

My hardware configuration for hostap:
My laptop is a toshiba 1555cdc laptop.
I initially installed mandrake 8.1, compiled linux
kernel 2.4.20-pre9 (2.4.19 with patches), compiled and
added pcmcia-cs 3.1.31 outside the kernel and am using
hostap-2002-10-12.

Please let me know if I can provide any additional
information.

Thanks,
Mudit

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com



From jkmaline  Sun Dec  1 17:12:32 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 1 Dec 2002 17:12:32 -0800
Subject: Cannot detect hostap based AP
In-Reply-To: <20021202010341.81092.qmail@web13104.mail.yahoo.com>
References: <20021202010341.81092.qmail@web13104.mail.yahoo.com>
Message-ID: <20021202011232.GA4549@jm.kir.nu>

On Sun, Dec 01, 2002 at 05:03:41PM -0800, Mudit Goel wrote:

> As far as I know I dont see any problems here either.
> 
> Can anyone please tell me how to troubleshoot it?

Do you get any error messages from the kernel driver (in 'dmesg' output)
during initialization or when the station be trying to associate? Which
firmware version does your card have? If you don't find any error
messages, please send output of 'utils/hostap_diag wlan0 -ru' to me for
further analysis.

-- 
Jouni Malinen                                            PGP id EFC895FA



From hazard  Sun Dec  1 17:15:31 2002
From: hazard (Vladimir Ivaschenko)
Date: Mon, 2 Dec 2002 03:15:31 +0200
Subject: [PATCH] HostAP/Cisco VPN compatibility
In-Reply-To: <1038790455.7681.19.camel@daim>
References: <1038790455.7681.19.camel@daim>
Message-ID: <20021202031531.A21141@hzdhome.home.blkseanet.ru>

IMHO you could work around this problem in much simpler way - using
something similar to "ip link set wlan0 name eth1" 

Sun, Dec 01, 2002 at 04:54:15PM -0800 Cyrus Behroozi wrote about [PATCH] HostAP/Cisco VPN compatibility

> I finally discovered why my laptop could connect fine to our VPN using
> Cisco and Lucent wireless cards but not with its built-in PRISM card
> running HostAP. The Cisco-supplied VPN client was objecting to devices
> that weren't named "ethX"!
> 
> Attached is a patch for the 2002-12-01 CVS driver. I added a module
> parameter called device_name, similar to the eth parameter in wvlan_cs.
> If device_name = 0 (default), the device is called "wlanX"; if it's 1
> the device is called "ethX". I haven't tested the patched driver with
> anything except a MiniPCI card.

-- 
Best Regards
Vladimir Ivaschenko
http://www.hazard.maks.net/



From jkmaline  Sun Dec  1 17:25:48 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 1 Dec 2002 17:25:48 -0800
Subject: 802.1x Support
In-Reply-To: <000e01c298a4$aa7f8ea0$090b7883@buffaloberry>
References: <000e01c298a4$aa7f8ea0$090b7883@buffaloberry>
Message-ID: <20021202012548.GB4549@jm.kir.nu>

On Sat, Nov 30, 2002 at 11:14:11AM -0800, Selcuk OZTURK wrote:

> I have RH 7.2 working on 2.4.20pre11 kernel. I'm using D-link DWL650
> Wireless NIC. I can run hostapd but when I try to connect my hostapd
> with a Radius Server to support 802.1x Authentication, I got this
> error..

Do you mean that you can successfully associate a station with hostapd
if you are not using 1x?

> >> ./hostapd -x -o xxx.xxx.xxx.xxx -a xxx.xxx.xxx.xxx. -s xxxx  wlan0 
> 
>   Using interface wlan0ap with hwaddr xxxxxxxxxxxx and ssid xxxxx
>   ioctl [ PRISM_IOCTL_PRISM2_PARAM] : Operation not supported
>   Could not setup IEEE 802.1X support in kernel driver.

That's odd.. Which version of the driver are you using? Are you using
the driver and hostapd from the same version (i.e., one should not mix
two different versions of driver/hostapd)? Do you see anything in
'dmesg' output from the driver? Can you run minimal EAP authentication
in hostapd (i.e., without external RADIUS server) with 'hostapd -xm
wlan0'?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec  1 17:51:38 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 1 Dec 2002 17:51:38 -0800
Subject: [PATCH] HostAP/Cisco VPN compatibility
In-Reply-To: <1038790455.7681.19.camel@daim>
References: <1038790455.7681.19.camel@daim>
Message-ID: <20021202015138.GA15936@jm.kir.nu>

On Sun, Dec 01, 2002 at 04:54:15PM -0800, Cyrus Behroozi wrote:

> I finally discovered why my laptop could connect fine to our VPN using
> Cisco and Lucent wireless cards but not with its built-in PRISM card
> running HostAP. The Cisco-supplied VPN client was objecting to devices
> that weren't named "ethX"!
> 
> Attached is a patch for the 2002-12-01 CVS driver.

So, Cisco VPN client does not work over PPP either? I would suggest
patching that client and not Host AP driver. If you need to work around
this, I would agree with Vladimir. Please, just rename the interface
after Host AP driver has initialized it. This does not need any extra
code in the driver.

-- 
Jouni Malinen                                            PGP id EFC895FA



From ebike  Sun Dec  1 19:39:21 2002
From: ebike (Bernard mentink)
Date: Mon, 02 Dec 2002 16:39:21 +1300
Subject: My wlan0 interface drops after a couple of secs
Message-ID: <3DEAD5E9.5060601@paradise.net.nz>

Hi All,

I have been using the HostAP driver with kismet in monitor mode, and 
every now and again the interface drops.
I.E ifconfig shows no wlan0, to fix I have to do an ifup wlan0, then it 
is fine.

It happens intermittantly, so am at a loss to debug it.

Cheers,
Bernie Mentink




From lists  Mon Dec  2 07:12:59 2002
From: lists (Chincogan Network Services Lists)
Date: Tue, 3 Dec 2002 02:12:59 +1100
Subject: wlan0 Interface seems to freeze.
Message-ID: <20021203021259.3053bdfe.lists@chincogan.net.au>

Hi List,

I have a problem where my wlan0 interface seems to freeze, a dmesg shows pages and pages of this:
wlan0: prism2_tx: hw not ready - skipping
wlan0: prism2_tx: hw not ready - skipping

Doing a "iwpriv wlan0 reset 1" does nothing, to fix this I have to restart pcmcia. Sometimes this problem will leave us for a couple of days other times this will happen multiple times a day.

This afternoon I am going to change this card with a Dlink DWL-520 to see if that makes any difference.

My Setup:
Hostap 2002-10-12
Kernel 2.4.19
Pcmcia_cs 3.2.1
Compaq WL-200

Once I change the card I will not be using pcmcis_cs anymore as the DWL-520 is a PCI based prism 2.5 chipset.
Does anyone have any ideas why this could be happening? I hope it goes away with the new card because it is really starting to get annoying.

Thanks,
Aaron Daniels



From victor.aleo  Mon Dec  2 02:07:58 2002
From: victor.aleo (Victor Aleo)
Date: Mon, 02 Dec 2002 11:07:58 +0100
Subject: Tx problem
Message-ID: <3DEB30FE.5050008@estudiant.upc.es>

Hi all,

I have a problem when the AP sends a "Disassociation" frame to a 
station. It happens sometimes that the station resets by itself. This is 
the output from the driver:

kernel: wlan1: prism2_tx - to BAP0 failed
kernel: hostap_pci: wlan1: resetting card
kernel: could not get TXEXC txframe
kernel: hostap_pci: wlan1: resetting card

where BAP stands for: Buffer Access Path (BAP). I really do not know 
what exactly is the problem. Do you think it is related with the 
firmware or with the Prism2 driver?

I would appreciate any suggestions or comments about it,

Thanks

Victor




From victor.aleo  Mon Dec  2 02:30:48 2002
From: victor.aleo (Victor Aleo)
Date: Mon, 02 Dec 2002 11:30:48 +0100
Subject: Tx problem
References: <3DEB30FE.5050008@estudiant.upc.es>
Message-ID: <3DEB3658.5060607@estudiant.upc.es>

Just another comment: wlan1 device is the station interface and this 
behaviour only happens when the station is tx data when the 
"Disassociation" message is received.

Victor Aleo wrote:

> Hi all,
>
> I have a problem when the AP sends a "Disassociation" frame to a 
> station. It happens sometimes that the station resets by itself. This 
> is the output from the driver:
>
> kernel: wlan1: prism2_tx - to BAP0 failed
> kernel: hostap_pci: wlan1: resetting card
> kernel: could not get TXEXC txframe
> kernel: hostap_pci: wlan1: resetting card
>
> where BAP stands for: Buffer Access Path (BAP). I really do not know 
> what exactly is the problem. Do you think it is related with the 
> firmware or with the Prism2 driver?
>
> I would appreciate any suggestions or comments about it,
>
> Thanks
>
> Victor
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>

-- 
Victor Aleo Monteagudo
Phone: 087521809
Mobile: (+46)0704485787
Forskarbacken 04-320
104 05 Stockholm (Sweden)
e-mail: victor.aleo at estudiant.upc.es, victor.aleo at swipnet.se






From jkmaline  Mon Dec  2 06:40:20 2002
From: jkmaline (Jouni Malinen)
Date: Mon, 2 Dec 2002 06:40:20 -0800
Subject: Tx problem
In-Reply-To: <3DEB30FE.5050008@estudiant.upc.es>
References: <3DEB30FE.5050008@estudiant.upc.es>
Message-ID: <20021202144020.GA1096@jm.kir.nu>

On Mon, Dec 02, 2002 at 11:07:58AM +0100, Victor Aleo wrote:

> I have a problem when the AP sends a "Disassociation" frame to a 
> station. It happens sometimes that the station resets by itself. This is 
> the output from the driver:
> 
> kernel: wlan1: prism2_tx - to BAP0 failed
> kernel: hostap_pci: wlan1: resetting card
> kernel: could not get TXEXC txframe
> kernel: hostap_pci: wlan1: resetting card

I have seen some TX failures with the latest code too; although mostly
on AP.

> where BAP stands for: Buffer Access Path (BAP). I really do not know 
> what exactly is the problem. Do you think it is related with the 
> firmware or with the Prism2 driver?

I would guess that it is the driver this time (or driver not able to
perform some workaround ;-). New TX/RX handling in tasklet may have
broken some locking etc. and that TXEXC frame might interrupt sending of
the new frame etc. They are using different BAPs, but at least with
hostap_pci there is a known hardware issue that should be worked around
when using both BAP0 and BAP1. I might eventually have to start using
only one BAP to get rid of these problems. I will be debugging this in
the near future..

-- 
Jouni Malinen                                            PGP id EFC895FA



From BichotG  Mon Dec  2 08:05:13 2002
From: BichotG (Bichot Guillaume Princeton)
Date: Mon, 2 Dec 2002 11:05:13 -0500 
Subject: Multicast with Linksys PCI WMP11 AP and PCMCIA WPC 11 ver 3
Message-ID: <FB52B3CCAE26D41181E800508B6D91EB02AFD76F@INDYEXCH23>

> 
> On Wed, Nov 27, 2002 at 10:10:14AM -0500, Bichot Guillaume 
> (Princeton) wrote:
> 
> > I'm making some measurement in multicast/broadcast mode having one 
> > server sending some multicast UDP traffic through a Linksys 
> WMP 11 PCI 
> > - Hostap - AP. The client is either the ipaq 3850 under 
> Familiar 0.5.3 
> > or a laptop under Linux redhat 8.0. Both uses a Linksys WPC 
> 11 PCMCIA 
> > card (manfid 0x274, 0x1613).
> > 
> > With the ipaq:
> > The hostap driver simply does not work with the linksys card (it 
> > supposed to work with this card). I got the following error:
> > hostap_cs: card initialization timed out
> > Hostap_cs: initialization failed
> 
> Does the same linksys card work in the laptop? Linksys WPC11 
> Ver3 should work fine with Host AP driver, but I have not 
> tested the latest version of the driver with ARM platform. Do 
> you see any other error messages in the kernel log ('dmesg')?

[Guilaume] Yes the same linksys card works with the laptop. 
It used to work with an old IPAQ though many Tx timeouts(ipaq 3635 , bootldr
2.18.01, Familiar 0.5.3). It does not work with the current one (ipaq 3870,
bootldr 2.18.54, Familiar 0.5.3)
Extra messages are (I do not have dmesg in the ipaq):
Wlan0: hfa384x_set_rid - to BAPA0 failed
hostap_cs: wlan0: resetting card

> 
> > With the laptop:
> > The average association time (i.e. the client detects and 
> associates 
> > with the AP)is 10 seconds between 256 Kbit/s and 1 Mbit/s. With a 
> > 2Mbit/s throughput it becomes impossible to associate with the AP.
> 
> Lot of date traffic in the network will result in association 
> problems since most stations seem to use quite strict limits 
> on how long time receiving of the auth/assoc reply can take. 
> If you upgrade your AP to use latest CVS version, you should 
> be able to see whether the station is acknowledging 
> auth/assoc replies (if not, the delay was probably too long).
> 
> At the moment, the driver does not prioritize outgoing frames 
> at all, but I might need to do this at some point to help 
> association under heavy load. It should help, if the AP would 
> simply by-pass any outgoing queue of data frames when sending 
> auth/assoc replies. There can still be some frames buffered 
> in the wlan card, but at least the host-side queue would not 
> be adding latency. In addition, number of buffered frames in 
> the wlan card could be reduced, if needed.
> 
> > I've tried the iwpriv command to decrease the beacon period 
> but I got 
> > the
> > following: 
> > 
> > # iwpriv wlan0 prism2_param wlan0 beacon_int 1
> > # Interface doesn't accept private ioctl
> > # prism2_param (8BE0): Operation not supported
> 
> That command is not correct. It should be either 'iwpriv 
> wlan0 beacon_int #' or 'prism2_param wlan0 beacon_int #' (if 
> iwpriv/wireless_ext does not support extended iwpriv 
> commands). In addition, you should note that setting beacon 
> interval to 1 would mean that the AP would be sending about 
> 1000 beacons per second in addition to all other traffic and 
> that might already be enough to prevent association..

Thanks. Sure 1 is not exactly the good value.
Currently I'm running wvlan_cs that is the only driver that works with my
ipaq (orinoco_cs does not work). I've constated a 20% packet loss in
multicast whatever the bit rate.

Guillaume
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021202/e74e1937/attachment.htm 


From ian.cass  Mon Dec  2 08:50:49 2002
From: ian.cass (Ian Cass)
Date: Mon, 2 Dec 2002 16:50:49 -0000
Subject: HostAP Drivers with non-Prism2
Message-ID: <06b101c29a22$f8018550$4c28a8c0@cblan.mblox.com>

Hi,

I'm aware that only Prism2 supports host ap mode, however the documentation
says the following....

In addition to Intersil's Prism2/2.5 chipsets, this driver may partly
support other chipsets. As far as I know, other chipsets do not have
Host AP mode, so this is not supported, but managed mode (i.e., being
a station in a BSS) seems to work with Prism1 (e.g., Intel, 3Com, and
Symbol cards) and Lucent WaveLAN.

I have a Prism 1 card (Zoomair 4000) and for reasons of sanity I'd rather
like to use the same drivers as my Prism2 card. I know the old card won't
work in Host AP mode, but if I could get it to work in Ad-Hoc mode, that'd
be cool. How can I get the host_ap drivers to even 'partly' support the old
Prism1 card?

Relevant part of /var/log/syslog below.

--
Ian Cass

Dec  2 16:37:37 defender cardmgr[194]: watching 2 sockets
Dec  2 16:37:37 defender cardmgr[194]: Card Services release does not match
Dec  2 16:37:37 defender kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Dec  2 16:37:37 defender kernel: cs: IO port probe 0x0800-0x08ff: clean.
Dec  2 16:37:37 defender kernel: cs: IO port probe 0x0100-0x04ff: excluding
0x220-0x22f 0x330-0x337 0x378-0
x37f 0x388-0x38f 0x4d0-0x4d7
Dec  2 16:37:37 defender kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Dec  2 16:37:37 defender kernel: cs: memory probe 0x0d0000-0x0dffff: clean.
Dec  2 16:37:37 defender cardmgr[194]: socket 0: ZoomAir 4000 2Mb/s WLAN
Card
Dec  2 16:37:37 defender cardmgr[194]: executing: 'modprobe hostap_cs'
Dec  2 16:37:38 defender kernel: hostap_crypt: registered algorithm 'NULL'
Dec  2 16:37:38 defender kernel: hostap_cs: hostap_cs.c 0.0.0 CVS (SSH
Communications Security Corp, Jouni
Malinen)
Dec  2 16:37:38 defender kernel: hostap_cs: (c) Jouni Malinen
<jkmaline at cc.hut.fi>
Dec  2 16:37:39 defender kernel: hostap_cs: setting Vcc=33 (constant)
Dec  2 16:37:39 defender kernel: hostap_cs: CS_EVENT_CARD_INSERTION
Dec  2 16:37:39 defender kernel: prism2_config()
Dec  2 16:37:39 defender kernel: hostap_cs: setting Vcc=50 (from config)
Dec  2 16:37:39 defender kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
Dec  2 16:37:39 defender kernel: IO window settings: cfg->io.nwin=1
dflt.io.nwin=1
Dec  2 16:37:39 defender kernel: io->flags = 0x0024, io.base=0x0000, len=16
Dec  2 16:37:39 defender kernel: hostap_cs: index 0x01: Vcc 5.0, irq 3, io
0x0100-0x010f
Dec  2 16:37:39 defender cardmgr[194]: executing: './network start wlan0'
Dec  2 16:37:39 defender kernel: hostap_cs: Registered netdevice wlan0
Dec  2 16:37:39 defender kernel: prism2_hw_init()
Dec  2 16:37:39 defender kernel: wlan0: hfa384x_cmd - timeout - reg=0x8000
Dec  2 16:37:39 defender kernel: hostap_cs: first command failed - is the
card compatible?
Dec  2 16:37:39 defender kernel: hostap_cs: Initialization failed
Dec  2 16:37:39 defender cardmgr[194]: + usage: /sbin/cardctl command
[socket #]
Dec  2 16:37:39 defender cardmgr[194]: +     or /sbin/cardctl [-c
configpath] [-f scheme] [-s stab] scheme
[name]
Dec  2 16:37:39 defender cardmgr[194]: +     commands: status config ident
suspend resume reset eject inser
t
Dec  2 16:37:39 defender ntpd[214]: ntpd 4.1.0 Mon Mar 25 23:39:47 UTC 2002
(2)
Dec  2 16:37:40 defender kernel: prism2: wlan0: operating mode changed 3 ->
1
Dec  2 16:37:40 defender kernel: wlan0: hfa384x_setup_bap - timeout before
Dec  2 16:37:40 defender kernel: wlan0: hfa384x_set_rid (rid=fc00, len=2) -
failed - res=-110
Dec  2 16:37:40 defender cardmgr[194]: + /sbin/iwconfig wlan0 mode Ad-Hoc
Dec  2 16:37:40 defender cardmgr[194]: + Error for wireless request "Set
Mode" (8B06) :
Dec  2 16:37:40 defender cardmgr[194]: +     SET failed on device wlan0 ;
Operation not supported.
Dec  2 16:37:40 defender kernel: wlan0: hfa384x_setup_bap - timeout before
Dec  2 16:37:40 defender kernel: wlan0: hfa384x_set_rid (rid=fc0e, len=34) -
failed - res=-110
Dec  2 16:37:40 defender ntpd[214]: signal_no_reset: signal 13 had flags
4000000
Dec  2 16:37:40 defender ntpd[214]: precision = 17 usec
Dec  2 16:37:40 defender ntpd[214]: kernel time discipline status 0040
Dec  2 16:37:40 defender ntpd[214]: getconfig: Couldn't open </etc/ntp.conf>
Dec  2 16:37:40 defender cardmgr[194]: + /sbin/iwconfig wlan0 channel 1
Dec  2 16:37:40 defender cardmgr[194]: + Error for wireless request "Set
Frequency" (8B04) :
Dec  2 16:37:40 defender cardmgr[194]: +     SET failed on device wlan0 ;
Invalid argument.
Dec  2 16:37:40 defender kernel: wlan0: hfa384x_setup_bap - timeout before
Dec  2 16:37:40 defender kernel: wlan0: hfa384x_set_rid (rid=fc84, len=2) -
failed - res=-110
Dec  2 16:37:40 defender kernel: wlan0: TXRateControl setting to 0xf failed
Dec  2 16:37:40 defender /usr/sbin/cron[230]: (CRON) INFO (pidfile fd = 3)
Dec  2 16:37:41 defender /usr/sbin/cron[236]: (CRON) STARTUP (fork ok)
Dec  2 16:37:41 defender kernel: hostap_crypt: registered algorithm 'WEP'
Dec  2 16:37:41 defender /usr/sbin/cron[236]: (CRON) INFO (Running @reboot
jobs)
Dec  2 16:37:41 defender kernel: wlan0: hfa384x_cmd_issue: cmd reg was busy
for 1000 usec
Dec  2 16:37:41 defender kernel: wlan0: hfa384x_cmd_issue - timeout -
reg=0x8000
Dec  2 16:37:41 defender kernel: wlan0: hfa384x_cmd: entry still in list?
(entry=c25121e0, type=0, res=-1)
Dec  2 16:37:41 defender kernel: wlan0: hfa384x_cmd: interrupted; err=-110
Dec  2 16:37:41 defender kernel: wlan0: hfa384x_get_rid: CMDCODE_ACCESS
failed (res=-110, rid=fc28, len=2)
Dec  2 16:37:41 defender kernel: Could not read current WEP flags.
Dec  2 16:37:41 defender kernel: wlan0: encryption setup failed
Dec  2 16:37:41 defender kernel: set_encryption or reset_port failed
Dec  2 16:37:41 defender cardmgr[194]: + /sbin/iwconfig wlan0 key
s:defender-plexus1
Dec  2 16:37:41 defender cardmgr[194]: + Error for wireless request "Set
Encode" (8B2A) :
Dec  2 16:37:41 defender cardmgr[194]: +     SET failed on device wlan0 ;
Invalid argument.
Dec  2 16:37:41 defender cardmgr[194]: + /sbin/iwconfig wlan0 essid
"defender-plexus.backbone.kentwireless.
net"
Dec  2 16:37:41 defender cardmgr[194]: + Error for wireless request "Set
ESSID" (8B1A) :
Dec  2 16:37:41 defender cardmgr[194]: +     argument too big (max 32)
Dec  2 16:37:42 defender kernel: wlan0: prism2_open
Dec  2 16:37:42 defender kernel: wlan0: hfa384x_cmd_issue: cmd reg was busy
for 1000 usec
Dec  2 16:37:42 defender kernel: wlan0: hfa384x_cmd_issue - timeout -
reg=0x8000
Dec  2 16:37:42 defender kernel: wlan0: hfa384x_cmd: entry still in list?
(entry=c25121e0, type=0, res=-1)
Dec  2 16:37:42 defender kernel: wlan0: hfa384x_cmd: interrupted; err=-110
Dec  2 16:37:42 defender kernel: wlan0: MAC port 0 enabling failed
Dec  2 16:37:42 defender kernel: wlan0: could not enable MAC port
Dec  2 16:37:42 defender kernel: wlan0: prism2_close
Dec  2 16:37:42 defender cardmgr[194]: + /sbin/ifconfig wlan0 up
192.168.2.254 netmask 255.255.255.0 broadc
ast 192.168.2.255
Dec  2 16:37:42 defender cardmgr[194]: + SIOCSIFFLAGS: No such device
Dec  2 16:37:42 defender cardmgr[194]: + /sbin/route add -net 192.168.2.0
netmask 255.255.255.0 dev wlan0
Dec  2 16:37:42 defender cardmgr[194]: + SIOCADDRT: Network is down





From tony  Mon Dec  2 09:08:26 2002
From: tony (Tony Toole)
Date: Mon, 2 Dec 2002 09:08:26 -0800
Subject: HostAP Drivers with non-Prism2
References: <06b101c29a22$f8018550$4c28a8c0@cblan.mblox.com>
Message-ID: <107b01c29a25$6e455460$114c35d1@tonyxp>

Hello Ian,

These cards are not command-compatible with Prism-II cards, and require a
seperate driver.

If your card uses and AMD firmware, you may need to download the legacy
driver from linux-wlan.com, otherwise you can use the 2MB driver we wrote
for Teletronics which is hosted on their site.  The driver has Access Point
mode.

Thanks,
Tony Toole

----- Original Message ----- 
From: "Ian Cass" <ian.cass at mblox.com>
To: <hostap at shmoo.com>
Sent: Monday, December 02, 2002 8:50 AM
Subject: HostAP Drivers with non-Prism2


> Hi,
>
> I'm aware that only Prism2 supports host ap mode, however the
documentation
> says the following....
>
> In addition to Intersil's Prism2/2.5 chipsets, this driver may partly
> support other chipsets. As far as I know, other chipsets do not have
> Host AP mode, so this is not supported, but managed mode (i.e., being
> a station in a BSS) seems to work with Prism1 (e.g., Intel, 3Com, and
> Symbol cards) and Lucent WaveLAN.
>
> I have a Prism 1 card (Zoomair 4000) and for reasons of sanity I'd rather
> like to use the same drivers as my Prism2 card. I know the old card won't
> work in Host AP mode, but if I could get it to work in Ad-Hoc mode, that'd
> be cool. How can I get the host_ap drivers to even 'partly' support the
old
> Prism1 card?
>
> Relevant part of /var/log/syslog below.
>
> --
> Ian Cass
>
> Dec  2 16:37:37 defender cardmgr[194]: watching 2 sockets
> Dec  2 16:37:37 defender cardmgr[194]: Card Services release does not
match
> Dec  2 16:37:37 defender kernel: cs: IO port probe 0x0c00-0x0cff: clean.
> Dec  2 16:37:37 defender kernel: cs: IO port probe 0x0800-0x08ff: clean.
> Dec  2 16:37:37 defender kernel: cs: IO port probe 0x0100-0x04ff:
excluding
> 0x220-0x22f 0x330-0x337 0x378-0
> x37f 0x388-0x38f 0x4d0-0x4d7
> Dec  2 16:37:37 defender kernel: cs: IO port probe 0x0a00-0x0aff: clean.
> Dec  2 16:37:37 defender kernel: cs: memory probe 0x0d0000-0x0dffff:
clean.
> Dec  2 16:37:37 defender cardmgr[194]: socket 0: ZoomAir 4000 2Mb/s WLAN
> Card
> Dec  2 16:37:37 defender cardmgr[194]: executing: 'modprobe hostap_cs'
> Dec  2 16:37:38 defender kernel: hostap_crypt: registered algorithm 'NULL'
> Dec  2 16:37:38 defender kernel: hostap_cs: hostap_cs.c 0.0.0 CVS (SSH
> Communications Security Corp, Jouni
> Malinen)
> Dec  2 16:37:38 defender kernel: hostap_cs: (c) Jouni Malinen
> <jkmaline at cc.hut.fi>
> Dec  2 16:37:39 defender kernel: hostap_cs: setting Vcc=33 (constant)
> Dec  2 16:37:39 defender kernel: hostap_cs: CS_EVENT_CARD_INSERTION
> Dec  2 16:37:39 defender kernel: prism2_config()
> Dec  2 16:37:39 defender kernel: hostap_cs: setting Vcc=50 (from config)
> Dec  2 16:37:39 defender kernel: Checking CFTABLE_ENTRY 0x01 (default
0x01)
> Dec  2 16:37:39 defender kernel: IO window settings: cfg->io.nwin=1
> dflt.io.nwin=1
> Dec  2 16:37:39 defender kernel: io->flags = 0x0024, io.base=0x0000,
len=16
> Dec  2 16:37:39 defender kernel: hostap_cs: index 0x01: Vcc 5.0, irq 3, io
> 0x0100-0x010f
> Dec  2 16:37:39 defender cardmgr[194]: executing: './network start wlan0'
> Dec  2 16:37:39 defender kernel: hostap_cs: Registered netdevice wlan0
> Dec  2 16:37:39 defender kernel: prism2_hw_init()
> Dec  2 16:37:39 defender kernel: wlan0: hfa384x_cmd - timeout - reg=0x8000
> Dec  2 16:37:39 defender kernel: hostap_cs: first command failed - is the
> card compatible?
> Dec  2 16:37:39 defender kernel: hostap_cs: Initialization failed
> Dec  2 16:37:39 defender cardmgr[194]: + usage: /sbin/cardctl command
> [socket #]
> Dec  2 16:37:39 defender cardmgr[194]: +     or /sbin/cardctl [-c
> configpath] [-f scheme] [-s stab] scheme
> [name]
> Dec  2 16:37:39 defender cardmgr[194]: +     commands: status config ident
> suspend resume reset eject inser
> t
> Dec  2 16:37:39 defender ntpd[214]: ntpd 4.1.0 Mon Mar 25 23:39:47 UTC
2002
> (2)
> Dec  2 16:37:40 defender kernel: prism2: wlan0: operating mode changed
3 ->
> 1
> Dec  2 16:37:40 defender kernel: wlan0: hfa384x_setup_bap - timeout before
> Dec  2 16:37:40 defender kernel: wlan0: hfa384x_set_rid (rid=fc00,
len=2) -
> failed - res=-110
> Dec  2 16:37:40 defender cardmgr[194]: + /sbin/iwconfig wlan0 mode Ad-Hoc
> Dec  2 16:37:40 defender cardmgr[194]: + Error for wireless request "Set
> Mode" (8B06) :
> Dec  2 16:37:40 defender cardmgr[194]: +     SET failed on device wlan0 ;
> Operation not supported.
> Dec  2 16:37:40 defender kernel: wlan0: hfa384x_setup_bap - timeout before
> Dec  2 16:37:40 defender kernel: wlan0: hfa384x_set_rid (rid=fc0e,
len=34) -
> failed - res=-110
> Dec  2 16:37:40 defender ntpd[214]: signal_no_reset: signal 13 had flags
> 4000000
> Dec  2 16:37:40 defender ntpd[214]: precision = 17 usec
> Dec  2 16:37:40 defender ntpd[214]: kernel time discipline status 0040
> Dec  2 16:37:40 defender ntpd[214]: getconfig: Couldn't open
</etc/ntp.conf>
> Dec  2 16:37:40 defender cardmgr[194]: + /sbin/iwconfig wlan0 channel 1
> Dec  2 16:37:40 defender cardmgr[194]: + Error for wireless request "Set
> Frequency" (8B04) :
> Dec  2 16:37:40 defender cardmgr[194]: +     SET failed on device wlan0 ;
> Invalid argument.
> Dec  2 16:37:40 defender kernel: wlan0: hfa384x_setup_bap - timeout before
> Dec  2 16:37:40 defender kernel: wlan0: hfa384x_set_rid (rid=fc84,
len=2) -
> failed - res=-110
> Dec  2 16:37:40 defender kernel: wlan0: TXRateControl setting to 0xf
failed
> Dec  2 16:37:40 defender /usr/sbin/cron[230]: (CRON) INFO (pidfile fd = 3)
> Dec  2 16:37:41 defender /usr/sbin/cron[236]: (CRON) STARTUP (fork ok)
> Dec  2 16:37:41 defender kernel: hostap_crypt: registered algorithm 'WEP'
> Dec  2 16:37:41 defender /usr/sbin/cron[236]: (CRON) INFO (Running @reboot
> jobs)
> Dec  2 16:37:41 defender kernel: wlan0: hfa384x_cmd_issue: cmd reg was
busy
> for 1000 usec
> Dec  2 16:37:41 defender kernel: wlan0: hfa384x_cmd_issue - timeout -
> reg=0x8000
> Dec  2 16:37:41 defender kernel: wlan0: hfa384x_cmd: entry still in list?
> (entry=c25121e0, type=0, res=-1)
> Dec  2 16:37:41 defender kernel: wlan0: hfa384x_cmd: interrupted; err=-110
> Dec  2 16:37:41 defender kernel: wlan0: hfa384x_get_rid: CMDCODE_ACCESS
> failed (res=-110, rid=fc28, len=2)
> Dec  2 16:37:41 defender kernel: Could not read current WEP flags.
> Dec  2 16:37:41 defender kernel: wlan0: encryption setup failed
> Dec  2 16:37:41 defender kernel: set_encryption or reset_port failed
> Dec  2 16:37:41 defender cardmgr[194]: + /sbin/iwconfig wlan0 key
> s:defender-plexus1
> Dec  2 16:37:41 defender cardmgr[194]: + Error for wireless request "Set
> Encode" (8B2A) :
> Dec  2 16:37:41 defender cardmgr[194]: +     SET failed on device wlan0 ;
> Invalid argument.
> Dec  2 16:37:41 defender cardmgr[194]: + /sbin/iwconfig wlan0 essid
> "defender-plexus.backbone.kentwireless.
> net"
> Dec  2 16:37:41 defender cardmgr[194]: + Error for wireless request "Set
> ESSID" (8B1A) :
> Dec  2 16:37:41 defender cardmgr[194]: +     argument too big (max 32)
> Dec  2 16:37:42 defender kernel: wlan0: prism2_open
> Dec  2 16:37:42 defender kernel: wlan0: hfa384x_cmd_issue: cmd reg was
busy
> for 1000 usec
> Dec  2 16:37:42 defender kernel: wlan0: hfa384x_cmd_issue - timeout -
> reg=0x8000
> Dec  2 16:37:42 defender kernel: wlan0: hfa384x_cmd: entry still in list?
> (entry=c25121e0, type=0, res=-1)
> Dec  2 16:37:42 defender kernel: wlan0: hfa384x_cmd: interrupted; err=-110
> Dec  2 16:37:42 defender kernel: wlan0: MAC port 0 enabling failed
> Dec  2 16:37:42 defender kernel: wlan0: could not enable MAC port
> Dec  2 16:37:42 defender kernel: wlan0: prism2_close
> Dec  2 16:37:42 defender cardmgr[194]: + /sbin/ifconfig wlan0 up
> 192.168.2.254 netmask 255.255.255.0 broadc
> ast 192.168.2.255
> Dec  2 16:37:42 defender cardmgr[194]: + SIOCSIFFLAGS: No such device
> Dec  2 16:37:42 defender cardmgr[194]: + /sbin/route add -net 192.168.2.0
> netmask 255.255.255.0 dev wlan0
> Dec  2 16:37:42 defender cardmgr[194]: + SIOCADDRT: Network is down
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>





From ian.cass  Mon Dec  2 09:14:26 2002
From: ian.cass (Ian Cass)
Date: Mon, 2 Dec 2002 17:14:26 -0000
Subject: HostAP Drivers with non-Prism2
References: <06b101c29a22$f8018550$4c28a8c0@cblan.mblox.com> <107b01c29a25$6e455460$114c35d1@tonyxp>
Message-ID: <070901c29a26$44c65ac0$4c28a8c0@cblan.mblox.com>

> These cards are not command-compatible with Prism-II cards, and require a
> seperate driver.

OK that's cool. But why does the HostAP README.Prism2 seem to suggest it
should work?

> If your card uses and AMD firmware, you may need to download the legacy
> driver from linux-wlan.com,

Unfortunately, I can't manage to compile that with 2.4.19. I don't really
want to go back to an old 2.2 kernel.

> otherwise you can use the 2MB driver we wrote
> for Teletronics which is hosted on their site.  The driver has Access
Point
> mode.

I'll look that one up, thanks.

--
Ian Cass




From tony  Mon Dec  2 09:24:36 2002
From: tony (Tony Toole)
Date: Mon, 2 Dec 2002 09:24:36 -0800
Subject: HostAP Drivers with non-Prism2
References: <06b101c29a22$f8018550$4c28a8c0@cblan.mblox.com> <107b01c29a25$6e455460$114c35d1@tonyxp> <070901c29a26$44c65ac0$4c28a8c0@cblan.mblox.com>
Message-ID: <10b201c29a27$aff86990$114c35d1@tonyxp>

The reference in the HostAP manual is refering to the Lucent Hermes (which
is also refered as Prism I).  These cards are command-compatible (to an
extent).

The zcom (and Teletronics 2MB) card uses an AMD MAC controler which is not
prism-I compatible.

Try the driver from the Teletronics site, it should compile fine with the
lates pcmcia services, and kernels.

Thanks,
Tony Toole
Valemount Networks Corporation
http://www.star-os.com/
http://forums.star-os.com/  (Support forums)


----- Original Message ----- 
From: "Ian Cass" <ian.cass at mblox.com>
To: <hostap at shmoo.com>
Sent: Monday, December 02, 2002 9:14 AM
Subject: Re: HostAP Drivers with non-Prism2


> > These cards are not command-compatible with Prism-II cards, and require
a
> > seperate driver.
>
> OK that's cool. But why does the HostAP README.Prism2 seem to suggest it
> should work?
>
> > If your card uses and AMD firmware, you may need to download the legacy
> > driver from linux-wlan.com,
>
> Unfortunately, I can't manage to compile that with 2.4.19. I don't really
> want to go back to an old 2.2 kernel.
>
> > otherwise you can use the 2MB driver we wrote
> > for Teletronics which is hosted on their site.  The driver has Access
> Point
> > mode.
>
> I'll look that one up, thanks.
>
> --
> Ian Cass
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From jar  Mon Dec  2 11:08:46 2002
From: jar (jar)
Date: Mon, 02 Dec 2002 21:08:46 +0200
Subject: Compiling problems with RedHat
Message-ID: <3DEBAFBE.72D07EA8@pcuf.fi>

I can't compile the stuff under /utils and /hostapd directories when
the hostap-2002-10-12 or CVS version is used with RedHat's recent 
kernels 2.4.18-17-7 or 2.4.18-18-7. Something wrong in
<linux/wireless.h> or
<linux/ethtool.h> in RedHat kernels ? It there any solution ?

Regards, Jar



From owens  Mon Dec  2 13:13:01 2002
From: owens (Owen Shoemaker)
Date: Mon, 2 Dec 2002 13:13:01 -0800
Subject: hostap w/ 2.4.20rc3 and cyrix chip
Message-ID: <D7152C85-063A-11D7-8B72-000393D5F2BA@speakeasy.net>

I was wondering if anyone had experience running the hostap code on 
cyrix.  Everytime I try and load the module or run hostapd I get 
"undefined symbol" and "_mmx_memcp" errors.

I am running the cyrix chip in a shuttle atx (small form factor) with a 
prism 200mw card in a pci->pcmcia adapter.  It sees the card and I have 
been able to initialize the card with a stock rpm RH kernel.

--
Owen Shoemaker
Speakeasy INC
1.800.556.5829 ext. 143




From pete  Mon Dec  2 14:04:09 2002
From: pete (Peter Buelow)
Date: Mon, 2 Dec 2002 16:04:09 -0600 (CST)
Subject: Compiling problems with RedHat
Message-ID: <55956.136.182.2.222.1038866649.squirrel@westnelson.net>

Couple of questions.
1. Which version of Redhat (I'm guessing 8, but just to make sure)
2. Can you post the actual compiler error(s)?

I won't say "It works for me", but it does, so gonna need more help from
you to identify the actual problem.

Quick note. There is a problem with hostap_pci and RH8.0 kernel 2.4.18-17
that causes a kernel panic when loading hostap_2002-10-12. The problem
seems to go away with the 2.4.18-18 kernel.

>
> I can't compile the stuff under /utils and /hostapd directories when the
> hostap-2002-10-12 or CVS version is used with RedHat's recent  kernels
> 2.4.18-17-7 or 2.4.18-18-7. Something wrong in
> <linux/wireless.h> or
> <linux/ethtool.h> in RedHat kernels ? It there any solution ?
>
> Regards, Jar
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap


-- 
"They that would give up essential liberty for temporary safety
deserveneither liberty nor safety." Benjamin Franklin
--
Peter Buelow
pete at putzin.net





From alok  Mon Dec  2 18:24:21 2002
From: alok (Alok K. Dhir)
Date: Mon, 2 Dec 2002 21:24:21 -0500
Subject: Kernel 2.4.20?
Message-ID: <000601c29a73$16dd3eb0$1e01a8c0@PEARL>

Hey all - I've been running kernel 2.4.19 for some time with my D-Link
DWL-520 Prism2.5 PCI card and the 2002-10-12 release.  I just upgraded
to kernel 2.4.20 and I can't get the modules to load - they compile
fine, but when I 'make install_pci' I get:

Installing hostap_crypt*.o to /lib/modules/2.4.20/net
mkdir -p /lib/modules/2.4.20/net
cp driver/modules/hostap_crypt*.o /lib/modules/2.4.20/net
Installing hostap.o to /lib/modules/2.4.20/net
mkdir -p /lib/modules/2.4.20/net
cp driver/modules/hostap.o /lib/modules/2.4.20/net
Installing hostap_pci.o to /lib/modules/2.4.20/net
mkdir -p /lib/modules/2.4.20/net
cp driver/modules/hostap_pci.o /lib/modules/2.4.20/net
/sbin/depmod -a
depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap_pci.o

So I did 'depmod -ae' and I get:

depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap.o
depmod:         wireless_send_event
depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap_pci.o
depmod:         wireless_send_event

Any ideas?

Thanks!





From evilbunny  Mon Dec  2 18:37:34 2002
From: evilbunny (evilbunny)
Date: Tue, 3 Dec 2002 13:37:34 +1100
Subject: Kernel 2.4.20?
In-Reply-To: <000601c29a73$16dd3eb0$1e01a8c0@PEARL>
References: <000601c29a73$16dd3eb0$1e01a8c0@PEARL>
Message-ID: <1371657498.20021203133734@groth.net>

Hello Alok,

I had the same thing ended up playing with it till it worked...

make sure you "make clean" a few times, reboot a few times, and all of
a sudden it will start working :)

-- 
Best regards,
 evilbunny                            mailto:evilbunny at sydneywireless.com

http://www.cacert.org - Free Security Certificates
http://www.nodedb.com - Think globally, network locally
http://www.sydneywireless.com - Telecommunications Freedom

Tuesday, December 3, 2002, 1:24:21 PM, you wrote:


AKD> Hey all - I've been running kernel 2.4.19 for some time with my D-Link
AKD> DWL-520 Prism2.5 PCI card and the 2002-10-12 release.  I just upgraded
AKD> to kernel 2.4.20 and I can't get the modules to load - they compile
AKD> fine, but when I 'make install_pci' I get:

AKD> Installing hostap_crypt*.o to /lib/modules/2.4.20/net
AKD> mkdir -p /lib/modules/2.4.20/net
AKD> cp driver/modules/hostap_crypt*.o /lib/modules/2.4.20/net
AKD> Installing hostap.o to /lib/modules/2.4.20/net
AKD> mkdir -p /lib/modules/2.4.20/net
AKD> cp driver/modules/hostap.o /lib/modules/2.4.20/net
AKD> Installing hostap_pci.o to /lib/modules/2.4.20/net
AKD> mkdir -p /lib/modules/2.4.20/net
AKD> cp driver/modules/hostap_pci.o /lib/modules/2.4.20/net
AKD> /sbin/depmod -a
AKD> depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap.o
AKD> depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap_pci.o

AKD> So I did 'depmod -ae' and I get:

AKD> depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap.o
AKD> depmod:         wireless_send_event
AKD> depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap_pci.o
AKD> depmod:         wireless_send_event

AKD> Any ideas?

AKD> Thanks!


AKD> _______________________________________________
AKD> HostAP mailing list
AKD> HostAP at shmoo.com
AKD> http://lists.shmoo.com/mailman/listinfo/hostap
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1966 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20021203/2974ad2f/attachment.bin 


From alok  Mon Dec  2 18:49:04 2002
From: alok (Alok K. Dhir)
Date: Mon, 2 Dec 2002 21:49:04 -0500
Subject: Kernel 2.4.20?
In-Reply-To: <000601c29a73$16dd3eb0$1e01a8c0@PEARL>
Message-ID: <001a01c29a76$8b03dda0$1e01a8c0@PEARL>

More info:

[root at wolf:~] grep wireless_send_event /proc/ksyms
c030e290 wireless_send_event_R__ver_wireless_send_event

[root at wolf:~] grep MODVER /usr/src/linux/.config
CONFIG_MODVERSIONS=y

Thanks for any assistance.

Al

> -----Original Message-----
> From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] 
> On Behalf Of Alok K. Dhir
> Sent: Monday, December 02, 2002 9:24 PM
> To: HostAP at shmoo.com
> Subject: Kernel 2.4.20?
> 
> 
> 
> Hey all - I've been running kernel 2.4.19 for some time with 
> my D-Link DWL-520 Prism2.5 PCI card and the 2002-10-12 
> release.  I just upgraded to kernel 2.4.20 and I can't get 
> the modules to load - they compile fine, but when I 'make 
> install_pci' I get:
> 
> Installing hostap_crypt*.o to /lib/modules/2.4.20/net
> mkdir -p /lib/modules/2.4.20/net
> cp driver/modules/hostap_crypt*.o /lib/modules/2.4.20/net 
> Installing hostap.o to /lib/modules/2.4.20/net mkdir -p 
> /lib/modules/2.4.20/net cp driver/modules/hostap.o 
> /lib/modules/2.4.20/net Installing hostap_pci.o to 
> /lib/modules/2.4.20/net mkdir -p /lib/modules/2.4.20/net cp 
> driver/modules/hostap_pci.o /lib/modules/2.4.20/net /sbin/depmod -a
> depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap.o
> depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap_pci.o
> 
> So I did 'depmod -ae' and I get:
> 
> depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap.o
> depmod:         wireless_send_event
> depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap_pci.o
> depmod:         wireless_send_event
> 
> Any ideas?
> 
> Thanks!
> 
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 




From jkmaline  Mon Dec  2 18:58:02 2002
From: jkmaline (Jouni Malinen)
Date: Mon, 2 Dec 2002 18:58:02 -0800
Subject: Kernel 2.4.20?
In-Reply-To: <001a01c29a76$8b03dda0$1e01a8c0@PEARL>
References: <000601c29a73$16dd3eb0$1e01a8c0@PEARL> <001a01c29a76$8b03dda0$1e01a8c0@PEARL>
Message-ID: <20021203025802.GA1261@jm.kir.nu>

On Mon, Dec 02, 2002 at 09:49:04PM -0500, Alok K. Dhir wrote:

> [root at wolf:~] grep wireless_send_event /proc/ksyms
> c030e290 wireless_send_event_R__ver_wireless_send_event

Looks like your kernel modversions have not been fully updated.
include/linux/modules/netsyms.ver should have defined that
__ver_wireless_send_event to something like e8c62182. How did you
updated your kernel to 2.4.20? Did you run 'make dep' before compiling
the new version? You would need to regenerate that netsyms.ver file to
get things working properly.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Dec  2 19:03:54 2002
From: jkmaline (Jouni Malinen)
Date: Mon, 2 Dec 2002 19:03:54 -0800
Subject: hostap w/ 2.4.20rc3 and cyrix chip
In-Reply-To: <D7152C85-063A-11D7-8B72-000393D5F2BA@speakeasy.net>
References: <D7152C85-063A-11D7-8B72-000393D5F2BA@speakeasy.net>
Message-ID: <20021203030354.GB1261@jm.kir.nu>

On Mon, Dec 02, 2002 at 01:13:01PM -0800, Owen Shoemaker wrote:

> I was wondering if anyone had experience running the hostap code on 
> cyrix.  Everytime I try and load the module or run hostapd I get 
> "undefined symbol" and "_mmx_memcp" errors.

What kind of kernel are you using? Have you compiled it yourself? Are
you sure your kernel .config file matches with the running kernel?
_mmx_memcpy is defined only if you have CONFIG_X86_USE_3DNOW defined and
this will be the case if you have selected MK7 or MCYRIXIII as the
processor type.

It would look like your kernel would be compiled with different
processor type than the Host AP module. You would need to have matching
.config when compiling Host AP driver. It might be enough to change the
processor type to something else to get that working, but compiling
kernel and Host AP driver with the same .config would be even better.

-- 
Jouni Malinen                                            PGP id EFC895FA



From alok  Mon Dec  2 19:13:57 2002
From: alok (Alok K. Dhir)
Date: Mon, 2 Dec 2002 22:13:57 -0500
Subject: Kernel 2.4.20?
In-Reply-To: <20021203025802.GA1261@jm.kir.nu>
Message-ID: <001b01c29a7a$051476b0$1e01a8c0@PEARL>

I did indeed to a 'make dep' before compiling.  How do I regenerate
netsyms.ver?  Should 'make dep' do that?  In a freshly 'make dep'ed
tree:

[root at wolf:/usr/src/linux/include/linux/modules] grep -i wireless
netsyms.ver 
[root at wolf:/usr/src/linux/include/linux/modules] 

I.e. nothing...

> -----Original Message-----
> From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] 
> On Behalf Of Jouni Malinen
> Sent: Monday, December 02, 2002 9:58 PM
> To: hostap at shmoo.com
> Subject: Re: Kernel 2.4.20?
> 
> 
> On Mon, Dec 02, 2002 at 09:49:04PM -0500, Alok K. Dhir wrote:
> 
> > [root at wolf:~] grep wireless_send_event /proc/ksyms
> > c030e290 wireless_send_event_R__ver_wireless_send_event
> 
> Looks like your kernel modversions have not been fully 
> updated. include/linux/modules/netsyms.ver should have 
> defined that __ver_wireless_send_event to something like 
> e8c62182. How did you updated your kernel to 2.4.20? Did you 
> run 'make dep' before compiling the new version? You would 
> need to regenerate that netsyms.ver file to get things 
> working properly.
> 
> -- 
> Jouni Malinen                                            PGP 
> id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 




From evilbunny  Mon Dec  2 19:18:08 2002
From: evilbunny (evilbunny)
Date: Tue, 3 Dec 2002 14:18:08 +1100
Subject: Kernel 2.4.20?
In-Reply-To: <001b01c29a7a$051476b0$1e01a8c0@PEARL>
References: <001b01c29a7a$051476b0$1e01a8c0@PEARL>
Message-ID: <3574091147.20021203141808@groth.net>

Hello Alok,

cp .config ..
make mrproper
cp ../.config .
make menuconfig
exit (don't need to make changes)
make dep bzlilo modules modules_install

(if it's the problem with make dep)

-- 
Best regards,
 evilbunny                            mailto:evilbunny at sydneywireless.com

http://www.cacert.org - Free Security Certificates
http://www.nodedb.com - Think globally, network locally
http://www.sydneywireless.com - Telecommunications Freedom

Tuesday, December 3, 2002, 2:13:57 PM, you wrote:

AKD> I did indeed to a 'make dep' before compiling.  How do I regenerate
AKD> netsyms.ver?  Should 'make dep' do that?  In a freshly 'make dep'ed
AKD> tree:

AKD> [root at wolf:/usr/src/linux/include/linux/modules] grep -i wireless
AKD> netsyms.ver 
AKD> [root at wolf:/usr/src/linux/include/linux/modules] 

AKD> I.e. nothing...

>> -----Original Message-----
>> From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] 
>> On Behalf Of Jouni Malinen
>> Sent: Monday, December 02, 2002 9:58 PM
>> To: hostap at shmoo.com
>> Subject: Re: Kernel 2.4.20?
>> 
>> 
>> On Mon, Dec 02, 2002 at 09:49:04PM -0500, Alok K. Dhir wrote:
>> 
>> > [root at wolf:~] grep wireless_send_event /proc/ksyms
>> > c030e290 wireless_send_event_R__ver_wireless_send_event
>> 
>> Looks like your kernel modversions have not been fully 
>> updated. include/linux/modules/netsyms.ver should have 
>> defined that __ver_wireless_send_event to something like 
>> e8c62182. How did you updated your kernel to 2.4.20? Did you 
>> run 'make dep' before compiling the new version? You would 
>> need to regenerate that netsyms.ver file to get things 
>> working properly.
>> 
>> -- 
>> Jouni Malinen                                            PGP 
>> id EFC895FA
>> _______________________________________________
>> HostAP mailing list
>> HostAP at shmoo.com
>> http://lists.shmoo.com/mailman/listinfo/hostap
>> 

AKD> _______________________________________________
AKD> HostAP mailing list
AKD> HostAP at shmoo.com
AKD> http://lists.shmoo.com/mailman/listinfo/hostap
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1966 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20021203/2c61bbd9/attachment.bin 


From alok  Mon Dec  2 19:22:24 2002
From: alok (Alok K. Dhir)
Date: Mon, 2 Dec 2002 22:22:24 -0500
Subject: Kernel 2.4.20?
In-Reply-To: <3574091147.20021203141808@groth.net>
Message-ID: <002201c29a7b$336cabd0$1e01a8c0@PEARL>

Thanks - doing that now - I just saw all the genksyms stuff go by, so I
think I did something right this time. ;)

> -----Original Message-----
> From: evilbunny [mailto:evilbunny at sydneywireless.com] 
> Sent: Monday, December 02, 2002 10:18 PM
> To: Alok K. Dhir
> Cc: hostap at shmoo.com
> Subject: Re[2]: Kernel 2.4.20?
> 
> 
> Hello Alok,
> 
> cp .config ..
> make mrproper
> cp ../.config .
> make menuconfig
> exit (don't need to make changes)
> make dep bzlilo modules modules_install
> 
> (if it's the problem with make dep)
> 
> -- 
> Best regards,
>  evilbunny                            
> mailto:evilbunny at sydneywireless.com
> 
http://www.cacert.org - 
Free Security Certificates http://www.nodedb.com - Think globally,
network locally http://www.sydneywireless.com - Telecommunications
Freedom

Tuesday, December 3, 2002, 2:13:57 PM, you wrote:

AKD> I did indeed to a 'make dep' before compiling.  How do I regenerate

AKD> netsyms.ver?  Should 'make dep' do that?  In a freshly 'make dep'ed
AKD> tree:

AKD> [root at wolf:/usr/src/linux/include/linux/modules] grep -i wireless 
AKD> netsyms.ver [root at wolf:/usr/src/linux/include/linux/modules]

AKD> I.e. nothing...

>> -----Original Message-----
>> From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com]
>> On Behalf Of Jouni Malinen
>> Sent: Monday, December 02, 2002 9:58 PM
>> To: hostap at shmoo.com
>> Subject: Re: Kernel 2.4.20?
>> 
>> 
>> On Mon, Dec 02, 2002 at 09:49:04PM -0500, Alok K. Dhir wrote:
>> 
>> > [root at wolf:~] grep wireless_send_event /proc/ksyms c030e290 
>> > wireless_send_event_R__ver_wireless_send_event
>> 
>> Looks like your kernel modversions have not been fully
>> updated. include/linux/modules/netsyms.ver should have 
>> defined that __ver_wireless_send_event to something like 
>> e8c62182. How did you updated your kernel to 2.4.20? Did you 
>> run 'make dep' before compiling the new version? You would 
>> need to regenerate that netsyms.ver file to get things 
>> working properly.
>> 
>> -- 
>> Jouni Malinen                                            PGP 
>> id EFC895FA
>> _______________________________________________
>> HostAP mailing list
>> HostAP at shmoo.com http://lists.shmoo.com/mailman/listinfo/hostap
>> 

AKD> _______________________________________________
AKD> HostAP mailing list
AKD> HostAP at shmoo.com http://lists.shmoo.com/mailman/listinfo/hostap




From dean-list-hostap  Mon Dec  2 22:00:13 2002
From: dean-list-hostap (dean gaudet)
Date: Mon, 2 Dec 2002 22:00:13 -0800 (PST)
Subject: problems with EN2511CD / NL2511CD
Message-ID: <Pine.LNX.4.50.0212022152090.11195-100000@twinlark.arctic.org>

i recently purchased an NL2511CD aka EN2511CD from netgate.com and i'm
having troubles getting it to work with the latest hostap-2002-10-12 code.

i've already had this laptop working as an AP with a linksys WPC11 prism2
card, so i think i've got the basics covered.  i can also get the NL2511CD
to work in a win2k laptop as a client, so i think the hardware works.

the NL2511CD has these firmware revs:  (i've tried a bunch of others i
found on the net)

Dec  2 20:57:13 mewlark kernel: wlan0: NIC: id=0x800c v1.0.0
Dec  2 20:57:13 mewlark kernel: wlan0: PRI: id=0x15 v1.1.0
Dec  2 20:57:13 mewlark kernel: wlan0: STA: id=0x1f v1.4.9

hostap doesn't complain about anything... but i can't associate with it.
here's some attempts by my cisco350 to associate:

Dec  2 20:57:23 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0 trans#=1 stat=0 len=6fc=00b0) ==> 0 (authenticated)
Dec  2 20:57:23 mewlark kernel: wlan0: 00:40:96:5a:5d:ce reassoc (len=32 prev_ap=00:03:2f:02:97:46) => 0(0) (OK, new AID)

those go on for a while, but the cisco never manages to associate.
(i tried a WPC11 as well, no luck either.)

i find this suspicious:

Socket 0:
  product info: "INTERSIL", "HFA384x/IEEE", "Version 01.02", ""
  manfid: 0x0156, 0x0002
  function: 6 (network)

Socket 0:
  3.3V 16-bit PC Card
  function 0: [ready]

those look like identifiers for a prism2 card but this one should
be a prism2.5.

any tips?

-dean



From jkmaline  Mon Dec  2 22:26:56 2002
From: jkmaline (Jouni Malinen)
Date: Mon, 2 Dec 2002 22:26:56 -0800
Subject: problems with EN2511CD / NL2511CD
In-Reply-To: <Pine.LNX.4.50.0212022152090.11195-100000@twinlark.arctic.org>
References: <Pine.LNX.4.50.0212022152090.11195-100000@twinlark.arctic.org>
Message-ID: <20021203062656.GA12480@jm.kir.nu>

On Mon, Dec 02, 2002 at 10:00:13PM -0800, dean gaudet wrote:

> Dec  2 20:57:23 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0 trans#=1 stat=0 len=6fc=00b0) ==> 0 (authenticated)
> Dec  2 20:57:23 mewlark kernel: wlan0: 00:40:96:5a:5d:ce reassoc (len=32 prev_ap=00:03:2f:02:97:46) => 0(0) (OK, new AID)
> 
> those go on for a while, but the cisco never manages to associate.
> (i tried a WPC11 as well, no luck either.)

As far as Host AP driver is concerned, that station has been
successfully associated. However, you could test this with the latest
CVS version to check whether the station is really acknowledging that
last reassociation response. 2002-10-12 release did not yet do this kind
of verification for the ACKs. The latest CVS version requires ACK before
marking station as associated. It should show both the incoming frame
and the ACK, so you should see two messages about authentication and two
about association (if everything goes well).

If the client card is not reporting any errors, I would just have to
guess that it did not like the reassociation reply for some reason (most
probably it arrived after too long delay). Since the client card sent
reassociation request, I would assume that it accepted authentication
frame from the AP (although, I've seen some stations not caring about
authentication that much..).

> Socket 0:
>   product info: "INTERSIL", "HFA384x/IEEE", "Version 01.02", ""
>   manfid: 0x0156, 0x0002
>   function: 6 (network)

> those look like identifiers for a prism2 card but this one should
> be a prism2.5.

I have seen so many re-uses for PC Card manfids with Prism2/2.5 cards
that nothing seems to suprise me anymore.. ;-)  I wouldn't worry about
this, at least before checking what happens to response frames from AP.

-- 
Jouni Malinen                                            PGP id EFC895FA



From brianc  Tue Dec  3 00:29:48 2002
From: brianc (Brian Capouch)
Date: Tue, 03 Dec 2002 03:29:48 -0500
Subject: ACK timeouts: done in firmware or software?
Message-ID: <3DEC6B7C.3010103@palaver.net>

I just read this paper, which I saw mentioned in a mail to the NoCat 
list.  I'm doing a rural WISP thing where this might be the eventual 
path to nirvana, if I'm reading it right.  Maybe it's old news.

I'm not aware enough to know whether I should assume that my 
drivers--HostAP and Agere's AP-1000 bins--currently only wait for a SIFS 
period before giving up on an ACK.   If that's what it is could I change 
it to length DIFS instead and thereby gain the benefit they posit?

Thanks.

B.

http://www.bell-labs.com/user/kin/papers/802.11.mac2.pdf




From dean  Mon Dec  2 22:59:24 2002
From: dean (dean gaudet)
Date: Mon, 2 Dec 2002 22:59:24 -0800 (PST)
Subject: problems with EN2511CD / NL2511CD
In-Reply-To: <20021203062656.GA12480@jm.kir.nu>
References: <Pine.LNX.4.50.0212022152090.11195-100000@twinlark.arctic.org>
 <20021203062656.GA12480@jm.kir.nu>
Message-ID: <Pine.LNX.4.50.0212022251260.11195-100000@twinlark.arctic.org>

On Mon, 2 Dec 2002, Jouni Malinen wrote:

> On Mon, Dec 02, 2002 at 10:00:13PM -0800, dean gaudet wrote:
>
> > Dec  2 20:57:23 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0 trans#=1 stat=0 len=6fc=00b0) ==> 0 (authenticated)
> > Dec  2 20:57:23 mewlark kernel: wlan0: 00:40:96:5a:5d:ce reassoc (len=32 prev_ap=00:03:2f:02:97:46) => 0(0) (OK, new AID)
> >
> > those go on for a while, but the cisco never manages to associate.
> > (i tried a WPC11 as well, no luck either.)
>
> As far as Host AP driver is concerned, that station has been
> successfully associated. However, you could test this with the latest
> CVS version to check whether the station is really acknowledging that
> last reassociation response.

here's what i get with latest CVS:

Dec  2 22:46:42 mewlark kernel: hostap_crypt: registered algorithm 'NULL'
Dec  2 22:46:42 mewlark kernel: hostap_cs: 0.0.0 CVS (Jouni Malinen <jkmaline at cc.hut.fi>)
Dec  2 22:46:42 mewlark kernel: hostap_cs: setting Vcc=33 (constant)
Dec  2 22:46:42 mewlark kernel: hostap_cs: CS_EVENT_CARD_INSERTION
Dec  2 22:46:42 mewlark kernel: prism2_config()
Dec  2 22:46:42 mewlark kernel: hostap_cs: ignoring Vcc=33 (from config)
Dec  2 22:46:42 mewlark kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
Dec  2 22:46:42 mewlark kernel: IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
Dec  2 22:46:42 mewlark kernel: io->flags = 0x0046, io.base=0x0000, len=64
Dec  2 22:46:42 mewlark kernel: hostap_cs: index 0x01: Vcc 3.3, irq 3, io 0x0180-0x01bf
Dec  2 22:46:43 mewlark kernel: hostap_cs: Registered netdevice wlan0
Dec  2 22:46:43 mewlark kernel: prism2_hw_init()
Dec  2 22:46:43 mewlark kernel: prism2_hw_config: initialized in 17095 iterations
Dec  2 22:46:43 mewlark kernel: wlan0: NIC: id=0x800c v1.0.0
Dec  2 22:46:43 mewlark kernel: wlan0: PRI: id=0x15 v1.1.0
Dec  2 22:46:43 mewlark kernel: wlan0: STA: id=0x1f v1.4.9
Dec  2 22:46:43 mewlark kernel: wlan0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
Dec  2 22:46:43 mewlark kernel: wlan0: LinkStatus=2 (Disconnected)
Dec  2 22:46:43 mewlark kernel: Setting ALC off
Dec  2 22:46:43 mewlark kernel: Setting TX power to 24 dBm
Dec  2 22:46:43 mewlark kernel: wlan0: LinkStatus=2 (Disconnected)
Dec  2 22:46:43 mewlark kernel: wlan0: LinkStatus=2 (Disconnected)
Dec  2 22:46:43 mewlark kernel: wlan0: prism2_open
Dec  2 22:46:51 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0 trans#=1 stat=0 len=6 fc=00b0) ==> 0 (authOK)
Dec  2 22:46:51 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth_cb - frame was not ACKed
Dec  2 22:47:27 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0 trans#=1 stat=0 len=6 fc=00b0) ==> 0 (authOK)
Dec  2 22:47:27 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth_cb - frame was not ACKed

and just for kicks, here's what happens when i use my older WPC11
card as AP on current CVS (which is working fine):

Dec  2 22:48:05 mewlark kernel: hostap_crypt: registered algorithm 'NULL'
Dec  2 22:48:05 mewlark kernel: hostap_cs: 0.0.0 CVS (Jouni Malinen <jkmaline at cc.hut.fi>)
Dec  2 22:48:05 mewlark kernel: hostap_cs: setting Vcc=33 (constant)
Dec  2 22:48:05 mewlark kernel: hostap_cs: CS_EVENT_CARD_INSERTION
Dec  2 22:48:05 mewlark kernel: prism2_config()
Dec  2 22:48:05 mewlark kernel: hostap_cs: ignoring Vcc=50 (from config)
Dec  2 22:48:05 mewlark kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
Dec  2 22:48:05 mewlark kernel: IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
Dec  2 22:48:05 mewlark kernel: io->flags = 0x0046, io.base=0x0000, len=64
Dec  2 22:48:05 mewlark kernel: hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0180-0x01bf
Dec  2 22:48:05 mewlark kernel: hostap_cs: Registered netdevice wlan0
Dec  2 22:48:05 mewlark kernel: prism2_hw_init()
Dec  2 22:48:05 mewlark kernel: prism2_hw_config: initialized in 9180 iterations
Dec  2 22:48:05 mewlark kernel: wlan0: NIC: id=0x8002 v1.0.0
Dec  2 22:48:05 mewlark kernel: wlan0: PRI: id=0x15 v0.3.0
Dec  2 22:48:05 mewlark kernel: wlan0: STA: id=0x1f v0.8.3
Dec  2 22:48:05 mewlark kernel: wlan0: defaulting to host-based encryption as a workaround for firmware bug in Host AP mode WEP
Dec  2 22:48:05 mewlark kernel: wlan0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
Dec  2 22:48:05 mewlark kernel: wlan0: LinkStatus=2 (Disconnected)
Dec  2 22:48:05 mewlark kernel: Setting ALC off
Dec  2 22:48:05 mewlark kernel: Setting TX power to 24 dBm
Dec  2 22:48:05 mewlark kernel: wlan0: LinkStatus=2 (Disconnected)
Dec  2 22:48:05 mewlark kernel: wlan0: LinkStatus=2 (Disconnected)
Dec  2 22:48:05 mewlark kernel: wlan0: prism2_open
Dec  2 22:48:38 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0 trans#=1 stat=0 len=6 fc=00b0) ==> 0 (authOK)
Dec  2 22:48:38 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth_cb - STA authenticated
Dec  2 22:48:38 mewlark kernel: wlan0: 00:40:96:5a:5d:ce reassoc (len=32 prev_ap=00:03:2f:02:97:46) => 0(0) (OK, new AID)
Dec  2 22:48:38 mewlark kernel: wlan0: 00:40:96:5a:5d:ce assoc_cb - STA associated
Dec  2 22:48:48 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0 trans#=1 stat=0 len=6 fc=00b0) ==> 0 (authOK)
Dec  2 22:48:48 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth_cb - STA authenticated
Dec  2 22:48:48 mewlark kernel: wlan0: 00:40:96:5a:5d:ce assoc (len=26 prev_ap=00:00:00:00:00:00) => 0(0) (OK, old AID)
Dec  2 22:48:48 mewlark kernel: wlan0: 00:40:96:5a:5d:ce assoc_cb - STA associated

note that prev_ap mac address is the mac address of the WPC11.


> If the client card is not reporting any errors, I would just have to
> guess that it did not like the reassociation reply for some reason (most
> probably it arrived after too long delay). Since the client card sent
> reassociation request, I would assume that it accepted authentication
> frame from the AP (although, I've seen some stations not caring about
> authentication that much..).

the client is win2k / cisco350 ... any idea how i check for errors?

-dean



From koraob  Mon Dec  2 23:34:56 2002
From: koraob (Andrew O'Brien)
Date: Tue, 03 Dec 2002 02:34:56 -0500
Subject: (no subject)
Message-ID: <F29pziwON0RjZaIs64X000159cc@hotmail.com>

Hello list,
	I want to integrate wireless access into my linux firewall using HostAP.  I 
have been researching the supported cards available for this, namely the 
Linksys WMP11 and D-Link DWL-520, and have not come up with a clear winner.  
The problem with the D-link is that I have read that it *requires* a 2.2pci 
bios and my machine is only a Pentium so that is no good and the I have read 
several places that the WMP11 now uses a different chipset that doesn't have 
a driver (I *hate* Linksys for this, they did it for their LNE100tx eth card 
also).  So around to the question does anyone know of a suitable card with 
the following specs, in order of importance:
1. Available to buy now, works with hostap driver
2. PCI, or ISA (If anyone knows whether an Actiontec PC700 pcmcia > isa card 
adapter works pcmcia would be ok)
3. doesn't require a 2.2pci bios
4. external antenna jack (would really like this one)
5. good power out ~100mw would be nice
Please reply to koraob at hotmail.com as I am not a member of this list *yet*.
	Thanks,
		Andrew O'Brien

_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail




From br1  Tue Dec  3 06:03:45 2002
From: br1 (bruno randolf)
Date: Tue, 3 Dec 2002 15:03:45 +0100
Subject: (no subject)
In-Reply-To: <F29pziwON0RjZaIs64X000159cc@hotmail.com>
References: <F29pziwON0RjZaIs64X000159cc@hotmail.com>
Message-ID: <200212031503.45931.br1@subnet.at>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi andrew!

the d-link dwl520 works fine on my old 586 mainboard (gigabyte
GA586ATS from 1996), which has a PCI2.1 controller from intel.

this is what my logs say:
- ---
Oct 28 16:50:08 router kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb620,
last bus=0
Oct 28 17:35:35 router kernel: wlan0: Intersil Prism2.5 PCI: mem=0xe1001000,
irq=10
- ---

other reports of it working in PCI2.1 boards are in the updates-section of
this page:
http://www.personaltelco.net/index.cgi/DlinkDwl520

the new linux-wlan-ng FAQ (v0.1.16-pre7), which i think is the source of this 
rumor, is updated with this information.

br1

On Tuesday 03 December 2002 08:34, Andrew O'Brien wrote:
> Hello list,
> 	I want to integrate wireless access into my linux firewall using HostAP. 
> I have been researching the supported cards available for this, namely the
> Linksys WMP11 and D-Link DWL-520, and have not come up with a clear winner.
> The problem with the D-link is that I have read that it *requires* a 2.2pci
> bios and my machine is only a Pentium so that is no good and the I have
> read several places that the WMP11 now uses a different chipset that
> doesn't have a driver (I *hate* Linksys for this, they did it for their
> LNE100tx eth card also).  So around to the question does anyone know of a
> suitable card with the following specs, in order of importance:
> 1. Available to buy now, works with hostap driver
> 2. PCI, or ISA (If anyone knows whether an Actiontec PC700 pcmcia > isa
> card adapter works pcmcia would be ok)
> 3. doesn't require a 2.2pci bios
> 4. external antenna jack (would really like this one)
> 5. good power out ~100mw would be nice
> Please reply to koraob at hotmail.com as I am not a member of this list *yet*.
> 	Thanks,
> 		Andrew O'Brien
>
> _________________________________________________________________
> Add photos to your e-mail with MSN 8. Get 2 months FREE*.
> http://join.msn.com/?page=features/featuredemail
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE97LnBqCK9CeX6cL8RAtUwAKDgb0TyZfp10kOcXiZYWF5O5yxRvwCgpGJq
dRbZqnQifWKg70y3f++8Uf0=
=Sy2x
-----END PGP SIGNATURE-----




From jjo-hostap-dated-1039357028.7d885f  Tue Dec  3 06:17:06 2002
From: jjo-hostap-dated-1039357028.7d885f (JuanJo Ciarlante)
Date: Tue, 3 Dec 2002 11:17:06 -0300
Subject: hostap w/ 2.4.20rc3 and cyrix chip
Message-ID: <20021203111706.P18475@mendoza.gov.ar>

On Mon, Dec 02, 2002 at 07:03:54PM -0800, Jouni Malinen wrote:
> On Mon, Dec 02, 2002 at 01:13:01PM -0800, Owen Shoemaker wrote:
> 
> > I was wondering if anyone had experience running the hostap code on 
> > cyrix.  Everytime I try and load the module or run hostapd I get 
> > "undefined symbol" and "_mmx_memcp" errors.
> 
> [...]
>
> It would look like your kernel would be compiled with different
> processor type than the Host AP module. You would need to have matching
> .config when compiling Host AP driver. It might be enough to change the
> processor type to something else to get that working, but compiling
> kernel and Host AP driver with the same .config would be even better.

Yup... FYI I do have a Cyrix (120Mhz) with a WL200 using hostap-2002-12-10
(or CVS) on 2.4.20-rc1, it always worked flawlessly.

-- 
--Juanjo

#  Juan Jose Ciarlante (JuanJo PGP) jjo ;at; mendoza.gov.ar              #
#  Key fingerprint = 76 60 A5 76 FD D2 53 E3  50 C7 90 20 22 8C F1 2D    #



From majo  Tue Dec  3 08:07:15 2002
From: majo (Marian Danisek)
Date: 03 Dec 2002 17:07:15 +0100
Subject: strange problem
Message-ID: <1038931635.2020.2.camel@mandrake.sunteq.sk>

hello,

i installed latest kernel 2.4.20 + wireless ver.15 patch and hostap 
10-12-2002 driver release. After pcmcia start a got this strange result 

hostap_cs: Registered netdevice wlan0
wlan0: could not get own MAC address
wlan0: Port type setting to 6 failed
wlan0: MAC port 0 enabling failed

Please can anyone tell me what this mean ?


Majo,


-- 
SUNTEQ s. r. o.
Bojnicka cesta 35 # Prievidza # 971 04 # Slovak republic
Tel: +421-46-5430 754 # Fax: +421-46-5439 144
http://www.sunteq.sk/
------------------------------------------------------------
A mind is like a parachute... it only works when it's open.




From doug  Tue Dec  3 08:17:41 2002
From: doug (Doug Yeager)
Date: Tue, 3 Dec 2002 11:17:41 -0500
Subject: (no subject)
Message-ID: <001b01c29ae7$8714ded0$1300a8c0@DOUG1>

I am going to load new firware to ram using prism2_srec.
 
Now, when the power goes off to the machine or I reboot.  Do I need to
load this to the card every time because it is ram.
Or does it somehow know and keep the firmware somewhere?
 
Thx,
doug
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021203/d92c9db9/attachment.htm 


From owens  Tue Dec  3 08:39:19 2002
From: owens (Owen Shoemaker)
Date: Tue, 3 Dec 2002 08:39:19 -0800
Subject: hostap w/ 2.4.20rc3 and cyrix chip
Message-ID: <C4E31109-06DD-11D7-A851-000393D5F2BA@speakeasy.net>

Kernel used: 2.4.20rc3

The kernel was patched, configured from scratch, built, and installed 
before building hostap.  I gave up and used the new 2.4.20 kernel with 
a p4 and had no problems.  Oh well I will come back to the cyrix later.

Thanks for the help.

--
Owen Shoemaker




From doug  Tue Dec  3 08:42:09 2002
From: doug (Doug Yeager)
Date: Tue, 3 Dec 2002 11:42:09 -0500
Subject: firmware to RAM question
Message-ID: <002301c29aea$f1a3bde0$1300a8c0@DOUG1>

Sorry, forgot to include subject line.  Here was my post:
 
 
I am going to load new firware to ram using prism2_srec.
 
Now, when the power goes off to the machine or I reboot.  Do I need to
load this to the card every time because it is ram.
Or does it somehow know and keep the firmware somewhere?
 
Thx,
doug
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021203/e98dca10/attachment.htm 


From jar  Tue Dec  3 08:42:45 2002
From: jar (jar at pcuf.fi)
Date: Tue, 3 Dec 2002 18:42:45 +0200 (EET)
Subject: Compiling problems with RedHat
In-Reply-To: <55956.136.182.2.222.1038866649.squirrel@westnelson.net>
References: <55956.136.182.2.222.1038866649.squirrel@westnelson.net>
Message-ID: <1902.194.157.0.2.1038933765.squirrel@netlandzone.dyndns.org>

> Couple of questions.
> 1. Which version of Redhat (I'm guessing 8, but just to make sure)

Same problem in Redhat 7.2 and 7.3.

> 2. Can you post the actual compiler error(s)?

Many error lines from ethtool.h. Parse errors,
";" missing, "}" missing, etc. If I remember right.

I can compile the driver (hostap_cs) itself and I can
drive the card, but the other stuff under /utils and
/hostapd directories doesn't compile.


Regards, Jar






From jasonb  Tue Dec  3 09:53:38 2002
From: jasonb (Jason Boxman)
Date: Tue, 3 Dec 2002 12:53:38 -0500 (EST)
Subject: firmware to RAM question
In-Reply-To: <002301c29aea$f1a3bde0$1300a8c0@DOUG1>
References: <002301c29aea$f1a3bde0$1300a8c0@DOUG1>
Message-ID: <2224.209.208.68.82.1038938018.squirrel@rebecca.edseek.com>

Doug Yeager said:
> Sorry, forgot to include subject line.  Here was my post:
>
>
> I am going to load new firware to ram using prism2_srec.
>
> Now, when the power goes off to the machine or I reboot.  Do I need to
> load this to the card every time because it is ram.
> Or does it somehow know and keep the firmware somewhere?

Every time.

> Thx,
> doug
>






From doug  Tue Dec  3 08:06:00 2002
From: doug (Doug Yeager)
Date: Tue, 3 Dec 2002 11:06:00 -0500
Subject: new firware loaded to ram
Message-ID: <001001c29ae5$e53e5150$1300a8c0@DOUG1>

I am going to load new firware to ram using prism2_srec.
 
Now, when the power goes off to the machine or I reboot.  Do I need to
load this to the card every time because it is ram.
Or does it somehow know and keep the firmware somewhere?
 
Thx,
doug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021203/8a5e235f/attachment.htm 


From adhir  Tue Dec  3 10:44:43 2002
From: adhir (Alok K. Dhir)
Date: Tue, 3 Dec 2002 13:44:43 -0500
Subject: (no subject)
In-Reply-To: <200212031503.45931.br1@subnet.at>
Message-ID: <004d01c29afc$0bb6a330$6501a8c0@frodo>

I, too, have a DWL-520 working perfectly in a non 2.2 compliant PCI bus
(Dell Workstation 420 - PCI 2.1).

> -----Original Message-----
> From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] 
> On Behalf Of bruno randolf
> Sent: Tuesday, December 03, 2002 9:04 AM
> To: Andrew O'Brien; hostap at shmoo.com
> Subject: Re: (no subject)
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> hi andrew!
> 
> the d-link dwl520 works fine on my old 586 mainboard 
> (gigabyte GA586ATS from 1996), which has a PCI2.1 controller 
> from intel.
> 
> this is what my logs say:
> - ---
> Oct 28 16:50:08 router kernel: PCI: PCI BIOS revision 2.10 
> entry at 0xfb620, last bus=0 Oct 28 17:35:35 router kernel: 
> wlan0: Intersil Prism2.5 PCI: mem=0xe1001000, irq=10
> - ---
> 
> other reports of it working in PCI2.1 boards are in the 
> updates-section of this page: 
> http://www.personaltelco.net/index.cgi/DlinkDwl520
> 
> the new linux-wlan-ng FAQ (v0.1.16-pre7), which i think is 
> the source of this 
> rumor, is updated with this information.
> 
> br1
> 
> On Tuesday 03 December 2002 08:34, Andrew O'Brien wrote:
> > Hello list,
> > 	I want to integrate wireless access into my linux 
> firewall using 
> > HostAP.
> > I have been researching the supported cards available for 
> this, namely the
> > Linksys WMP11 and D-Link DWL-520, and have not come up with 
> a clear winner.
> > The problem with the D-link is that I have read that it 
> *requires* a 2.2pci
> > bios and my machine is only a Pentium so that is no good 
> and the I have
> > read several places that the WMP11 now uses a different chipset that
> > doesn't have a driver (I *hate* Linksys for this, they did 
> it for their
> > LNE100tx eth card also).  So around to the question does 
> anyone know of a
> > suitable card with the following specs, in order of importance:
> > 1. Available to buy now, works with hostap driver
> > 2. PCI, or ISA (If anyone knows whether an Actiontec PC700 
> pcmcia > isa
> > card adapter works pcmcia would be ok)
> > 3. doesn't require a 2.2pci bios
> > 4. external antenna jack (would really like this one)
> > 5. good power out ~100mw would be nice
> > Please reply to koraob at hotmail.com as I am not a member of 
> this list *yet*.
> > 	Thanks,
> > 		Andrew O'Brien
> >
> > _________________________________________________________________
> > Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
> > http://join.msn.com/?page=features/featuredemail
> >
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com http://lists.shmoo.com/mailman/listinfo/hostap
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.0 (GNU/Linux)
> 
> iD8DBQE97LnBqCK9CeX6cL8RAtUwAKDgb0TyZfp10kOcXiZYWF5O5yxRvwCgpGJq
> dRbZqnQifWKg70y3f++8Uf0=
> =Sy2x
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 




From pete  Tue Dec  3 14:28:54 2002
From: pete (Peter Buelow)
Date: Tue, 3 Dec 2002 16:28:54 -0600 (CST)
Subject: Compiling problems with RedHat
In-Reply-To: <1902.194.157.0.2.1038933765.squirrel@netlandzone.dyndns.org>
References: <55956.136.182.2.222.1038866649.squirrel@westnelson.net>
        <1902.194.157.0.2.1038933765.squirrel@netlandzone.dyndns.org>
Message-ID: <19869.136.182.2.222.1038954534.squirrel@westnelson.net>

  Can you just copy and paste the errors into a reply? It'll be long, but
I would still like to see them, and others may too. The first compiler
error line is probably the most interesting and will provide the most
guidance as to the exact problem. Also, what version of wireless tools
are you building this agains? I don't think that matters, as I believe
there aren't any intersting header files in there, but I thought I would
ask. RH8 is version 25, but I'm not sure about the other two.

>> Couple of questions.
>> 1. Which version of Redhat (I'm guessing 8, but just to make sure)
>
> Same problem in Redhat 7.2 and 7.3.
>
>> 2. Can you post the actual compiler error(s)?
>
> Many error lines from ethtool.h. Parse errors,
> ";" missing, "}" missing, etc. If I remember right.
>
> I can compile the driver (hostap_cs) itself and I can
> drive the card, but the other stuff under /utils and
> /hostapd directories doesn't compile.
>
>
> Regards, Jar


-- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety." Benjamin Franklin
--
Peter Buelow
pete at putzin.net





From judah  Tue Dec  3 14:35:34 2002
From: judah (Aaron Baer)
Date: 03 Dec 2002 14:35:34 -0800
Subject: Kernel 2.4.20?
In-Reply-To: <3574091147.20021203141808@groth.net>
References: <001b01c29a7a$051476b0$1e01a8c0@PEARL>
	 <3574091147.20021203141808@groth.net>
Message-ID: <1038954934.13956.22.camel@localhost.localdomain>

On Mon, 2002-12-02 at 19:18, evilbunny wrote:
> Hello Alok,
> 
> cp .config ..
> make mrproper
> cp ../.config .
> make menuconfig

make oldconfig is good for this step as well.. faster probably.. 

A-

-- 
----
Aaron Baer
judah at opusnet.com
http://www.cat.pdx.edu/~baera/




From rogan  Tue Dec  3 15:09:45 2002
From: rogan (Rogan Lynch)
Date: Tue, 03 Dec 2002 15:09:45 -0800
Subject: What hardware to buy. WAS Re:(no subject)
Message-ID: <WorldClient-F200212031509.AA09450000@lynchdom.dyndns.org>

1. Available to buy now, works with hostap driver

I use an Intel 2011b PCI in my old pentium 166 LEAF Router: it's reall a 
rebranded Xircom miniPCI in a sleave. I have also used ealy model linksys 
wmp11s (mfctred before June of this year) 

2. PCI, or ISA (If anyone knows whether an Actiontec PC700 pcmcia > isa 
card adapter works pcmcia would be ok)

PCI.... The adapters from ISA to PCMCIA are fine... but finding a PCMCIA 
card with an external antenna jack is tough...

3. doesn't require a 2.2pci bios

See comment 1...

4. external antenna jack (would really like this one)

See comment 2

5. good power out ~100mw would be nice
The Intel seems to get up to 100mW, but the Linksys only got to 95mW




From jkmaline  Tue Dec  3 19:22:43 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 3 Dec 2002 19:22:43 -0800
Subject: problems with EN2511CD / NL2511CD
In-Reply-To: <Pine.LNX.4.50.0212022251260.11195-100000@twinlark.arctic.org>
References: <Pine.LNX.4.50.0212022152090.11195-100000@twinlark.arctic.org> <20021203062656.GA12480@jm.kir.nu> <Pine.LNX.4.50.0212022251260.11195-100000@twinlark.arctic.org>
Message-ID: <20021204032243.GA1232@jm.kir.nu>

On Mon, Dec 02, 2002 at 10:59:24PM -0800, dean gaudet wrote:

> Dec  2 22:46:51 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0 trans#=1 stat=0 len=6 fc=00b0) ==> 0 (authOK)
> Dec  2 22:46:51 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth_cb - frame was not ACKed

OK, that's the problem.. The station is not acknowledging authentication
frame from the AP (or at least the AP does not receive this ACK). Most
common reason for this is the delay between authentication frames being
too long. Some station firmware implementation seem to be quite strict
on this. Do you happen to have lot of wireless traffic on the same
channel? Is the AP host heavily loaded or is it writing kernel messages
to frame buffer or serial console?

The best method for researching the problem would be to use a third host
as a wireless sniffer and record the frame exchange between the station
and the AP. I would like to be sure that the authentication reply from
the AP is really going out and that the station is not sending an ACK
for it.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Dec  3 19:33:09 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 3 Dec 2002 19:33:09 -0800
Subject: strange problem
In-Reply-To: <1038931635.2020.2.camel@mandrake.sunteq.sk>
References: <1038931635.2020.2.camel@mandrake.sunteq.sk>
Message-ID: <20021204033309.GB1232@jm.kir.nu>

On Tue, Dec 03, 2002 at 05:07:15PM +0100, Marian Danisek wrote:

> hostap_cs: Registered netdevice wlan0
> wlan0: could not get own MAC address
> wlan0: Port type setting to 6 failed
> wlan0: MAC port 0 enabling failed
> 
> Please can anyone tell me what this mean ?

Full kernel debug log output ('dmesg') should show some addition
information. If you did not get any errors before that "could not get
own MAC address", it would mean that the driver was able to read
component versions from the card but for some reason failed to read the
own MAC address RID. Apparently the card was in quite confused state
from this point on and the rest of initialization failed too.

I have seen this happening only once on my test cards (and was unable to
repeat it), so it is a bit difficult to find out the real reason for it.
I would guess that driver is doing something that kills firmware code.
I'm doing some changes to BAP handling (i.e., to use only one BAP) and
that might help also with this kind of problems.

-- 
Jouni Malinen                                            PGP id EFC895FA



From dean-list-hostap  Tue Dec  3 19:38:32 2002
From: dean-list-hostap (dean gaudet)
Date: Tue, 3 Dec 2002 19:38:32 -0800 (PST)
Subject: problems with EN2511CD / NL2511CD
In-Reply-To: <20021204032243.GA1232@jm.kir.nu>
References: <Pine.LNX.4.50.0212022152090.11195-100000@twinlark.arctic.org>
 <20021203062656.GA12480@jm.kir.nu> <Pine.LNX.4.50.0212022251260.11195-100000@twinlark.arctic.org>
 <20021204032243.GA1232@jm.kir.nu>
Message-ID: <Pine.LNX.4.50.0212031935320.11195-100000@twinlark.arctic.org>

On Tue, 3 Dec 2002, Jouni Malinen wrote:

> On Mon, Dec 02, 2002 at 10:59:24PM -0800, dean gaudet wrote:
>
> > Dec  2 22:46:51 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0 trans#=1 stat=0 len=6 fc=00b0) ==> 0 (authOK)
> > Dec  2 22:46:51 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth_cb - frame was not ACKed
>
> OK, that's the problem.. The station is not acknowledging authentication
> frame from the AP (or at least the AP does not receive this ACK). Most
> common reason for this is the delay between authentication frames being
> too long. Some station firmware implementation seem to be quite strict
> on this. Do you happen to have lot of wireless traffic on the same
> channel? Is the AP host heavily loaded or is it writing kernel messages
> to frame buffer or serial console?

the problem happens with both a cisco 350 and a linksys WPC11 on the
client side.

there's no other wireless traffic on this channel (it's in my house and
none of my neighbours are using wireless) ... there could be other types
of 2.4GHz interference, but i've been testing with the client and AP
within 1m of each other.

no load on the AP host.

> The best method for researching the problem would be to use a third host
> as a wireless sniffer and record the frame exchange between the station
> and the AP. I would like to be sure that the authentication reply from
> the AP is really going out and that the station is not sending an ACK
> for it.

i can do this sniffing with my WPC11 (prism2) card, right?  i'll have to
build another linux laptop to do this... i'll give it a go though.  what
is the preferred tool for sniffing?

thanks
-dean



From jasonb  Tue Dec  3 20:51:34 2002
From: jasonb (Jason Boxman)
Date: Tue, 3 Dec 2002 23:51:34 -0500
Subject: problems with EN2511CD / NL2511CD
In-Reply-To: <Pine.LNX.4.50.0212031935320.11195-100000@twinlark.arctic.org>
References: <Pine.LNX.4.50.0212022152090.11195-100000@twinlark.arctic.org> <20021204032243.GA1232@jm.kir.nu> <Pine.LNX.4.50.0212031935320.11195-100000@twinlark.arctic.org>
Message-ID: <200212032351.34703.jasonb@edseek.com>

On Tuesday 03 December 2002 10:38 pm, dean gaudet wrote:
> On Tue, 3 Dec 2002, Jouni Malinen wrote:
> > On Mon, Dec 02, 2002 at 10:59:24PM -0800, dean gaudet wrote:
> > > Dec  2 22:46:51 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0
> > > trans#=1 stat=0 len=6 fc=00b0) ==> 0 (authOK) Dec  2 22:46:51 mewlark
> > > kernel: wlan0: 00:40:96:5a:5d:ce auth_cb - frame was not ACKed
> >
<snip>
> i can do this sniffing with my WPC11 (prism2) card, right?  i'll have to
> build another linux laptop to do this... i'll give it a go though.  what
> is the preferred tool for sniffing?

I think you'll enjoy sniffing.

I just "iwconfig wlan0 mode monitor" and then run tethereal on it.  Works 
nicely.

> thanks
> -dean

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages





From jar  Wed Dec  4 07:19:04 2002
From: jar (jar at pcuf.fi)
Date: Wed, 4 Dec 2002 17:19:04 +0200 (EET)
Subject: Compiling problems with RedHat
In-Reply-To: <19869.136.182.2.222.1038954534.squirrel@westnelson.net>
References: <55956.136.182.2.222.1038866649.squirrel@westnelson.net>
        <1902.194.157.0.2.1038933765.squirrel@netlandzone.dyndns.org>
        <19869.136.182.2.222.1038954534.squirrel@westnelson.net>
Message-ID: <3613.194.157.0.2.1039015144.squirrel@netlandzone.dyndns.org>

>   Can you just copy and paste the errors into a reply? It'll be long,
> but I would still like to see them, and others may too.

Ok here it is:

[root at redhat73 utils]# make
cc -O2 -Wall -I/usr/src/linux/include   -c -o prism2_srec.o prism2_srec.c
In file included from /usr/src/linux/include/linux/wireless.h:70,
                 from prism2_srec.c:20:
/usr/src/linux/include/linux/ethtool.h:18: parse error before `u32'
/usr/src/linux/include/linux/ethtool.h:18: warning: no semicolon at end of
struct or union
/usr/src/linux/include/linux/ethtool.h:19: warning: type defaults to `int'
in declaration of `supported'
/usr/src/linux/include/linux/ethtool.h:19: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:20: parse error before `advertising'
/usr/src/linux/include/linux/ethtool.h:20: warning: type defaults to `int'
in declaration of `advertising'
/usr/src/linux/include/linux/ethtool.h:20: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:21: parse error before `speed'
/usr/src/linux/include/linux/ethtool.h:21: warning: type defaults to `int'
in declaration of `speed'
/usr/src/linux/include/linux/ethtool.h:21: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:22: parse error before `duplex'
/usr/src/linux/include/linux/ethtool.h:22: warning: type defaults to `int'
in declaration of `duplex'
/usr/src/linux/include/linux/ethtool.h:22: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:23: parse error before `port'
/usr/src/linux/include/linux/ethtool.h:23: warning: type defaults to `int'
in declaration of `port'
/usr/src/linux/include/linux/ethtool.h:23: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:24: parse error before `phy_address'
/usr/src/linux/include/linux/ethtool.h:24: warning: type defaults to `int'
in declaration of `phy_address'
/usr/src/linux/include/linux/ethtool.h:24: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:25: parse error before `transceiver'
/usr/src/linux/include/linux/ethtool.h:25: warning: type defaults to `int'
in declaration of `transceiver'
/usr/src/linux/include/linux/ethtool.h:25: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:26: parse error before `autoneg'
/usr/src/linux/include/linux/ethtool.h:26: warning: type defaults to `int'
in declaration of `autoneg'
/usr/src/linux/include/linux/ethtool.h:26: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:27: parse error before `maxtxpkt'
/usr/src/linux/include/linux/ethtool.h:27: warning: type defaults to `int'
in declaration of `maxtxpkt'
/usr/src/linux/include/linux/ethtool.h:27: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:28: parse error before `maxrxpkt'
/usr/src/linux/include/linux/ethtool.h:28: warning: type defaults to `int'
in declaration of `maxrxpkt'
/usr/src/linux/include/linux/ethtool.h:28: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:29: parse error before `reserved'
/usr/src/linux/include/linux/ethtool.h:29: warning: type defaults to `int'
in declaration of `reserved'
/usr/src/linux/include/linux/ethtool.h:29: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:30: parse error before `}'
/usr/src/linux/include/linux/ethtool.h:35: parse error before `u32'
/usr/src/linux/include/linux/ethtool.h:35: warning: no semicolon at end of
struct or union
/usr/src/linux/include/linux/ethtool.h:43: parse error before `testinfo_len'
/usr/src/linux/include/linux/ethtool.h:43: warning: type defaults to `int'
in declaration of `testinfo_len'
/usr/src/linux/include/linux/ethtool.h:43: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:44: parse error before `eedump_len'
/usr/src/linux/include/linux/ethtool.h:44: warning: type defaults to `int'
in declaration of `eedump_len'
/usr/src/linux/include/linux/ethtool.h:44: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:45: parse error before `regdump_len'
/usr/src/linux/include/linux/ethtool.h:45: warning: type defaults to `int'
in declaration of `regdump_len'
/usr/src/linux/include/linux/ethtool.h:45: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:51: parse error before `u32'
/usr/src/linux/include/linux/ethtool.h:51: warning: no semicolon at end of
struct or union
/usr/src/linux/include/linux/ethtool.h:52: warning: type defaults to `int'
in declaration of `supported'
/usr/src/linux/include/linux/ethtool.h:52: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:53: parse error before `wolopts'
/usr/src/linux/include/linux/ethtool.h:53: warning: type defaults to `int'
in declaration of `wolopts'
/usr/src/linux/include/linux/ethtool.h:53: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:54: parse error before `sopass'
/usr/src/linux/include/linux/ethtool.h:54: warning: type defaults to `int'
in declaration of `sopass'
/usr/src/linux/include/linux/ethtool.h:54: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:55: parse error before `}'
/usr/src/linux/include/linux/ethtool.h:59: parse error before `u32'
/usr/src/linux/include/linux/ethtool.h:59: warning: no semicolon at end of
struct or union
/usr/src/linux/include/linux/ethtool.h:60: warning: type defaults to `int'
in declaration of `data'
/usr/src/linux/include/linux/ethtool.h:60: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:65: parse error before `u32'
/usr/src/linux/include/linux/ethtool.h:65: warning: no semicolon at end of
struct or union
/usr/src/linux/include/linux/ethtool.h:66: warning: type defaults to `int'
in declaration of `version'
/usr/src/linux/include/linux/ethtool.h:66: conflicting types for `version'
/usr/src/linux/include/linux/ethtool.h:37: previous declaration of `version'
/usr/src/linux/include/linux/ethtool.h:66: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:67: parse error before `len'
/usr/src/linux/include/linux/ethtool.h:67: warning: type defaults to `int'
in declaration of `len'
/usr/src/linux/include/linux/ethtool.h:67: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:68: parse error before `data'
/usr/src/linux/include/linux/ethtool.h:68: warning: type defaults to `int'
in declaration of `data'
/usr/src/linux/include/linux/ethtool.h:68: conflicting types for `data'
/usr/src/linux/include/linux/ethtool.h:60: previous declaration of `data'
/usr/src/linux/include/linux/ethtool.h:68: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:69: parse error before `}'
/usr/src/linux/include/linux/ethtool.h:73: parse error before `u32'
/usr/src/linux/include/linux/ethtool.h:73: warning: no semicolon at end of
struct or union
/usr/src/linux/include/linux/ethtool.h:74: warning: type defaults to `int'
in declaration of `magic'
/usr/src/linux/include/linux/ethtool.h:74: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:75: parse error before `offset'
/usr/src/linux/include/linux/ethtool.h:75: warning: type defaults to `int'
in declaration of `offset'
/usr/src/linux/include/linux/ethtool.h:75: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:76: parse error before `len'
/usr/src/linux/include/linux/ethtool.h:76: warning: type defaults to `int'
in declaration of `len'
/usr/src/linux/include/linux/ethtool.h:76: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:77: parse error before `data'
/usr/src/linux/include/linux/ethtool.h:77: warning: type defaults to `int'
in declaration of `data'
/usr/src/linux/include/linux/ethtool.h:77: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:78: parse error before `}'
/usr/src/linux/include/linux/ethtool.h:82: parse error before `u32'
/usr/src/linux/include/linux/ethtool.h:82: warning: no semicolon at end of
struct or union
/usr/src/linux/include/linux/ethtool.h:88: warning: type defaults to `int'
in declaration of `rx_coalesce_usecs'
/usr/src/linux/include/linux/ethtool.h:88: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:96: parse error before
`rx_max_coalesced_frames'
/usr/src/linux/include/linux/ethtool.h:96: warning: type defaults to `int'
in declaration of `rx_max_coalesced_frames'
/usr/src/linux/include/linux/ethtool.h:96: warning: data definition has no
type or storage class
/usr/src/linux/include/linux/ethtool.h:103: parse error before
`rx_coalesce_usecs_irq'
/usr/src/linux/include/linux/ethtool.h:103: warning: type defaults to
`int' in declaration of `rx_coalesce_usecs_irq'
/usr/src/linux/include/linux/ethtool.h:103: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:104: parse error before
`rx_max_coalesced_frames_irq'
/usr/src/linux/include/linux/ethtool.h:104: warning: type defaults to
`int' in declaration of `rx_max_coalesced_frames_irq'
/usr/src/linux/include/linux/ethtool.h:104: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:110: parse error before
`tx_coalesce_usecs'
/usr/src/linux/include/linux/ethtool.h:110: warning: type defaults to
`int' in declaration of `tx_coalesce_usecs'
/usr/src/linux/include/linux/ethtool.h:110: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:118: parse error before
`tx_max_coalesced_frames'
/usr/src/linux/include/linux/ethtool.h:118: warning: type defaults to
`int' in declaration of `tx_max_coalesced_frames'
/usr/src/linux/include/linux/ethtool.h:118: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:125: parse error before
`tx_coalesce_usecs_irq'
/usr/src/linux/include/linux/ethtool.h:125: warning: type defaults to
`int' in declaration of `tx_coalesce_usecs_irq'
/usr/src/linux/include/linux/ethtool.h:125: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:126: parse error before
`tx_max_coalesced_frames_irq'
/usr/src/linux/include/linux/ethtool.h:126: warning: type defaults to
`int' in declaration of `tx_max_coalesced_frames_irq'
/usr/src/linux/include/linux/ethtool.h:126: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:133: parse error before
`stats_block_coalesce_usecs'
/usr/src/linux/include/linux/ethtool.h:133: warning: type defaults to
`int' in declaration of `stats_block_coalesce_usecs'
/usr/src/linux/include/linux/ethtool.h:133: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:142: parse error before
`use_adaptive_rx_coalesce'
/usr/src/linux/include/linux/ethtool.h:142: warning: type defaults to
`int' in declaration of `use_adaptive_rx_coalesce'
/usr/src/linux/include/linux/ethtool.h:142: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:143: parse error before
`use_adaptive_tx_coalesce'
/usr/src/linux/include/linux/ethtool.h:143: warning: type defaults to
`int' in declaration of `use_adaptive_tx_coalesce'
/usr/src/linux/include/linux/ethtool.h:143: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:149: parse error before `pkt_rate_low'
/usr/src/linux/include/linux/ethtool.h:149: warning: type defaults to
`int' in declaration of `pkt_rate_low'
/usr/src/linux/include/linux/ethtool.h:149: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:150: parse error before
`rx_coalesce_usecs_low'
/usr/src/linux/include/linux/ethtool.h:150: warning: type defaults to
`int' in declaration of `rx_coalesce_usecs_low'
/usr/src/linux/include/linux/ethtool.h:150: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:151: parse error before
`rx_max_coalesced_frames_low'
/usr/src/linux/include/linux/ethtool.h:151: warning: type defaults to
`int' in declaration of `rx_max_coalesced_frames_low'
/usr/src/linux/include/linux/ethtool.h:151: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:152: parse error before
`tx_coalesce_usecs_low'
/usr/src/linux/include/linux/ethtool.h:152: warning: type defaults to
`int' in declaration of `tx_coalesce_usecs_low'
/usr/src/linux/include/linux/ethtool.h:152: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:153: parse error before
`tx_max_coalesced_frames_low'
/usr/src/linux/include/linux/ethtool.h:153: warning: type defaults to
`int' in declaration of `tx_max_coalesced_frames_low'
/usr/src/linux/include/linux/ethtool.h:153: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:164: parse error before
`pkt_rate_high'
/usr/src/linux/include/linux/ethtool.h:164: warning: type defaults to
`int' in declaration of `pkt_rate_high'
/usr/src/linux/include/linux/ethtool.h:164: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:165: parse error before
`rx_coalesce_usecs_high'
/usr/src/linux/include/linux/ethtool.h:165: warning: type defaults to
`int' in declaration of `rx_coalesce_usecs_high'
/usr/src/linux/include/linux/ethtool.h:165: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:166: parse error before
`rx_max_coalesced_frames_high'
/usr/src/linux/include/linux/ethtool.h:166: warning: type defaults to
`int' in declaration of `rx_max_coalesced_frames_high'
/usr/src/linux/include/linux/ethtool.h:166: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:167: parse error before
`tx_coalesce_usecs_high'
/usr/src/linux/include/linux/ethtool.h:167: warning: type defaults to
`int' in declaration of `tx_coalesce_usecs_high'
/usr/src/linux/include/linux/ethtool.h:167: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:168: parse error before
`tx_max_coalesced_frames_high'
/usr/src/linux/include/linux/ethtool.h:168: warning: type defaults to
`int' in declaration of `tx_max_coalesced_frames_high'
/usr/src/linux/include/linux/ethtool.h:168: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:173: parse error before
`rate_sample_interval'
/usr/src/linux/include/linux/ethtool.h:173: warning: type defaults to
`int' in declaration of `rate_sample_interval'
/usr/src/linux/include/linux/ethtool.h:173: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:178: parse error before `u32'
/usr/src/linux/include/linux/ethtool.h:178: warning: no semicolon at end
of struct or union
/usr/src/linux/include/linux/ethtool.h:184: warning: type defaults to
`int' in declaration of `rx_max_pending'
/usr/src/linux/include/linux/ethtool.h:184: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:185: parse error before
`rx_mini_max_pending'
/usr/src/linux/include/linux/ethtool.h:185: warning: type defaults to
`int' in declaration of `rx_mini_max_pending'
/usr/src/linux/include/linux/ethtool.h:185: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:186: parse error before
`rx_jumbo_max_pending'
/usr/src/linux/include/linux/ethtool.h:186: warning: type defaults to
`int' in declaration of `rx_jumbo_max_pending'
/usr/src/linux/include/linux/ethtool.h:186: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:187: parse error before
`tx_max_pending'
/usr/src/linux/include/linux/ethtool.h:187: warning: type defaults to
`int' in declaration of `tx_max_pending'
/usr/src/linux/include/linux/ethtool.h:187: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:192: parse error before `rx_pending'
/usr/src/linux/include/linux/ethtool.h:192: warning: type defaults to
`int' in declaration of `rx_pending'
/usr/src/linux/include/linux/ethtool.h:192: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:193: parse error before
`rx_mini_pending'
/usr/src/linux/include/linux/ethtool.h:193: warning: type defaults to
`int' in declaration of `rx_mini_pending'
/usr/src/linux/include/linux/ethtool.h:193: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:194: parse error before
`rx_jumbo_pending'
/usr/src/linux/include/linux/ethtool.h:194: warning: type defaults to
`int' in declaration of `rx_jumbo_pending'
/usr/src/linux/include/linux/ethtool.h:194: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:195: parse error before `tx_pending'
/usr/src/linux/include/linux/ethtool.h:195: warning: type defaults to
`int' in declaration of `tx_pending'
/usr/src/linux/include/linux/ethtool.h:195: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:200: parse error before `u32'
/usr/src/linux/include/linux/ethtool.h:200: warning: no semicolon at end
of struct or union
/usr/src/linux/include/linux/ethtool.h:212: warning: type defaults to
`int' in declaration of `autoneg'
/usr/src/linux/include/linux/ethtool.h:212: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:213: parse error before `rx_pause'
/usr/src/linux/include/linux/ethtool.h:213: warning: type defaults to
`int' in declaration of `rx_pause'
/usr/src/linux/include/linux/ethtool.h:213: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:214: parse error before `tx_pause'
/usr/src/linux/include/linux/ethtool.h:214: warning: type defaults to
`int' in declaration of `tx_pause'
/usr/src/linux/include/linux/ethtool.h:214: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:225: parse error before `u32'
/usr/src/linux/include/linux/ethtool.h:225: warning: no semicolon at end
of struct or union
/usr/src/linux/include/linux/ethtool.h:226: warning: type defaults to
`int' in declaration of `string_set'
/usr/src/linux/include/linux/ethtool.h:226: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:227: parse error before `len'
/usr/src/linux/include/linux/ethtool.h:227: warning: type defaults to
`int' in declaration of `len'
/usr/src/linux/include/linux/ethtool.h:227: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:228: parse error before `data'
/usr/src/linux/include/linux/ethtool.h:228: warning: type defaults to
`int' in declaration of `data'
/usr/src/linux/include/linux/ethtool.h:228: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:229: parse error before `}'
/usr/src/linux/include/linux/ethtool.h:238: parse error before `u32'
/usr/src/linux/include/linux/ethtool.h:238: warning: no semicolon at end
of struct or union
/usr/src/linux/include/linux/ethtool.h:239: warning: type defaults to
`int' in declaration of `flags'
/usr/src/linux/include/linux/ethtool.h:239: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:240: parse error before `reserved'
/usr/src/linux/include/linux/ethtool.h:240: warning: type defaults to
`int' in declaration of `reserved'
/usr/src/linux/include/linux/ethtool.h:240: conflicting types for `reserved'
/usr/src/linux/include/linux/ethtool.h:29: previous declaration of `reserved'
/usr/src/linux/include/linux/ethtool.h:240: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:241: parse error before `len'
/usr/src/linux/include/linux/ethtool.h:241: warning: type defaults to
`int' in declaration of `len'
/usr/src/linux/include/linux/ethtool.h:241: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:242: parse error before `data'
/usr/src/linux/include/linux/ethtool.h:242: warning: type defaults to
`int' in declaration of `data'
/usr/src/linux/include/linux/ethtool.h:242: warning: data definition has
no type or storage class
/usr/src/linux/include/linux/ethtool.h:243: parse error before `}'
make: *** [prism2_srec.o] Error 1
[root at redhat73 utils]#

Regards, Jar






From jkmaline  Wed Dec  4 08:27:42 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 4 Dec 2002 18:27:42 +0200
Subject: Changed BAP use - only BAP0 used
Message-ID: <20021204182742.A32017@jm.epitest.fi>

The latest CVS version of the driver uses only BAP0 for wlan card memory
access. Previously, BAP1 was used to copy data from the wlan card to
host memory for RX and info frames.

There has been various reports about card hangs etc. that might have
been related to concurrent BAP0/BAP1 use. This should, in theory, be
supported by the hardware, but there seem to be issues with
hardware/firmware code. Current driver code should now be fully
protecting BAP against concurrent access, so hopefully these issues have
been resolved.

I haven't tested the new code thoroughly, so I would be interested in
hearing if it happens to help with problem cases or cause any new
problems. I just quickly verified that it does not crash my test setup
and that the network performance has not suffered noticeably.

-- 
Jouni Malinen                                            PGP id EFC895FA



From antonio.vilei  Wed Dec  4 09:37:40 2002
From: antonio.vilei (Antonio Vilei)
Date: Wed, 4 Dec 2002 18:37:40 +0100
Subject: receive frames with FCS errors
Message-ID: <00cd01c29bbb$d8157630$151e0a0a@stmantoniov>

Hi all,

Is it possible to receive frames with FCS errors while working in Master (or
Ad Hoc) mode?

In the prism2_rx() function (in file hostap_hw.c) I read:
 /* FCS errors should not come this far, but let's make sure that frames
  * with errors will be dropped even in Host AP mode */

Does it mean that frames with FCS errors are discarded by the card?

Thanks in advance,
Antonio





From lists  Wed Dec  4 10:02:05 2002
From: lists (lists)
Date: Wed, 4 Dec 2002 13:02:05 -0500 (EST)
Subject: RTS
Message-ID: <Pine.LNX.4.44.0212041301240.9822-100000@mhess.qn.net>

Can I set RTS info in HOSTAP

if so where do I set it?

and can someone explain (in detail) what it does, or tell me where I can 
find information on it.


Michael




From jt  Wed Dec  4 13:29:42 2002
From: jt (Jean Tourrilhes)
Date: Wed, 4 Dec 2002 13:29:42 -0800
Subject: receive frames with FCS errors
Message-ID: <20021204212942.GA25281@bougret.hpl.hp.com>

Antonio Vilei wrote :
> 
> Does it mean that frames with FCS errors are discarded by the card?

	Yes, because :
	o for most FCS errors the receiver didn't manage to
synchronise to the bit stream, so there is nothing to receive.
	o if the FCS didn't check, you can't trust the 802.11 header
(packet len, packet type, dest address and co).
	o error in unlicensed band are usually clustered (fading,
interference), which means that packet that would "look" OK are
usually not really usefull (which explain why FEC is useless, ask
people using BlueTooth-SCO links about it).
	So, receiving frame with FCS error is generally not possible.

	Regards,

	Jean




From jt  Wed Dec  4 13:31:33 2002
From: jt (Jean Tourrilhes)
Date: Wed, 4 Dec 2002 13:31:33 -0800
Subject: RTS
Message-ID: <20021204213133.GA25362@bougret.hpl.hp.com>

Michael wrote :
> 
> Can I set RTS info in HOSTAP
> 
> if so where do I set it?

	man iwconfig

> and can someone explain (in detail) what it does, or tell me where I can 
> find information on it.

	It's in the Howto.

	Jean




From jt  Wed Dec  4 15:25:53 2002
From: jt (Jean Tourrilhes)
Date: Wed, 4 Dec 2002 15:25:53 -0800
Subject: RTS
In-Reply-To: <3DEE8D75.9070008@ncweb.com>
References: <20021204213133.GA25362@bougret.hpl.hp.com> <3DEE8D75.9070008@ncweb.com>
Message-ID: <20021204232553.GA25943@bougret.hpl.hp.com>

On Wed, Dec 04, 2002 at 06:19:17PM -0500, Jeff Meden wrote:
> I have been working with michael on some performance issues in hostap, 
> and we have been seeing similar patterns relating to the tuning, namely 
> RTS threshold as set up by iwconfig seems to have little or no effect, 
> and although we have no way of checking definately for RTS usage, the 
> performance we see suggests that it is being used rarely if ever.   Is 
> there a way to see the rts activity by clients or the hostap driver?
> 
> Jeff Meden

	I probably would use my favorite excuse : blame it on the
firmware.
	The stats available in the firmware are not enough to know
those things. The only things you may want to look at is the number of
short and long retries, this is the only way I could see the firmware
behaving differently when using RTS.
	Can you find an Aironet card to put as a test partner ? The
stats out of the Aironet firmware are pretty exhaustive and would tell
you all those details.
	Good luck...

	Jean




From victor.aleo  Wed Dec  4 16:04:45 2002
From: victor.aleo (Victor Aleo)
Date: Thu, 05 Dec 2002 01:04:45 +0100
Subject: Problems with the last CVS version
Message-ID: <3DEE981D.6080708@estudiant.upc.es>

Hi all,

I have the next problem when a station tx data frames to the AP (both 
running the last CVS version):

wlan0: RX: dropped FCSErr frame (status=01)
wlan0: RX: dropped FCSErr frame (status=2001)
wlan0: RX: unknown MACPort 5

Where wlan0 is the AP interface.

FCS stands for Frame Check Sequence, if I'm not wrong, but I do not know 
what is the problem. I did not have problems with the 2002-10-12 version 
of the driver. At the end, more than a half of the packets are not 
transmitted. Moreover, the driver decreases the date bit rate of the 
station from 11 to 1 Mbps.

Do you know where is the problem?

Thanks,

Victor






From bapper  Wed Dec  4 17:12:34 2002
From: bapper (Brian Pomerantz)
Date: Wed, 4 Dec 2002 17:12:34 -0800
Subject: deauthentication on setting WEP key
Message-ID: <20021205011234.GA25880@skull.piratehaven.org>

I'm using the hostap driver in managed mode (client) to connect to a
Cisco Aironet 350.  I'm using xsupplicant to handle the 802.1x
transaction and everything looks like it is working just fine until
the broadcast and unicast WEP keys are set.  At this point the hostap
driver sends a deauthentication packet with reason 3 (station is
leaving).  What this does it makes it so the EAP/TLS transaction needs
to be restarted (at least as far as the Cisco is concerned) making a
very bad loop where connectivity is never reached.

Before I dive in and try to find exactly where in the set key ioctl()
this behavior is occurring, is there a setting or something that
prevents this behavior?  I can provide packet traces and register
dumps if that is useful.


BAPper



From Jacques.Caron  Wed Dec  4 17:16:22 2002
From: Jacques.Caron (Jacques Caron)
Date: Thu, 05 Dec 2002 02:16:22 +0100
Subject: deauthentication on setting WEP key
In-Reply-To: <20021205011234.GA25880@skull.piratehaven.org>
Message-ID: <5.2.0.9.0.20021205021146.024a7008@pop.mail.yahoo.com>

Hi,

Look through the archives (of the old mailing list, I'm afraid, don't know 
if they are actually still online?), I remember someone posting a patch 
that avoids this particular behavior:
>From: Glenn.Durfee at parc.com
>To: hostap at lists.ssh.com
>Subject: dynamic WEP keying
>Date: Thu, 19 Sep 2002 16:04:32 PDT

Don't know if it was integrated in the CVS tree, though.

Jacques.

At 02:12 05/12/2002, Brian Pomerantz wrote:
>I'm using the hostap driver in managed mode (client) to connect to a
>Cisco Aironet 350.  I'm using xsupplicant to handle the 802.1x
>transaction and everything looks like it is working just fine until
>the broadcast and unicast WEP keys are set.  At this point the hostap
>driver sends a deauthentication packet with reason 3 (station is
>leaving).  What this does it makes it so the EAP/TLS transaction needs
>to be restarted (at least as far as the Cisco is concerned) making a
>very bad loop where connectivity is never reached.
>
>Before I dive in and try to find exactly where in the set key ioctl()
>this behavior is occurring, is there a setting or something that
>prevents this behavior?  I can provide packet traces and register
>dumps if that is useful.
>
>
>BAPper
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap


-- Jacques Caron, IP Sector Technologies
    Join the discussion on public WLAN open global roaming:
    http://lists.ipsector.com/listinfo/openroaming





From bapper  Wed Dec  4 17:38:19 2002
From: bapper (Brian Pomerantz)
Date: Wed, 4 Dec 2002 17:38:19 -0800
Subject: deauthentication on setting WEP key
In-Reply-To: <5.2.0.9.0.20021205021146.024a7008@pop.mail.yahoo.com>
References: <20021205011234.GA25880@skull.piratehaven.org> <5.2.0.9.0.20021205021146.024a7008@pop.mail.yahoo.com>
Message-ID: <20021205013819.GA26338@skull.piratehaven.org>

Excellent!  It was a simple change.  In case anyone else wants a quick
link to it:

	http://hostap.epitest.fi/hostap/2002-09/2056.html

I tried it and it now works, thanks.


BAPper

On Thu, Dec 05, 2002 at 02:16:22AM +0100, Jacques Caron wrote:
> Hi,
> 
> Look through the archives (of the old mailing list, I'm afraid, don't know 
> if they are actually still online?), I remember someone posting a patch 
> that avoids this particular behavior:
> >From: Glenn.Durfee at parc.com
> >To: hostap at lists.ssh.com
> >Subject: dynamic WEP keying
> >Date: Thu, 19 Sep 2002 16:04:32 PDT
> 
> Don't know if it was integrated in the CVS tree, though.
> 
> Jacques.
> 
> At 02:12 05/12/2002, Brian Pomerantz wrote:
> >I'm using the hostap driver in managed mode (client) to connect to a
> >Cisco Aironet 350.  I'm using xsupplicant to handle the 802.1x
> >transaction and everything looks like it is working just fine until
> >the broadcast and unicast WEP keys are set.  At this point the hostap
> >driver sends a deauthentication packet with reason 3 (station is
> >leaving).  What this does it makes it so the EAP/TLS transaction needs
> >to be restarted (at least as far as the Cisco is concerned) making a
> >very bad loop where connectivity is never reached.
> >
> >Before I dive in and try to find exactly where in the set key ioctl()
> >this behavior is occurring, is there a setting or something that
> >prevents this behavior?  I can provide packet traces and register
> >dumps if that is useful.
> >
> >
> >BAPper
> >_______________________________________________
> >HostAP mailing list
> >HostAP at shmoo.com
> >http://lists.shmoo.com/mailman/listinfo/hostap
> 
> 
> -- Jacques Caron, IP Sector Technologies
>    Join the discussion on public WLAN open global roaming:
>    http://lists.ipsector.com/listinfo/openroaming
> 



From djennings  Wed Dec  4 04:22:12 2002
From: djennings (Derek Jennings)
Date: Wed, 4 Dec 2002 12:22:12 +0000
Subject: HostAP for USB?
Message-ID: <200212041222.12208.djennings@operamail.com>

Probably a long shot, but does anyone know of a way to get HostAP to work with 
USB?

TIA

derek




From jkmaline  Wed Dec  4 19:01:02 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 4 Dec 2002 19:01:02 -0800
Subject: Problems with the last CVS version
In-Reply-To: <3DEE981D.6080708@estudiant.upc.es>
References: <3DEE981D.6080708@estudiant.upc.es>
Message-ID: <20021205030102.GA1000@jm.kir.nu>

On Thu, Dec 05, 2002 at 01:04:45AM +0100, Victor Aleo wrote:

> I have the next problem when a station tx data frames to the AP (both 
> running the last CVS version):
> 
> wlan0: RX: dropped FCSErr frame (status=01)
> wlan0: RX: dropped FCSErr frame (status=2001)
> wlan0: RX: unknown MACPort 5

Are you using bridging or having wlan0 configured to promiscuous mode?
The patch for adding support to station mode promiscuous sniffing and
multicast caused these things to be printed. Previously firmware dropped
those frames before they hit the driver.

I might revert that patch as far as AP mode is concerned, i.e., not to
set promiscuous mode in Host AP mode. It is not needed anyway since
802.11 AP is already receiving all data frames in its own BSS.

> FCS stands for Frame Check Sequence, if I'm not wrong, but I do not know 
> what is the problem. I did not have problems with the 2002-10-12 version 
> of the driver. At the end, more than a half of the packets are not 
> transmitted. Moreover, the driver decreases the date bit rate of the 
> station from 11 to 1 Mbps.

That might be something else.. I would have assumed that those FCS
errors would not cause this kind of problems (unless printing them is
using too much CPU power). If you would like to test something before I
change the CVS version, you could just comment out
HFA384X_RID_PROMISCUOUSMODE setting in hostap_hw.c function
prism2_setup_rids(). It should at least remove those "dropped FCSErr
frame" messages and reduce the number of "unknown MACPort" errors.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Dec  4 19:13:21 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 4 Dec 2002 19:13:21 -0800
Subject: deauthentication on setting WEP key
In-Reply-To: <20021205013819.GA26338@skull.piratehaven.org>
References: <20021205011234.GA25880@skull.piratehaven.org> <5.2.0.9.0.20021205021146.024a7008@pop.mail.yahoo.com> <20021205013819.GA26338@skull.piratehaven.org>
Message-ID: <20021205031321.GB1000@jm.kir.nu>

On Wed, Dec 04, 2002 at 05:38:19PM -0800, Brian Pomerantz wrote:

> Excellent!  It was a simple change.  In case anyone else wants a quick
> link to it:
> 
> 	http://hostap.epitest.fi/hostap/2002-09/2056.html
> 
> I tried it and it now works, thanks.

There is just one problem with that patch (or Intersil documentation)..
Changed WEP keys should be taken into use only after port0 has been
reseted. I haven't merged this patch into the CVS for this reason since
I haven't had time to test it thorougly.

Anyway, if one is using host decryption and encryption, this port reset
should not be needed (assuming WEP was already set before). I will need
to experiment a bit more with this and make that reset code conditional
at least for station mode.

I think there is a difference in how Cisco AP and hostapd handle new .11
authentications and .1x. If I remember correctly, I decided to start new
.1x authentication only when the station arrives for the first time and
not for the possible re-authentication. But yes, I would agree that it
would be nicer if the station would not start new authentication every
time WEP setup is changed.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Dec  4 19:37:39 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 4 Dec 2002 19:37:39 -0800
Subject: Compiling problems with RedHat
In-Reply-To: <3613.194.157.0.2.1039015144.squirrel@netlandzone.dyndns.org>
References: <55956.136.182.2.222.1038866649.squirrel@westnelson.net> <1902.194.157.0.2.1038933765.squirrel@netlandzone.dyndns.org> <19869.136.182.2.222.1038954534.squirrel@westnelson.net> <3613.194.157.0.2.1039015144.squirrel@netlandzone.dyndns.org>
Message-ID: <20021205033739.GA1350@jm.kir.nu>

On Wed, Dec 04, 2002 at 05:19:04PM +0200, jar at pcuf.fi wrote:

> [root at redhat73 utils]# make
> cc -O2 -Wall -I/usr/src/linux/include   -c -o prism2_srec.o prism2_srec.c
> In file included from /usr/src/linux/include/linux/wireless.h:70,
>                  from prism2_srec.c:20:
> /usr/src/linux/include/linux/ethtool.h:18: parse error before `u32'

What is this? Including ethtool.h from wireless.h... I haven't seen that
in kernel.org tree, so that is probably something Red Hat specific.

Well, I should not really be including kernel header files to user
space, but linux/wireless.h is something that is really needed.. It
might be useful to get it from something else like C library etc. at
some point, but for now, it is going to come from the kernel.

You might try moving '#include "util.h"' line in prism2_srec.c before
'#include <linux/wireless.h>' to fix this. util.h will end up defining
that u32, so it might be enough. I do not have (and I do not indent to
get ;-) Red Hat kernel tree, so I have not tested this.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jasonb  Wed Dec  4 19:41:03 2002
From: jasonb (Jason Boxman)
Date: Wed, 4 Dec 2002 22:41:03 -0500
Subject: HostAP for USB?
In-Reply-To: <200212041222.12208.djennings@operamail.com>
References: <200212041222.12208.djennings@operamail.com>
Message-ID: <200212042241.03231.jasonb@edseek.com>

On Wednesday 04 December 2002 07:22 am, Derek Jennings wrote:
> Probably a long shot, but does anyone know of a way to get HostAP to work
> with USB?

There is no USB support currently.

> TIA
>
> derek
>

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages





From jkmaline  Wed Dec  4 19:42:44 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 4 Dec 2002 19:42:44 -0800
Subject: HostAP for USB?
In-Reply-To: <200212041222.12208.djennings@operamail.com>
References: <200212041222.12208.djennings@operamail.com>
Message-ID: <20021205034244.GB1350@jm.kir.nu>

On Wed, Dec 04, 2002 at 12:22:12PM +0000, Derek Jennings wrote:

> Probably a long shot, but does anyone know of a way to get HostAP to work with 
> USB?

I have heard about at least two projects that have attempted to make
this work. However, I have not seen any code or heard of these at least
during last month or so. I do not have any Prism2 USB devices, so this
has not been that important for me. If someone would like to get me more
interested on the subject, be prepared to donate such device and I'll
check what I can do about getting that port running.. ;-)

-- 
Jouni Malinen                                            PGP id EFC895FA



From blade  Wed Dec  4 22:13:54 2002
From: blade (Jeff Meden)
Date: Thu, 05 Dec 2002 01:13:54 -0500
Subject: RTS
In-Reply-To: <20021204213133.GA25362@bougret.hpl.hp.com>
References: <20021204213133.GA25362@bougret.hpl.hp.com>
Message-ID: <3DEEEEA2.3090800@ncweb.com>

I have been working with michael on some performance issues in hostap,
and we have been seeing similar patterns relating to the tuning, namely
RTS threshold as set up by iwconfig seems to have little or no effect,
and although we have no way of checking definately for RTS usage, the
performance we see suggests that it is being used rarely if ever.   Is
there a way to see the rts activity by clients or the hostap driver?

Jeff Meden



Jean Tourrilhes wrote:

>Michael wrote :
>  
>
>>Can I set RTS info in HOSTAP
>>
>>if so where do I set it?
>>    
>>
>
>	man iwconfig
>
>  
>
>>and can someone explain (in detail) what it does, or tell me where I can 
>>find information on it.
>>    
>>
>
>	It's in the Howto.
>
>	Jean
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>
>  
>






From antonio.vilei  Thu Dec  5 02:05:21 2002
From: antonio.vilei (Antonio Vilei)
Date: Thu, 5 Dec 2002 11:05:21 +0100
Subject: receive frames with FCS errors
References: <20021204212942.GA25281@bougret.hpl.hp.com>
Message-ID: <004e01c29c45$d2457900$151e0a0a@stmantoniov>

Jean Tourrilhes wrote:

> error in unlicensed band are usually clustered (fading,
> interference), which means that packet that would "look" OK are
> usually not really usefull (which explain why FEC is useless, ask
> people using BlueTooth-SCO links about it).

Could you please explain what you mean by "look OK"? 

Why is FEC useless?

Thanks in advance,
Antonio





From ian.cass  Thu Dec  5 07:39:35 2002
From: ian.cass (Ian Cass)
Date: Thu, 5 Dec 2002 15:39:35 -0000
Subject: Linux 2.2
Message-ID: <04d801c29c74$840143d0$4c28a8c0@cblan.mblox.com>

Does HostAP work on older 2.2 series kernels and if so, what about Wireless
Extensions versions?

--
Ian Cass




From jar  Thu Dec  5 07:47:37 2002
From: jar (jar)
Date: Thu, 05 Dec 2002 17:47:37 +0200
Subject: Compiling problems with RedHat
References: <55956.136.182.2.222.1038866649.squirrel@westnelson.net> <1902.194.157.0.2.1038933765.squirrel@netlandzone.dyndns.org> <19869.136.182.2.222.1038954534.squirrel@westnelson.net> <3613.194.157.0.2.1039015144.squirrel@netlandzone.dyndns.org> <20021205033739.GA1350@jm.kir.nu>
Message-ID: <3DEF7519.B36EEDDB@pcuf.fi>


Jouni Malinen wrote:
> 
> On Wed, Dec 04, 2002 at 05:19:04PM +0200, jar at pcuf.fi wrote:
> 
> > [root at redhat73 utils]# make
> > cc -O2 -Wall -I/usr/src/linux/include   -c -o prism2_srec.o prism2_srec.c
> > In file included from /usr/src/linux/include/linux/wireless.h:70,
> >                  from prism2_srec.c:20:
> > /usr/src/linux/include/linux/ethtool.h:18: parse error before `u32'
> 
> What is this? Including ethtool.h from wireless.h... I haven't seen that
> in kernel.org tree, so that is probably something Red Hat specific.

I comment the ethtool.h out from the wireless.h in the kernel source and
after that
the stuff under /utils and /hostapd compiled fine. Thanks !

Regards, Jar



From doug  Thu Dec  5 08:19:57 2002
From: doug (Doug Yeager)
Date: Thu, 5 Dec 2002 11:19:57 -0500
Subject: WEP help
Message-ID: <000001c29c7a$2d983c50$1300a8c0@DOUG1>

I'm looking for some kind of help guild to explain to me the basic
concepts of WEP.
 
Right now I have a few wireless nodes serving various coffee shops.  I
have not experimented with WEP.
 
What I think it does is this:  allow any client to select to use WEP and
pick their own key.
Then they can talk w/ the AP using that encryption key that they picked.
 
But those who just want to talk w/ the AP w/o WEP can do so also.  
 
I may be wrong on how WEP is used but that is what I thought it should
do.
 
I've experimented w/ setting my AP in open mode w/ some random key using
iwconfig util.  
 
Iwconfig wlan0 s:aircom open
 
This doesn't seem to do what I want.  Actually it cuts off communication
to my clients.
 
 
If someone could clear up how wep is used, it may help a bit along with
what commands to enable it how it want to use it would be helpful.
Or if a document tells me somewhere, that reference would be great.
 
Thx much,
doug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021205/9d0e5213/attachment.htm 


From Joshua.Wright  Thu Dec  5 08:27:15 2002
From: Joshua.Wright (Joshua Wright)
Date: Thu, 5 Dec 2002 11:27:15 -0500
Subject: WEP help
Message-ID: <156AA90517398D479A3473C35CE99EDD0157A5B8@pvdexc99.jwu.edu>

Doug,

WEP wasn't designed to be used in the fashion you are describing - the WEP keys must be known to both parties before being able to communicate.

I'm not sure how you would establish a mechanism where the client tells the AP what WEP key they want to use.  Even if you did get past that stumbling block, you would need to communicate the key in the clear before using it - which would give an attacker the key to decode the traffic with. :(

-Joshua Wright
Team Leader, Networks and Systems
Johnson & Wales University
Joshua.Wright at jwu.edu 
http://home.jwu.edu/jwright/

pgpkey: http://home.jwu.edu/jwright/pgpkey.htm
fingerprint: FDA5 12FC F391 3740 E0AE BDB6 8FE2 FC0A D44B 4A73


-----Original Message-----
From: Doug Yeager [mailto:doug at aircomwireless.net]
Sent: Thursday, December 05, 2002 11:20 AM
To: hostap at shmoo.com
Subject: WEP help


I'm looking for some kind of help guild to explain to me the basic concepts of WEP.
 
Right now I have a few wireless nodes serving various coffee shops.  I have not experimented with WEP.
 
What I think it does is this:  allow any client to select to use WEP and pick their own key.
Then they can talk w/ the AP using that encryption key that they picked.
 
But those who just want to talk w/ the AP w/o WEP can do so also.  
 
I may be wrong on how WEP is used but that is what I thought it should do.
 
I've experimented w/ setting my AP in open mode w/ some random key using iwconfig util.  
 
Iwconfig wlan0 s:aircom open
 
This doesn't seem to do what I want.  Actually it cuts off communication to my clients.
 
 
If someone could clear up how wep is used, it may help a bit along with what commands to enable it how it want to use it would be helpful.
Or if a document tells me somewhere, that reference would be great.
 
Thx much,
doug



From Jacques.Caron  Thu Dec  5 08:37:39 2002
From: Jacques.Caron (Jacques Caron)
Date: Thu, 05 Dec 2002 17:37:39 +0100
Subject: WEP help
In-Reply-To: <000001c29c7a$2d983c50$1300a8c0@DOUG1>
Message-ID: <5.2.0.9.0.20021205172636.017955c0@pop.mail.yahoo.com>

Hi,

The goal of WEP is (in theory) to make sure that only people who have the 
key can decrypt packets sent with that key. In the general case, this means 
you have to use so-called "pre-shared keys", i.e. keys that both ends (the 
client and the AP) know in advance. And since most APs have only a limited 
number of keys they can use, that also means that everybody is using the 
same key, and hence that everybody you give the key to will be able to 
decrypt the trafic from anyone else using the AP.

In the case of a public WLAN, the only way to use WEP is together with 
802.1x. This means:
- the client must support 802.1x, the appropriate EAP method chosen, and 
dynamic keys
- the AP must support 802.1x and dynamic keys
- you must have a RADIUS server with support for EAP and the appropriate 
EAP method chosen and the generation of dynamic keys.

In that case, when a user connects, it authenticates using the relevant EAP 
method, and a dynamic WEP key is generated and used just for that client 
(i.e. the AP handles one WEP key for each client). And no-one but the 
client and the AP can decrypt the trafic sent between them using that key.

Now, depending on what your exact security goals are, there are quite a 
number of alternatives:
- do not use WEP at all, and rely on the users having appropriate VPN 
software and/or SSL/TLS-enabled software (and servers to talk to)
- do not use WEP at all, and provide some other form of encryption for the 
customers (PPPoE, PPTP, L2TP, IPsec)

I would personally recommend using WEP with 802.1x, since:
- 802.1x is built into Windows XP
- there is now a free 802.1x add-on from MS for W2K
- versions for other Windows platforms are coming
- there is a free 802.1x client for Unix systems (open1x aka xsupplicant)
- hostap supports 802.1x
- there are free (freeRADIUS) and commercial (many) RADIUS servers that 
support 802.1x
- this will give you security and accounting
- this scheme is the only one that will enable WLAN roaming in a secure, 
open and transparent fashion

Obviously, you still need a way to allow users with 802.1x or a 
subscription to connect (without WEP) to a limited set of pages to know 
what they need, subscribe, download the necessary software, etc.

Let me know if I can be of any help :-)

Jacques.

At 17:19 05/12/2002, Doug Yeager wrote:

>Im looking for some kind of help guild to explain to me the basic concepts 
>of WEP.
>
>
>
>Right now I have a few wireless nodes serving various coffee shops.  I 
>have not experimented with WEP.
>
>
>
>What I think it does is this:  allow any client to select to use WEP and 
>pick their own key.
>
>Then they can talk w/ the AP using that encryption key that they picked.
>
>
>
>But those who just want to talk w/ the AP w/o WEP can do so also.
>
>
>
>I may be wrong on how WEP is used but that is what I thought it should do.
>
>
>
>Ive experimented w/ setting my AP in open mode w/ some random key using 
>iwconfig util.
>
>
>
>Iwconfig wlan0 s:aircom open
>
>
>
>This doesnt seem to do what I want.  Actually it cuts off communication to 
>my clients.
>
>
>
>
>
>If someone could clear up how wep is used, it may help a bit along with 
>what commands to enable it how it want to use it would be helpful.
>
>Or if a document tells me somewhere, that reference would be great.
>
>
>
>Thx much,
>
>doug


-- Jacques Caron, IP Sector Technologies
    Join the discussion on public WLAN open global roaming:
    http://lists.ipsector.com/listinfo/openroaming





From doug  Thu Dec  5 08:59:35 2002
From: doug (Doug Yeager)
Date: Thu, 5 Dec 2002 11:59:35 -0500
Subject: WEP help
In-Reply-To: <5.2.0.9.0.20021205172636.017955c0@pop.mail.yahoo.com>
Message-ID: <000901c29c7f$b5e29420$1300a8c0@DOUG1>

This is very informative Jacques...hope others can benefit also.


I'm using nocatauth for these nodes.  It would be very easy for me to
allow the user to enter their wep password into their member profile in
the authserver website...this of course would be the same one they enter
for their wifi card setup.  At that point when they login it would be
easy for me to send that password to the ap through the nocat gateway.
At that point would I be able to use a command to let the hostap know to
use that key?

Something like:
Iwconfig wlan0 key s:users_password on
?

if so, what about multiple users on that node?  Will the AP remember the
different keys and associate them to the correct clients?  Also, if
there is an open mode, can those users also be able to communicate?

Thx in advance,
doug

-----Original Message-----
From: Jacques Caron [mailto:Jacques.Caron at IPsector.com] 
Sent: Thursday, December 05, 2002 11:38 AM
To: doug at ycomsystems.com
Cc: hostap at shmoo.com
Subject: Re: WEP help

Hi,

The goal of WEP is (in theory) to make sure that only people who have
the 
key can decrypt packets sent with that key. In the general case, this
means 
you have to use so-called "pre-shared keys", i.e. keys that both ends
(the 
client and the AP) know in advance. And since most APs have only a
limited 
number of keys they can use, that also means that everybody is using the

same key, and hence that everybody you give the key to will be able to 
decrypt the trafic from anyone else using the AP.

In the case of a public WLAN, the only way to use WEP is together with 
802.1x. This means:
- the client must support 802.1x, the appropriate EAP method chosen, and

dynamic keys
- the AP must support 802.1x and dynamic keys
- you must have a RADIUS server with support for EAP and the appropriate

EAP method chosen and the generation of dynamic keys.

In that case, when a user connects, it authenticates using the relevant
EAP 
method, and a dynamic WEP key is generated and used just for that client

(i.e. the AP handles one WEP key for each client). And no-one but the 
client and the AP can decrypt the trafic sent between them using that
key.

Now, depending on what your exact security goals are, there are quite a 
number of alternatives:
- do not use WEP at all, and rely on the users having appropriate VPN 
software and/or SSL/TLS-enabled software (and servers to talk to)
- do not use WEP at all, and provide some other form of encryption for
the 
customers (PPPoE, PPTP, L2TP, IPsec)

I would personally recommend using WEP with 802.1x, since:
- 802.1x is built into Windows XP
- there is now a free 802.1x add-on from MS for W2K
- versions for other Windows platforms are coming
- there is a free 802.1x client for Unix systems (open1x aka
xsupplicant)
- hostap supports 802.1x
- there are free (freeRADIUS) and commercial (many) RADIUS servers that 
support 802.1x
- this will give you security and accounting
- this scheme is the only one that will enable WLAN roaming in a secure,

open and transparent fashion

Obviously, you still need a way to allow users with 802.1x or a 
subscription to connect (without WEP) to a limited set of pages to know 
what they need, subscribe, download the necessary software, etc.

Let me know if I can be of any help :-)

Jacques.

At 17:19 05/12/2002, Doug Yeager wrote:

>Im looking for some kind of help guild to explain to me the basic
concepts 
>of WEP.
>
>
>
>Right now I have a few wireless nodes serving various coffee shops.  I 
>have not experimented with WEP.
>
>
>
>What I think it does is this:  allow any client to select to use WEP
and 
>pick their own key.
>
>Then they can talk w/ the AP using that encryption key that they
picked.
>
>
>
>But those who just want to talk w/ the AP w/o WEP can do so also.
>
>
>
>I may be wrong on how WEP is used but that is what I thought it should
do.
>
>
>
>Ive experimented w/ setting my AP in open mode w/ some random key using

>iwconfig util.
>
>
>
>Iwconfig wlan0 s:aircom open
>
>
>
>This doesnt seem to do what I want.  Actually it cuts off communication
to 
>my clients.
>
>
>
>
>
>If someone could clear up how wep is used, it may help a bit along with

>what commands to enable it how it want to use it would be helpful.
>
>Or if a document tells me somewhere, that reference would be great.
>
>
>
>Thx much,
>
>doug


-- Jacques Caron, IP Sector Technologies
    Join the discussion on public WLAN open global roaming:
    http://lists.ipsector.com/listinfo/openroaming







From chuck  Thu Dec  5 09:42:28 2002
From: chuck (Chuck Rohs)
Date: Thu, 05 Dec 2002 10:42:28 -0700
Subject: HostAP for USB?
In-Reply-To: <20021205034244.GB1350@jm.kir.nu>
Message-ID: <MBEHIHJEBIBCNDGKJEFCMEJMCFAA.chuck@au-zone.com>

We have put USB support into the HostAP code based on USB code from absolute
value. Our clients plan to release a project that they are working on that
uses this code into sourceforge around the Christmas time frame.  They will
make an announcement on their website when this is done
(www.wirelessnetworksinc.com).  At this time we will be free to release a
tarball of our development tree to Jouni (for integration into the HostAP
baseline if he is so inclined :) and to anyone else who wants it.  I'll post
another message to the list when the code is available.

Chuck Rohs

www.au-zone.com

-----Original Message-----
From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com]On Behalf Of
Jouni Malinen
Sent: Wednesday, December 04, 2002 8:43 PM
To: hostap at shmoo.com
Subject: Re: HostAP for USB?

On Wed, Dec 04, 2002 at 12:22:12PM +0000, Derek Jennings wrote:

> Probably a long shot, but does anyone know of a way to get HostAP to work
with
> USB?

I have heard about at least two projects that have attempted to make
this work. However, I have not seen any code or heard of these at least
during last month or so. I do not have any Prism2 USB devices, so this
has not been that important for me. If someone would like to get me more
interested on the subject, be prepared to donate such device and I'll
check what I can do about getting that port running.. ;-)

--
Jouni Malinen                                            PGP id EFC895FA
_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap




From Jacques.Caron  Thu Dec  5 10:03:46 2002
From: Jacques.Caron (Jacques Caron)
Date: Thu, 05 Dec 2002 19:03:46 +0100
Subject: WEP help
Message-ID: <5.2.0.9.0.20021205190323.01769f08@wheresmymailserver.com>

Hi,

I know the driver supports per-client keys, but I don't know offhand how 
you would be able to change those keys from userland, probably some form of 
ioctl (I'm not sure there is a command or iwconfig param that does this), 
you might want to look into the hostapd source code, since that program is 
actually doing the 802.1x bit and the WEP key setting. Probably not very 
difficult to write a very short program that would take a MAC address and 
WEP key and give that information to the driver, if there isn't one already.

Note however that if using nocatauth rather than 802.1x, you end up with 
the problem that the user must switch from unencrypted to encrypted right 
after the authentication is done (you have to start without encryption 
because the AP does not know who it is at first). Also it would not give 
you the advantages of dynamic keying and automatic configuration (the user 
actually needs to enter the key, and will keep the same key for a while, 
which leaves WEP open to its known weaknesses). 802.1x on the other hand 
would give you automatic configuration and dynamic re-keying.

Do I sound like a big 802.1x advocate? :-)

Jacques.

At 17:58 05/12/2002, Doug Yeager wrote:
>This is very informative Jacques...hope others can benefit also.
>
>
>I'm using nocatauth for these nodes.  It would be very easy for me to
>allow the user to enter their wep password into their member profile in
>the authserver website...this of course would be the same one they enter
>for their wifi card setup.  At that point when they login it would be
>easy for me to send that password to the ap through the nocat gateway.
>At that point would I be able to use a command to let the hostap know to
>use that key?
>
>Something like:
>Iwconfig wlan0 key s:users_password on
>?
>
>if so, what about multiple users on that node?  Will the AP remember the
>different keys and associate them to the correct clients?  Also, if
>there is an open mode, can those users also be able to communicate?
>
>Thx in advance,
>doug
>
>-----Original Message-----
>From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] On Behalf
>Of Jacques Caron
>Sent: Thursday, December 05, 2002 11:38 AM
>To: doug at ycomsystems.com
>Cc: hostap at shmoo.com
>Subject: Re: WEP help
>
>Hi,
>
>The goal of WEP is (in theory) to make sure that only people who have
>the
>key can decrypt packets sent with that key. In the general case, this
>means
>you have to use so-called "pre-shared keys", i.e. keys that both ends
>(the
>client and the AP) know in advance. And since most APs have only a
>limited
>number of keys they can use, that also means that everybody is using the
>
>same key, and hence that everybody you give the key to will be able to
>decrypt the trafic from anyone else using the AP.
>
>In the case of a public WLAN, the only way to use WEP is together with
>802.1x. This means:
>- the client must support 802.1x, the appropriate EAP method chosen, and
>
>dynamic keys
>- the AP must support 802.1x and dynamic keys
>- you must have a RADIUS server with support for EAP and the appropriate
>
>EAP method chosen and the generation of dynamic keys.
>
>In that case, when a user connects, it authenticates using the relevant
>EAP
>method, and a dynamic WEP key is generated and used just for that client
>
>(i.e. the AP handles one WEP key for each client). And no-one but the
>client and the AP can decrypt the trafic sent between them using that
>key.
>
>Now, depending on what your exact security goals are, there are quite a
>number of alternatives:
>- do not use WEP at all, and rely on the users having appropriate VPN
>software and/or SSL/TLS-enabled software (and servers to talk to)
>- do not use WEP at all, and provide some other form of encryption for
>the
>customers (PPPoE, PPTP, L2TP, IPsec)
>
>I would personally recommend using WEP with 802.1x, since:
>- 802.1x is built into Windows XP
>- there is now a free 802.1x add-on from MS for W2K
>- versions for other Windows platforms are coming
>- there is a free 802.1x client for Unix systems (open1x aka
>xsupplicant)
>- hostap supports 802.1x
>- there are free (freeRADIUS) and commercial (many) RADIUS servers that
>support 802.1x
>- this will give you security and accounting
>- this scheme is the only one that will enable WLAN roaming in a secure,
>
>open and transparent fashion
>
>Obviously, you still need a way to allow users with 802.1x or a
>subscription to connect (without WEP) to a limited set of pages to know
>what they need, subscribe, download the necessary software, etc.
>
>Let me know if I can be of any help :-)
>
>Jacques.
>
>At 17:19 05/12/2002, Doug Yeager wrote:
>
> >Im looking for some kind of help guild to explain to me the basic
>concepts
> >of WEP.
> >
> >
> >
> >Right now I have a few wireless nodes serving various coffee shops.  I
> >have not experimented with WEP.
> >
> >
> >
> >What I think it does is this:  allow any client to select to use WEP
>and
> >pick their own key.
> >
> >Then they can talk w/ the AP using that encryption key that they
>picked.
> >
> >
> >
> >But those who just want to talk w/ the AP w/o WEP can do so also.
> >
> >
> >
> >I may be wrong on how WEP is used but that is what I thought it should
>do.
> >
> >
> >
> >Ive experimented w/ setting my AP in open mode w/ some random key using
>
> >iwconfig util.
> >
> >
> >
> >Iwconfig wlan0 s:aircom open
> >
> >
> >
> >This doesnt seem to do what I want.  Actually it cuts off communication
>to
> >my clients.
> >
> >
> >
> >
> >
> >If someone could clear up how wep is used, it may help a bit along with
>
> >what commands to enable it how it want to use it would be helpful.
> >
> >Or if a document tells me somewhere, that reference would be great.
> >
> >
> >
> >Thx much,
> >
> >doug
>
>
>-- Jacques Caron, IP Sector Technologies
>     Join the discussion on public WLAN open global roaming:
>     http://lists.ipsector.com/listinfo/openroaming
>
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap


-- Jacques Caron, IP Sector Technologies
    Join the discussion on public WLAN open global roaming:
    http://lists.ipsector.com/listinfo/openroaming





From doug  Thu Dec  5 10:11:02 2002
From: doug (Doug Yeager)
Date: Thu, 5 Dec 2002 13:11:02 -0500
Subject: WEP help
In-Reply-To: <5.2.0.9.0.20021205182125.01795700@wheresmymailserver.com>
Message-ID: <000001c29c89$b1c9cc00$1300a8c0@DOUG1>

I totally agree with you.
No cat auth really is just an authentication to allow people through the
gateway.  I think it is on a different level than the WEP encryption.

I think I can do exactly what you are saying w/ 802.1x  as when the user
gets to a hotspot they can surf the local lan all they want but when
they try to go to the internet and ftp and such to the internet
nocatauth kicks in.

So I think what you are saying is that the hostap can assign the keys to
the clients based on the mac address of the client card.  That is
perfect!

I can see if hostap has that capability I think.  Anybody out there try
this?!

Now, on the client, how do you set it up so they have this capability?

My linksys card always wants me to put in my own pass phrase or keys.  I
don't want it to ask.  I just want the server to assign me one and me to
accept it like https.

Thx,
doug

-----Original Message-----
From: Jacques Caron [mailto:Jacques.Caron at IPsector.com] 
Sent: Thursday, December 05, 2002 12:28 PM
To: doug at ycomsystems.com
Subject: RE: WEP help

Hi,

I know the driver supports per-client keys, but I don't know offhand how

you would be able to change those keys from userland, probably some form
of 
ioctl (I'm not sure there is a command or iwconfig param that does
this), 
you might want to look into the hostapd source code, since that program
is 
actually doing the 802.1x bit and the WEP key setting. Probably not very

difficult to write a very short program that would take a MAC address
and 
WEP key and give that information to the driver, if there isn't one
already.

Note however that if using nocatauth rather than 802.1x, you end up with

the problem that the user must switch from unencrypted to encrypted
right 
after the authentication is done (you have to start without encryption 
because the AP does not know who it is at first). Also it would not give

you the advantages of dynamic keying and automatic configuration (the
user 
actually needs to enter the key, and will keep the same key for a while,

which leaves WEP open to its known weaknesses). 802.1x on the other hand

would give you automatic configuration and dynamic re-keying.

Do I sound like a big 802.1x advocate? :-)

Jacques.

At 17:58 05/12/2002, Doug Yeager wrote:
>This is very informative Jacques...hope others can benefit also.
>
>
>I'm using nocatauth for these nodes.  It would be very easy for me to
>allow the user to enter their wep password into their member profile in
>the authserver website...this of course would be the same one they
enter
>for their wifi card setup.  At that point when they login it would be
>easy for me to send that password to the ap through the nocat gateway.
>At that point would I be able to use a command to let the hostap know
to
>use that key?
>
>Something like:
>Iwconfig wlan0 key s:users_password on
>?
>
>if so, what about multiple users on that node?  Will the AP remember
the
>different keys and associate them to the correct clients?  Also, if
>there is an open mode, can those users also be able to communicate?
>
>Thx in advance,
>doug
>
>-----Original Message-----
>From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] On Behalf
>Of Jacques Caron
>Sent: Thursday, December 05, 2002 11:38 AM
>To: doug at ycomsystems.com
>Cc: hostap at shmoo.com
>Subject: Re: WEP help
>
>Hi,
>
>The goal of WEP is (in theory) to make sure that only people who have
>the
>key can decrypt packets sent with that key. In the general case, this
>means
>you have to use so-called "pre-shared keys", i.e. keys that both ends
>(the
>client and the AP) know in advance. And since most APs have only a
>limited
>number of keys they can use, that also means that everybody is using
the
>
>same key, and hence that everybody you give the key to will be able to
>decrypt the trafic from anyone else using the AP.
>
>In the case of a public WLAN, the only way to use WEP is together with
>802.1x. This means:
>- the client must support 802.1x, the appropriate EAP method chosen,
and
>
>dynamic keys
>- the AP must support 802.1x and dynamic keys
>- you must have a RADIUS server with support for EAP and the
appropriate
>
>EAP method chosen and the generation of dynamic keys.
>
>In that case, when a user connects, it authenticates using the relevant
>EAP
>method, and a dynamic WEP key is generated and used just for that
client
>
>(i.e. the AP handles one WEP key for each client). And no-one but the
>client and the AP can decrypt the trafic sent between them using that
>key.
>
>Now, depending on what your exact security goals are, there are quite a
>number of alternatives:
>- do not use WEP at all, and rely on the users having appropriate VPN
>software and/or SSL/TLS-enabled software (and servers to talk to)
>- do not use WEP at all, and provide some other form of encryption for
>the
>customers (PPPoE, PPTP, L2TP, IPsec)
>
>I would personally recommend using WEP with 802.1x, since:
>- 802.1x is built into Windows XP
>- there is now a free 802.1x add-on from MS for W2K
>- versions for other Windows platforms are coming
>- there is a free 802.1x client for Unix systems (open1x aka
>xsupplicant)
>- hostap supports 802.1x
>- there are free (freeRADIUS) and commercial (many) RADIUS servers that
>support 802.1x
>- this will give you security and accounting
>- this scheme is the only one that will enable WLAN roaming in a
secure,
>
>open and transparent fashion
>
>Obviously, you still need a way to allow users with 802.1x or a
>subscription to connect (without WEP) to a limited set of pages to know
>what they need, subscribe, download the necessary software, etc.
>
>Let me know if I can be of any help :-)
>
>Jacques.
>
>At 17:19 05/12/2002, Doug Yeager wrote:
>
> >Im looking for some kind of help guild to explain to me the basic
>concepts
> >of WEP.
> >
> >
> >
> >Right now I have a few wireless nodes serving various coffee shops.
I
> >have not experimented with WEP.
> >
> >
> >
> >What I think it does is this:  allow any client to select to use WEP
>and
> >pick their own key.
> >
> >Then they can talk w/ the AP using that encryption key that they
>picked.
> >
> >
> >
> >But those who just want to talk w/ the AP w/o WEP can do so also.
> >
> >
> >
> >I may be wrong on how WEP is used but that is what I thought it
should
>do.
> >
> >
> >
> >Ive experimented w/ setting my AP in open mode w/ some random key
using
>
> >iwconfig util.
> >
> >
> >
> >Iwconfig wlan0 s:aircom open
> >
> >
> >
> >This doesnt seem to do what I want.  Actually it cuts off
communication
>to
> >my clients.
> >
> >
> >
> >
> >
> >If someone could clear up how wep is used, it may help a bit along
with
>
> >what commands to enable it how it want to use it would be helpful.
> >
> >Or if a document tells me somewhere, that reference would be great.
> >
> >
> >
> >Thx much,
> >
> >doug
>
>
>-- Jacques Caron, IP Sector Technologies
>     Join the discussion on public WLAN open global roaming:
>     http://lists.ipsector.com/listinfo/openroaming
>
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap


-- Jacques Caron, IP Sector Technologies
    Join the discussion on public WLAN open global roaming:
    http://lists.ipsector.com/listinfo/openroaming







From jasonb  Thu Dec  5 12:43:01 2002
From: jasonb (Jason Boxman)
Date: Thu, 5 Dec 2002 15:43:01 -0500
Subject: WEP help
In-Reply-To: <5.2.0.9.0.20021205172636.017955c0@pop.mail.yahoo.com>
References: <5.2.0.9.0.20021205172636.017955c0@pop.mail.yahoo.com>
Message-ID: <200212051543.01305.jasonb@edseek.com>

On Thursday 05 December 2002 11:37 am, Jacques Caron wrote:
> Hi,
>
<snip>
> I would personally recommend using WEP with 802.1x, since:
> - 802.1x is built into Windows XP
> - there is now a free 802.1x add-on from MS for W2K

Where might this be?  This is the only missing thing preventing me from 
writing an article on setting up 802.1x using HostAP and Windows clients.

> - versions for other Windows platforms are coming
> - there is a free 802.1x client for Unix systems (open1x aka xsupplicant)
> - hostap supports 802.1x
> - there are free (freeRADIUS) and commercial (many) RADIUS servers that
> support 802.1x
> - this will give you security and accounting
> - this scheme is the only one that will enable WLAN roaming in a secure,
> open and transparent fashion
>
> Obviously, you still need a way to allow users with 802.1x or a
> subscription to connect (without WEP) to a limited set of pages to know
> what they need, subscribe, download the necessary software, etc.
>
> Let me know if I can be of any help :-)
>
<snip>
> -- Jacques Caron, IP Sector Technologies
>     Join the discussion on public WLAN open global roaming:
>     http://lists.ipsector.com/listinfo/openroaming
>

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages





From owens  Thu Dec  5 13:12:51 2002
From: owens (Owen Shoemaker)
Date: Thu, 5 Dec 2002 13:12:51 -0800
Subject: hostapd startup
Message-ID: <5039C590-0896-11D7-A2EE-000393D5F2BA@speakeasy.net>

I have been trying to get hostapd working and have had some troubles.  
After configuring my network on wlan0 I fire up hostapd with 'hostapd 
-xm wlan0' and I am able to authenticate with a winXP machine.   The 
problem is that even after authenticating and verifying that I am 
authenticated on the AP I can't get any IP connectivity.  Does anyone 
know of any good documentation other than the PRISM2 readme?  Maybe 
tips on network config and startup scripts?  Do I need to add IP info 
to the wlan0ap device?  Shouldn't after auth just forward the traffic 
to the wlan0 device?  I haven't really dug too deep yet but just wanted 
to know if my settings were correct.

Here are my current settings:
owens at paragon:~$ less iwconfig_list
wlan0     IEEE 802.11-b  ESSID:"test"
           Mode:Master  Frequency:2.422GHz  Access Point: 
00:02:6F:01:FB:1B
           Bit Rate:11Mb/s   Tx-Power:-7 dBm   Sensitivity=1/3
           Retry min limit:8   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality:0  Signal level:0  Noise level:0
           Rx invalid nwid:0  Rx invalid crypt:628  Rx invalid frag:0
           Tx excessive retries:3033  Invalid misc:16910   Missed 
beacon:0

wlan0ap   IEEE 802.11-b  ESSID:"test"
           Mode:Master  Frequency:2.422GHz  Access Point: 
00:02:6F:01:FB:1B
           Bit Rate:11Mb/s   Tx-Power:-7 dBm   Sensitivity=1/3
           Retry min limit:8   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off

owens at paragon:~$ less ifconfig_list
  eth0      Link encap:Ethernet  HWaddr 00:01:02:EB:B0:C5
           inet addr:216.254.0.49  Bcast:216.254.0.255  
Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:695297 errors:0 dropped:0 overruns:0 frame:0
           TX packets:101 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:100
           RX bytes:43662096 (41.6 Mb)  TX bytes:6942 (6.7 Kb)
           Interrupt:12 Base address:0xc000

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:2 errors:0 dropped:0 overruns:0 frame:0
           TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:150 (150.0 b)  TX bytes:150 (150.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:02:6F:01:FB:1B
           inet addr:192.168.201.1  Bcast:192.168.201.255  
Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:2 errors:0 dropped:506 overruns:0 frame:0
           TX packets:939 errors:540 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:100
           RX bytes:0 (0.0 b)  TX bytes:288 (288.0 b)
           Interrupt:11 Base address:0x100

output of hostapd -dxm wlan0:

Opening raw packet socket for ifindex 5
Using interface wlan0ap with hwaddr 00:02:6f:01:fb:1b and ssid 'test'
Flushing old station entries
Received 30 bytes management frame
MGMT
mgmt::auth
authentication: STA=00:02:dd:32:48:e0 auth_alg=0 auth_transaction=1 
status_code=0
   New STA
Station 00:02:dd:32:48:e0 authenticated (open system)
Received 40 bytes management frame
MGMT
mgmt::assoc_req
association request: STA=00:02:dd:32:48:e0 capab_info=0x01 
listen_interval=1
   new AID 1
Station 00:02:dd:32:48:e0 associated (aid 1)
IEEE 802.1X: Start authentication for new station 00:02:dd:32:48:e0
IEEE 802.1X: 00:02:dd:32:48:e0 AUTH_PAE entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 BE_AUTH entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 AUTH_KEY_TX entering state 
NO_KEY_TRANSMIT
IEEE 802.1X: 00:02:dd:32:48:e0 AUTH_PAE entering state DISCONNECTED
IEEE 802.1X: Unauthorizing station 00:02:dd:32:48:e0
IEEE 802.1X: Sending canned EAP packet FAILURE to 00:02:dd:32:48:e0 
(identifier 0)
IEEE 802.1X: 00:02:dd:32:48:e0 BE_AUTH entering state IDLE
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 AUTH_PAE entering state CONNECTING
IEEE 802.1X: Sending EAP Request-Identity to 00:02:dd:32:48:e0 
(identifier 1)
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
Received 37 bytes management frame
DATA
IEEE 802.1X: 5 bytes from 00:02:dd:32:48:e0
    IEEE 802.1X: version=1 type=1 length=0
    ignoring 1 extra octets after IEEE 802.1X packet
    EAPOL-Start
IEEE 802.1X: 00:02:dd:32:48:e0 AUTH_PAE entering state CONNECTING
IEEE 802.1X: Sending EAP Request-Identity to 00:02:dd:32:48:e0 
(identifier 1)
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
Received 46 bytes management frame
DATA
IEEE 802.1X: 14 bytes from 00:02:dd:32:48:e0
    IEEE 802.1X: version=1 type=0 length=10
    EAP: code=2 identifier=1 length=10 (response)
    EAP Response-Identity
IEEE 802.1X: 00:02:dd:32:48:e0 AUTH_PAE entering state AUTHENTICATING
IEEE 802.1X: 00:02:dd:32:48:e0 BE_AUTH entering state RESPONSE
Minimal Authentication Server
Minimal Authentication Server: station 00:02:dd:32:48:e0 EAP 
Response-Identity: (len=10) 'owens'
IEEE 802.1X: 00:02:dd:32:48:e0 BE_AUTH entering state SUCCESS
IEEE 802.1X: Sending canned EAP packet SUCCESS to 00:02:dd:32:48:e0 
(identifier 0)
IEEE 802.1X: 00:02:dd:32:48:e0 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:02:dd:32:48:e0 AUTH_PAE entering state AUTHENTICATED
IEEE 802.1X: Authorizing station 00:02:dd:32:48:e0
IEEE 802.1X: 00:02:dd:32:48:e0 BE_AUTH entering state IDLE
Signal 2 received - terminating
Flushing old station entries
Deauthenticate all stations


--
Owen Shoemaker




From doug  Thu Dec  5 13:24:35 2002
From: doug (Doug Yeager)
Date: Thu, 5 Dec 2002 16:24:35 -0500
Subject: WEP help
In-Reply-To: <200212051543.01305.jasonb@edseek.com>
Message-ID: <000001c29ca4$bcb344f0$1300a8c0@DOUG1>

Agreed, I need these two things and I'm ready to go w/ this:
> I would personally recommend using WEP with 802.1x, since:
> - 802.1x is built into Windows XP
> - there is now a free 802.1x add-on from MS for W2K

also need to know how to do this:

> Obviously, you still need a way to allow users with 802.1x or a
> subscription to connect (without WEP) to a limited set of pages to
know
> what they need, subscribe, download the necessary software, etc.

any thoughts on how to do this?

I guess my question is... if you set up hostapd to do encryption, is it
optional to the client?  Can they use the network at all w/o wep so they
can hit a website and signup?

Anyone done this?

Thx,
doug
-----Original Message-----
From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] On Behalf
Of Jason Boxman
Sent: Thursday, December 05, 2002 3:43 PM
To: hostap at shmoo.com
Subject: Re: WEP help

On Thursday 05 December 2002 11:37 am, Jacques Caron wrote:
> Hi,
>
<snip>
> I would personally recommend using WEP with 802.1x, since:
> - 802.1x is built into Windows XP
> - there is now a free 802.1x add-on from MS for W2K

Where might this be?  This is the only missing thing preventing me from 
writing an article on setting up 802.1x using HostAP and Windows
clients.

> - versions for other Windows platforms are coming
> - there is a free 802.1x client for Unix systems (open1x aka
xsupplicant)
> - hostap supports 802.1x
> - there are free (freeRADIUS) and commercial (many) RADIUS servers
that
> support 802.1x
> - this will give you security and accounting
> - this scheme is the only one that will enable WLAN roaming in a
secure,
> open and transparent fashion
>
> Obviously, you still need a way to allow users with 802.1x or a
> subscription to connect (without WEP) to a limited set of pages to
know
> what they need, subscribe, download the necessary software, etc.
>
> Let me know if I can be of any help :-)
>
<snip>
> -- Jacques Caron, IP Sector Technologies
>     Join the discussion on public WLAN open global roaming:
>     http://lists.ipsector.com/listinfo/openroaming
>

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages


_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap





From jt  Thu Dec  5 18:40:56 2002
From: jt (Jean Tourrilhes)
Date: Thu, 5 Dec 2002 18:40:56 -0800
Subject: [PATCH] : Scan in master mode
Message-ID: <20021206024056.GA2255@bougret.hpl.hp.com>

	Hi,

	As part of WE-16, I'm improving the iwspy support. HostAP is
currently problematic as I want to "reclaim" the SIOCGIWSPY call, and
HostAP currently uses it.

	So, I've decided 2 things :
	1) I've un-deprecated SIOCGIWAPLIST and broaden its
definition. You can now return any list of address you want, not only
APs, and will remain supported.
	2) I've made the little patch below (for 2002-10-12) and I'm
suggesting its inclusion in HostAP. The patch was *very* quickly
tested.

	Jouni, any comments ?

	Have fun...

	Jean

-------------- next part --------------
diff -u -p driver/modules.15/hostap.c driver/modules/hostap.c
--- driver/modules.15/hostap.c	Sun Sep 15 10:33:05 2002
+++ driver/modules/hostap.c	Thu Dec  5 18:25:47 2002
@@ -63,6 +63,9 @@ static int prism2_wds_del(local_info_t *
 static int prism2_ap_get_sta_qual(local_info_t *local, struct sockaddr addr[],
 				  struct iw_quality qual[], int buf_size,
 				  int aplist);
+#if WIRELESS_EXT > 13
+static int prism2_ap_translate_scan(struct net_device *dev, char *buffer);
+#endif /* WIRELESS_EXT > 13 */
 #endif /* WIRELESS_EXT */
 static int prism2_hostapd(struct ap_data *ap,
 			  struct prism2_hostapd_param *param);
diff -u -p driver/modules.15/hostap_ap.c driver/modules/hostap_ap.c
--- driver/modules.15/hostap_ap.c	Sat Sep 14 08:54:12 2002
+++ driver/modules/hostap_ap.c	Thu Dec  5 18:30:19 2002
@@ -2129,6 +2129,84 @@ static int prism2_ap_get_sta_qual(local_
 
 	return count;
 }
+
+#if WIRELESS_EXT > 13
+/* Translate our list of Access Points & Stations to a card independant
+ * format that the Wireless Tools will understand - Jean II */
+static int prism2_ap_translate_scan(struct net_device *dev, char *buffer)
+{
+	local_info_t *local = (local_info_t *) dev->priv;
+	struct ap_data *ap = local->ap;
+	struct list_head *ptr;
+	unsigned long flags;
+	struct iw_event iwe;
+	char *current_ev = buffer;
+	char *end_buf = buffer + IW_SCAN_MAX_DATA;
+
+	spin_lock_irqsave(&ap->sta_table_lock, flags);
+
+	for (ptr = ap->sta_list.next; ptr != NULL && ptr != &ap->sta_list;
+	     ptr = ptr->next) {
+		struct sta_info *sta = (struct sta_info *) ptr;
+
+		/* First entry *MUST* be the AP MAC address */
+		memset(&iwe, 0, sizeof(iwe));
+		iwe.cmd = SIOCGIWAP;
+		iwe.u.ap_addr.sa_family = ARPHRD_ETHER;
+		memcpy(iwe.u.ap_addr.sa_data, sta->addr, ETH_ALEN);
+		iwe.len = IW_EV_ADDR_LEN;
+		current_ev = iwe_stream_add_event(current_ev, end_buf, &iwe,
+						  IW_EV_ADDR_LEN);
+
+		/* Use the mode to indicate if it's a station or
+		 * an Access Point */
+		memset(&iwe, 0, sizeof(iwe));
+		iwe.cmd = SIOCGIWMODE;
+		if (sta->ap)
+			iwe.u.mode = IW_MODE_MASTER;
+		else
+			iwe.u.mode = IW_MODE_INFRA;
+		iwe.len = IW_EV_UINT_LEN;
+		current_ev = iwe_stream_add_event(current_ev, end_buf, &iwe,
+						  IW_EV_UINT_LEN);
+
+		/* Some quality */
+		memset(&iwe, 0, sizeof(iwe));
+		iwe.cmd = IWEVQUAL;
+		if (sta->last_rx_silence == 0)
+			iwe.u.qual.qual = sta->last_rx_signal < 27 ?
+				0 : (sta->last_rx_signal - 27) * 92 / 127;
+		else
+			iwe.u.qual.qual = sta->last_rx_signal -
+				sta->last_rx_silence - 35;
+		iwe.u.qual.level = HFA384X_LEVEL_TO_dBm(sta->last_rx_signal);
+		iwe.u.qual.noise = HFA384X_LEVEL_TO_dBm(sta->last_rx_silence);
+		iwe.u.qual.updated = sta->last_rx_updated;
+		iwe.len = IW_EV_QUAL_LEN;
+		current_ev = iwe_stream_add_event(current_ev, end_buf, &iwe,
+						  IW_EV_QUAL_LEN);
+		sta->last_rx_updated = 0;
+
+		/* To be continued, we should make good use of IWEVCUSTOM */
+	}
+	spin_unlock_irqrestore(&ap->sta_table_lock, flags);
+
+#if 0
+	{
+		u8 *pos = buffer;
+		left = (current_ev - buffer);
+		printk(KERN_DEBUG "IW SCAN (len=%d):", left);
+		while (left > 0) {
+			printk(" %02x", *pos++);
+			left--;
+		}
+		printk("\n");
+	}
+#endif
+
+	return current_ev - buffer;
+}
+#endif /* WIRELESS_EXT > 13 */
 #endif /* WIRELESS_EXT */
 
 
diff -u -p driver/modules.15/hostap_ioctl.c driver/modules/hostap_ioctl.c
--- driver/modules.15/hostap_ioctl.c	Sat Oct 12 04:37:26 2002
+++ driver/modules/hostap_ioctl.c	Thu Dec  5 18:18:08 2002
@@ -1369,20 +1369,24 @@ static int prism2_ioctl_siwscan(struct n
 				struct iw_request_info *info,
 				struct iw_point *data, char *extra)
 {
-#ifdef PRISM2_NO_STATION_MODES
-	return -EOPNOTSUPP;
-#else /* PRISM2_NO_STATION_MODES */
 	local_info_t *local = (local_info_t *) dev->priv;
+#ifndef PRISM2_NO_STATION_MODES
 	struct hfa384x_scan_request scan_req;
 	int ret = 0;
+#endif /* !PRISM2_NO_STATION_MODES */
 
 	if (local->iw_mode == IW_MODE_MASTER) {
-		printk(KERN_DEBUG "%s: SIOCSIWSCAN is currently only supported"
-		       " in Station modes\n", dev->name);
+		/* In master mode, we just return the results of our local
+		 * tables, so we don't need to start anything...
+		 * Jean II */
 		data->length = 0;
-		return -EOPNOTSUPP;
+		return 0;
 	}
 
+#ifdef PRISM2_NO_STATION_MODES
+	return -EOPNOTSUPP;
+#else /* PRISM2_NO_STATION_MODES */
+
 	memset(&scan_req, 0, sizeof(scan_req));
 	scan_req.channel_list = __constant_cpu_to_le16(0x3fff);
 	scan_req.txrate = __constant_cpu_to_le16(HFA384X_RATES_1MBPS);
@@ -1490,7 +1494,7 @@ static inline int prism2_translate_scan(
 		if (capabilities & (WLAN_CAPABILITY_ESS |
 				    WLAN_CAPABILITY_IBSS)) {
 			if (capabilities & WLAN_CAPABILITY_ESS)
-				iwe.u.mode = IW_MODE_INFRA;
+				iwe.u.mode = IW_MODE_MASTER;
 			else
 				iwe.u.mode = IW_MODE_ADHOC;
 			iwe.len = IW_EV_UINT_LEN;
@@ -1569,10 +1573,9 @@ static inline int prism2_translate_scan(
 }
 #endif /* PRISM2_NO_STATION_MODES */
 
-
-static int prism2_ioctl_giwscan(struct net_device *dev,
-				struct iw_request_info *info,
-				struct iw_point *data, char *extra)
+static inline int prism2_ioctl_giwscan_sta(struct net_device *dev,
+					   struct iw_request_info *info,
+					   struct iw_point *data, char *extra)
 {
 #ifdef PRISM2_NO_STATION_MODES
 	return -EOPNOTSUPP;
@@ -1644,6 +1647,41 @@ static int prism2_ioctl_giwscan(struct n
 		return res;
 	}
 #endif /* PRISM2_NO_STATION_MODES */
+}
+
+static int prism2_ioctl_giwscan(struct net_device *dev,
+				struct iw_request_info *info,
+				struct iw_point *data, char *extra)
+{
+	local_info_t *local = (local_info_t *) dev->priv;
+	int res;
+
+	if (local->iw_mode == IW_MODE_MASTER) {
+		/* In MASTER mode, it doesn't make sense to go around
+		 * scanning the frequencies and make the stations we serve
+		 * wait when what the user is really interested about is the
+		 * list of stations and access points we are talking to.
+		 * So, just extract results from our cache...
+		 * Jean II */
+
+		/* Translate to WE format */
+		res = prism2_ap_translate_scan(dev, extra);
+		if (res >= 0) {
+			printk(KERN_DEBUG "Scan result translation succeeded "
+			       "(length=%d)\n", res);
+			data->length = res;
+			return 0;
+		} else {
+			printk(KERN_DEBUG
+			       "Scan result translation failed (res=%d)\n",
+			       res);
+			data->length = 0;
+			return res;
+		}
+	} else {
+		/* Station mode */
+		return prism2_ioctl_giwscan_sta(dev, info, data, extra);
+	}
 }
 #endif /* WIRELESS_EXT > 13 */
 


From marcb  Fri Dec  6 01:12:33 2002
From: marcb (marcb at softhome.net)
Date: Fri, 06 Dec 2002 02:12:33 -0700
Subject: 802.1x with WinXP
Message-ID: <courier.3DF06A02.00006393@softhome.net>

I'm hoping someone can help me...  I'm  way out of my depth, and I've been 
banging my head against a wall for quite some time now...  but I think I'm 
close. 

I have a Linux box with a DWL-520 and a laptop running WinXP with a DWL-650. 

I'm trying to set the linux box up with hostap as an access point using 
802.1x, authenticating to freeRadius. 

I've nearly got it all working...  in that when the laptop transmits a 
request to authenticate to the linux box...  the request is correctly sent 
by hostapd to the radius server, and I get an "ACCEPT-ACCEPT" from the 
radius server back to hostapd. 

I'm pretty sure the key is then sent to the laptop... as for a brief second 
or two I get a "Authentication Successful" message on WinXP, but as soon as 
the connection is authenticated it drops out and hostapd deauthenticates it. 

I tried doing this whilst continually trying to ping the laptop and for the 
brief few seconds that the laptop is authenticated I get responses... so I 
am able to pass packets through....   I just don't understand why the laptop 
is deauthenticated immediately after authenticating. 

I've tried both hostap-2002-10-12 and the latest CVS, with no noticeable 
difference in behaviour. 

I've attached the output from hostapd below... 

Thanks, 

Marc 

 

 


Opening raw packet socket for ifindex 4
Using interface wlan0ap with hwaddr 00:05:5d:5b:c4:1c and ssid 'test'
Default WEP key - hexdump(len=13): 67 8d 91 69 48 94 85 93 59 fb 48 a4 48
Flushing old station entries
Received 30 bytes management frame
MGMT
mgmt::auth
authentication: STA=00:40:05:ae:bd:2d auth_alg=0 auth_transaction=1 
status_code=0
 New STA
Station 00:40:05:ae:bd:2d authenticated (open system)
Received 40 bytes management frame
MGMT
mgmt::assoc_req
association request: STA=00:40:05:ae:bd:2d capab_info=0x01 listen_interval=1
 new AID 1
Station 00:40:05:ae:bd:2d associated (aid 1)
IEEE 802.1X: Start authentication for new station 00:40:05:ae:bd:2d
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_KEY_TX entering state NO_KEY_TRANSMIT
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state DISCONNECTED
IEEE 802.1X: Unauthorizing station 00:40:05:ae:bd:2d
IEEE 802.1X: Sending canned EAP packet FAILURE to 00:40:05:ae:bd:2d 
(identifier 0)
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state IDLE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state CONNECTING
IEEE 802.1X: Sending EAP Request-Identity to 00:40:05:ae:bd:2d (identifier 
1)
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 37 bytes management frame
DATA
IEEE 802.1X: 5 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=1 length=0
  ignoring 1 extra octets after IEEE 802.1X packet
  EAPOL-Start
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state CONNECTING
IEEE 802.1X: Sending EAP Request-Identity to 00:40:05:ae:bd:2d (identifier 
1)
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 26 bytes management frame
MGMT
MGMT: BSSID=32:33:38:3b:36:33 not our address
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 30 bytes management frame
MGMT
mgmt::auth
authentication: STA=00:40:05:ae:bd:2d auth_alg=0 auth_transaction=1 
status_code=0
Station 00:40:05:ae:bd:2d authenticated (open system)
Received 40 bytes management frame
MGMT
mgmt::assoc_req
association request: STA=00:40:05:ae:bd:2d capab_info=0x11 listen_interval=1
 old AID 1
Station 00:40:05:ae:bd:2d associated (aid 1)
Received 37 bytes management frame
DATA
IEEE 802.1X: 5 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=1 length=0
  ignoring 1 extra octets after IEEE 802.1X packet
  EAPOL-Start
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state CONNECTING
IEEE 802.1X: Sending EAP Request-Identity to 00:40:05:ae:bd:2d (identifier 
1)
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state DISCONNECTED
IEEE 802.1X: Unauthorizing station 00:40:05:ae:bd:2d
IEEE 802.1X: Sending canned EAP packet FAILURE to 00:40:05:ae:bd:2d 
(identifier 1)
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state CONNECTING
IEEE 802.1X: Sending EAP Request-Identity to 00:40:05:ae:bd:2d (identifier 
2)
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 51 bytes management frame
DATA
IEEE 802.1X: 19 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=0 length=15
  EAP: code=2 identifier=1 length=15 (response)
EAP Identifier of the Response-Identity from 00:40:05:ae:bd:2d does not 
match (was 1, expected 2)
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 51 bytes management frame
DATA
IEEE 802.1X: 19 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=0 length=15
  EAP: code=2 identifier=2 length=15 (response)
  EAP Response-Identity
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state AUTHENTICATING
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state RESPONSE
Encapsulating EAP message into a RADIUS packet
Sending RADIUS message to authentication server
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 84 bytes from authentication server
Received RADIUS message
RADIUS packet matching with station 00:40:05:ae:bd:2d
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:40:05:ae:bd:2d (identifier 3)
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 148 bytes management frame
DATA
IEEE 802.1X: 116 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=0 length=112
  EAP: code=2 identifier=3 length=112 (response)
  EAP Response-TLS
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state RESPONSE
Encapsulating EAP message into a RADIUS packet
Sending RADIUS message to authentication server
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 1120 bytes from authentication server
Received RADIUS message
RADIUS packet matching with station 00:40:05:ae:bd:2d
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:40:05:ae:bd:2d (identifier 4)
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 42 bytes management frame
DATA
IEEE 802.1X: 10 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=0 length=6
  EAP: code=2 identifier=4 length=6 (response)
  EAP Response-TLS
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state RESPONSE
Encapsulating EAP message into a RADIUS packet
Sending RADIUS message to authentication server
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 980 bytes from authentication server
Received RADIUS message
RADIUS packet matching with station 00:40:05:ae:bd:2d
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:40:05:ae:bd:2d (identifier 5)
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 1080 bytes management frame
DATA
IEEE 802.1X: 1048 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=0 length=1044
  EAP: code=2 identifier=5 length=1044 (response)
  EAP Response-TLS
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state RESPONSE
Encapsulating EAP message into a RADIUS packet
Sending RADIUS message to authentication server
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 131 bytes from authentication server
Received RADIUS message
RADIUS packet matching with station 00:40:05:ae:bd:2d
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:40:05:ae:bd:2d (identifier 6)
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 42 bytes management frame
DATA
IEEE 802.1X: 10 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=0 length=6
  EAP: code=2 identifier=6 length=6 (response)
  EAP Response-TLS
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state RESPONSE
Encapsulating EAP message into a RADIUS packet
Sending RADIUS message to authentication server
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
Received 160 bytes from authentication server
Received RADIUS message
RADIUS packet matching with station 00:40:05:ae:bd:2d
MS-MPPE-Send-Key (len=32): 2f 39 60 e6 50 da e9 d1 52 7d f8 ec 1f 94 d0 42 
9d 16 2f 4c c0 8c 4f 7f 00 7c 82 d3 aa e0 4e ea
MS-MPPE-Recv-Key (len=32): ee 99 e6 57 2b 76 37 71 d0 f5 3c c7 a4 92 72 35 
9c b0 9d fc e2 2a f4 78 a6 ed 81 15 2c 10 cb 7a
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state SUCCESS
IEEE 802.1X: Sending canned EAP packet SUCCESS to 00:40:05:ae:bd:2d 
(identifier 6)
IEEE 802.1X: 00:40:05:ae:bd:2d REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state AUTHENTICATED
IEEE 802.1X: Authorizing station 00:40:05:ae:bd:2d
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state IDLE
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_KEY_TX entering state KEY_TRANSMIT
IEEE 802.1X: Sending EAPOL-Key(s) to 00:40:05:ae:bd:2d (identifier 7)
IEEE 802.1X: Sending EAPOL-Key to 00:40:05:ae:bd:2d (broadcast index=0)
Received 37 bytes management frame
DATA
IEEE 802.1X: 5 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=1 length=0
  ignoring 1 extra octets after IEEE 802.1X packet
  EAPOL-Start
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state CONNECTING
IEEE 802.1X: Sending EAP Request-Identity to 00:40:05:ae:bd:2d (identifier 
7)
Received 51 bytes management frame
DATA
IEEE 802.1X: 19 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=0 length=15
  EAP: code=2 identifier=7 length=15 (response)
  EAP Response-Identity
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state AUTHENTICATING
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state RESPONSE
Encapsulating EAP message into a RADIUS packet
Sending RADIUS message to authentication server
Received 84 bytes from authentication server
Received RADIUS message
RADIUS packet matching with station 00:40:05:ae:bd:2d
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:40:05:ae:bd:2d (identifier 8)
Received 148 bytes management frame
DATA
IEEE 802.1X: 116 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=0 length=112
  EAP: code=2 identifier=8 length=112 (response)
  EAP Response-TLS
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state RESPONSE
Encapsulating EAP message into a RADIUS packet
Sending RADIUS message to authentication server
Received 1120 bytes from authentication server
Received RADIUS message
RADIUS packet matching with station 00:40:05:ae:bd:2d
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:40:05:ae:bd:2d (identifier 9)
Received 42 bytes management frame
DATA
IEEE 802.1X: 10 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=0 length=6
  EAP: code=2 identifier=9 length=6 (response)
  EAP Response-TLS
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state RESPONSE
Encapsulating EAP message into a RADIUS packet
Sending RADIUS message to authentication server
Received 980 bytes from authentication server
Received RADIUS message
RADIUS packet matching with station 00:40:05:ae:bd:2d
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:40:05:ae:bd:2d (identifier 10)
Received 1080 bytes management frame
DATA
IEEE 802.1X: 1048 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=0 length=1044
  EAP: code=2 identifier=10 length=1044 (response)
  EAP Response-TLS
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state RESPONSE
Encapsulating EAP message into a RADIUS packet
Sending RADIUS message to authentication server
Received 131 bytes from authentication server
Received RADIUS message
RADIUS packet matching with station 00:40:05:ae:bd:2d
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:40:05:ae:bd:2d (identifier 11)
Received 42 bytes management frame
DATA
IEEE 802.1X: 10 bytes from 00:40:05:ae:bd:2d
  IEEE 802.1X: version=1 type=0 length=6
  EAP: code=2 identifier=11 length=6 (response)
  EAP Response-TLS
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state RESPONSE
Encapsulating EAP message into a RADIUS packet
Sending RADIUS message to authentication server
Received 160 bytes from authentication server
Received RADIUS message
RADIUS packet matching with station 00:40:05:ae:bd:2d
MS-MPPE-Send-Key (len=32): d8 fd e6 87 ce a6 7a a3 33 d2 c5 aa 61 7e ac 72 
6c 4a cc 55 08 cf a6 87 c7 f2 3a 15 94 ee 09 ac
MS-MPPE-Recv-Key (len=32): b2 8c 32 62 41 bb 50 78 17 7b cc f5 17 8e 91 c1 
b3 66 33 18 3c 01 dc e1 95 10 e4 72 89 d5 81 b0
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state SUCCESS
IEEE 802.1X: Sending canned EAP packet SUCCESS to 00:40:05:ae:bd:2d 
(identifier 11)
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_KEY_TX entering state KEY_TRANSMIT
IEEE 802.1X: Sending EAPOL-Key(s) to 00:40:05:ae:bd:2d (identifier 11)
IEEE 802.1X: Sending EAPOL-Key to 00:40:05:ae:bd:2d (broadcast index=0)
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state AUTHENTICATED
IEEE 802.1X: Authorizing station 00:40:05:ae:bd:2d
IEEE 802.1X: 00:40:05:ae:bd:2d BE_AUTH entering state IDLE
Received 26 bytes management frame
MGMT
MGMT: BSSID=32:33:38:3b:36:33 not our address
Received 26 bytes management frame
MGMT
mgmt::deauth
deauthentication: STA=00:40:05:ae:bd:2d reason_code=3
Station 00:40:05:ae:bd:2d deauthenticated
IEEE 802.1X: station 00:40:05:ae:bd:2d port disabled
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state INITIALIZE
IEEE 802.1X: 00:40:05:ae:bd:2d AUTH_PAE entering state INITIALIZE
Signal 2 received - terminating
Flushing old station entries
Deauthenticate all stations 



From ian.cass  Fri Dec  6 02:42:04 2002
From: ian.cass (Ian Cass)
Date: Fri, 6 Dec 2002 10:42:04 -0000
Subject: Linux 2.2
References: <04d801c29c74$840143d0$4c28a8c0@cblan.mblox.com>
Message-ID: <060401c29d14$1e293900$4c28a8c0@cblan.mblox.com>

> Does HostAP work on older 2.2 series kernels and if so, what about
Wireless
> Extensions versions?

Bad form to reply to my own mails, but for the archives, I've compiled up
2.2.23 with pcmcia-cs-3.2.3 and it seems to work OK. Some of the iw-tools
don't work anymore, but there's enough functionality to get by (I think).

I'm not sure at this point if there's any other gotchas.

--
Ian Cass




From Jacques.Caron  Fri Dec  6 03:00:21 2002
From: Jacques.Caron (Jacques Caron)
Date: Fri, 06 Dec 2002 12:00:21 +0100
Subject: WEP help
In-Reply-To: <000001c29ca4$bcb344f0$1300a8c0@DOUG1>
References: <200212051543.01305.jasonb@edseek.com>
Message-ID: <5.2.0.9.0.20021206115658.026f9608@pop.mail.yahoo.com>

At 22:24 05/12/2002, Doug Yeager wrote:
> > Obviously, you still need a way to allow users with 802.1x or a
> > subscription to connect (without WEP) to a limited set of pages to
>know
> > what they need, subscribe, download the necessary software, etc.
>
>any thoughts on how to do this?
>
>I guess my question is... if you set up hostapd to do encryption, is it
>optional to the client?  Can they use the network at all w/o wep so they
>can hit a website and signup?

The problem is really in the beacon frames and how the clients interpret 
it. For instance, XP will not associate with an access point that doesn't 
have the privacy bit turned on in beacons if it is configured for 
encryption (even with 802.1x). On the other hand, most clients won't 
associate to an access point advertising WEP encryption if they don't have 
it on.

So I guess one would need a way to broadcast two different beacons 
(probably with different SSIDs), one with and the other without the privacy 
bit set to one.

>Anyone done this?

Not yet :-( Let me know if you get to anything interesting.

Jacques.


-- Jacques Caron, IP Sector Technologies
    Join the discussion on public WLAN open global roaming:
    http://lists.ipsector.com/listinfo/openroaming





From location  Fri Dec  6 03:01:36 2002
From: location (Location Proj)
Date: Fri, 6 Dec 2002 11:01:36 +0000 (GMT)
Subject: [PATCH] : Scan in master mode
In-Reply-To: <20021206024056.GA2255@bougret.hpl.hp.com>
Message-ID: <Pine.BSO.4.44.0212061100310.22055-100000@snet.wit.ie>

> 	As part of WE-16, I'm improving the iwspy support. HostAP is
> currently problematic as I want to "reclaim" the SIOCGIWSPY call, and
> HostAP currently uses it.
>
> 	So, I've decided 2 things :
> 	1) I've un-deprecated SIOCGIWAPLIST and broaden its
> definition. You can now return any list of address you want, not only
> APs, and will remain supported.

Does this mean that iwapy will retun stats for any station in range...?

--

Andrew




From Jacques.Caron  Fri Dec  6 02:56:28 2002
From: Jacques.Caron (Jacques Caron)
Date: Fri, 06 Dec 2002 11:56:28 +0100
Subject: WEP help
In-Reply-To: <200212051543.01305.jasonb@edseek.com>
References: <5.2.0.9.0.20021205172636.017955c0@pop.mail.yahoo.com>
 <5.2.0.9.0.20021205172636.017955c0@pop.mail.yahoo.com>
Message-ID: <5.2.0.9.0.20021206115606.021eee90@pop.mail.yahoo.com>

At 21:43 05/12/2002, Jason Boxman wrote:
>On Thursday 05 December 2002 11:37 am, Jacques Caron wrote:
> > Hi,
> >
><snip>
> > I would personally recommend using WEP with 802.1x, since:
> > - 802.1x is built into Windows XP
> > - there is now a free 802.1x add-on from MS for W2K
>
>Where might this be?  This is the only missing thing preventing me from
>writing an article on setting up 802.1x using HostAP and Windows clients.

http://support.microsoft.com/default.aspx?scid=kb;en-us;313664

Jacques.


-- Jacques Caron, IP Sector Technologies
    Join the discussion on public WLAN open global roaming:
    http://lists.ipsector.com/listinfo/openroaming





From jt  Fri Dec  6 09:50:27 2002
From: jt (Jean Tourrilhes)
Date: Fri, 6 Dec 2002 09:50:27 -0800
Subject: Scan in master mode
Message-ID: <20021206175027.GA6987@bougret.hpl.hp.com>

Location Proj wrote :
>
> Does this mean that iwapy will retun stats for any station in range...?

	I can't make impossible things happen. But I guess that iwspy
would still work when you put the card in monitor mode.
	Regards,

	Jean



From owens  Fri Dec  6 09:51:35 2002
From: owens (Owen Shoemaker)
Date: Fri, 6 Dec 2002 09:51:35 -0800
Subject: LDAP encrypted passwords
Message-ID: <5CBE5218-0943-11D7-8FC8-000393D5F2BA@speakeasy.net>

Does anyone know a way to make hostapd work with encrypted passwords in 
LDAP?  After a little digging through the RFC of EAP it looks like the 
password needs to be in plaintext.  Does anyone know of a workaround?

--
Owen Shoemaker




From bapper  Fri Dec  6 09:57:21 2002
From: bapper (Brian Pomerantz)
Date: Fri, 6 Dec 2002 09:57:21 -0800
Subject: 802.1x with WinXP
In-Reply-To: <courier.3DF06A02.00006393@softhome.net>
References: <courier.3DF06A02.00006393@softhome.net>
Message-ID: <20021206175721.GC10061@skull.piratehaven.org>

On Fri, Dec 06, 2002 at 02:12:33AM -0700, marcb at softhome.net wrote:
> 
> I'm pretty sure the key is then sent to the laptop... as for a brief second 
> or two I get a "Authentication Successful" message on WinXP, but as soon as 
> the connection is authenticated it drops out and hostapd deauthenticates 
> it. 

This sounds like the same problem I had from a client side perspective
(though the same problem is probably there for AP as well).  When the
WEP key is set on the card, the card is reset.  Take a look at this
email and patch to see if the problem goes away:

	http://hostap.epitest.fi/hostap/2002-09/2056.html

Certainly in the case where you are using the encryption module
instead of the card's firmware, you DON'T want the card to be reset.
You may have multiple supplicants with different WEP keys for each
one.  They would all be deauthenticated every time someone new comes
along.


BAPper



From jkmaline  Fri Dec  6 19:20:45 2002
From: jkmaline (Jouni Malinen)
Date: Fri, 6 Dec 2002 19:20:45 -0800
Subject: 802.1x with WinXP
In-Reply-To: <courier.3DF06A02.00006393@softhome.net>
References: <courier.3DF06A02.00006393@softhome.net>
Message-ID: <20021207032045.GA1263@jm.kir.nu>

On Fri, Dec 06, 2002 at 02:12:33AM -0700, marcb at softhome.net wrote:

> I'm pretty sure the key is then sent to the laptop... as for a brief second 
> or two I get a "Authentication Successful" message on WinXP, but as soon as 
> the connection is authenticated it drops out and hostapd deauthenticates 
> it. 
> I tried doing this whilst continually trying to ping the laptop and for the 
> brief few seconds that the laptop is authenticated I get responses... so I 
> am able to pass packets through....   I just don't understand why the 
> laptop is deauthenticated immediately after authenticating. 

I have the same problem with WinXP SP1. WEP key exchanges clearly works
since I can also ping the station for couple of seconds, but after that,
WinXP decides to deauthenticate for some unknown reason. In other words,
it is not hostapd, but Supplicant in WinXP doing the deauthentication.

> IEEE 802.1X: Authorizing station 00:40:05:ae:bd:2d

Auth. server and hostapd were happy with the station, and it was
authorized.

> IEEE 802.1X: Sending EAPOL-Key(s) to 00:40:05:ae:bd:2d (identifier 7)
> IEEE 802.1X: Sending EAPOL-Key to 00:40:05:ae:bd:2d (broadcast index=0)

Here goes the WEP keys and after this point, I was able to ping the
station.

>  EAPOL-Start

Station seems to start another .1x round here. However, I don't know
why..

> IEEE 802.1X: Authorizing station 00:40:05:ae:bd:2d

.. and it also successful (as far as hostapd and freeradius are
concerned), but..

> deauthentication: STA=00:40:05:ae:bd:2d reason_code=3
> Station 00:40:05:ae:bd:2d deauthenticated
> IEEE 802.1X: station 00:40:05:ae:bd:2d port disabled

For some reason, Supplicant was not happy with something and
deauthenticated itself.


I have finally managed to get my .1x testing setup working again, so I
will be debugging this in the near future. I think I will go through the
changes made to IEEE 802.1x in the latest draft version of IEEE 802.1aa.
There seemed to be couple of changes to the state machines that might
have something to do with the problems. I don't think I have changed
anything in my code related to this.. I was able to get the same setup
working previously with WinXP (without SP1) and using exactly same
certificates, so it would seem that something has changed in the
Supplicant.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Dec  6 19:34:39 2002
From: jkmaline (Jouni Malinen)
Date: Fri, 6 Dec 2002 19:34:39 -0800
Subject: hostapd startup
In-Reply-To: <5039C590-0896-11D7-A2EE-000393D5F2BA@speakeasy.net>
References: <5039C590-0896-11D7-A2EE-000393D5F2BA@speakeasy.net>
Message-ID: <20021207033439.GB1263@jm.kir.nu>

On Thu, Dec 05, 2002 at 01:12:51PM -0800, Owen Shoemaker wrote:

> problem is that even after authenticating and verifying that I am 
> authenticated on the AP I can't get any IP connectivity.  Does anyone 
> know of any good documentation other than the PRISM2 readme?  Maybe 
> tips on network config and startup scripts?

Unfortunately, there does not seem to be any good documentation for
hostapd at the moment. I have written only minimal amount of
documentation that should be enough to get people started with it. I
would still consider 802.1x code in hostapd to be in experimental and
evolving state, so documenting it has not been my first priority. In
addition, getting FreeRADIUS compiled and running with EAP/TLS is not
exactly trivial thing yet (requirements for different openssl versions,
etc.). Anyway, I hope that there will be more thorough documentation
available when both hostapd and FreeRADIUS support mature a bit.

> Do I need to add IP info 
> to the wlan0ap device?  Shouldn't after auth just forward the traffic 
> to the wlan0 device?  I haven't really dug too deep yet but just wanted 
> to know if my settings were correct.

No, wlan0ap does not need an IP address. If that 'auth' is refering to
authorization (and not authentication), yes, you should be able get
data traffic going after that. As far as I can tell, your configuration
looked fine.

> Station 00:02:dd:32:48:e0 authenticated (open system)
> Station 00:02:dd:32:48:e0 associated (aid 1)

802.11 authentication and associated completed

> Minimal Authentication Server: station 00:02:dd:32:48:e0 EAP 
> Response-Identity: (len=10) 'owens'
> IEEE 802.1X: Authorizing station 00:02:dd:32:48:e0

802.1x completed. After this, you should be able to send data frames to
and from the station. Did WinXP report that the authentication was
successful (after you entered username and password, or whatever it
asked)? Did you use WinXP with or without service pack 1? Which wlan
card was used in the client?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Dec  6 19:38:40 2002
From: jkmaline (Jouni Malinen)
Date: Fri, 6 Dec 2002 19:38:40 -0800
Subject: Linux 2.2
In-Reply-To: <04d801c29c74$840143d0$4c28a8c0@cblan.mblox.com>
References: <04d801c29c74$840143d0$4c28a8c0@cblan.mblox.com>
Message-ID: <20021207033840.GC1263@jm.kir.nu>

On Thu, Dec 05, 2002 at 03:39:35PM -0000, Ian Cass wrote:

> Does HostAP work on older 2.2 series kernels and if so, what about Wireless
> Extensions versions?

I do not actively test 2.2 kernels with the driver, so there may well be
some problems. I would like to have the code working with 2.2 kernels,
but since I do not test it, I generally need to be told about the
specific problems. I know that current CVS version does not work with
2.2 kernels due to a missing skb function, but previous release might be
work fine. I'll try to add some compatibility code to workaround this
latest issue at some point.

-- 
Jouni Malinen                                            PGP id EFC895FA



From bapper  Fri Dec  6 20:31:09 2002
From: bapper (Brian Pomerantz)
Date: Fri, 6 Dec 2002 20:31:09 -0800
Subject: 802.1x with WinXP
In-Reply-To: <20021207032045.GA1263@jm.kir.nu>
References: <courier.3DF06A02.00006393@softhome.net> <20021207032045.GA1263@jm.kir.nu>
Message-ID: <20021207043109.GA29766@skull.piratehaven.org>

On Fri, Dec 06, 2002 at 07:20:45PM -0800, Jouni Malinen wrote:
> 
> I have the same problem with WinXP SP1. WEP key exchanges clearly works
> since I can also ping the station for couple of seconds, but after that,
> WinXP decides to deauthenticate for some unknown reason. In other words,
> it is not hostapd, but Supplicant in WinXP doing the deauthentication.
> 

If I have time next week I'll set up hostap as an AP (I've been using
the driver only for a client) and capture the packets with Airopeek to
see exactly who is doing the deauthentication and the reason given for
it.  We had a bit of a problem getting our AP working with XP and
802.1x but seem to have worked things out with/without SP1.


BAPper



From jkmaline  Fri Dec  6 20:43:35 2002
From: jkmaline (Jouni Malinen)
Date: Fri, 6 Dec 2002 20:43:35 -0800
Subject: 802.1x with WinXP
In-Reply-To: <20021207043109.GA29766@skull.piratehaven.org>
References: <courier.3DF06A02.00006393@softhome.net> <20021207032045.GA1263@jm.kir.nu> <20021207043109.GA29766@skull.piratehaven.org>
Message-ID: <20021207044335.GA2048@jm.kir.nu>

On Fri, Dec 06, 2002 at 08:31:09PM -0800, Brian Pomerantz wrote:

> If I have time next week I'll set up hostap as an AP (I've been using
> the driver only for a client) and capture the packets with Airopeek to
> see exactly who is doing the deauthentication and the reason given for
> it.

You should not need to setup a sniffer for this.. hostapd log is clearly
showing an incoming deauthentication frame (with reason "STA is
leaving") from the station.. Anyway, I would welcome any new information
on this subject.

If only Supplicant in WinXP would give a bit more debugging information
to find out what is causing the problems.. If anyone happens to know a
way of configuring something like this or knows of a debug version of
that Supplicant, please do let me know. This would certainly make
debugging lot easier.

-- 
Jouni Malinen                                            PGP id EFC895FA



From doug  Sat Dec  7 07:35:46 2002
From: doug (Doug Yeager)
Date: Sat, 07 Dec 2002 10:35:46 -0500
Subject: No more space in this STA's PS mo
Message-ID: <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com>

i have a few AP's in downtown knoxville serving coffee houses. i review the 
dmesg logs frequently to see what is going on. every now and then i get 
this log messages. usually follows a resetting of the AP card. my ap is 
wmp11 pci card. it would be much appreciated if someone could interpret 
this message for me. what is PS mode buffer? can i prevent this w/ some 
setting? the results of this are not horrible as only the client that 
causes this usually cannot get back on....everyone else is usually o.k. 
until i reboot the AP. one time i was able to run down one of the clients 
on the wlan and beat him up and take his laptop. i found a dwl-650 card 
inside if that helps at all.
i am using the latest hostap driver just before the BAP0 and BAP1 stuff was 
changed.  do you think this may have anything to do w/ this/  my firmware 
is sta1.5.6 and prim:1.1.0

dmesg log where the trouble starts:
---------------------
wlan0: 00:04:75:c4:36:b1 auth_cb - STA authenticated
wlan0: 00:04:75:c4:36:b1 reassoc (len=24 prev_ap=00:06:25:09:0b:31) => 0(0) 
(OK,
old AID)
wlan0: 00:04:75:c4:36:b1 assoc_cb - STA associated
wlan0: STA 00:04:75:c4:36:b1 TX rate lowered to 55
wlan0: STA 00:04:75:c4:36:b1 TX rate raised to 110
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
wlan0: STA 00:04:75:c4:36:b1 TX rate lowered to 55
wlan0: sending disassociation info to STA 00:04:75:c4:36:b1(last=22325356, 
jiffi
es=22355456)
wlan0: STA 00:04:75:c4:36:b1 TX rate lowered to 20
wlan0: sending deauthentication info to STA 
00:04:75:c4:36:b1(last=22325356, jif
fies=22355556)
wlan0: Could not find STA for this TX error
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
wlan0: STA 00:02:2d:66:cb:0c TX rate raised to 55
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer




From mark-hostap  Sat Dec  7 09:10:06 2002
From: mark-hostap (Mark Glines)
Date: Sat, 7 Dec 2002 09:10:06 -0800
Subject: No more space in this STA's PS mo
In-Reply-To: <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com>
References: <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com>
Message-ID: <20021207171006.GA10127@glines.org>

On Sat, Dec 07, 2002 at 10:35:46AM -0500, Doug Yeager wrote:
> No more space in this STA's PS mode buffer
> No more space in this STA's PS mode buffer


Hi!  I've seen this problem before, with a win98 client laptop using a linksys
WPC11 card.  The "PS mode buffer" is a temporary storage space to store packets
while the AP is waiting for a client to wake back up again... this is only used
when the client card is in power-saving (also known as "off") mode.  In my
case, having the client in power-saving mode only caused more lag... it didn't
break anything.  For your client, can you try turning off power-saving mode?

Mark



From jkmaline  Sat Dec  7 09:45:40 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 7 Dec 2002 09:45:40 -0800
Subject: No more space in this STA's PS mo
In-Reply-To: <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com>
References: <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com>
Message-ID: <20021207174540.GA2896@jm.kir.nu>

On Sat, Dec 07, 2002 at 10:35:46AM -0500, Doug Yeager wrote:

> i have a few AP's in downtown knoxville serving coffee houses. i review the 
> dmesg logs frequently to see what is going on. every now and then i get 
> this log messages. usually follows a resetting of the AP card.

That indicates that the number of buffered frames for power saving
station exceeded limit of 32 frames. Usually, this would mean that the
station has started to use power saving mode, but is not sending PS poll
frames to request the buffered frames.

If this happens just after resetting the AP card, it might be possible
that the buffer was already full before reset and after reset a TIM bit
in beacon is not set. This bit is used by the station as an indication
of buffered frames. Current driver code does not setup TIM bits after
reset and this might end up in state where no frame in AP->STA direction
is able to trigger PS polling. I will fix the reset code to setup TIM
configuration, so that this kind of situation could be avoided. I'm not
sure whether this will fix your case, but it might.

-- 
Jouni Malinen                                            PGP id EFC895FA



From doug  Sat Dec  7 10:32:15 2002
From: doug (Doug Yeager)
Date: Sat, 07 Dec 2002 13:32:15 -0500
Subject: No more space in this STA's PS mo
In-Reply-To: <20021207174540.GA2896@jm.kir.nu>
References: <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com>
 <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com>
Message-ID: <4.3.2.7.0.20021207132842.00a901c0@yeagerautomation.com>

after reading my email.  i stated it incorrectly.    after i see these 
messages,  the card resets itself.  i'll dig deeper to see if i find any 
more messages that tell  more of the story.
thanks for the reply though, it was very informative.
is there a reason my AP would be in power saving mode?  it isn't a laptop 
and is plugged in, so i don't really care about this.  if i could set it 
out of power saving mode, that would be fine w/ me.

thx,
doug

At 09:45 AM 12/07/2002 -0800, you wrote:
>On Sat, Dec 07, 2002 at 10:35:46AM -0500, Doug Yeager wrote:
>
> > i have a few AP's in downtown knoxville serving coffee houses. i review 
> the
> > dmesg logs frequently to see what is going on. every now and then i get
> > this log messages. usually follows a resetting of the AP card.
>
>That indicates that the number of buffered frames for power saving
>station exceeded limit of 32 frames. Usually, this would mean that the
>station has started to use power saving mode, but is not sending PS poll
>frames to request the buffered frames.
>
>If this happens just after resetting the AP card, it might be possible
>that the buffer was already full before reset and after reset a TIM bit
>in beacon is not set. This bit is used by the station as an indication
>of buffered frames. Current driver code does not setup TIM bits after
>reset and this might end up in state where no frame in AP->STA direction
>is able to trigger PS polling. I will fix the reset code to setup TIM
>configuration, so that this kind of situation could be avoided. I'm not
>sure whether this will fix your case, but it might.
>
>--
>Jouni Malinen                                            PGP id EFC895FA
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap




From msmith  Sat Dec  7 13:56:22 2002
From: msmith (Michael Smith)
Date: Sat, 7 Dec 2002 16:56:22 -0500 (EST)
Subject: No more space in this STA's PS mo
In-Reply-To: <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com>
Message-ID: <Pine.LNX.4.44.0212071654060.6693-100000@juice.ott.ctd.com>

I've seen an AP with HostAP 2002-10-12 think a client has gone
into PS mode when it actually hasn't - maybe it got a garbled packet? This
was on a distance link with a lot of traffic. I think the fix was to
reset the card on the station (also HostAP 2002-10-12) forcing it to
reassociate.

Mike


On Sat, 7 Dec 2002, Doug Yeager wrote:

> No more space in this STA's PS mode buffer




From jkmaline  Sat Dec  7 14:37:21 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 7 Dec 2002 14:37:21 -0800
Subject: No more space in this STA's PS mo
In-Reply-To: <4.3.2.7.0.20021207132842.00a901c0@yeagerautomation.com>
References: <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com> <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com> <4.3.2.7.0.20021207132842.00a901c0@yeagerautomation.com>
Message-ID: <20021207223721.GA1322@jm.kir.nu>

On Sat, Dec 07, 2002 at 01:32:15PM -0500, Doug Yeager wrote:

> is there a reason my AP would be in power saving mode?

No, AP is not and even cannot be in power saving mode on IEEE 802.11
nerworks. It is the station that is using power saving.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Dec  7 16:26:47 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 7 Dec 2002 16:26:47 -0800
Subject: WEP help
In-Reply-To: <5.2.0.9.0.20021205190323.01769f08@wheresmymailserver.com>
References: <5.2.0.9.0.20021205190323.01769f08@wheresmymailserver.com>
Message-ID: <20021208002647.GA1318@jm.kir.nu>

On Thu, Dec 05, 2002 at 07:03:46PM +0100, Jacques Caron wrote:

> I know the driver supports per-client keys, but I don't know offhand how 
> you would be able to change those keys from userland, probably some form of 
> ioctl (I'm not sure there is a command or iwconfig param that does this), 
> you might want to look into the hostapd source code, since that program is 
> actually doing the 802.1x bit and the WEP key setting. Probably not very 
> difficult to write a very short program that would take a MAC address and 
> WEP key and give that information to the driver, if there isn't one already.

Yes, it uses an ioctl and yes, there is a program for setting this up
manually, so no need to write a new one. I have even written
documentation for hostap_crypt_conf ;-).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Dec  7 16:46:16 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 7 Dec 2002 16:46:16 -0800
Subject: WEP help
In-Reply-To: <000001c29c89$b1c9cc00$1300a8c0@DOUG1>
References: <5.2.0.9.0.20021205182125.01795700@wheresmymailserver.com> <000001c29c89$b1c9cc00$1300a8c0@DOUG1>
Message-ID: <20021208004616.GB1318@jm.kir.nu>

On Thu, Dec 05, 2002 at 01:11:02PM -0500, Doug Yeager wrote:

> My linksys card always wants me to put in my own pass phrase or keys.  I
> don't want it to ask.  I just want the server to assign me one and me to
> accept it like https.

Then you would need to use IEEE 802.1x..

There are some problems with running an AP that would support both WEP
or .1x and guest users without any encryption. One issue that was
already mentioned, is the Privacy bit in beacons. WinXP requires this
bit for .1x and non-WEP stations might require the bit to be off before
they even try to associate.

If .1x is not a suitable method for your environment, you might be able
to something else in a bit more adhoc style. To get rid of the beacon
Privacy bit problem, you would probably need to configure the AP and all
stations to default to some publicly known key. Stations using this key
could then get the "guest privileges" (e.g., limited Internet access or
limited QoS priority/ bandwidth, etc.). Privileged users would first use
the common WEP key to authenticate (using, e.g., .1x, nocatauth, or
whatever) and as part of this process, a dynamic key would be assigned
to them and firewall/QoS configuration would be changed.

Currently, you would need to update firewall/QoS configuration for each
station, but I have considered adding some kind of packet tagging to the
driver code for 802.1x use. This would make it easier to configure
firewall for .1x-authorized and non-authorized (i.e., guest) users.
Current version of hostapd does not allow such behavior, i.e., all
non-authorized data frames will be dropped unconditionally.

I know that this would still require some configuration changes to the
clients using guest mode (i.e., setting up that WEP key). The AP could
be configured to allow non-encrypted frames, but the beacons would still
be sent with Privacy bit. I haven't tested this, but it might be
possible to get at least some non-1x stations associating with the AP
even without changing WEP configuration of the station.

-- 
Jouni Malinen                                            PGP id EFC895FA



From marcb  Sat Dec  7 17:44:38 2002
From: marcb (marcb at softhome.net)
Date: Sat, 07 Dec 2002 18:44:38 -0700
Subject: 802.1x with WinXP
In-Reply-To: <20021206175721.GC10061@skull.piratehaven.org> 
References: <courier.3DF06A02.00006393@softhome.net>
            <20021206175721.GC10061@skull.piratehaven.org>
Message-ID: <courier.3DF2A406.00005E6F@softhome.net>

Thanks for the help... 

but I tried the patch and unfortunately it doesn't seem to make any 
difference to the problem. 

Following Jouni's suggestion that the problem might be with WinXP SP1...  I 
had a look at the Microsoft knowledgebase.  They have an article there 
describing pretty much the behaviour I'm seeing (from a WinXp 
persepective)..  and they say that WinXP SP1 cannot receive or process 
multiple EAPOL keys. 

 From my crude understanding of the what is happening... the WinXp machine is 
authenticating once...  and then authenticating again...  before it drops 
out.  Does that mean it is receiving two different keys, which Microsoft 
seem to think WinXp cannot handle?



From jkmaline  Sat Dec  7 18:09:39 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 7 Dec 2002 18:09:39 -0800
Subject: 802.1x with WinXP
In-Reply-To: <courier.3DF2A406.00005E6F@softhome.net>
References: <courier.3DF06A02.00006393@softhome.net> <20021206175721.GC10061@skull.piratehaven.org> <courier.3DF2A406.00005E6F@softhome.net>
Message-ID: <20021208020939.GA2314@jm.kir.nu>

On Sat, Dec 07, 2002 at 06:44:38PM -0700, marcb at softhome.net wrote:

> Following Jouni's suggestion that the problem might be with WinXP SP1...  I 
> had a look at the Microsoft knowledgebase.  They have an article there 
> describing pretty much the behaviour I'm seeing (from a WinXp 
> persepective)..  and they say that WinXP SP1 cannot receive or process 
> multiple EAPOL keys. 

Could you please send me the Article ID for that KB entry?

> From my crude understanding of the what is happening... the WinXp machine 
> is authenticating once...  and then authenticating again...  before it 
> drops out.  Does that mean it is receiving two different keys, which 
> Microsoft seem to think WinXp cannot handle?

At least your log showed only one EAPOL-Key frame (broadcast) being
sent. However, it was sent again after the client decided to
authenticate again.

-- 
Jouni Malinen                                            PGP id EFC895FA



From doug  Sat Dec  7 18:25:59 2002
From: doug (Doug Yeager)
Date: Sat, 07 Dec 2002 21:25:59 -0500
Subject: No more space in this STA's PS mo
In-Reply-To: <20021207223721.GA1322@jm.kir.nu>
References: <4.3.2.7.0.20021207132842.00a901c0@yeagerautomation.com>
 <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com>
 <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com>
 <4.3.2.7.0.20021207132842.00a901c0@yeagerautomation.com>
Message-ID: <4.3.2.7.0.20021207212215.03748d00@yeagerautomation.com>

the dmesg log that i listed was from the AP, i assumed the word "this 
sta's" meant the AP but i could have interpreted incorrectly.  is that what 
you are saying?  those messages seem to build, even with no clients in the 
area.  i do know there is another AP within about 100 yards from this 
one.  i don't know if that is part of the problem or 
not.  regardless,  i'll keep snooping the logs until the card resets, there 
are other funny messages before that happens.  i'll post those.

-doug

At 02:37 PM 12/07/2002 -0800, you wrote:
>On Sat, Dec 07, 2002 at 01:32:15PM -0500, Doug Yeager wrote:
>
> > is there a reason my AP would be in power saving mode?
>
>No, AP is not and even cannot be in power saving mode on IEEE 802.11
>nerworks. It is the station that is using power saving.
>
>--
>Jouni Malinen                                            PGP id EFC895FA
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap




From jkmaline  Sat Dec  7 18:52:50 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 7 Dec 2002 18:52:50 -0800
Subject: No more space in this STA's PS mo
In-Reply-To: <4.3.2.7.0.20021207212215.03748d00@yeagerautomation.com>
References: <4.3.2.7.0.20021207132842.00a901c0@yeagerautomation.com> <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com> <4.3.2.7.0.20021207103407.0374bcd0@yeagerautomation.com> <4.3.2.7.0.20021207132842.00a901c0@yeagerautomation.com> <4.3.2.7.0.20021207212215.03748d00@yeagerautomation.com>
Message-ID: <20021208025250.GA2490@jm.kir.nu>

On Sat, Dec 07, 2002 at 09:25:59PM -0500, Doug Yeager wrote:

> the dmesg log that i listed was from the AP, i assumed the word "this 
> sta's" meant the AP but i could have interpreted incorrectly.  is that what 
> you are saying?  those messages seem to build, even with no clients in the 
> area.

Yes, that message is misleading.. It does indeed mean a client station,
not the "AP station". I added client hwaddr to it so that it will be
easier to understand and debug. In addition, I added TIM bit setting
here to make sure that it is set even if AP's wlan card get reseted. You
can do the following changes manually or just use the latest CVS version
to get the new version.

Please also note, that these messages might be about a station that was
using power saving and that left the AP during some network activity. AP
would be adding all incoming frames to PS buffer in this kind of case
and since the station is not anymore present there will be no PS poll
frames to empty the queue.


diff -u -p -r1.33 hostap_ap.c
--- driver/modules/hostap_ap.c  26 Nov 2002 04:59:16 -0000      1.33
+++ driver/modules/hostap_ap.c  8 Dec 2002 02:47:35 -0000
@@ -2620,8 +2620,12 @@ ap_tx_ret hostap_handle_sta_tx(local_inf
        }
 
        if (skb_queue_len(&sta->tx_buf) >= STA_MAX_TX_BUFFER) {
-               PDEBUG(DEBUG_PS, "No more space in this STA's PS mode "
-                      "buffer\n");
+               PDEBUG(DEBUG_PS, "%s: No more space in STA (" MACSTR ")'s PS "
+                      "mode buffer\n", local->dev->name, MAC2STR(sta->addr));
+               /* Make sure that TIM is set for the station (it might not be
+                * after AP wlan hw reset). */
+               hostap_set_tim(local, sta->aid, 1);
+               sta->flags |= WLAN_STA_TIM;
                ret = AP_TX_DROP;
                goto out;
        }


-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Dec  7 18:58:07 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 7 Dec 2002 18:58:07 -0800
Subject: ACK timeouts: done in firmware or software?
In-Reply-To: <3DEC6B7C.3010103@palaver.net>
References: <3DEC6B7C.3010103@palaver.net>
Message-ID: <20021208025807.GB2490@jm.kir.nu>

On Tue, Dec 03, 2002 at 03:29:48AM -0500, Brian Capouch wrote:

> I'm not aware enough to know whether I should assume that my 
> drivers--HostAP and Agere's AP-1000 bins--currently only wait for a SIFS 
> period before giving up on an ACK.   If that's what it is could I change 
> it to length DIFS instead and thereby gain the benefit they posit?

ACK handling is quite lowlevel task in firmware/hardware. I'm not aware
of any way to configure this from the driver code for Prism2-based
cards. It would be possible to set the maximum retry count to zero so
that the firmware does not do any retransmissions and then retransmit
the frames from the driver code based on some criteria. However, it
might not be possible to get any signal about the possible ACK received
after the original timeout.

-- 
Jouni Malinen                                            PGP id EFC895FA



From marcb  Sat Dec  7 19:28:11 2002
From: marcb (Marc Brady)
Date: Sun, 8 Dec 2002 14:28:11 +1100
Subject: 802.1x with WinXP
In-Reply-To: <20021206175721.GC10061@skull.piratehaven.org>
Message-ID: <000001c29e69$d6e6a670$b6d832d2@kaoticinnovations.com.au>



>Could you please send me the Article ID for that KB entry?

>-- 
>Jouni Malinen                                            PGP id
EFC895FA


Its not a very informative KB article... but for your reference it is
KB328658.









From jkmaline  Sat Dec  7 20:20:12 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 7 Dec 2002 20:20:12 -0800
Subject: [PATCH] : Scan in master mode
In-Reply-To: <20021206024056.GA2255@bougret.hpl.hp.com>
References: <20021206024056.GA2255@bougret.hpl.hp.com>
Message-ID: <20021208042012.GA3742@jm.kir.nu>

On Thu, Dec 05, 2002 at 06:40:56PM -0800, Jean Tourrilhes wrote:

> 	As part of WE-16, I'm improving the iwspy support. HostAP is
> currently problematic as I want to "reclaim" the SIOCGIWSPY call, and
> HostAP currently uses it.

Hmm.. If I understood your design correctly, iwspy ioctl's were from
driver code to main kernel. That is fine for me. It will make the driver
code a bit more complex with all those conditional #if blocks for
different wireless extension versions since I'm going to keep supporting
the older versions, but I think I can manage with it.

> 	So, I've decided 2 things :
> 	1) I've un-deprecated SIOCGIWAPLIST and broaden its
> definition. You can now return any list of address you want, not only
> APs, and will remain supported.

'iwlist wlan0 ap' shows "Access Point in range".. Will this also change
to show something else? And will there be some kind of flag that will
differentiate APs from associated stations?

> 	2) I've made the little patch below (for 2002-10-12) and I'm
> suggesting its inclusion in HostAP. The patch was *very* quickly
> tested.

Merged into Host AP CVS with couple of minor changes due to differences
between 2002-10-12 release and CVS head.

> 	Jouni, any comments ?

Above comments were about this patch and I already replied to your
private message about WE-16 in a separate email.

-- 
Jouni Malinen                                            PGP id EFC895FA



From brian  Sat Dec  7 20:29:21 2002
From: brian (Brian Sugar)
Date: Sat, 7 Dec 2002 20:29:21 -0800
Subject: ad-hoc works but master does not
Message-ID: <9F73A8DE-0A65-11D7-ADC0-0003935B4B60@sugar.tv>

redhat 8.0 - master
mac os x.2 - client

cannot see access point when redhat box is in master mode only in 
ad-hoc mode.  i have the non broadcom linksys wmp11 pci card (1.4.2 
firmware) in the rh box.

btw kernel 2.4.20

help, pls




From jasonb  Sat Dec  7 20:37:26 2002
From: jasonb (Jason Boxman)
Date: Sat, 7 Dec 2002 23:37:26 -0500
Subject: ad-hoc works but master does not
In-Reply-To: <9F73A8DE-0A65-11D7-ADC0-0003935B4B60@sugar.tv>
References: <9F73A8DE-0A65-11D7-ADC0-0003935B4B60@sugar.tv>
Message-ID: <200212072337.26157.jasonb@edseek.com>

On Saturday 07 December 2002 11:29 pm, Brian Sugar wrote:
> redhat 8.0 - master
> mac os x.2 - client
>
> cannot see access point when redhat box is in master mode only in
> ad-hoc mode.  i have the non broadcom linksys wmp11 pci card (1.4.2
> firmware) in the rh box.

STA 1.4.2 is widely known to be quite busted.  You need to upgrade or 
downgrade your firmware.  If you can't flash it, you can RAM upload 1.4.9.

Check out my HostAP 2002-10-12 howto:

http://trekweb.com/~jasonb/articles/hostap_20021012.shtml

> btw kernel 2.4.20
>
> help, pls
>

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages





From doug  Sat Dec  7 20:48:30 2002
From: doug (Doug Yeager)
Date: Sat, 07 Dec 2002 23:48:30 -0500
Subject: ad-hoc works but master does not
In-Reply-To: <9F73A8DE-0A65-11D7-ADC0-0003935B4B60@sugar.tv>
Message-ID: <4.3.2.7.0.20021207234658.03751280@yeagerautomation.com>

1.4.2 firmware didn't work for me for master no matter what i tried.
i updated to 1.4.9 and actually to 1.5.6 now and all is good.  update your 
firmware and i'll bet it works.
i would like to know also, as i have mac users try i'm sure....don't know 
if they are successful. :)



At 08:29 PM 12/07/2002 -0800, you wrote:
>redhat 8.0 - master
>mac os x.2 - client
>
>cannot see access point when redhat box is in master mode only in ad-hoc 
>mode.  i have the non broadcom linksys wmp11 pci card (1.4.2 firmware) in 
>the rh box.
>
>btw kernel 2.4.20
>
>help, pls
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap




From doug  Sat Dec  7 07:30:54 2002
From: doug (Doug Yeager)
Date: Sat, 07 Dec 2002 10:30:54 -0500
Subject: No more space in this STA's PS mode buffer
Message-ID: <4.3.2.7.0.20021207102631.03675870@yeagerautomation.com>

i have a few AP's in downtown knoxville serving coffee houses.  i review 
the dmesg logs frequently to see what is going on.  every now and then i 
get this log messages.  usually follows a resetting of the AP card.  my ap 
is wmp11 pci card.  it would be much appreciated if someone could interpret 
this message for me.  what is PS mode buffer?  can i prevent this w/ some 
setting?  the results of this  are not horrible as only the client that 
causes this usually cannot get back on....everyone else is usually o.k. 
until i reboot the AP.  one time i was able to run down one of the clients 
on the wlan and beat him up and take his laptop.  i found a dwl-650 card 
inside if that helps at all.

dmesg log where the trouble starts:
---------------------

wlan0: 00:04:75:c4:36:b1 auth_cb - STA authenticated
wlan0: 00:04:75:c4:36:b1 reassoc (len=24 prev_ap=00:06:25:09:0b:31) => 0(0) 
(OK,
  old AID)
wlan0: 00:04:75:c4:36:b1 assoc_cb - STA associated
wlan0: STA 00:04:75:c4:36:b1 TX rate lowered to 55
wlan0: STA 00:04:75:c4:36:b1 TX rate raised to 110
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
wlan0: STA 00:04:75:c4:36:b1 TX rate lowered to 55
wlan0: sending disassociation info to STA 00:04:75:c4:36:b1(last=22325356, 
jiffi
es=22355456)
wlan0: STA 00:04:75:c4:36:b1 TX rate lowered to 20
wlan0: sending deauthentication info to STA 
00:04:75:c4:36:b1(last=22325356, jif
fies=22355556)
wlan0: Could not find STA for this TX error
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
wlan0: STA 00:02:2d:66:cb:0c TX rate raised to 55
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer
No more space in this STA's PS mode buffer




From czoffoli  Sun Dec  8 08:37:36 2002
From: czoffoli (Christian Zoffoli)
Date: Sun, 08 Dec 2002 17:37:36 +0100
Subject: Senao cards & antsel_rx / antsel_tx
Message-ID: <3DF37550.9070901@xmerlin.org>

Hi to all.

I'm tring to set the rx ant on the lower connector and the tx ant on the 
higher ...but without success.
Is it possible ? ..someone did it ?

I'm using PRI v1.1.1 and STA v1.5.6 (on some senao / engenius NL2511CD 
PLUS EXT2) ...with hostap 2002-10-12 and wireless ext v15.


Thanks,
Christian




From brian  Sun Dec  8 12:17:05 2002
From: brian (Brian Sugar)
Date: Sun, 8 Dec 2002 12:17:05 -0800
Subject: ad-hoc works but master does not
In-Reply-To: <200212072337.26157.jasonb@edseek.com>
Message-ID: <0510614C-0AEA-11D7-ADC0-0003935B4B60@sugar.tv>

i don't have a windows machine so i'll have to RAM upload...can i do 
this with the wmp11?

On Saturday, December 7, 2002, at 08:37  PM, Jason Boxman wrote:

> On Saturday 07 December 2002 11:29 pm, Brian Sugar wrote:
>> redhat 8.0 - master
>> mac os x.2 - client
>>
>> cannot see access point when redhat box is in master mode only in
>> ad-hoc mode.  i have the non broadcom linksys wmp11 pci card (1.4.2
>> firmware) in the rh box.
>
> STA 1.4.2 is widely known to be quite busted.  You need to upgrade or
> downgrade your firmware.  If you can't flash it, you can RAM upload 
> 1.4.9.
>
> Check out my HostAP 2002-10-12 howto:
>
> http://trekweb.com/~jasonb/articles/hostap_20021012.shtml
>
>> btw kernel 2.4.20
>>
>> help, pls
>>
>
> -- 
>
> Jason Boxman
> Administrator TrekWeb.COM
> http://trekweb.com/~jasonb/articles/ - Linux Pages
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From doug  Sun Dec  8 12:37:21 2002
From: doug (Doug Yeager)
Date: Sun, 08 Dec 2002 15:37:21 -0500
Subject: ad-hoc works but master does not
In-Reply-To: <0510614C-0AEA-11D7-ADC0-0003935B4B60@sugar.tv>
References: <200212072337.26157.jasonb@edseek.com>
Message-ID: <4.3.2.7.0.20021208153539.0375a1a0@yeagerautomation.com>

yep,
i do it successfully right now on two different machines using wmp11 pci card.
prism2_srec -rv wlan0 rf010506.hex



At 12:17 PM 12/08/2002 -0800, you wrote:
>i don't have a windows machine so i'll have to RAM upload...can i do this 
>with the wmp11?
>
>On Saturday, December 7, 2002, at 08:37  PM, Jason Boxman wrote:
>
>>On Saturday 07 December 2002 11:29 pm, Brian Sugar wrote:
>>>redhat 8.0 - master
>>>mac os x.2 - client
>>>
>>>cannot see access point when redhat box is in master mode only in
>>>ad-hoc mode.  i have the non broadcom linksys wmp11 pci card (1.4.2
>>>firmware) in the rh box.
>>
>>STA 1.4.2 is widely known to be quite busted.  You need to upgrade or
>>downgrade your firmware.  If you can't flash it, you can RAM upload 1.4.9.
>>
>>Check out my HostAP 2002-10-12 howto:
>>
>>http://trekweb.com/~jasonb/articles/hostap_20021012.shtml
>>
>>>btw kernel 2.4.20
>>>
>>>help, pls
>>
>>--
>>
>>Jason Boxman
>>Administrator TrekWeb.COM
>>http://trekweb.com/~jasonb/articles/ - Linux Pages
>>
>>
>>_______________________________________________
>>HostAP mailing list
>>HostAP at shmoo.com
>>http://lists.shmoo.com/mailman/listinfo/hostap
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap




From brian  Sun Dec  8 13:00:13 2002
From: brian (Brian Sugar)
Date: Sun, 8 Dec 2002 13:00:13 -0800
Subject: ad-hoc works but master does not
In-Reply-To: <4.3.2.7.0.20021208153539.0375a1a0@yeagerautomation.com>
Message-ID: <0BAAF058-0AF0-11D7-AF86-0003935B4B60@sugar.tv>

cool it worked!

i can get online via my g4 powerbook.  next question - can i set the 
ifconfig eth0???  how can i get to the access point via ssh or http??


On Sunday, December 8, 2002, at 12:37  PM, Doug Yeager wrote:

> yep,
> i do it successfully right now on two different machines using wmp11 
> pci card.
> prism2_srec -rv wlan0 rf010506.hex
>
>
>
> At 12:17 PM 12/08/2002 -0800, you wrote:
>> i don't have a windows machine so i'll have to RAM upload...can i do 
>> this with the wmp11?
>>
>> On Saturday, December 7, 2002, at 08:37  PM, Jason Boxman wrote:
>>
>>> On Saturday 07 December 2002 11:29 pm, Brian Sugar wrote:
>>>> redhat 8.0 - master
>>>> mac os x.2 - client
>>>>
>>>> cannot see access point when redhat box is in master mode only in
>>>> ad-hoc mode.  i have the non broadcom linksys wmp11 pci card (1.4.2
>>>> firmware) in the rh box.
>>>
>>> STA 1.4.2 is widely known to be quite busted.  You need to upgrade or
>>> downgrade your firmware.  If you can't flash it, you can RAM upload 
>>> 1.4.9.
>>>
>>> Check out my HostAP 2002-10-12 howto:
>>>
>>> http://trekweb.com/~jasonb/articles/hostap_20021012.shtml
>>>
>>>> btw kernel 2.4.20
>>>>
>>>> help, pls
>>>
>>> --
>>>
>>> Jason Boxman
>>> Administrator TrekWeb.COM
>>> http://trekweb.com/~jasonb/articles/ - Linux Pages
>>>
>>>
>>> _______________________________________________
>>> HostAP mailing list
>>> HostAP at shmoo.com
>>> http://lists.shmoo.com/mailman/listinfo/hostap
>>
>> _______________________________________________
>> HostAP mailing list
>> HostAP at shmoo.com
>> http://lists.shmoo.com/mailman/listinfo/hostap
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From brian  Sun Dec  8 13:07:07 2002
From: brian (Brian Sugar)
Date: Sun, 8 Dec 2002 13:07:07 -0800
Subject: ad-hoc works but master does not
In-Reply-To: <0BAAF058-0AF0-11D7-AF86-0003935B4B60@sugar.tv>
Message-ID: <027C9CFD-0AF1-11D7-AF86-0003935B4B60@sugar.tv>

some more questions:

how can the access point give out ips?
how do i set the ip of the access point?


On Sunday, December 8, 2002, at 01:00  PM, Brian Sugar wrote:

> cool it worked!
>
> i can get online via my g4 powerbook.  next question - can i set the 
> ifconfig eth0???  how can i get to the access point via ssh or http??
>
>
> On Sunday, December 8, 2002, at 12:37  PM, Doug Yeager wrote:
>
>> yep,
>> i do it successfully right now on two different machines using wmp11 
>> pci card.
>> prism2_srec -rv wlan0 rf010506.hex
>>
>>
>>
>> At 12:17 PM 12/08/2002 -0800, you wrote:
>>> i don't have a windows machine so i'll have to RAM upload...can i do 
>>> this with the wmp11?
>>>
>>> On Saturday, December 7, 2002, at 08:37  PM, Jason Boxman wrote:
>>>
>>>> On Saturday 07 December 2002 11:29 pm, Brian Sugar wrote:
>>>>> redhat 8.0 - master
>>>>> mac os x.2 - client
>>>>>
>>>>> cannot see access point when redhat box is in master mode only in
>>>>> ad-hoc mode.  i have the non broadcom linksys wmp11 pci card (1.4.2
>>>>> firmware) in the rh box.
>>>>
>>>> STA 1.4.2 is widely known to be quite busted.  You need to upgrade 
>>>> or
>>>> downgrade your firmware.  If you can't flash it, you can RAM upload 
>>>> 1.4.9.
>>>>
>>>> Check out my HostAP 2002-10-12 howto:
>>>>
>>>> http://trekweb.com/~jasonb/articles/hostap_20021012.shtml
>>>>
>>>>> btw kernel 2.4.20
>>>>>
>>>>> help, pls
>>>>
>>>> --
>>>>
>>>> Jason Boxman
>>>> Administrator TrekWeb.COM
>>>> http://trekweb.com/~jasonb/articles/ - Linux Pages
>>>>
>>>>
>>>> _______________________________________________
>>>> HostAP mailing list
>>>> HostAP at shmoo.com
>>>> http://lists.shmoo.com/mailman/listinfo/hostap
>>>
>>> _______________________________________________
>>> HostAP mailing list
>>> HostAP at shmoo.com
>>> http://lists.shmoo.com/mailman/listinfo/hostap
>>
>> _______________________________________________
>> HostAP mailing list
>> HostAP at shmoo.com
>> http://lists.shmoo.com/mailman/listinfo/hostap
>>
>




From doug  Sun Dec  8 13:21:37 2002
From: doug (Doug Yeager)
Date: Sun, 08 Dec 2002 16:21:37 -0500
Subject: ad-hoc works but master does not
In-Reply-To: <027C9CFD-0AF1-11D7-AF86-0003935B4B60@sugar.tv>
References: <0BAAF058-0AF0-11D7-AF86-0003935B4B60@sugar.tv>
Message-ID: <4.3.2.7.0.20021208161416.0375bb50@yeagerautomation.com>

you probably need wireless tools installed on your AP to control things 
like ipaddress and ssid, etc. of the AP...it gives you the iwconfig command 
really.  you will also need dchpd installed and configured (to hand out IP 
addresses on your wlan0).    you may also need to build the kernel again 
for NAT (masquerade). i'm not sure if default install of linux has this 
option turned on or not....anyone know?    while your at it, might as well 
install DNS(named) to translate domain names too.


At 01:07 PM 12/08/2002 -0800, you wrote:
>some more questions:
>
>how can the access point give out ips?
>how do i set the ip of the access point?
>
>
>On Sunday, December 8, 2002, at 01:00  PM, Brian Sugar wrote:
>
>>cool it worked!
>>
>>i can get online via my g4 powerbook.  next question - can i set the 
>>ifconfig eth0???  how can i get to the access point via ssh or http??
>>
>>
>>On Sunday, December 8, 2002, at 12:37  PM, Doug Yeager wrote:
>>
>>>yep,
>>>i do it successfully right now on two different machines using wmp11 pci 
>>>card.
>>>prism2_srec -rv wlan0 rf010506.hex
>>>
>>>
>>>
>>>At 12:17 PM 12/08/2002 -0800, you wrote:
>>>>i don't have a windows machine so i'll have to RAM upload...can i do 
>>>>this with the wmp11?
>>>>
>>>>On Saturday, December 7, 2002, at 08:37  PM, Jason Boxman wrote:
>>>>
>>>>>On Saturday 07 December 2002 11:29 pm, Brian Sugar wrote:
>>>>>>redhat 8.0 - master
>>>>>>mac os x.2 - client
>>>>>>
>>>>>>cannot see access point when redhat box is in master mode only in
>>>>>>ad-hoc mode.  i have the non broadcom linksys wmp11 pci card (1.4.2
>>>>>>firmware) in the rh box.
>>>>>
>>>>>STA 1.4.2 is widely known to be quite busted.  You need to upgrade or
>>>>>downgrade your firmware.  If you can't flash it, you can RAM upload 1.4.9.
>>>>>
>>>>>Check out my HostAP 2002-10-12 howto:
>>>>>
>>>>>http://trekweb.com/~jasonb/articles/hostap_20021012.shtml
>>>>>
>>>>>>btw kernel 2.4.20
>>>>>>
>>>>>>help, pls
>>>>>
>>>>>--
>>>>>
>>>>>Jason Boxman
>>>>>Administrator TrekWeb.COM
>>>>>http://trekweb.com/~jasonb/articles/ - Linux Pages
>>>>>
>>>>>
>>>>>_______________________________________________
>>>>>HostAP mailing list
>>>>>HostAP at shmoo.com
>>>>>http://lists.shmoo.com/mailman/listinfo/hostap
>>>>
>>>>_______________________________________________
>>>>HostAP mailing list
>>>>HostAP at shmoo.com
>>>>http://lists.shmoo.com/mailman/listinfo/hostap
>>>
>>>_______________________________________________
>>>HostAP mailing list
>>>HostAP at shmoo.com
>>>http://lists.shmoo.com/mailman/listinfo/hostap
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap




From brian  Sun Dec  8 13:52:14 2002
From: brian (Brian Sugar)
Date: Sun, 8 Dec 2002 13:52:14 -0800
Subject: ad-hoc works but master does not
In-Reply-To: <4.3.2.7.0.20021208161416.0375bb50@yeagerautomation.com>
Message-ID: <501F7F8F-0AF7-11D7-A981-0003935B4B60@sugar.tv>

I need NAT so that both machines can get on the network?  my problem is 
either the laptop can get to other machines or the access point can. if 
the laptop is online thru the ap then the ap can't see the network and 
vice versa.

ideally the ap can act normally (i can ssh to and from it, etc) plus it 
is an access point...meaning it's wireless clients can also get on the 
network. it seems that when the machine is acting as an ap it can not 
get on the network, etc.

i have iwconfig, etc

as soon as i "ifconfig br0 192.168.1.1 up" the access point comes off 
the network.




On Sunday, December 8, 2002, at 01:21  PM, Doug Yeager wrote:

> you probably need wireless tools installed on your AP to control 
> things like ipaddress and ssid, etc. of the AP...it gives you the 
> iwconfig command really.  you will also need dchpd installed and 
> configured (to hand out IP addresses on your wlan0).    you may also 
> need to build the kernel again for NAT (masquerade). i'm not sure if 
> default install of linux has this option turned on or not....anyone 
> know?    while your at it, might as well install DNS(named) to 
> translate domain names too.
>
>
> At 01:07 PM 12/08/2002 -0800, you wrote:
>> some more questions:
>>
>> how can the access point give out ips?
>> how do i set the ip of the access point?
>>
>>
>> On Sunday, December 8, 2002, at 01:00  PM, Brian Sugar wrote:
>>
>>> cool it worked!
>>>
>>> i can get online via my g4 powerbook.  next question - can i set the 
>>> ifconfig eth0???  how can i get to the access point via ssh or >>> http??
>>>
>>>
>>> On Sunday, December 8, 2002, at 12:37  PM, Doug Yeager wrote:
>>>
>>>> yep,
>>>> i do it successfully right now on two different machines using 
>>>> wmp11 pci card.
>>>> prism2_srec -rv wlan0 rf010506.hex
>>>>
>>>>
>>>>
>>>> At 12:17 PM 12/08/2002 -0800, you wrote:
>>>>> i don't have a windows machine so i'll have to RAM upload...can i 
>>>>> do this with the wmp11?
>>>>>
>>>>> On Saturday, December 7, 2002, at 08:37  PM, Jason Boxman wrote:
>>>>>
>>>>>> On Saturday 07 December 2002 11:29 pm, Brian Sugar wrote:
>>>>>>> redhat 8.0 - master
>>>>>>> mac os x.2 - client
>>>>>>>
>>>>>>> cannot see access point when redhat box is in master mode only in
>>>>>>> ad-hoc mode.  i have the non broadcom linksys wmp11 pci card 
>>>>>>> (1.4.2
>>>>>>> firmware) in the rh box.
>>>>>>
>>>>>> STA 1.4.2 is widely known to be quite busted.  You need to 
>>>>>> upgrade or
>>>>>> downgrade your firmware.  If you can't flash it, you can RAM 
>>>>>> upload 1.4.9.
>>>>>>
>>>>>> Check out my HostAP 2002-10-12 howto:
>>>>>>
>>>>>> http://trekweb.com/~jasonb/articles/hostap_20021012.shtml
>>>>>>
>>>>>>> btw kernel 2.4.20
>>>>>>>
>>>>>>> help, pls
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Jason Boxman
>>>>>> Administrator TrekWeb.COM
>>>>>> http://trekweb.com/~jasonb/articles/ - Linux Pages
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> HostAP mailing list
>>>>>> HostAP at shmoo.com
>>>>>> http://lists.shmoo.com/mailman/listinfo/hostap
>>>>>
>>>>> _______________________________________________
>>>>> HostAP mailing list
>>>>> HostAP at shmoo.com
>>>>> http://lists.shmoo.com/mailman/listinfo/hostap
>>>>
>>>> _______________________________________________
>>>> HostAP mailing list
>>>> HostAP at shmoo.com
>>>> http://lists.shmoo.com/mailman/listinfo/hostap
>>
>> _______________________________________________
>> HostAP mailing list
>> HostAP at shmoo.com
>> http://lists.shmoo.com/mailman/listinfo/hostap
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From linux  Sun Dec  8 15:05:26 2002
From: linux (Linux Rocks!)
Date: Sun, 8 Dec 2002 15:05:26 -0800
Subject: no luck in linux... works in windows.... help! 
Message-ID: <200212081505.26412.linux@rocksolidnetworks.com>

Let me preface this with an  apology for such a long  message.. I really dont 
know what Info I need to include....Im sorry its soooo long.

I need some help figureing out what Im doing right, and what Im doing wrong, 
so I can make an AP. I am using a proxim rangelan-ds pcmcia card (using the 
hostap_cs module). I think Its loading w/out errors Im loading the module (I 
made an entry in hostap_cs.conf with my manfif, and am using the following 
options:
module "hostap_cs" opts "channel=11 iw_mode=3 edssid=any ignore_cis_vcc=1"
Im using the ignore vcc option because it fails to load w/out it (i guess this 
is a voltage issue..)
Im  using the essid "any" because thats what the windows software uses as the 
default id.
iwmode=3 is master
The driver seems to load fine, iwconfig shows wlan0 with a bunch of info (too 
much to type in this messge...)

at boot time, the last messages i see about wlan0 are:
wlan0: NIC: id=0x8002 v1.0.0
wlan0: PRI:: id=0x15 v0.3.0
wlan0: STA: id=0x1f v0.8.3
(i noticed the following after boot using dmesg) 
wlan0: defaluting to host-based encryption as a woraround for a firmware bug 
in Host AP mod WEP
wlan0: LinkStatus=2 (Disconnected)
wlan0: prism2_open
(all of the above is typed, not pasted.. may have typos)

So... Im guessing its fine. I setup tcp/ip using wlan0 via /etc/rc.d/rc.inet1

I have 2 laptops, and 2 proxim cards.
Using windows 98 the cards work fine
using linux I cant seem to get them to work :(

Ive tried re-configuring (via hostap_cs.conf) every way I can think of, and 
every way on the windows computer (using windows as a workstation to connect 
to the linux hostap_cs box) in every possible way I can think of (using the 
proxim software...) and I still cant get them to talk. 

any help is apreciated.

Jamie

-- 
No microsoft products were used to produce this message.
EUG-LUG Mailing List:
http://mailman.efn.org/cgi-bin/listinfo/eug-lug




From victor.aleo  Sun Dec  8 15:46:26 2002
From: victor.aleo (Victor Aleo)
Date: Mon, 09 Dec 2002 00:46:26 +0100
Subject: Problems with the last CVS version
References: <3DEE981D.6080708@estudiant.upc.es> <20021205030102.GA1000@jm.kir.nu>
Message-ID: <3DF3D9D2.1080804@estudiant.upc.es>

Jouni Malinen wrote:

>On Thu, Dec 05, 2002 at 01:04:45AM +0100, Victor Aleo wrote:
>
>>I have the next problem when a station tx data frames to the AP (both 
>>running the last CVS version):
>>
>>wlan0: RX: dropped FCSErr frame (status=01)
>>wlan0: RX: dropped FCSErr frame (status=2001)
>>wlan0: RX: unknown MACPort 5
>>    
>>
>
>Are you using bridging or having wlan0 configured to promiscuous mode?
>The patch for adding support to station mode promiscuous sniffing and
>multicast caused these things to be printed. Previously firmware dropped
>those frames before they hit the driver.
>
Yes, I am using bridging with the AP device (wlan0) and an ethernet 
device. Thus, wlan0 is set in promiscous mode as you have pointed out.

>I might revert that patch as far as AP mode is concerned, i.e., not to
>set promiscuous mode in Host AP mode. It is not needed anyway since
>802.11 AP is already receiving all data frames in its own BSS.
>
>>FCS stands for Frame Check Sequence, if I'm not wrong, but I do not know 
>>what is the problem. I did not have problems with the 2002-10-12 version 
>>of the driver. At the end, more than a half of the packets are not 
>>transmitted. Moreover, the driver decreases the date bit rate of the 
>>station from 11 to 1 Mbps.
>>    
>>
>
>That might be something else.. I would have assumed that those FCS
>errors would not cause this kind of problems (unless printing them is
>using too much CPU power). If you would like to test something before I
>change the CVS version, you could just comment out
>HFA384X_RID_PROMISCUOUSMODE setting in hostap_hw.c function
>prism2_setup_rids(). It should at least remove those "dropped FCSErr
>frame" messages and reduce the number of "unknown MACPort" errors.
>
I just have comment out HFA384X_RID_PROMISCUOUSMODE setting in 
hostap_hw.c function prism2_setup_rids(). However, the results are 
pretty much the same or even worse because now I get new "wlan0: RX: 
unknown MACPort #" errors, where # can be 1, 3, 4, or 6 (see a part of 
an experiment below).

I think this is a really serious problem due to the stations cannot 
transmit to the AP. Notice that my AP is bridged with an ethernet device 
and I did not have this problem with the version 2002-10-12 of the 
driver. Have you tried the last CVS version with the configuration I 
have: AP bridged with an ethernet device?

wlan0: RX: dropped FCSErr frame (status=8001)
wlan0: RX: unknown MACPort 6
wlan0: RX: dropped FCSErr frame (status=8001)
wlan0: RX: dropped FCSErr frame (status=01)
wlan0: RX: dropped FCSErr frame (status=2001)

Thanks,

Victor




From shong  Sun Dec  8 16:14:02 2002
From: shong (Seungpyo Hong)
Date: Mon, 9 Dec 2002 09:14:02 +0900
Subject: ad-hoc works but master does not
In-Reply-To: <200212072337.26157.jasonb@edseek.com>
Message-ID: <KHELIOHONAEJAMGECMHKCEFMCLAA.shong@clipcomm.co.kr>


Jason, 

I've been suffered by same problem with WPC11-firmware v1.4.2.
But I cannot find a later version(v1.4.9) neither in Linksys site nor Intersil site.
( Linksys site have only v1.4.2 as the latest one. )
Where can I find it? 

BR,
S. Hong

-----Original Message-----
From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com]On Behalf Of Jason Boxman
Sent: Sunday, December 08, 2002 1:37 PM
To: hostap at shmoo.com
Subject: Re: ad-hoc works but master does not


On Saturday 07 December 2002 11:29 pm, Brian Sugar wrote:
> redhat 8.0 - master
> mac os x.2 - client
>
> cannot see access point when redhat box is in master mode only in
> ad-hoc mode.  i have the non broadcom linksys wmp11 pci card (1.4.2
> firmware) in the rh box.

STA 1.4.2 is widely known to be quite busted.  You need to upgrade or 
downgrade your firmware.  If you can't flash it, you can RAM upload 1.4.9.

Check out my HostAP 2002-10-12 howto:

http://trekweb.com/~jasonb/articles/hostap_20021012.shtml

> btw kernel 2.4.20
>
> help, pls
>

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages


_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap


From jasonb  Sun Dec  8 16:21:13 2002
From: jasonb (Jason Boxman)
Date: Sun, 8 Dec 2002 19:21:13 -0500
Subject: ad-hoc works but master does not
In-Reply-To: <KHELIOHONAEJAMGECMHKCEFMCLAA.shong@clipcomm.co.kr>
References: <KHELIOHONAEJAMGECMHKCEFMCLAA.shong@clipcomm.co.kr>
Message-ID: <200212081921.13696.jasonb@edseek.com>

On Sunday 08 December 2002 07:14 pm, Seungpyo Hong wrote:
> Jason,
>
> I've been suffered by same problem with WPC11-firmware v1.4.2.
> But I cannot find a later version(v1.4.9) neither in Linksys site nor
> Intersil site. ( Linksys site have only v1.4.2 as the latest one. )
> Where can I find it?

You'll find a link to files which are RAM uploadable in my article linked 
earlier in this thread which NetGate is kind enough to host.  It's 1.4.9.zip 
I believe.

> BR,
> S. Hong
>
<snip>

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages





From doug  Sun Dec  8 18:04:06 2002
From: doug (Doug Yeager)
Date: Sun, 08 Dec 2002 21:04:06 -0500
Subject: ad-hoc works but master does not
In-Reply-To: <501F7F8F-0AF7-11D7-A981-0003935B4B60@sugar.tv>
References: <4.3.2.7.0.20021208161416.0375bb50@yeagerautomation.com>
Message-ID: <4.3.2.7.0.20021208205858.037554e0@yeagerautomation.com>

what is your wired network address?  i'm sure you have an eth0.
i'd guess your problem has to do w/ your routing table.
here is what mine looks like:
Last login: Sun Dec  8 15:00:26 2002
[root at home root]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
255.255.255.255 *               255.255.255.255 UH    0      0        0 wlan0
kntn0dsl-l0.tn. *               255.255.255.255 UH    0      0        0 ppp0
192.168.1.0     *               255.255.255.0   U     0      0        0 wlan0
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
default         kntn0dsl-l0.tn. 0.0.0.0         UG    0      0        0 ppp0


i have a DSL pppoe connection to the net.  i've setup my wlan w/ a 
192.168.1.xxx network scheme.

i use nocatauth to manage the firewall.  it is really a cool setup. :)




At 01:52 PM 12/08/2002 -0800, you wrote:
>I need NAT so that both machines can get on the network?  my problem is 
>either the laptop can get to other machines or the access point can. if 
>the laptop is online thru the ap then the ap can't see the network and 
>vice versa.
>
>ideally the ap can act normally (i can ssh to and from it, etc) plus it is 
>an access point...meaning it's wireless clients can also get on the 
>network. it seems that when the machine is acting as an ap it can not get 
>on the network, etc.
>
>i have iwconfig, etc
>
>as soon as i "ifconfig br0 192.168.1.1 up" the access point comes off the 
>network.
>
>
>
>
>On Sunday, December 8, 2002, at 01:21  PM, Doug Yeager wrote:
>
>>you probably need wireless tools installed on your AP to control things 
>>like ipaddress and ssid, etc. of the AP...it gives you the iwconfig 
>>command really.  you will also need dchpd installed and configured (to 
>>hand out IP addresses on your wlan0).    you may also need to build the 
>>kernel again for NAT (masquerade). i'm not sure if default install of 
>>linux has this option turned on or not....anyone know?    while your at 
>>it, might as well install DNS(named) to translate domain names too.
>>
>>
>>At 01:07 PM 12/08/2002 -0800, you wrote:
>>>some more questions:
>>>
>>>how can the access point give out ips?
>>>how do i set the ip of the access point?
>>>
>>>
>>>On Sunday, December 8, 2002, at 01:00  PM, Brian Sugar wrote:
>>>
>>>>cool it worked!
>>>>
>>>>i can get online via my g4 powerbook.  next question - can i set the 
>>>>ifconfig eth0???  how can i get to the access point via ssh or >>> http??
>>>>
>>>>
>>>>On Sunday, December 8, 2002, at 12:37  PM, Doug Yeager wrote:
>>>>
>>>>>yep,
>>>>>i do it successfully right now on two different machines using wmp11 
>>>>>pci card.
>>>>>prism2_srec -rv wlan0 rf010506.hex
>>>>>
>>>>>
>>>>>
>>>>>At 12:17 PM 12/08/2002 -0800, you wrote:
>>>>>>i don't have a windows machine so i'll have to RAM upload...can i do 
>>>>>>this with the wmp11?
>>>>>>
>>>>>>On Saturday, December 7, 2002, at 08:37  PM, Jason Boxman wrote:
>>>>>>
>>>>>>>On Saturday 07 December 2002 11:29 pm, Brian Sugar wrote:
>>>>>>>>redhat 8.0 - master
>>>>>>>>mac os x.2 - client
>>>>>>>>
>>>>>>>>cannot see access point when redhat box is in master mode only in
>>>>>>>>ad-hoc mode.  i have the non broadcom linksys wmp11 pci card (1.4.2
>>>>>>>>firmware) in the rh box.
>>>>>>>
>>>>>>>STA 1.4.2 is widely known to be quite busted.  You need to upgrade or
>>>>>>>downgrade your firmware.  If you can't flash it, you can RAM upload 
>>>>>>>1.4.9.
>>>>>>>
>>>>>>>Check out my HostAP 2002-10-12 howto:
>>>>>>>
>>>>>>>http://trekweb.com/~jasonb/articles/hostap_20021012.shtml
>>>>>>>
>>>>>>>>btw kernel 2.4.20
>>>>>>>>
>>>>>>>>help, pls
>>>>>>>
>>>>>>>--
>>>>>>>
>>>>>>>Jason Boxman
>>>>>>>Administrator TrekWeb.COM
>>>>>>>http://trekweb.com/~jasonb/articles/ - Linux Pages
>>>>>>>
>>>>>>>
>>>>>>>_______________________________________________
>>>>>>>HostAP mailing list
>>>>>>>HostAP at shmoo.com
>>>>>>>http://lists.shmoo.com/mailman/listinfo/hostap
>>>>>>
>>>>>>_______________________________________________
>>>>>>HostAP mailing list
>>>>>>HostAP at shmoo.com
>>>>>>http://lists.shmoo.com/mailman/listinfo/hostap
>>>>>
>>>>>_______________________________________________
>>>>>HostAP mailing list
>>>>>HostAP at shmoo.com
>>>>>http://lists.shmoo.com/mailman/listinfo/hostap
>>>
>>>_______________________________________________
>>>HostAP mailing list
>>>HostAP at shmoo.com
>>>http://lists.shmoo.com/mailman/listinfo/hostap
>>
>>_______________________________________________
>>HostAP mailing list
>>HostAP at shmoo.com
>>http://lists.shmoo.com/mailman/listinfo/hostap
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap




From jkmaline  Sun Dec  8 18:25:45 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 8 Dec 2002 18:25:45 -0800
Subject: Problems with the last CVS version
In-Reply-To: <3DF3D9D2.1080804@estudiant.upc.es>
References: <3DEE981D.6080708@estudiant.upc.es> <20021205030102.GA1000@jm.kir.nu> <3DF3D9D2.1080804@estudiant.upc.es>
Message-ID: <20021209022545.GA1283@jm.kir.nu>

On Mon, Dec 09, 2002 at 12:46:26AM +0100, Victor Aleo wrote:

> I just have comment out HFA384X_RID_PROMISCUOUSMODE setting in 
> hostap_hw.c function prism2_setup_rids(). However, the results are 
> pretty much the same or even worse because now I get new "wlan0: RX: 
> unknown MACPort #" errors, where # can be 1, 3, 4, or 6 (see a part of 
> an experiment below).

Oops.. That was not enough since promiscuous mode was also set in
hostap.c.. I would guess that your card was still in promiscuous mode.

> I think this is a really serious problem due to the stations cannot 
> transmit to the AP. Notice that my AP is bridged with an ethernet device 
> and I did not have this problem with the version 2002-10-12 of the 
> driver. Have you tried the last CVS version with the configuration I 
> have: AP bridged with an ethernet device?

Yes, that works fine in my tests.

However, I was able to duplicate FCSErr and unknown MACPort errors with
station firmware version 1.4.9 (running in Managed mode, associated with
another card in Host AP mode). Removing promiscuous mode removed all
these errors. I have now commented out the promiscuous mode setting from
CVS version until these things can be resolved. So, I would suggest that
you would retest with the latest CVS version.

I have also seen another problem when Host AP driver is running as a
client. It seems to be quite easy to get the card into state in which it
does not ACK frames sent to it even though it receives the frames
correctly. This will lead to txexc increasing by one for every TX frame
in the AP and TX rate is reduced to 1 Mbps. I have usally been able to
get the ACKs back by reseting the card (with 'iwpriv wlan0 reset 0' or
sometimes this has required 'iwpriv wlan0 reset 1'). I'm not sure why
this happens, but it will certainly cause poor performance.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec  8 20:17:40 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 8 Dec 2002 20:17:40 -0800
Subject: HostAP IEEE 802.1x modifications
In-Reply-To: <200211131843.20247.oleg.izhvanov@resonext.com>
References: <200211131843.20247.oleg.izhvanov@resonext.com>
Message-ID: <20021209041740.GA5108@jm.kir.nu>

On Wed, Nov 13, 2002 at 06:43:20PM +0000, Oleg Izhvanov wrote:

> Ok, here is the patch. There are some other modifications except
> WEP rekeying, so here is the brief changelog:
> 
> * WEP rekeying support added ('-t' command line option)

Merged to CVS version. I modified this a bit and it seems to work fine
also with individual station keys (i.e., both broadcast and unicast keys
will be updated). I still need to add TX callback function to make sure
that station ACKs (802.11) EAPOL-Key frame before taking the new unicast
key into use. Broadcast key needs to be taken into use immediately (but
previous key is still available for decryption). EAPOL-Key could anyway
be resent if a station does not ACK it.

I removed MSB setting of key index from hostapd_rotate_wep() since it
looked like a workaround for WinXP Supplicant and I would guess it
should be in more generic place. Similar behavior is now available with
separate command line option '-w'. Do you have any extra information
about the WinXP Supplicant operations? At least, setting this bit did
not fix my WinXP Supplicant.

On the positive side, with this rekeying patch, I was able to use
Xsupplicant and Host AP driver in the Managed mode to automatically set
both the broadcast and unicast keys and rekey them. prism2_params
ieee_802_1x, host_encrypt, and host_decrypt need to be set to make
rekeying work.

> * EAPOL-key frame now uses an NTP timestamp as the replay
>   counter

Merged to CVS.

> * Added support for non-prism based cards(Wireless Extensions only).

I haven't merged this in yet. I'm going to change the patch a bit and
call it something else.. It should work also with Prism-based card when
using Host AP driver without hostapd (i.e., kernel driver performing
802.11 auth/assoc).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec  8 20:33:48 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 8 Dec 2002 20:33:48 -0800
Subject: 802.1x with WinXP
In-Reply-To: <20021207044335.GA2048@jm.kir.nu>
References: <courier.3DF06A02.00006393@softhome.net> <20021207032045.GA1263@jm.kir.nu> <20021207043109.GA29766@skull.piratehaven.org> <20021207044335.GA2048@jm.kir.nu>
Message-ID: <20021209043348.GA5225@jm.kir.nu>

On Fri, Dec 06, 2002 at 08:43:35PM -0800, Jouni Malinen wrote:

> If only Supplicant in WinXP would give a bit more debugging information
> to find out what is causing the problems.. If anyone happens to know a
> way of configuring something like this or knows of a debug version of
> that Supplicant, please do let me know. This would certainly make
> debugging lot easier.

Several hours of expirimenting with various tricks did not help with
this.. Everything seems to be working fine with Xsupplicant, but I
cannot get WinXP (SP1) Supplicant to be happy with the transmitted keys.
It just reports that network connection could not be established (I have
seen at least two different error messages for this). In some cases I
have been able to send frames using WEP encryption, so apparently the
keys were in proper format.

I have found possible cause for some of the problems. Current Host AP
driver does not support PS buffering for 802.1x frames. However, even
with power saving disabled in the WinXP driver, there was no way of
getting the connection last more than few seconds. I'm guessing that
this is because WinXP Supplicant rejects either EAPOL-Key packet
(although WEP key gets changed) or final Access-Accept from RADIUS.
However, I have no idea why..

I would really need to get more debug info out of the WinXP Supplicant,
so if someone happens to have good contact info for Microsoft
developers/support, please let me know. Should someone have (or can
easily make) a frame dump (i.e., sniffed from the wireless media) of a
successful 802.1x exchange using WinXP Supplicant and any .1x
Authenticator/Auth Server, it might be useful in comparing what could go
wrong. This dump would need to include WEP key exchange using EAPOL-Key
frame.

-- 
Jouni Malinen                                            PGP id EFC895FA



From linux  Sun Dec  8 20:37:57 2002
From: linux (Linux Rocks!)
Date: Sun, 8 Dec 2002 20:37:57 -0800
Subject: I think Im getting closer... but maybe Im fooling myself :(
Message-ID: <200212082037.57241.linux@rocksolidnetworks.com>

Im thinking I have hostap setup right (although I dont really know, but Im not 
getting any obvious erors..) However I still cant connect to it. If setup 
dhcpd on wlan0. Im trying to use the windows laptop to connect with it, and I 
have many options that I dont really know what to set. Heres a list:
Mode: AdHoc, 802.11 AdHoc, Infrastructure
SSID (im using "blah")
Ethernet Conversion: RFC1042, Excapsulated, 802.1h
I have the TX rate set to Fully Automatic
WEP Disabled (no need to add complications untill I get something working)
PS Mode: disabled (same as above)
Channel: 11

On the hostap_cs.conf Im using these options:
module "hostap_cs" opts "channel=11 iw_mode=3 essid=blah ignore_cis_vcc=1"

Eventually I will want to use a linux workstation too, should I use hostap 
module for the workstation? or should I use orinoco_cs? and how should I 
configure it?

Is there a simple cheatsheet type thing that has definitions of things? It 
would be really handy If I could have a single page that explained wireless 
terms such as adhoc, essid, tx rate, ....

Jamie


-- 
No microsoft products were used to produce this message.
EUG-LUG Mailing List:
http://mailman.efn.org/cgi-bin/listinfo/eug-lug




From bapper  Sun Dec  8 21:55:47 2002
From: bapper (Brian Pomerantz)
Date: Sun, 8 Dec 2002 21:55:47 -0800
Subject: 802.1x with WinXP
In-Reply-To: <20021209043348.GA5225@jm.kir.nu>
References: <courier.3DF06A02.00006393@softhome.net> <20021207032045.GA1263@jm.kir.nu> <20021207043109.GA29766@skull.piratehaven.org> <20021207044335.GA2048@jm.kir.nu> <20021209043348.GA5225@jm.kir.nu>
Message-ID: <20021209055547.GA19065@skull.piratehaven.org>

On Sun, Dec 08, 2002 at 08:33:48PM -0800, Jouni Malinen wrote:
> 
> I would really need to get more debug info out of the WinXP Supplicant,
> so if someone happens to have good contact info for Microsoft
> developers/support, please let me know. Should someone have (or can
> easily make) a frame dump (i.e., sniffed from the wireless media) of a
> successful 802.1x exchange using WinXP Supplicant and any .1x
> Authenticator/Auth Server, it might be useful in comparing what could go
> wrong. This dump would need to include WEP key exchange using EAPOL-Key
> frame.
> 

If no one gets you one before tomorrow, then I'll get a trace of an
agere AP2000, Cisco 350, and our AP.  We had a bit of a problem
getting this to work as well.  Right now, I think we don't derive the
keys, we just send new ones that we generate.


BAPper



From jonwood  Sun Dec  8 23:52:12 2002
From: jonwood (Jonathan Wood)
Date: Sun, 8 Dec 2002 23:52:12 -0800
Subject: IAPP?
Message-ID: <207D3624-0B4B-11D7-B084-0003930D291E@speakeasy.net>

Are there any open-source implementations of IAPP, preferably based on 
HostAP?

Thanks




From oleg.izhvanov  Mon Dec  9 06:36:47 2002
From: oleg.izhvanov (Oleg Izhvanov)
Date: Mon, 09 Dec 2002 11:36:47 -0300
Subject: HostAP IEEE 802.1x modifications
References: <200211131843.20247.oleg.izhvanov@resonext.com> <20021209041740.GA5108@jm.kir.nu>
Message-ID: <3DF4AA7F.10601@resonext.com>

Jouni Malinen wrote:

>I removed MSB setting of key index from hostapd_rotate_wep() since it
>looked like a workaround for WinXP Supplicant and I would guess it
>should be in more generic place. Similar behavior is now available with
>separate command line option '-w'. Do you have any extra information
>about the WinXP Supplicant operations? At least, setting this bit did
>not fix my WinXP Supplicant.
>

Setting this bit was the workaround for WLAN card, that is yet being 
developed, not
for XP supplicant.  Setting this bit  is a directive for XP supplicant 
to set the default key
(not the unicast one, but one with indexes from 1 to 4) active. 

There is a way to enable debugging messages in WinXP for EAPOL
related stuff. Just look into following entry in your registry :

\\HKEY_LOCAL_MACHINE\Microsoft\Tracing\EAPOL

All parameters there are self-explanatory, though I haven't managed to 
get console
tracing work, though file tracing worked just fine.

The problem I discovered that XP supplicant doesn't like your replay 
counter fields.
The gettimeofday() call, which was used as replay counter didn't work 
correctly, because
those 8 bytes, generated by it was not constantly growing (struct 
timeval consists of two
longs that leads to machine endian dependency for this field). At least 
this problem
was fixed by the NTP patch.

>I haven't merged this in yet. I'm going to change the patch a bit and
>call it something else.. It should work also with Prism-based card when
>using Host AP driver without hostapd (i.e., kernel driver performing
>802.11 auth/assoc).
>
If you need help just let me know.

Best regards, Oleg





From zimage  Mon Dec  9 01:30:51 2002
From: zimage (Theodor Milkov)
Date: Mon, 9 Dec 2002 11:30:51 +0200
Subject: wlan0 Interface seems to freeze.
In-Reply-To: <20021203021259.3053bdfe.lists@chincogan.net.au>
References: <20021203021259.3053bdfe.lists@chincogan.net.au>
Message-ID: <20021209093051.GE488@del.bg>

On Tue, Dec 03, 2002 at 02:12:59AM +1100, Chincogan Network Services Lists wrote:
> Hi List,
> 
> I have a problem where my wlan0 interface seems to freeze, a dmesg shows pages and pages of this:
> wlan0: prism2_tx: hw not ready - skipping
> wlan0: prism2_tx: hw not ready - skipping
> 
> Doing a "iwpriv wlan0 reset 1" does nothing, to fix this I have to restart pcmcia. Sometimes this problem will leave us for a couple of days other times this will happen multiple times a day.
> 
> This afternoon I am going to change this card with a Dlink DWL-520 to see if that makes any difference.
> 
> My Setup:
> Hostap 2002-10-12
> Kernel 2.4.19
> Pcmcia_cs 3.2.1
> Compaq WL-200
> 
> Once I change the card I will not be using pcmcis_cs anymore as the DWL-520 is a PCI based prism 2.5 chipset.
> Does anyone have any ideas why this could be happening? I hope it goes away with the new card because it is really starting to get annoying.

Just to confirm the same problem here. My setup is very similar to
yours:

hostap 2002-10-12
kernel 2.4.18
pcmcia-cs 3.2.1
Compaq WL-200 (STA 1.4.9)

Ricoh PCI-PCMCIA adapter + Senao 2511 (STA 1.4.9) instead of WL-200
works just fine for weeks. So it must be something with WL-200s.

Kindest regards,

-- 
        Theodor Milkov        Network Administrator
        Davidov Net           Phone: +359 (2) 730158



From adomas.genutis  Mon Dec  9 02:36:47 2002
From: adomas.genutis (Adomas Genutis)
Date: Mon, 09 Dec 2002 11:36:47 +0100
Subject: Reasons for reassociation?
Message-ID: <3DF4723F.9EAA1FB3@mchp.siemens.de>

Hi,

maybe it's an off-topic, but I want to know what are event(s) or
reason(s) for wireless system management entity to initiate
reassociation procedure with other AP. I couldn't found that explicitly
stated in ieee standard, so maybe someone working with firmware could
explain me how it works or reference to other information source. Thank
you for the help.


Adomas Genutis




From praedor  Mon Dec  9 03:33:37 2002
From: praedor (Praedor Atrebates)
Date: Mon, 9 Dec 2002 06:33:37 -0500
Subject: wlan0 Interface seems to freeze.
In-Reply-To: <20021209093051.GE488@del.bg>
References: <20021203021259.3053bdfe.lists@chincogan.net.au> <20021209093051.GE488@del.bg>
Message-ID: <200212090633.40281.praedor@yahoo.com>

I get essentially the same problem, sans the dmesg message, with my WUSB11 
v2.6 (atmel driver).  I have a good connection to my laptop (using pcmcia 
Zoomair prism2 and hostap), kernel 2.4.18, which NEVER goes down or has a 
problem as you describe.  My WUSB11, however, works for some hours (sometimes 
half a dozen or more, sometimes just a few) but then just stops responding 
and resetting is impossible.  The only way to get it back is with a reboot.

The problem appears similar to your prism2 problem though from totally 
different system (different device type - atmel - and interface - usb).

praedor

On Monday 09 December 2002 04:30 am, Theodor Milkov wrote:
> On Tue, Dec 03, 2002 at 02:12:59AM +1100, Chincogan Network Services Lists 
wrote:
> > Hi List,
> >
> > I have a problem where my wlan0 interface seems to freeze, a dmesg shows
> > pages and pages of this: wlan0: prism2_tx: hw not ready - skipping
> > wlan0: prism2_tx: hw not ready - skipping
> >
> > Doing a "iwpriv wlan0 reset 1" does nothing, to fix this I have to
> > restart pcmcia. Sometimes this problem will leave us for a couple of days
> > other times this will happen multiple times a day.
> >
> > This afternoon I am going to change this card with a Dlink DWL-520 to see
> > if that makes any difference.
> >
> > My Setup:
> > Hostap 2002-10-12
> > Kernel 2.4.19
> > Pcmcia_cs 3.2.1
> > Compaq WL-200
> >
> > Once I change the card I will not be using pcmcis_cs anymore as the
> > DWL-520 is a PCI based prism 2.5 chipset. Does anyone have any ideas why
> > this could be happening? I hope it goes away with the new card because it
> > is really starting to get annoying.
>
> Just to confirm the same problem here. My setup is very similar to
> yours:
>
> hostap 2002-10-12
> kernel 2.4.18
> pcmcia-cs 3.2.1
> Compaq WL-200 (STA 1.4.9)
>
> Ricoh PCI-PCMCIA adapter + Senao 2511 (STA 1.4.9) instead of WL-200
> works just fine for weeks. So it must be something with WL-200s.
>
> Kindest regards,



From oleg.izhvanov  Mon Dec  9 11:15:51 2002
From: oleg.izhvanov (Oleg Izhvanov)
Date: Mon, 09 Dec 2002 16:15:51 -0300
Subject: HostAP IEEE 802.1x modifications
References: <200211131843.20247.oleg.izhvanov@resonext.com> <20021209041740.GA5108@jm.kir.nu> <3DF4AA7F.10601@resonext.com>
Message-ID: <3DF4EBE7.20805@resonext.com>

Hi, all

It seems that I misspelled registry value in my previous letter,
so here is the knew one:

\\HKEY_LOCAL_MACHINE\Software\Microsoft\Tracing\EAPOL

Best regards, Oleg





From jkmaline  Mon Dec  9 06:31:02 2002
From: jkmaline (Jouni Malinen)
Date: Mon, 9 Dec 2002 06:31:02 -0800
Subject: IAPP?
In-Reply-To: <207D3624-0B4B-11D7-B084-0003930D291E@speakeasy.net>
References: <207D3624-0B4B-11D7-B084-0003930D291E@speakeasy.net>
Message-ID: <20021209143102.GA1061@jm.kir.nu>

On Sun, Dec 08, 2002 at 11:52:12PM -0800, Jonathan Wood wrote:

> Are there any open-source implementations of IAPP, preferably based on 
> HostAP?

Not that I know of, but if you take a look at the CVS version of
hostapd, there is a start for this.. It does not really do anything yet,
but I'm implementing it. IAPP-ADD and Level 2 Update should be trivial
to finish. MOVE-notify requires some RADIUS processing, but that
shouldn't take too much effort.

-- 
Jouni Malinen                                            PGP id EFC895FA



From mike  Mon Dec  9 08:09:03 2002
From: mike (Michael Shuler)
Date: Mon, 9 Dec 2002 10:09:03 -0600
Subject: Zcomax 200mw Card And Tx-Power
Message-ID: <006b01c29f9d$4fae2590$9600a8c0@oemcomputer>

Earlier in the mailing list I noticed an email about Tx-Power capping.
Essentially it said (if I understood it correctly) that the power will
always be capped at 20db.  However Zcomax now makes a 200mw (23db) card.
I'm using 'iwconfig wlan0 tx-power 23' and it seems to work, i.e. I type
'iwconfig' and it shows 23db power...but I guess based off the previous
email in the mailing list, is it actually setting it to 23db or is it
capping it at 20db?

Also I have noticed when inserting a card and putting it into 'Master'
mode the tx-power seems to take on a random power level...is this a bug
in hostap/wireless tools or something wrong with the Zcomax?

Thanks,
Mike





From mike  Mon Dec  9 08:44:45 2002
From: mike (Michael Shuler)
Date: Mon, 9 Dec 2002 10:44:45 -0600
Subject: Help With Antenna Diversity
Message-ID: <006c01c29fa2$4cae39c0$9600a8c0@oemcomputer>

I'm trying to understand how the tx/rx diversity works if anyone would
be kind enough to enlighten me about their experiences I would really
appreciate it.

Here is what I have tried so far:
1 -> Installed 2 Maxrad 10db omni's on standoff arms at about the top of
a 100ft tower spaced 15ft apart horizontally, ran 2 separate Andrew's
1/2" Andrews Heliax cables to each antenna.

2 -> Attached one antenna cable to first port on Zcomax 200mw card.

3 -> Sampled signal at several locations around the tower (about 2500ft
from the tower; not all are line-of-sight to both antennas and some
times neither antennas have line-of-sight; spaced locations in an even
circle around the tower; took 8 samples)

4 -> I then ran 'prism2_param wlan0 antsel_tx 1' and 'prism2_param wlan0
antsel_rx 1'.

5 -> Reran tests from step 3

Results after diversity seemed to be exactly the same...or negligible
differences.  I was expecting something amazing to happen and was quite
disappointed.  Am I doing something wrong or is antenna diversity a way
for antenna manufacturers to sell more antennas?  

Is there a way to see tx/rx stats based off by the antenna instead of
the card as a whole?  That way I would know for sure that both antennas
were doing something or if something was wrong with one of them.  


Here is what I am thinking of trying but want to check if I am wasting
my time:
Use two Zcomax 200mw cards and 4 90 degree sector panels (two to each
card, one to each antenna port).  One card would be set to channel 1 the
other to 11 and tx/rx diversity would be turned on.  This 'should' give
me 360 degrees of coverage and all of the benefits of sector panels
(smaller window of noise, higher gain, etc).  The only disadvantage
should be only 2 of 4 panels could listen/transmit at a time...this also
could lead to high collisions since a station wanting to transmit on an
inactive panel would think it was clear to transmit, when in reality the
radio card may already be transmitting or receiving on its other panel
and in turn would cause that client to retransmit...which I guess
wouldn't be the end of the world since the other panel would barely
pickup the nose from that client.  

Thanks,
Mike





From czoffoli  Mon Dec  9 09:15:36 2002
From: czoffoli (Christian Zoffoli)
Date: Mon, 09 Dec 2002 18:15:36 +0100
Subject: Zcomax 200mw Card And Tx-Power
In-Reply-To: <006b01c29f9d$4fae2590$9600a8c0@oemcomputer>
References: <006b01c29f9d$4fae2590$9600a8c0@oemcomputer>
Message-ID: <3DF4CFB8.2050308@xmerlin.org>

Michael Shuler wrote:
> Earlier in the mailing list I noticed an email about Tx-Power capping.
> Essentially it said (if I understood it correctly) that the power will
> always be capped at 20db.  However Zcomax now makes a 200mw (23db) card.
> I'm using 'iwconfig wlan0 tx-power 23' and it seems to work, i.e. I type
> 'iwconfig' and it shows 23db power...but I guess based off the previous
> email in the mailing list, is it actually setting it to 23db or is it
> capping it at 20db?
> 
> Also I have noticed when inserting a card and putting it into 'Master'
> mode the tx-power seems to take on a random power level...is this a bug
> in hostap/wireless tools or something wrong with the Zcomax?
> 

with my senao cards (NL-2511CD Plus ext 2) i have found these values 
(seeing the output with a spectrum analizer HP 8592A)

value  dbm
128 -- 26
120 -- 12
110 -- 14.5
107 -- 14
100 -- 16
90  -- 16.5
80  -- 18
70  -- 19.5
60  -- 21
50  -- 22
40  -- 22
30  -- 23.5
20  -- 24.5
10  -- 25
0   -- 25
130 -- 27.5
140 -- 27

the command i've used to set the power is "iwpriv wlan0 txpower $value"

...as you can see the output may be higher than the manufacturer spec 
(...but with distortion at higher levels > 24.5/25dbm).


Regards,
Christian






From Dave.Edwards  Mon Dec  9 09:13:48 2002
From: Dave.Edwards (Dave Edwards)
Date: Mon, 09 Dec 2002 17:13:48 +0000
Subject: Help With Antenna Diversity
References: <006c01c29fa2$4cae39c0$9600a8c0@oemcomputer>
Message-ID: <3DF4CF4C.9080005@abicom-international.com>

Hi Michael,

In my experience Antenna Diversity only really works inside a building, 
the net effect is around +3dB improvement on the receive sensitivity for 
equal antennas.

There is also an issue with the Prism II diversity state machine. I 
don't know if it's been fixed with the later versions of the chipset but 
here is what we observed with the Prism I and Prism II devices:

Firstly the receive process starts with either the last good antenna (ie 
the last port to sucessfully receive a packet) or the default TX/RX port 
(see the prism manual for Antenna port selection) being selected.

Antenna diversity operates when the receiver detects enough energy on 
that port and a decision is then made about which port to use for the 
rest of the packet. The chipset will switch ports for a number of cycles 
until it makes the decision

The problem comes when you are in a situation where the port being 
selected does not receive enough energy to trigger the process, when 
this occurs the radio will effectively become deaf until there is enough 
energy at the port.

We've seen this problem when using a sectored antenna approach, you will 
need some overlap to try and trigger the RX, and in a situation where 
one antenna was completely nulled out by multipath for about 1/2 an hour 
every 8 or 9 hours.

The problem can be solved by forcing the chipset to change antenna ports 
but I'm not sure how you would do this automatically under hostap.


Hope this helps

Dave








From Dave.Edwards  Mon Dec  9 09:16:57 2002
From: Dave.Edwards (Dave Edwards)
Date: Mon, 09 Dec 2002 17:16:57 +0000
Subject: Zcomax 200mw Card And Tx-Power
References: <006b01c29f9d$4fae2590$9600a8c0@oemcomputer> <3DF4CFB8.2050308@xmerlin.org>
Message-ID: <3DF4D009.10902@abicom-international.com>

[cut]

Have you checked the output on a spectrum analyser? We have found that 
the higher output on some radios can effectively splatter across the 
whole 83MHz band, rendering it useless. Also this will "noise" can 
reduce the range of the device significantly.

Dave






From Dave.Edwards  Mon Dec  9 09:32:49 2002
From: Dave.Edwards (Dave Edwards)
Date: Mon, 09 Dec 2002 17:32:49 +0000
Subject: Zcomax 200mw Card And Tx-Power
References: <007b01c29fa7$57164fb0$9600a8c0@oemcomputer>
Message-ID: <3DF4D3C1.4010505@abicom-international.com>

HP 25GHz (HP8193 I think) or Anritsu.

They are not cheap! A 2.5GHz one will cost in excess of  ?10K. If it's 
an issue you could hire one, they tend to be around ?500/week (somebody 
correct me if I'm wrong).

Another way of checking would be to see what receive sensitivity you can 
get with a second link on another channel (try 1 & 7). To do this you 
will need a decent variable attenuator (again not cheap) and some RF 
pads. To do the test, measure the rx sensitivity by increasing the 
attenuation until this link stops working (don't forget about shielding) 
then repeat the test with the second link running at full power.

You will see that the sensitivity is around 80dBm at 11Mbit and higher 
at lower data rates. If the tx is splattering this will reduce to around 
40dBm or worse. Additionally the rx sensitivity on the high power link 
may also drop due to distortion in the amplifier.


Hope this helps

Dave



Michael Shuler wrote:

>Don't have one but would love to, can you recommend a brand/model?  Any
>idea how much it should cost?  Do you have a card that you recommend?
>
>Thanks!
>Mike
>
>-----Original Message-----
>From: Dave Edwards [mailto:Dave.Edwards at abicom-international.com] 
>Sent: Monday, December 09, 2002 11:17 AM
>To: Christian Zoffoli
>Cc: Michael Shuler; hostap at shmoo.com
>Subject: Re: Zcomax 200mw Card And Tx-Power
>
>
>[cut]
>
>Have you checked the output on a spectrum analyser? We have found that 
>the higher output on some radios can effectively splatter across the 
>whole 83MHz band, rendering it useless. Also this will "noise" can 
>reduce the range of the device significantly.
>
>Dave
>
>
>
>
>
>
>  
>






From czoffoli  Mon Dec  9 09:41:21 2002
From: czoffoli (Christian Zoffoli)
Date: Mon, 09 Dec 2002 18:41:21 +0100
Subject: Zcomax 200mw Card And Tx-Power
In-Reply-To: <3DF4D009.10902@abicom-international.com>
References: <006b01c29f9d$4fae2590$9600a8c0@oemcomputer> <3DF4CFB8.2050308@xmerlin.org> <3DF4D009.10902@abicom-international.com>
Message-ID: <3DF4D5C1.4030703@xmerlin.org>

Dave Edwards wrote:
> [cut]
> 
> Have you checked the output on a spectrum analyser?

yes

> We have found that 
> the higher output on some radios can effectively splatter across the 
> whole 83MHz band, rendering it useless.

i have found that the output could be large ~ 100Mhz ...you have to
watch the s/n ratio at 23dbm the cards works well with a good sepatation
between noise and "the good" signal. Nevertheless, IMHO, a good filter
at the output is a good practice (in particular if you plan to branch
many channels on a single antenna).


Regards,
Christian








From jt  Mon Dec  9 10:37:35 2002
From: jt (Jean Tourrilhes)
Date: Mon, 9 Dec 2002 10:37:35 -0800
Subject: [PATCH] : Scan in master mode
In-Reply-To: <20021208042012.GA3742@jm.kir.nu>
References: <20021206024056.GA2255@bougret.hpl.hp.com> <20021208042012.GA3742@jm.kir.nu>
Message-ID: <20021209183734.GC28084@bougret.hpl.hp.com>

On Sat, Dec 07, 2002 at 08:20:12PM -0800, Jouni Malinen wrote:
> On Thu, Dec 05, 2002 at 06:40:56PM -0800, Jean Tourrilhes wrote:
> 
> > 	As part of WE-16, I'm improving the iwspy support. HostAP is
> > currently problematic as I want to "reclaim" the SIOCGIWSPY call, and
> > HostAP currently uses it.
> 
> Hmm.. If I understood your design correctly, iwspy ioctl's were from
> driver code to main kernel. That is fine for me. It will make the driver
> code a bit more complex with all those conditional #if blocks for
> different wireless extension versions since I'm going to keep supporting
> the older versions, but I think I can manage with it.

	The patch listed on my web page does it with minimal
fuss. Actually, I was impressed by how small it was. Notice that for
WE < 16, it uses the old iwspy support.
	If you look carefully, I don't really "reclaim" the ioctl, and
it's as usual up to the driver if it wants to use the new scheme or
not.

> > 	So, I've decided 2 things :
> > 	1) I've un-deprecated SIOCGIWAPLIST and broaden its
> > definition. You can now return any list of address you want, not only
> > APs, and will remain supported.
> 
> 'iwlist wlan0 ap' shows "Access Point in range".. Will this also change
> to show something else? And will there be some kind of flag that will
> differentiate APs from associated stations?

	New wtools (24-pre4) shows : "Peers/Access Points in range".
	There won't be any flags. Well, there can't be
miracles. Anything I would add would be WE-16 and later, so would not
help those older versions of WE, and starting with WE-14 we have
scanning support that has all the flags we need (cf. patch we are
talking about).
	In fact, if you look at the current output of iwspy with
HostAP, you have all stations and APs together without any flag. My
idea was only to move this info from iwspy to aplist.
	But as you have seen, I didn't implement it in my HostAP
patch. It's because I don't know which is most important, getting only
APs or getting all stations and APs.

> > 	2) I've made the little patch below (for 2002-10-12) and I'm
> > suggesting its inclusion in HostAP. The patch was *very* quickly
> > tested.
> 
> Merged into Host AP CVS with couple of minor changes due to differences
> between 2002-10-12 release and CVS head.

	Ok.

> > 	Jouni, any comments ?
> 
> Above comments were about this patch and I already replied to your
> private message about WE-16 in a separate email.

	I'll update with your comments and re-spin.

> Jouni Malinen                                            PGP id EFC895FA

	Have fun...

	Jean



From linux  Mon Dec  9 10:47:25 2002
From: linux (Linux Rocks!)
Date: Mon, 9 Dec 2002 10:47:25 -0800
Subject: no luck in linux... works in windows.... help!
In-Reply-To: <3DF4C1B4.40604@liwest.at>
References: <200212081505.26412.linux@rocksolidnetworks.com> <3DF4C1B4.40604@liwest.at>
Message-ID: <200212091047.25386.linux@rocksolidnetworks.com>

Martin/all
Andrew mailed me and informed me of that... I should have posted that to the 
list. It seems kinda goofy that the windows client used any, when its a 
reserved word... Ive changd that.... Im still working on getting things going 
properly. Ive done some extensive testing with the orinoco_cs module too... 
but its not quite right yet...

Jamie

On Monday 09 December 2002 08:15 am, Martin Polak wrote:
: Linux Rocks! schrieb:
: > Let me preface this with an  apology for such a long  message.. I really
: > dont know what Info I need to include....Im sorry its soooo long.
: >
: > I need some help figureing out what Im doing right, and what Im doing
: > wrong, so I can make an AP. I am using a proxim rangelan-ds pcmcia card
: > (using the hostap_cs module). I think Its loading w/out errors Im loading
: > the module (I made an entry in hostap_cs.conf with my manfif, and am
: > using the following options:
: > module "hostap_cs" opts "channel=11 iw_mode=3 edssid=any
: > ignore_cis_vcc=1" Im using the ignore vcc option because it fails to load
: > w/out it (i guess this is a voltage issue..)
: > Im  using the essid "any" because thats what the windows software uses as
: > the default id.
: > iwmode=3 is master
:
: Ok, i thinks that is your Problem. If you configure your card as master,
: it acts as an AP and that is what you want. ESSID "ANY" is a special
: Wildcard for clients to register with Masters of differnet Essids and
: therefore doesnt make much sense (or even is not allowed) to set it on
: an Accesspoint.
: So try to set ESSID to something different and your clients to managed
: mode (they can use ANY if you want)
:
: Martin

-- 
No microsoft products were used to produce this message.
EUG-LUG Mailing List:
http://mailman.efn.org/cgi-bin/listinfo/eug-lug




From linux  Mon Dec  9 11:03:34 2002
From: linux (Linux Rocks!)
Date: Mon, 9 Dec 2002 11:03:34 -0800
Subject: Ethernet Conversion?
Message-ID: <200212091103.34455.linux@rocksolidnetworks.com>

I have a question about the windows software settings. 
What is Ethernet Conversion? I have 3 options there... 802.1h, RFC1042, 
Encapsulated. could someone explain what they are/mean? 

Jamie

-- 
No microsoft products were used to produce this message.
EUG-LUG Mailing List:
http://mailman.efn.org/cgi-bin/listinfo/eug-lug




From linux  Mon Dec  9 11:40:21 2002
From: linux (Linux Rocks!)
Date: Mon, 9 Dec 2002 11:40:21 -0800
Subject: Ethernet Conversion?
In-Reply-To: <200212091103.34455.linux@rocksolidnetworks.com>
References: <200212091103.34455.linux@rocksolidnetworks.com>
Message-ID: <200212091140.22012.linux@rocksolidnetworks.com>

Ive answered my own question... This page explains it:
http://www.unex.com.tw/Support/FAQ/Wireless/faq9.html

Jamie


On Monday 09 December 2002 11:03 am, Linux Rocks! wrote:
: I have a question about the windows software settings.
: What is Ethernet Conversion? I have 3 options there... 802.1h, RFC1042,
: Encapsulated. could someone explain what they are/mean?
:
: Jamie

-- 
No microsoft products were used to produce this message.
EUG-LUG Mailing List:
http://mailman.efn.org/cgi-bin/listinfo/eug-lug




From bapper  Mon Dec  9 13:05:34 2002
From: bapper (Brian Pomerantz)
Date: Mon, 9 Dec 2002 13:05:34 -0800
Subject: 802.1x with WinXP
In-Reply-To: <20021209043348.GA5225@jm.kir.nu>
References: <courier.3DF06A02.00006393@softhome.net> <20021207032045.GA1263@jm.kir.nu> <20021207043109.GA29766@skull.piratehaven.org> <20021207044335.GA2048@jm.kir.nu> <20021209043348.GA5225@jm.kir.nu>
Message-ID: <20021209210534.GA6770@skull.piratehaven.org>

On Sun, Dec 08, 2002 at 08:33:48PM -0800, Jouni Malinen wrote:
> 
> I would really need to get more debug info out of the WinXP Supplicant,
> so if someone happens to have good contact info for Microsoft
> developers/support, please let me know. Should someone have (or can
> easily make) a frame dump (i.e., sniffed from the wireless media) of a
> successful 802.1x exchange using WinXP Supplicant and any .1x
> Authenticator/Auth Server, it might be useful in comparing what could go
> wrong. This dump would need to include WEP key exchange using EAPOL-Key
> frame.
> 

Okay, I got a couple of traces for you from Windows XP SP1 sessions.
One is from a Cisco Aironet 350 and the other is from our AP.  Both
had authentication successful and were passing encrypted packets
afterward.  The radius server in both cases is freeradius with all the
voodoo to get it to work with WinXP EAP/TLS.  The tarball of the
packets in Airopeek format (ethereal can read them) can be found at:

	http://piratehaven.org/~bapper/trace.tgz


BAPper



From proski  Mon Dec  9 14:00:14 2002
From: proski (Pavel Roskin)
Date: Mon, 9 Dec 2002 17:00:14 -0500 (EST)
Subject: [PATCH] Compile problem with WE 14
Message-ID: <Pine.LNX.4.50.0212091657050.31474-100000@marabou.research.att.com>

Hello!

The CVS version of HostAP doesn't compile with Wireless Extesions 14
(Linux 2.4.20).  IWEVCUSTOM is defined starting with WE 15.

Patch:
=========================================
--- driver/modules/hostap_ap.c
+++ driver/modules/hostap_ap.c
@@ -2372,7 +2372,7 @@ static int prism2_ap_translate_scan(stru
 	struct iw_event iwe;
 	char *current_ev = buffer;
 	char *end_buf = buffer + IW_SCAN_MAX_DATA;
-#ifndef PRISM2_HOSTAPD
+#if !defined(PRISM2_HOSTAPD) && (WIRELESS_EXT > 14)
 	char buf[64];
 #endif

@@ -2453,6 +2453,7 @@ static int prism2_ap_translate_scan(stru
 					IW_EV_FREQ_LEN);
 			}

+#if WIRELESS_EXT > 14
 			memset(&iwe, 0, sizeof(iwe));
 			iwe.cmd = IWEVCUSTOM;
 			sprintf(buf, "beacon_interval=%d",
@@ -2460,6 +2461,7 @@ static int prism2_ap_translate_scan(stru
 			iwe.u.data.length = strlen(buf);
 			current_ev = iwe_stream_add_point(current_ev, end_buf,
 							  &iwe, buf);
+#endif /* WIRELESS_EXT > 14 */
 		}
 #endif /* PRISM2_HOSTAPD */

=========================================

-- 
Regards,
Pavel Roskin



From hazard  Mon Dec  9 14:02:21 2002
From: hazard (Vladimir Ivaschenko)
Date: Tue, 10 Dec 2002 00:02:21 +0200
Subject: Zcomax 200mw Card And Tx-Power
In-Reply-To: <006b01c29f9d$4fae2590$9600a8c0@oemcomputer>
References: <006b01c29f9d$4fae2590$9600a8c0@oemcomputer>
Message-ID: <20021210000221.A6735@hzdhome.home.blkseanet.ru>

>From what I know Zcomax use their own amplifier design and its output
power cannot be changed via standard Manual TxPwr setting. Also it does
not report current power correctly as well.

>From what I remember when you change the power manually the driver starts
to report the power you have set instead of getting it from the card which
would explain why iwconfig says that you have 23db power.

Mon, Dec 09, 2002 at 10:09:03AM -0600 Michael Shuler wrote about Zcomax 200mw Card And Tx-Power
> Earlier in the mailing list I noticed an email about Tx-Power capping.
> Essentially it said (if I understood it correctly) that the power will
> always be capped at 20db.  However Zcomax now makes a 200mw (23db) card.
> I'm using 'iwconfig wlan0 tx-power 23' and it seems to work, i.e. I type
> 'iwconfig' and it shows 23db power...but I guess based off the previous
> email in the mailing list, is it actually setting it to 23db or is it
> capping it at 20db?
> 
> Also I have noticed when inserting a card and putting it into 'Master'
> mode the tx-power seems to take on a random power level...is this a bug
> in hostap/wireless tools or something wrong with the Zcomax?
> 
> Thanks,
> Mike
> 
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

-- 
Best Regards
Vladimir Ivaschenko
http://www.hazard.maks.net/



From adaniels  Mon Dec  9 14:58:15 2002
From: adaniels (Aaron Daniels)
Date: Tue, 10 Dec 2002 09:58:15 +1100
Subject: wlan0 Interface seems to freeze.
In-Reply-To: <20021209093051.GE488@del.bg>
References: <20021203021259.3053bdfe.lists@chincogan.net.au>
	<20021209093051.GE488@del.bg>
Message-ID: <20021210095815.3dff38c0.adaniels@chincogan.net.au>

The DWL-520 has not skipped a beat since it was installed a week ago.

Thanks,
Aaron Daniels
Chincogan Network Services


On Mon, 9 Dec 2002 11:30:51 +0200
Theodor Milkov <zimage at del.bg> wrote:

> On Tue, Dec 03, 2002 at 02:12:59AM +1100, Chincogan Network Services Lists wrote:
> > Hi List,
> > 
> > I have a problem where my wlan0 interface seems to freeze, a dmesg shows pages and pages of this:
> > wlan0: prism2_tx: hw not ready - skipping
> > wlan0: prism2_tx: hw not ready - skipping
> > 
> > Doing a "iwpriv wlan0 reset 1" does nothing, to fix this I have to restart pcmcia. Sometimes this problem will leave us for a couple of days other times this will happen multiple times a day.
> > 
> > This afternoon I am going to change this card with a Dlink DWL-520 to see if that makes any difference.
> > 
> > My Setup:
> > Hostap 2002-10-12
> > Kernel 2.4.19
> > Pcmcia_cs 3.2.1
> > Compaq WL-200
> > 
> > Once I change the card I will not be using pcmcis_cs anymore as the DWL-520 is a PCI based prism 2.5 chipset.
> > Does anyone have any ideas why this could be happening? I hope it goes away with the new card because it is really starting to get annoying.
> 
> Just to confirm the same problem here. My setup is very similar to
> yours:
> 
> hostap 2002-10-12
> kernel 2.4.18
> pcmcia-cs 3.2.1
> Compaq WL-200 (STA 1.4.9)
> 
> Ricoh PCI-PCMCIA adapter + Senao 2511 (STA 1.4.9) instead of WL-200
> works just fine for weeks. So it must be something with WL-200s.
> 
> Kindest regards,
> 
> -- 
>         Theodor Milkov        Network Administrator
>         Davidov Net           Phone: +359 (2) 730158
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 



From jkmaline  Mon Dec  9 19:07:23 2002
From: jkmaline (Jouni Malinen)
Date: Mon, 9 Dec 2002 19:07:23 -0800
Subject: HostAP IEEE 802.1x modifications
In-Reply-To: <3DF4AA7F.10601@resonext.com>
References: <200211131843.20247.oleg.izhvanov@resonext.com> <20021209041740.GA5108@jm.kir.nu> <3DF4AA7F.10601@resonext.com>
Message-ID: <20021210030723.GA1991@jm.kir.nu>

On Mon, Dec 09, 2002 at 11:36:47AM -0300, Oleg Izhvanov wrote:

> Setting this bit was the workaround for WLAN card, that is yet being 
> developed, not
> for XP supplicant.  Setting this bit  is a directive for XP supplicant 
> to set the default key
> (not the unicast one, but one with indexes from 1 to 4) active. 

Actually, now that I got EAPOL-Keys working again with WinXP (see
below), that workaround was needed when only broadcast key is used. If
also individual unicast keys were sent, the workaround was not needed.
WinXP Supplicant reported this as "EAPOL-Key for transmit key *NOT*
received within 5 seconds in AUTHENTICATED state".

> There is a way to enable debugging messages in WinXP for EAPOL
> related stuff. Just look into following entry in your registry :
> 
> \\HKEY_LOCAL_MACHINE\Microsoft\Tracing\EAPOL

Thank you! This (or actually, the fixed address in the next message)
proved to be very helpful. I did search for 'eap' from the registry,
but there was so many matches that I must have missed this.


I finally got dynamic WEP keying working again with WinXP Supplicant.
Actually, it should have worked fine before, if I just would have tested
by sending both broadcast and unicast keys (I used only broadcast)..
IEEE 802.1aa/D4 update changed the order of EAP Success and EAPOL-Key
frames (key was now sent first). This seemed to break operation with
WinXP Supplicant (which seems to derive MPPE-Send/Recv-Keys only after
receiving EAP Success).

EAPOL tracing was helpful enough to tell me that EAPOL-Key decryption
failed, so I just reverted the change in EAPOL state machine (EAP
Success is sent first) and WinXP managed to decrypt keys yet again.
After this, I hit the problem that WinXP Supplicant claimed that it did
not receive EAPOL-Key for transmit key within 5 seconds.

I have interpreted standard so that the broadcast key would be used for
transmit if there is no individual unicast key. WinXP Supplicant does
not seem to agree with this. So, the '-w' workaround for hostapd can be
used to set unicast bit for the broadcast key to get this working. When
both broadcast (-b5) and unicast (-i5) keys are set, this workaround is
not needed.

Current CVS version of hostapd should now be able to work fine with
WinXP Supplicant. I have tested it with Lucent card and dynamic WEP key
setting for both broadcast and individual keys worked fine. In addition,
rekeying both keys was also working.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Dec  9 19:18:40 2002
From: jkmaline (Jouni Malinen)
Date: Mon, 9 Dec 2002 19:18:40 -0800
Subject: [PATCH] Compile problem with WE 14
In-Reply-To: <Pine.LNX.4.50.0212091657050.31474-100000@marabou.research.att.com>
References: <Pine.LNX.4.50.0212091657050.31474-100000@marabou.research.att.com>
Message-ID: <20021210031840.GA2129@jm.kir.nu>

On Mon, Dec 09, 2002 at 05:00:14PM -0500, Pavel Roskin wrote:

> The CVS version of HostAP doesn't compile with Wireless Extesions 14
> (Linux 2.4.20).  IWEVCUSTOM is defined starting with WE 15.

Thanks, applied. I have been working mostly with PRISM2_HOSTAPD defined
and when testing this, I used WE 15.. By the way, number of backward
compatibility blocks for various wireless extensions versions is
starting to get huge (about 50 or so). Those are making the code less
readable, so there might be some need for cleanup eventually.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Dec  9 19:21:12 2002
From: jkmaline (Jouni Malinen)
Date: Mon, 9 Dec 2002 19:21:12 -0800
Subject: 802.1x with WinXP
In-Reply-To: <20021209210534.GA6770@skull.piratehaven.org>
References: <courier.3DF06A02.00006393@softhome.net> <20021207032045.GA1263@jm.kir.nu> <20021207043109.GA29766@skull.piratehaven.org> <20021207044335.GA2048@jm.kir.nu> <20021209043348.GA5225@jm.kir.nu> <20021209210534.GA6770@skull.piratehaven.org>
Message-ID: <20021210032112.GB2129@jm.kir.nu>

On Mon, Dec 09, 2002 at 01:05:34PM -0800, Brian Pomerantz wrote:

> Okay, I got a couple of traces for you from Windows XP SP1 sessions.
> One is from a Cisco Aironet 350 and the other is from our AP.  Both
> had authentication successful and were passing encrypted packets
> afterward.

Thanks! Both of these were sending EAPOL-Key packets after EAP Success
and in addition, both cases included unicast WEP key.. With these
changed, hostapd is now working with my WinXP setup.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jt  Mon Dec  9 19:47:10 2002
From: jt (Jean Tourrilhes)
Date: Mon, 9 Dec 2002 19:47:10 -0800
Subject: [PATCH] Compile problem with WE 14
Message-ID: <20021210034710.GA31894@bougret.hpl.hp.com>

Jouni Malinen wrote :
> On Mon, Dec 09, 2002 at 05:00:14PM -0500, Pavel Roskin wrote:
> 
> > The CVS version of HostAP doesn't compile with Wireless Extesions 14
> > (Linux 2.4.20).  IWEVCUSTOM is defined starting with WE 15.

	Thanks for the good work, as usual...
	Note that there is another way to fix this one :
-----------------------------
#ifndef IWEVCUSTOM
#define IWEVCUSTOM	0x8C02		/* Driver specific ascii string */
#endif
-----------------------------

> Thanks, applied. I have been working mostly with PRISM2_HOSTAPD defined
> and when testing this, I used WE 15.. By the way, number of backward
> compatibility blocks for various wireless extensions versions is
> starting to get huge (about 50 or so). Those are making the code less
> readable, so there might be some need for cleanup eventually.

	Well... I wish I could have got it right at the first
iteration in 96, this would have simplified the situation
drastically. Unfortunately, I'm only a common mortal.
	Remember that some of those feature I'm adding to Wireless
Extension are stuff you guys are asking for. And I try to make sure
that new feature that you don't need or don't like don't get in your
way.

	There is a few options :
	1) Don't use W-Ext at all, and have your own set of tools
strongly linked with the driver, like linux-wlan-ng, or use a /proc
interface, like airo.c.
	2) Assume only a baseline WE (like WE-9), and ignore all
functionality added after that. Refer to #1 for additional config.
	3) Assume the lastest WE, and generate a compilation error for
earlier WE, point to my web pages for necessary WE patches.
	4) #if WIRELESS_EXT of all the features needed, which is the
current solution.
	5) Mix 2/3/4 too make the conditional blocks less
granular. For example, you could decide to use scanning only after
WE-15 (and not on WE-14), or not use IWEVCUSTOM at all.
	6) Include driver in the kernel, and use whatever WE version
is in that kernel.

	I would quickly point out that most Linux APIs are using
solution #6 and it's having drivers out of the kernel that make things
difficult. Don't take my word for it, just check
driver/modules/hostap_compat.h and
pcmcia-cs-XXX/include/linux/netdevice.h for example.
	Also, in most case you may migrate the "conditionality" to the
header file (the solution above), but this will result in bloat in the
driver.

	But, if anybody has any brilliant idea, please tell me...

	Good luck...

	Jean



From jkmaline  Mon Dec  9 20:22:43 2002
From: jkmaline (Jouni Malinen)
Date: Mon, 9 Dec 2002 20:22:43 -0800
Subject: [PATCH] Compile problem with WE 14
In-Reply-To: <20021210034710.GA31894@bougret.hpl.hp.com>
References: <20021210034710.GA31894@bougret.hpl.hp.com>
Message-ID: <20021210042243.GA3107@jm.kir.nu>

On Mon, Dec 09, 2002 at 07:47:10PM -0800, Jean Tourrilhes wrote:

> 	Note that there is another way to fix this one :
> #ifndef IWEVCUSTOM
> #define IWEVCUSTOM	0x8C02		/* Driver specific ascii string */
> #endif

Thanks, that is actually lot nicer since it can be hidden in some
compatibility header file..

> 	Remember that some of those feature I'm adding to Wireless
> Extension are stuff you guys are asking for. And I try to make sure
> that new feature that you don't need or don't like don't get in your
> way.

Yes and I appreciate this a lot.

> 	There is a few options :
> 	1) Don't use W-Ext at all, and have your own set of tools
> strongly linked with the driver, like linux-wlan-ng, or use a /proc
> interface, like airo.c.

I don't even consider that to be an option ;-). Having a common user
space API for most drivers is certainly very useful. I have to admit
that hostapd is using couple of own ioctl()'s and so is individual
WEP key configuration, but these are (at least for now) specific to
Host AP driver.

> 	2) Assume only a baseline WE (like WE-9), and ignore all
> functionality added after that. Refer to #1 for additional config.
> 	3) Assume the lastest WE, and generate a compilation error for
> earlier WE, point to my web pages for necessary WE patches.
> 	4) #if WIRELESS_EXT of all the features needed, which is the
> current solution.
> 	5) Mix 2/3/4 too make the conditional blocks less
> granular. For example, you could decide to use scanning only after
> WE-15 (and not on WE-14), or not use IWEVCUSTOM at all.

I don't wish to break compilation or ignore all new WE features. Some
sort of mix is probably the way to go with Host AP driver, but I might
change the support to be a bit less generic. I have already dropped
done some limitations (like requiring WE 9 for some code that would
actually work even with WE 8). Maybe a good selection would be to
support latest 2.2 kernel, latest two version from 2.4 (i.e., current
stable kernel), and latest version of 2.5 (i.e., current devel kernel).
This would at least limit the number of different versions to 4 (9, 13,
14, and 15 at the moment).

> 	6) Include driver in the kernel, and use whatever WE version
> is in that kernel.

That would make the code more readable, but I would prefer to maintain
one version of the driver, that would work at least with two latest
stable kernel trees (2.2 and 2.4) and latest devel tree (2.5)..

> 	Also, in most case you may migrate the "conditionality" to the
> header file (the solution above), but this will result in bloat in the
> driver.

This makes it easier to maintain the code, so I would prefer to do this.
In some cases it has just been easier to add new ifdef block, but I
should probably go through these once and check what could be removed.

-- 
Jouni Malinen                                            PGP id EFC895FA



From proski  Mon Dec  9 23:29:35 2002
From: proski (Pavel Roskin)
Date: Tue, 10 Dec 2002 02:29:35 -0500 (EST)
Subject: [PATCH] Compile problem with WE 14
In-Reply-To: <20021210034710.GA31894@bougret.hpl.hp.com>
Message-ID: <Pine.LNX.4.44.0212100123570.2364-100000@localhost.localdomain>

Hello, Jean!

> 	Thanks for the good work, as usual...
> 	Note that there is another way to fix this one :
> -----------------------------
> #ifndef IWEVCUSTOM
> #define IWEVCUSTOM	0x8C02		/* Driver specific ascii string */
> #endif

I considered this possibility but decided not to use the constant that is
not supported to be on the safe side and to be consistent with the
approach that I don't really like.

If it just a number that wasn't allocated in WE 14, then it's OK to use.  
If there is something in the WE code that needs to support this function,
then it's a very different situation.

If you allocate new numbers in the next version on Wireless Extensions,
it's unreasonable to forbid newer drivers to use those numbers and provide
compatibility includes.  It's somewhat like forbidding to port a driver to
2.2 kernel because the major number for that driver wasn't allocated in
2.2 series.

I believe it's only reasonable to limit functionality of the driver if
that functionality relies on the actual code in the kernel, not on
_conventions_ that were in effect when the kernel code was written, if
they are not used in the code.

> 	Well... I wish I could have got it right at the first iteration in
> 96, this would have simplified the situation drastically. Unfortunately,
> I'm only a common mortal.

Not so common actually :-)

> 	Remember that some of those feature I'm adding to Wireless
> Extension are stuff you guys are asking for. And I try to make sure that
> new feature that you don't need or don't like don't get in your way.

And by the way, backward compatibility is a very hard thing to do right
even without those pesky guys :-)

> 	There is a few options :
> 	1) Don't use W-Ext at all, and have your own set of tools strongly
> linked with the driver, like linux-wlan-ng, or use a /proc interface,
> like airo.c.

Not an option.  Poor WE support is the reason why I'm using linux-wlan-ng
only if I absolutely have to, namely on cards with tertiary firmware and
to use prism2dl for firmware upgrade.

> 	2) Assume only a baseline WE (like WE-9), and ignore all
> functionality added after that. Refer to #1 for additional config.

That would be a step back.  Standardization is a good thing.

> 	3) Assume the lastest WE, and generate a compilation error for
> earlier WE, point to my web pages for necessary WE patches.

It's acceptable, but inconvenient and not quite compatible with 6.

> 	4) #if WIRELESS_EXT of all the features needed, which is the
> current solution.

Acceptable, but see below.

> 	5) Mix 2/3/4 too make the conditional blocks less granular. For
> example, you could decide to use scanning only after WE-15 (and not on
> WE-14), or not use IWEVCUSTOM at all.

This doesn't benefit the users.  Dropping functionality to simplify code
is not justified except some very specific cases, e.g. support for very
old code.  Dropping scanning support with the stock 2.4.20 kernel would be
outrageous.

> 	6) Include driver in the kernel, and use whatever WE version is in
> that kernel.

Acceptable, but not necessary.

7) Split wireless.h into 2 headers.  The API part should be versioned.  
The constant part should not be versioned, but instead should be backward
compatible.  New constants could be added, but removal of the old
constants would not be allowed.

> 	I would quickly point out that most Linux APIs are using solution
> #6 and it's having drivers out of the kernel that make things difficult.
> Don't take my word for it, just check driver/modules/hostap_compat.h and
> pcmcia-cs-XXX/include/linux/netdevice.h for example.

Yes, there is some similarity.  But I think there is another thing that 
makes things difficult - it's the number of user-configurable parameters 
and complexity of the protocol.  mii-tool is simpler that iwconfig.

> 	But, if anybody has any brilliant idea, please tell me...

Maybe not brilliant, but hopefully not stupid to be completely ignored :-)

-- 
Regards,
Pavel Roskin




From marcb  Tue Dec 10 02:32:58 2002
From: marcb (Marc Brady)
Date: Tue, 10 Dec 2002 21:32:58 +1100
Subject: 802.1x with WinXP
In-Reply-To: <20021209143301.47040.23610.Mailman@sisyphus.iocaine.com>
Message-ID: <000001c2a037$995b0600$0a01010a@kaoticinnovations.com.au>

> Thanks! Both of these were sending EAPOL-Key packets after EAP Success
> and in addition, both cases included unicast WEP key.. With these
> changed, hostapd is now working with my WinXP setup.
> 
> -- 
> Jouni Malinen                                            PGP id
EFC895FA

Thanks Jouni and Brian for your help,
802.1x with WinXP SP1 works beautifully now!!





From ian.cass  Tue Dec 10 03:34:48 2002
From: ian.cass (Ian Cass)
Date: Tue, 10 Dec 2002 11:34:48 -0000
Subject: Zcomax 200mw Card And Tx-Power
References: <006b01c29f9d$4fae2590$9600a8c0@oemcomputer> <20021210000221.A6735@hzdhome.home.blkseanet.ru>
Message-ID: <04df01c2a040$2587c0c0$4c28a8c0@cblan.mblox.com>

> From what I know Zcomax use their own amplifier design and its output
> power cannot be changed via standard Manual TxPwr setting. Also it does
> not report current power correctly as well.

Apologies for hijacking this thread somewhat, but can anyone confirm whether
these Zcomax cards support 'ansel' and if so, what settings relate to which
socket?

--
Ian Cass




From bigbloke  Tue Dec 10 04:12:04 2002
From: bigbloke (Big Bloke)
Date: Tue, 10 Dec 2002 12:12:04 +0000 (UTC)
Subject: HostAP digest, Vol 1 #61 - 14 msgs
In-Reply-To: <20021209220501.77026.21517.Mailman@sisyphus.iocaine.com>
Message-ID: <Pine.NEB.4.44.0212101131350.25629-100000@droog>

On Mon, 9 Dec 2002 hostap-request at shmoo.com wrote:

Mike Wrote.

> I'm trying to understand how the tx/rx diversity works if anyone would
> be kind enough to enlighten me about their experiences I would really
> appreciate it.

Hi Mike,

as far as I know, (If I am wrong someone please correct me) TX diversity
is not used in WLAN.

The idea of RX diversity is to combat "Phasing" . If you have ever
listened to FM car radio under weak signal conditions you may have heard
"flutter" on the signal. Diversity is a method of countering
that effect.

When signals arrive at the receive antenna, they may do so from a
number of directions, either direct from the transmitter, or via
some object that has reflected the signal. If the signals arrive
together "In time" (i.e. in phase) then the two will add together
to produce a larger version of the original signal (additive mixing)
,if they arrive at different times, there is a chance that one of
the Signals will reduce the other (known as "subtractive mixing" )
and the resulting signal may be considerably weaker.

The two receive antennas are spaced a critical distance (a number
of wavelengths) apart in such a position, that if a signal is out
of phase with the one antenna, it should be in phase with the other.

Given that one wavelength is around 13cms then the spacing is quite
critical!

The Diversity circuit of the receiver will compare the phase difference
of the two received signals, delay the more advanced of the two so that
it is phased up with the other signal, then combine them together to
produce one composite stronger signal, which can be de-modulated more
effectively.

This technique has been used in the cellphone industry for around 20+
years.

IIRC, in a typical 2 antenna Access point setup, one antenna is both
TX and RX whereas the other is RX diversity only.

> Here is what I have tried so far:
> 1 -> Installed 2 Maxrad 10db omni's on standoff arms at about the top of
> a 100ft tower spaced 15ft apart horizontally, ran 2 separate Andrew's
> 1/2" Andrews Heliax cables to each antenna.

WOW! Serious setup ;-))

I thought my Homebrewed 28 Element omni into about 20 foot of LDF 5-50
was "Going some! " , But.... sheesh !!!  ;-)

The spacing of the two antennas is quite critical, as is the feeder
Length , which IIRC needs to be identical for the two antennas.
Also, considering the small power levels in use the
feeder length is rather long even for LDF/FSJ-450.

I calculate you would be losing 5.4 db Minimum climbing that 100Ft
Tower ! and 3db represents a 50% reduction in that signal level.
Is there anyway you could site the AP at the top of the tower and
just run Ethernet up to it ? There is commercial equipment available
to provide DC power for the AP over the Ethernet cable and the increase
in performance should be significant with only a few feet of heliax
between the AP and the Antennas.

<Snipped> !!

I'm not "quite" sure what you want to achieve with sectorising, I am
considering an OTSR solution (Omni Transmit, Sectored Receive) by
hacking into the WLAN card. to boost the "uplink" from the client cards.
as an alternative.

You might like to look at www.wimo.de who produce very good quality
"Power Splitters" for 2.4GHz that could be used for sectoring.

Any other questions, by all means mail me directly.

cheers

B B





From Dave.Edwards  Tue Dec 10 05:43:29 2002
From: Dave.Edwards (Dave Edwards)
Date: Tue, 10 Dec 2002 13:43:29 +0000
Subject: HostAP digest, Vol 1 #61 - 14 msgs
References: <Pine.NEB.4.44.0212101131350.25629-100000@droog>
Message-ID: <3DF5EF81.7050701@abicom-international.com>

Mike, BB,

<cut>

The Diversity circuit of the receiver will compare the phase difference
of the two received signals, delay the more advanced of the two so that
it is phased up with the other signal, then combine them together to
produce one composite stronger signal, which can be de-modulated more
effectively.

This technique has been used in the cellphone industry for around 20+
years.

<cut>

If you are using an intersil based radio (i.e. Prism 2/2.5) then antenna 
diversity is rather limited. This is because the radio only has a single 
RX channel and a switch to select the receive antenna. Due to this, the 
device can only listen on one port at a time and so mixing the received 
signals is not possible.

The Prism Baseband chip makes it's decision about antenna diversity by 
sampling the received signal on each of the antenna ports during the 
synchronization portion of the RF transmission. This is one of the 
reasons for having a preamble on the radio. Once the BB chip has 
selected a port it will then stick with it until the end of the reception.

Hope this clarifies things

Dave





From li9  Tue Dec 10 07:48:45 2002
From: li9 (Min Li)
Date: Tue, 10 Dec 2002 10:48:45 -0500 (EST)
Subject: 2002-10-12 monitor mode
In-Reply-To: <Pine.NEB.4.44.0212101131350.25629-100000@droog>
Message-ID: <Pine.GSO.4.44.0212101046580.15962-100000@expert.ics.purdue.edu>

Hi all,


>From the mailing list archive, I found that Jouni Malinen's reply about
the bug in exisiting 2002-10-12 version for monitor mode configuration. Is
there any way to fix the bug right now? Thanks

Min






From li9  Tue Dec 10 08:01:40 2002
From: li9 (Min Li)
Date: Tue, 10 Dec 2002 11:01:40 -0500 (EST)
Subject: 2002-10-12 monitor mode
In-Reply-To: <Pine.GSO.4.44.0212101046580.15962-100000@expert.ics.purdue.edu>
Message-ID: <Pine.GSO.4.44.0212101059520.15962-100000@expert.ics.purdue.edu>

Also, the tar ball downloaded from the CVS repository, is it compatible
with redhat 8.0? It is not compilable right away. thanks.



> Hi all,
>
>
> >From the mailing list archive, I found that Jouni Malinen's reply about
> the bug in exisiting 2002-10-12 version for monitor mode configuration. Is
> there any way to fix the bug right now? Thanks
>
> Min
>
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From BichotG  Tue Dec 10 08:57:48 2002
From: BichotG (Bichot Guillaume Princeton)
Date: Tue, 10 Dec 2002 11:57:48 -0500
Subject: 2002-10-12 monitor mode
Message-ID: <FB52B3CCAE26D41181E800508B6D91EB02AFD775@INDYEXCH23>

I guess the only mentionned problem I'm aware was about the method to set-up
the monitor mode: the deprecated method (iwpriv) has a bug. 

However,
I found that some time, switching to the monitor mode, the incoming frames
are wrong. I mean running wlansniff I found that there is a shift in the
data packet delivered to the user space in such a way the wlansniff
misinterprets the header. Ethereal is also unable to interprets correctly
the frames as well. To solve the problem I have to switch back to the
managed mode and switch back to the monitor mode (need sometime several back
and forth until the things go right). I have to add that I use the monitor
mode with the frequency I want to listen (i.e. iwconfig wlan0 freq
"2.437ghz" mode "monitor").

I'm using the Linksys WPC 11 PCMCIA card (manfid 0x274, 0x1613).

Guillaume

> -----Original Message-----
> From: Min Li [mailto:li9 at expert.ics.purdue.edu] 
> Sent: Tuesday, December 10, 2002 10:49 AM
> Cc: hostap at shmoo.com
> Subject: 2002-10-12 monitor mode
> 
> 
> Hi all,
> 
> 
> From the mailing list archive, I found that Jouni Malinen's 
> reply about the bug in exisiting 2002-10-12 version for 
> monitor mode configuration. Is there any way to fix the bug 
> right now? Thanks
> 
> Min
> 
> 
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021210/ead30f78/attachment.htm 


From jt  Tue Dec 10 09:19:53 2002
From: jt (Jean Tourrilhes)
Date: Tue, 10 Dec 2002 09:19:53 -0800
Subject: [PATCH] Compile problem with WE 14
In-Reply-To: <Pine.LNX.4.44.0212100123570.2364-100000@localhost.localdomain>
References: <20021210034710.GA31894@bougret.hpl.hp.com> <Pine.LNX.4.44.0212100123570.2364-100000@localhost.localdomain>
Message-ID: <20021210171953.GB3505@bougret.hpl.hp.com>

On Tue, Dec 10, 2002 at 02:29:35AM -0500, Pavel Roskin wrote:
> Hello, Jean!
> 
> > 	Thanks for the good work, as usual...
> > 	Note that there is another way to fix this one :
> > -----------------------------
> > #ifndef IWEVCUSTOM
> > #define IWEVCUSTOM	0x8C02		/* Driver specific ascii string */
> > #endif
> 
> I considered this possibility but decided not to use the constant that is
> not supported to be on the safe side and to be consistent with the
> approach that I don't really like.
> 
> If it just a number that wasn't allocated in WE 14, then it's OK to use.  
> If there is something in the WE code that needs to support this function,
> then it's a very different situation.

	This number is unused in WE-14 and earlier and therefore safe
to use. The only thing is that the tools will drop it.
	If you want, I could use the same construct in the tools so
that IWEVCUSTOM would get supported also on WE-14. Actually, that's
probably a good idea, so I'll do it ;-)

> If you allocate new numbers in the next version on Wireless Extensions,
> it's unreasonable to forbid newer drivers to use those numbers and provide
> compatibility includes.  It's somewhat like forbidding to port a driver to
> 2.2 kernel because the major number for that driver wasn't allocated in
> 2.2 series.

	Exactly. I tend to always add numbers and not remove them. For
example, APLIST is supposed to be deprecated, but I've decided that
after all I'll keep it.

> 7) Split wireless.h into 2 headers.  The API part should be versioned.  
> The constant part should not be versioned, but instead should be backward
> compatible.  New constants could be added, but removal of the old
> constants would not be allowed.

	Well, actually wireless.h is versioned *and* backward
compatible. The only two time I've remove stuff was v8->v9 and the
SIOCSIWCOMMIT accident, but I've learned my lesson.

> > 	I would quickly point out that most Linux APIs are using solution
> > #6 and it's having drivers out of the kernel that make things difficult.
> > Don't take my word for it, just check driver/modules/hostap_compat.h and
> > pcmcia-cs-XXX/include/linux/netdevice.h for example.
> 
> Yes, there is some similarity.  But I think there is another thing that 
> makes things difficult - it's the number of user-configurable parameters 
> and complexity of the protocol.  mii-tool is simpler that iwconfig.

	A better example would have been the USB driver API. This one
has been a wild ride.

> Maybe not brilliant, but hopefully not stupid to be completely ignored :-)

	Thanks for the advices, I'll try to be even more careful on
those point and write those rules in stone. That's another reason why
I won't remove APLIST support.

> Regards,
> Pavel Roskin

	Have fun...

	Jean



From mike  Tue Dec 10 11:59:14 2002
From: mike (Michael Shuler)
Date: Tue, 10 Dec 2002 13:59:14 -0600
Subject: Disco Antenna
Message-ID: <001901c2a086$a069b820$9600a8c0@oemcomputer>

     Well it looks like the general consensus is that the Prism
implementation of antenna diversity isn't very useful.  So I am
proposing a different solution and want to see what other people think
of it.  I've had this idea for quite some time but haven't know quite
how to implement it, maybe someone else here could help?

     As a WISP covering many different cities/terrains we have seen all
kinds of weird interference issues.  Most of our problems DO NOT come
from other radio interference but rather completely unexplainable
interference.  Usually the unexplainable interference seems to come from
specific directions but for varying amounts of time.  The level of
interference seems to vary quite a bit too.  Other times it just seems
to go completely away for a while and nobody knows why, sometimes for
days at a time.  In every one of these situations we found that our
signal levels never dropped but only the noise level changed.  When the
noise floor would increase enough the connection would obviously break
or be impaired.  In a big city you would expect this type of behavior as
more and more WiFi devices get sold every day, but this is happening in
small towns (under 1000 population) too and it just doesn't add up.
I've noticed a general increase in all of my noise floors since about
the time XM Radio went live and from what I understand their frequency
is right next to the ISM band...but anyway where I was actually going
with this is that to improve performance (get a better SNR) we would
replace omni's with 3 120 degree sector panels and 3 radios (channels
1,6,11).  Not only would the signal levels get higher because of the
higher gains of the antennas but the noise floors would drop.  Obviously
since a single sector panel is only looking at 120 degrees of potential
interference its noise floor should improve...and it always did.  Taking
this concept even further we have a 500ft tower that we rent space on.
We ran CAT5e & 110 AC (Power over Ethernet wouldn't make it, but despite
the 100m limit for Ethernet data it runs without any line errors...go
figure) to the 400ft and 500ft levels.  At the 500ft level we put 3 60
degree vertically polarized sector panels and 3 radios (channels
1,6,11).  At 400ft we put 3 60 horizontally polarized sector panels and
3 radios (channels 1,6,11 again).  We also put an 8db omni at 400ft to
test the performance differences between sector panels and the omni.
The test proved exactly what we expected.  The noise floor on the omni
was considerably higher then each sector panel.  We were able to get
distances in excess of 50 miles (to a 250 water tower using a 24db grid
antenna) that actually would hold a pretty decent link.  The water tower
worked because it had pretty good Frenel Zone clearance but nothing else
lower would work that far out, pretty cool anyway.  The 3 panels that
covered the larger city (150,000 population) that was about 4 miles from
the tower massively out-performed the omni (obviously the signal levels
were higher due to the higher gain of the antennas but I'm mainly
referring to noise levels).  With the exception of thick trees and hills
we are able to hit about everything as long as we can get reasonable
line of site to the customer.

     Finally, here is where I'm going with all this :)  

     Since sectorizing to 60 degrees caused and even greater improvement
(many db reduction in noise floor) vs. 120 degrees and the added bonus
of increase antenna gain, then why not cut it down even further into
hundreds of sectors not only horizontally but vertically too?
Essentially creating an antenna that looks like a "Disco" mirror ball.  

Problem 1 - Only 3 non-overlapping frequencies and 2 available
polarizations....good luck finding an ISM circular sector panel.  Pretty
much maxes you out at 6 panels in *near* proximity of each other and
even then they still interfere just due to the RF leakage coming off the
PCMCIA cards alone.

Problem 2 - The 6 could be increased to 12 if diversity worked
right...looks like no luck there :)

Problem 3 - If the gain of your AP's antenna became too high in a multi
point situation would exceed the max EIRP allowed by the FCC



Looking for ideas from anyone out there but here are my ideas so far:

The Antenna (120 degree of coverage per panel):  
     The "Disco" antenna would consist of 16x16 evenly spaced antenna
elements in a 120x16 degree arc (the idea is to cover a total of 120
degrees since most towers have 3 faces to them).  I really don't know
much about antenna design so it may have to be flat instead of an arc.
I'm guessing that it will be about 1ft high and about 3ft wide.  I
picked 256 elements because my Soekris boards I use for our existing APs
have a general purpose 8 bit I/O port...although using a serial
interface would be better if anyone knows how to make a decoder.  Based
off the value of the I/O ports it would create a connection between the
radio cards and one of the elements using a simple set of logic gates.
I'm sure some all-in-one chip exists for this type of thing but I'm not
a hardware guy, any suggestions would help.

The Radios:
     3 Soekris boards with 3 radios each (2 PCMCIA and 1 Mini-PCI).
SENAO seems to make the best radio card for the buck...23db for
~$85/each.  They would be linked together via the second Ethernet ports
on a private subnet for driver communications.  The primary Ethernets
would be for actual data traffic.  Each radio would have an antenna lead
attached to its spot on the input to the gates.  ONLY ONE radio is for
transmitting, the remaining 8 all passively listen.  More about this in
the next section.

How it works:
     It's easiest to conceptualize if you think of the antenna as just a
big grid if smaller flat panel antennas that have a beam width of 7.5x1
degrees.  We will label the rows 1-16 and the columns A-P, you sunk my
battle ship :)  The 9 radios will attach to nine different antenna
elements simultaneously with only the center element actively
transmitting.  The surrounding 8 radios will be listening to determine
if their antenna element is better suited to transmit and receive on.
Here is an example of listening on C3:

P = Passively Monitor
* = Transmit/Receive
  = Unused at the moment

  A B C D E F G H I J K L M N O P
1
2   P P P
3   P * P
4   P P P
5
6
7
8
9
10
11
12
13
14
15
16


Only C3 is actually doing any real work.  The remaining 8 are only
watching signal levels.  I'm guessing that the passive radios should be
checked about 10 times per second or so but I think we are going to have
to just fiddle with it until a "magic number" is found.  When one of the
passive radios has a better receive SNR the whole set of radios will
move in that direction.  For example lets say that D4's SNR level is a
db higher, the driver would change the I/O pins to make the gates adjust
to the following:

P = Passivly Monitor
* = Transmit/Receive
  = Unused at the moment

  A B C D E F G H I J K L M N O P
1
2   
3     P P P
4     P * P
5     P P P
6
7
8
9
10
11
12
13
14
15
16

When the radio is not busy transmitting or receiving it can go into an
antenna scan mode where it is essentially sending out its usual beacons
or whatever else it has to do while being quickly moved throughout the
different elements of the antenna.  When one of the 9 radios picks up a
signal from one of the associated clients it will immediately return to
the last know position for that client and then adjust accordingly.
Whenever it has something to transmit to a client it will also return to
the last know position for that client.

Summary (finally):
	If all goes well this antenna should create a 7.5x1 degree beam
towards a client, which should keep the noise level low for everyone
else in the area and should have a much higher gain like 30db+radio
power.  On the receive side the noise level should be decreased
dramatically and since the panel is 3ftx1ft (guessing) it should have a
pretty good receive gain too, maybe 25-30db gain.  With all that it
sounds to me like this would solve everyone's interference issues and
would provide enough receive gain to get though some extra trees or
walls :)


Before I start to build this thing I wanted to get some feedback from
some other people who might have already tried this.

Mike





From schmidt  Tue Dec 10 14:29:07 2002
From: schmidt (Edson Roberto Schmidt)
Date: Tue, 10 Dec 2002 19:29:07 -0300
Subject: Linux 2.2
References: <04d801c29c74$840143d0$4c28a8c0@cblan.mblox.com>
Message-ID: <002c01c2a09b$8e073fd0$d23baec8@schmidt>

I'm currently using hostAP 2002-10-12 on Kernel 2.2.22, pcmcia-cs 3.2.3,
wireless tools 25  and all work fine.

schmidt
----- Original Message -----
From: "Ian Cass" <ian.cass at mblox.com>
To: <hostap at shmoo.com>
Sent: Thursday, December 05, 2002 12:39 PM
Subject: Linux 2.2


> Does HostAP work on older 2.2 series kernels and if so, what about
Wireless
> Extensions versions?
>
> --
> Ian Cass
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From schmidt  Tue Dec 10 14:40:30 2002
From: schmidt (Edson Roberto Schmidt)
Date: Tue, 10 Dec 2002 19:40:30 -0300
Subject: problems with EN2511CD / NL2511CD
References: <Pine.LNX.4.50.0212022152090.11195-100000@twinlark.arctic.org> <20021203062656.GA12480@jm.kir.nu> <Pine.LNX.4.50.0212022251260.11195-100000@twinlark.arctic.org>
Message-ID: <003801c2a09d$24d34390$d23baec8@schmidt>

I'm currently using an NL2511CD PLUX EXT2 and the only pri and sta that work
fine are 1.0.4 and 1.0.3.

Nov 30 15:35:17 ap_pico cardmgr[277]: socket 0: Senao
SL-2011CD/SL-2011CDPLUS
Nov 30 15:35:17 ap_pico cardmgr[277]: executing: 'modprobe hostap_cs'
Nov 30 15:35:18 ap_pico kernel: hostap_cs: hostap_cs.c 0.0.0 2002-10-12 (SSH
Communications Security Corp, Jouni Malinen)
Nov 30 15:35:18 ap_pico kernel: hostap_cs: (c) Jouni Malinen
<jkmaline at cc.hut.fi>
Nov 30 15:35:18 ap_pico kernel: cs: IO port probe 0x0100-0x04ff: excluding
0x4d0-0x4d7
Nov 30 15:35:18 ap_pico kernel: cs: IO port probe 0x04d8-0x04ff: clean.
Nov 30 15:35:18 ap_pico kernel: cs: IO port probe 0x0800-0x08ff: clean.
Nov 30 15:35:18 ap_pico kernel: cs: IO port probe 0x0a00-0x0aff: excluding
0xaf8-0xaff
Nov 30 15:35:18 ap_pico kernel: cs: IO port probe 0x0c00-0x0cff: excluding
0xcf8-0xcff
Nov 30 15:35:18 ap_pico kernel: hostap_cs: index 0x01: Vcc 3.3, irq 15, io
0x010 0-0x013f
Nov 30 15:35:18 ap_pico kernel: hostap_cs: Registered netdevice wlan0
Nov 30 15:35:18 ap_pico kernel: wlan0: NIC: id=0x800c v1.0.0
Nov 30 15:35:18 ap_pico kernel: wlan0: PRI: id=0x15 v1.0.4
Nov 30 15:35:18 ap_pico kernel: wlan0: STA: id=0x1f v1.0.3
Nov 30 15:35:18 ap_pico cardmgr[277]: executing: './network start wlan0'
Nov 30 15:35:18 ap_pico snmpd: snmpd startup succeeded
Nov 30 15:35:19 ap_pico cardmgr[277]: socket 1: Senao
SL-2011CD/SL-2011CDPLUS
Nov 30 15:35:19 ap_pico crond: crond startup succeeded
Nov 30 15:35:20 ap_pico kernel: hostap_cs: index 0x01: Vcc 3.3, irq 10, io
0x014 0-0x017f
Nov 30 15:35:20 ap_pico kernel: hostap_cs: Registered netdevice wlan1
Nov 30 15:35:20 ap_pico kernel: wlan1: NIC: id=0x800c v1.0.0
Nov 30 15:35:20 ap_pico kernel: wlan1: PRI: id=0x15 v1.0.4
Nov 30 15:35:20 ap_pico kernel: wlan1: STA: id=0x1f v1.0.3
Nov 30 15:35:20 ap_pico cardmgr[277]: executing: './network start wlan1'

Schmidt
----- Original Message -----
From: "dean gaudet" <dean at arctic.org>
To: "Jouni Malinen" <jkmaline at cc.hut.fi>
Cc: <hostap at shmoo.com>
Sent: Tuesday, December 03, 2002 3:59 AM
Subject: Re: problems with EN2511CD / NL2511CD


> On Mon, 2 Dec 2002, Jouni Malinen wrote:
>
> > On Mon, Dec 02, 2002 at 10:00:13PM -0800, dean gaudet wrote:
> >
> > > Dec  2 20:57:23 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0
trans#=1 stat=0 len=6fc=00b0) ==> 0 (authenticated)
> > > Dec  2 20:57:23 mewlark kernel: wlan0: 00:40:96:5a:5d:ce reassoc
(len=32 prev_ap=00:03:2f:02:97:46) => 0(0) (OK, new AID)
> > >
> > > those go on for a while, but the cisco never manages to associate.
> > > (i tried a WPC11 as well, no luck either.)
> >
> > As far as Host AP driver is concerned, that station has been
> > successfully associated. However, you could test this with the latest
> > CVS version to check whether the station is really acknowledging that
> > last reassociation response.
>
> here's what i get with latest CVS:
>
> Dec  2 22:46:42 mewlark kernel: hostap_crypt: registered algorithm 'NULL'
> Dec  2 22:46:42 mewlark kernel: hostap_cs: 0.0.0 CVS (Jouni Malinen
<jkmaline at cc.hut.fi>)
> Dec  2 22:46:42 mewlark kernel: hostap_cs: setting Vcc=33 (constant)
> Dec  2 22:46:42 mewlark kernel: hostap_cs: CS_EVENT_CARD_INSERTION
> Dec  2 22:46:42 mewlark kernel: prism2_config()
> Dec  2 22:46:42 mewlark kernel: hostap_cs: ignoring Vcc=33 (from config)
> Dec  2 22:46:42 mewlark kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
> Dec  2 22:46:42 mewlark kernel: IO window settings: cfg->io.nwin=1
dflt.io.nwin=1
> Dec  2 22:46:42 mewlark kernel: io->flags = 0x0046, io.base=0x0000, len=64
> Dec  2 22:46:42 mewlark kernel: hostap_cs: index 0x01: Vcc 3.3, irq 3, io
0x0180-0x01bf
> Dec  2 22:46:43 mewlark kernel: hostap_cs: Registered netdevice wlan0
> Dec  2 22:46:43 mewlark kernel: prism2_hw_init()
> Dec  2 22:46:43 mewlark kernel: prism2_hw_config: initialized in 17095
iterations
> Dec  2 22:46:43 mewlark kernel: wlan0: NIC: id=0x800c v1.0.0
> Dec  2 22:46:43 mewlark kernel: wlan0: PRI: id=0x15 v1.1.0
> Dec  2 22:46:43 mewlark kernel: wlan0: STA: id=0x1f v1.4.9
> Dec  2 22:46:43 mewlark kernel: wlan0: defaulting to bogus WDS frame as a
workaround for firmware bug in Host AP mode WDS
> Dec  2 22:46:43 mewlark kernel: wlan0: LinkStatus=2 (Disconnected)
> Dec  2 22:46:43 mewlark kernel: Setting ALC off
> Dec  2 22:46:43 mewlark kernel: Setting TX power to 24 dBm
> Dec  2 22:46:43 mewlark kernel: wlan0: LinkStatus=2 (Disconnected)
> Dec  2 22:46:43 mewlark kernel: wlan0: LinkStatus=2 (Disconnected)
> Dec  2 22:46:43 mewlark kernel: wlan0: prism2_open
> Dec  2 22:46:51 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0
trans#=1 stat=0 len=6 fc=00b0) ==> 0 (authOK)
> Dec  2 22:46:51 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth_cb - frame
was not ACKed
> Dec  2 22:47:27 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0
trans#=1 stat=0 len=6 fc=00b0) ==> 0 (authOK)
> Dec  2 22:47:27 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth_cb - frame
was not ACKed
>
> and just for kicks, here's what happens when i use my older WPC11
> card as AP on current CVS (which is working fine):
>
> Dec  2 22:48:05 mewlark kernel: hostap_crypt: registered algorithm 'NULL'
> Dec  2 22:48:05 mewlark kernel: hostap_cs: 0.0.0 CVS (Jouni Malinen
<jkmaline at cc.hut.fi>)
> Dec  2 22:48:05 mewlark kernel: hostap_cs: setting Vcc=33 (constant)
> Dec  2 22:48:05 mewlark kernel: hostap_cs: CS_EVENT_CARD_INSERTION
> Dec  2 22:48:05 mewlark kernel: prism2_config()
> Dec  2 22:48:05 mewlark kernel: hostap_cs: ignoring Vcc=50 (from config)
> Dec  2 22:48:05 mewlark kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
> Dec  2 22:48:05 mewlark kernel: IO window settings: cfg->io.nwin=1
dflt.io.nwin=1
> Dec  2 22:48:05 mewlark kernel: io->flags = 0x0046, io.base=0x0000, len=64
> Dec  2 22:48:05 mewlark kernel: hostap_cs: index 0x01: Vcc 5.0, irq 3, io
0x0180-0x01bf
> Dec  2 22:48:05 mewlark kernel: hostap_cs: Registered netdevice wlan0
> Dec  2 22:48:05 mewlark kernel: prism2_hw_init()
> Dec  2 22:48:05 mewlark kernel: prism2_hw_config: initialized in 9180
iterations
> Dec  2 22:48:05 mewlark kernel: wlan0: NIC: id=0x8002 v1.0.0
> Dec  2 22:48:05 mewlark kernel: wlan0: PRI: id=0x15 v0.3.0
> Dec  2 22:48:05 mewlark kernel: wlan0: STA: id=0x1f v0.8.3
> Dec  2 22:48:05 mewlark kernel: wlan0: defaulting to host-based encryption
as a workaround for firmware bug in Host AP mode WEP
> Dec  2 22:48:05 mewlark kernel: wlan0: defaulting to bogus WDS frame as a
workaround for firmware bug in Host AP mode WDS
> Dec  2 22:48:05 mewlark kernel: wlan0: LinkStatus=2 (Disconnected)
> Dec  2 22:48:05 mewlark kernel: Setting ALC off
> Dec  2 22:48:05 mewlark kernel: Setting TX power to 24 dBm
> Dec  2 22:48:05 mewlark kernel: wlan0: LinkStatus=2 (Disconnected)
> Dec  2 22:48:05 mewlark kernel: wlan0: LinkStatus=2 (Disconnected)
> Dec  2 22:48:05 mewlark kernel: wlan0: prism2_open
> Dec  2 22:48:38 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0
trans#=1 stat=0 len=6 fc=00b0) ==> 0 (authOK)
> Dec  2 22:48:38 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth_cb - STA
authenticated
> Dec  2 22:48:38 mewlark kernel: wlan0: 00:40:96:5a:5d:ce reassoc (len=32
prev_ap=00:03:2f:02:97:46) => 0(0) (OK, new AID)
> Dec  2 22:48:38 mewlark kernel: wlan0: 00:40:96:5a:5d:ce assoc_cb - STA
associated
> Dec  2 22:48:48 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0
trans#=1 stat=0 len=6 fc=00b0) ==> 0 (authOK)
> Dec  2 22:48:48 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth_cb - STA
authenticated
> Dec  2 22:48:48 mewlark kernel: wlan0: 00:40:96:5a:5d:ce assoc (len=26
prev_ap=00:00:00:00:00:00) => 0(0) (OK, old AID)
> Dec  2 22:48:48 mewlark kernel: wlan0: 00:40:96:5a:5d:ce assoc_cb - STA
associated
>
> note that prev_ap mac address is the mac address of the WPC11.
>
>
> > If the client card is not reporting any errors, I would just have to
> > guess that it did not like the reassociation reply for some reason (most
> > probably it arrived after too long delay). Since the client card sent
> > reassociation request, I would assume that it accepted authentication
> > frame from the AP (although, I've seen some stations not caring about
> > authentication that much..).
>
> the client is win2k / cisco350 ... any idea how i check for errors?
>
> -dean
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From praedor  Tue Dec 10 14:06:28 2002
From: praedor (Praedor Atrebates)
Date: Tue, 10 Dec 2002 17:06:28 -0500
Subject: kismet sniffer and hostap driver
Message-ID: <200212101706.31042.praedor@yahoo.com>

I seem to recall not too long ago someone in the list mentioning getting 
kismet to work with the hostap driver.  Has anyone managed to get kismet to 
work with it?  I have used kismet for a while with success when using the 
prism2_cs driver but since switching to hostap_cs, I can't get it working.

Running "kismet_monitor" knocks my card into master mode from which the app 
just doesn't seem to work.  Starting kismet connects to the kismet server but 
it never ever sees any traffic even in heavy wireless traffic areas.

praedor



From lennon  Tue Dec 10 14:39:16 2002
From: lennon (Craig Whitmore)
Date: Wed, 11 Dec 2002 11:39:16 +1300
Subject: DHCP Problems
Message-ID: <00a301c2a09c$f87eff50$6df058db@PC2>

Hi there

We have hostap up and running and if we set an ip address on the remote card
(winXP machine) we can ping the linux box and internet access works 100%,
But if we run DHCPD on the linux box to give the ip address to the WinXP
machine we get lots of errors as below. Can anyone know what is causing this
and can help?

I've tried the latest stable version and the latest CVS version (upto about
5 mins ago) with the same problem.

Thanks
Craig Whitmore
Orcon Internet
http://www.orcon.net.nz


Dec 11 11:32:10 wireless kernel:    FC=0x0080 (type=0:8) dur=0x0000
seq=0xcccc data_len=52428
Dec 11 11:32:10 wireless kernel:    A1=ff:ff:00:60:1d:f2
A2=32:47:00:60:1d:f2 A3=32:47:f0:d2:cc:cc A4=cc:ec:29:00:cc:cc
Dec 11 11:32:10 wireless kernel:    dst=cc:cc:44:4c:cc:c8
src=cc:dc:00:29:8d:d1 len=19416
Dec 11 11:32:10 wireless kernel: wlan0: RX: len(16717) > MAX(2304)
Dec 11 11:32:10 wireless kernel: wlan0: Received frame with invalid length
0x8050
Dec 11 11:32:10 wireless kernel: wlan0: RX status=0x8000 (port=0, type=4,
fcserr=0) silence=3 signal=39 rate=20 rxflow=0; jiffies=669659
Dec 11 11:32:10 wireless kernel:    FC=0x0080 (type=0:8) dur=0x0000
seq=0x8050 data_len=32848
Dec 11 11:32:10 wireless kernel:    A1=ff:ff:ff:ff:00:60
A2=1d:f2:32:47:00:60 A3=1d:f2:32:47:30:d3 A4=50:80:50:80:29:00
Dec 11 11:32:10 wireless kernel:    dst=50:80:50:80:50:80
src=50:80:50:80:00:29 len=32385
Dec 11 11:32:10 wireless kernel: wlan0: Received frame with invalid length
0xcccc
Dec 11 11:32:10 wireless kernel: wlan0: RX status=0x8000 (port=0, type=4,
fcserr=0) silence=2 signal=39 rate=20 rxflow=0; jiffies=669680
Dec 11 11:32:10 wireless kernel:    FC=0x0080 (type=0:8) dur=0x0000
seq=0xccc8 data_len=52428
Dec 11 11:32:10 wireless kernel:    A1=ff:ff:00:60:1d:f2
A2=32:47:00:60:1d:f2 A3=32:47:50:d3:cc:4c A4=cc:cc:29:00:cc:cd
Dec 11 11:32:10 wireless kernel:    dst=cd:8c:cc:c5:cc:cc
src=cc:cc:00:29:88:a1 len=21464
Dec 11 11:32:10 wireless kernel: wlan0: RX: len(5143) > MAX(2304)
Dec 11 11:32:10 wireless kernel: wlan0: Received frame with invalid length
0x8cce
Dec 11 11:32:10 wireless kernel: wlan0: RX status=0x8000 (port=0, type=4,
fcserr=0) silence=2 signal=40 rate=20 rxflow=0; jiffies=669700

---------------
Dec 11 11:37:10 wireless kernel: hostap_cs: 0.0.0 CVS (Jouni Malinen
<jkmaline at cc.hut.fi>)
Dec 11 11:37:10 wireless kernel: hostap_cs: index 0x01: Vcc 5.0, irq 3, io
0x0100-0x013f
Dec 11 11:37:10 wireless kernel: hostap_cs: Registered netdevice wlan0
Dec 11 11:37:10 wireless kernel: wlan0: NIC: id=0x800c v1.0.0
Dec 11 11:37:10 wireless kernel: wlan0: PRI: id=0x15 v1.0.7
Dec 11 11:37:10 wireless kernel: wlan0: STA: id=0x1f v1.3.5
---------------
wireless:/archives/hostap/utils# ./hostap_diag wlan0
Host AP driver diagnostics information for 'wlan0'

NICID: id=0x800c v1.0.0 (PRISM II (2.5) PCMCIA (SST parallel flash))
PRIID: id=0x0015 v1.0.7
STAID: id=0x001f v1.3.5 (station firmware)
-----------------

wireless:/archives/hostap# cardctl info
PRODID_1="D"
PRODID_2="Link DWL-650 11Mbps WLAN Card"
PRODID_3="Version 01.02"
PRODID_4=""
MANFID=0156,0002
FUNCID=6
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255




From jkmaline  Tue Dec 10 19:54:07 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 10 Dec 2002 19:54:07 -0800
Subject: 2002-10-12 monitor mode
In-Reply-To: <Pine.GSO.4.44.0212101046580.15962-100000@expert.ics.purdue.edu>
References: <Pine.NEB.4.44.0212101131350.25629-100000@droog> <Pine.GSO.4.44.0212101046580.15962-100000@expert.ics.purdue.edu>
Message-ID: <20021211035407.GA27785@jm.kir.nu>

On Tue, Dec 10, 2002 at 10:48:45AM -0500, Min Li wrote:

> >From the mailing list archive, I found that Jouni Malinen's reply about
> the bug in exisiting 2002-10-12 version for monitor mode configuration. Is
> there any way to fix the bug right now? Thanks

Update to the latest CVS version or do apply following patch:

--- hostap_ioctl.c      16 Nov 2002 07:01:57 -0000      1.19
+++ hostap_ioctl.c      27 Nov 2002 02:50:51 -0000      1.20
@@ -2374,8 +2374,9 @@ static int prism2_ioctl_priv_monitor(str
                        local->monitor_type = PRISM2_MONITOR_PRISM;
                        break;
                }
-               mode = IW_MODE_MASTER;
+               mode = IW_MODE_MONITOR;
                ret = prism2_ioctl_siwmode(dev, NULL, &mode, NULL);
+               hostap_monitor_mode_enable(local);
        } else
                ret = -EINVAL;
 
-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Dec 10 19:56:31 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 10 Dec 2002 19:56:31 -0800
Subject: 2002-10-12 monitor mode
In-Reply-To: <Pine.GSO.4.44.0212101059520.15962-100000@expert.ics.purdue.edu>
References: <Pine.GSO.4.44.0212101046580.15962-100000@expert.ics.purdue.edu> <Pine.GSO.4.44.0212101059520.15962-100000@expert.ics.purdue.edu>
Message-ID: <20021211035631.GB27785@jm.kir.nu>

On Tue, Dec 10, 2002 at 11:01:40AM -0500, Min Li wrote:

> Also, the tar ball downloaded from the CVS repository, is it compatible
> with redhat 8.0? It is not compilable right away. thanks.

I'm testing only with kernel.org release, so I do not know whether
kernel trees modified by various distribution vendors are working. There
was a problem that broke compilation with wireless extensions version
14, but it is now fixed in the CVS. If the latest CVS version does not
compile with your kernel tree, please send a more detailed report (i.e.,
error output from the compiler).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Dec 10 21:59:49 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 10 Dec 2002 21:59:49 -0800
Subject: Disco Antenna
In-Reply-To: <001901c2a086$a069b820$9600a8c0@oemcomputer>
References: <001901c2a086$a069b820$9600a8c0@oemcomputer>
Message-ID: <20021211055949.GA4324@jm.kir.nu>

On Tue, Dec 10, 2002 at 01:59:14PM -0600, Michael Shuler wrote:

>      Well it looks like the general consensus is that the Prism
> implementation of antenna diversity isn't very useful.  So I am
> proposing a different solution and want to see what other people think
> of it.  I've had this idea for quite some time but haven't know quite
> how to implement it, maybe someone else here could help?

I would have to say that antenna/radio design is not exactly within the
main topics of Host AP mailing list ;-). Anyway, you might like to take
a look at "Wi-Fi switch" that Vivato (www.vivato.net) demoed at the last
bawug meeting last week.

-- 
Jouni Malinen                                            PGP id EFC895FA



From daryl  Wed Dec 11 00:59:20 2002
From: daryl (Daryl J Clarkson)
Date: Wed, 11 Dec 2002 21:59:20 +1300
Subject: Fw: wlan0 Interface seems to freeze.
Message-ID: <88bb0fdfe41dedc510f01d568909ce983df70010@alliedpress.co.nz>

> On Tue, Dec 03, 2002 at 02:12:59AM +1100, Chincogan Network Services Lists
wrote:
> > Hi List,
> >
> > I have a problem where my wlan0 interface seems to freeze, a dmesg shows
pages and pages of this:
> > wlan0: prism2_tx: hw not ready - skipping
> > wlan0: prism2_tx: hw not ready - skipping
> >
> > Doing a "iwpriv wlan0 reset 1" does nothing, to fix this I have to
restart pcmcia. Sometimes this problem will leave us for a couple of days
other times this will happen multiple times a day.
> >
> > This afternoon I am going to change this card with a Dlink DWL-520 to
see if that makes any difference.
> >
> > My Setup:
> > Hostap 2002-10-12
> > Kernel 2.4.19
> > Pcmcia_cs 3.2.1
> > Compaq WL-200
> >

Confirming same problem here as well, configuaration:-

hostap 2002-10-12
kernel 2.4.18
pcmcia-cs-3.1.33
Compaq WL-200's (each end)

Cheers, Daryl.





From msc1  Wed Dec 11 14:50:51 2002
From: msc1 (msc1 at alu.um.es)
Date: Wed, 11 Dec 2002 14:50:51 MET
Subject: hostap and freeRadius
Message-ID: <200212111350.OAA19335@zape.um.es>

How can I configure hostap to use freeRadius?






From jkmaline  Wed Dec 11 06:31:49 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 11 Dec 2002 06:31:49 -0800
Subject: hostap and freeRadius
In-Reply-To: <200212111350.OAA19335@zape.um.es>
References: <200212111350.OAA19335@zape.um.es>
Message-ID: <20021211143149.GA1281@jm.kir.nu>

On Wed, Dec 11, 2002 at 02:50:51PM +0100, msc1 at alu.um.es wrote:

> How can I configure hostap to use freeRadius?

I would start by reading 'IEEE 802.1X' section in README.prism2.

-- 
Jouni Malinen                                            PGP id EFC895FA



From praedor  Wed Dec 11 09:08:39 2002
From: praedor (Praedor Atrebates)
Date: Wed, 11 Dec 2002 12:08:39 -0500
Subject: What file is controlling hostap_cs module?
Message-ID: <200212111208.41730.praedor@yahoo.com>

I don't understand.  I am trying to go back to using the prism2_cs module for 
a while so I can use kismet (I have failed to get kismet working with hostap 
inspite of trying several suggestions from users).  I moved my hostap_cs.conf 
file in my /etc/pcmcia dir to a new name to "kill" it.  I made sure that my 
remaining config files all bind "prism2_cs" to my card but no matter what I 
do, if I remove and reinsert the card, the hostap driver gets installed 
instead of prism2_cs.  What files are controlling this?  There was also an 
entry in my modules.conf:  alias wlan0 hostap_cs which I altered to alias 
prism2_cs.  Nothing happens and I still get hostap installing.

praedor



From linux  Wed Dec 11 11:42:09 2002
From: linux (Linux Rocks!)
Date: Wed, 11 Dec 2002 11:42:09 -0800
Subject: What file is controlling hostap_cs module?
In-Reply-To: <200212111208.41730.praedor@yahoo.com>
References: <200212111208.41730.praedor@yahoo.com>
Message-ID: <200212111142.09758.linux@rocksolidnetworks.com>

Praedor,
	It sounds like your using pcmcia, in that case you would likely have an 
/etc/pcmcia/config that sources *.conf (which is what is reading in your 
/etc/pcmcia/hostap_cs.conf). In my case, I had to add an entry to recognize 
my card by its manfid. You can simply edit the line in your hostap_cs.conf 
with your manfid (note: issue cardctl ident to display the cards in your 
machine, and you will see your manfid) to load whatever module you like.

Jamie

On Wednesday 11 December 2002 09:08 am, Praedor Atrebates wrote:
: I don't understand.  I am trying to go back to using the prism2_cs module
: for a while so I can use kismet (I have failed to get kismet working with
: hostap inspite of trying several suggestions from users).  I moved my
: hostap_cs.conf file in my /etc/pcmcia dir to a new name to "kill" it.  I
: made sure that my remaining config files all bind "prism2_cs" to my card
: but no matter what I do, if I remove and reinsert the card, the hostap
: driver gets installed instead of prism2_cs.  What files are controlling
: this?  There was also an entry in my modules.conf:  alias wlan0 hostap_cs
: which I altered to alias prism2_cs.  Nothing happens and I still get hostap
: installing.
:
: praedor
: _______________________________________________
: HostAP mailing list
: HostAP at shmoo.com
: http://lists.shmoo.com/mailman/listinfo/hostap

-- 
No microsoft products were used to produce this message.
EUG-LUG Mailing List:
http://mailman.efn.org/cgi-bin/listinfo/eug-lug




From jadeks  Tue Dec 10 01:42:05 2002
From: jadeks (=?gb2312?q?jade=20k?=)
Date: Tue, 10 Dec 2002 17:42:05 +0800 (CST)
Subject: HostAP with 3Com 3CRWE737A?
Message-ID: <20021210094205.39426.qmail@web21407.mail.yahoo.com>

Hi ,
 
Does anyone have run the hostAP with 3Com 3CRWE737A
AirConnect Wireless LAN PC Card ?
 
I understand that the 3com card is based on symbol's
modified Prism2 design. I've tried running both the
hostAP release 05-02-2001 and 12-10-2002 with 3com
card. WLAN0 device can up but seems it doesn't work.
 
Also , the notebook install with win2000/3COM card
can't talk to the HostAP based AP(with Linkup WPC11),
any suggestions to make the AP support 3COM Airconnect
client?
 
Yours help will be very much appreciate, Thanks!
 
Regards,
Jade



_________________________________________________________
Do You Yahoo!? 
"?IT??????????????"
http://cn.promo.yahoo.com/cgi-bin/udb/u



From Simon  Thu Dec 12 02:58:19 2002
From: Simon (Simon Waters)
Date: Thu, 12 Dec 2002 10:58:19 +0000
Subject: Traffic Control
Message-ID: <3DF86BCB.A8D96803@wretched.demon.co.uk>

Pretty basic question to start with...

When using hostap as an Access Point, will client to client IP
packets on the same subnet (and interface) go through the layers
that allow Linux tc to regulate bandwidth usage?

I assume some layer 2 stuff definitely won't hit this code, if
only the administrative traffic. Is there a packet by packet
description of what is happening anywhere, or must I master the
source code?



From martin.daur  Thu Dec 12 04:58:26 2002
From: martin.daur (Martin Daur)
Date: Thu, 12 Dec 2002 13:58:26 +0100
Subject: hostapd failed/ hostab_cs works
References: <200212111208.41730.praedor@yahoo.com>
Message-ID: <3DF887F2.2010108@web.de>

Hello,

i have a lucent wavelan silver pcmcia card. the hostap_cs driver
(hostap-2002-10-12) is running well in the ad-hoc mode (managed mode
seems to work) but i can't use the master mode, because i can't get
hostapd running.

iwconfig:
wlan0     IEEE 802.11-b  ESSID:"test"
            Mode:Master  Frequency:2.422GHz  Access Point:
00:60:1D:F0:F5:A8
            Bit Rate:11Mb/s   Tx-Power:-12 dBm   Sensitivity=1/3
            Retry limit:4   RTS thr:off
	...

./hostapd wlan0:
ioctl(SIOCGIFINDEX): No such device
ioctl[SIOCGIFFLAGS]: No such device
modprobe: modprobe: Can't locate module wlan0ap	(syslog)
	
what does "ap" behind the wlan0 mean, i think the device is called wlan0
(modules.conf includes "alias wlan0 hostap_cs")?


thanks
martin
-- 
Martin Daur          Tel: 07344/6915                * Please Encrypt *
Weilerstr. 48/6      Fax: 07344/kaputt              *  Certificates, *
D-89143 Blaubeuren   ICQ: 39532297                  *   GnuPG, PGP   *
Germany              Web: mdaur.homeip.net/martin   ******************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4661 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20021212/6c6ab723/attachment.bin 


From wlan  Thu Dec 12 06:45:13 2002
From: wlan (wlan)
Date: 12 Dec 2002 15:45:13 +0100
Subject: hostapd failed/ hostab_cs works
In-Reply-To: <3DF887F2.2010108@web.de>
References: <200212111208.41730.praedor@yahoo.com> 
	<3DF887F2.2010108@web.de>
Message-ID: <1039704313.1889.25.camel@localhost.localdomain>

On Thu, 2002-12-12 at 13:58, Martin Daur wrote:
> Hello,
> 
> i have a lucent wavelan silver pcmcia card. the hostap_cs driver
> (hostap-2002-10-12) is running well in the ad-hoc mode (managed mode
> seems to work) but i can't use the master mode, because i can't get
> hostapd running.
> 
> iwconfig:
> wlan0     IEEE 802.11-b  ESSID:"test"
>             Mode:Master  Frequency:2.422GHz  Access Point:
> 00:60:1D:F0:F5:A8
>             Bit Rate:11Mb/s   Tx-Power:-12 dBm   Sensitivity=1/3
>             Retry limit:4   RTS thr:off
> 	
As far as i know you cannot run hermes chipset card in Master mode. More
info about orinoco/lucent cards:
http://www.seattlewireless.net/index.cgi/LucentWirelessCard


...
> 
> ./hostapd wlan0:
> ioctl(SIOCGIFINDEX): No such device
> ioctl[SIOCGIFFLAGS]: No such device
> modprobe: modprobe: Can't locate module wlan0ap	(syslog)
> 	
> what does "ap" behind the wlan0 mean, i think the device is called wlan0
> (modules.conf includes "alias wlan0 hostap_cs")?
> 
> 
> thanks
> martin
> -- 
> Martin Daur          Tel: 07344/6915                * Please Encrypt *
> Weilerstr. 48/6      Fax: 07344/kaputt              *  Certificates, *
> D-89143 Blaubeuren   ICQ: 39532297                  *   GnuPG, PGP   *
> Germany              Web: mdaur.homeip.net/martin   ******************





From pedro.estrela  Thu Dec 12 08:56:13 2002
From: pedro.estrela (Pedro Estrela)
Date: Thu, 12 Dec 2002 16:56:13 -0000
Subject: Traffic Control
References: <3DF86BCB.A8D96803@wretched.demon.co.uk>
Message-ID: <003d01c2a1ff$6166ba90$98e216d5@pedropc>

hello,
a) The client to client packets on the same AP cell are sent directly to
each other, not passing through the AP at all. It is sufficient for the
destination STA to be in range to receive the packet.

b) if option "ap_bridge_packets == 1" is set, then all received packets on
the AP destinated to another client associated to this AP are sent directly
to the interface on the driver, not passing through TC. this also happens
for Layer2 broadcast and multicast packets. Howerver, currently AFAIK this
facility is not used because point A (see above) causes all traffic to go
_direct_ between stations. Maybe this could be used to extend the coverage
of an AP cell, by enabling client to speak trough the AP (for example: "A"
does not see "B", but both see "AP", so they could speak at hight speed
trough "AP"), but i don't thing that this is implemented, .

c) the remaining packets are those between diferent AP cells, normally for
using bridging & WDS for stations on same subnet. I'm do not know if the
bridge interfaces can be used for TC operation, but somebody on this list
could.

d) for the packets that goes to diferent subnets pass the AP until they
reach the subnet's router, which normally will not be the AP. The only
exception is when the AP is the sole router of the subnet, but that defeats
roaming and scalability.

---------

I am currenltly investigating on IP Mobility coupled with IP QoS Support on
micro-mobility cenarios, and it was this exact problem that i've tryed to
solve 2 years ago. For this, i've designed a micro-mobility protocol called
TIMIP that enables roaming of any IP terminal inside a domain between APs,
which are IP routers.

Using this protocol, all existing IP tecnologies can be used on the 802.11
interface of the APs (because they are _always_ routers). Using this, i was
able to implement the Diffserv techology for managing downlink troughtput
passing to the wireless interface. Another feature is that the TIMIP routing
forces all packts to pass trough the AP, to solve the "A" problem (client to
client direct on the same cell, see above).

I anyone needs further details on my work or 802.11 for this problem, feel
free to ask...

Pedro Estrela

----- Original Message -----
From: "Simon Waters" <Simon at wretched.demon.co.uk>
To: <hostap at shmoo.com>
Sent: Thursday, December 12, 2002 10:58 AM
Subject: Traffic Control


> Pretty basic question to start with...
>
> When using hostap as an Access Point, will client to client IP
> packets on the same subnet (and interface) go through the layers
> that allow Linux tc to regulate bandwidth usage?
>
> I assume some layer 2 stuff definitely won't hit this code, if
> only the administrative traffic. Is there a packet by packet
> description of what is happening anywhere, or must I master the
> source code?






From jphstap  Thu Dec 12 14:41:36 2002
From: jphstap (Joe Parks)
Date: Thu, 12 Dec 2002 17:41:36 -0500
Subject: Cross channel WDS ?!
Message-ID: <20021212224136.GA3625@scrodconumulus.roinet.com>

Strange phenomena:  2 machines, both running hostap driver in Master 
mode with autom_ap_wds=1 and  other_ap_policy=1.  Same ESSID, but 
DIFFERENT channels.  (one on 1 one on 11, but works with ANY 2 channels)

They establish WORKING WDS links to one another!

When the channels differ the WDS links are only ever at 2Mb (11Mb when 
same channel).

Also SNR drops in proportion to the separation between the two channels.

I've tried this with various prism2 based cards and they all do this.   
Shouldn't this NOT happen?  Not that its completely a bad thing, I have 
imagined some interesting uses for this (full duplex with a single card 
anyone?)   This means that the driver is processing packets that it 
probably shouldn't have seen in the first place though, doesn't it?



From ariel  Thu Dec 12 09:46:29 2002
From: ariel (ariel at fismat.umich.mx)
Date: Thu, 12 Dec 2002 17:46:29 -0000 (UTC)
Subject: WPC11 1.4.2 firmware not AP mode
Message-ID: <35650.148.216.6.188.1039715189.squirrel@fismat.umich.mx>

Greetings:

I got a linksys WPC11

http://www.linksys.com/products/product.asp?prid=156&grid=22

and installed the latest hostap_cs.
But whenever i insert the card (or do a reboot) it shows a message:

"wlan0 warning firmware 1.4.2 does not work in AP mode"

So i searched the web looking for an older firmware, searched and
searched. But i've not found anything. First i went to the linksys webpage
and found a download page
http://www.linksys.com/support/support.asp?spid=62

But it says that the WPC11 _does not_ require a firmware. So i cant
download anything.

Please, can you tell me where to find an older firmware, and if i
downgrade will mi card work or it will be messed up?

Or can you tell me a way to make my card work in AP mode?

Thankx  :-D






From linux  Thu Dec 12 15:25:40 2002
From: linux (Linux Rocks!)
Date: Thu, 12 Dec 2002 15:25:40 -0800
Subject: Still no ap action going on here :( help please.
Message-ID: <200212121525.40166.linux@rocksolidnetworks.com>

Hi,
	Im still not having any luck with any linux modules for my Proxim RangeLan-DS 
PC Cards. Im really unsure what Im doing wrong. 
	Im currently using Kernel 2.4.20, hostap-2002-10-12, my firmware version is 
0.8.3. Wireless Tools Version 26 (compiles with WE 15).  
	Im compiling stuff on my main workstation (not the machines using hostap) as 
the laptops that are using hostap suck (p-120/24meg/300, 720mb hard disks)
	The hostap module is using the standard stuff in the 2.4.20 kernel source, 
(yes, WE 14...)
	Ive compiled the orinoco_cs module using the same 2.4.20 kernel source, tried 
it against hostap, and the windows software w/no luck.
	Ive tried hostap_cs in all 3 modes (master, ad-hoc, managed) against the 
windows laptop with no luck (on the windows computer Ive tried 
Infrastructure, Ad-hoc, and 802.11 Ad-hoc). No matter what I do, I cannot 
seem to get anything to associate! 
	Before my big laptop hard disk died, I had tested the cards with 2 windows 
laptops... they worked fine, so Im confident that there arent hardware 
problems.
	This is what Im doing:
	cd to hostap-2002-10-12
	make pccard
	make install_pccard
	Then I copy the files that make install_pccard copys to a directory, tar them 
up, and ftp them to the laptop. I then make the directorys and copy those 
files to the exact same locations on the laptop (yes, I used copy/paste to 
make sure I get that right).
	NOTE: I havnt edited any files in the hostap source, I just make them. I get 
no errors or problems compiling, I get no errors loading the modules. dmesg 
looks fine, lsmod looks fine. make install_pccard does give me depmod errors, 
but only Im not using it on the workstation... When I run depmod -a on the 
laptop, it gives no errors. 
	Others on this list say my dmesg/iwconfig look fine, but Ill include them 
below again to see if anyone can find a problem.

iwconfig:
Warning: Driver for device wlan0 has been compiled with version 14
of Wireless Extension, while this program is using version 15.
Some things may be broken...

wlan0     IEEE 802.11-b  ESSID:"blah"  
          Mode:Master  Frequency:2.422GHz  Access Point: 00:60:B3:6F:63:CC  
          Bit Rate:11Mb/s   Tx-Power:-6 dBm   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root at lapdance:~# iwconfig --version
iwconfig  Version 26
          Compatible with Wireless Extension v15 or earlier,
          Currently compiled with Wireless Extension v15.

wlan0     Recommend Wireless Extension v13 or later,
          Currently compiled with Wireless Extension v14.


<bottom section of dmesg containing hostap stuff...>

cs: IO port probe 0x0a00-0x0aff: excluding 0xa68-0xa6f 0xaa0-0xaa7 0xaf8-0xaff
cs: memory probe 0x0d0000-0x0dffff: clean.
hostap_crypt: registered algorithm 'NULL'
hostap_cs: hostap_cs.c 0.0.0 2002-10-12 (SSH Communications Security Corp, 
Jouni Malinen)
hostap_cs: (c) Jouni Malinen <jkmaline at cc.hut.fi>
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
prism2_config()
hostap_cs: ignoring 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: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
hostap_cs: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_config: initialized in 9089 iterations
wlan0: NIC: id=0x8002 v1.0.0
wlan0: PRI: id=0x15 v0.3.0
wlan0: STA: id=0x1f v0.8.3
wlan0: defaulting to host-based encryption as a workaround for firmware bug in 
Host AP mode WEP
wlan0: LinkStatus=2 (Disconnected)
wlan0: prism2_open

<hostap_cs.conf (part regarding my card)>

   manfid 0x0126, 0x8000
   bind "hostap_cs"
#   module "hostap_cs" opts "essid=any channel=6 ignore_cis_vcc=1"


# Optional configuration parameters for hostap_cs.o
# module "hostap_cs" opts "channel=6 essid=any ignore_cis_vcc=1"
 module "hostap_cs" opts "channel=3 iw_mode=3 essid=blah ignore_cis_vcc=1"
# module "orinoco_cs" opts "ignore_cis_vcc=1"

Note: I need the ignore_cis_vcc=1 or I get a bunch of nasty errors!

Thanks in advance, Jamie

-- 
No microsoft products were used to produce this message.
EUG-LUG Mailing List:
http://mailman.efn.org/cgi-bin/listinfo/eug-lug




From proski  Thu Dec 12 15:33:06 2002
From: proski (Pavel Roskin)
Date: Thu, 12 Dec 2002 18:33:06 -0500 (EST)
Subject: WPC11 1.4.2 firmware not AP mode
In-Reply-To: <35650.148.216.6.188.1039715189.squirrel@fismat.umich.mx>
References: <35650.148.216.6.188.1039715189.squirrel@fismat.umich.mx>
Message-ID: <Pine.LNX.4.50.0212121829570.27151-100000@marabou.research.att.com>

Hello!

> "wlan0 warning firmware 1.4.2 does not work in AP mode"

My experience confirms that, and it's also a Linksys card (WCF12).

The approach that works for me is to load secondary 1.5.6 firmware by
prism2_srec every time the driver is loaded.  Search the list and the web
for more details.  Somebody even posted the firmware on a website.

-- 
Regards,
Pavel Roskin



From dave  Thu Dec 12 15:37:47 2002
From: dave (Dave Wang)
Date: Thu, 12 Dec 2002 15:37:47 -0800
Subject: WPC11 1.4.2 firmware not AP mode
Message-ID: <B2FC93133CB3EB4A813CBD19717B148814FE5D@aruba-server.arubanetworks.com>

This older posting was very helpful

http://lists.shmoo.com/pipermail/hostap/2002-October/000024.html

use the links to the dlink/intersil flasher, and the netgate firmware

-----Original Message-----
From: ariel at fismat.umich.mx [mailto:ariel at fismat.umich.mx] 
Sent: Thursday, December 12, 2002 9:46 AM
To: hostap at shmoo.com
Subject: WPC11 1.4.2 firmware not AP mode

Greetings:

I got a linksys WPC11

http://www.linksys.com/products/product.asp?prid=156&grid=22

and installed the latest hostap_cs.
But whenever i insert the card (or do a reboot) it shows a message:

"wlan0 warning firmware 1.4.2 does not work in AP mode"

So i searched the web looking for an older firmware, searched and
searched. But i've not found anything. First i went to the linksys webpage
and found a download page
http://www.linksys.com/support/support.asp?spid=62

But it says that the WPC11 _does not_ require a firmware. So i cant
download anything.

Please, can you tell me where to find an older firmware, and if i
downgrade will mi card work or it will be messed up?

Or can you tell me a way to make my card work in AP mode?

Thankx  :-D



_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap



From jkmaline  Thu Dec 12 19:35:19 2002
From: jkmaline (Jouni Malinen)
Date: Thu, 12 Dec 2002 19:35:19 -0800
Subject: hostapd failed/ hostab_cs works
In-Reply-To: <3DF887F2.2010108@web.de>
References: <200212111208.41730.praedor@yahoo.com> <3DF887F2.2010108@web.de>
Message-ID: <20021213033519.GA1067@jm.kir.nu>

On Thu, Dec 12, 2002 at 01:58:26PM +0100, Martin Daur wrote:

> i have a lucent wavelan silver pcmcia card. the hostap_cs driver
> (hostap-2002-10-12) is running well in the ad-hoc mode (managed mode
> seems to work) but i can't use the master mode, because i can't get
> hostapd running.

That is not the main problem.. Lucent WaveLAN does not have a Host AP
mode, so it will not work in Master mode even if you get hostapd
running.

> ./hostapd wlan0:
> ioctl[SIOCGIFFLAGS]: No such device
> modprobe: modprobe: Can't locate module wlan0ap	(syslog)

> what does "ap" behind the wlan0 mean, i think the device is called wlan0
> (modules.conf includes "alias wlan0 hostap_cs")?

wlan0ap is the interface used for management frames. You have to compile
the kernel driver with PRISM2_HOSTAPD defined to build a version that
can be used with hostapd.

-- 
Jouni Malinen                                            PGP id EFC895FA



From linux  Fri Dec 13 00:35:10 2002
From: linux (Linux Rocks!)
Date: Fri, 13 Dec 2002 00:35:10 -0800
Subject: Still no ap action going on here :( help please.
In-Reply-To: <002c01c2a261$00598770$468101d9@pcwks356>
References: <002c01c2a261$00598770$468101d9@pcwks356>
Message-ID: <200212130035.10172.linux@rocksolidnetworks.com>

Manjunathan, other hostappers....

        Hi. I tried blah and any on both linux and windows workstations. I 
belive the 
any essid is a reserved/key word which tells the software/device to just use 
any essid it can find. wep is definetly disabled (iwconfig says so, and I 
havnt made any keys for it...). 
        I went to the LUG meeting tonite, we have an ap runnig there, so I 
brought my 
laptop, and 3 hard drives (they pull out easily). I started the laptop with 
the windows drive first. It promptly prompted me with a message telling me 
its connected to the AP... I pulled up the proxim software, and found I had 
associated, and an excelent signal strength. Woo Hoo! 
        I swapped out the hard disk, and tried the hostap (in 
Infrastructer/managed 
mode) no luck :( I tried the orinoco_cs module too... no luck! I tried them 
both using the previous kernel/modules (2.4.19-rc3)... no luck. 
        I did notice that when I put it in managed mode, I got some odd 
errors!
wlan0: hfa384x_cmd: entry still in list? (entry=c10b1220, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=c10b1220, type=0, 
cmd=0x0002, param0=0x0000)
wlan0: MAC port 0 reseting failed
I dont know what that means... but it dosnt look good!
I also noticed this:
hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
The card is suposed to be a 3.3 volt card (but my laptop doesnt support that I 
guess...) however it does work in windows (yeah... I hate it when people say 
that too!)

I can try setting the ssid to Super-wlan, but I just dont think its going to 
make any difference. it shouldnt be any better than blah.

Once again, I have not seen this card work at all in linux, no matter wether I 
use hostap, orinoco, ad-hoc, infrastrucure/managed or master modes. I think 
Ive tried every possible combination, used 4 different kernel sources 
(2.4.18, 2.4.19,2.4.19-rc3, 2.4.20)
What can I possibly be doing wrong!

Jamie

On Thursday 12 December 2002 08:35 pm, Manjunathan PY wrote:
: Hi,
:
:
:  I still feel that every things is fine with the configuration, except that
: you are using    essid "blah" on HostAP and "Any" on Windows clients, this
: may not work. So do something like as given below!
:  Check if you have disabled the wep security on the Windows laptops.
:
:  Also verify if your configuration on Hostap i.e Linux box is as shown
: below
:
: --------------------------------Hostap
: Configuration--------------------------------------
: IEEE 802.11-b  ESSID:"Super-Wlan"
:           Mode:Master  Frequency:2.422GHz  Access Point: 00:60:B3:6F:63:CC
:           Bit Rate:11Mb/s   Tx-Power:-6 dBm   Sensitivity=1/3
:           Retry min limit:8   RTS thr:off   Fragment thr:off
:           Encryption key:off
:           Power Management:off
:           Link Quality:0  Signal level:0  Noise level:0
:           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
:           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
:
: ---------------------------------------------------------------------------
:- ----------------------
:
:
:
: --------------------------------Client configuration running on Windows
: laptops-----------------------
:
: IEEE 802.11-b  ESSID:"Super-Wlan"
:           Mode:Managed  Frequency:2.422GHz  Access Point: 44:44:44:44:44:44
:           Bit Rate:11Mb/s   Tx-Power:-6 dBm   Sensitivity=1/3
:           Retry min limit:8   RTS thr:off   Fragment thr:off
:           Encryption key:off
:           Power Management:off
:           Link Quality:0  Signal level:0  Noise level:0
:           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
:           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
:
:
:
: With WEP security options =  disabled, also encryption key is off (open
: authentication)
:
: ---------------------------------------------------------------------------
:- --------------------------------------------------
:
: Note that ESSID in both the hostap and client are same. Make sure that
: essid field is same in hostap and on two clients. This is very important
: for associate (in open authentication method).
:
: I think this should solve ur problem!
:
: Cheers,
:
: Manjunathan PY

-- 
No microsoft products were used to produce this message.
EUG-LUG Mailing List:
http://mailman.efn.org/cgi-bin/listinfo/eug-lug




From Simon  Thu Dec 12 21:32:56 2002
From: Simon (Simon Waters)
Date: Fri, 13 Dec 2002 05:32:56 +0000
Subject: hostap_plx switching off encryption?
References: <200212111208.41730.praedor@yahoo.com> <3DF887F2.2010108@web.de> <20021213033519.GA1067@jm.kir.nu>
Message-ID: <3DF97108.2B627E3B@wretched.demon.co.uk>

Had trouble switching of hostap_plx encryption on WISP (using
Linksys cards with 1.4.9).

The menuing system has a minor bug, which slowed me down a
little, but I couldn't manually issue iwconfig command to switch
encryption off.

Should both "iwconfig wlan0 key off" and "iwconfig wlan0 enc
off" switch off encryption, I couldn't persuade WISP to do this
when hostap_plx was in MASTER mode, in the end I had to "vi
/etc/network/wireless.config", commit to flash, and reboot.

Minor issue but I'd like to understand it fully, as I need to
explain all the failures to network.

 Simon



From Simon  Thu Dec 12 21:49:51 2002
From: Simon (Simon Waters)
Date: Fri, 13 Dec 2002 05:49:51 +0000
Subject: Duplicate pings again (traffic control answer).
References: <200212111208.41730.praedor@yahoo.com> <3DF887F2.2010108@web.de> <20021213033519.GA1067@jm.kir.nu>
Message-ID: <3DF974FF.BDE69419@wretched.demon.co.uk>

Okay;

hostap_plx with Linksys card, STA 1.4.9 9 evil firmware ;-),
WISP (see leaf.sourceforge.net).

Clients, both using Lucent Silver Cards
	2.2.19 Linux + wvlan_cs.o (from pcmcia_cs3.2.0 I think)
	Mandrake 8.1 + orinoco.o

Both pinging hostap default ping options, no duplicates.

Both pinging each other, via hostap, lots and lots of duplicates
(nearly 1 per packet).

One pinging access point default settings, one using larger
packet size (-s 6550), odd duplicate packet spotted.

Pinging AP, ping size pumped up to maximum allowed on one client
- oh dear - one doesn't return, the other coughs duplicates-
should I have enabled fragmenting?

Simply switching of retires "iwconfig wlan0 retry 0" on
hostap_plx access point, gave three or four duplicates per
packet.

I'm missing something simple (or basic) here I fear.

All tests done with enc 0102-0304-00, although unencrypted I
still got duplicates, I didn't test much further of unenc.

 Simon

PS: To answer an earlier question of mine, traffic control seems
to work on packets going through access point (via same master
hostap_plx card, and same subnet), at least in some fashion.
i.e. I can restrict my throughput down to a few Kbytes, and use
various smart queuing on ingress and egress to give a better
balance between sessions (although I think the hashing
algorithmn had some trouble distinguishing two SSH sessions
between the same two hosts). Too soon to say if there is a
downside, but I don't seem off hand why it should be different
to cabled traffic shaping. Although till I get better throughput
and less duplicates it is hard to be confident in the subtler
effects.



From nerdboy  Fri Dec 13 00:09:36 2002
From: nerdboy (Nerdboy)
Date: Fri, 13 Dec 2002 00:09:36 -0800
Subject: Still no ap action going on here :( help please.
In-Reply-To: <002c01c2a261$00598770$468101d9@pcwks356>
References: <002c01c2a261$00598770$468101d9@pcwks356>
Message-ID: <200212130009.36508.nerdboy@rocksolidnetworks.com>

Manjunathan,
	Hi. I tried blah and any on both linux and windows workstations. I belive the 
any essid is a reserved/key word which tells the software/device to just use 
any essid it can find. wep is definetly disabled (iwconfig says so, and I 
havnt made any keys for it...). 
	I went to the LUG meeting tonite, we have an ap runnig there, so I brought my 
laptop, and 3 hard drives (they pull out easily). I started the laptop with 
the windows drive first. It promptly prompted me with a message telling me 
its connected to the AP... I pulled up the proxim software, and found I had 
associated, and an excelent signal strength. Woo Hoo! 
	I swapped out the hard disk, and tried the hostap (in Infrastructer/managed 
mode) no luck :( I tried the orinoco_cs module too... no luck! I tried them 
both using the previous kernel/modules (2.4.19-rc3)... no luck. 
	I did notice that when I put it in managed mode, I got some odd errors!
wlan0: hfa384x_cmd: entry still in list? (entry=c10b1220, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=c10b1220, type=0, 
cmd=0x0002, param0=0x0000)
wlan0: MAC port 0 reseting failed
I dont know what that means... but it dosnt look good!
I also noticed this:
hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
The card is suposed to be a 3.3 volt card (but my laptop doesnt support that I 
guess...) however it does work in windows (yeah... I hate it when people say 
that too!)

I can try setting the ssid to Super-wlan, but I just dont think its going to 
make any difference. it shouldnt be any better than blah.

Once again, I have not seen this card work at all in linux, no matter wether I 
use hostap, orinoco, ad-hoc, infrastrucure/managed or master modes. I think 
Ive tried every possible combination, used 4 different kernel sources 
(2.4.18, 2.4.19,2.4.19-rc3, 2.4.20)
What can I possibly be doing wrong!

Jamie




 	
 On Thursday 12 December 2002 08:35 pm, Manjunathan PY wrote:
: Hi,
:
:
:  I still feel that every things is fine with the configuration, except that
: you are using    essid "blah" on HostAP and "Any" on Windows clients, this
: may not work. So do something like as given below!
:  Check if you have disabled the wep security on the Windows laptops.
:
:  Also verify if your configuration on Hostap i.e Linux box is as shown
: below
:
: --------------------------------Hostap
: Configuration--------------------------------------
: IEEE 802.11-b  ESSID:"Super-Wlan"
:           Mode:Master  Frequency:2.422GHz  Access Point: 00:60:B3:6F:63:CC
:           Bit Rate:11Mb/s   Tx-Power:-6 dBm   Sensitivity=1/3
:           Retry min limit:8   RTS thr:off   Fragment thr:off
:           Encryption key:off
:           Power Management:off
:           Link Quality:0  Signal level:0  Noise level:0
:           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
:           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
:
: ---------------------------------------------------------------------------
:- ----------------------
:
:
:
: --------------------------------Client configuration running on Windows
: laptops-----------------------
:
: IEEE 802.11-b  ESSID:"Super-Wlan"
:           Mode:Managed  Frequency:2.422GHz  Access Point: 44:44:44:44:44:44
:           Bit Rate:11Mb/s   Tx-Power:-6 dBm   Sensitivity=1/3
:           Retry min limit:8   RTS thr:off   Fragment thr:off
:           Encryption key:off
:           Power Management:off
:           Link Quality:0  Signal level:0  Noise level:0
:           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
:           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
:
:
:
: With WEP security options =  disabled, also encryption key is off (open
: authentication)
:
: ---------------------------------------------------------------------------
:- --------------------------------------------------
:
: Note that ESSID in both the hostap and client are same. Make sure that
: essid field is same in hostap and on two clients. This is very important
: for associate (in open authentication method).
:
: I think this should solve ur problem!
:
: Cheers,
:
: Manjunathan PY




From Carsten  Fri Dec 13 01:17:41 2002
From: Carsten (Carsten Tschach)
Date: Fri, 13 Dec 2002 10:17:41 +0100
Subject: Compaq WL100 Init Problem...
Message-ID: <20021213091741.GB2586615@Tschach.com>

Hi Folks,

I do have a Compaq WL100 card I would like to use in my RedHat 8.0 based
Notebook.

I did use the current CVS-Snapshot from the Server, which is running
perfectly in a Desktop-PC using a WL200 card.

When inserting the WL100 into the Notebook I do get the following 
error in /var/log/messages:

-------------------------------------------------------------------------------
Dec 13 10:05:31 porty cardmgr[2262]: executing: 'insmod /lib/modules/2.4.20/pcmcia/hostap_cs.o'
Dec 13 10:05:31 porty kernel: hostap_cs: 0.0.0 CVS (Jouni Malinen <jkmaline at cc.hut.fi>)
Dec 13 10:05:31 porty kernel: hostap_cs: index 0x01: Vcc 3.3, irq 3, io 0x0180-0x01bf
Dec 13 10:05:32 porty kernel: hostap_cs: Registered netdevice wlan0
Dec 13 10:05:32 porty cardmgr[2262]: executing: './network start wlan0'
Dec 13 10:05:32 porty kernel: hostap_cs: card initialization timed out
Dec 13 10:05:32 porty kernel: hostap_cs: Initialization failed
-------------------------------------------------------------------------------

Seems like the driver can't initilize the card.



iwconfig wlan0 produced the following output:
-------------------------------------------------------------------------------
wlan0     IEEE 802.11-DS  ESSID:"test"  
          Mode:Master  Tx-Power:15 dBm   
          Encryption key:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
-------------------------------------------------------------------------------


ifconfig wlan0 produced the following output:
-------------------------------------------------------------------------------
wlan0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Base address:0x180 
-------------------------------------------------------------------------------

So the driver doesn't even recognize the Cards MAC-Adress...hmmm....

Thanks for your help....Carsten



From hazard  Fri Dec 13 06:56:48 2002
From: hazard (Vladimir Ivaschenko)
Date: Fri, 13 Dec 2002 16:56:48 +0200
Subject: hostap_plx switching off encryption?
In-Reply-To: <3DF97108.2B627E3B@wretched.demon.co.uk>
References: <200212111208.41730.praedor@yahoo.com> <3DF887F2.2010108@web.de> <20021213033519.GA1067@jm.kir.nu> <3DF97108.2B627E3B@wretched.demon.co.uk>
Message-ID: <20021213165647.A12583@hzdhome.home.blkseanet.ru>

Hi,

As far as I understand you're talking about WISP-Dist. I'm the developer
of this distribution. To be honest from your description I don't
understand whether the problem is in the WISP-Dist or in the driver.

Fri, Dec 13, 2002 at 05:32:56AM +0000 Simon Waters wrote about hostap_plx switching off encryption?

> Had trouble switching of hostap_plx encryption on WISP (using
> Linksys cards with 1.4.9).
> 
> The menuing system has a minor bug, which slowed me down a
> little, but I couldn't manually issue iwconfig command to switch
> encryption off.
> 
> Should both "iwconfig wlan0 key off" and "iwconfig wlan0 enc
> off" switch off encryption, I couldn't persuade WISP to do this
> when hostap_plx was in MASTER mode, in the end I had to "vi
> /etc/network/wireless.config", commit to flash, and reboot.
> 
> Minor issue but I'd like to understand it fully, as I need to
> explain all the failures to network.
> 
>  Simon
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

-- 
Best Regards
Vladimir Ivaschenko
http://www.hazard.maks.net/



From judah  Fri Dec 13 11:32:42 2002
From: judah (Aaron Baer)
Date: 13 Dec 2002 11:32:42 -0800
Subject: Kernel RPMs with HostAP Available
Message-ID: <1039807962.6791.2.camel@localhost.localdomain>

I have put together an rpm package using the latest RedHat kernel
release that contains all of the HostAP drivers included as modules.
i386, i686 rpms are available and have been tested on RedHat 8.0, 7.2
and Mandrake (although on that system we had to upgrade mkinitrd)

Also available for download are the src.rpm and kernel-source packages
that I have created with HostAP. Please see the url for some more
information and if you have any questions feel free to email.

The packages can be found at
http://www.cat.pdx.edu/~baera/redhat_hostap/

A-

-- 
----
Aaron Baer
judah at opusnet.com
http://www.cat.pdx.edu/~baera/




From hazard  Fri Dec 13 11:44:09 2002
From: hazard (Vladimir Ivaschenko)
Date: Fri, 13 Dec 2002 21:44:09 +0200
Subject: hostap_plx switching off encryption?
In-Reply-To: <3DF9FBFE.CD3C02CC@wretched.demon.co.uk>
References: <200212111208.41730.praedor@yahoo.com> <3DF887F2.2010108@web.de> <20021213033519.GA1067@jm.kir.nu> <3DF97108.2B627E3B@wretched.demon.co.uk> <20021213165647.A12583@hzdhome.home.blkseanet.ru> <3DF9FBFE.CD3C02CC@wretched.demon.co.uk>
Message-ID: <20021213214409.A12766@hzdhome.home.blkseanet.ru>

Fri, Dec 13, 2002 at 03:25:50PM +0000 Simon Waters wrote about Re: hostap_plx switching off encryption?

> The issue from a WISP perspective is what is left in
> /etc/network/wireless.config ENC and KEY setting, when
> encryption is switched off in the menu's (after being on)
> doesn't leave me with an access point with encryption disabled.
> It is possible to vi out the fields, and then things work okay
> on a reboot, but I think this is more a workaround, I don't
> think WISP needs modifying, I think it issues the right
> commands, but they have the wrong effect.

Ok, by your description it looks like the problem is with driver (or may
be with iwconfig). Encryption mode is set after a key is configured so
according to iwconfig's man pages encryption should be turned off in your
case. 

However the driver used in current public release of WISP-Dist is quite
old - I was waiting for things to get stable. I have a new test image,
e-mail off-list and I will give it to you for testing. 

-- 
Best Regards
Vladimir Ivaschenko
http://www.hazard.maks.net/



From jkmaline  Fri Dec 13 12:49:42 2002
From: jkmaline (Jouni Malinen)
Date: Fri, 13 Dec 2002 22:49:42 +0200
Subject: hostap_plx switching off encryption?
In-Reply-To: <20021213214409.A12766@hzdhome.home.blkseanet.ru>; from hazard@hazard.maks.net on Fri, Dec 13, 2002 at 09:44:09PM +0200
References: <200212111208.41730.praedor@yahoo.com> <3DF887F2.2010108@web.de> <20021213033519.GA1067@jm.kir.nu> <3DF97108.2B627E3B@wretched.demon.co.uk> <20021213165647.A12583@hzdhome.home.blkseanet.ru> <3DF9FBFE.CD3C02CC@wretched.demon.co.uk> <20021213214409.A12766@hzdhome.home.blkseanet.ru>
Message-ID: <20021213224942.A9404@jm.epitest.fi>

On Fri, Dec 13, 2002 at 05:32:56AM +0000, Simon Waters wrote:

> Should both "iwconfig wlan0 key off" and "iwconfig wlan0 enc
> off" switch off encryption, I couldn't persuade WISP to do this
> when hostap_plx was in MASTER mode, in the end I had to "vi
> /etc/network/wireless.config", commit to flash, and reboot.

Yes, those should switch off encryption.


On Fri, Dec 13, 2002 at 09:44:09PM +0200, Vladimir Ivaschenko wrote:

> Ok, by your description it looks like the problem is with driver (or may
> be with iwconfig).

I assumed that this was a problem in getting proper iwconfig commands
executed.. I'm not familiar with WISP, so I do not have an idea how it
is doing the configuration. Could you please list all iwconfig commands
that are run (and in which order they are run) to make it easier to
verify whether this really is a driver issue or not?
 
-- 
Jouni Malinen                                            PGP id EFC895FA



From hazard  Fri Dec 13 12:58:01 2002
From: hazard (Vladimir Ivaschenko)
Date: Fri, 13 Dec 2002 22:58:01 +0200
Subject: hostap_plx switching off encryption?
In-Reply-To: <20021213224942.A9404@jm.epitest.fi>
References: <200212111208.41730.praedor@yahoo.com> <3DF887F2.2010108@web.de> <20021213033519.GA1067@jm.kir.nu> <3DF97108.2B627E3B@wretched.demon.co.uk> <20021213165647.A12583@hzdhome.home.blkseanet.ru> <3DF9FBFE.CD3C02CC@wretched.demon.co.uk> <20021213214409.A12766@hzdhome.home.blkseanet.ru> <20021213224942.A9404@jm.epitest.fi>
Message-ID: <20021213225801.A12837@hzdhome.home.blkseanet.ru>

Fri, Dec 13, 2002 at 10:49:42PM +0200 Jouni Malinen wrote about Re: hostap_plx switching off encryption?

> I assumed that this was a problem in getting proper iwconfig commands
> executed.. I'm not familiar with WISP, so I do not have an idea how it
> is doing the configuration. Could you please list all iwconfig commands
> that are run (and in which order they are run) to make it easier to
> verify whether this really is a driver issue or not?

Jouni,

I will investigate it myself and let you know. The driver used in the
latest official WISP-Dist release is quite old (2002-05-16 with a couple
of bugfixes).

The order is as follows:

iwconfig [iface] key [KEY]
iwconfig [iface] key off

-- 
Best Regards
Vladimir Ivaschenko
http://www.hazard.maks.net/



From jt  Fri Dec 13 14:54:06 2002
From: jt (Jean Tourrilhes)
Date: Fri, 13 Dec 2002 14:54:06 -0800
Subject: hostap_plx switching off encryption?
Message-ID: <20021213225406.GA28335@bougret.hpl.hp.com>

Vladimir Ivaschenko wrote :
> 
> Ok, by your description it looks like the problem is with driver (or may
> be with iwconfig). Encryption mode is set after a key is configured so
> according to iwconfig's man pages encryption should be turned off in your
> case. 

	Bug in iwconfig v23, please upgrade to v24 or v25. Check
release notes on my web page for details.
	Good luck...

	Jean




From Simon  Fri Dec 13 07:25:50 2002
From: Simon (Simon Waters)
Date: Fri, 13 Dec 2002 15:25:50 +0000
Subject: hostap_plx switching off encryption?
References: <200212111208.41730.praedor@yahoo.com> <3DF887F2.2010108@web.de> <20021213033519.GA1067@jm.kir.nu> <3DF97108.2B627E3B@wretched.demon.co.uk> <20021213165647.A12583@hzdhome.home.blkseanet.ru>
Message-ID: <3DF9FBFE.CD3C02CC@wretched.demon.co.uk>

Vladimir Ivaschenko wrote:
> 
> As far as I understand you're talking about WISP-Dist. I'm the developer
> of this distribution. 

Big thanks! It is brillant.

> To be honest from your description I don't
> understand whether the problem is in the WISP-Dist or in the driver.

I'm not 100% sure either, but I think the driver/firmware is
misbehaving, as I can't switch off encryption with iwconfig at
the command line. It could also be iwconfig/wireless tools or
me.

(I loaded the hacked 1.4.9 for Linksys card on PLX I found
lurking in the list, although it looks like others found a
download at Intersil that works).

When I understand what is wrong with iwconfig I'll let you know
if the scripts in WISP need changing!

The issue from a WISP perspective is what is left in
/etc/network/wireless.config ENC and KEY setting, when
encryption is switched off in the menu's (after being on)
doesn't leave me with an access point with encryption disabled.
It is possible to vi out the fields, and then things work okay
on a reboot, but I think this is more a workaround, I don't
think WISP needs modifying, I think it issues the right
commands, but they have the wrong effect.

I can't believe I'm alone with this configuration of hardware,
does anyone else has a hostap_plx with Linksys PLX and ver 3.0
PCMCIA cards, where "iwconfig wlan0 enc off" doesn't seem to
work?



From hostap  Fri Dec 13 13:33:59 2002
From: hostap (Carsten Tschach)
Date: Fri, 13 Dec 2002 22:33:59 +0100
Subject: hostap_plx switching off encryption?
Message-ID: <20021213213359.GA3287742@Tschach.com>

> The order is as follows:
> 
> iwconfig [iface] key [KEY]
> iwconfig [iface] key off

I had a similar problem - I wanted to delete the key while testing. It doesn't
work the way it was said in the man-page, but the following worked for
me:

	iwconfig wlan0 key "s:mykey" off

Hope this might be the solution for your problem...

Bye, Carsten



From Pavel.Vondricka  Fri Dec 13 19:53:49 2002
From: Pavel.Vondricka (Pavel Vondricka)
Date: Sat, 14 Dec 2002 02:53:49 -0100
Subject: TXPOWER has no impact on ZCOM XI-325H?
Message-ID: <200212140253.49324.Pavel.Vondricka@ff.cuni.cz>

Hi!
I have a problem with my ZCOM PCMCIA card XI-325H. It seems everything works, 
I just couldn't measure any changes in the strength of received signal on 
another computer when I changed the TXPOWER setting in the master mode. The 
numbers change in my iwconfig, but the other computer receives always the 
same signal.

I'm using kernel 2.4.20 (with standard WE14) with an ACPI patch (because of my 
notebook), pcmcia-cs 3.2.3, wireless tools v25. The base of the system is 
RedHat 8.0.

Any ideas what's wrong? Is it possible to change the txpower dynamically or do 
I have to "restart" or "reset" anything? What?

Thanks,
Pavel

-- 
###########################################################################
# mailto:Pavel.Vondricka at ff.cuni.cz / ICQ:143159880 
# http://web.ff.cuni.cz/~vondric
#
# Muzete mi psat cesky s libovolnym kodovanim (UTF-8, ISO-8859-2,
# windows-1250, atd. ...)
###########################################################################



From hazard  Fri Dec 13 17:59:41 2002
From: hazard (Vladimir Ivaschenko)
Date: Sat, 14 Dec 2002 03:59:41 +0200
Subject: TXPOWER has no impact on ZCOM XI-325H?
In-Reply-To: <200212140253.49324.Pavel.Vondricka@ff.cuni.cz>
References: <200212140253.49324.Pavel.Vondricka@ff.cuni.cz>
Message-ID: <20021214035941.A13198@hzdhome.home.blkseanet.ru>

XI-325H uses its own amplifier design and you cannot control it's output
power (at least it's not documented). 

Sat, Dec 14, 2002 at 02:53:49AM -0100 Pavel Vondricka wrote about TXPOWER has no impact on ZCOM XI-325H?

> Hi!
> I have a problem with my ZCOM PCMCIA card XI-325H. It seems everything works, 
> I just couldn't measure any changes in the strength of received signal on 
> another computer when I changed the TXPOWER setting in the master mode. The 
> numbers change in my iwconfig, but the other computer receives always the 
> same signal.
> 
> I'm using kernel 2.4.20 (with standard WE14) with an ACPI patch (because of my 
> notebook), pcmcia-cs 3.2.3, wireless tools v25. The base of the system is 
> RedHat 8.0.
> 
> Any ideas what's wrong? Is it possible to change the txpower dynamically or do 
> I have to "restart" or "reset" anything? What?
> 
> Thanks,
> Pavel
> 
> -- 
> ###########################################################################
> # mailto:Pavel.Vondricka at ff.cuni.cz / ICQ:143159880 
> # http://web.ff.cuni.cz/~vondric
> #
> # Muzete mi psat cesky s libovolnym kodovanim (UTF-8, ISO-8859-2,
> # windows-1250, atd. ...)
> ###########################################################################
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

-- 
Best Regards
Vladimir Ivaschenko
http://www.hazard.maks.net/



From hazard  Fri Dec 13 18:23:22 2002
From: hazard (Vladimir Ivaschenko)
Date: Sat, 14 Dec 2002 04:23:22 +0200
Subject: TXPOWER has no impact on ZCOM XI-325H?
In-Reply-To: <200212140315.25496.Pavel.Vondricka@ff.cuni.cz>
References: <200212140253.49324.Pavel.Vondricka@ff.cuni.cz> <20021214035941.A13198@hzdhome.home.blkseanet.ru> <200212140315.25496.Pavel.Vondricka@ff.cuni.cz>
Message-ID: <20021214042322.A1039@hzdhome.home.blkseanet.ru>

Sat, Dec 14, 2002 at 03:15:25AM -0100 Pavel Vondricka wrote about Re: TXPOWER has no impact on ZCOM XI-325H?

> > XI-325H uses its own amplifier design and you cannot control it's output
> > power (at least it's not documented).
> 
> Are you sure about it?

I got this info from a person with direct contact with Z-Com.

> Is it the same for XI-325 as well? They told me the card is the same as XI-626 
> where it works!

I guess so. XI-626 looks to be a PCI card based on standard Intersil
Prism2 design (14 dBm), so it's not surprising that it will work. 

-- 
Best Regards
Vladimir Ivaschenko
http://www.hazard.maks.net/



From hazard  Fri Dec 13 18:36:34 2002
From: hazard (Vladimir Ivaschenko)
Date: Sat, 14 Dec 2002 04:36:34 +0200
Subject: TXPOWER has no impact on ZCOM XI-325H?
In-Reply-To: <200212140327.28181.Pavel.Vondricka@ff.cuni.cz>
References: <200212140253.49324.Pavel.Vondricka@ff.cuni.cz> <200212140315.25496.Pavel.Vondricka@ff.cuni.cz> <20021214042322.A1039@hzdhome.home.blkseanet.ru> <200212140327.28181.Pavel.Vondricka@ff.cuni.cz>
Message-ID: <20021214043634.A1378@hzdhome.home.blkseanet.ru>

Sat, Dec 14, 2002 at 03:27:28AM -0100 Pavel Vondricka wrote about Re: TXPOWER has no impact on ZCOM XI-325H?

> > I guess so. XI-626 looks to be a PCI card based on standard Intersil
> > Prism2 design (14 dBm), so it's not surprising that it will work.
> 
> The basic version XI-325 should be completely the same as XI-626. Same output 
> power, aso. So, is it or is it not? Can I change the output power there?

XI-325 uses Prism 2.5 chipset which has much better sensitivity (and,
according to my tests, stability). Also there is 100 mW version, I'm not
sure if they label it as XI-325H or not. 

> BTW: I thought that XI-325H also has Intersils Prism chipset. Or is it just 
> the amplifier that is different?

It is. The amplifier part is different.

-- 
Best Regards
Vladimir Ivaschenko
http://www.hazard.maks.net/



From matrix  Fri Dec 13 19:19:31 2002
From: matrix (Francois Gurin)
Date: Fri, 13 Dec 2002 22:19:31 -0500
Subject: [HostAP]  Still no ap action going on here :( help please.
In-Reply-To: <200212121525.40166.linux@rocksolidnetworks.com>
References: <200212121525.40166.linux@rocksolidnetworks.com>
Message-ID: <20021214031930.GH22559@shot.org>

On Thu, Dec 12, 2002 at 03:25:40PM -0800, Linux Rocks! wrote:
> Hi,
> 	Im still not having any luck with any linux modules for my Proxim RangeLan-DS 
> PC Cards. Im really unsure what Im doing wrong. 

> hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
                         ^^^^^^^

> Note: I need the ignore_cis_vcc=1 or I get a bunch of nasty errors!


the rangelan-ds is a 3.3v only card.  i've completely toasted one (looks 
like the firmware is gone) and partially toasted another (it looks like 
it works, but gets mac errors, and has busted a previously working pcmcia 
controller during debug) when ran at 5v.  

--francois






From linux  Fri Dec 13 19:46:33 2002
From: linux (Linux Rocks!)
Date: Fri, 13 Dec 2002 19:46:33 -0800
Subject: [HostAP]  Still no ap action going on here :( help please.
In-Reply-To: <20021214031930.GH22559@shot.org>
References: <200212121525.40166.linux@rocksolidnetworks.com> <20021214031930.GH22559@shot.org>
Message-ID: <200212131937.56510.linux@rocksolidnetworks.com>

Hmm... that doesnt sound good. It makes me wonder... why does it work fine in 
windows?
Has anyone ever really gotten these cards to work under linux? ifso, how?
Is there something I can change in the source for either hostap, or pcmcia to 
make  it work, like it does in windows? 
This is pretty frustrating... Ive tried to get these cards working under linux 
for over 6 months, yet windows (yetch!) it works fine (but heck... cant 
really do much usefull in windows

Jamie

On Friday 13 December 2002 07:19 pm, Francois Gurin wrote:
: On Thu, Dec 12, 2002 at 03:25:40PM -0800, Linux Rocks! wrote:
: > Hi,
: > 	Im still not having any luck with any linux modules for my Proxim
: > RangeLan-DS PC Cards. Im really unsure what Im doing wrong.
: >
: > hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
:
:                          ^^^^^^^
:
: > Note: I need the ignore_cis_vcc=1 or I get a bunch of nasty errors!
:
: the rangelan-ds is a 3.3v only card.  i've completely toasted one (looks
: like the firmware is gone) and partially toasted another (it looks like
: it works, but gets mac errors, and has busted a previously working pcmcia
: controller during debug) when ran at 5v.
:
: --francois
:
:
:
: _______________________________________________
: HostAP mailing list
: HostAP at shmoo.com
: http://lists.shmoo.com/mailman/listinfo/hostap

-- 
No microsoft products were used to produce this message.
EUG-LUG Mailing List:
http://mailman.efn.org/cgi-bin/listinfo/eug-lug




From matrix  Fri Dec 13 20:48:29 2002
From: matrix (Francois Gurin)
Date: Fri, 13 Dec 2002 23:48:29 -0500
Subject: [HostAP]  Re: [HostAP]  Still no ap action going on here :( help please.
In-Reply-To: <200212131937.56510.linux@rocksolidnetworks.com>
References: <200212121525.40166.linux@rocksolidnetworks.com> <20021214031930.GH22559@shot.org> <200212131937.56510.linux@rocksolidnetworks.com>
Message-ID: <20021214044829.GI22559@shot.org>

the rangelan-ds cards work perfectly in linux with the hostap drivers.  I've
been using them for over a year now.  however, not all laptops support
3.3v pcmcia cards. 

if it works under windows but not linux (assuming the same machine), i would
venture pcmcia-cs can't set vcc to 3.3v for some reason even tho the hardware
is capable of it. i've never experienced this before, usually i'm stuck
with older 5v/12v slots that just don't electrically support 3.3v operation.

the plastic ridgeson the front end of the rangelan is spaced differently 
than most other pcmcia cards.  apparently this is to prevent sticking a
3.3v only card into a 5v/12v slot. 

the culprit here isn't hostap, it's your pcmcia configuration.  if you're 
using the kernel pcmcia system, try the userland pcmcia or vice versa.

forcing this card with ignore_cis_vcc is not a safe idea

--francois

On Fri, Dec 13, 2002 at 07:46:33PM -0800, Linux Rocks! wrote:
> Hmm... that doesnt sound good. It makes me wonder... why does it work fine in 
> windows?
> Has anyone ever really gotten these cards to work under linux? ifso, how?
> Is there something I can change in the source for either hostap, or pcmcia to 
> make  it work, like it does in windows? 
> This is pretty frustrating... Ive tried to get these cards working under linux 
> for over 6 months, yet windows (yetch!) it works fine (but heck... cant 
> really do much usefull in windows
> 
> Jamie
> 
> On Friday 13 December 2002 07:19 pm, Francois Gurin wrote:
> : On Thu, Dec 12, 2002 at 03:25:40PM -0800, Linux Rocks! wrote:
> : > Hi,
> : > 	Im still not having any luck with any linux modules for my Proxim
> : > RangeLan-DS PC Cards. Im really unsure what Im doing wrong.
> : >
> : > hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
> :
> :                          ^^^^^^^
> :
> : > Note: I need the ignore_cis_vcc=1 or I get a bunch of nasty errors!
> :
> : the rangelan-ds is a 3.3v only card.  i've completely toasted one (looks
> : like the firmware is gone) and partially toasted another (it looks like
> : it works, but gets mac errors, and has busted a previously working pcmcia
> : controller during debug) when ran at 5v.
> :
> : --francois
> :
> :
> :
> : _______________________________________________
> : HostAP mailing list
> : HostAP at shmoo.com
> : http://lists.shmoo.com/mailman/listinfo/hostap
> 
> -- 
> No microsoft products were used to produce this message.
> EUG-LUG Mailing List:
> http://mailman.efn.org/cgi-bin/listinfo/eug-lug
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap



From salil  Fri Dec 13 21:42:57 2002
From: salil (Salil Gokhale)
Date: Sat, 14 Dec 2002 00:42:57 -0500 (EST)
Subject: hostap bridging wired and wireless network query
Message-ID: <Pine.GSO.4.33.0212140030040.7790-100000@compserv1>

hello

I have set up an access point using hostap. My laptop also has an ethernet
conenction. My machine has static IP 130.245.126.245 .I want to establish
bridging between wlan and wired lan.

I used the following commands to setup the bridge

brctl addbr br0
brctl addif br0 eth0
brctl addif br0 wlan0

ifconfig eth0 0.0.0.0
ifconfig wlan0 0.0.0.0

ifconfig br0 130.245.126.245 up

After these steps I cannot access network even from the access point
machine. Also I cannot access network from any machine on wlan.

Am I missing something?
Do I need to setup gateway or routes on access point or other machines?

My configuration

access point on Dell Inspiron, kernel 2.4.19, hostap 09/12, pcmcia cs-
3.1.34


Thanks in advance
Salil Gokhale




From hazard  Sat Dec 14 03:21:14 2002
From: hazard (Vladimir Ivaschenko)
Date: Sat, 14 Dec 2002 13:21:14 +0200
Subject: TXPOWER has no impact on ZCOM XI-325H?
In-Reply-To: <200212140342.16769.Pavel.Vondricka@ff.cuni.cz>
References: <200212140253.49324.Pavel.Vondricka@ff.cuni.cz> <200212140327.28181.Pavel.Vondricka@ff.cuni.cz> <20021214043634.A1378@hzdhome.home.blkseanet.ru> <200212140342.16769.Pavel.Vondricka@ff.cuni.cz>
Message-ID: <20021214132114.A1788@hzdhome.home.blkseanet.ru>

Sat, Dec 14, 2002 at 03:42:16AM -0100 Pavel Vondricka wrote about Re: TXPOWER has no impact on ZCOM XI-325H?
> > XI-325 uses Prism 2.5 chipset which has much better sensitivity (and,
> > according to my tests, stability). Also there is 100 mW version, I'm not
> > sure if they label it as XI-325H or not.
> 
> Yes. XI-325H is the 100mW version of XI-325, which should be the PCMCIA 

There is also 200mW version.

> version of XI-626. They all are told to use the Prism 2.5 chipset. So it 

No, I think that the PCMCIA version of XI-626 is XI-300.

-- 
Best Regards
Vladimir Ivaschenko
http://www.hazard.maks.net/



From jason  Sat Dec 14 06:07:04 2002
From: jason (Jason Straight)
Date: Sat, 14 Dec 2002 09:07:04 -0500
Subject: TXPOWER has no impact on ZCOM XI-325H?
In-Reply-To: <20021214132114.A1788@hzdhome.home.blkseanet.ru>
References: <200212140253.49324.Pavel.Vondricka@ff.cuni.cz> <200212140342.16769.Pavel.Vondricka@ff.cuni.cz> <20021214132114.A1788@hzdhome.home.blkseanet.ru>
Message-ID: <200212140907.09248.jason@jeetkunedomaster.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 14 December 2002 06:21, Vladimir Ivaschenko wrote:
> There is also 200mW version.

There are 3 versions actually, with the 2.5 chipset - 325(32mW/15dBm), 325H 
(100mW/20dBm), 325HP(200mW/23dBm).

Where I work we are phasing out using orinoco for the zcomax cards.


- -- 
Jason Straight
ICQ: 1796276
PGP: http://www.jeetkunedomaster.net/~jason/pubkey.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iQCVAwUBPfs7DRFHZPcobeHxAQLVdAP/fYnB8Up2YS3m1rNDYYksQUYYBCqKuJLK
HjgUORXOWPSlMb82qrLK+jAiDeng4cTnlZ/iV1SYNI9ZfsEfAnQeV2OezuXo3onk
GfnopOt2MBzeUSK8l9CnZdQF08hV87PRm40RtFcFkmMqTHfGE47pwapYgCrop6sO
NVzmqnPhoqs=
=Bnjc
-----END PGP SIGNATURE-----




From ghuntress  Sat Dec 14 06:06:51 2002
From: ghuntress (Gary Huntress)
Date: Sat, 14 Dec 2002 09:06:51 -0500
Subject: Linksys WPC 11  
Message-ID: <003501c2a37a$0c94a140$0200a8c0@springfield>

I am trying to use the hostap driver with a linksys wpc11.   This is on an
IBM Thinkpad running a very stock installation of RH 7.3 (installed fresh).

Here is what I have done

1) download and unpack hostap-2002-10-12
2) make pccard ran ok with no errors
3) make install_pccard ran ok with no errors
4) I restarted cargmgr and inserted card and it was detected, lsmod returns:
        hostap_cs (unused)
        hostap        [hostap_cs]
        hostap_crypt    [hostap]

5)  I see only successful messages in /var/log/messages;
        "executing './network start wlan0'
        "hostap_cs: index 0x01: vcc 5.0, irq3, io 0x01 80-0x01bf
        "hostap_cs: Registered netdevice wlan0"
        "/etc/hotplug/net.agent:   invoke ifup wlan0"

5)  iwconfig returns only lo and I am not online.

6)  Using cardctl ident I verified that my manfid (0x0274, 0x1613) is in
/etc/hostap_cs.conf, but the entry did not seem to have the exact card
title, so I added the info reported by cardctl :
    card "The Linksys Group, Inc."
    version "Instant Wireless Network PC Card", "ISL37300P", "RevA"
    manfid 0x0274, 0x1613
    bind "hostap_cs"

after adding that, I restarted cardmgr again and see the same thing.

I'm still offline and totally out of ideas.  Can anyone tell me how I should
continue troubleshooting this?


Thanks!


Gary




From jasonb  Sat Dec 14 07:50:31 2002
From: jasonb (Jason Boxman)
Date: Sat, 14 Dec 2002 10:50:31 -0500
Subject: Linksys WPC 11
In-Reply-To: <003501c2a37a$0c94a140$0200a8c0@springfield>
References: <003501c2a37a$0c94a140$0200a8c0@springfield>
Message-ID: <200212141050.31897.jasonb@edseek.com>

On Saturday 14 December 2002 09:06 am, Gary Huntress wrote:
> I am trying to use the hostap driver with a linksys wpc11.   This is on an
> IBM Thinkpad running a very stock installation of RH 7.3 (installed fresh).
>
<snip>
> I'm still offline and totally out of ideas.  Can anyone tell me how I
> should continue troubleshooting this?

What happens if you use ifconfig to give wlan0 an IP?

If it loaded successfully you ought to be able to run ifconfig -a and see the 
interface even without an IP.

>
> Thanks!
>
>
> Gary

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages





From ghuntress  Sat Dec 14 09:30:25 2002
From: ghuntress (Gary Huntress)
Date: Sat, 14 Dec 2002 12:30:25 -0500
Subject: Linksys WPC 11
References: <003501c2a37a$0c94a140$0200a8c0@springfield> <200212141050.31897.jasonb@edseek.com>
Message-ID: <000901c2a396$7d69c1e0$0200a8c0@springfield>

Thanks for the reply.  I'm sure that part of the problem is my lack of
understanding of the detection and iwconfig/ifconfig process.

After booting, I insert the card and iwconfig does not list wlan0 as I
expected (I assumed this must occur before I can ifconfig).   Ifconfig -a
does list wlan0 but with no ip address.

Someone suggested that I do:

    iwconfig wlan0 mode managed

And then I did

    ifconfig wlan0 192.168.0.45

both completed without error, but clearly something is wrong because
iwconfig reports the access point as 44:44:44:44:44:44.   (but ifconfig
reports 966 RX packets!)


The only other problem I notice is that if I eject the card I get:

    hostap_cs:   release postponed wlan0 still locked

and I can't reinsert the card :
    requestID : resource in use





----- Original Message -----
From: "Jason Boxman" <jasonb at edseek.com>
To: <hostap at shmoo.com>
Sent: Saturday, December 14, 2002 10:50 AM
Subject: Re: Linksys WPC 11


On Saturday 14 December 2002 09:06 am, Gary Huntress wrote:
> I am trying to use the hostap driver with a linksys wpc11.   This is on an
> IBM Thinkpad running a very stock installation of RH 7.3 (installed
fresh).
>
<snip>
> I'm still offline and totally out of ideas.  Can anyone tell me how I
> should continue troubleshooting this?

What happens if you use ifconfig to give wlan0 an IP?

If it loaded successfully you ought to be able to run ifconfig -a and see
the
interface even without an IP.

>
> Thanks!
>
>
> Gary

--

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages


_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap




From ghuntress  Sat Dec 14 10:05:24 2002
From: ghuntress (Gary Huntress)
Date: Sat, 14 Dec 2002 13:05:24 -0500
Subject: Linksys WPC 11 -  Followup
References: <003501c2a37a$0c94a140$0200a8c0@springfield> <200212141050.31897.jasonb@edseek.com> <000901c2a396$7d69c1e0$0200a8c0@springfield>
Message-ID: <004e01c2a39b$60991a20$0200a8c0@springfield>

I'm not sure what I have done differently (because I haven't really changed
anything) but now iwconfig reports  an access point of 00:06:25:A8:F7:CE
which tells me that my basic connectivity is ok.

ifconfig shows wlan0 with the IP of 192.168.0.45 and I added the default
gateway again but I still can't even ping the gateway (192.168.0.1)

This seems less like a wireless problem and more like a plain old networking
problem, but I still don't know what to do next!




----- Original Message -----
From: "Gary Huntress" <ghuntress at attbi.com>
To: <jasonb at edseek.com>; <hostap at shmoo.com>
Sent: Saturday, December 14, 2002 12:30 PM
Subject: Re: Linksys WPC 11


> Thanks for the reply.  I'm sure that part of the problem is my lack of
> understanding of the detection and iwconfig/ifconfig process.
>
> After booting, I insert the card and iwconfig does not list wlan0 as I
> expected (I assumed this must occur before I can ifconfig).   Ifconfig -a
> does list wlan0 but with no ip address.
>
> Someone suggested that I do:
>
>     iwconfig wlan0 mode managed
>
> And then I did
>
>     ifconfig wlan0 192.168.0.45
>
> both completed without error, but clearly something is wrong because
> iwconfig reports the access point as 44:44:44:44:44:44.   (but ifconfig
> reports 966 RX packets!)
>
>
> The only other problem I notice is that if I eject the card I get:
>
>     hostap_cs:   release postponed wlan0 still locked
>
> and I can't reinsert the card :
>     requestID : resource in use
>
>
>
>
>
> ----- Original Message -----
> From: "Jason Boxman" <jasonb at edseek.com>
> To: <hostap at shmoo.com>
> Sent: Saturday, December 14, 2002 10:50 AM
> Subject: Re: Linksys WPC 11
>
>
> On Saturday 14 December 2002 09:06 am, Gary Huntress wrote:
> > I am trying to use the hostap driver with a linksys wpc11.   This is on
an
> > IBM Thinkpad running a very stock installation of RH 7.3 (installed
> fresh).
> >
> <snip>
> > I'm still offline and totally out of ideas.  Can anyone tell me how I
> > should continue troubleshooting this?
>
> What happens if you use ifconfig to give wlan0 an IP?
>
> If it loaded successfully you ought to be able to run ifconfig -a and see
> the
> interface even without an IP.
>
> >
> > Thanks!
> >
> >
> > Gary
>
> --
>
> Jason Boxman
> Administrator TrekWeb.COM
> http://trekweb.com/~jasonb/articles/ - Linux Pages
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From ghuntress  Sat Dec 14 10:11:59 2002
From: ghuntress (Gary Huntress)
Date: Sat, 14 Dec 2002 13:11:59 -0500
Subject: Linksys WPC 11
References: <003501c2a37a$0c94a140$0200a8c0@springfield> <200212141050.31897.jasonb@edseek.com> <000901c2a396$7d69c1e0$0200a8c0@springfield>
Message-ID: <005701c2a39c$4bcac200$0200a8c0@springfield>

Ok....minor success.....  iwconfig reported mode master, rather than mode
managed, and now I can get online ok.

However the secondary problem that I reported in my original email still
persists that if I unplug the card I get "hostap_cs:  release postponed" and
I can't plug it back in.

what would I need to do to properly release the driver?

Gary



----- Original Message -----
From: "Gary Huntress" <ghuntress at attbi.com>
To: <jasonb at edseek.com>; <hostap at shmoo.com>
Sent: Saturday, December 14, 2002 12:30 PM
Subject: Re: Linksys WPC 11


> Thanks for the reply.  I'm sure that part of the problem is my lack of
> understanding of the detection and iwconfig/ifconfig process.
>
> After booting, I insert the card and iwconfig does not list wlan0 as I
> expected (I assumed this must occur before I can ifconfig).   Ifconfig -a
> does list wlan0 but with no ip address.
>
> Someone suggested that I do:
>
>     iwconfig wlan0 mode managed
>
> And then I did
>
>     ifconfig wlan0 192.168.0.45
>
> both completed without error, but clearly something is wrong because
> iwconfig reports the access point as 44:44:44:44:44:44.   (but ifconfig
> reports 966 RX packets!)
>
>
> The only other problem I notice is that if I eject the card I get:
>
>     hostap_cs:   release postponed wlan0 still locked
>
> and I can't reinsert the card :
>     requestID : resource in use
>
>
>
>
>
> ----- Original Message -----
> From: "Jason Boxman" <jasonb at edseek.com>
> To: <hostap at shmoo.com>
> Sent: Saturday, December 14, 2002 10:50 AM
> Subject: Re: Linksys WPC 11
>
>
> On Saturday 14 December 2002 09:06 am, Gary Huntress wrote:
> > I am trying to use the hostap driver with a linksys wpc11.   This is on
an
> > IBM Thinkpad running a very stock installation of RH 7.3 (installed
> fresh).
> >
> <snip>
> > I'm still offline and totally out of ideas.  Can anyone tell me how I
> > should continue troubleshooting this?
>
> What happens if you use ifconfig to give wlan0 an IP?
>
> If it loaded successfully you ought to be able to run ifconfig -a and see
> the
> interface even without an IP.
>
> >
> > Thanks!
> >
> >
> > Gary
>
> --
>
> Jason Boxman
> Administrator TrekWeb.COM
> http://trekweb.com/~jasonb/articles/ - Linux Pages
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From jasonb  Sat Dec 14 10:15:15 2002
From: jasonb (Jason Boxman)
Date: Sat, 14 Dec 2002 13:15:15 -0500
Subject: Linksys WPC 11
In-Reply-To: <005701c2a39c$4bcac200$0200a8c0@springfield>
References: <003501c2a37a$0c94a140$0200a8c0@springfield> <000901c2a396$7d69c1e0$0200a8c0@springfield> <005701c2a39c$4bcac200$0200a8c0@springfield>
Message-ID: <200212141315.15852.jasonb@edseek.com>

On Saturday 14 December 2002 01:11 pm, Gary Huntress wrote:
> Ok....minor success.....  iwconfig reported mode master, rather than mode
> managed, and now I can get online ok.
>
> However the secondary problem that I reported in my original email still
> persists that if I unplug the card I get "hostap_cs:  release postponed"
> and I can't plug it back in.
>
> what would I need to do to properly release the driver?

My guess would be that the hostap modules are still loaded when you remove the 
card, so you can't plug it back in.  But it's only a guess.  You can do an 
'lsmod' after you remove the device to be sure.  (I've yet to use Linux on my 
laptop.)

> Gary
>
>
>
<snip>

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages





From pbrossin  Sat Dec 14 10:52:35 2002
From: pbrossin (Pierrick Brossin)
Date: Sat, 14 Dec 2002 19:52:35 +0100
Subject: I assume it's not working on linux side
Message-ID: <3DFB7DF2.1060401@swissgeeks.com>

Hey!

I've installed hostap on my machine.
I use hostap_plx with a US.Robotics Adapter and a PCMCIA Card (USR2410).

Here is my problem.
I managed to make hostap work and it work quiet a long time but I had
the bad idea to reboot my server and it won't work anymore.
I can load the module and set the parameters for wlan0 but no PC can
connect to my AP. I've tried with FreeBSD and Windows... I assume it
would be same thing with Linux as client.
btw I have a 2.4.18-5 Kernel...

Here is what I'm doing:

cd /lib/modules/2.4.18-5/net
modprobe hostap_plx
cd /
ifconfig wlan0 10.0.1.1 netmask 255.255.255.0
iwconfig wlan0 channel 11
iwconfig wlan0 mode Master
iwpriv   wlan0 maccmd 1
iwpriv   wlan0 maccmd 4
iwpriv   wlan0 addmac 00:90:XX:XX:XX:XX
iwconfig wlan0 key XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX
iwconfig wlan0

On the FreeBSD side I made a shell script (which worked perfectly before
the reboot of my Linux server) so I KNOW it's not the problem.

The Mac Address is the one written after 'iwpriv wlan0 addmac' and the
WEP key is the also the same on my FreeBSD laptop and is activated
(wicontrol -k XX.... and then wicontrol -e 1).

I had the same thing once and managed after many hours to make it work
again but I'm not able to find what I've done..

If someone could help I'd really appreciate.

Thanks




From khoff  Sat Dec 14 11:14:17 2002
From: khoff (Kristian Hoffmann)
Date: Sat, 14 Dec 2002 11:14:17 -0800 (PST)
Subject: TXPOWER has no impact on ZCOM XI-325H?
In-Reply-To: <200212140907.09248.jason@jeetkunedomaster.net>
Message-ID: <Pine.LNX.4.44.0212141112160.4628-100000@luaren.pc-intouch.com>

On Sat, 14 Dec 2002, Jason Straight wrote:

>
> There are 3 versions actually, with the 2.5 chipset - 325(32mW/15dBm), 325H
> (100mW/20dBm), 325HP(200mW/23dBm).
>
> Where I work we are phasing out using orinoco for the zcomax cards.

I have used the XI-325, XI-325H, and XI-626 with great results.  XI-626 is
what we're currently using for all APs because of the stability,
seperation, and better heat dissapation with the PCI cards.

-Kristian




From doug  Sat Dec 14 12:49:59 2002
From: doug (Doug Yeager)
Date: Sat, 14 Dec 2002 15:49:59 -0500
Subject: using a bridge....i think
Message-ID: <4.3.2.7.0.20021214154938.034cd850@yeagerautomation.com>

k, for all those network designers out there. i think this question is 
fairly simple one.
i have an appartment complex that wants wireless. i've never put it more 
than one access point...but this will require more than one. i would think 
it is really neat if you could roam between them but it is o.k. if you 
can't...not a biggy.
what i want to do is this:
T1 coming into the building to an access point. then i want to place other 
AP's in various rooms in the building acting as AP's also because it is 
bigger than a radius of 300 feet so that one AP could not handle all rooms.
in order to use one T1 internet connection, is it possible to connect AP's 
together without wires? or do i need to wire all AP's together on a wired 
network? it would be totolly great if i could just route all traffic over 
wireless from one AP to another....eliminating the need to wire anything up 
for this.
also, am i getting into a situation where a "bridge" might be required to 
do this. any docs on this and how to use one DHCPD server to handle all 
AP's would be much appreciated.
thx,
doug




From gallir  Sat Dec 14 14:43:16 2002
From: gallir (Ricardo Galli)
Date: Sat, 14 Dec 2002 23:43:16 +0100
Subject: Problems and [possibly] bugs with WDS
Message-ID: <200212142343.16053.gallir@uib.es>

Hi Jouni,
	last days I've playing with WDS and bridging (with 2002-10 estable version) on several computers. 
I followed your examples in README.Prism2. Find the report below.

CONFIGURATION OF BOTH APs

AP-A: ----------------------------------------------------
ponti:~# iwconfig
wlan0     IEEE 802.11-b  ESSID:"Antoli"
          Mode:Master  Frequency:2.437GHz  Access Point: 00:50:C2:01:96:14
          Bit Rate:2Mb/s   Tx-Power:7 dBm   Sensitivity=1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:7569-6264-6D69-6C74-696D-3332-31   Encryption mode:restricted
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1656  Invalid misc:1309   Missed beacon:0

wlan0wds  IEEE 802.11-b  ESSID:"Antoli"
          Mode:Master  Frequency:2.437GHz  Access Point: 00:50:C2:01:96:14
          Bit Rate:2Mb/s   Tx-Power:7 dBm   Sensitivity=1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:7569-6264-6D69-6C74-696D-3332-31   Encryption mode:restricted
          Power Management:off

ponti:~# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.0050c2019614       yes             eth0
                                                        wlan0
                                                        wlan0wds0
----------------------------------------------------

AP-B ------------------------------------------------
raquel:~# iwconfig
wlan0     IEEE 802.11-b  ESSID:"Antoli"  Nickname:"raquel"
          Mode:Master  Frequency:2.437GHz  Access Point: 00:05:5D:D6:4B:DA
          Bit Rate:11Mb/s   Tx-Power:-6 dBm   Sensitivity=1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:7569-6264-6D69-6C74-696D-3332-31   Encryption mode:restricted
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:482  Rx invalid frag:0
          Tx excessive retries:338  Invalid misc:1312   Missed beacon:0

wlan0wds  IEEE 802.11-b  ESSID:"Antoli"  Nickname:"raquel"
          Mode:Master  Frequency:2.437GHz  Access Point: 00:05:5D:D6:4B:DA
          Bit Rate:11Mb/s   Tx-Power:-5 dBm   Sensitivity=1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:7569-6264-6D69-6C74-696D-3332-31   Encryption mode:restricted
          Power Management:off

raquel:~# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.00055dd64bda       yes             wlan0
                                                        wlan0wds0
----------------------------------------------------------------------


PROBLEMS

1. When there is traffic, which is very slow, among the two AP I get the following 
errors in both APs:
...
Dec 14 22:56:18 ponti kernel: wlan0: adding automatic WDS connection to AP 00:05:5d:d6:4b:da
Dec 14 22:56:18 ponti kernel: wlan0: using pre-allocated WDS netdevice wlan0wds0
...
Dec 14 23:16:50 ponti kernel: wlan0: STA 00:05:5d:d6:4b:da TX rate raised to 55
Dec 14 23:16:50 ponti kernel: wlan0: STA 00:05:5d:d6:4b:da TX rate raised to 110
Dec 14 23:16:51 ponti kernel: wlan0: STA 00:05:5d:d6:4b:da TX rate lowered to 55
...
...
Dec 14 23:16:31 raquel kernel: wlan0: STA 00:30:65:1d:e6:3a TX rate lowered to 55
Dec 14 23:16:31 raquel kernel: wlan0: STA 00:30:65:1d:e6:3a TX rate raised to 110
Dec 14 23:16:51 raquel kernel: wlan0: STA 00:50:c2:01:96:14 TX rate lowered to 55
...


2. Sometimes it seems they try to "bypass" wds: 
Dec 14 23:22:07 raquel kernel: wlan0: deauthentication: 00:50:c2:01:96:14 len=2, reason_code=3

3. Sometimes gives the following error:
Dec 14 22:51:27 ponti kernel: AP: packet to non-associated STA 00:40:43:05:66:00
But 00:40:43:05:66:00 is an ethernet! (Nokia ethernet router).

4. If a wireless station C is connected to AP-B:
C ~~~~~ AP-B ~~~wds~~~~~ AP-A
AP-A cannot connect to C for a long period (more than 5 minutes) if 
before was connected to AP-A. I'm not sure if it's a problem of the STP or WDS...


And one not related to WDS: if hostap is compiled as module against 2.4.20 and the 
last pcmcia modules version, hostap_crypt_wep is not loaded automatically.


Regards,

-- 
  ricardo galli       GPG id C8114D34




From jkmaline  Sat Dec 14 15:00:47 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 14 Dec 2002 15:00:47 -0800
Subject: Problems and [possibly] bugs with WDS
In-Reply-To: <200212142343.16053.gallir@uib.es>
References: <200212142343.16053.gallir@uib.es>
Message-ID: <20021214230047.GA1643@jm.kir.nu>

On Sat, Dec 14, 2002 at 11:43:16PM +0100, Ricardo Galli wrote:

> 1. When there is traffic, which is very slow, among the two AP I get the following 
> errors in both APs:

> Dec 14 23:16:50 ponti kernel: wlan0: STA 00:05:5d:d6:4b:da TX rate raised to 55
> Dec 14 23:16:50 ponti kernel: wlan0: STA 00:05:5d:d6:4b:da TX rate raised to 110
> Dec 14 23:16:51 ponti kernel: wlan0: STA 00:05:5d:d6:4b:da TX rate lowered to 55

I would not call these errors.. Automatic TX rate controlling is
lowering the rate whenever a packet is not ACKed and then raising it if
packets are not lost for some time.

> 2. Sometimes it seems they try to "bypass" wds: 
> Dec 14 23:22:07 raquel kernel: wlan0: deauthentication: 00:50:c2:01:96:14 len=2, reason_code=3

That is odd.. It looks like one of the APs sent deauthenticatin frame
even though they should not be authenticated/associated at all in this
kind of configuration.. I haven't seen this happening before. It might
be possible that station firmware is sending deauthentication frame even
in Host AP mode under some circumstances (e.g., when port0 is disabled &
enabled for configuration change).

> 3. Sometimes gives the following error:
> Dec 14 22:51:27 ponti kernel: AP: packet to non-associated STA 00:40:43:05:66:00
> But 00:40:43:05:66:00 is an ethernet! (Nokia ethernet router).

I have also seen this many times. I would assume that Linux bridge code
did not know where to find that hwaddr and decided to send the frame to
all interfaces just in case, or something like this. Host AP driver
would print this if such frame is sent using wlan0 interface.

> 4. If a wireless station C is connected to AP-B:
> C ~~~~~ AP-B ~~~wds~~~~~ AP-A
> AP-A cannot connect to C for a long period (more than 5 minutes) if 
> before was connected to AP-A. I'm not sure if it's a problem of the STP or WDS...

If you mean that C was first associated with AP-A and then reassociated
with AP-B, then I would assume this problem occurs due to AP-A still
having the association up for C. At the moment, old AP does not get
any information when an associated station moves to another AP. IAPP
should eventually remove this problem.

> And one not related to WDS: if hostap is compiled as module against 2.4.20 and the 
> last pcmcia modules version, hostap_crypt_wep is not loaded automatically.

It should be loaded when you are setting up WEP keys, assuming your
module loader is working properly. At least hostap.o should request that
module automatically.

-- 
Jouni Malinen                                            PGP id EFC895FA



From david.goodenough  Sat Dec 14 14:07:17 2002
From: david.goodenough (David Goodenough)
Date: Sat, 14 Dec 2002 22:07:17 +0000
Subject: TXPOWER has no impact on ZCOM XI-325H?
In-Reply-To: <20021214042322.A1039@hzdhome.home.blkseanet.ru>
References: <200212140253.49324.Pavel.Vondricka@ff.cuni.cz> <200212140315.25496.Pavel.Vondricka@ff.cuni.cz> <20021214042322.A1039@hzdhome.home.blkseanet.ru>
Message-ID: <200212150012.PAA29691@archimedes.shmoo.com>

On Saturday 14 December 2002 02:23, you wrote:
</snip>

> I got this info from a person with direct contact with Z-Com.

Could you ask your contact a question for me please.  I understand that
Z-Com produce a PC-104 802.11b, but I can not find it anywhere.  Could
you ask is they have a part number or the like.  I would be most grateful.

David

<snip/>



From brianc  Sat Dec 14 16:34:33 2002
From: brianc (Brian Capouch)
Date: Sat, 14 Dec 2002 19:34:33 -0500
Subject: "prism2" driver on Zaurus PDA
Message-ID: <3DFBCE19.3000607@palaver.net>

I just installed the "Open Zaurus" distribution on my Sharp Zaurus 
5000-D, and am having a bit of trouble with the (older, I'm certain) 
version of the HostAP driver that is installed on that machine.

And I'm further pretty sure I know what the problem is; I just don't 
know if there is anything I can do about it.

The card I put in (a Zcom XI-325) is 5v, but it appears that there is a 
constant setting requiring it to be 3.3?  There is no mention of the 
"cis" stuff in any of the config files in /etc/pcmcia.

Can I just add one like the current hostap_cs.conf, and set ignore_cis to 0?

Below is the dmesg output.  A DLink650 as well as a Mikrotik (Senao) 
200mw card both work just fine, but in both of those cases "cardctl 
status" reports them as 3.3v, not 5.

Thanks if anyone knows a fix. . .

B.


sa1100_pcmcia_init(0)
prism2: prism2.c 0.0.0 2002-05-19 (SSH Communications Security Corp, 
Jouni Malinen)
prism2: (c) SSH Communications Security Corp <jkm at ssh.com>
prism2: setting Vcc=33 (constant)
prism2: CS_EVENT_CARD_INSERTION
prism2_config()
prism2: setting Vcc=33 (from config)
CISTPL_MANFID: 0xd601, 0x0005
Checking CFTABLE_ENTRY 0x01 (default 0x01)
prism2: GetNextTuple: No more items
prism2_release
: card already removed or not configured during shutdown
release - done
prism2_detach




From linux  Sat Dec 14 16:48:56 2002
From: linux (Linux Rocks!)
Date: Sat, 14 Dec 2002 16:48:56 -0800
Subject: PCMCIA....
In-Reply-To: <3DFBCE19.3000607@palaver.net>
References: <3DFBCE19.3000607@palaver.net>
Message-ID: <200212141648.56913.linux@rocksolidnetworks.com>

	I guess my issue currenly is with PCMCIA. Even though the card is 3.3v, and 
the craptops dont support 3.3v(Im guessing its the pcmcia controller). the 
cards do  infact work in windows, so while technicly I have a hardware issue, 
it seems that windows 95 and 98 are able to work around it.
	I Tried writing to David Hinds @ his sourceforge address, but it just bounced 
back :( 
	Is there anyone here that is familiar enough with the pcmcia source that 
could help me get the linux pcmcia (Im currently using whatever comes in the 
2.4.20 kernel source). so that my 3.3V cards  work? I figure if windows can 
do it, then damnit linux can do it to (if not better!).

Jamie
-- 
No microsoft products were used to produce this message.
EUG-LUG Mailing List:
http://mailman.efn.org/cgi-bin/listinfo/eug-lug




From doug  Sat Dec 14 12:11:07 2002
From: doug (Doug Yeager)
Date: Sat, 14 Dec 2002 15:11:07 -0500
Subject: making a bridge.....i think
Message-ID: <20021214201107.859.qmail@12.150.120.133>

k,  for all those network designers out there.  i think this question is 
fairly simple one. 

i have an appartment complex that wants wireless.  i've never put it more 
than one access point...but this will require more than one.  i would think 
it is really neat if you could roam between them but it is o.k. if you 
can't...not a biggy. 

what i want to do is this:
T1 coming into the building to an access point.  then i want to place other 
AP's in various rooms in the building acting as AP's also because it is 
bigger than a radius of 300 feet so that one AP could not handle all rooms. 

in order to use one T1 internet connection,  is it possible to connect AP's 
together without wires?  or do i need to wire all AP's together on a wired 
network?  it would be totolly great if i could just route all traffic over 
wireless from one AP to another....eliminating the need to wire anything up 
for this. 

also, am i getting into a situation where a "bridge" might be required to do 
this.   any docs on this and how to use one DHCPD server to handle all AP's 
would be much appreciated. 

thx,
doug



From khoff  Sat Dec 14 20:30:43 2002
From: khoff (Kristian Hoffmann)
Date: Sat, 14 Dec 2002 20:30:43 -0800 (PST)
Subject: TXPOWER has no impact on ZCOM XI-325H?
In-Reply-To: <200212150012.PAA29691@archimedes.shmoo.com>
Message-ID: <Pine.LNX.4.44.0212142028570.26735-100000@luaren.pc-intouch.com>

You might want to check out www.zcom.com.tw.  Zcomax used to list a 802.11
(not b) PC-104 adapter board.  The only 802.11b embedded board I know of
is the XI-625 Mini-PCI adapter.  You might be able to hook that up to a
PC-104+ interface though.

-Kristian


On Sat, 14 Dec 2002, David Goodenough wrote:

> On Saturday 14 December 2002 02:23, you wrote:
> </snip>
>
> > I got this info from a person with direct contact with Z-Com.
>
> Could you ask your contact a question for me please.  I understand that
> Z-Com produce a PC-104 802.11b, but I can not find it anywhere.  Could
> you ask is they have a part number or the like.  I would be most grateful.
>
> David
>
> <snip/>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From brianc  Sun Dec 15 01:04:40 2002
From: brianc (Brian Capouch)
Date: Sun, 15 Dec 2002 04:04:40 -0500
Subject: "prism2" driver on Zaurus PDA
In-Reply-To: <3DFBCE19.3000607@palaver.net>
References: <3DFBCE19.3000607@palaver.net>
Message-ID: <3DFC45A8.1000008@palaver.net>

Brian Capouch wrote:> I just installed the "Open Zaurus" distribution on 
my Sharp Zaurus
> 5000-D, and am having a bit of trouble with the (older, I'm certain) 
> version of the HostAP driver that is installed on that machine.
> 
> 
> Can I just add one like the current hostap_cs.conf, and set ignore_cis 
> to 0?
> 
> 
> Thanks if anyone knows a fix. . .
> 

I know it's considered gauche to reply to your own question, but through 
trial-and-error I determined that I had the parameter just backwards.

To use the 5v card in the Zaurus, the file /etc/pcmcia/prism2.conf 
should contain the option "ignore_cis_vcc=1"

Sorry for the noise; hope this helps someone out in the future.

B.




From adrian  Sun Dec 15 08:35:47 2002
From: adrian (Adrian McMenamin)
Date: Sun, 15 Dec 2002 16:35:47 +0000
Subject: Problem(s) with a Compaq WL200
Message-ID: <200212151635.47873.adrian@mcmen.demon.co.uk>

I've googled for an answer, but to no avail, even though I have had this 
problem with two different WL200 cards, so I assume it must be reasonably 
common.

I am using a 2.4.18 kernel with hostap_cs:

hostap_cs: hostap_cs.c 0.0.0 2002-05-19 (SSH Communications Security Corp, 
Jouni Malinen)

When the server boots the card appears to trip through ever lower tx bit rits 
due to retry errors and then settles for the lowest (1 Mb/s). Even then 
operation is poor (very poor) unless I set retry to zero - but there are 
still huge numbers of errors:

[root at electra /]# /usr/local/sbin/iwconfig
wlan0     IEEE 802.11-DS  ESSID:"Consume"
          Mode:Master  Frequency:2.412GHz  Access Point: 00:50:8B:46:C6:E5
          Bit Rate:1Mb/s   Tx-Power=20 dBm   Sensitivity=1/3
          Retry limit:0   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:87017  Invalid misc:1268   Missed beacon:0

ifconfig output...


wlan0     Link encap:Ethernet  HWaddr 00:50:8B:46:C6:E5
          inet addr:192.168.63.64  Bcast:192.168.63.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:86454 errors:0 dropped:2 overruns:0 frame:0
          TX packets:86964 errors:86788 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:9945782 (9.4 Mb)  TX bytes:80421809 (76.6 Mb)
          Interrupt:9 Base address:0x100


Is this a known problem? Is there a fix?

Thanks in adavance

Adrian




From jkmaline  Sun Dec 15 08:49:29 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 15 Dec 2002 08:49:29 -0800
Subject: Problem(s) with a Compaq WL200
In-Reply-To: <200212151635.47873.adrian@mcmen.demon.co.uk>
References: <200212151635.47873.adrian@mcmen.demon.co.uk>
Message-ID: <20021215164929.GA1732@jm.kir.nu>

On Sun, Dec 15, 2002 at 04:35:47PM +0000, Adrian McMenamin wrote:

> When the server boots the card appears to trip through ever lower tx bit rits 
> due to retry errors and then settles for the lowest (1 Mb/s). Even then 
> operation is poor (very poor) unless I set retry to zero - but there are 
> still huge numbers of errors:

I'm assuming that you are using Compaq WL200 as the AP in Host AP mode.
What card and driver are you using as the client that associates with
this AP? I have seen such behavior when the associated station does not
ACK frames even though it receives them correctly. This has happened
with various Prism2/3-based cards running in Managed mode using Host AP
driver. Card reset has often fixed the problem ('iwpriv wlan0 reset 0'
or 'iwpriv wlan0 reset 1'), but not always. I haven't yet found out the
real cause for this.

-- 
Jouni Malinen                                            PGP id EFC895FA



From adrian  Sun Dec 15 08:59:53 2002
From: adrian (Adrian McMenamin)
Date: Sun, 15 Dec 2002 16:59:53 +0000
Subject: Problem(s) with a Compaq WL200
In-Reply-To: <20021215164929.GA1732@jm.kir.nu>
References: <200212151635.47873.adrian@mcmen.demon.co.uk> <20021215164929.GA1732@jm.kir.nu>
Message-ID: <200212151659.53128.adrian@mcmen.demon.co.uk>

On Sunday 15 Dec 2002 4:49 pm, Jouni Malinen wrote:
> On Sun, Dec 15, 2002 at 04:35:47PM +0000, Adrian McMenamin wrote:
> > When the server boots the card appears to trip through ever lower tx bit
> > rits due to retry errors and then settles for the lowest (1 Mb/s). Even
> > then operation is poor (very poor) unless I set retry to zero - but there
> > are still huge numbers of errors:
>
> I'm assuming that you are using Compaq WL200 as the AP in Host AP mode.

Yes, sorry - I just assumed people would understand that bit! :->

> What card and driver are you using as the client that associates with
> this AP? 

On booting, nothing. The client is usually a Prism 2 in managed mode. But 
either way it is also impossible to reset the txrate.

I have seen such behavior when the associated station does not
> ACK frames even though it receives them correctly. This has happened
> with various Prism2/3-based cards running in Managed mode using Host AP
> driver. Card reset has often fixed the problem ('iwpriv wlan0 reset 0'
> or 'iwpriv wlan0 reset 1'), but not always. I haven't yet found out the
> real cause for this.




From jkmaline  Sun Dec 15 08:57:19 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 15 Dec 2002 08:57:19 -0800
Subject: Linksys WPC 11
In-Reply-To: <000901c2a396$7d69c1e0$0200a8c0@springfield>
References: <003501c2a37a$0c94a140$0200a8c0@springfield> <200212141050.31897.jasonb@edseek.com> <000901c2a396$7d69c1e0$0200a8c0@springfield>
Message-ID: <20021215165719.GB1732@jm.kir.nu>

On Sat, Dec 14, 2002 at 12:30:25PM -0500, Gary Huntress wrote:

> The only other problem I notice is that if I eject the card I get:
> 
>     hostap_cs:   release postponed wlan0 still locked
> 
> and I can't reinsert the card :
>     requestID : resource in use

If you just eject the card without setting the wlan0 interface down,
some resources are not freed immediately. You will need to set the
interface down either before ejecting the card or after (I haven't
tested this for a while, but it should work). In other words, the
Linux network interface does not necessarily disappear immediately when
you eject the card. This was needed to fix couple of potential crashes.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 15 09:05:17 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 15 Dec 2002 09:05:17 -0800
Subject: I assume it's not working on linux side
In-Reply-To: <3DFB7DF2.1060401@swissgeeks.com>
References: <3DFB7DF2.1060401@swissgeeks.com>
Message-ID: <20021215170517.GC1732@jm.kir.nu>

On Sat, Dec 14, 2002 at 07:52:35PM +0100, Pierrick Brossin wrote:

> I can load the module and set the parameters for wlan0 but no PC can
> connect to my AP. I've tried with FreeBSD and Windows... I assume it
> would be same thing with Linux as client.

Which version of Host AP driver? Do you see the AP in the client when
you do a scan? Do you get any error messages in the client system? Does
'dmesg' output show any errors in the AP when a station is trying to
associate?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 15 09:09:46 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 15 Dec 2002 09:09:46 -0800
Subject: hostap bridging wired and wireless network query
In-Reply-To: <Pine.GSO.4.33.0212140030040.7790-100000@compserv1>
References: <Pine.GSO.4.33.0212140030040.7790-100000@compserv1>
Message-ID: <20021215170946.GD1732@jm.kir.nu>

On Sat, Dec 14, 2002 at 12:42:57AM -0500, Salil Gokhale wrote:

> brctl addbr br0
> brctl addif br0 eth0
> brctl addif br0 wlan0
> 
> ifconfig eth0 0.0.0.0

This command will probably remove some of your previous routing setup.

> ifconfig wlan0 0.0.0.0
> 
> ifconfig br0 130.245.126.245 up

After this one, there will be a short delay (depends on your bridge
configuration, but about 30 sec with defaults) when the bridge code
(STP) tries to figure out network configuration. During this period data
frames are not sent or received. If you look at kernel log ('dmesg'),
you should see the interface state changing from learning to forwarding
and after this the interfaces should be working again.

> After these steps I cannot access network even from the access point
> machine. Also I cannot access network from any machine on wlan.

> Do I need to setup gateway or routes on access point or other machines?

Yes, you will need to restore your correct routing setup after this. At
least setup default gateway again.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 15 09:17:12 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 15 Dec 2002 09:17:12 -0800
Subject: Compaq WL100 Init Problem...
In-Reply-To: <20021213091741.GB2586615@Tschach.com>
References: <20021213091741.GB2586615@Tschach.com>
Message-ID: <20021215171712.GE1732@jm.kir.nu>

On Fri, Dec 13, 2002 at 10:17:41AM +0100, Carsten Tschach wrote:

> I do have a Compaq WL100 card I would like to use in my RedHat 8.0 based
> Notebook.

> When inserting the WL100 into the Notebook I do get the following 
> error in /var/log/messages:

> Dec 13 10:05:32 porty kernel: hostap_cs: card initialization timed out

The driver was able to start initialization command, but the command
execution timed out. Have you tested that card with any other driver/OS?
Initialization timeout in Host AP driver should be long enough, but you
could also test increasing HFA384X_INIT_TIMEOUT in
driver/modules/hostap_hw.c

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 15 09:28:46 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 15 Dec 2002 09:28:46 -0800
Subject: Traffic Control
In-Reply-To: <003d01c2a1ff$6166ba90$98e216d5@pedropc>
References: <3DF86BCB.A8D96803@wretched.demon.co.uk> <003d01c2a1ff$6166ba90$98e216d5@pedropc>
Message-ID: <20021215172846.GF1732@jm.kir.nu>

On Thu, Dec 12, 2002 at 04:56:13PM -0000, Pedro Estrela wrote:

> a) The client to client packets on the same AP cell are sent directly to
> each other, not passing through the AP at all. It is sufficient for the
> destination STA to be in range to receive the packet.

That's not true with current IEEE 802.11 BSS mode; in IBSS that is the
case, but there is no AP in IBSS anyway. In BSS, stations send all
frames via the AP. If I remember correctly, possibility for direct
STA->STA traffic (i.e., bypassing AP) is proposed in new draft standard
(802.11e), but I do not think it is yet implemented in current wlan
products.

> b) if option "ap_bridge_packets == 1" is set, then all received packets on
> the AP destinated to another client associated to this AP are sent directly
> to the interface on the driver, not passing through TC. this also happens
> for Layer2 broadcast and multicast packets. Howerver, currently AFAIK this
> facility is not used because point A (see above) causes all traffic to go
> _direct_ between stations.

This is used and ap_bridge_packets=1 is the default in the driver. So
yes, it is the AP code doing this bridging between two associated
stations. By setting ap_bridge_packets=0, one should get the frames
going through the Linux stack and be able to perform QoS, etc. for them.
However, this will also mean that there has to be something doing the
bridging back to the same interface (or routing without ICMP redirects,
if that is more appropriate).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 15 09:51:54 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 15 Dec 2002 09:51:54 -0800
Subject: Problem(s) with a Compaq WL200
In-Reply-To: <200212151659.53128.adrian@mcmen.demon.co.uk>
References: <200212151635.47873.adrian@mcmen.demon.co.uk> <20021215164929.GA1732@jm.kir.nu> <200212151659.53128.adrian@mcmen.demon.co.uk>
Message-ID: <20021215175154.GA2412@jm.kir.nu>

On Sun, Dec 15, 2002 at 04:59:53PM +0000, Adrian McMenamin wrote:
> On Sunday 15 Dec 2002 4:49 pm, Jouni Malinen wrote:

> > What card and driver are you using as the client that associates with
> > this AP? 
> 
> On booting, nothing. The client is usually a Prism 2 in managed mode. But 
> either way it is also impossible to reset the txrate.

And the (client) driver? I would really need to get details to know
which client cards/firmware versions/drivers are showing this kind of
behavior to be able to find out the reason for the problems.. If you can
test the same AP with non-Prism2 card and non-Host AP driver as the
client, it would be nice to know whether the same problem occurs with
that station.

-- 
Jouni Malinen                                            PGP id EFC895FA



From ariel  Sun Dec 15 13:25:31 2002
From: ariel (ariel at fismat.umich.mx)
Date: Sun, 15 Dec 2002 21:25:31 -0000 (UTC)
Subject: How to restrict peer bandwidth use
Message-ID: <1378.148.243.177.58.1039987531.squirrel@fismat.umich.mx>

Hello:

Is there any way to restrict the bandwidth used by every wireless client.
I have many users, and i need some to have only 56Kpbs, others 1Mb and
others should have full bandwidth.

Merely i just need to restrict internet access, if they can have
11mbps(with luck) between themselves would be great, i only want they to
have slower connections to the internet.







From Simon  Sun Dec 15 19:34:59 2002
From: Simon (Simon Waters)
Date: Mon, 16 Dec 2002 03:34:59 +0000
Subject: How to restrict peer bandwidth use
References: <1378.148.243.177.58.1039987531.squirrel@fismat.umich.mx>
Message-ID: <3DFD49E3.55940DB1@wretched.demon.co.uk>

ariel at fismat.umich.mx wrote:
> 
> Is there any way to restrict the bandwidth used by every wireless client.
> I have many users, and i need some to have only 56Kpbs, others 1Mb and
> others should have full bandwidth.

Linux traffic control is documented at www.lartc.org

> Merely i just need to restrict internet access, if they can have
> 11mbps(with luck) between themselves would be great, i only want they to
> have slower connections to the internet.

See the "traffic control" thread. You probably need to apply
both policing, and rate limiting, but there are some example
scripts doing something similar.

I'm still fighting the same question. Despite Jouni's comments I
was seeing an effect, with just two clients to the access point,
when one is also the default route of the AP, when applying a
limitation to the outgoing traffic by interface. I wasn't sure
this should work when the access point is just being an access
point but it seems to work as you'd expect for a router.
Although I'm still ironing out network performance issues this
end - too many duplicates and I can't kill them for some reason.

 Simon



From keresztg  Mon Dec 16 01:57:13 2002
From: keresztg (Gabor Keresztfalvi)
Date: Mon, 16 Dec 2002 10:57:13 +0100
Subject: Duplicated packets (Was: Re: How to restrict peer bandwidth use)
In-Reply-To: <3DFD49E3.55940DB1@wretched.demon.co.uk>
References: <1378.148.243.177.58.1039987531.squirrel@fismat.umich.mx> <3DFD49E3.55940DB1@wretched.demon.co.uk>
Message-ID: <20021216095713.GA29265@balu.sch.bme.hu>

On Mon, Dec 16, 2002 at 03:34:59AM +0000, Simon Waters wrote:
> Although I'm still ironing out network performance issues this
> end - too many duplicates and I can't kill them for some reason.
I had the same problems with two SMC card with STA v0.8.3 as the AP
(with hostapd!) and the client. If the client was a Lucent Bronze card
with the orinoco driver, the duplicates went away... So I've taken the
latest RAM downloadable firmware (v1.5.6 from the original Intersil
ISL3PRDSUIT-EXE_WIN_(2-0-9).zip) for the SMC card, and upgraded them.
Now they work fine, without duplicated packets.
So try the latest firmware...

Greets,
Gabor

Ps.: Without hostapd in the AP and with the original 0.8.3 firmware
there were no duplicates as well. Strange, isn't it?

-- 
+ Keresztfalvi Gabor
+ Student of the Budapest University of Technology and Economics 
+ mailto: keresztg at mail.com  keresztg at sch.bme.hu
+ http://keresztg.ini.hu/



From jharana  Mon Dec 16 02:24:37 2002
From: jharana (Jharana)
Date: Mon, 16 Dec 2002 15:54:37 +0530
Subject: SNMP support
Message-ID: <3DFDAA61.CDEB8B84@mahindrabt.com>

Hi All,
Does hostap driver have any support for SNMP? If it doesnt, how does one
enable snmp for AP based on hostap?
regards,
Jharana

*********************************************************
Disclaimer

This message (including any attachments) contains 
confidential information intended for a specific 
individual and purpose, and is protected by law. 
If you are not the intended recipient, you should 
delete this message and are hereby notified that 
any disclosure, copying, or distribution of this
message, or the taking of any action based on it, 
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com






From gallir  Mon Dec 16 04:02:52 2002
From: gallir (Ricardo Galli)
Date: Mon, 16 Dec 2002 13:02:52 +0100
Subject: Link and question for WDS
Message-ID: <200212161302.52124.gallir@uib.es>

Hi Jouni,
	I just wrote an article in Spanish explaining how to configure WDS, just 
in case you want to add it to your links: 
http://bulmalug.net/body.phtml?nIdNoticia=1624

The question: in a server with two prism2 cards I want to use one for a 
WDS link (wlan0). The other one (wlan1), in master mode and in a 
different channel, to give connectivity to wireless stations. How can I 
force stations to register just in wlan1? (i.e. to disable wlan0)

I thought in using ACLs, but it seems not the right solution.


Thanks,

-- 
  ricardo galli       GPG id C8114D34




From sneeze  Mon Dec 16 00:47:02 2002
From: sneeze (Ryan Abbenhuys)
Date: Mon, 16 Dec 2002 19:47:02 +1100
Subject: Problem(s) with a Compaq WL200
References: <200212151635.47873.adrian@mcmen.demon.co.uk> <20021215164929.GA1732@jm.kir.nu> <200212151659.53128.adrian@mcmen.demon.co.uk> <20021215175154.GA2412@jm.kir.nu>
Message-ID: <009d01c2a4df$b6e97290$0100a8c0@silver>

I noticed the email from Jouni that mentioned WL200's have issues shutting
down and that you have to shutdown the interface first before shutting down
the system.  I'm running Redhat 8, PCMCIA Card Services 3.2.3 and kernel
build 2.4.18-18.8.0 on an SMP platform.

Can anyone tell me if I can use this line in the network.opts file in
/etc/pcmcia

# Extra stuff to do before shutting down the interface
    stop_fn () { return; }

If so what could I change this to in order to shutdown the interface to try
and stop the system hanging during shutdown?  If anyone can help me out but
needs some more info let me know and i'll do my best to provide it.

At the moment my WL200 seems to initialise fine with the latest CVS of the
HostAP driver. But when it comes to shutting down the system it dies when
trying to shutdown PCMCIA.  I then have to reboot and upon rebooting get the
following error when trying to start PCMCIA again

cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
memory_cs: mem0: anonymous: unknown size

If I then stop and start PCMCIA it seems to work fine.


Here's the successful PCMCIA initialisation....

Linux PCMCIA Card Services 3.2.3
  kernel build: 2.4.18-18.8.0custom #2 SMP Sat Dec 14 07:30:59 EST 2002
  options:  [pci] [cardbus] [apm]
Intel ISA/PCI/CardBus PCIC probe:
  Ricoh RL5C475 rev 80 PCI-to-CardBus at slot 00:0a, mem 0x20000000
    host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 18] [lat
32/176] [bus 2/5]
    PCI card interrupts, PCI status changes
  Cirrus PD6729 rev 00 PCI-to-PCMCIA at slot 00:0c, port 0xa800
    host opts [0]: [ring] [pci irq 16] [1/5/0] [1/20/0]
    host opts [1]: [ring] [pci irq 16] [1/5/0] [1/20/0]
    PCI card interrupts, PCI status changes
cs: memory probe 0x0d0000-0x0dffff: clean.
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.0.0 CVS (Jouni Malinen <jkmaline at cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
prism2_config()
hostap_cs: setting Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
Config has no IRQ info, but trying to enable IRQ anyway..
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
cs: IO port probe 0x0100-0x04ff: excluding 0x290-0x297 0x378-0x37f
0x3c0-0x3df 0x4d0-0x4d7
cs: IO port probe 0x0298-0x0377: clean.
cs: IO port probe 0x0380-0x03bf: clean.
cs: IO port probe 0x03e0-0x04cf: clean.
cs: IO port probe 0x04d8-0x04ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
hostap_cs: index 0x01: Vcc 3.3, irq 16, io 0x0100-0x013f
hostap_cs: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_config: initialized in 10101 iterations
wlan0: NIC: id=0x8002 v1.0.1
wlan0: PRI: id=0x15 v0.3.0
wlan0: STA: id=0x1f v1.4.9
wlan0: defaulting to bogus WDS frame as a workaround for firmware bug in
Host AP mode WDS
wlan0: LinkStatus=2 (Disconnected)
wlan0: LinkStatus=2 (Disconnected)
wlan0: LinkStatus=2 (Disconnected)
wlan0: LinkStatus=2 (Disconnected)
Setting ALC off
Setting TX power to 20 dBm
wlan0: LinkStatus=2 (Disconnected)
wlan0: prism2_open
.............
etc etc etc



----- Original Message -----
From: "Jouni Malinen" <jkmaline at cc.hut.fi>
To: <hostap at shmoo.com>
Sent: Monday, December 16, 2002 4:51 AM
Subject: Re: Problem(s) with a Compaq WL200


> On Sun, Dec 15, 2002 at 04:59:53PM +0000, Adrian McMenamin wrote:
> > On Sunday 15 Dec 2002 4:49 pm, Jouni Malinen wrote:
>
> > > What card and driver are you using as the client that associates with
> > > this AP?
> >
> > On booting, nothing. The client is usually a Prism 2 in managed mode.
But
> > either way it is also impossible to reset the txrate.
>
> And the (client) driver? I would really need to get details to know
> which client cards/firmware versions/drivers are showing this kind of
> behavior to be able to find out the reason for the problems.. If you can
> test the same AP with non-Prism2 card and non-Host AP driver as the
> client, it would be nice to know whether the same problem occurs with
> that station.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From jkmaline  Mon Dec 16 18:54:45 2002
From: jkmaline (Jouni Malinen)
Date: Mon, 16 Dec 2002 18:54:45 -0800
Subject: Link and question for WDS
In-Reply-To: <200212161302.52124.gallir@uib.es>
References: <200212161302.52124.gallir@uib.es>
Message-ID: <20021217025445.GB2023@jm.kir.nu>

On Mon, Dec 16, 2002 at 01:02:52PM +0100, Ricardo Galli wrote:

> The question: in a server with two prism2 cards I want to use one for a 
> WDS link (wlan0). The other one (wlan1), in master mode and in a 
> different channel, to give connectivity to wireless stations. How can I 
> force stations to register just in wlan1? (i.e. to disable wlan0)

If you don't want to have any station associating with wlan0, you could
just configure it to use Repeater (i.e., WDS) mode, in which the card
does not send beacons or reply to probe requests.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Dec 16 18:55:13 2002
From: jkmaline (Jouni Malinen)
Date: Mon, 16 Dec 2002 18:55:13 -0800
Subject: SNMP support
In-Reply-To: <3DFDAA61.CDEB8B84@mahindrabt.com>
References: <3DFDAA61.CDEB8B84@mahindrabt.com>
Message-ID: <20021217025513.GC2023@jm.kir.nu>

On Mon, Dec 16, 2002 at 03:56:41PM +0530, Jharana wrote:

> Does hostap driver have any support for SNMP? If it doesnt, how does one
> enable snmp for AP based on hostap?

Host AP driver collects statistics for various things, but I haven't
checked whether these cover all 802.11 related MIBs. As far as I know,
an interface between SNMP agent and the driver or hostapd has not yet
been implemented, so this would also require some effort to get SNMP
support working.

-- 
Jouni Malinen                                            PGP id EFC895FA



From feldmand  Mon Dec 16 21:04:20 2002
From: feldmand (Dan Feldman)
Date: Mon, 16 Dec 2002 23:04:20 -0600
Subject: CISCO 350 card--> the open HOSTAP Challenge ... 
Message-ID: <F135sZsvlPpZDzsfOy70001d537@hotmail.com>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021216/f5be9bfe/attachment.htm 


From imp  Mon Dec 16 23:36:20 2002
From: imp (=?utf-7?B?K3ZCWFhaY1gwLQ==?=)
Date: Tue, 17 Dec 2002 16:36:20 +0900
Subject: Too slow then previous
Message-ID: <HIEILNBGFIFLDLBJCOLAEEHLCFAA.imp@airlinktek.com>

Dear all..

I thinks the software interrupt handler work too slow then previous host AP.

the previous one is before 2002-10-12. I measure the througput test from client PC with pcmcia card
to hostap and internet speed test site...

and the result is the previous one is about 4.5Mbps for download through ADSL line
but the current one is only 3.0 or 3.1 Mbps ...

Could you give me any comment for the result ? 

Thanks.




From sec4wlan  Tue Dec 17 05:48:49 2002
From: sec4wlan (Nikhil Chauhan)
Date: Tue, 17 Dec 2002 05:48:49 -0800 (PST)
Subject: Hostap and 802.1X
Message-ID: <20021217134850.5264.qmail@web10903.mail.yahoo.com>


Hello:

I'm in the process of implementing the 802.1x functionality alongwith the key

handshaking (Pairwise key handshake and the Group handshake). I'm using

the Open1x source code to achieve the same.

 

I've been able to test the xsupplicant functionality on a linux machine with

Systemonic's WLAN card. I've used Cisco's AP350 as the authenticator and 

FreeRadius as the authentication server. Open1x code seems fine till it receives an 

EAPOL-Key message. I've been able to get the xsupplicant authenticated, and the 

connection looks good (I'm able to ping the Auth server from the xsupplicant). 

 

Now, I wish to test the authenticator functionality of the Open1x. It seems the 

authenticator doesn't have a proper functioning Key transmit state machine as

well as the key receive state machine. My questions are based on the above tests:

1. Can the HostAP code be used in place of the open1x authenticator? What 

    relation do they have with each other?

2. Does the HostAP support the 4-way pairwise key and the group key handshaking

    thereby installing the keys? If no, is there any other freeware to achieve this?

Thanks in advance,
Nikhil.



---------------------------------
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021217/aa352d5f/attachment.htm 


From tangja  Mon Dec 16 08:40:11 2002
From: tangja (=?ks_c_5601-1987?B?wMzFwr/1?=)
Date: Tue, 17 Dec 2002 01:40:11 +0900
Subject: Problem of get RID
Message-ID: <000001c2a521$ce0dcd30$7600000a@smallbigyurx30>

I am using..
Kernel        : v2.4.19
pcmcia-cs           : 3.1.22
hostap driver : latest version
pcmcia card : Intersil Chipset?.
 
But, I got a access fail messge from kernel ..
 
 
=======================> kernel messgess.......
<========================
.....
...
.
Linux Kernel Card Services 3.1.22
  options:  none
hostap_crypt: registered algorithm 'NULL'
hostap_crypt: registered algorithm 'WEP'
hostap_cs: 0.0.0 CVS (Jouni Malinen <jkmaline at cc.hut.fi>)
cs: CardServices(GetCardServicesInfo, 0x001b1f90, 0x00000001)
hostap_cs: setting Vcc=33 (constant)
cs: CardServices(RegisterClient, 0x001a788c, 0x00ae1c48)
hostap_cs: CS_EVENT_CARD_INSERTION
prism2_config()
cs: CardServices(GetFirstTuple, 0x001a7760, 0x00ae1b3c)
cs: CardServices(GetTupleData, 0x001a7760, 0x00ae1b3c)
cs: CardServices(ParseTuple, 0x001a7760, 0x00ae1b3c)
cs: CardServices(GetConfigurationInfo, 0x001a7760, 0x00ae1940)
hostap_cs: setting Vcc=33 (from config)
cs: CardServices(GetFirstTuple, 0x001a7760, 0x00ae1b3c)
cs: CardServices(GetTupleData, 0x001a7760, 0x00ae1b3c)
cs: CardServices(ParseTuple, 0x001a7760, 0x00ae1b3c)
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
cs: CardServices(RequestIO, 0x001a7760, 0x001a7890)
cs: CardServices(RequestIRQ, 0x001a7760, 0x001a78a4)
: Interrupt, but dev not OK
cs: CardServices(RequestConfiguration, 0x001a7760, 0x001a78bc)
hostap_cs: index 0x01: Vcc 3.3, irq 0, io 0x0100-0x013f
hostap_cs: Registered netdevice wlan0
hostap_cs: Registered netdevice wlan0ap for AP management
prism2_hw_init()
wlan0: init command completed too quickly - retrying
prism2_hw_config: initialized in 0 iterations
wlan0: hfa384x_cmd: entry still in list? (entry=001bc420, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=001bc420,
type=0)
wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd0b,
len=8)
Could not get RID for component NIC
wlan0: hfa384x_cmd: entry still in list? (entry=001bc420, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=001bc420,
type=0)
wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd02,
len=8)
Could not get RID for component PRI
wlan0: hfa384x_cmd: entry still in list? (entry=001bc420, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=001bc420,
type=0)
wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd20,
len=8)
Could not get RID for component STA
...........
.......
....
..
Finally,
 
wlan0: could not get own MAC address
wlan0: Port type setting to 6 failed
wlan0: MAC port 0 enabling failed
 
I can not resolve this problem.
 
Please help me...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021217/164bb9f8/attachment.htm 


From martin.daur  Tue Dec 17 11:04:51 2002
From: martin.daur (Martin Daur)
Date: Tue, 17 Dec 2002 20:04:51 +0100
Subject: alternative retry count
References: <20021217170015.29418.80483.Mailman@lists.linux-wlan.com> <40730.208.24.179.208.1040140070.squirrel@www.phatcom.net>
Message-ID: <3DFF7553.7000806@web.de>

hi,

in the release note posting from 2002-04-05 I found out this driver is 
now supporting setting the retry paramater manually. the source code is 
talking about an  alternative retry count, may anybody explain me what 
the "alternative retry count" is?

Is it possible to set the retry count (or alternative retry count and 
other driver parameters) per every delivered packet?

By the way what intersil/prism card can you recommend (with good 
firmware support and tools by the vendor)?

thanks for the good work on hostap.

cu
martin
-- 
Martin Daur          Tel: 07344/6915                * Please Encrypt *
Weilerstr. 48/6      Fax: 07344/kaputt              *  Certificates, *
D-89143 Blaubeuren   ICQ: 39532297                  *   GnuPG, PGP   *
Germany              Web: mdaur.homeip.net/martin   ******************




From gallir  Tue Dec 17 14:10:42 2002
From: gallir (Ricardo Galli)
Date: Tue, 17 Dec 2002 23:10:42 +0100
Subject: Link and question for WDS (in repeater mode)
In-Reply-To: <20021217025445.GB2023@jm.kir.nu>
References: <200212161302.52124.gallir@uib.es> <20021217025445.GB2023@jm.kir.nu>
Message-ID: <200212172310.42363.gallir@uib.es>

On Tuesday 17 December 2002 03:54, Jouni Malinen shaped the electrons to 
shout:
> If you don't want to have any station associating with wlan0, you could
> just configure it to use Repeater (i.e., WDS) mode, in which the card
> does not send beacons or reply to probe requests.

Thanks... but :-)


I am trying in repeater mode and couldn't realize how to solve the 
problem. First, when I used autom_ap_wds 1, neither the ap or the 
repeater "saw" each other.

So I added specified the mac manually in iwpriv wlan0 wds_add, and the 
link is shown in /proc/net/hostap/wlan0/wds in both computers (the 
example is the master):

ponti:~# cat /proc/net/hostap/wlan0/wds
wlan0wds0       00:05:5d:d6:4b:da

But, there is no link among them, the repeater station show no messages at 
all.

The master gives the following messages:

...
handle_ap_item - addr3(BSSID)=00:05:5d:d6:4b:da not own MAC
handle_ap_item - addr3(BSSID)=00:05:5d:d6:4b:da not own MAC
handle_ap_item - addr3(BSSID)=00:05:5d:d6:4b:da not own MAC
handle_ap_item - addr3(BSSID)=00:05:5d:d6:4b:da not own MAC
handle_ap_item - addr3(BSSID)=ff:ff:ff:ff:ff:ff not own MAC
handle_ap_item - addr3(BSSID)=ff:ff:ff:ff:ff:ff not own MAC
handle_ap_item - addr3(BSSID)=01:00:5e:00:00:01 not own MAC
handle_ap_item - addr3(BSSID)=ff:ff:ff:ff:ff:ff not own MAC
handle_ap_item - addr3(BSSID)=ff:ff:ff:ff:ff:ff not own MAC
handle_ap_item - addr3(BSSID)=ff:ff:ff:ff:ff:ff not own MAC
handle_ap_item - addr3(BSSID)=ff:ff:ff:ff:ff:ff not own MAC
handle_ap_item - addr3(BSSID)=01:00:5e:00:00:01 not own MAC
...

As you can see, 00:05:5d:d6:4b:da is the other end of the wds link, but 
01:00:5e:00:00:01 is unknown to me. I suppose ff:ff:ff are brodcasts from 
the repeater. 

The driver version is 2002-10-12, I tried all configuration options but 
couldn't find the reason of these messages.


Regards,

-- 
  ricardo galli       GPG id C8114D34




From lesbell  Tue Dec 17 15:15:01 2002
From: lesbell (Les Bell)
Date: Wed, 18 Dec 2002 10:15:01 +1100
Subject: What Am I Missing?
Message-ID: <OF8B0975AE.9965B135-ONCA256C92.007ED60C@lesbell.com.au>

I have a couple of machines as follows:

RH 7.3, hostap_pci.o, wlan0 on 192.168.170.254, Netgear MA311 PCI card
Win2K, Netgear MA401 PC Card with the Netgear driver

They talk perfectly happily in Ad-Hoc mode, but whenever I put the Linux
box into Master mode and the Win2K box into its "Infrastructure" mode, the
game is over. Nothing. Nada. Zip.

What am I missing here? The Linux box is configured to route from the
wireless LAN to the rest of our setup - does Master mode require it to be
reconfigured as a bridge? I've got to be overlooking something simple . . .

One other question, while I'm at it: the PCI card is at the back of a
mini-tower box in the middle of a row of servers, where the cabling seems
to be screening its miniature antenna pretty badly, so I need to add an
external antenna higher up. The Netgear docs don't mention what the antenna
connector is, so does anyone know what that little threaded coax connector
is called? MMCX? RMMCX? SMA?

Thanks, and Compliments of the Season,

--- Les Bell
[http://www.lesbell.com.au]





From Pavel.Vondricka  Tue Dec 17 17:17:32 2002
From: Pavel.Vondricka (Pavel Vondricka)
Date: Wed, 18 Dec 2002 00:17:32 -0100
Subject: TXPOWER has no impact on ZCOM XI-325H (final report)
In-Reply-To: <20021214043634.A1378@hzdhome.home.blkseanet.ru>
References: <200212140253.49324.Pavel.Vondricka@ff.cuni.cz> <200212140327.28181.Pavel.Vondricka@ff.cuni.cz> <20021214043634.A1378@hzdhome.home.blkseanet.ru>
Message-ID: <200212180017.32539.Pavel.Vondricka@ff.cuni.cz>

Final report for concerned:

Today we tested both XI-325 and XI-325H and it seems that the first one really 
can control it's output power, but not the second one. The conditions were 
quite strange - the signal changed much more just by itself (maybe strong 
reflections from the concrete walls?). A small movement with a notebook made 
much greater change in signal strength than any regulation, however there 
really were some visible changes in the strength, when the situation got 
stable. But there was no change with the XI-325H at all.

Thanks for your info,
Pavel

-- 
###########################################################################
# mailto:Pavel.Vondricka at ff.cuni.cz / ICQ:143159880 
# http://web.ff.cuni.cz/~vondric
#
# Muzete mi psat cesky s libovolnym kodovanim (UTF-8, ISO-8859-2,
# windows-1250, atd. ...)
###########################################################################



From cupid90  Tue Dec 17 16:11:52 2002
From: cupid90 (cupid90 at samsung.co.kr)
Date: Wed, 18 Dec 2002 09:11:52 +0900
Subject: (Re) HostAP digest, Vol 1 #69 - 14 msgs
In-Reply-To: <20021217134900.3773.989.Mailman@sisyphus.iocaine.com>
Message-ID: <H000050a13ef2431.1040170079.kgomap0@MHS>

My name is Roh You-chang.
I will start develop hostap driver next week.
I am reading the information what I prepare for it.

Maybe I will need your help.

I will develop it with Cisco 350 pcmcia card(embeded in station firmware).

once I have questions, I will send to you.

Thanks
             
????????????????????????????????????????????????

_?_____
/______/~? .?.        ???
?????? ``     
 ----------             
Happy day~?          Roh You-Chang

      Application S/W Engineer
      System Solution Group
      Access Network SOC Team
      System LSI Business
      Device Solution Network
      SAMSUNG ELECTRONICS CO., LTD.

      phone:82-31-209-8314,  fax:82-31-209-8309
      e-mail:cupid90 at samsung.co.kr

????????????????????????????????????????????????

WARNING: 

 This e-mail contains confidential and/or privileged information for the
 sole use by the specified recipient(s).  Any unauthorized review distribution, 
 disclosure or other use of the information in this message and the attched
 file hereto is strictly prohibited.  If you are not the specified recipient, please 
 contact the sender (terius90 at samsung.com or cupid90 at samsung.co.kr)
 and delete the original message and all copies thereof.  

 Thanks!

????????????????????????????????????????????????




From hazard  Tue Dec 17 16:12:06 2002
From: hazard (Vladimir Ivaschenko)
Date: Wed, 18 Dec 2002 02:12:06 +0200
Subject: TXPOWER has no impact on ZCOM XI-325H (final report)
In-Reply-To: <200212180017.32539.Pavel.Vondricka@ff.cuni.cz>
References: <200212140253.49324.Pavel.Vondricka@ff.cuni.cz> <200212140327.28181.Pavel.Vondricka@ff.cuni.cz> <20021214043634.A1378@hzdhome.home.blkseanet.ru> <200212180017.32539.Pavel.Vondricka@ff.cuni.cz>
Message-ID: <20021218021206.B8167@hzdhome.home.blkseanet.ru>

Hi,

So what difference were you able to measure? What did you use for
measurements?

Wed, Dec 18, 2002 at 12:17:32AM -0100 Pavel Vondricka wrote about Re: TXPOWER has no impact on ZCOM XI-325H (final report)

> Final report for concerned:
> 
> Today we tested both XI-325 and XI-325H and it seems that the first one really 
> can control it's output power, but not the second one. The conditions were 
> quite strange - the signal changed much more just by itself (maybe strong 
> reflections from the concrete walls?). A small movement with a notebook made 
> much greater change in signal strength than any regulation, however there 
> really were some visible changes in the strength, when the situation got 
> stable. But there was no change with the XI-325H at all.

-- 
Best Regards
Vladimir Ivaschenko
http://www.hazard.maks.net/



From dan  Tue Dec 17 19:02:44 2002
From: dan (Daniel Feldman)
Date: Tue, 17 Dec 2002 21:02:44 -0600
Subject: FW:  CISCO 350 card--> the open HOSTAP Challenge ... 
Message-ID: <HBEPKIMCNAHKLBDCJMPAGEBFCAAA.dan@baselinesys.com>


-----Original Message-----
From: Daniel Feldman [mailto:dan at baselinesys.com]
Sent: Tuesday, December 17, 2002 7:02 PM
To: HostAP at shmoo.com
Subject: CISCO 350 card--> the open HOSTAP Challenge ...



Prologe
 My apologizes for first using hotmail to send out an HTML draft of
this email. (i guess it got all messed up, thanks Jason for the heads up)

to begin ... over 37 hours spent working out this problem ... so
 far no success...

The goal: to get a public IP address (via PPPOE) on the win2k box
 via a win2k - cisco350 card - air - cisco350 card - Linux - 3com card -
adsl device...

I have two computers... (yay)
1. sony viao laptop p233 Debian 2.4.18 - Cisco 350 pcmcia - and 3com pcmcia
patched to ADSL device.

2. thinkpad - win2k - Cisco 350 pcmcia (primary workstation)

I want to have the win2k box able to wirelessly get on the internet with the
public IP. I need to pppoe running in general to get on the big "I" via my
adsl ISP... so my solution thus far is to pppoe from the linux box and
iptables masq 192.168 for the win2k.... yay! i have internet connectivity on
the win2k but my ideal solution would be to raspppoe through the linux box
so to get the public IP on the win2k...  when I replace the wireless
adhoc(yuck) connection between the two with a wired one (swap out the cisco
350 in the linux and use another 3com pcmcia card I got lying around and
crossover into the builtin eth on the thinkpad), the BRCTL bridging stuff
works..

the ff.ff.ff.ff MAC broadcast from the win2k is propagated across the bridge
.. the adsl device replies with its MAC..then the win2k box sends a directed
MAC packet to the adsl device ... SUCCESS!! the raspppoe establishes and
wa-la I have the public IP on the win2k.

the motivation: lets just say there is a beautiful lady across the pond
which I would like to netmeeting with but do not want to go through the
trouble of running through a h323 gateway...tried it but its hard to get
such a fair thing to work out those gatekeeper junk commands in a
swiss-german localed pc :-(

of course the two cisco350's are adhoc for previously mentioned current
setup to work wirelessly BUT not its no able to get the darn public IP on
the win2k box...  here is what I try when on the linux, I kill the pppoe
session... replace the wired solution with the cisco350 pcmcia ..then brctl
(bridge) the two eth's (eth0-3com eth1-cisco350) and then try to raspppoe
from the win2k box...  BUT when I try to do this via the ad-hoc wireless
(350 to 350) connection.. its seems (from ethereal running
 on the linux eth1) that after the ADSL device replies with its MAC .. the
win2k box will then send a packet ONLY TO the MAC of the linux cisco 350
card... (darn you cisco win2k ad-hoc mode)

SO THE OPEN HOSTAP CHALLENGE is for someone to work out the cisco350 hostap
solution so that I can video conf with my baby overseas!!! I believe with
one of these cards in AP mode and the other associating.. I will not have
the layer-2 limitation that I currently have when running in adhoc mode.

I PUT THIS CHALLEGE TO YOU!! I know "you" can do it.(in fact from scouring
this archive... someone has kinda.... besides is must burn you that cisco's
AP costs $600.. with no free solution for cisco cards....) lets make this
thing happen in linux... some one has said it may require a modified airo.o
or something.. whatever... just lets do this thing... and since im begging
into the wind..
 why not write a nice howto for it once its done...
you all rock hard! thanks in advance...

 -Dan




From lesbell  Tue Dec 17 19:29:33 2002
From: lesbell (Les Bell)
Date: Wed, 18 Dec 2002 14:29:33 +1100
Subject: What Am I Missing?
Message-ID: <OF89CFCC07.5244090F-ONCA256C93.0010CA83@lesbell.com.au>

STA firmware? Good question - after doing some reading to find the answer,
I realised I needed to build the contents of the utils directory to get
hostap_diag. However, just running make results in violent objections to
/usr/src/linux/include/linux:

In file included from /usr/src/linux/include/linux/wireless.h:70,
                 from prism2_srec.c:20:
/usr/src/linux/include/linux/ethtool.h:18: parse error before `u32'
/usr/src/linux/include/linux/ethtool.h:18: warning: no semicolon at end of
struct or union
/usr/src/linux/include/linux/ethtool.h:19: warning: type defaults to `int'
in declaration of `supported'

and on, and on, and on, for pages. Strange, because ethtool.h looks
inoffensive enough on a cursory examination. However, I'm clearly going to
have to sort this out before I can get any further. This is on RH 7.3 with
kernel-source-2.4.18-18.7.x installed.

Does the W2K station associate with the hostap box in Master mode? No -
Win2K immediately shows "Network cable unplugged" and the Netgear control
panel applet shows the status as "Scanning". Switch both ends back to
Ad-Hoc, and it associates again.

Finally, I tracked down the connector type for the MA311, at
http://www.fulton.net.au/qt045.htm - the connector on the antenna (and
hence any cable) is a reverse polarity SMA (RP SMA) type. I'm just waiting
for a local distributor to email me back a quote on a cable and pigtail
lead, so that's one problem sorted. . .<grin>

BTW, I took the liberty of copying this, including your reply to the list;
hope you don't mind.

Best,

--- Les Bell, CISSP
[http://www.lesbell.com.au]


                                                                                                                              
                      "Jason Boxman"                                                                                          
                      <jasonb at edseek.co        To:       <lesbell at lesbell.com.au>                                             
                      m>                       cc:                                                                            
                                               Subject:  Re: What Am I Missing?                                               
                      18/12/2002 01:48                                                                                        
                      PM                                                                                                      
                      Please respond to                                                                                       
                      jasonb                                                                                                  
                                                                                                                              
                                                                                                                              




Les Bell said:

> I have a couple of machines as follows:
>
> RH 7.3, hostap_pci.o, wlan0 on 192.168.170.254, Netgear MA311 PCI card
Win2K, Netgear MA401 PC Card with the Netgear driver
>
> They talk perfectly happily in Ad-Hoc mode, but whenever I put the Linux
box into Master mode and the Win2K box into its "Infrastructure" mode,
the game is over. Nothing. Nada. Zip.

What STA firmware is on the MA401?

Does the W2K station associate with the HostAP Box in Master mode?

> What am I missing here? The Linux box is configured to route from the
wireless LAN to the rest of our setup - does Master mode require it to
be reconfigured as a bridge? I've got to be overlooking something simple
. . .

A bridge setup isn't necessary.

> One other question, while I'm at it: the PCI card is at the back of a
mini-tower box in the middle of a row of servers, where the cabling
seems to be screening its miniature antenna pretty badly, so I need to
add an external antenna higher up. The Netgear docs don't mention what
the antenna
> connector is, so does anyone know what that little threaded coax
connector is called? MMCX? RMMCX? SMA?

Good question -- I'd suspect a Google search on the card will turn up your
answer if someone here doesn't know.

> Thanks, and Compliments of the Season,
>
> --- Les Bell
> [http://www.lesbell.com.au]
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>











From jkmaline  Tue Dec 17 19:28:09 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 17 Dec 2002 19:28:09 -0800
Subject: alternative retry count
In-Reply-To: <3DFF7553.7000806@web.de>
References: <20021217170015.29418.80483.Mailman@lists.linux-wlan.com> <40730.208.24.179.208.1040140070.squirrel@www.phatcom.net> <3DFF7553.7000806@web.de>
Message-ID: <20021218032809.GB996@jm.kir.nu>

On Tue, Dec 17, 2002 at 08:04:51PM +0100, Martin Daur wrote:

> in the release note posting from 2002-04-05 I found out this driver is 
> now supporting setting the retry paramater manually. the source code is 
> talking about an  alternative retry count, may anybody explain me what 
> the "alternative retry count" is?

Prism2 cards support two 'maximum retry count' values and well, that is
the second one ;-). The default value is hard coded so it cannot be used
for manual configuration. However, this alternative retry count can be
changed and that is why the driver is using it.

> Is it possible to set the retry count (or alternative retry count and 
> other driver parameters) per every delivered packet?

You can only select whether you want to use default or alternative retry
count for each frame. There is not enough time to change the alternative
retry count between frames. So, you have two possible values for retry
counts, if you need to have different setting for some frames.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Dec 17 21:06:06 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 17 Dec 2002 21:06:06 -0800
Subject: Accounting support for Radius
In-Reply-To: <5.1.0.14.0.20021123185440.00af9d98@mail.marekroy.com>
References: <5.1.0.14.0.20021123185440.00af9d98@mail.marekroy.com>
Message-ID: <20021218050606.GA2409@jm.kir.nu>

On Sat, Nov 23, 2002 at 07:01:46PM +1100, Marek Roy wrote:

> 	Has anyone started to add any Accounting support to ieee802_1x.c 
> 	yet?  It would be nice to have this feature in Hostapd. (802.1x)

Yes, I have started and also finished ;-). Current CVS version of
hostapd supports RADIUS Accounting (RFC 2866). I have tested this
successfully with FreeRADIUS, but if someone happens to test it with
other RADIUS servers, I would be interested in test results. Actually,
same goes for 802.1x authentication server since I have only used
FreeRADIUS for that, too.

Accounting support in hostapd should work with and without 802.1x. An
example command line for running without .1x and using local RADIUS
accounting server:

./hostapd -o127.0.0.1 -A127.0.0.1 -E12345678 wlan0

-o own address for NAS-IP-Address
-A RADIUS Accounting server IP address
-E shared secret with accounting server

I haven't yet tested accounting with 802.1x, but it should work. You can
use either the same RADIUS server as both authentication server and
accounting server or use different servers for auth/acct.


-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Dec 17 21:17:11 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 17 Dec 2002 21:17:11 -0800
Subject: Hostap and 802.1X
In-Reply-To: <20021217134850.5264.qmail@web10903.mail.yahoo.com>
References: <20021217134850.5264.qmail@web10903.mail.yahoo.com>
Message-ID: <20021218051711.GB2409@jm.kir.nu>

On Tue, Dec 17, 2002 at 05:48:49AM -0800, Nikhil Chauhan wrote:

> Now, I wish to test the authenticator functionality of the Open1x. It seems the 
> authenticator doesn't have a proper functioning Key transmit state machine as
> well as the key receive state machine. My questions are based on the above tests:
> 1. Can the HostAP code be used in place of the open1x authenticator? What 
>     relation do they have with each other?

Yes, hostapd implements IEEE 802.1x Authenticator, including key
transmit state machine. Apart from implementing same standard, Host AP
code and Open1x do not really have any relation with each other.

> 2. Does the HostAP support the 4-way pairwise key and the group key handshaking
>     thereby installing the keys? If no, is there any other freeware to achieve this?

I'm assuming you are refering to IEEE 802.11i draft with this. I haven't
implemented 4-way handshake yet (or to be more exact, anything from that
draft). hostapd implementation of authenticator is able to install both
unicast and broadcast keys with 802.1x style, but not with method
specified in IEEE 802.11i draft. I'm not aware of any open source
implementation of IEEE 802.11i draft.

-- 
Jouni Malinen                                            PGP id EFC895FA



From antonio.vilei  Wed Dec 18 00:35:36 2002
From: antonio.vilei (Antonio Vilei)
Date: Wed, 18 Dec 2002 09:35:36 +0100
Subject: difference between Prism2 and other chipsets for AP features
Message-ID: <004401c2a670$701ecd50$151e0a0a@stmantoniov>

Hi all,
what is the difference between Prism2 and other chipset for AP specific
features?
Is it possible to implement a driver such as HostAP (with AP features) for
other chipsets?

Thanks in advance,
Antonio











From rob  Wed Dec 18 05:11:42 2002
From: rob (Rob Schrack)
Date: Wed, 18 Dec 2002 08:11:42 -0500
Subject: Accounting support for Radius
References: <5.1.0.14.0.20021123185440.00af9d98@mail.marekroy.com> <20021218050606.GA2409@jm.kir.nu>
Message-ID: <042201c2a697$02628a00$070012ac@schrack.net>

> Yes, I have started and also finished ;-). Current CVS version of
> hostapd supports RADIUS Accounting (RFC 2866). I have tested this
> successfully with FreeRADIUS, but if someone happens to test it with
> other RADIUS servers, I would be interested in test results. Actually,
> same goes for 802.1x authentication server since I have only used
> FreeRADIUS for that, too.

Excellent timing!  I was just wondering the same thing myself...

I have everything except WEP rekeying working with Steel Belted 
RADIUS 4.0/Enterprise.  Authentication is using TLS with certificates cut
from a Microsoft Enterprise CA.  Client is a Windows 2000 laptop using 
the MS 802.1x authentication client.

Accounting appears to work with it as well.  Starts & stops appear when
expected.

Command line is:
hostapd -SSSID -x -o192.168.0.1 -a192.168.0.2 -spwd \
-A192.168.0.2 -Epwd -t300 wlan0

Quick question tho:  If -E is not given, does the password for accounting 
default to the authentication password?

Great work!

Rob




From Laurentiu-Sorin.Paun  Wed Dec 18 06:44:41 2002
From: Laurentiu-Sorin.Paun (Sorin PAUN)
Date: Wed, 18 Dec 2002 15:44:41 +0100
Subject: Scans
Message-ID: <3E0089D9.7060502@imag.fr>

Please tell me if I understood the scan mechanism in HostAP:

-in firmware-based roaming mode (prism2_param wlan0 host_roaming 0), the 
firmware do scans whenever the link quality is poor, and the AP with the 
best signal level is chosen.

-in host-based roaming mode (prism2_param wlan0 host_roaming 1), the 
firmware continues to do scans when the link quality is poor, but the AP 
is chosen in the driver (prism2_host_roaming() ), looking also to 
preferred_ap setting. In this mode; the driver can also command a part 
of scans.

How (which type - active or passive) are this scans done ? It seems that 
the scans commanded by SIOCSIWSCAN are done also by the firmware, by 
setting the HFA384X_RID_SCANREQUEST.  What I don't really understand is 
why a JoinRequest is made at every scan results 
(HFA384X_INFO_SCANRESULTS) , even then when the best AP is in fact the 
current AP. Does this slows the card someway, and if it slows, could one 
eliminate the JoinRequest in the case of a same AP?


I've also noticed that for sta f/w>1.3.0, we can command a 
HFA384X_RID_HOSTSCAN, and will we obtain a HFA384X_INFO_HOSTSCANRESULTS 
frame. How is this different (what means "it keeps old association 
status") ? It doesn't made/ We don't have to make a JoinRequest every time?


Abous the passive scans , I see that this can be do by a private ioctl. 
How the passive is done by the f/w and what the results of these passive 
scans are : a HFA384X_INFO_SCANRESULTS or HFA384X_INFO_HOSTSCANRESULTS 
info frame?

Thank you all for this great work,
-- 
________________________________________________________________________
Sorin PAUN                           mailto:Laurentiu-Sorin.Paun at imag.fr

Doctorant INPG                             http://drakkar.imag.fr/~lpaun

Laboratoire LSR-IMAG, Equipe Drakkar
681, rue de la Passerelle - BP 72          phone: (+33) (0)4 76 82 72 12
38402 St Martin d'H?res Cedex - France       fax: (+33) (0)4 76 82 72 87
________________________________________________________________________




From dan  Tue Dec 17 14:55:36 2002
From: dan (Daniel Feldman)
Date: Tue, 17 Dec 2002 16:55:36 -0600
Subject: CISCO 350 card--> the open HOSTAP Challenge ... 
Message-ID: <HBEPKIMCNAHKLBDCJMPACEBECAAA.dan@baselinesys.com>

Prologe
 My apologizes for first using hotmail to send out an HTML draft of
this email. (i guess it got all messed up, thanks Jason for the heads up)

to begin ... over 37 hours spent working out this problem ... so
 far no success...

The goal: to get a public IP address (via PPPOE) on the win2k box
 via a win2k - cisco350 card - air - cisco350 card - Linux - 3com card -
adsl device...

I have two computers... (yay)
1. sony viao laptop p233 Debian 2.4.18 - Cisco 350 pcmcia - and 3com pcmcia
patched to ADSL device.

2. thinkpad - win2k - Cisco 350 pcmcia (primary workstation)

I want to have the win2k box able to wirelessly get on the internet with the
public IP. I need to pppoe running in general to get on the big "I" via my
adsl ISP... so my solution thus far is to pppoe from the linux box and
iptables masq 192.168 for the win2k.... yay! i have internet connectivity on
the win2k but my ideal solution would be to raspppoe through the linux box
so to get the public IP on the win2k...  when I replace the wireless
adhoc(yuck) connection between the two with a wired one (swap out the cisco
350 in the linux and use another 3com pcmcia card I got lying around and
crossover into the builtin eth on the thinkpad), the BRCTL bridging stuff
works..

the ff.ff.ff.ff MAC broadcast from the win2k is propagated across the bridge
.. the adsl device replies with its MAC..then the win2k box sends a directed
MAC packet to the adsl device ... SUCCESS!! the raspppoe establishes and
wa-la I have the public IP on the win2k.

the motivation: lets just say there is a beautiful lady across the pond
which I would like to netmeeting with but do not want to go through the
trouble of running through a h323 gateway...tried it but its hard to get
such a fair thing to work out those gatekeeper junk commands in a
swiss-german localed pc :-(

of course the two cisco350's are adhoc for previously mentioned current
setup to work wirelessly BUT not its no able to get the darn public IP on
the win2k box...  here is what I try when on the linux, I kill the pppoe
session... replace the wired solution with the cisco350 pcmcia ..then brctl
(bridge) the two eth's (eth0-3com eth1-cisco350) and then try to raspppoe
from the win2k box...  BUT when I try to do this via the ad-hoc wireless
(350 to 350) connection.. its seems (from ethereal running
 on the linux eth1) that after the ADSL device replies with its MAC .. the
win2k box will then send a packet ONLY TO the MAC of the linux cisco 350
card... (darn you cisco win2k ad-hoc mode)

SO THE OPEN HOSTAP CHALLENGE is for someone to work out the cisco350 hostap
solution so that I can video conf with my baby overseas!!! I believe with
one of these cards in AP mode and the other associating.. I will not have
the layer-2 limitation that I currently have when running in adhoc mode.

I PUT THIS CHALLEGE TO YOU!! I know "you" can do it.(in fact from scouring
this archive... someone has kinda.... besides is must burn you that cisco's
AP costs $600.. with no free solution for cisco cards....) lets make this
thing happen in linux... some one has said it may require a modified airo.o
or something.. whatever... just lets do this thing... and since im begging
into the wind..
 why not write a nice howto for it once its done...
you all rock hard! thanks in advance...

 -Dan




From Pavel.Vondricka  Wed Dec 18 09:05:57 2002
From: Pavel.Vondricka (Pavel Vondricka)
Date: Wed, 18 Dec 2002 16:05:57 -0100
Subject: TXPOWER has no impact on ZCOM XI-325H (final report)
In-Reply-To: <20021218021206.B8167@hzdhome.home.blkseanet.ru>
References: <200212140253.49324.Pavel.Vondricka@ff.cuni.cz> <200212180017.32539.Pavel.Vondricka@ff.cuni.cz> <20021218021206.B8167@hzdhome.home.blkseanet.ru>
Message-ID: <200212181605.58347.Pavel.Vondricka@ff.cuni.cz>

> So what difference were you able to measure? What did you use for
> measurements?

It was very simple. The build-in antennas didn't help very much, the signal 
was almost the same or changig too much by itself. We used two notebooks, 
each with one card (XI-325 and XI-325H). Later we tried to cennect a 
directional antenna (about 16-18dB) to the transmitting card (Linux+hostap). 
The receiving notebook (Win+NetStumbler) was across a hall in another room 
(at least 5m distance, may be more). When the receiving computer stayed 
without movement and I changed the txpower, we could see in NetStumbler 
graphical view of the received signal steps going down, as I changed the 
txpower from 20 to 10,0,-10,-20,aso. The steps were not linear - first steps 
were small about a few dB, then may be greatest when going down from 10 to 0 
(or 0 to -10?) of about 15dB. I think it would be better to measure somewhere 
outside.

At the end my friend just moved the notebook (on the lap) a little bit and the 
signal strength went up by some 10-20dB again without any change. When he 
moved the notebook back to about the same position, the signal came down to 
the same level as before. Nevertheless I hope our results were not 
accidental, because the signal was in the stable position really quite stable 
and the "steps" in the graph were stable, even though short (just a few 
seconds). But he has done some measurements with his XI-626 in his room and 
the results were similar. So I think the problems we had were caused by the 
omnidirectional build-in antennas and maybe reflecting walls(?). 

>
> Wed, Dec 18, 2002 at 12:17:32AM -0100 Pavel Vondricka wrote about Re:
> TXPOWER has no impact on ZCOM XI-325H (final report)
>
> > Final report for concerned:
> >
> > Today we tested both XI-325 and XI-325H and it seems that the first one
> > really can control it's output power, but not the second one. The
> > conditions were quite strange - the signal changed much more just by
> > itself (maybe strong reflections from the concrete walls?). A small
> > movement with a notebook made much greater change in signal strength than
> > any regulation, however there really were some visible changes in the
> > strength, when the situation got stable. But there was no change with the
> > XI-325H at all.

-- 
###########################################################################
# mailto:Pavel.Vondricka at ff.cuni.cz / ICQ:143159880 
# http://web.ff.cuni.cz/~vondric
#
# Muzete mi psat cesky s libovolnym kodovanim (UTF-8, ISO-8859-2,
# windows-1250, atd. ...)
###########################################################################



From hazard  Wed Dec 18 11:38:06 2002
From: hazard (Vladimir Ivaschenko)
Date: Wed, 18 Dec 2002 21:38:06 +0200
Subject: TXPOWER has no impact on ZCOM XI-325H (final report)
In-Reply-To: <200212181605.58347.Pavel.Vondricka@ff.cuni.cz>
References: <200212140253.49324.Pavel.Vondricka@ff.cuni.cz> <200212180017.32539.Pavel.Vondricka@ff.cuni.cz> <20021218021206.B8167@hzdhome.home.blkseanet.ru> <200212181605.58347.Pavel.Vondricka@ff.cuni.cz>
Message-ID: <20021218213806.A9225@hzdhome.home.blkseanet.ru>

Wed, Dec 18, 2002 at 04:05:57PM -0100 Pavel Vondricka wrote about Re: TXPOWER has no impact on ZCOM XI-325H (final report)

> > So what difference were you able to measure? What did you use for
> > measurements?
> 
> It was very simple. The build-in antennas didn't help very much, the signal 
> was almost the same or changig too much by itself. We used two notebooks, 
> each with one card (XI-325 and XI-325H). Later we tried to cennect a 
> directional antenna (about 16-18dB) to the transmitting card (Linux+hostap). 
> The receiving notebook (Win+NetStumbler) was across a hall in another room 
> (at least 5m distance, may be more). When the receiving computer stayed 

Not very scientific. :-) However looks like it really makes difference for
XI-325, and considering that it's low power, there is no reason for ZCom
to use their own amplifier design instead of the standard one. I have a
spectrum analyzer here, but I don't have XI-325. My tests on XI-325H had
similar results to yours and showed that changing on txpower does not
alter its behavior.

-- 
Best Regards
Vladimir Ivaschenko
http://www.hazard.maks.net/



From ariel  Wed Dec 18 09:34:10 2002
From: ariel (ariel at fismat.umich.mx)
Date: Wed, 18 Dec 2002 17:34:10 -0000 (UTC)
Subject: AP pings client, client not pinging AP, why?
In-Reply-To: <004401c2a670$701ecd50$151e0a0a@stmantoniov>
References: <004401c2a670$701ecd50$151e0a0a@stmantoniov>
Message-ID: <36962.148.216.6.188.1040232850.squirrel@fismat.umich.mx>

Gee,

You guys rock! im just beggining with this wireless thing and im impressed.
I finally got my Linksys WPC11 card working on linux as an AP.

But now i have another problem, my client (WinME Box + WMP11 PCI). Detects
de AP and in the Linksys Config Maganer (or somthing like that) it gets
connected and even shows a 80% link quality, in additon the AP can ping
the WinMe box.

The problem: Even thought the AP can ping the WinMe Box , the WinMe
box(192.168.2.5) cannot ping the AP (192.168.2.6).
The AP cannot do a smbclient session with de billy'$ box...
i cant establish any kind of conection with the AP from the billy'$ box.

Strange thing: I configured SMB using SWAT and the WinMe box can see the
Smbserver, yes it appears in the WinExplorer, but i cant connect.

i thought first that it was a firewall problem, so i deactivated totally
my firewall. Also, if i connect my 2 compus using ethernet there is not
any problem.

Ariel Molina





From jt  Wed Dec 18 15:09:53 2002
From: jt (Jean Tourrilhes)
Date: Wed, 18 Dec 2002 15:09:53 -0800
Subject: What Am I Missing?
Message-ID: <20021218230953.GA489@bougret.hpl.hp.com>

Les Bell wrote :
> In file included from /usr/src/linux/include/linux/wireless.h:70,
>                  from prism2_srec.c:20:
> /usr/src/linux/include/linux/ethtool.h:18: parse error before `u32'
> /usr/src/linux/include/linux/ethtool.h:18: warning: no semicolon at end of
> struct or union
> /usr/src/linux/include/linux/ethtool.h:19: warning: type defaults to `int'
> in declaration of `supported'

	Hu ? What's that ? I believe ethtool should not find it's way
to user space, and it's never included from wireless.h.
	Can you cut'n'paste the first 100 lines of wireless.h in an
e-mail on the list ? Also, can you reproduce that with an official
kernel from kernel.org (not a Red-Hat kernel) ?
	Some people may argue that prism2_srec.c should include
/usr/include/linux/wireless.h, but that's another story.

	Regards,

	Jean



From jt  Wed Dec 18 16:13:24 2002
From: jt (Jean Tourrilhes)
Date: Wed, 18 Dec 2002 16:13:24 -0800
Subject: What Am I Missing?
In-Reply-To: <OF5E607EEF.FFF6B6BE-ONCA256C93.008100F7@lesbell.com.au>
References: <OF5E607EEF.FFF6B6BE-ONCA256C93.008100F7@lesbell.com.au>
Message-ID: <20021219001324.GB841@bougret.hpl.hp.com>

On Thu, Dec 19, 2002 at 10:44:20AM +1100, Les Bell wrote:
> 
> Jean Tourrilhes <jt at bougret.hpl.hp.com> wrote:
> 
> >>
> Hu ? What's that ? I believe ethtool should not find it's way
> to user space, and it's never included from wireless.h.
> <<
> 
> Jean, if anyone should know, you should - and yet, lines 65 - 70 of
> wireless.h read:
> 
> /***************************** INCLUDES *****************************/
> 
> #include <linux/types.h>                /* for "caddr_t" et al          */
> #include <linux/socket.h>               /* for "struct sockaddr" et al  */
> #include <linux/if.h>                   /* for IFNAMSIZ and co... */
> #include <linux/ethtool.h>
> 
> The header reads:
> 
> /*
>  * This file define a set of standard wireless extensions
>  *
>  * Version :    13      6.12.01
>  *
>  * Authors :    Jean Tourrilhes - HPL - <jt at hpl.hp.com>
>  * Copyright (c) 1997-2001 Jean Tourrilhes, All Rights Reserved.
>  */
> 
> It appears to be part of the Red Hat kernel-source-2.4.18-18.7.x package.
> Perhaps RH have modified it?

	Definitely. If you look into the Wireless Tool package, you
will find all version of wireless.h as I put them in the kernel. And
as far as can see, neither 2.5.51 nor 2.4.21-pre1 from kernel.org has
this change.
	(And by the way, this change doesn't make much sense)
	In the long term, I plan to remove all #include from
wireless.h, because it created problems in user space, but this will
probably take another year (time for the proper iwlib and fixes to go
in all user space package).

> Looking at where the compiler squawks on ethtool.h:
> 
> /* This should work for both 32 and 64 bit userland. */
> struct ethtool_cmd {
>         u32     cmd;
>         u32     supported;      /* Features this interface supports */
>         u32     advertising;    /* Features this interface advertises */
>         u16     speed;          /* The forced speed, 10Mb, 100Mb, gigabit
> */
>         u8      duplex;         /* Duplex, half or full */
>         u8      port;           /* Which connector port */
>         u8      phy_address;
>         u8      transceiver;    /* Which tranceiver to use */
>         u8      autoneg;        /* Enable or disable autonegotiation */
>         u32     maxtxpkt;       /* Tx pkts before generating tx int */
>         u32     maxrxpkt;       /* Rx pkts before generating rx int */
>         u32     reserved[4];
> };
> 
> It looks to me as though the compiler hasn't yet seen a #define or typedef
> for u32, u16, etc.

	Correct, because they are kernel specific. Only the '_'
prefixed version are availalble in user space (that's why I say this
file should never go in user space).

> My next line of attack is going to be to find where they
> are defined, and get that #include'd. . .

	Just nuke the offensive #include in wireless.h, that might
work fine.

> Thanks,
> 
> Best,
> 
> --- Les Bell, CISSP

	Regards,

	Jean



From lesbell  Wed Dec 18 16:27:11 2002
From: lesbell (Les Bell)
Date: Thu, 19 Dec 2002 11:27:11 +1100
Subject: What Am I Missing?
Message-ID: <OFFE52824C.EEC1383B-ONCA256C94.000252EC@lesbell.com.au>

Jean Tourrilhes <jt at bougret.hpl.hp.com> wrote:

>>
Just nuke the offensive #include in wireless.h, that might
work fine.
<<

And, indeed, it does. Very helpful of RH to modify wireless.h like that,
huh?

Thanks again,

Best,

--- Les Bell, CISSP
[http://www.lesbell.com.au]





From lesbell  Wed Dec 18 16:37:27 2002
From: lesbell (Les Bell)
Date: Thu, 19 Dec 2002 11:37:27 +1100
Subject: What Am I Missing?
Message-ID: <OF2B544992.2C825D8C-ONCA256C94.0002D3F1@lesbell.com.au>

"Jason Boxman" <jasonb at edseek.com> wrote:

>>
> They talk perfectly happily in Ad-Hoc mode, but whenever I put the Linux
box into Master mode and the Win2K box into its "Infrastructure" mode,
the game is over. Nothing. Nada. Zip.

What STA firmware is on the MA401?
<<

OK, thanks to Jean's pointers, I'm back in the game. . .

./hostap_diag wlan0
Host AP driver diagnostics information for 'wlan0'

NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.0.7
STAID: id=0x001f v1.3.6 (station firmware)

I'm guessing that's pretty old station firmware, right?

>>
Does the W2K station associate with the HostAP Box in Master mode?
<<

As mentioned previously, no association - the W2K machine shows "scanning".
Basically, everything works fine in Ad-Hoc mode - I'm using it right now -
but no association with the HostAp box in "Master" mode and the W2K in
"Infrastructure" mode.

Best,

--- Les Bell, CISSP
[http://www.lesbell.com.au]





From jkmaline  Wed Dec 18 20:03:50 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 18 Dec 2002 20:03:50 -0800
Subject: difference between Prism2 and other chipsets for AP features
In-Reply-To: <004401c2a670$701ecd50$151e0a0a@stmantoniov>
References: <004401c2a670$701ecd50$151e0a0a@stmantoniov>
Message-ID: <20021219040350.GA1097@jm.kir.nu>

On Wed, Dec 18, 2002 at 09:35:36AM +0100, Antonio Vilei wrote:

> what is the difference between Prism2 and other chipset for AP specific
> features?

Prism2 chipset was the first 802.11b chipset (at least for me) that
supported methods for performing part of the 802.11 management
functionality in the host driver (so called Host AP mode) and for which
there was some documentation available to describe how to use this mode.

I would assume that many of the new chipsets would offer something
similar, or better, for host-based operations. Alas, getting
documentation for writing open source drivers for these might prove to
be next to impossible..

> Is it possible to implement a driver such as HostAP (with AP features) for
> other chipsets?

Yes.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Dec 18 20:07:28 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 18 Dec 2002 20:07:28 -0800
Subject: Accounting support for Radius
In-Reply-To: <042201c2a697$02628a00$070012ac@schrack.net>
References: <5.1.0.14.0.20021123185440.00af9d98@mail.marekroy.com> <20021218050606.GA2409@jm.kir.nu> <042201c2a697$02628a00$070012ac@schrack.net>
Message-ID: <20021219040728.GB1097@jm.kir.nu>

On Wed, Dec 18, 2002 at 08:11:42AM -0500, Rob Schrack wrote:

> Quick question tho:  If -E is not given, does the password for accounting 
> default to the authentication password?

No, you will need to set both just like you need to set both IP
addresses even if you are using the same RADIUS server for
authentication and accounting. Anyway, I should really replace that
command line way of configuring things with a configuration file. It is
not really that wise to require passwords to be set on command line and
there is already quite a few options to make the command lines complex.

-- 
Jouni Malinen                                            PGP id EFC895FA



From thanag  Thu Dec 19 04:17:46 2002
From: thanag (Theodore Anagnostopoulos)
Date: Thu, 19 Dec 2002 04:17:46 -0800 (PST)
Subject: HostAP installation guide for wireless card?
Message-ID: <20021219121746.47619.qmail@web11308.mail.yahoo.com>

Dear all,

Does anybody know to tell me where to find information
about how to install the hostAP on a DWL-650 wireless
card? - You know a some kind of README file...

I can't make sense from README.prism2...

Thanks,
TED.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com



From dave  Thu Dec 19 11:14:13 2002
From: dave (David C Wang)
Date: Thu, 19 Dec 2002 11:14:13 -0800
Subject: Linux Route/Loopback Problem - 2 STAs on same machine
Message-ID: <B2FC93133CB3EB4A813CBD19717B14881FB4C5@aruba-server.arubanetworks.com>

Hi,

I've been unable to resolve this problem for a while.  Hopefully
someone can help me out.  I've already posted this question to
comp.os.linux.networking with no luck.  I'll probably also post 
to linux-wlan.

I have 2 wireless interfaces on the *same machine* wlan0 and wlan1
(linux-wlan), and am trying to test an ap (hostap) by having both
interfaces wlan0 and wlan1 speak to each other via the ap.  Both
interfaces associate just fine, but i'm having trouble setting up the
linux routes so that the stas can ping each other.  I'm hoping that
someone on this list has tried this before.

It seems that linux is ignoring the routing table for local network
devices, and forcing the route through the loopback device.  Is there
any way to get around this?

Here's a description of the problem.  On the same computer, I have
interfaces wlan0 (192.168.0.10) and wlan1 (192.168.0.11).  I want to
ping from wlan0 to wlan1, and make the packet physically hit the
radio, instead of going through the loopback netdevice.

I enable ip_forwarding
  echo "1" > /proc/sys/net/ipv4/ip_forward 
I clear the kernel routing cache
  echo "1" > /proc/sys/net/ipv4/route/flush

Then, I modify my routing tables to say that packets going to
192.168.0.10 (wlan0) should exit through the wlan1 netdevice, and vice
versa:

  dave:/home/dave# route add -host 192.168.0.11 dev wlan0
  dave:/home/dave# route add -host 192.168.0.10 dev wlan1
  dave:/home/dave# route -n
  Kernel IP routing table
  Destination  Gateway      Genmask         Flags Metric Ref  Use Iface
  192.168.0.10 0.0.0.0      255.255.255.255 UH    0      0      0 wlan1
  192.168.0.11 0.0.0.0      255.255.255.255 UH    0      0      0 wlan0
  10.1.1.0     0.0.0.0      255.255.255.0   U     0      0      0 eth0
  0.0.0.0      10.1.1.254   0.0.0.0         UG    0      0      0 eth0

Then I ping 192.168.0.10, which should get routed through the second
netdevice wlan1, but the packet still goes through the loopback
netdevice, instead of directly out the physical device.

  dave:/home/dave#  ping -c 1 192.168.0.10
  PING 192.168.0.10 (192.168.0.10): 56 data bytes
  64 bytes from 192.168.0.10: icmp_seq=0 ttl=64 time=0.0 ms
  --- 192.168.0.10 ping statistics ---
  1 packets transmitted, 1 packets received, 0% packet loss
  round-trip min/avg/max = 0.0/0.0/0.0 ms

To verify, I check the Kernel Routing Cache, which indeed shows that
pings to 192.68.0.10 will go through the loopback device.

  dave:/home/dave# route -nC|grep -v 10                
  Kernel IP routing cache
  Source        Destination   Gateway       Flags Metric Ref  Use Iface
  192.168.0.11  192.168.0.11  192.168.0.11  l     0      0      0 lo
  192.168.0.11  192.168.0.11  192.168.0.11  l     0      0      0 lo
  192.168.0.10  192.168.0.10  192.168.0.10  l     0      0      1 lo
  192.168.0.10  192.168.0.10  192.168.0.10  l     0      0      1 lo

I try again by modifying the routing tables to include a gateway for
each device.  But I get the same result, and the same output from the
kernel routing cache.

  da:/home/dave# route add -host 192.168.0.11 gw 192.168.0.10 dev wlan0
  da:/home/dave# route add -host 192.168.0.10 gw 192.168.0.11 dev wlan1
  dave:/home/dave# route -n
  Kernel IP routing table
  Destination  Gateway      Genmask         Flags Metric Ref Use Iface
  192.168.0.10 192.168.0.11 255.255.255.255 UGH   0      0     0 wlan1
  192.168.0.11 192.168.0.10 255.255.255.255 UGH   0      0     0 wlan0
  10.1.1.0     0.0.0.0      255.255.255.0   U     0      0     0 eth0
  0.0.0.0      10.1.1.254   0.0.0.0         UG    0      0     0 eth0

I am also aware of the "local" routing table accessible through the
old linux-2.2 "iproute2" interface.

  dave:/home/dave# ip route show table local|grep 192
  broadcast 192.168.0.255 dev wlan0  proto kernel  scope link  src
192.168.0.10 
  broadcast 192.168.0.255 dev wlan1  proto kernel  scope link  src
192.168.0.11 
  local 192.168.0.11 dev wlan1  proto kernel  scope host  src
192.168.0.11 
  local 192.168.0.10 dev wlan0  proto kernel  scope host  src
192.168.0.10 
  broadcast 192.168.0.0 dev wlan0  proto kernel  scope link  src
192.168.0.10 
  broadcast 192.168.0.0 dev wlan1  proto kernel  scope link  src
192.168.0.11 

So I try to swap the sources also in this table for each device

  dave:/home/dave# ip route change table local local 192.168.0.10 dev
wlan1 \
		  proto kernel scope host src 192.168.0.11
  dave:/home/dave# ip route change table local local 192.168.0.11 dev
wlan0 \
		  proto kernel scope host src 192.168.0.10

And this is what i get.

  dave:/home/dave# ip route show table local|grep 192
  broadcast 192.168.0.255 dev wlan0  proto kernel  scope link  src
192.168.0.10 
  broadcast 192.168.0.255 dev wlan1  proto kernel  scope link  src
192.168.0.11 
  local 192.168.0.11 dev wlan0  proto kernel  scope host  src
192.168.0.10 
  local 192.168.0.10 dev wlan1  proto kernel  scope host  src
192.168.0.11 
  broadcast 192.168.0.0 dev wlan0  proto kernel  scope link  src
192.168.0.10 
  broadcast 192.168.0.0 dev wlan1  proto kernel  scope link  src
192.168.0.11 

Again, when i try to ping it goes through the loopback device.  The
routing cache verifies this again.

It seems that linux is ignoring the routing table for local network
devices, and forcing the route through the loopback device.  Is there
any way to get around this?

thanks,
-dave
dave at davidwang dot c*m








From cornelisse  Thu Dec 19 12:25:38 2002
From: cornelisse (Cornelisse)
Date: Thu, 19 Dec 2002 21:25:38 +0100
Subject: cant load hostap_cs.o with senoa EL2511CD PLUS Ext2
Message-ID: <000f01c2a79c$d57d7160$0201a8c0@vthoog.nl>

I'm runnig redhat 7.1 with a newly compiled 2.4.20 kernel and pcmcia-cs
3.2.3 

So far I've compiled the hostap 2002-10-12 drive with the make pccard &
make pccard_install command

After that I've restarted the pcmcia card services with 'service pcmcia
restart', after that I got the error: hostap_cs: (c) Jouni Malinen
,jkmaline at cc.hut.fi> hostap_cs: Cardservices release does not match!

Googling this error told me that I could ignore this, since it just
tells me that cardmgr is somewhat different than some of the drivers.

But when when I try insmod the following error occurs: 

Dec 19 20:18:42 toshiba kernel: eth0: flipped to 10baseT
Dec 19 20:18:45 toshiba kernel: eth0: lost link beat
Dec 19 20:18:55 toshiba cardmgr[467]: executing: 'modprobe -r hostap_cs'
Dec 19 20:18:55 toshiba cardmgr[467]: executing: './network check eth0'
Dec 19 20:18:56 toshiba cardmgr[467]: executing: './network stop eth0'
Dec 19 20:18:58 toshiba cardmgr[467]: executing: 'modprobe -r
smc91c92_cs'
Dec 19 20:18:58 toshiba cardmgr[467]: exiting
Dec 19 20:18:59 toshiba kernel: Trying to free nonexistent resource
<000003e0-000003e1>
Dec 19 20:18:59 toshiba kernel: unloading PCMCIA Card Services
Dec 19 20:18:59 toshiba kernel: Linux PCMCIA Card Services 3.2.3
Dec 19 20:18:59 toshiba kernel:   kernel build: 2.4.20 #1 SMP Thu Dec 19
15:54:43 CET 2002
Dec 19 20:18:59 toshiba kernel:   options:  [pci] [cardbus] [apm]
Dec 19 20:18:59 toshiba kernel: Intel ISA/PCI/CardBus PCIC probe:
Dec 19 20:18:59 toshiba kernel:   Intel i82365sl B step rev 00
ISA-to-PCMCIA at port 0x3e0 ofs 0x00
Dec 19 20:18:59 toshiba kernel:     host opts [0]: none
Dec 19 20:18:59 toshiba kernel:     host opts [1]: none
Dec 19 20:19:00 toshiba kernel:     ISA irqs (scanned) = 3,4,5,7,9,11
status change on irq 11
Dec 19 20:19:00 toshiba cardmgr[1058]: watching 2 sockets
Dec 19 20:19:00 toshiba cardmgr[1059]: starting, version is 3.2.3
Dec 19 20:19:00 toshiba kernel: cs: memory probe 0x0d0000-0x0dffff:
clean.
Dec 19 20:19:00 toshiba cardmgr[1059]: socket 0: Senao
SL-2011CD/SL-2011CDPLUS
Dec 19 20:19:00 toshiba cardmgr[1059]: executing: 'modprobe hostap_cs'
Dec 19 20:19:01 toshiba kernel: hostap_cs: hostap_cs.c 0.0.0 2002-10-12
(SSH Communications Security Corp, Jouni Malinen)
Dec 19 20:19:01 toshiba kernel: hostap_cs: (c) Jouni Malinen
<jkmaline at cc.hut.fi>
Dec 19 20:19:01 toshiba kernel: hostap_cs: CardServices release does not
match!
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: init_module: Operation not
permitted
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: insmod
/lib/modules/2.4.20/pcmcia/hostap_cs.o failed
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: insmod hostap_cs failed
Dec 19 20:19:01 toshiba cardmgr[1059]: + Hint: insmod errors can be
caused by incorrect module parameters, including invalid IO or IRQ
parameters
Dec 19 20:19:01 toshiba cardmgr[1059]: modprobe exited with status 255
Dec 19 20:19:01 toshiba cardmgr[1059]: executing: 'insmod
/lib/modules/2.4.20/pcmcia/hostap_cs.o'
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_remove_proc_Rsmp_90eecd87
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_set_antsel_Rsmp_f31a9ba2
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_dump_tx_header_Rsmp_3abcbf80
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_rx_Rsmp_515b60cd
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_netif_stop_queues_Rsmp_4cdbe945
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_handle_sta_rx_Rsmp_0b7f9513
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_is_sta_assoc_Rsmp_098b7638
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_handle_sta_tx_Rsmp_5b63ae69
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_get_porttype_Rsmp_69a62f2d
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_netif_wake_queues_Rsmp_0093638e
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_set_word_Rsmp_dcebbc77
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_dump_rx_header_Rsmp_27a069d6
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_init_data_Rsmp_b3706dee
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_free_data_Rsmp_eff1ee39
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_set_encryption_Rsmp_1070ce43
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_handle_sta_crypto_Rsmp_110aee44
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_get_stats_Rsmp_fee89cd2
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_handle_sta_release_Rsmp_27df6133
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_check_sta_fw_version_Rsmp_f3cfcbba
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_setup_dev_Rsmp_e8fd804d
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_set_string_Rsmp_2ede9ae5
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_init_proc_Rsmp_75d78563
Dec 19 20:19:01 toshiba cardmgr[1059]: +
/lib/modules/2.4.20/pcmcia/hostap_cs.o: unresolved symbol
hostap_handle_sta_tx_exc_Rsmp_adaa80f9
Dec 19 20:19:01 toshiba cardmgr[1059]: insmod exited with status 1
Dec 19 20:19:02 toshiba cardmgr[1059]: get dev info on socket 0 failed:
Resource temporarily unavailable
Dec 19 20:19:02 toshiba cardmgr[1059]: socket 1: Farallon Enet
Dec 19 20:19:03 toshiba cardmgr[1059]: executing: 'modprobe smc91c92_cs'
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x0100-0x04ff:
excluding 0x1f8-0x1ff 0x220-0x22f 0x378-0x37f 0x388-0x38f 0x3c0-0x3e7
0x400-0x4c7 0x4d0-0x4ef
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x0200-0x021f: clean.
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x0230-0x0377: clean.
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x0380-0x0387: clean.
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x0390-0x03bf: clean.
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x03e8-0x03ff: clean.
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x04c8-0x04cf: clean.
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x04f0-0x04ff: clean.
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x0a00-0x0aff:
excluding 0xa20-0xa2f
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x0a30-0x0aff: clean.
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x0c00-0x0cff:
excluding 0xc00-0xc7f 0xca0-0xcc7 0xcd0-0xcef
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x0cc8-0x0ccf: clean.
Dec 19 20:19:03 toshiba cardmgr[1059]: executing: './network start eth0'
Dec 19 20:19:03 toshiba kernel: cs: IO port probe 0x0cf0-0x0cff: clean.
Dec 19 20:19:03 toshiba kernel: eth0: smc91c94 rev 1: io 0x100, irq 3,
hw_addr 00:00:C5:56:09:3C
Dec 19 20:19:03 toshiba kernel:   4608 byte buffer, auto xcvr
Dec 19 20:19:03 toshiba modprobe: modprobe: Can't locate module net-pf-4
Dec 19 20:19:03 toshiba modprobe: modprobe: Can't locate module net-pf-5
Dec 19 20:19:04 toshiba /etc/hotplug/net.agent: register event not
handled
Dec 19 20:19:08 toshiba cardmgr[1059]: + SIOCADDRT: File exists







From gallir  Thu Dec 19 12:24:26 2002
From: gallir (Ricardo Galli)
Date: Thu, 19 Dec 2002 21:24:26 +0100
Subject: cant load hostap_cs.o with senoa EL2511CD PLUS Ext2
In-Reply-To: <000f01c2a79c$d57d7160$0201a8c0@vthoog.nl>
References: <000f01c2a79c$d57d7160$0201a8c0@vthoog.nl>
Message-ID: <200212192124.26269.gallir@uib.es>

On Thursday 19 December 2002 21:25, Cornelisse shaped the electrons to 
shout:
> I'm runnig redhat 7.1 with a newly compiled 2.4.20 kernel and pcmcia-cs
> 3.2.3
>
> So far I've compiled the hostap 2002-10-12 drive with the make pccard &
> make pccard_install command

But it seem you didn't specify PCMCIA_PATH en hostap makefile (which must 
be specified if you use external pcmcia modules).


-- 
  ricardo galli       GPG id C8114D34




From khoff  Thu Dec 19 13:49:35 2002
From: khoff (Kristian Hoffmann)
Date: Thu, 19 Dec 2002 13:49:35 -0800 (PST)
Subject: Linux Route/Loopback Problem - 2 STAs on same machine
In-Reply-To: <B2FC93133CB3EB4A813CBD19717B14881FB4C5@aruba-server.arubanetworks.com>
Message-ID: <Pine.LNX.4.44.0212191346080.31173-100000@luaren.pc-intouch.com>

If you have the iproute2 utilities, run "ip route show table local".
Those routes are visited first, so your host routes are never reached.

You can delete the routes in the local table that tell your machine how to
get to its own addresses, and then it will use the host routes you
specify.  The packets will reach the AP and then be sent back to your
other interface.  Since you delete the local routes though, when the other
interface receives the packets, they will be dropped because it won't know
how to route to itself.

In other words, this is just a bad idea.  Get another machine to test
with. :-)

-Kristian

On Thu, 19 Dec 2002, David C Wang wrote:

> Hi,
>
> I've been unable to resolve this problem for a while.  Hopefully
> someone can help me out.  I've already posted this question to
> comp.os.linux.networking with no luck.  I'll probably also post
> to linux-wlan.
>
> I have 2 wireless interfaces on the *same machine* wlan0 and wlan1
> (linux-wlan), and am trying to test an ap (hostap) by having both
> interfaces wlan0 and wlan1 speak to each other via the ap.  Both
> interfaces associate just fine, but i'm having trouble setting up the
> linux routes so that the stas can ping each other.  I'm hoping that
> someone on this list has tried this before.
>
> It seems that linux is ignoring the routing table for local network
> devices, and forcing the route through the loopback device.  Is there
> any way to get around this?
>
> Here's a description of the problem.  On the same computer, I have
> interfaces wlan0 (192.168.0.10) and wlan1 (192.168.0.11).  I want to
> ping from wlan0 to wlan1, and make the packet physically hit the
> radio, instead of going through the loopback netdevice.
>
> I enable ip_forwarding
>   echo "1" > /proc/sys/net/ipv4/ip_forward
> I clear the kernel routing cache
>   echo "1" > /proc/sys/net/ipv4/route/flush
>
> Then, I modify my routing tables to say that packets going to
> 192.168.0.10 (wlan0) should exit through the wlan1 netdevice, and vice
> versa:
>
>   dave:/home/dave# route add -host 192.168.0.11 dev wlan0
>   dave:/home/dave# route add -host 192.168.0.10 dev wlan1
>   dave:/home/dave# route -n
>   Kernel IP routing table
>   Destination  Gateway      Genmask         Flags Metric Ref  Use Iface
>   192.168.0.10 0.0.0.0      255.255.255.255 UH    0      0      0 wlan1
>   192.168.0.11 0.0.0.0      255.255.255.255 UH    0      0      0 wlan0
>   10.1.1.0     0.0.0.0      255.255.255.0   U     0      0      0 eth0
>   0.0.0.0      10.1.1.254   0.0.0.0         UG    0      0      0 eth0
>
> Then I ping 192.168.0.10, which should get routed through the second
> netdevice wlan1, but the packet still goes through the loopback
> netdevice, instead of directly out the physical device.
>
>   dave:/home/dave#  ping -c 1 192.168.0.10
>   PING 192.168.0.10 (192.168.0.10): 56 data bytes
>   64 bytes from 192.168.0.10: icmp_seq=0 ttl=64 time=0.0 ms
>   --- 192.168.0.10 ping statistics ---
>   1 packets transmitted, 1 packets received, 0% packet loss
>   round-trip min/avg/max = 0.0/0.0/0.0 ms
>
> To verify, I check the Kernel Routing Cache, which indeed shows that
> pings to 192.68.0.10 will go through the loopback device.
>
>   dave:/home/dave# route -nC|grep -v 10
>   Kernel IP routing cache
>   Source        Destination   Gateway       Flags Metric Ref  Use Iface
>   192.168.0.11  192.168.0.11  192.168.0.11  l     0      0      0 lo
>   192.168.0.11  192.168.0.11  192.168.0.11  l     0      0      0 lo
>   192.168.0.10  192.168.0.10  192.168.0.10  l     0      0      1 lo
>   192.168.0.10  192.168.0.10  192.168.0.10  l     0      0      1 lo
>
> I try again by modifying the routing tables to include a gateway for
> each device.  But I get the same result, and the same output from the
> kernel routing cache.
>
>   da:/home/dave# route add -host 192.168.0.11 gw 192.168.0.10 dev wlan0
>   da:/home/dave# route add -host 192.168.0.10 gw 192.168.0.11 dev wlan1
>   dave:/home/dave# route -n
>   Kernel IP routing table
>   Destination  Gateway      Genmask         Flags Metric Ref Use Iface
>   192.168.0.10 192.168.0.11 255.255.255.255 UGH   0      0     0 wlan1
>   192.168.0.11 192.168.0.10 255.255.255.255 UGH   0      0     0 wlan0
>   10.1.1.0     0.0.0.0      255.255.255.0   U     0      0     0 eth0
>   0.0.0.0      10.1.1.254   0.0.0.0         UG    0      0     0 eth0
>
> I am also aware of the "local" routing table accessible through the
> old linux-2.2 "iproute2" interface.
>
>   dave:/home/dave# ip route show table local|grep 192
>   broadcast 192.168.0.255 dev wlan0  proto kernel  scope link  src
> 192.168.0.10
>   broadcast 192.168.0.255 dev wlan1  proto kernel  scope link  src
> 192.168.0.11
>   local 192.168.0.11 dev wlan1  proto kernel  scope host  src
> 192.168.0.11
>   local 192.168.0.10 dev wlan0  proto kernel  scope host  src
> 192.168.0.10
>   broadcast 192.168.0.0 dev wlan0  proto kernel  scope link  src
> 192.168.0.10
>   broadcast 192.168.0.0 dev wlan1  proto kernel  scope link  src
> 192.168.0.11
>
> So I try to swap the sources also in this table for each device
>
>   dave:/home/dave# ip route change table local local 192.168.0.10 dev
> wlan1 \
> 		  proto kernel scope host src 192.168.0.11
>   dave:/home/dave# ip route change table local local 192.168.0.11 dev
> wlan0 \
> 		  proto kernel scope host src 192.168.0.10
>
> And this is what i get.
>
>   dave:/home/dave# ip route show table local|grep 192
>   broadcast 192.168.0.255 dev wlan0  proto kernel  scope link  src
> 192.168.0.10
>   broadcast 192.168.0.255 dev wlan1  proto kernel  scope link  src
> 192.168.0.11
>   local 192.168.0.11 dev wlan0  proto kernel  scope host  src
> 192.168.0.10
>   local 192.168.0.10 dev wlan1  proto kernel  scope host  src
> 192.168.0.11
>   broadcast 192.168.0.0 dev wlan0  proto kernel  scope link  src
> 192.168.0.10
>   broadcast 192.168.0.0 dev wlan1  proto kernel  scope link  src
> 192.168.0.11
>
> Again, when i try to ping it goes through the loopback device.  The
> routing cache verifies this again.
>
> It seems that linux is ignoring the routing table for local network
> devices, and forcing the route through the loopback device.  Is there
> any way to get around this?
>
> thanks,
> -dave
> dave at davidwang dot c*m
>
>
>
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From wlan  Thu Dec 19 16:34:01 2002
From: wlan (wlan)
Date: 20 Dec 2002 01:34:01 +0100
Subject: iwconfig wlan0 ap MAC
Message-ID: <1040344441.2985.27.camel@localhost.localdomain>

We have two AP with the same essid but differnt channels 1 and 6 802.11b
roaming work without problems, we have cover from both AP, and we try to
fix to one AP throug command: iwconfig wlan0 ap MAC_AP_TO_FIX
but there is no problem but we get connected always to the other AP, is
this feature supported by hostap as man iwconfig explain?

Thanks in advance





From cornelisse  Thu Dec 19 17:12:44 2002
From: cornelisse (Cornelisse)
Date: Fri, 20 Dec 2002 02:12:44 +0100
Subject: error loading driver (buffer too small)
Message-ID: <002b01c2a7c4$eaa118d0$0201a8c0@vthoog.nl>

After succesfully compiling the hostap-cs driver and firing it up, the
following error occours:

 

wlan0 (WE) : Buffer for request 8B1B too small (0<23)

wlan0 (WE) : Buffer for request 8B1D too small (0<1)

wlan0 (WE) : Buffer for request 8D0B too small (0<308)

 

Any suggestions ?

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021220/092be9fd/attachment.htm 


From jkmaline  Thu Dec 19 18:25:18 2002
From: jkmaline (Jouni Malinen)
Date: Thu, 19 Dec 2002 18:25:18 -0800
Subject: error loading driver (buffer too small)
In-Reply-To: <002b01c2a7c4$eaa118d0$0201a8c0@vthoog.nl>
References: <002b01c2a7c4$eaa118d0$0201a8c0@vthoog.nl>
Message-ID: <20021220022518.GA1008@jm.kir.nu>

On Fri, Dec 20, 2002 at 02:12:44AM +0100, Cornelisse wrote:

> After succesfully compiling the hostap-cs driver and firing it up, the
> following error occours:

> wlan0 (WE) : Buffer for request 8B1B too small (0<23)

That looks like an error message from wireless extensions code in the
kernel. Which version of the kernel are you using? That errors seems to
indicate that the request specified buffer size as 0.. That should
really not happen.. Which program was used to make those WE ioctl calls?
If it was wireless tools (e.g., iwconfig), which version of them?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Thu Dec 19 19:29:48 2002
From: jkmaline (Jouni Malinen)
Date: Thu, 19 Dec 2002 19:29:48 -0800
Subject: iwconfig wlan0 ap MAC
In-Reply-To: <1040344441.2985.27.camel@localhost.localdomain>
References: <1040344441.2985.27.camel@localhost.localdomain>
Message-ID: <20021220032948.GB1008@jm.kir.nu>

On Fri, Dec 20, 2002 at 01:34:01AM +0100, wlan wrote:

> We have two AP with the same essid but differnt channels 1 and 6 802.11b
> roaming work without problems, we have cover from both AP, and we try to
> fix to one AP throug command: iwconfig wlan0 ap MAC_AP_TO_FIX
> but there is no problem but we get connected always to the other AP, is
> this feature supported by hostap as man iwconfig explain?

It is supported, but only with host-based roaming. You need to set this
up with 'prism2_param wlan0 host_roaming 1'.

-- 
Jouni Malinen                                            PGP id EFC895FA



From rpgoldman  Thu Dec 19 19:31:19 2002
From: rpgoldman (rpgoldman at real-time.com)
Date: Thu, 19 Dec 2002 21:31:19 -0600
Subject: problems with Linksys WMP11
Message-ID: <15874.36615.940741.574708@tsathoggua.mydomain>

[I fear that this is a Frequently Asked Question, but I've spent a
couple of hours with the mailing list search and no luck....]

I've been having no end of trouble with my WMP11 card.  I have the
latest hostap, and have it all installed and working.  I am just
trying to use the card in managed mode and connect to a Linksys WAP.

The card DOES become active (I can see it from the WAP).  But I can't
get a working TCP/IP connection no matter what I seem to do.  When I
look at iwconfig's output I see that I'm receiving packets just fine,
but I'm not successfully transmitting ANY.  And they're all misc
failures --- no nwid or encryption failures.

I have checked and the card has the <obscenity> 1.4.2 firmware.  Is
this likely to be causing my problem?  I got the 1.4.9 firmware, but
since I don't have a windows box, I would prefer not to have to flash
it.  I also didn't get any explanation of the firmware files --- there
are just a Pk10100.hex and Sf104090.hex files.  When I try to use
prism2_srec, it complains that the Pk file is inappropriate and the Sf
file is not intended for download to volatile memory.  

As I said, I'm sure this is a frequently-asked question, but I'm a
bear of very little brain, and if anyone could explain, that'd be
fabulous...

With abject gratitude,
R











From jasonb  Thu Dec 19 21:08:40 2002
From: jasonb (Jason Boxman)
Date: Fri, 20 Dec 2002 00:08:40 -0500
Subject: problems with Linksys WMP11
In-Reply-To: <15874.36615.940741.574708@tsathoggua.mydomain>
References: <15874.36615.940741.574708@tsathoggua.mydomain>
Message-ID: <200212200008.40020.jasonb@edseek.com>

On Thursday 19 December 2002 10:31 pm, rpgoldman at real-time.com wrote:
> [I fear that this is a Frequently Asked Question, but I've spent a
> couple of hours with the mailing list search and no luck....]
>
<snip>
> I have checked and the card has the <obscenity> 1.4.2 firmware.  Is
> this likely to be causing my problem?  I got the 1.4.9 firmware, but
> since I don't have a windows box, I would prefer not to have to flash
> it.  I also didn't get any explanation of the firmware files --- there
> are just a Pk10100.hex and Sf104090.hex files.  When I try to use
> prism2_srec, it complains that the Pk file is inappropriate and the Sf
> file is not intended for download to volatile memory.

The reported issues with 1.4.2 are indeed true.  You should flash your card if 
you can or upload 1.4.9 into ram each time you warm boot your machine.

> As I said, I'm sure this is a frequently-asked question, but I'm a
> bear of very little brain, and if anyone could explain, that'd be
> fabulous...

You might check:

http://trekweb.com/~jasonb/articles/hostap_20021012.shtml

> With abject gratitude,
> R
>

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages





From jharana  Thu Dec 19 21:35:50 2002
From: jharana (Jharana Mehta)
Date: Fri, 20 Dec 2002 11:05:50 +0530
Subject: unsubscribe
References: <5.1.0.14.0.20021123185440.00af9d98@mail.marekroy.com> <20021218050606.GA2409@jm.kir.nu> <042201c2a697$02628a00$070012ac@schrack.net> <20021219040728.GB1097@jm.kir.nu>
Message-ID: <3E02AC08.BEFFD666@mahindrabt.com>


unsubscribe

*********************************************************
Disclaimer

This message (including any attachments) contains 
confidential information intended for a specific 
individual and purpose, and is protected by law. 
If you are not the intended recipient, you should 
delete this message and are hereby notified that 
any disclosure, copying, or distribution of this
message, or the taking of any action based on it, 
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: jharana.vcf
Type: text/x-vcard
Size: 238 bytes
Desc: Card for Jharana Mehta
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20021220/94a36f45/attachment.vcf 


From jkmaline  Thu Dec 19 21:54:26 2002
From: jkmaline (Jouni Malinen)
Date: Thu, 19 Dec 2002 21:54:26 -0800
Subject: problems with Linksys WMP11
In-Reply-To: <200212200008.40020.jasonb@edseek.com>
References: <15874.36615.940741.574708@tsathoggua.mydomain> <200212200008.40020.jasonb@edseek.com>
Message-ID: <20021220055426.GB3024@jm.kir.nu>

On Fri, Dec 20, 2002 at 12:08:40AM -0500, Jason Boxman wrote:

> The reported issues with 1.4.2 are indeed true.

Yes, but they should not cause problems when testing the card in
managed mode as was the case in the original question.

-- 
Jouni Malinen                                            PGP id EFC895FA



From cornelisse  Fri Dec 20 00:37:19 2002
From: cornelisse (Cornelisse)
Date: Fri, 20 Dec 2002 09:37:19 +0100
Subject: error loading driver (buffer too small)
In-Reply-To: <20021220022518.GA1008@jm.kir.nu>
Message-ID: <000601c2a803$05e00190$0201a8c0@vthoog.nl>

Yes it was wireless tools, version 25 

Using kernel 2.4.20 (on a p100, 24mb ram)



-----Original Message-----
From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] On Behalf
Of Jouni Malinen
Sent: Friday, December 20, 2002 3:25 AM
To: hostap at shmoo.com
Subject: Re: error loading driver (buffer too small)

On Fri, Dec 20, 2002 at 02:12:44AM +0100, Cornelisse wrote:

> After succesfully compiling the hostap-cs driver and firing it up, the
> following error occours:

> wlan0 (WE) : Buffer for request 8B1B too small (0<23)

That looks like an error message from wireless extensions code in the
kernel. Which version of the kernel are you using? That errors seems to
indicate that the request specified buffer size as 0.. That should
really not happen.. Which program was used to make those WE ioctl calls?
If it was wireless tools (e.g., iwconfig), which version of them?

-- 
Jouni Malinen                                            PGP id EFC895FA
_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap






From msc1  Fri Dec 20 12:06:22 2002
From: msc1 (msc1 at alu.um.es)
Date: Fri, 20 Dec 2002 12:06:22 MET
Subject: eap-md5
Message-ID: <200212201106.MAA07132@zape.um.es>

How can I use Xsupplicant tu use only user and password authentication?

Thanks.





From dave  Thu Dec 19 14:51:40 2002
From: dave (David C Wang)
Date: Thu, 19 Dec 2002 14:51:40 -0800
Subject: Linux Route/Loopback Problem - 2 STAs on same machine
In-Reply-To: <Pine.LNX.4.44.0212191346080.31173-100000@luaren.pc-intouch.com>
Message-ID: <B2FC93133CB3EB4A813CBD19717B14881FB4C6@aruba-server.arubanetworks.com>

Kristian,

> If you have the iproute2 utilities, run "ip route show table local".
> Those routes are visited first, so your host routes are never
> reached.

Thanks for the suggestion on iproute2.  I've already tried modifying
the "local" table directly to do the redirection, but packets were
still looping back.

  dave:/home/dave# ip route change table local local 192.168.0.10 \
		  dev wlan1 proto kernel scope host src 192.168.0.11
  dave:/home/dave# ip route change table local local 192.168.0.11 \
		  dev wlan0 proto kernel scope host src 192.168.0.10

> You can delete the routes in the local table that tell your machine
> how to get to its own addresses, and then it will use the host
> routes you specify.

I did try your suggestion on removing the routes from "local".  The
REALLY GOOD news is that the Kernel IP routing cache is finally
reflecting the intended interface destinations.  Also, doing a
wireless dump of the radio, the packets are indeed hitting the radio
medium.

  dave:/home/dave# route -nC|grep -v 10.
  Kernel IP routing cache
  Source       Destination     Gateway         Flags Metric Ref Use
Iface
  192.168.0.11 192.168.0.10    192.168.0.10    i     0      0     2
wlan1
  192.168.0.10 192.168.0.11    192.168.0.11          0      0     1
wlan0
  192.168.0.11 192.168.0.10    192.168.0.10          0      0     1
wlan1
  192.168.0.10 192.168.0.11    192.168.0.11    i     0      0     2
wlan0

The bad news is that when I attempt to ping STA to STA, I'm not
receiving the replies over any medium, neither loopback nor radio.

The strange thing here is that the "Gateway" field in the Kernel
routing *cache* (above) is set to a value, even though I did not
define it in the Kernel routing *table* (below).  I'm wondering if
this is causing the problem of me not receiving ping replies.

  dave:/home/dave# route add -host 192.168.0.11 dev wlan0
  dave:/home/dave# route add -host 192.168.0.10 dev wlan1
  dave:/home/dave# route -n
  Kernel IP routing table
  Destination  Gateway      Genmask         Flags Metric Ref  Use Iface
  192.168.0.10 0.0.0.0      255.255.255.255 UH    0      0      0 wlan1
  192.168.0.11 0.0.0.0      255.255.255.255 UH    0      0      0 wlan0
  10.1.1.0     0.0.0.0      255.255.255.0   U     0      0      0 eth0
  0.0.0.0      10.1.1.254   0.0.0.0         UG    0      0      0 eth0

> The packets will reach the AP and then be sent back to your other
> interface.  Since you delete the local routes though, when the other
> interface receives the packets, they will be dropped because it
> won't know how to route to itself.

I believe that what you say is correct here.  If I set up a direct
route to the AP and then ping it, then over radio I see a request go
from my wlan0 to the ap (+ control ack), and then a reply go from the
ap to my wlan0 (+ control ack).  The ping reply, however, is never
received by the ping program.

  dave:/home/dave# route add -host 192.168.0.1 dev wlan0
  dave:/home/dave# ping -c 1 192.168.0.1

There must be some way to make the return trip work.  This problem is
90% solved.  Do anyone have any other suggestions?

thanks,
-dave
dave at davidwang dot c*m

------------------------------------------------------------------
# Excerpt from 1st message
I am also aware of the "local" routing table accessible through the old
linux-2.2 "iproute2" interface.

  dave:/home/dave# ip route show table local|grep 192
  broadcast 192.168.0.255 dev wlan0  proto kernel  scope link  src
192.168.0.10 
  broadcast 192.168.0.255 dev wlan1  proto kernel  scope link  src
192.168.0.11 
  local 192.168.0.11 dev wlan1  proto kernel  scope host  src
192.168.0.11 
  local 192.168.0.10 dev wlan0  proto kernel  scope host  src
192.168.0.10 
  broadcast 192.168.0.0 dev wlan0  proto kernel  scope link  src
192.168.0.10 
  broadcast 192.168.0.0 dev wlan1  proto kernel  scope link  src
192.168.0.11 

So I try to swap the sources also in this table for each device

  dave:/home/dave# ip route change table local local 192.168.0.10 dev
wlan1 \
		  proto kernel scope host src 192.168.0.11
  dave:/home/dave# ip route change table local local 192.168.0.11 dev
wlan0 \
		  proto kernel scope host src 192.168.0.10

And this is what i get.

  dave:/home/dave# ip route show table local|grep 192
  broadcast 192.168.0.255 dev wlan0  proto kernel  scope link  src
192.168.0.10 
  broadcast 192.168.0.255 dev wlan1  proto kernel  scope link  src
192.168.0.11 
  local 192.168.0.11 dev wlan0  proto kernel  scope host  src
192.168.0.10 
  local 192.168.0.10 dev wlan1  proto kernel  scope host  src
192.168.0.11 
  broadcast 192.168.0.0 dev wlan0  proto kernel  scope link  src
192.168.0.10 
  broadcast 192.168.0.0 dev wlan1  proto kernel  scope link  src
192.168.0.11 

Again, when i try to ping it goes through the loopback device.  The
routing cache verifies this again.

It seems that linux is ignoring the routing table for local network
devices, and forcing the route through the loopback device.  Is there
any way to get around this?

-----Original Message-----
From: Kristian Hoffmann [mailto:khoff at pc-intouch.com] 
Sent: Thursday, December 19, 2002 1:50 PM
To: David C Wang
Cc: hostap at shmoo.com
Subject: Re: Linux Route/Loopback Problem - 2 STAs on same machine

If you have the iproute2 utilities, run "ip route show table local".
Those routes are visited first, so your host routes are never reached.

You can delete the routes in the local table that tell your machine how
to
get to its own addresses, and then it will use the host routes you
specify.  The packets will reach the AP and then be sent back to your
other interface.  Since you delete the local routes though, when the
other
interface receives the packets, they will be dropped because it won't
know
how to route to itself.

In other words, this is just a bad idea.  Get another machine to test
with. :-)

-Kristian

On Thu, 19 Dec 2002, David C Wang wrote:

> Hi,
>
> I've been unable to resolve this problem for a while.  Hopefully
> someone can help me out.  I've already posted this question to
> comp.os.linux.networking with no luck.  I'll probably also post
> to linux-wlan.
>
> I have 2 wireless interfaces on the *same machine* wlan0 and wlan1
> (linux-wlan), and am trying to test an ap (hostap) by having both
> interfaces wlan0 and wlan1 speak to each other via the ap.  Both
> interfaces associate just fine, but i'm having trouble setting up the
> linux routes so that the stas can ping each other.  I'm hoping that
> someone on this list has tried this before.
>
> It seems that linux is ignoring the routing table for local network
> devices, and forcing the route through the loopback device.  Is there
> any way to get around this?
>
> Here's a description of the problem.  On the same computer, I have
> interfaces wlan0 (192.168.0.10) and wlan1 (192.168.0.11).  I want to
> ping from wlan0 to wlan1, and make the packet physically hit the
> radio, instead of going through the loopback netdevice.
>
> I enable ip_forwarding
>   echo "1" > /proc/sys/net/ipv4/ip_forward
> I clear the kernel routing cache
>   echo "1" > /proc/sys/net/ipv4/route/flush
>
> Then, I modify my routing tables to say that packets going to
> 192.168.0.10 (wlan0) should exit through the wlan1 netdevice, and vice
> versa:
>
>   dave:/home/dave# route add -host 192.168.0.11 dev wlan0
>   dave:/home/dave# route add -host 192.168.0.10 dev wlan1
>   dave:/home/dave# route -n
>   Kernel IP routing table
>   Destination  Gateway      Genmask         Flags Metric Ref  Use
Iface
>   192.168.0.10 0.0.0.0      255.255.255.255 UH    0      0      0
wlan1
>   192.168.0.11 0.0.0.0      255.255.255.255 UH    0      0      0
wlan0
>   10.1.1.0     0.0.0.0      255.255.255.0   U     0      0      0 eth0
>   0.0.0.0      10.1.1.254   0.0.0.0         UG    0      0      0 eth0
>
> Then I ping 192.168.0.10, which should get routed through the second
> netdevice wlan1, but the packet still goes through the loopback
> netdevice, instead of directly out the physical device.
>
>   dave:/home/dave#  ping -c 1 192.168.0.10
>   PING 192.168.0.10 (192.168.0.10): 56 data bytes
>   64 bytes from 192.168.0.10: icmp_seq=0 ttl=64 time=0.0 ms
>   --- 192.168.0.10 ping statistics ---
>   1 packets transmitted, 1 packets received, 0% packet loss
>   round-trip min/avg/max = 0.0/0.0/0.0 ms
>
> To verify, I check the Kernel Routing Cache, which indeed shows that
> pings to 192.68.0.10 will go through the loopback device.
>
>   dave:/home/dave# route -nC|grep -v 10
>   Kernel IP routing cache
>   Source        Destination   Gateway       Flags Metric Ref  Use
Iface
>   192.168.0.11  192.168.0.11  192.168.0.11  l     0      0      0 lo
>   192.168.0.11  192.168.0.11  192.168.0.11  l     0      0      0 lo
>   192.168.0.10  192.168.0.10  192.168.0.10  l     0      0      1 lo
>   192.168.0.10  192.168.0.10  192.168.0.10  l     0      0      1 lo
>
> I try again by modifying the routing tables to include a gateway for
> each device.  But I get the same result, and the same output from the
> kernel routing cache.
>
>   da:/home/dave# route add -host 192.168.0.11 gw 192.168.0.10 dev
wlan0
>   da:/home/dave# route add -host 192.168.0.10 gw 192.168.0.11 dev
wlan1
>   dave:/home/dave# route -n
>   Kernel IP routing table
>   Destination  Gateway      Genmask         Flags Metric Ref Use Iface
>   192.168.0.10 192.168.0.11 255.255.255.255 UGH   0      0     0 wlan1
>   192.168.0.11 192.168.0.10 255.255.255.255 UGH   0      0     0 wlan0
>   10.1.1.0     0.0.0.0      255.255.255.0   U     0      0     0 eth0
>   0.0.0.0      10.1.1.254   0.0.0.0         UG    0      0     0 eth0
>
> I am also aware of the "local" routing table accessible through the
> old linux-2.2 "iproute2" interface.
>
>   dave:/home/dave# ip route show table local|grep 192
>   broadcast 192.168.0.255 dev wlan0  proto kernel  scope link  src
> 192.168.0.10
>   broadcast 192.168.0.255 dev wlan1  proto kernel  scope link  src
> 192.168.0.11
>   local 192.168.0.11 dev wlan1  proto kernel  scope host  src
> 192.168.0.11
>   local 192.168.0.10 dev wlan0  proto kernel  scope host  src
> 192.168.0.10
>   broadcast 192.168.0.0 dev wlan0  proto kernel  scope link  src
> 192.168.0.10
>   broadcast 192.168.0.0 dev wlan1  proto kernel  scope link  src
> 192.168.0.11
>
> So I try to swap the sources also in this table for each device
>
>   dave:/home/dave# ip route change table local local 192.168.0.10 dev
> wlan1 \
> 		  proto kernel scope host src 192.168.0.11
>   dave:/home/dave# ip route change table local local 192.168.0.11 dev
> wlan0 \
> 		  proto kernel scope host src 192.168.0.10
>
> And this is what i get.
>
>   dave:/home/dave# ip route show table local|grep 192
>   broadcast 192.168.0.255 dev wlan0  proto kernel  scope link  src
> 192.168.0.10
>   broadcast 192.168.0.255 dev wlan1  proto kernel  scope link  src
> 192.168.0.11
>   local 192.168.0.11 dev wlan0  proto kernel  scope host  src
> 192.168.0.10
>   local 192.168.0.10 dev wlan1  proto kernel  scope host  src
> 192.168.0.11
>   broadcast 192.168.0.0 dev wlan0  proto kernel  scope link  src
> 192.168.0.10
>   broadcast 192.168.0.0 dev wlan1  proto kernel  scope link  src
> 192.168.0.11
>
> Again, when i try to ping it goes through the loopback device.  The
> routing cache verifies this again.
>
> It seems that linux is ignoring the routing table for local network
> devices, and forcing the route through the loopback device.  Is there
> any way to get around this?
>
> thanks,
> -dave
> dave at davidwang dot c*m
>
>
>
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From w.vanthoog  Thu Dec 19 17:09:12 2002
From: w.vanthoog (Wim van 't Hoog)
Date: Fri, 20 Dec 2002 02:09:12 +0100
Subject: error loading driver (buffer too small)
Message-ID: <002a01c2a7c4$6b8397d0$0201a8c0@vthoog.nl>

After succesfully compiling the hostap-cs driver and firing it up, the
following error occours:

wlan0 (WE) : Buffer for request 8B1B too small (0<23)
wlan0 (WE) : Buffer for request 8B1D too small (0<1)
wlan0 (WE) : Buffer for request 8D0B too small (0<308)

Any suggestions ?





From rpgoldman  Fri Dec 20 07:26:16 2002
From: rpgoldman (rpgoldman at real-time.com)
Date: Fri, 20 Dec 2002 09:26:16 -0600
Subject: problems with Linksys WMP11
In-Reply-To: <20021220055426.GB3024@jm.kir.nu>
References: <15874.36615.940741.574708@tsathoggua.mydomain>
	<200212200008.40020.jasonb@edseek.com>
	<20021220055426.GB3024@jm.kir.nu>
Message-ID: <15875.13976.589405.293017@tsathoggua.mydomain>

Jouni Malinen writes:
 > On Fri, Dec 20, 2002 at 12:08:40AM -0500, Jason Boxman wrote:
 > 
 > > The reported issues with 1.4.2 are indeed true.
 > 
 > Yes, but they should not cause problems when testing the card in
 > managed mode as was the case in the original question.

Then if that's not the problem, here's what I'm trying:

I start up the card in /etc/rc.local (if I can get it working, I can
move the initialization to a more appropriate place) trying the
following:

ifconfig eth0 down
modprobe hostap_pci
/sbin/iwconfig wlan0 essid sift-holmes 
/sbin/iwconfig wlan0 mode managed
/sbin/iwconfig wlan0 channel 6
/sbin/iwconfig wlan0 key  xxxxxxxxxx [1]
/sbin/iwconfig wlan0 key  xxxxxxxxxx [2]
/sbin/iwconfig wlan0 key  xxxxxxxxxx  [3]
/sbin/iwconfig wlan0 key  xxxxxxxxxx [4]
/sbin/iwconfig wlan ap any
/sbin/ifconfig wlan0 192.168.1.12 netmask 255.255.255.0 broadcast 192.168.1.255
/sbin/route add default gw 192.168.1.1

Here's what I see in dmesg:

ap_crypt: registered algorithm 'NULL'
hostap_pci: hostap_pci.c 0.0.0 2002-10-12 (SSH Communications Security Corp, Jouni Malinen)
hostap_pci: (c) Jouni Malinen <jkmaline at cc.hut.fi>
PCI: Found IRQ 10 for device 00:0b.0
hostap_pci: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_config: initialized in 18516 iterations
wlan0: trying to read PDA from 0x007f0000: OK
wlan0: hfa384x_get_rid - RID len mismatch: rid=0xfd0b, len=10 (expected 8)
Could not get RID for component NIC
wlan0: PRI: id=0x15 v1.1.0
wlan0: STA: id=0x1f v1.4.2
wlan0: defaulting to host-based encryption as a workaround for firmware bug in Host AP mode WEP
wlan0: Warning: secondary station firmware version 1.4.2 does not seem to work in Host AP mode
wlan0: hfa384x_cmd: entry still in list? (entry=d6ae1ae0, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=d6ae1ae0, type=0, cmd=0x0002, param0=0x0000)
wlan0: MAC port 0 reseting failed
hostap_pci: hardware initialization failed
hostap_pci: Netdevice wlan0 unregistered
hostap_pci: No devices found, driver not installed.
hostap_crypt: unregistered algorithm 'NULL' (deinit)
hostap_crypt: registered algorithm 'NULL'
hostap_pci: hostap_pci.c 0.0.0 2002-10-12 (SSH Communications Security Corp, Jouni Malinen)
hostap_pci: (c) Jouni Malinen <jkmaline at cc.hut.fi>
PCI: Found IRQ 10 for device 00:0b.0
hostap_pci: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_config: initialized in 18515 iterations
wlan0: trying to read PDA from 0x007f0000: OK
wlan0: hfa384x_get_rid - RID len mismatch: rid=0xfd0b, len=10 (expected 8)
Could not get RID for component NIC
wlan0: PRI: id=0x15 v1.1.0
wlan0: STA: id=0x1f v1.4.2
wlan0: defaulting to host-based encryption as a workaround for firmware bug in Host AP mode WEP
wlan0: Warning: secondary station firmware version 1.4.2 does not seem to work in Host AP mode
wlan0: hfa384x_get_rid - RID len mismatch: rid=0xfdc1, len=4 (expected 2)
wlan0: LinkStatus=2 (Disconnected)
wlan0: Intersil Prism2.5 PCI: mem=0xe3000000, irq=10
hostap_crypt: registered algorithm 'WEP'
wlan0: LinkStatus=2 (Disconnected)
wlan0: LinkStatus=2 (Disconnected)
wlan0: LinkStatus=2 (Disconnected)
wlan0: LinkStatus=2 (Disconnected)
wlan0: prism2_open
[And about a zillion copies of this:]
wlan0: Could not find STA for this TX error

I have been using a Mandrake 9.0 kernel.  I believed that it was
patched for the wireless extensions.  I could be wrong about that ---
would that explain the above kind of errors?

Anyway, the system just comes up in a totally bollixed-up state:

wlan0     IEEE 802.11-b  ESSID:"test"  
          Mode:Master  Frequency:2.422GHz  Access Point: 00:06:25:09:A8:4A
          Bit Rate:11Mb/s   Tx-Power:-17 dBm   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:xxxx-xxxx-xx   Encryption mode:restricted
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Seeming to have ignored all my iwconfig commands.  I reissue them from
the console, but still don't get good behavior.  Pings of the WAP
fail, leaving me with this statistical information:

wlan0     Link encap:Ethernet  HWaddr 00:06:25:09:A8:4A  
          inet addr:192.168.1.12  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:22 errors:0 dropped:0 overruns:0 frame:0
          TX packets:339 errors:339 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:4030 (3.9 Kb)  TX bytes:42702 (41.7 Kb)
          Interrupt:10 Memory:d907b000-d907c000 

Note that I seem to be RECEIVING fine, but all transmissions fail.
Reinvoking iwconfig gives me the following settings, which look ok to
me (but I'm dumb about this):

wlan0     IEEE 802.11-b  ESSID:"sift-holmes"  
          Mode:Managed  Frequency:2.437GHz  Access Point: 00:06:25:67:22:82
          Bit Rate:2Mb/s   Tx-Power:-15 dBm   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:xxxx-xxxx-xx   Encryption mode:restricted
          Power Management:off
          Link Quality:64/92  Signal level:-62 dBm  Noise level:-100 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Again, my profuse apologies if I'm just doing something obviously
stupid.  And my profound gratitude to anyone who can set me straight!

Best,
R



From jasonb  Fri Dec 20 07:48:19 2002
From: jasonb (Jason Boxman)
Date: Fri, 20 Dec 2002 10:48:19 -0500
Subject: problems with Linksys WMP11
In-Reply-To: <20021220055426.GB3024@jm.kir.nu>
References: <15874.36615.940741.574708@tsathoggua.mydomain> <200212200008.40020.jasonb@edseek.com> <20021220055426.GB3024@jm.kir.nu>
Message-ID: <200212201048.19397.jasonb@edseek.com>

On Friday 20 December 2002 12:54 am, Jouni Malinen wrote:
> On Fri, Dec 20, 2002 at 12:08:40AM -0500, Jason Boxman wrote:
> > The reported issues with 1.4.2 are indeed true.
>
> Yes, but they should not cause problems when testing the card in
> managed mode as was the case in the original question.

Yeah, that's what I figured. :)

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages





From Peter.DeCleyn  Fri Dec 20 07:49:12 2002
From: Peter.DeCleyn (Peter De Cleyn)
Date: Fri, 20 Dec 2002 16:49:12 +0100 (CET)
Subject: Forcing handover
Message-ID: <Pine.LNX.4.33L2.0212201646180.12153-100000@pcinf26.uia.ac.be>

Hi,

As a testcase, I would like to examine the hanoff procedure between access
points. I managed to configure 2 APs with HostAP and I'm now looking for a
way to force a handover between APs.

Can I use iwconfig wlan0 txpower on the APs and hope that the MN will
notice the drop in quality? I already tried iwpriv wlan0 maccmd 4, but
this replied " no private ioctls"

I'm using Linksys WPC11 card, with secondary firmware 1.4.9 in ram.

If anyone has experience with this manner, I would appreciate it if you
shared it.

Thanks in advance,

Peter


 _______________
/ Peter De Cleyn\
-------------------------------------------------------
| Phone:                +32 (0)3 820.24.18            |
| Fax:                  +32 (0)3 820.24.21            |
| email:                peter.decleyn at ua.ac.be        |
|                                                     |
| University of Antwerp (UIA)                         |
| Dept. Mathematics and Computer Science              |
| PATS Research Group                                 |
| Universiteitsplein 1                                |
| B-2610 Wilrijk                                      |
| Belgium                                             |
-------------------------------------------------------






From jasonb  Fri Dec 20 07:51:22 2002
From: jasonb (Jason Boxman)
Date: Fri, 20 Dec 2002 10:51:22 -0500
Subject: problems with Linksys WMP11
In-Reply-To: <15875.13976.589405.293017@tsathoggua.mydomain>
References: <15874.36615.940741.574708@tsathoggua.mydomain> <20021220055426.GB3024@jm.kir.nu> <15875.13976.589405.293017@tsathoggua.mydomain>
Message-ID: <200212201051.22449.jasonb@edseek.com>

On Friday 20 December 2002 10:26 am, rpgoldman at real-time.com wrote:
> Jouni Malinen writes:
>  > On Fri, Dec 20, 2002 at 12:08:40AM -0500, Jason Boxman wrote:
>  > > The reported issues with 1.4.2 are indeed true.
>  >
>  > Yes, but they should not cause problems when testing the card in
>  > managed mode as was the case in the original question.
>
> Then if that's not the problem, here's what I'm trying:
>
> I start up the card in /etc/rc.local (if I can get it working, I can
> move the initialization to a more appropriate place) trying the
> following:
>
<snip>
> Again, my profuse apologies if I'm just doing something obviously
> stupid.  And my profound gratitude to anyone who can set me straight!

Have you tired doing it with WEP disabled and Open access on the AP first?  

> Best,
> R

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages





From pedro.estrela  Fri Dec 20 08:20:38 2002
From: pedro.estrela (Pedro Estrela)
Date: Fri, 20 Dec 2002 16:20:38 -0000
Subject: Fw: Forcing handover
Message-ID: <004e01c2a843$bd416550$1fe016d5@pedropc>


> Hi,
>
> > As a testcase, I would like to examine the hanoff procedure between
access
> > points. I managed to configure 2 APs with HostAP and I'm now looking for
a
> > way to force a handover between APs.
> >
> > Can I use iwconfig wlan0 txpower on the APs and hope that the MN will
> > notice the drop in quality?
> Yes, This is the best way to emulate the actul movement of one station
> between the Access Points. Using a very simple script and rsh (remote
shell)
> i was able to test what happens in the handover, by performing it many,
many
> times, without actually moving around the terminal.
>
> Pedro Estrela
>
>





From rpgoldman  Fri Dec 20 11:34:13 2002
From: rpgoldman (rpgoldman at real-time.com)
Date: Fri, 20 Dec 2002 13:34:13 -0600
Subject: problems with Linksys WMP11
In-Reply-To: <200212201051.22449.jasonb@edseek.com>
References: <15874.36615.940741.574708@tsathoggua.mydomain>
	<20021220055426.GB3024@jm.kir.nu>
	<15875.13976.589405.293017@tsathoggua.mydomain>
	<200212201051.22449.jasonb@edseek.com>
Message-ID: <15875.28853.799853.611643@tsathoggua.mydomain>

Jason Boxman writes:
 > On Friday 20 December 2002 10:26 am, rpgoldman at real-time.com wrote:
 > > Jouni Malinen writes:
 > >  > On Fri, Dec 20, 2002 at 12:08:40AM -0500, Jason Boxman wrote:
 > >  > > The reported issues with 1.4.2 are indeed true.
 > >  >
 > >  > Yes, but they should not cause problems when testing the card in
 > >  > managed mode as was the case in the original question.
 > >
 > > Then if that's not the problem, here's what I'm trying:
 > >
 > > I start up the card in /etc/rc.local (if I can get it working, I can
 > > move the initialization to a more appropriate place) trying the
 > > following:
 > >
 > <snip>
 > > Again, my profuse apologies if I'm just doing something obviously
 > > stupid.  And my profound gratitude to anyone who can set me straight!
 > 
 > Have you tired doing it with WEP disabled and Open access on the AP first?  


I'll look into that, but I don't think it can be ALL the problem,
since the card comes up in a wacko state.  I.e., if you look at my
first iwconfig outputs, which I captured right after boot-up, it's
clear that something's going wrong and the card is not accepting the
initial iwconfig commands in the /etc/rc.local file.  


Thanks,
Robert



From ammirata  Fri Dec 20 15:12:35 2002
From: ammirata (Sergio M. Ammirata)
Date: Fri, 20 Dec 2002 18:12:35 -0500
Subject: hostap_plx
Message-ID: <000501c2a87d$4957bba0$160aa8c0@ammirata.net>

Hi,

 

I patched my 2.4.19 with the hostap-2002-10-12 driver.

Everything compiles fine as long as I don't select to have support for
both the hostap_plx and hostap_pci.

Are these mutually exclusive? The kernel compilation gives and error if
they are both selected.

 

Thanks in advance,

 

Sergio

P.S. The hostap_cs can coexist with either one of them.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021220/56051e9a/attachment.htm 


From pdcleyn  Fri Dec 20 07:26:28 2002
From: pdcleyn (peter.decleyn)
Date: Fri, 20 Dec 2002 16:26:28 +0100 (CET)
Subject: Forcing handover
Message-ID: <Pine.LNX.4.33L2.0212201622430.11454-100000@pcinf26.uia.ac.be>

Hi,

As a testcase, I would like to examine the hanoff procedure between access
points. I managed to configure 2 APs with HostAP and I'm now looking for a
way to force a handover between APs.

Can I use iwconfig wlan0 txpower on the APs and hope that the MN will
notice the drop in quality?

If anyone has experience with this manner, I would appreciate it if you
shared it.

Thanks in advance,

Peter


 _______________
/ Peter De Cleyn\
-------------------------------------------------------
| Phone:                +32 (0)3 820.24.18            |
| Fax:                  +32 (0)3 820.24.21            |
| email:                peter.decleyn at ua.ac.be        |
|                                                     |
| University of Antwerp (UIA)                         |
| Dept. Mathematics and Computer Science              |
| PATS Research Group                                 |
| Universiteitsplein 1                                |
| B-2610 Wilrijk                                      |
| Belgium                                             |
-------------------------------------------------------





From jasonb  Fri Dec 20 18:26:16 2002
From: jasonb (Jason Boxman)
Date: Fri, 20 Dec 2002 21:26:16 -0500
Subject: Forcing handover
In-Reply-To: <Pine.LNX.4.33L2.0212201622430.11454-100000@pcinf26.uia.ac.be>
References: <Pine.LNX.4.33L2.0212201622430.11454-100000@pcinf26.uia.ac.be>
Message-ID: <200212202126.16139.jasonb@edseek.com>

On Friday 20 December 2002 10:26 am, peter.decleyn wrote:
> Hi,
>
> As a testcase, I would like to examine the hanoff procedure between access
> points. I managed to configure 2 APs with HostAP and I'm now looking for a
> way to force a handover between APs.

I know you can ban a station's mac address, then kick it off so it can't 
reassociate with that particular AP for the duration of the ban.

You migh search the archives, too, as I think this has been discussed before.

<snip>
> Thanks in advance,
>
> Peter
>
-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages





From jkmaline  Fri Dec 20 19:15:43 2002
From: jkmaline (Jouni Malinen)
Date: Fri, 20 Dec 2002 19:15:43 -0800
Subject: Forcing handover
In-Reply-To: <Pine.LNX.4.33L2.0212201622430.11454-100000@pcinf26.uia.ac.be>
References: <Pine.LNX.4.33L2.0212201622430.11454-100000@pcinf26.uia.ac.be>
Message-ID: <20021221031543.GA1015@jm.kir.nu>

On Fri, Dec 20, 2002 at 04:26:28PM +0100, peter.decleyn wrote:

> As a testcase, I would like to examine the hanoff procedure between access
> points. I managed to configure 2 APs with HostAP and I'm now looking for a
> way to force a handover between APs.
> 
> Can I use iwconfig wlan0 txpower on the APs and hope that the MN will
> notice the drop in quality?

Depending on what you want to test, you can either ask station to
associate with another AP or make one of the APs "invisible" for the
station. I have been using 'iwconfig wlan0 txpower off' quite a lot to
test reassociation. AP will no be able to send any frames after that and
the station should soon report AP out of range and start looking for a
new one.

-- 
Jouni Malinen                                            PGP id EFC895FA



From raghu  Fri Dec 20 19:39:31 2002
From: raghu (raghu at sraamerica.com)
Date: Fri, 20 Dec 2002 22:39:31 -0500
Subject: 802.1X Unicast Keys?
Message-ID: <20021221033931.XTWP5165.imta02a2.registeredsite.com@smtp.registeredsite.com>

Hi,   
   
My Setup is XSupplicant, HostAP(client), HostAP(AP),   
Hostapd (Authenticator), FreeRADIUS.   
I modified Xsupplicant code to work with EAPOL key frames.   
   
Hostapd -b13 option is working as expected. ie EAPOL key   
frame   
is properly sent from hostapd to xsupplicant after EAP/TLS   
authentication is successful.   
   
$ ./hostapd -x -b13 -o192.168.1.1 -a192.168.1.1 -stest   
-SSSID wlan0   
......   
IEEE 802.1X: 00:04:5a:0d:f4:68 BE_AUTH entering state   
SUCCESS   
IEEE 802.1X: 00:04:5a:0d:f4:68 REAUTH_TIMER entering state   
INITIALIZE   
IEEE 802.1X: 00:04:5a:0d:f4:68 AUTH_PAE entering state   
AUTHENTICATED   
IEEE 802.1X: Authorizing station 00:04:5a:0d:f4:68   
IEEE 802.1X: 00:04:5a:0d:f4:68 BE_AUTH entering state IDLE   
DEBUG: STATE_MACHINE KEY TRANSMIT   
IEEE 802.1X: 00:04:5a:0d:f4:68 AUTH_KEY_TX entering state   
KEY_TRANSMIT   
IEEE 802.1X: Sending EAPOL-Key(s) to 00:04:5a:0d:f4:68   
(identifier 6)   
Station 00:04:5a:0d:f4:68 authenticated (open system)   
Station 00:04:5a:0d:f4:68 associated (aid 1)   
   
   
But with -i13 option, I didnot find EAPOL AUTH_KEY_TX   
state machine   
getting triggered after EAP/TLS authentication is   
successful.   
   
$ ./hostapd -x -i13 -o192.168.1.1 -a192.168.1.1 -stest   
-SSSID wlan0   
......   
IEEE 802.1X: 00:04:5a:0d:f4:68 BE_AUTH entering state   
SUCCESS   
IEEE 802.1X: 00:04:5a:0d:f4:68 REAUTH_TIMER entering state   
INITIALIZE   
IEEE 802.1X: 00:04:5a:0d:f4:68 AUTH_PAE entering state   
AUTHENTICATED   
IEEE 802.1X: Authorizing station 00:04:5a:0d:f4:68   
IEEE 802.1X: 00:04:5a:0d:f4:68 BE_AUTH entering state IDLE   
   
   
Can someone please let me know, how hosapd unicast keys   
are supposed to work ? 
   
regards,   
-Raghu   
   




From jkmaline  Fri Dec 20 23:06:09 2002
From: jkmaline (Jouni Malinen)
Date: Fri, 20 Dec 2002 23:06:09 -0800
Subject: 802.1X Unicast Keys?
In-Reply-To: <20021221033931.XTWP5165.imta02a2.registeredsite.com@smtp.registeredsite.com>
References: <20021221033931.XTWP5165.imta02a2.registeredsite.com@smtp.registeredsite.com>
Message-ID: <20021221070609.GA2312@jm.kir.nu>

On Fri, Dec 20, 2002 at 10:39:31PM -0500, raghu at sraamerica.com wrote:

> But with -i13 option, I didnot find EAPOL AUTH_KEY_TX   
> state machine   
> getting triggered after EAP/TLS authentication is   
> successful.   
>    
> $ ./hostapd -x -i13 -o192.168.1.1 -a192.168.1.1 -stest   
> -SSSID wlan0   

I have never tested unicast keys without setting broadcast keys with
.1x. Are you setting broadcast keys manually for both the stations and
AP? I would suggest trying with both -i13 and -b13 on the same command
line to get both keys set automatically. Please let me know, if there is
a valid setup in which one would want to use only unicast keys with .1x
and I'll take a closer look at the implementation.

-- 
Jouni Malinen                                            PGP id EFC895FA



From yamaken  Sat Dec 21 06:57:11 2002
From: yamaken (yamada kenta)
Date: Sat, 21 Dec 2002 23:57:11 +0900
Subject: Simple questions (RID, fragmentation, handover)
Message-ID: <3E048147191.3AA5YAMAKEN@inl2.elcom.nitech.ac.jp>

Hi all,

I am new to HostAP. 
I have three questions as follows.

1. 
What's RID ? I think it Resource IDentifier. 
And if RID is Resource IDentifier what's this?
 
2. 
When Packet size is larger than 802.11x frame size , packet is
fragmented. Is this fragmentation processed by firmware or HostAP driver ?

3. 
How to select APs when handover happend ? 
and Is this event processed by firmware or HostAP driver ?

Can anybody please answer these questions ?
Thanks in advance,

Yamada Kenta




From jkmaline  Sat Dec 21 18:45:23 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 21 Dec 2002 18:45:23 -0800
Subject: Simple questions (RID, fragmentation, handover)
In-Reply-To: <3E048147191.3AA5YAMAKEN@inl2.elcom.nitech.ac.jp>
References: <3E048147191.3AA5YAMAKEN@inl2.elcom.nitech.ac.jp>
Message-ID: <20021222024523.GA3756@jm.kir.nu>

On Sat, Dec 21, 2002 at 11:57:11PM +0900, yamada kenta wrote:

> What's RID ? I think it Resource IDentifier. 
> And if RID is Resource IDentifier what's this?

Yes, it is resource identifier and it is a data element that is used to
configure Prism2 card and to read configuration related information from
the card.

> When Packet size is larger than 802.11x frame size , packet is
> fragmented. Is this fragmentation processed by firmware or HostAP driver ?

There is no 802.11x, but I'm assuming you are talking about 802.11
fragmentation. First of all, this framentation is mainly used to make
sent frames smaller to reduce probability of errors, so it does not
generally increase the packet size. Anyway, 802.11 fragmentation and
reassembly is performed by firmware, except when host-based WEP
decryption is used. Since 802.11 encrypts each fragment separately, Host
AP driver takes care of reassembly when host_decrypt is configured.

> How to select APs when handover happend ? 
> and Is this event processed by firmware or HostAP driver ?

That is implementation specific issue. Usually station selects the best
available AP when the signal quality of the current AP drops below some
threshold value. In default Managed mode, firmware takes care of this.
However, Host AP driver has support for host-based roaming (prism2_param
wlan0 host_roaming 1), in which Host AP driver does this AP selection
(although, current implementation depends on firmware doing the scanning
and noticing when signal quality drops).

-- 
Jouni Malinen                                            PGP id EFC895FA



From dean-list-hostap  Sat Dec 21 19:28:02 2002
From: dean-list-hostap (dean gaudet)
Date: Sat, 21 Dec 2002 19:28:02 -0800 (PST)
Subject: problems with EN2511CD / NL2511CD
In-Reply-To: <Pine.LNX.4.50.0212031935320.11195-100000@twinlark.arctic.org>
References: <Pine.LNX.4.50.0212022152090.11195-100000@twinlark.arctic.org>
 <20021203062656.GA12480@jm.kir.nu> <Pine.LNX.4.50.0212022251260.11195-100000@twinlark.arctic.org>
 <20021204032243.GA1232@jm.kir.nu> <Pine.LNX.4.50.0212031935320.11195-100000@twinlark.arctic.org>
Message-ID: <Pine.LNX.4.50.0212211922110.12862-101000@twinlark.arctic.org>

hi -- a couple weeks ago i was asking for assistance with an NL2511CD...
my schedule finally permitted me to collect the sniffing dumps which jouni
malinen asked me for.

the attached file was collected by "tethereal -s 1600"... i hope it helps!

i've included some more context below.

thanks
-dean

On Mon, 2 Dec 2002, dean gaudet wrote:

> i recently purchased an NL2511CD aka EN2511CD from netgate.com and i'm
> having troubles getting it to work with the latest hostap-2002-10-12 code.
>
> i've already had this laptop working as an AP with a linksys WPC11 prism2
> card, so i think i've got the basics covered.  i can also get the NL2511CD
> to work in a win2k laptop as a client, so i think the hardware works.
>
> the NL2511CD has these firmware revs:  (i've tried a bunch of others i
> found on the net)
>
> Dec  2 20:57:13 mewlark kernel: wlan0: NIC: id=0x800c v1.0.0
> Dec  2 20:57:13 mewlark kernel: wlan0: PRI: id=0x15 v1.1.0
> Dec  2 20:57:13 mewlark kernel: wlan0: STA: id=0x1f v1.4.9
>
> hostap doesn't complain about anything... but i can't associate with it.
> here's some attempts by my cisco350 to associate:
>
> Dec  2 20:57:23 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0 trans#=1 stat=0 len=6fc=00b0) ==> 0 (authenticated)
> Dec  2 20:57:23 mewlark kernel: wlan0: 00:40:96:5a:5d:ce reassoc (len=32 prev_ap=00:03:2f:02:97:46) => 0(0) (OK, new AID)
>
> those go on for a while, but the cisco never manages to associate.
> (i tried a WPC11 as well, no luck either.)


On Tue, 3 Dec 2002, dean gaudet wrote:

> On Tue, 3 Dec 2002, Jouni Malinen wrote:
>
> > On Mon, Dec 02, 2002 at 10:59:24PM -0800, dean gaudet wrote:
> >
> > > Dec  2 22:46:51 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth (alg=0 trans#=1 stat=0 len=6 fc=00b0) ==> 0 (authOK)
> > > Dec  2 22:46:51 mewlark kernel: wlan0: 00:40:96:5a:5d:ce auth_cb - frame was not ACKed
> >
> > OK, that's the problem.. The station is not acknowledging authentication
> > frame from the AP (or at least the AP does not receive this ACK). Most
> > common reason for this is the delay between authentication frames being
> > too long. Some station firmware implementation seem to be quite strict
> > on this. Do you happen to have lot of wireless traffic on the same
> > channel? Is the AP host heavily loaded or is it writing kernel messages
> > to frame buffer or serial console?
>
> the problem happens with both a cisco 350 and a linksys WPC11 on the
> client side.
>
> there's no other wireless traffic on this channel (it's in my house and
> none of my neighbours are using wireless) ... there could be other types
> of 2.4GHz interference, but i've been testing with the client and AP
> within 1m of each other.
>
> no load on the AP host.
>
> > The best method for researching the problem would be to use a third host
> > as a wireless sniffer and record the frame exchange between the station
> > and the AP. I would like to be sure that the authentication reply from
> > the AP is really going out and that the station is not sending an ACK
> > for it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: apdump1600
Type: application/octet-stream
Size: 12513 bytes
Desc: 
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20021221/16907e9d/attachment.obj 


From jkmaline  Sat Dec 21 21:04:32 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 21 Dec 2002 21:04:32 -0800
Subject: hostap_plx
In-Reply-To: <000501c2a87d$4957bba0$160aa8c0@ammirata.net>
References: <000501c2a87d$4957bba0$160aa8c0@ammirata.net>
Message-ID: <20021222050432.GA4874@jm.kir.nu>

On Fri, Dec 20, 2002 at 06:12:35PM -0500, Sergio M. Ammirata wrote:

> I patched my 2.4.19 with the hostap-2002-10-12 driver.
> 
> Everything compiles fine as long as I don't select to have support for
> both the hostap_plx and hostap_pci.
> 
> Are these mutually exclusive? The kernel compilation gives and error if
> they are both selected.

They shouldn't be.. I just made a new patch for 2.4.20 kernel and tested
compiling both hostap_plx and hostap_pci into kernel image. I did not
notice any errors in this. Please test with the latest CVS version and
if it fails to compile, send me the error messages shown during
compilation. It is possible that I have fixed something after 2002-10-12
release for this.

-- 
Jouni Malinen                                            PGP id EFC895FA



From raghu  Sun Dec 22 00:23:55 2002
From: raghu (raghu at sraamerica.com)
Date: Sun, 22 Dec 2002 3:23:55 -0500
Subject: 802.1X Unicast Keys?
Message-ID: <20021222082355.BNCB17506.imta01a2.registeredsite.com@smtp.registeredsite.com>

> I have never tested unicast keys without setting broadcast keys with
> .1x. Are you setting broadcast keys manually for both the stations and
> AP? I would suggest trying with both -i13 and -b13 on the same command
> line to get both keys set automatically. Please let me know, if there is

I was not trying any manual broadcast key settings, Since
I was under the impression that using 1X, we can set either
broadcast keys(-b) or Unicast keys(-i) or both(-b & -i).
So I started with -b13 option, but since -i13 option
failed, I didnot proceed further to try -b13 & -i13 on the
same command. Thankyou very much for your suggestion, 
I will try this now.


> a valid setup in which one would want to use only unicast keys with .1x
> and I'll take a closer look at the implementation.

In Mobile IP scenario, Setting Broadcast key to the roaming
STA in the foreign n/w doesnot add any value, IMHO.

A small favor, Please CC me as I am only subscribed to the digest.

-Raghu




From ammirata  Sun Dec 22 06:28:42 2002
From: ammirata (Sergio M. Ammirata)
Date: Sun, 22 Dec 2002 09:28:42 -0500
Subject: hostap_plx
In-Reply-To: <20021222050432.GA4874@jm.kir.nu>
Message-ID: <000001c2a9c6$6e6b9c00$017ba8c0@ammirata.net>

The latest CVS version does indeed compile without any problems.

Thanks,

Sergio

> -----Original Message-----
> From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] On Behalf
Of
> Jouni Malinen
> Sent: Sunday, December 22, 2002 12:05 AM
> To: hostap at shmoo.com
> Subject: Re: hostap_plx
> 
> On Fri, Dec 20, 2002 at 06:12:35PM -0500, Sergio M. Ammirata wrote:
> 
> > I patched my 2.4.19 with the hostap-2002-10-12 driver.
> >
> > Everything compiles fine as long as I don't select to have support
for
> > both the hostap_plx and hostap_pci.
> >
> > Are these mutually exclusive? The kernel compilation gives and error
if
> > they are both selected.
> 
> They shouldn't be.. I just made a new patch for 2.4.20 kernel and
tested
> compiling both hostap_plx and hostap_pci into kernel image. I did not
> notice any errors in this. Please test with the latest CVS version and
> if it fails to compile, send me the error messages shown during
> compilation. It is possible that I have fixed something after
2002-10-12
> release for this.
> 
> --
> Jouni Malinen                                            PGP id
EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap





From jar  Sun Dec 22 11:23:51 2002
From: jar (jar)
Date: Sun, 22 Dec 2002 21:23:51 +0200
Subject: Proper FW-1.4.9 for WL200
Message-ID: <3E061147.C211AC2A@pcuf.fi>

Hi

I am planning to udpate my Compaq WL200 firmware(flash)
to version 1.4.9. I has found two suitable *.hex files from
the hostap list. So.. which one I should use?

1) S1010409.HEX posted by Alejandro Lamas
2) Sf010409.hex psoted by Pedro Estrela

By the way, what is the difference between those files ?

Regards, Jar



From ebike  Sun Dec 22 15:28:06 2002
From: ebike (Bernard Mentink)
Date: Mon, 23 Dec 2002 12:28:06 +1300
Subject: Can not get Hostap into monitor mode under Gentoo
Message-ID: <3E064A86.9010306@paradise.net.nz>

Hi all,

I have changed my Linux system over to Gentoo (from Yellowdog) and the 
last issue to iron out is my WLan card.

I am using a d-link DWL-650 card with the hostap driver, this worked 
very well when I was running Yellowdog.

Normal operation is fine, but I get the following error when trying to 
put the device in monitor mode:

 iwconfig wlan0 mode monitor
Error for wireless request "Set Mode" (8B06) :
    invalid argument "monitor".

The out put from iwpriv is:

 iwpriv wlan0
wlan0     Available private ioctl :
          monitor (8BE4) : set   1 int  & get   0
          readmif (8BE3) : set   1 byte & get   1 byte
          writemif (8BE2) : set   2 byte & get   0
          reset (8BE6) : set   1 int  & get   0
          inquire (8BE8) : set   1 int  & get   0
          set_rid_word (8BEE) : set   2 int  & get   0
          maccmd (8BF0) : set   1 int  & get   0
          wds_add (8BEA) : set  18 char & get   0
          wds_del (8BEC) : set  18 char & get   0
          addmac (8BF2) : set  18 char & get   0
          delmac (8BF4) : set  18 char & get   0
          kickmac (8BF6) : set  18 char & get   0
          prism2_param (8BE0) : set   2 int  & get   0
          getprism2_param (8BE1) : set   1 int  & get   1 int

It seems I am using version 13 of the wireless extensions and version 12 
of the tools, as per:

iwconfig
Warning : Device wlan0 has been compiled with version 13
of Wireless Extension, while we are using version 12.
Some things may be broken...

I don't think this is the issue though, I was getting the same warning 
under Yellowdog and it worked fine.

On observation from the above though, the monitor ioctl expected by the 
tools is (8B06) and by the device (8BE4),
It seems there is a mis-match there.

My wireless tools (from gentoo) is version 24, I seem to remember using 
version 25 under YDL.

Can some-one tell me what I should upgrade .... thanks.

Cheers,
Bernie.






From jkmaline  Sun Dec 22 17:55:21 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 22 Dec 2002 17:55:21 -0800
Subject: Can not get Hostap into monitor mode under Gentoo
In-Reply-To: <3E064A86.9010306@paradise.net.nz>
References: <3E064A86.9010306@paradise.net.nz>
Message-ID: <20021223015521.GC1233@jm.kir.nu>

On Mon, Dec 23, 2002 at 12:28:06PM +1300, Bernard Mentink wrote:

> iwconfig wlan0 mode monitor
> Error for wireless request "Set Mode" (8B06) :
>    invalid argument "monitor".

Too old version of wireless tools..

> On observation from the above though, the monitor ioctl expected by the 
> tools is (8B06) and by the device (8BE4),
> It seems there is a mis-match there.

That is a different ioctl. 8B06 is "set mode", 8be4 is private ioctl.

> My wireless tools (from gentoo) is version 24, I seem to remember using 
> version 25 under YDL.

Yes, this is the problem here. Just do 'emerge rsync; emerge -u
wireless-tools'.. Current Gentoo portage seems to include version 25.

-- 
Jouni Malinen                                            PGP id EFC895FA



From pedro.estrela  Sun Dec 22 19:09:24 2002
From: pedro.estrela (Pedro Estrela)
Date: Mon, 23 Dec 2002 03:09:24 -0000
Subject: Proper FW-1.4.9 for WL200
References: <3E061147.C211AC2A@pcuf.fi>
Message-ID: <004901c2aa30$b364e040$0ae216d5@pedropc>

i don't remember the diference, but you can use the one that i've posted
without fear for WL200.

Regards,
Pedro Estrela

> Hi
>
> I am planning to udpate my Compaq WL200 firmware(flash)
> to version 1.4.9. I has found two suitable *.hex files from
> the hostap list. So.. which one I should use?
>
> 1) S1010409.HEX posted by Alejandro Lamas
> 2) Sf010409.hex psoted by Pedro Estrela
>
> By the way, what is the difference between those files ?
>
> Regards, Jar
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>





From jeffery  Sun Dec 22 20:33:23 2002
From: jeffery (Jeffery Huang)
Date: Mon, 23 Dec 2002 12:33:23 +0800
Subject: Corega PCCL-11 
Message-ID: <3E069213.10501@imining.com.tw>

Dear all,
  I tried to use corega PCCL-11 in AP mode. But it seems cannot startup.
How do I startup it in AP mode.
  I have upgrade firmware to 1.4.9
  my os enviroment is RH 8.0 - with kernel 2.4.18-19.8.0
  pcmcia-cs-3.2.3
  linux-wlan-0.1.15

Please give me a hand to resolve it!
-- 
Regard,
Jeffery Huang
iMining Technology Co.,Ltd.
886-2-2723-5122-11
886-2-27232287
http://www.imining.com.tw
email://jeffery at imining.com.tw




From cupid90  Mon Dec 23 02:34:17 2002
From: cupid90 (cupid90 at samsung.co.kr)
Date: Mon, 23 Dec 2002 19:34:17 +0900
Subject: [Question] About Host AP
Message-ID: <H000050a140d6ee1.1040638109.kgomap0@MHS>

Dear. host ap administrators,

I am testing HOSTAP solution in my PC.
I want to use my PC with access point.

I got the package and compiled and loading HOSTAP driver with hostapd(hostap daemon).
and It was succeeded scanning AP(access point) in my the other PC(PCI client wireless card).

The following information is my test environments.
Both samsung wireless cards are using the intersil chipset.

PC-1(linux)    < -------------------------------------- >    PC-2(windows)
Samsung MagicLan pcmci type Wireless card             Samsung MagicLan PCI type Wireless card
used HostAP driver and hostapd				mode:infrastructure
mode: Master(configured with iwconfig)

<test result>

Association was succeeded. but after authentication suceeded. hostapd report "IEEE 802.1X: Unauthorizing station xx:xx..."
I don't know the reason. I changed various variables with iwpriv and prism2_param tools. but I failed.
and then I found some errors in directory /proc/net/hostap/wlan0/stats. the errors was occurred in item "RxFCSErrors=9650".

If show the configuratioin of "ifconfig"

lo Link encap: Local loopback...
   inet addr: 127.0.0.1
   ...............

wlan0 Link encap: Ethernet Hwaddr: .....
   inet addr: 12.25.167.41
   ...............

wlan0ap Link encap:UNSPEC Hwaddr:......
   UP BROADCAST.....
   ...............

and iwconfig

wlan0 IEEE 802.11-b ESSID:"test" ....
      Mode:Master Freq: ...........
      .............................

I am testing on WEP "off" in both side of PC.
Can you advise for me?
I am searching and reading many documents.

If ping is good, I am supposed to stack the bridge protocol or route protocol.








             

????????????????????????????????????????????????

_?_____
/______/~? .?.        ???
?????? ``     
 ----------             
Happy day~?          Roh You-Chang

      Application S/W Engineer
      System Solution Group
      Access Network SOC Team
      System LSI Business
      Device Solution Network
      SAMSUNG ELECTRONICS CO., LTD.

      phone:82-31-209-8314,  fax:82-31-209-8309
      e-mail:cupid90 at samsung.co.kr

????????????????????????????????????????????????

WARNING: 

 This e-mail contains confidential and/or privileged information for the
 sole use by the specified recipient(s).  Any unauthorized review distribution, 
 disclosure or other use of the information in this message and the attched
 file hereto is strictly prohibited.  If you are not the specified recipient, please 
 contact the sender (terius90 at samsung.com or cupid90 at samsung.co.kr)
 and delete the original message and all copies thereof.  

 Thanks!

????????????????????????????????????????????????




From cupid90  Mon Dec 23 03:22:21 2002
From: cupid90 (cupid90 at samsung.co.kr)
Date: Mon, 23 Dec 2002 20:22:21 +0900
Subject: Unautorizing station  problem
Message-ID: <H000050a140d6ee9.1040642503.kgomap0@MHS>

Dear. host ap administrators,

I am testing HOSTAP solution in my linux PC.
I want to use my PC with access point.

I got the package and compiled and loading HOSTAP driver with hostapd(hostap daemon).
and It was succeeded scanning AP(access point) in my the other PC(PCI client wireless card).

The following information is my test environments.
Both samsung wireless cards are using the intersil chipset.

PC-1(linux)    < -------------------------------------- >    PC-2(windows)
Samsung MagicLan pcmcia type Wireless card             Samsung MagicLan PCI type Wireless card
used HostAP driver and hostapd				mode:infrastructure
mode: Master(configured with iwconfig)

<test result>

Association was succeeded. but after authentication suceeded. hostapd report "IEEE 802.1X: Unauthorizing station xx:xx..."
I don't know the reason. I changed various variables with iwpriv and prism2_param tools. but I failed.
and then I found some errors in directory /proc/net/hostap/wlan0/stats. the errors was occurred in item "RxFCSErrors=9650".

If show the configuration of "ifconfig"

lo Link encap: Local loopback...
   inet addr: 127.0.0.1
   ...............

wlan0 Link encap: Ethernet Hwaddr: .....
   inet addr: xx.xx.xx.xx
   ...............

wlan0ap Link encap:UNSPEC Hwaddr:......  => WHY "Link encap" is "UNSPEC". let me know the reason.
   UP BROADCAST.....
   ...............

and iwconfig

wlan0 IEEE 802.11-b ESSID:"test" ....
      Mode:Master Freq: ...........
      .............................

I am testing on WEP "off" in both side of PC.
Can you advise for me?
I am searching and reading many documents.

If ping is good, I am supposed to stack the bridge protocol or route protocol.


             

????????????????????????????????????????????????

_?_____
/______/~? .?.        ???
?????? ``     
 ----------             
Happy day~?          Roh You-Chang

      Application S/W Engineer
      System Solution Group
      Access Network SOC Team
      System LSI Business
      Device Solution Network
      SAMSUNG ELECTRONICS CO., LTD.

      phone:82-31-209-8314,  fax:82-31-209-8309
      e-mail:cupid90 at samsung.co.kr

????????????????????????????????????????????????

WARNING: 

 This e-mail contains confidential and/or privileged information for the
 sole use by the specified recipient(s).  Any unauthorized review distribution, 
 disclosure or other use of the information in this message and the attched
 file hereto is strictly prohibited.  If you are not the specified recipient, please 
 contact the sender (terius90 at samsung.com or cupid90 at samsung.co.kr)
 and delete the original message and all copies thereof.  

 Thanks!

????????????????????????????????????????????????




From cupid90  Mon Dec 23 03:39:13 2002
From: cupid90 (cupid90 at samsung.co.kr)
Date: Mon, 23 Dec 2002 20:39:13 +0900
Subject: (help) Unautorizing station  problem
Message-ID: <H000050a140d6eef.1040643526.kgomap0@MHS>


I am testing HOSTAP solution in my linux PC.
I want to use my PC with access point.

I got the package and compiled and loading HOSTAP driver with hostapd(hostap daemon).
and It was succeeded scanning AP(access point) in my the other PC(PCI client wireless card).

The following information is my test environments.
Both samsung wireless cards are using the intersil chipset.

PC-1(linux)    < -------------------------------------- >    PC-2(windows)
Samsung MagicLan pcmcia type Wireless card             Samsung MagicLan PCI type Wireless card
used HostAP driver and hostapd				mode:infrastructure
mode: Master(configured with iwconfig)

<test result>

Association was succeeded. but after authentication suceeded. hostapd report "IEEE 802.1X: Unauthorizing station xx:xx..."
I don't know the reason. I changed various variables with iwpriv and prism2_param tools. but I failed.
and then I found some errors in directory /proc/net/hostap/wlan0/stats. the errors was occurred in item "RxFCSErrors=9650".

If show the configuration of "ifconfig"

lo Link encap: Local loopback...
   inet addr: 127.0.0.1
   ...............

wlan0 Link encap: Ethernet Hwaddr: .....
   inet addr: xx.xx.xx.xx
   ...............

wlan0ap Link encap:UNSPEC Hwaddr:......  => WHY "Link encap" is "UNSPEC". let me know the reason.
   UP BROADCAST.....
   ...............

and iwconfig

wlan0 IEEE 802.11-b ESSID:"test" ....
      Mode:Master Freq: ...........
      .............................

I am testing on WEP "off" in both side of PC.
Can you advise for me?
I am searching and reading many documents.

If ping is good, I am supposed to stack the bridge protocol or route protocol.


             

????????????????????????????????????????????????

_?_____
/______/~? .?.        ???
?????? ``     
 ----------             
Happy day~?          Roh You-Chang

      Application S/W Engineer
      System Solution Group
      Access Network SOC Team
      System LSI Business
      Device Solution Network
      SAMSUNG ELECTRONICS CO., LTD.

      phone:82-31-209-8314,  fax:82-31-209-8309
      e-mail:cupid90 at samsung.co.kr

????????????????????????????????????????????????

WARNING: 

 This e-mail contains confidential and/or privileged information for the
 sole use by the specified recipient(s).  Any unauthorized review distribution, 
 disclosure or other use of the information in this message and the attched
 file hereto is strictly prohibited.  If you are not the specified recipient, please 
 contact the sender (terius90 at samsung.com or cupid90 at samsung.co.kr)
 and delete the original message and all copies thereof.  

 Thanks!

????????????????????????????????????????????????
             


      Roh you-chang

      Application S/W Engineer
      System Solution Group
      Access Network SOC Team
      System LSI Business
      Device Solution Network
      SAMSUNG ELECTRONICS CO., LTD.

      phone:82-31-209-8314,  fax:82-31-209-8309
      e-mail:cupid90 at samsung.co.kr





From cupid90  Mon Dec 23 03:40:57 2002
From: cupid90 (cupid90 at samsung.co.kr)
Date: Mon, 23 Dec 2002 20:40:57 +0900
Subject: (help) Unautorizing station  problem
Message-ID: <H000050a140dd62d.1040643643.kgomap0@MHS>


I am testing HOSTAP solution in my linux PC.
I want to use my PC with access point.

I got the package and compiled and loading HOSTAP driver with hostapd(hostap daemon).
and It was succeeded scanning AP(access point) in my the other PC(PCI client wireless card).

The following information is my test environments.
Both samsung wireless cards are using the intersil chipset.

PC-1(linux)    < -------------------------------------- >    PC-2(windows)
Samsung MagicLan pcmcia type Wireless card             Samsung MagicLan PCI type Wireless card
used HostAP driver and hostapd				mode:infrastructure
mode: Master(configured with iwconfig)

<test result>

Association was succeeded. but after authentication suceeded. hostapd report "IEEE 802.1X: Unauthorizing station xx:xx..."
I don't know the reason. I changed various variables with iwpriv and prism2_param tools. but I failed.
and then I found some errors in directory /proc/net/hostap/wlan0/stats. the errors was occurred in item "RxFCSErrors=9650".

If show the configuration of "ifconfig"

lo Link encap: Local loopback...
   inet addr: 127.0.0.1
   ...............

wlan0 Link encap: Ethernet Hwaddr: .....
   inet addr: xx.xx.xx.xx
   ...............

wlan0ap Link encap:UNSPEC Hwaddr:......  => WHY "Link encap" is "UNSPEC". let me know the reason.
   UP BROADCAST.....
   ...............

and iwconfig

wlan0 IEEE 802.11-b ESSID:"test" ....
      Mode:Master Freq: ...........
      .............................

I am testing on WEP "off" in both side of PC.
Can you advise for me?
I am searching and reading many documents.

If ping is good, I am supposed to stack the bridge protocol or route protocol.

             


      Roh you-chang

      Application S/W Engineer
      System Solution Group
      Access Network SOC Team
      System LSI Business
      Device Solution Network
      SAMSUNG ELECTRONICS CO., LTD.

      phone:82-31-209-8314,  fax:82-31-209-8309
      e-mail:cupid90 at samsung.co.kr





From hazard  Mon Dec 23 03:45:29 2002
From: hazard (Vladimir Ivaschenko)
Date: Mon, 23 Dec 2002 13:45:29 +0200
Subject: (help) Unautorizing station  problem
In-Reply-To: <H000050a140dd62d.1040643643.kgomap0@MHS>
References: <H000050a140dd62d.1040643643.kgomap0@MHS>
Message-ID: <20021223134529.A18132@hzdhome.home.blkseanet.ru>

You think it is good to send the same message four times?

Looking at your diagram you don't need hostapd and 802.1X at all, since
you don't have any RADIUS server to authenticate to. So compile your
driver without hostapd support and everything should start to work. 

Mon, Dec 23, 2002 at 08:40:57PM +0900 cupid90 at samsung.co.kr wrote about (help) Unautorizing station  problem

> I am testing HOSTAP solution in my linux PC.
> I want to use my PC with access point.
> 
> I got the package and compiled and loading HOSTAP driver with hostapd(hostap daemon).
> and It was succeeded scanning AP(access point) in my the other PC(PCI client wireless card).

-- 
Best Regards
Vladimir Ivaschenko
http://www.hazard.maks.net/



From raghu  Mon Dec 23 13:10:24 2002
From: raghu (Raghu)
Date: Mon, 23 Dec 2002 16:10:24 -0500
Subject: 802.1X Unicast Keys?
Message-ID: <20021223211024.KOZ2474.imta01a2.registeredsite.com@smtp.registeredsite.com>

> I have never tested unicast keys without setting 
broadcast keys with 
> .1x. Are you setting broadcast keys manually for both 
the stations and 
> AP? I would suggest trying with both -i13 and -b13 on 
the same command 
> line to get both keys set automatically. Please let me 
know, if there is 
> 
 
$ ./hostapd -x -b13 -i13 -o192.168.1.1 -a192.168.1.1 
-stest -SSSID wlan0 
.. 
IEEE 802.1X: 00:04:5a:0d:f4:68 BE_AUTH entering state 
SUCCESS 
IEEE 802.1X: 00:04:5a:0d:f4:68 REAUTH_TIMER entering state 
INITIALIZE 
IEEE 802.1X: 00:04:5a:0d:f4:68 AUTH_PAE entering state 
AUTHENTICATED 
IEEE 802.1X: Authorizing station 00:04:5a:0d:f4:68 
IEEE 802.1X: 00:04:5a:0d:f4:68 BE_AUTH entering state IDLE 
DEBUG: STATE_MACHINE KEY TRANSMIT 
IEEE 802.1X: 00:04:5a:0d:f4:68 AUTH_KEY_TX entering state 
KEY_TRANSMIT 
IEEE 802.1X: Sending EAPOL-Key(s) to 00:04:5a:0d:f4:68 
(identifier 6) 
Individual WEP key - hexdump(len=13): bd f9 b4 6b 1c 2e 42 
46 b1 49 fc 7e ee 
Station 00:04:5a:0d:f4:68 authenticated (open system) 
Station 00:04:5a:0d:f4:68 associated (aid 1) 
 
 
Unicast key is getting generated but I am not sure if the 
same is 
sent to the Supplicant. I think only the Broadcast key is 
being sent. 
Currently I am not able to atleast ping the AP. With -b13 
option I was 
able to ping AP. 
 
Can you please let me know the state machine of 
transmitting the 
Broadcast key and Unicast key to the supplicant when -b13 
& -i13 
options are used on the same command? 
 
-Raghu 
 




From raghu  Mon Dec 23 20:11:46 2002
From: raghu (Raghu)
Date: Mon, 23 Dec 2002 23:11:46 -0500
Subject: 802.1X Unicast Keys?
Message-ID: <20021224041146.IBAR5165.imta02a2.registeredsite.com@smtp.registeredsite.com>

> Unicast key is getting generated but I am not sure if 
the  
> same is  
> sent to the Supplicant. I think only the Broadcast key 
is  
> being sent.  
> Currently I am not able to atleast ping the AP. With 
-b13  
> option I was  
> able to ping AP.  
>   
 
 
hostapd might be sending the Unicast key. I am not sure. 
But XSupplicant never receives the second EAPOL key frame. 
Is it possible that STA stops listening to open channel 
once after it receives the Broadcast key. 
How can I make sure that STA driver is aware of 802.1x ? 
 
-Raghu 




From ammirata  Tue Dec 24 08:04:50 2002
From: ammirata (Sergio M. Ammirata)
Date: Tue, 24 Dec 2002 11:04:50 -0500
Subject: hostapd
Message-ID: <000001c2ab66$3159d560$017ba8c0@ammirata.net>

I started to play around with the latest cvs version and the hostapd
program (enabled the option before compilation).

 

I have a few questions:

 

1)      Is there a way for hostapd to fork execution? How do I put it in
my init scripts if it doesn't? 

 

2)      Is there a way to enable a rotating key with the -m option. I
don't care about authenticating based on the 802.1X against a radius
server, I just want to leverage the rotating key functionality if the
client supports it to at least prevent WEP password cracking.

 

3)      Is there a way to leverage the radius client inside hostapd to
authenticate the MAC address for association? Right now the two options
are either to allow open access or to authenticate against a list of MAC
addresses that gets populated with "iwpriv wlan0 wds_add MAC-goes-here".
The idea is to be able to use a central server for global authentication
of MAC addresses throughout a network of Access Points without having to
maintain the same list in each of them. I know that 802.1X does this but
the idea is to not have to require it on the client side. Perhaps it can
use radius with the MAC as Username and Password and hit the radius
server using PAP.

 

4)      How does the radius client inside hostapd communicate with the
server? Is it PAP, CHAP, MsChapV2 or am I way off in understanding how
this works?

 

Thanks in advance,

 

Sergio

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021224/4c9baf7c/attachment.htm 


From jasonb  Tue Dec 24 08:30:04 2002
From: jasonb (Jason Boxman)
Date: Tue, 24 Dec 2002 11:30:04 -0500
Subject: hostapd
In-Reply-To: <000001c2ab66$3159d560$017ba8c0@ammirata.net>
References: <000001c2ab66$3159d560$017ba8c0@ammirata.net>
Message-ID: <200212241130.04109.jasonb@edseek.com>

On Tuesday 24 December 2002 11:04 am, Sergio M. Ammirata wrote:
> I started to play around with the latest cvs version and the hostapd
> program (enabled the option before compilation).
>
>
>
> I have a few questions:
>
>
>
> 1)      Is there a way for hostapd to fork execution? How do I put it in
> my init scripts if it doesn't?

I know Debian has start-stop-daemon with an optional argument to force 
processes into the background that just won't background.  There's also 
classic '&'.

As to the other questions, I am curious what the answers are myself.

<snip>
> Thanks in advance,
>
>
>
> Sergio

-- 

Jason Boxman
Administrator TrekWeb.COM
http://trekweb.com/~jasonb/articles/ - Linux Pages





From Jacques.Caron  Tue Dec 24 11:39:59 2002
From: Jacques.Caron (Jacques Caron)
Date: Tue, 24 Dec 2002 20:39:59 +0100
Subject: hostapd
In-Reply-To: <000001c2ab66$3159d560$017ba8c0@ammirata.net>
Message-ID: <5.2.0.9.0.20021224203124.01960130@pop.mail.yahoo.com>

Hi,

At 17:04 24/12/2002, Sergio M. Ammirata wrote:
>2)      Is there a way to enable a rotating key with the m option. I dont 
>care about authenticating based on the 802.1X against a radius server, I 
>just want to leverage the rotating key functionality if the client 
>supports it to at least prevent WEP password cracking.

I don't know the details of the hostapd implementation, but I don't quite 
see how key rotation could happen without 802.1X: EAPOL-Key frames are part 
of 802.1X, and they rely on the session key negotiated between the 
supplicant (client) and the auth server (RADIUS server) within the selected 
EAP method. Without this, anybody could decrypt the key sent and this would 
not be very useful, would it?

The only other option is to have the AP and client be synchronized on keys 
that change at regular intervals, using a pre-shared seed. But that's a 
totally different thing.

>3)      Is there a way to leverage the radius client inside hostapd to 
>authenticate the MAC address for association? Right now the two options 
>are either to allow open access or to authenticate against a list of MAC 
>addresses that gets populated with iwpriv wlan0 wds_add MAC-goes-here. The 
>idea is to be able to use a central server for global authentication of 
>MAC addresses throughout a network of Access Points without having to 
>maintain the same list in each of them. I know that 802.1X does this but 
>the idea is to not have to require it on the client side. Perhaps it can 
>use radius with the MAC as Username and Password and hit the radius server 
>using PAP.

The big problem with MAC addresses is that they are so easy to change that 
it doesn't even qualify as a security feature, and certainly not for a 
large-scale setup where you need/use a central auth server.

>4)      How does the radius client inside hostapd communicate with the 
>server? Is it PAP, CHAP, MsChapV2 or am I way off in understanding how 
>this works?

Errr... RADIUS? And within RADIUS, EAP messages (exchanged between the 
supplicant and the auth server) are encapsulated in the appropriate AVPs. 
And EAP messages themselves can use one of several different methods, the 
most common being EAP-TLS, but there's also EAP-MD5 (to be avoided), 
EAP-OTP, EAP-SRP, PEAP (with another protocol within, like EAP-MSCHAPv2), 
etc. Hostapd is transparent to those message, it just passes them between 
the supplicant and the auth server, just changing the encapsulation (EAPOL 
aka 802.1X on one side, RADIUS on the other).

Hope that helps,

Jacques.


-- Jacques Caron, IP Sector Technologies
    Join the discussion on public WLAN open global roaming:
    http://lists.ipsector.com/listinfo/openroaming





From ammirata  Tue Dec 24 13:31:22 2002
From: ammirata (Sergio M. Ammirata)
Date: Tue, 24 Dec 2002 16:31:22 -0500
Subject: hostapd
In-Reply-To: <5.2.0.9.0.20021224203124.01960130@pop.mail.yahoo.com>
Message-ID: <000001c2ab93$cf262140$017ba8c0@ammirata.net>


> -----Original Message-----
> From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] On Behalf
Of
> Jacques Caron
> Sent: Tuesday, December 24, 2002 2:40 PM
> To: Sergio M. Ammirata
> Cc: 'hostap mailing list'
> Subject: Re: hostapd
> Importance: High
> 
> Hi,
> 
> At 17:04 24/12/2002, Sergio M. Ammirata wrote:
> >2)      Is there a way to enable a rotating key with the m option. I
dont
> >care about authenticating based on the 802.1X against a radius
server, I
> >just want to leverage the rotating key functionality if the client
> >supports it to at least prevent WEP password cracking.
> 
> I don't know the details of the hostapd implementation, but I don't
quite
> see how key rotation could happen without 802.1X: EAPOL-Key frames are
> part
> of 802.1X, and they rely on the session key negotiated between the
> supplicant (client) and the auth server (RADIUS server) within the
> selected
> EAP method. Without this, anybody could decrypt the key sent and this
> would
> not be very useful, would it?

I am not suggesting that we do a proprietary key exchanging mechanism. I
am suggesting that hostapd be enhanced to do what the radius server does
as far as key rotation. Perhaps starting with a random key for each
client and keeping track of the key changes per client.

That way if a client supports 802.1X it can be leveraged for key
rotation.

> The only other option is to have the AP and client be synchronized on
keys
> that change at regular intervals, using a pre-shared seed. But that's
a
> totally different thing.

Any proprietary method of key exchange would require special client
software. The idea is to leverage existing Windows, MAC and linux
clients that already have support for 802.1X without having to have a
complex authentication setup.

> >3)      Is there a way to leverage the radius client inside hostapd
to
> >authenticate the MAC address for association? Right now the two
options
> >are either to allow open access or to authenticate against a list of
MAC
> >addresses that gets populated with iwpriv wlan0 wds_add
MAC-goes-here.
> The
> >idea is to be able to use a central server for global authentication
of
> >MAC addresses throughout a network of Access Points without having to
> >maintain the same list in each of them. I know that 802.1X does this
but
> >the idea is to not have to require it on the client side. Perhaps it
can
> >use radius with the MAC as Username and Password and hit the radius
> server
> >using PAP.
> 
> The big problem with MAC addresses is that they are so easy to change
that
> it doesn't even qualify as a security feature, and certainly not for a
> large-scale setup where you need/use a central auth server.

I agree that this layer of security is easily hackable. But why discard
it? It will detour at least the roaming users that are not supposed to
link to your network. 

> >4)      How does the radius client inside hostapd communicate with
the
> >server? Is it PAP, CHAP, MsChapV2 or am I way off in understanding
how
> >this works?
> 
> Errr... RADIUS? And within RADIUS, EAP messages (exchanged between the
> supplicant and the auth server) are encapsulated in the appropriate
AVPs.
> And EAP messages themselves can use one of several different methods,
the
> most common being EAP-TLS, but there's also EAP-MD5 (to be avoided),
> EAP-OTP, EAP-SRP, PEAP (with another protocol within, like
EAP-MSCHAPv2),
> etc. Hostapd is transparent to those message, it just passes them
between
> the supplicant and the auth server, just changing the encapsulation
(EAPOL
> aka 802.1X on one side, RADIUS on the other).

I guess it will not be as simple to emulate the radius server for the
EAP messages.

However, for the custom MAC address authentication against a radius
server, the hostapd program can create a few simple Radius Value Pairs
that emulate PAP authentication and then parse the response.

Sergio





From Jacques.Caron  Tue Dec 24 17:58:20 2002
From: Jacques.Caron (Jacques Caron)
Date: Wed, 25 Dec 2002 02:58:20 +0100
Subject: hostapd
In-Reply-To: <000001c2ab93$cf262140$017ba8c0@ammirata.net>
References: <5.2.0.9.0.20021224203124.01960130@pop.mail.yahoo.com>
Message-ID: <5.2.0.9.0.20021225025120.0334adf8@wheresmymailserver.com>

At 22:31 24/12/2002, Sergio M. Ammirata wrote:
>I am not suggesting that we do a proprietary key exchanging mechanism. I
>am suggesting that hostapd be enhanced to do what the radius server does
>as far as key rotation. Perhaps starting with a random key for each
>client and keeping track of the key changes per client.

Well then you mean having a RADIUS server built-in :-) Install freeRADIUS 
on the same box and off you go. I don't think putting this functionality in 
hostapd itself would be a good thing, you would need to implement (again) 
the EAP methods, when you could just use a RADIUS server which is really 
not that hard to set up.

And even if the keys are random (they can be), you *need* to have a master 
session key that has been derived independently by the client and server 
sides of the EAP method based on the credentials (which btw limits the use 
to EAP methods that can actually do that, like EAP TLS, EAP SRP, but not 
EAP MD5 or EAP OTP). And this implies having a credentials database on the 
server side, so putting all this in hostapd would make it a lot bigger 
without much gain if compared to separate hostapd / RADIUS servers on the 
same box (and less flexibility etc.).

> > The big problem with MAC addresses is that they are so easy to change
>that
> > it doesn't even qualify as a security feature, and certainly not for a
> > large-scale setup where you need/use a central auth server.
>
>I agree that this layer of security is easily hackable. But why discard
>it? It will detour at least the roaming users that are not supposed to
>link to your network.

If it is used as a first step auth (e.g. at association time, before moving 
on to 802.1X for known MAC addresses), it could indeed be a good idea. But 
there might be timing issues with that, I'm not sure a round-trip to a 
possibly remote RADIUS server would be possible within the time allowed for 
the association (but I'm wild guessing here and too lazy to go check the 
spec right now).

BTW, Merry Christmas to everybody!

Jacques.


-- Jacques Caron, IP Sector Technologies
    Join the discussion on public WLAN open global roaming:
    http://lists.ipsector.com/listinfo/openroaming





From gbritton  Wed Dec 25 19:43:17 2002
From: gbritton (Gerald Britton)
Date: Wed, 25 Dec 2002 22:43:17 -0500
Subject: new capture format
Message-ID: <20021225224317.A25654@nevermore.toe.doomcom.org>

I've completed an implementation of the new capture format included in
recent linux-wlan-ng.  It's attached.  This implements monitor_type 2
providing the new frame format with the arp type of ARPHRD_IEEE80211_PRISM,
The two frame types using this arp type place a unique 32bit word in the
first location of the packet, I used that value to determine which type is
used in an skb for the header_parse function and in my userspace code.

Merry Christmas.

				-- Gerald

-------------- next part --------------
diff -ruN hostap/driver/modules/hostap.c hostap.cap/driver/modules/hostap.c
--- hostap/driver/modules/hostap.c	2002-12-08 21:18:21.000000000 -0500
+++ hostap.cap/driver/modules/hostap.c	2002-12-25 20:55:52.000000000 -0500
@@ -596,8 +596,15 @@
 
 int hostap_80211_prism_header_parse(struct sk_buff *skb, unsigned char *haddr)
 {
-	memcpy(haddr, skb->mac.raw + sizeof(struct linux_wlan_ng_prism_hdr) +
-	       10, ETH_ALEN); /* addr2 */
+	if (*(u32 *)skb->mac.raw == LWNG_CAP_DID_BASE) {
+		memcpy(haddr, skb->mac.raw +
+		       sizeof(struct linux_wlan_ng_prism_hdr) + 10,
+		       ETH_ALEN); /* addr2 */
+	} else { /* (*(u32 *)skb->mac.raw == htonl(LWNG_CAPHDR_VERSION)) */
+		memcpy(haddr, skb->mac.raw +
+		       sizeof(struct linux_wlan_ng_cap_hdr) + 10,
+		       ETH_ALEN); /* addr2 */
+	}
 	return ETH_ALEN;
 }
 
diff -ruN hostap/driver/modules/hostap_hw.c hostap.cap/driver/modules/hostap_hw.c
--- hostap/driver/modules/hostap_hw.c	2002-12-04 11:17:47.000000000 -0500
+++ hostap.cap/driver/modules/hostap_hw.c	2002-12-25 21:07:26.000000000 -0500
@@ -2079,6 +2079,7 @@
 static int prism2_rx_80211(struct net_device *dev, struct sk_buff *skb,
 			   int type, char *extra, int extra_len)
 {
+	local_info_t *local = (local_info_t *) dev->priv;
 	int hdrlen, phdrlen, head_need, tail_need;
 	u16 len, fc;
 	int prism_header;
@@ -2091,7 +2092,18 @@
 	memcpy(&rxdesc, skb->data, sizeof(rxdesc));
 	skb_pull(skb, sizeof(rxdesc));
 
-	prism_header = dev->type == ARPHRD_IEEE80211_PRISM;
+	if (dev->type == ARPHRD_IEEE80211_PRISM) {
+		if (local->monitor_type == PRISM2_MONITOR_PRISM) {
+			prism_header = 1;
+			phdrlen = sizeof(struct linux_wlan_ng_prism_hdr);
+		} else { /* local->monitor_type == PRISM2_MONITOR_CAPHDR */
+			prism_header = 2;
+			phdrlen = sizeof(struct linux_wlan_ng_cap_hdr);
+		}
+	} else {
+		prism_header = 0;
+		phdrlen = 0;
+	}
 
 	fc = le16_to_cpu(rxdesc.frame_control);
 
@@ -2102,7 +2114,6 @@
 		return 0;
 	}
 
-	phdrlen = prism_header ? sizeof(struct linux_wlan_ng_prism_hdr) : 0;
 	hdrlen = hostap_80211_get_hdrlen(fc);
 
 	if (extra) {
@@ -2154,18 +2165,17 @@
 	 * the extra data */
 	memcpy(skb_push(skb, hdrlen), &rxdesc.frame_control, hdrlen);
 
-	if (prism_header) {
+	if (prism_header == 1) {
 		struct linux_wlan_ng_prism_hdr *hdr;
 		hdr = (struct linux_wlan_ng_prism_hdr *)
 			skb_push(skb, phdrlen);
 		memset(hdr, 0, phdrlen);
-#define LWNG_DID_BASE (4 | (1 << 6)) /* section 4, group 1 */
-		hdr->msgcode = LWNG_DID_BASE;
+		hdr->msgcode = LWNG_CAP_DID_BASE;
 		hdr->msglen = sizeof(*hdr);
 		memcpy(hdr->devname, dev->name, sizeof(hdr->devname));
 #define LWNG_SETVAL(f,i,s,l,d) \
-hdr->f.did = LWNG_DID_BASE | (i << 12); hdr->f.status = s; hdr->f.len = l; \
-hdr->f.data = d
+hdr->f.did = LWNG_CAP_DID_BASE | (i << 12); \
+hdr->f.status = s; hdr->f.len = l; hdr->f.data = d
 		LWNG_SETVAL(hosttime, 1, 0, 4, jiffies);
 		LWNG_SETVAL(mactime, 2, 0, 0, le32_to_cpu(rxdesc.time));
 		LWNG_SETVAL(channel, 3, 1 /* no value */, 4, 0);
@@ -2181,7 +2191,25 @@
 		LWNG_SETVAL(frmlen, 10, 0, 4, hdrlen + len);
 #endif /* PRISM2_ADD_BOGUS_CRC */
 #undef LWNG_SETVAL
-#undef LWNG_DID_BASE
+	} else if (prism_header == 2) {
+		struct linux_wlan_ng_cap_hdr *hdr;
+		hdr = (struct linux_wlan_ng_cap_hdr *)
+			skb_push(skb, phdrlen);
+		memset(hdr, 0, phdrlen);
+		hdr->version    = htonl(LWNG_CAPHDR_VERSION);
+		hdr->length     = htonl(phdrlen);
+		hdr->mactime    = __cpu_to_be64(rxdesc.time);
+		hdr->hosttime   = __cpu_to_be64(jiffies);
+		hdr->phytype    = htonl(4); /* dss_dot11_b */
+		hdr->channel    = htonl(0); /* unknown */
+		hdr->datarate   = htonl(rxdesc.rate);
+		hdr->antenna    = htonl(0); /* unknown */
+		hdr->priority   = htonl(0); /* unknown */
+		hdr->ssi_type   = htonl(3); /* raw */
+		hdr->ssi_signal = htonl(rxdesc.signal);
+		hdr->ssi_noise  = htonl(rxdesc.silence);
+		hdr->preamble   = htonl(0); /* unknown */
+		hdr->encoding   = htonl(1); /* cck */
 	}
 
 #ifdef PRISM2_ADD_BOGUS_CRC
diff -ruN hostap/driver/modules/hostap_ioctl.c hostap.cap/driver/modules/hostap_ioctl.c
--- hostap/driver/modules/hostap_ioctl.c	2002-12-08 03:54:53.000000000 -0500
+++ hostap.cap/driver/modules/hostap_ioctl.c	2002-12-25 21:10:12.000000000 -0500
@@ -731,7 +731,8 @@
 {
 	struct net_device *dev = local->dev;
 
-	if (local->monitor_type == PRISM2_MONITOR_PRISM) {
+	if (local->monitor_type == PRISM2_MONITOR_PRISM ||
+	    local->monitor_type == PRISM2_MONITOR_CAPHDR) {
 		dev->type = ARPHRD_IEEE80211_PRISM;
 		dev->hard_header_parse =
 			hostap_80211_prism_header_parse;
@@ -2094,6 +2095,7 @@
 
 	case PRISM2_PARAM_MONITOR_TYPE:
 		if (value != PRISM2_MONITOR_80211 &&
+		    value != PRISM2_MONITOR_CAPHDR &&
 		    value != PRISM2_MONITOR_PRISM) {
 			ret = -EINVAL;
 			break;
diff -ruN hostap/driver/modules/hostap_wlan.h hostap.cap/driver/modules/hostap_wlan.h
--- hostap/driver/modules/hostap_wlan.h	2002-12-03 22:56:55.000000000 -0500
+++ hostap.cap/driver/modules/hostap_wlan.h	2002-12-25 21:04:55.000000000 -0500
@@ -49,6 +49,25 @@
 		noise, rate, istx, frmlen;
 } __attribute__ ((packed));
 
+struct linux_wlan_ng_cap_hdr {
+	u32 version;
+	u32 length;
+	u64 mactime;
+	u64 hosttime;
+	u32 phytype;
+	u32 channel;
+	u32 datarate;
+	u32 antenna;
+	u32 priority;
+	u32 ssi_type;
+	s32 ssi_signal;
+	s32 ssi_noise;
+	u32 preamble;
+	u32 encoding;
+} __attribute__ ((packed));
+
+#define LWNG_CAP_DID_BASE   (4 | (1 << 6)) /* section 4, group 1 */
+#define LWNG_CAPHDR_VERSION 0x80211001
 
 struct hostap_ieee80211_hdr {
 	u16 frame_control;
@@ -1146,7 +1165,8 @@
 #endif /* WIRELESS_EXT > 13 */
 #endif /* WIRELESS_EXT */
 	enum {
-		PRISM2_MONITOR_80211 = 0, PRISM2_MONITOR_PRISM = 1
+		PRISM2_MONITOR_80211 = 0, PRISM2_MONITOR_PRISM = 1,
+		PRISM2_MONITOR_CAPHDR = 2
 	} monitor_type;
 	int (*saved_eth_header_parse)(struct sk_buff *skb,
 				      unsigned char *haddr);


From jwickman  Thu Dec 26 07:42:49 2002
From: jwickman (Joachim Wickman)
Date: Thu, 26 Dec 2002 17:42:49 +0200 (EET)
Subject: Unresolved symbols & kernel-2.4.20 & pcmcia-cs-3.2.3
Message-ID: <Pine.LNX.4.33.0212261734260.12963-100000@www.tawi.fi>

Hello,

I'm trying to get my Compaq WL-200 to work with kernel 2.4.20.
First problem is that kernel pcmcia doesn't find the bridge so I
downloaded pcmcia-3.2.3 and installed that one.

Now it finds the card. =)

The main problem.
depmod -e
depmod: *** Unresolved symbols in /lib/modules/2.4.20/net/hostap.o
depmod:         wireless_send_event
depmod: *** Unresolved symbols in /lib/modules/2.4.20/pcmcia/hostap_cs.o
depmod:         wireless_send_event

I've tried everything I can think of now and no success. Tested with
hostap cvs and last stable, pcmcia-cs-3.2.1 and 3.2.3.

Added this in HostAP Makefile:
PCMCIA_PATH=/usr/src/pcmcia-cs-3.2.3

I did choose wireless lan in kernel, s? wireless extensions should be
compiled with kernel.
[*] Wireless LAN (non-hamradio)

I even upgrade to wireless extension v15, but no difference.

What am I missing?


Thx,
  Joachim





From doug  Thu Dec 26 08:25:36 2002
From: doug (Doug Yeager)
Date: Thu, 26 Dec 2002 11:25:36 -0500
Subject: NL-2511CD PLUS EXT2 
Message-ID: <4.3.2.7.0.20021226112314.032f5a10@yeagerautomation.com>

just got a 200 mw card and pci adapter from netgate.
i've always used the wmp11 (pci wireless card) before.

i'm trying to use the latest cvs of hostap to get it running.

i'm confused on weather to use the _plx driver or the _cs driver.
has anyone use this card and pci adapter before?

any advice on getting the driver up and running would be most appreciated.

thx,
doug




From Peter.DeCleyn  Thu Dec 26 08:35:41 2002
From: Peter.DeCleyn (Peter De Cleyn)
Date: Thu, 26 Dec 2002 17:35:41 +0100 (CET)
Subject: NL-2511CD PLUS EXT2 
In-Reply-To: <4.3.2.7.0.20021226112314.032f5a10@yeagerautomation.com>
Message-ID: <Pine.LNX.4.33L2.0212261732290.32124-100000@pcinf26.uia.ac.be>

On Thu, 26 Dec 2002, Doug Yeager wrote:

Hi Doug,

I succeeded in running hostap with Linksys WPC11 and a TI adapter using
the _cs driver.

Orinoco cards in the same adapter also use the PCMCIA drivers from the
pcmcia package. Using the adaptor, you expand your system with a PCMCIA
slot and you have to work with  it as if it were a built-in device of your
laptop.

Peter

> just got a 200 mw card and pci adapter from netgate.
> i've always used the wmp11 (pci wireless card) before.
>
> i'm trying to use the latest cvs of hostap to get it running.
>
> i'm confused on weather to use the _plx driver or the _cs driver.
> has anyone use this card and pci adapter before?
>
> any advice on getting the driver up and running would be most appreciated.
>
> thx,
> doug
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>

 _______________
/ Peter De Cleyn\
-------------------------------------------------------
| Phone:                +32 (0)3 820.24.18            |
| Fax:                  +32 (0)3 820.24.21            |
| email:                peter.decleyn at ua.ac.be        |
|                                                     |
| University of Antwerp (UIA)                         |
| Dept. Mathematics and Computer Science              |
| PATS Research Group                                 |
| Universiteitsplein 1                                |
| B-2610 Wilrijk                                      |
| Belgium                                             |
-------------------------------------------------------






From Peter.DeCleyn  Thu Dec 26 10:32:34 2002
From: Peter.DeCleyn (Peter De Cleyn)
Date: Thu, 26 Dec 2002 19:32:34 +0100 (CET)
Subject: NL-2511CD PLUS EXT2 
In-Reply-To: <4.3.2.7.0.20021226131017.032ee510@yeagerautomation.com>
Message-ID: <Pine.LNX.4.33L2.0212261923120.32427-100000@pcinf26.uia.ac.be>

On Thu, 26 Dec 2002, Doug Yeager wrote:

> thanks again peter,
> i think i'm finding out in the docs about something called "cardmgr"  that
> may have to do w/ the pcmcia and pci adapter.
> i did a "find / -name "cardmgr"" and nothing came up on my system.  i
> assume that means i'm missing something that i probably need but not sure.
> any thoughts would be helpful.
>
> i'm running radhat 7.3 (2.4 kernel).  on a desktop machine w/ that pci adapter.
> i'm guessing i need to rebuild the kernel again for pcmcia or something,
> but unclear if i need to do that.

Yes, as I said you need to handle your adaptor like a PCMIA slot and thus
you need the pcmcia drivers. There are 2 options: the kernel version or
the separate package. the pcmcia_cs package can be found on
sourceforge.org. The other option is to enable the PCMCIA option in your
kernel and install this new kernel.

If you whish to get the most out of hostap you might want to read
http://www.trekweb.com/~jasonb/articles/hostap_20021012.shtml. There's a
list of the upgrades you need if you would like to upgrade to the latest
wireless tools and wireless extentions.

Hope this helps,

Peter




From mohit  Fri Dec 27 06:21:09 2002
From: mohit (Mohit Bajpai)
Date: Fri, 27 Dec 2002 19:51:09 +0530
Subject: reassosciation request comes more than once!
Message-ID: <001e01c2adb3$9cd5be40$f009030a@mahindrabt.com>

Hi,
    I have been trying out IAPP implementation with  latest hostap driver released on 2002-10-12.  I am using the hostapd mode of the hostap driver.During testing the MOVE operation I found that when STA moves to new AP the new AP detects reassociation of STA more than once. could you please tell that whether this multiple detection of reassociating STA should happen or not because if it is so then it will send move signal more than once which does not seem to be correct.

Thanks and regards,
Mohit Bajpai

*********************************************************
Disclaimer

This message (including any attachments) contains 
confidential information intended for a specific 
individual and purpose, and is protected by law. 
If you are not the intended recipient, you should 
delete this message and are hereby notified that 
any disclosure, copying, or distribution of this
message, or the taking of any action based on it, 
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021227/91fcd829/attachment.htm 


From doug  Sat Dec 28 15:06:09 2002
From: doug (Doug Yeager)
Date: Sat, 28 Dec 2002 18:06:09 -0500
Subject: wds with both ap's associating to stations
Message-ID: <4.3.2.7.0.20021228180147.02f89f00@yeagerautomation.com>

following this example is great, but i want both AP's to associate to 
stations.  this example only has A associating.
is it o.k. to do a "brctl addif br0 wlan0" and "ifconfig wlan0 0.0.0.0" for 
B configuration also?  i try to do this and i start getting some errors 
when i try to ping from one station to another.  i don't know if the errors 
are supposed to be there or a bug.  any help would be great

AP-A configuration:

iwpriv wlan0 wds_add 00:22:22:22:22:22
brctl addbr br0
brctl addif br0 eth0
brctl addif br0 wlan0
brctl addif br0 wlan0wds0
ifconfig eth0 0.0.0.0
ifconfig wlan0 0.0.0.0
ifconfig wlan0wds0 0.0.0.0
ifconfig br0 192.168.1.1 up

AP-B configuration:

iwpriv wlan0 wds_add 00:11:11:11:11:11
brctl addbr br0
brctl addif br0 eth0
brctl addif br0 wlan0wds0
ifconfig eth0 0.0.0.0
ifconfig wlan0wds0 0.0.0.0
ifconfig br0 192.168.1.2 up




From jkmaline  Sun Dec 29 01:41:06 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 29 Dec 2002 01:41:06 -0800
Subject: wds with both ap's associating to stations
In-Reply-To: <4.3.2.7.0.20021228180147.02f89f00@yeagerautomation.com>
References: <4.3.2.7.0.20021228180147.02f89f00@yeagerautomation.com>
Message-ID: <20021229094106.GA2606@jm.kir.nu>

On Sat, Dec 28, 2002 at 06:06:09PM -0500, Doug Yeager wrote:

> following this example is great, but i want both AP's to associate to 
> stations.  this example only has A associating.
> is it o.k. to do a "brctl addif br0 wlan0" and "ifconfig wlan0 0.0.0.0" for 
> B configuration also?  i try to do this and i start getting some errors 
> when i try to ping from one station to another.  i don't know if the errors 
> are supposed to be there or a bug.  any help would be great

Yes, it should be OK to add wlan0 to the bridge device on both APs. What
kind of errors do you get? Is the connection between stations working at
all in that configuration? If not, can you find the place where packet
is lost (e.g., is it sent over WDS link)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From doug  Sun Dec 29 05:01:23 2002
From: doug (Doug Yeager)
Date: Sun, 29 Dec 2002 08:01:23 -0500
Subject: wds with both ap's associating to stations
In-Reply-To: <20021229094106.GA2606@jm.kir.nu>
References: <4.3.2.7.0.20021228180147.02f89f00@yeagerautomation.com>
 <4.3.2.7.0.20021228180147.02f89f00@yeagerautomation.com>
Message-ID: <4.3.2.7.0.20021229075755.02fc58f0@yeagerautomation.com>

thanks jouni,
i wanted to make sure i was attempting something that was possible before i 
went looking for my problem.
things seem to happen as soon as i bringe up the bridge.  at this point i 
have one other AP about 5 feet away with basically the identical config.  i 
also have one station running at the same time.

this is my messages log when i bring up the bridge.  thesse "hook" messages 
go on and on in my log.


Dec 28 11:31:18 home kernel: NET4: Ethernet Bridge 008 for NET4.0
Dec 28 11:31:18 home kernel: Bridge firewalling registered
Dec 28 11:31:18 home /etc/hotplug/net.agent: invoke ifup br0
Dec 28 11:31:39 home kernel: device wlan0 entered promiscuous mode
Dec 28 11:33:33 home login(pam_unix)[1053]: session opened for user root by 
LOGIN(uid=0)
Dec 28 11:33:33 home  -- root[1053]: ROOT LOGIN ON tty1
Dec 28 11:34:18 home kernel: device wlan0wds0 entered promiscuous mode
Dec 28 11:34:55 home kernel: br0: port 1(wlan0) entering listening state
Dec 28 11:35:10 home kernel: br0: port 1(wlan0) entering learning state
Dec 28 11:35:25 home kernel: br0: port 1(wlan0) entering forwarding state
Dec 28 11:35:25 home kernel: br0: topology change detected, propagating
Dec 28 11:35:41 home kernel: br0: port 1(wlan0) entering disabled state
Dec 28 11:46:56 home kernel: br0: port 1(wlan0) entering listening state
Dec 28 11:47:01 home kernel: br0: port 2(wlan0wds0) entering listening state
Dec 28 11:47:11 home kernel: br0: port 1(wlan0) entering learning state
Dec 28 11:47:16 home kernel: br0: port 2(wlan0wds0) entering learning state
Dec 28 11:47:26 home kernel: br0: port 1(wlan0) entering forwarding state
Dec 28 11:47:26 home kernel: br0: topology change detected, sending tcn bpdu
Dec 28 11:47:31 home kernel: br0: port 2(wlan0wds0) entering forwarding state
Dec 28 11:47:31 home kernel: br0: topology change detected, sending tcn bpdu
Dec 28 11:47:32 home kernel: nf_hook: hook 3 already set.
Dec 28 11:47:32 home kernel: skb: pf=7 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: nf_hook: hook 3 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.1:0 192.168.1.10:0 L=84 
S=0x00 I=0 F=0x4000 T=64
Dec 28 11:47:32 home kernel: nf_hook: hook 4 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.1:0 192.168.1.10:0 L=84 
S=0x00 I=0 F=0x4000 T=64
Dec 28 11:47:32 home kernel: nf_hook: hook 4 already set.
Dec 28 11:47:32 home kernel: skb: pf=7 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: nf_hook: hook 3 already set.
Dec 28 11:47:32 home kernel: skb: pf=7 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: nf_hook: hook 3 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.1:0 192.168.1.10:0 L=84 
S=0x00 I=0 F=0x4000 T=64
Dec 28 11:47:32 home kernel: nf_hook: hook 4 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.1:0 192.168.1.10:0 L=84 
S=0x00 I=0 F=0x4000 T=64
Dec 28 11:47:32 home kernel: nf_hook: hook 0 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (unowned) dev=br0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.10:0 192.168.1.1:0 L=84 
S=0x00 I=12225 F=0x0000 T=255
Dec 28 11:47:32 home kernel: nf_hook: hook 0 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (unowned) dev=br0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.10:0 192.168.1.1:0 L=84 
S=0x00 I=12225 F=0x0000 T=255
Dec 28 11:47:32 home kernel: nf_hook: hook 1 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (unowned) dev=br0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.10:0 192.168.1.1:0 L=84 
S=0x00 I=12225 F=0x0000 T=255
Dec 28 11:47:33 home kernel: nf_hook: hook 3 already set.
Dec 28 11:47:33 home kernel: skb: pf=7 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:33 home kernel: nf_hook: hook 3 already set.
Dec 28 11:47:33 home kernel: skb: pf=2 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:33 home kernel: PROTO=1 192.168.1.1:0 192.168.1.10:0 L=84 
S=0x00 I=0 F=0x4000 T=64
Dec 28 11:47:33 home kernel: nf_hook: hook 4 already set.
Dec 28 11:47:33 home kernel: skb: pf=2 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:33 home kernel: PROTO=1 192.168.1.1:0 192.168.1.10:0 L=84 
S=0x00 I=0 F=0x4000 T=64
D






At 01:41 AM 12/29/2002 -0800, Jouni Malinen wrote:
>On Sat, Dec 28, 2002 at 06:06:09PM -0500, Doug Yeager wrote:
>
> > following this example is great, but i want both AP's to associate to
> > stations.  this example only has A associating.
> > is it o.k. to do a "brctl addif br0 wlan0" and "ifconfig wlan0 0.0.0.0" 
> for
> > B configuration also?  i try to do this and i start getting some errors
> > when i try to ping from one station to another.  i don't know if the 
> errors
> > are supposed to be there or a bug.  any help would be great
>
>Yes, it should be OK to add wlan0 to the bridge device on both APs. What
>kind of errors do you get? Is the connection between stations working at
>all in that configuration? If not, can you find the place where packet
>is lost (e.g., is it sent over WDS link)?
>
>--
>Jouni Malinen                                            PGP id EFC895FA
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap




From bh  Sun Dec 29 16:15:08 2002
From: bh (Henrion Benjamin)
Date: Mon, 30 Dec 2002 01:15:08 +0100
Subject: Phased Array antenna project and I/Q values
Message-ID: <20021230001508.GA6955@localhost>

Hello,

I'm trying to build a phased array antenna system with 4 prism2 pci cards.

I've taken a look at:

http://www.stanford.edu/~anilkot/transceivers.html

I would like to know if it's possible with the help of the source code
of hostap to get the values of I and Q (DAC and ADC) that are that taken in
input in the wireless system.

Is it possible? Maybe there's developpers of the prism2 driver here that
can help me?

-- 
Benjamin Henrion <bh at udev.org>
http://bh.udev.org



From james.harper  Mon Dec 30 01:51:40 2002
From: james.harper (James Harper)
Date: Mon, 30 Dec 2002 20:51:40 +1100
Subject: DWL-520 intermittent init failures
Message-ID: <3E10172C.7080605@bigpond.com>

  hi all,

I'm using a dlink DWL-520 with some success. When it works, it appears 
to work fine. about 50% of the time though, it won't initialize 
correctly. I can see a wlan0 interface if i type 'ifconfig wlan0' but as 
far as anything else is concerned (iwconfig, ifconfig wlan0 up, etc) it 
just ain't there.

When it works, i get the following startup logs:
Dec 28 22:08:50 portal kernel: hostap_pci: 0.0.0 CVS (Jouni Malinen 
<jkmaline at cc.hut.fi>)
Dec 28 22:08:50 portal kernel: hostap_pci: Registered netdevice wlan0
Dec 28 22:08:50 portal kernel: prism2_hw_init()
Dec 28 22:08:50 portal kernel: prism2_hw_config: initialized in 17322 
iterations
Dec 28 22:08:50 portal kernel: wlan0: trying to read PDA from 0x007f0000: OK
Dec 28 22:08:50 portal kernel: wlan0: NIC: id=0x8013 v1.0.0
Dec 28 22:08:50 portal kernel: wlan0: PRI: id=0x15 v1.0.5
Dec 28 22:08:50 portal kernel: wlan0: STA: id=0x1f v1.3.4
Dec 28 22:08:50 portal kernel: wlan0: defaulting to host-based 
encryption as a workaround for firmware bug in Host AP mode WEP
Dec 28 22:08:50 portal kernel: wlan0: defaulting to bogus WDS frame as a 
workaround for firmware bug in Host AP mode WDS
Dec 28 22:08:50 portal kernel: wlan0: LinkStatus=2 (Disconnected)
Dec 28 22:08:50 portal kernel: wlan0: Intersil Prism2.5 PCI: 
mem=0xd9002000, irq=19
Dec 28 22:08:50 portal kernel: wlan0: prism2_open

When it fails i get something like one of the following:
Dec 29 10:22:49 portal kernel: prism2_hw_init()
Dec 29 10:22:49 portal kernel: wlan0: prism2_open
Dec 29 10:22:49 portal kernel: Module hostap_pci cannot be unloaded due 
to unsafe usage in drivers/net/wireless/hostap.c:688
Dec 29 10:22:49 portal kernel: prism2_hw_config: initialized in 22324 
iterations
Dec 29 10:22:49 portal kernel: wlan0: trying to read PDA from 0x007f0000: OK
Dec 29 10:22:49 portal kernel: wlan0: fid allocate, len=2364 - timeout
Dec 29 10:22:49 portal kernel: wlan0: Using shorter TX FID (1600 bytes)
Dec 29 10:22:49 portal kernel: wlan0: could not find matching txfid 
(0x01bb) for alloc event
Dec 29 10:22:49 portal kernel: wlan0: NIC: id=0x8013 v1.0.0
Dec 29 10:22:49 portal kernel: wlan0: PRI: id=0x15 v1.0.5
Dec 29 10:22:49 portal kernel: wlan0: STA: id=0x1f v1.3.4
Dec 29 10:22:49 portal kernel: wlan0: defaulting to host-based 
encryption as a workaround for firmware bug in Host AP mode WEP
Dec 29 10:22:49 portal kernel: wlan0: defaulting to bogus WDS frame as a 
workaround for firmware bug in Host AP mode WDS
Dec 29 10:22:49 portal kernel: wlan0: LinkStatus=2 (Disconnected)
Dec 29 10:22:49 portal kernel: wlan0: Intersil Prism2.5 PCI: 
mem=0xd9002000, irq=19
(I think that one might have actually worked - the first init failed but 
the second with the reduced size=1600 succeded)

Dec 29 11:02:05 portal kernel: prism2_hw_init()
Dec 29 11:02:05 portal kernel: wlan0: prism2_open
Dec 29 11:02:05 portal kernel: Module hostap_pci cannot be unloaded due 
to unsafe usage in drivers/net/wireless/hostap.c:688
Dec 29 11:02:05 portal kernel: prism2_hw_config: initialized in 17321 
iterations
Dec 29 11:02:05 portal kernel: wlan0: trying to read PDA from 0x007f0000: OK
Dec 29 11:02:05 portal kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=cfb2bd20, type=0, res=0)
Dec 29 11:02:05 portal kernel: wlan0: hfa384x_cmd: command was not 
completed (res=0, entry=cfb2bd20, type=0, cmd=0x0001, param0=0x0000)
Dec 29 11:02:05 portal kernel: wlan0: MAC port 0 enabling failed
Dec 29 11:02:05 portal kernel: wlan0: could not enable MAC port 
Dec 29 11:02:05 portal kernel: wlan0: prism2_close
Dec 29 11:02:05 portal kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=cf16f4a0, type=0, res=0)
Dec 29 11:02:05 portal kernel: wlan0: hfa384x_cmd: command was not 
completed (res=0, entry=cf16f4a0, type=0, cmd=0x0021, param0=0xfd0b)
Dec 29 11:02:05 portal kernel: wlan0: hfa384x_get_rid: CMDCODE_ACCESS 
failed (res=-110, rid=fd0b, len=8)
Dec 29 11:02:05 portal kernel: Could not get RID for component NIC
Dec 29 11:02:05 portal kernel: wlan0: PRI: id=0x15 v1.0.5
Dec 29 11:02:05 portal kernel: wlan0: STA: id=0x1f v1.3.4

I'm sure i've seen some other error messages in the init sequence but 
looking through my logs i can't seem to see them.

On poweron, if i pause at the GRUB boot menu (grub = 'GRand Unified 
Bootloader' for anyone who doesn't know) for a minute or so i seem to 
have more success, but even after a 60 second pause it has failed at 
least once.

from what i can deduce by looking at the code, one of the first things 
it does is try and read the 'NIC' value on the card. the code thinks the 
command has been accepted, but the card appears jammed, so the 
subsequent command to be executed gets confused.

my config is:
ABIT BP6
2 x Celeron 400 CPUs (running at 400 - never overclocked)
NVidia graphics adapter
various other adapters - i don't think they're important but if someone 
thinks they might be i'll get the info.
kernel version 2.5.53 (with hostap-linux-2.5.47.patch applied)
hostap installed in kernel tree (didn't work otherwise - 2.5.x has 
really changed the way modules work)
CONFIG_HOSTAP=m
# CONFIG_HOSTAP_HOSTAPD is not set
CONFIG_HOSTAP_FIRMWARE=y
# CONFIG_HOSTAP_PLX is not set
CONFIG_HOSTAP_PCI=m
CONFIG_NET_WIRELESS=y

It definitely appears to be a timing issue at boot. I just tried 
rebooting with 'maxcpus=1' but it still failed sometimes. Using 'nosmp' 
my machine won't boot at all so i can't easily test a 'proper' 
uniprocessor kernel (although i can compile one if anyone feels it will 
help). The failure definitely lies in the part of the code that runs 
before interrupts are enabled on the card though...

I have also tried turning off HOSTAP_FIRMWARE with no success.

can anyone help/offer any suggestions?

thanks

James





From mohit_bajpai  Mon Dec 30 06:28:48 2002
From: mohit_bajpai (Mohit bajpai)
Date: Mon, 30 Dec 2002 06:28:48 -0800 (PST)
Subject: multiple reassociation at HostAP
Message-ID: <20021230142848.68143.qmail@web41105.mail.yahoo.com>


Hi Jouni,

I am using the hostapd driver released on 2002-10-12 for WLAN AP with Linksys WPC11 cards. While moving between two APs it is observed that the number of times reassociation request comes is not constant, sometimes more than one reassociation request comes when we move the STA to new AP area. 

Though the new AP shows that the STA has associated with it , the STA shows the MAC address of the old AP for several seconds before showing the new APs MAC address. Is it ok to have multiple reassociation requests? How can we detect, at the hostap, that the STA is finally associated to it? 

The distance between two APs is approximately 40 feet . Are the multiple re-association requests due to this?

Please reply,

Regards,

Mohit Bajpai



---------------------------------
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021230/6382cd89/attachment.htm 


From li9  Mon Dec 30 07:16:29 2002
From: li9 (Min Li)
Date: Mon, 30 Dec 2002 10:16:29 -0500 (EST)
Subject: (no subject)
In-Reply-To: <20021230142848.68143.qmail@web41105.mail.yahoo.com>
Message-ID: <Pine.GSO.4.44.0212301014400.11984-100000@expert.ics.purdue.edu>

Hi, All,

In the monitor mode, the driver can redirect all the incoming packets to
the user space. How about the outgoing pacets? Can I also use the monitor
mode to redirect it to the user space? Thanks.

Min






From pzz  Sun Dec 29 04:16:22 2002
From: pzz (Alexander Pevzner)
Date: 29 Dec 2002 15:16:22 +0300
Subject: wds with both ap's associating to stations
References: <4.3.2.7.0.20021228180147.02f89f00@yeagerautomation.com>
Message-ID: <87adip9g15.fsf@toy.pzz.msk.ru>

Hello, Doug Yeager!

Sat, 28 Dec 2002 18:06:09 -0500 you wrote:

DY> following this example is great, but i want both AP's to associate to
DY> stations.  this example only has A associating.  is it o.k. to do a

AP doesn't associate anywhere. Station does association to AP.
Station may be associated to only one AP in a time.

DY> "brctl addif br0 wlan0" and "ifconfig wlan0 0.0.0.0" for B
DY> configuration also?  i try to do this and i start getting some errors
DY> when i try to ping from one station to another.  i don't know if the
DY> errors are supposed to be there or a bug.  any help would be great

What kind of errors? BTW, do you know, Linux ethernet bridge requires
about 30 seconds to initialize itself. 

--
        Wishes, Alexander Pevzner (pzz at pzz.msk.ru)





From doug  Mon Dec 30 07:32:38 2002
From: doug (Doug Yeager)
Date: Mon, 30 Dec 2002 10:32:38 -0500
Subject: wds with both ap's associating to stations
In-Reply-To: <87adip9g15.fsf@toy.pzz.msk.ru>
Message-ID: <000501c2b018$b510b570$b600a8c0@DOUG1>

Thx much,
All is working now.
Found a post on the messages I was getting.  The solution was to turn
off netfilter debug in the kernel.  All is working great and stations
can associate to either ap!

Thx again,
doug

-----Original Message-----
From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] On Behalf
Of Alexander Pevzner
Sent: Sunday, December 29, 2002 7:16 AM
To: hostap at shmoo.com
Subject: Re: wds with both ap's associating to stations

Hello, Doug Yeager!

Sat, 28 Dec 2002 18:06:09 -0500 you wrote:

DY> following this example is great, but i want both AP's to associate
to
DY> stations.  this example only has A associating.  is it o.k. to do a

AP doesn't associate anywhere. Station does association to AP.
Station may be associated to only one AP in a time.

DY> "brctl addif br0 wlan0" and "ifconfig wlan0 0.0.0.0" for B
DY> configuration also?  i try to do this and i start getting some
errors
DY> when i try to ping from one station to another.  i don't know if the
DY> errors are supposed to be there or a bug.  any help would be great

What kind of errors? BTW, do you know, Linux ethernet bridge requires
about 30 seconds to initialize itself. 

--
        Wishes, Alexander Pevzner (pzz at pzz.msk.ru)


_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap





From jasonb  Mon Dec 30 16:39:30 2002
From: jasonb (Jason Boxman)
Date: Mon, 30 Dec 2002 19:39:30 -0500 (EST)
Subject: (no subject)
In-Reply-To:      <Pine.GSO.4.44.0212301014400.11984-100000@expert.ics.purdue.edu>
References: <20021230142848.68143.qmail@web41105.mail.yahoo.com> 
     <Pine.GSO.4.44.0212301014400.11984-100000@expert.ics.purdue.edu>
Message-ID: <1625.209.208.68.56.1041295170.squirrel@rebecca.edseek.com>

Min Li said:

> Hi, All,
>
> In the monitor mode, the driver can redirect all the incoming packets to
> the user space. How about the outgoing pacets? Can I also use the monitor
> mode to redirect it to the user space? Thanks.

There shouldn't be any outgoing packets from a Prism card in monitor mode
afaik.

> Min
>




From mike  Tue Dec 31 09:19:41 2002
From: mike (Michael Shuler)
Date: Tue, 31 Dec 2002 11:19:41 -0600
Subject: Klogd messages
Message-ID: <000601c2b0f0$d15d7dc0$9600a8c0@oemcomputer>

This is what my log files contains on our test AP:
Apr 28 12:24:41 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate lowered to 55
Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate raised to 110
Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate lowered to 55
Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate raised to 110
Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate lowered to 55
Apr 28 12:24:43 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate raised to 110
Apr 28 12:24:43 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate lowered to 55
Apr 28 12:24:43 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate raised to 110
Apr 28 12:24:43 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate lowered to 55
Apr 28 12:24:44 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate raised to 110
Apr 28 12:24:44 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate lowered to 55
Apr 28 12:24:45 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate raised to 110
Apr 28 12:24:45 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate lowered to 55
Apr 28 12:24:45 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate raised to 110
Apr 28 12:24:46 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate lowered to 55
Apr 28 12:24:46 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate raised to 110
Apr 28 12:24:46 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate lowered to 55
Apr 28 12:24:47 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate raised to 110
Apr 28 12:24:48 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea TX
rate lowered to 55

As you can see off just one client having a less than optimal connection
it makes a big mess in my log files.  It also is wasting CPU cyles of
the driver by outputting a message that I don't really care about.  If
there any way to disable some or all debug messages...I still would like
to see the association/disassociation messages.

Also, how can I make the radio not switch back and forth between 11 and
5.5 so easily?  Is it possible to make the AP always stay at 11Mbps?

Mike





From ammirata  Tue Dec 31 14:09:52 2002
From: ammirata (Sergio M. Ammirata)
Date: Tue, 31 Dec 2002 17:09:52 -0500
Subject: Klogd messages
In-Reply-To: <000601c2b0f0$d15d7dc0$9600a8c0@oemcomputer>
Message-ID: <000001c2b119$5c6050f0$017ba8c0@ammirata.net>

I am also experiencing the same fluctuation between 5.5 and 11Mbit (not
as often though).

I do value the messages and would not want to see them removed though.

Sergio

> -----Original Message-----
> From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] On Behalf
Of
> Michael Shuler
> Sent: Tuesday, December 31, 2002 12:20 PM
> To: hostap at shmoo.com
> Subject: Klogd messages
> 
> This is what my log files contains on our test AP:
> Apr 28 12:24:41 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate lowered to 55
> Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate raised to 110
> Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate lowered to 55
> Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate raised to 110
> Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate lowered to 55
> Apr 28 12:24:43 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate raised to 110
> Apr 28 12:24:43 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate lowered to 55
> Apr 28 12:24:43 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate raised to 110
> Apr 28 12:24:43 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate lowered to 55
> Apr 28 12:24:44 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate raised to 110
> Apr 28 12:24:44 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate lowered to 55
> Apr 28 12:24:45 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate raised to 110
> Apr 28 12:24:45 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate lowered to 55
> Apr 28 12:24:45 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate raised to 110
> Apr 28 12:24:46 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate lowered to 55
> Apr 28 12:24:46 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate raised to 110
> Apr 28 12:24:46 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate lowered to 55
> Apr 28 12:24:47 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate raised to 110
> Apr 28 12:24:48 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
TX
> rate lowered to 55
> 
> As you can see off just one client having a less than optimal
connection
> it makes a big mess in my log files.  It also is wasting CPU cyles of
> the driver by outputting a message that I don't really care about.  If
> there any way to disable some or all debug messages...I still would
like
> to see the association/disassociation messages.
> 
> Also, how can I make the radio not switch back and forth between 11
and
> 5.5 so easily?  Is it possible to make the AP always stay at 11Mbps?
> 
> Mike
> 
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap





From pete  Tue Dec 31 16:42:31 2002
From: pete (Peter Buelow)
Date: Tue, 31 Dec 2002 18:42:31 -0600 (CST)
Subject: Klogd messages
In-Reply-To: <000001c2b119$5c6050f0$017ba8c0@ammirata.net>
References: <000601c2b0f0$d15d7dc0$9600a8c0@oemcomputer>
        <000001c2b119$5c6050f0$017ba8c0@ammirata.net>
Message-ID: <3820.66.58.20.179.1041381751.squirrel@westnelson.net>

Actually, it would be nice if these were in some other log. syslog getting
full of this is not useful (well, to me anyway), but the information from
hostap is. Currently, I'm cutting a pasting this stuff out cause I want to
parse through it from time to time, but other syslog stuff that is as
important or more important get drowned out too easily. Any chance this
could go into some sort of other log file in /var/log?

> I am also experiencing the same fluctuation between 5.5 and 11Mbit (not
> as often though).
>
> I do value the messages and would not want to see them removed though.
>
> Sergio
>
>> -----Original Message-----
>> From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] On Behalf
> Of
>> Michael Shuler
>> Sent: Tuesday, December 31, 2002 12:20 PM
>> To: hostap at shmoo.com
>> Subject: Klogd messages
>>
>> This is what my log files contains on our test AP:
>> Apr 28 12:24:41 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate lowered to 55
>> Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate raised to 110
>> Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate lowered to 55
>> Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate raised to 110
>> Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate lowered to 55
>> Apr 28 12:24:43 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate raised to 110
>> Apr 28 12:24:43 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate lowered to 55
>> Apr 28 12:24:43 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate raised to 110
>> Apr 28 12:24:43 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate lowered to 55
>> Apr 28 12:24:44 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate raised to 110
>> Apr 28 12:24:44 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate lowered to 55
>> Apr 28 12:24:45 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate raised to 110
>> Apr 28 12:24:45 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate lowered to 55
>> Apr 28 12:24:45 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate raised to 110
>> Apr 28 12:24:46 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate lowered to 55
>> Apr 28 12:24:46 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate raised to 110
>> Apr 28 12:24:46 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate lowered to 55
>> Apr 28 12:24:47 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate raised to 110
>> Apr 28 12:24:48 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate lowered to 55
>>
>> As you can see off just one client having a less than optimal
> connection
>> it makes a big mess in my log files.  It also is wasting CPU cyles of
>> the driver by outputting a message that I don't really care about.  If
>> there any way to disable some or all debug messages...I still would
> like
>> to see the association/disassociation messages.
>>
>> Also, how can I make the radio not switch back and forth between 11
> and
>> 5.5 so easily?  Is it possible to make the AP always stay at 11Mbps?
>>
>> Mike
>>
>>
>> _______________________________________________
>> HostAP mailing list
>> HostAP at shmoo.com
>> http://lists.shmoo.com/mailman/listinfo/hostap
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap


-- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety." Benjamin Franklin
--
Peter Buelow
pete at putzin.net





From jkmaline  Tue Dec 31 17:23:55 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 31 Dec 2002 17:23:55 -0800
Subject: multiple reassociation at HostAP
In-Reply-To: <20021230142848.68143.qmail@web41105.mail.yahoo.com>
References: <20021230142848.68143.qmail@web41105.mail.yahoo.com>
Message-ID: <20030101012355.GA1096@jm.kir.nu>

On Mon, Dec 30, 2002 at 06:28:48AM -0800, Mohit bajpai wrote:

> I am using the hostapd driver released on 2002-10-12 for WLAN AP with Linksys WPC11 cards. While moving between two APs it is observed that the number of times reassociation request comes is not constant, sometimes more than one reassociation request comes when we move the STA to new AP area. 

Do you mean that the station sends reassociation request multiple times
to the same (new) AP? This could indicate that the previous
reassociation failed for some reason (e.g., timeout in getting
reassociation reply for the request).
 
> Though the new AP shows that the STA has associated with it , the STA shows the MAC address of the old AP for several seconds before showing the new APs MAC address. Is it ok to have multiple reassociation requests? How can we detect, at the hostap, that the STA is finally associated to it? 

IEEE 802.11 specifies that station can have only one association at any
given time, so at least stations should not send reassociation to
multiple APs at the same time. It is OK to authenticate with multiple
APs. From the AP view point, the station has completed association when
it acknowledges the association reply from the AP. 2002-10-12 release
does not check for this ACK frame, but latest CVS version does.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Dec 31 17:24:02 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 31 Dec 2002 17:24:02 -0800
Subject: reassosciation request comes more than once!
In-Reply-To: <001e01c2adb3$9cd5be40$f009030a@mahindrabt.com>
References: <001e01c2adb3$9cd5be40$f009030a@mahindrabt.com>
Message-ID: <20030101012402.GB1096@jm.kir.nu>

On Fri, Dec 27, 2002 at 07:54:04PM +0530, Mohit Bajpai wrote:

>     I have been trying out IAPP implementation with  latest hostap driver released on 2002-10-12.  I am using the hostapd mode of the hostap driver.During testing the MOVE operation I found that when STA moves to new AP the new AP detects reassociation of STA more than once. could you please tell that whether this multiple detection of reassociating STA should happen or not because if it is so then it will send move signal more than once which does not seem to be correct.

If the station sends reassociation request multiple times, current
hostapd will report each reassociation as a new one. If this is not
desired, some kind of timer could be used to skip higher-level
processing of reassociations (the request frame itself needs to be
replied to, but there is probably no need to use, e.g., IAPP for each
reassociation that is happening within a short period of time.

-- 
Jouni Malinen                                            PGP id EFC895FA



