From jkm  Fri Oct 11 01:19:48 2002
From: jkm (Jouni Malinen)
Date: Fri, 11 Oct 2002 11:19:48 +0300
Subject: [HostAP] testing - please ignore
Message-ID: <20021011111948.A15431@ssh.com>

Just testing.. Please ignore.

-- 
Jouni Malinen



From jkmaline  Sat Oct 12 00:30:14 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Oct 2002 10:30:14 +0300
Subject: [HostAP] New Host AP mailing list
Message-ID: <20021012103014.A22201@jm.epitest.fi>

Thanks to Bruce Potter and the Shmoo Group we now have a new Host AP
mailing list. From now on, it is recommended to use the new list for new  
messages. The old list will remain functional for some time and I will
cc replies to old threads also to the new list. No subscription
information is moved automatically from the old list to the new, so you
will need to subscribe to the new list if you wish to receive messages
in the future.

The new list is hosted at lists.shmoo.com and the delivery address for    
messages to the list is hostap at shmoo.com. The list uses MailMan and an    
info page is at http://lists.shmoo.com/mailman/listinfo/hostap. This   
address includes subscription information and mailing list archive. 
Also the new list is configured to accept messages only from subscribed
addresses to limit the amount of spam and virus/worms getting through.

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Sat Oct 12 01:13:48 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Oct 2002 11:13:48 +0300
Subject: [HostAP] Re: link becomes very poor in hostapd mode
In-Reply-To: <3DA505F1.2015BBD9@mahindrabt.com>; from jharana@mahindrabt.com on Thu, Oct 10, 2002 at 10:15:37AM +0530
References: <3DA505F1.2015BBD9@mahindrabt.com>
Message-ID: <20021012111348.A23407@jm.epitest.fi>

On Thu, Oct 10, 2002 at 10:15:37AM +0530, Jharana Mehta wrote:

> I am using Linksys WPC11 cards for my hostap setup. The driver works
> really well in pure kernel mode, and even bridging and all works fine.
> but when i compile and start the driver in hostapd mode, i.e by doing
> make pccard EXTRACFLAGS etc. and compiling and starting the hostapd
> without 802.1x authentication, the link quality becomes really poor and
> ping requests return after as long as 7 secs!

That's odd.. There shouldn't be any differences in kernel and hostapd
management that would have this kind of effect on TX/RX or link
quality.. Do you get any error messages in kernel log ('dmesg')? Have
you tested this with only one station card or more than one? You could
check whether 'utils/hostap_diag -a wlan0' output or
/proc/net/hostap/wlan0/<STA hwaddr> have significant differences when
comparing driver and hostapd management code.

> Also, when i compiled the driver for PCI adapter, i.e hostap_plx, the
> link remains up for only a very short time, after which the iwconfig
> shows transmit power to be 0 db.

Which PLX adapter (which PCI id)? Which PC Card in the PLX adapter? Any
error messages in 'dmesg' output? You could also check
'utils/hostap_diag -a wlan0' output just after loading the driver (i.e.,
when the link is up) and after the problems start.

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Sat Oct 12 01:27:48 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Oct 2002 11:27:48 +0300
Subject: [HostAP] Re: a question
In-Reply-To: <200210100230.g9A2Ujb22807@mail.tju.edu.cn>; from lphao@tju.edu.cn on Thu, Oct 10, 2002 at 10:57:42AM +0800
References: <200210100230.g9A2Ujb22807@mail.tju.edu.cn>
Message-ID: <20021012112748.B23407@jm.epitest.fi>

On Thu, Oct 10, 2002 at 10:57:42AM +0800, hao wrote:

> 	I dump the tx frame header when the interrupt HFA384X_EV_TX is called,but I found that the seq number do not continuous increase; when the interrupt HFA384X_EV_TXEXC is called ,I dump the tx header and do not found the frame with same seq number. why(this kind of frame need retransmition)? otherwise,I dump the time stamp when the prism2_transmit is called and the HFA384X_EV_TX is called,Can the duration between them be considered as delay of this frame.

I'm not exactly sure that I understood what you are doing, but maybe
these clarifications could help you. Each TX frame from the host get
only one TX event. This will be either TX or TXExc depending on whether
the transmit was consider successful. If a unicast frame is
retransmitted, it will still get only one TX or TXExc event. Firmware
sets seq# and it should be unique for frames so you should not see the
same seq# in other TX frame.

If you would like to match TX/TXExc event to a transmitted frame, you
should use txfids. Transmit command records the txfid in
local->intransmitfid table and TX/TXExc should have matching txfid in
TXCOMPLFID register.

Time interval between prism2_transmit and matching TX is includes
possible retransmission attempts. In addition, it includes frame queuing
in the firmware code. In other words, this value would show how much
time was spent from the moment the frame was queued to the firmware to
the moment the frame was ACKed (or in case of broadcast/multicast frame
the moment it was sent). It cannot, e.g., be used to resolve how long
time it takes for a station to ACK one TX frame since this time interval
includes queueing and possible retransmissions.

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Sat Oct 12 01:37:14 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Oct 2002 11:37:14 +0300
Subject: [HostAP] Re: 802.1x Problems
In-Reply-To: <00f401c2701a$8b29aca0$468101d9@pcwks356>; from pymanju@miel.mot.com on Thu, Oct 10, 2002 at 10:34:41AM +0530
References: <20021010071323.B22238@jm.epitest.fi> <00f401c2701a$8b29aca0$468101d9@pcwks356>
Message-ID: <20021012113714.C23407@jm.epitest.fi>

On Thu, Oct 10, 2002 at 10:34:41AM +0530, Manjunathan PY wrote:

> What exactly you mean by "It sends a key pair both to station and AP" ?
> What does the Radius server send to station and AP, in what message does it
> do so?

To AP:

MS-MPPE-Send-Key and MS-MPPE-Recv-Key attributes in Access-Accept
message. These attributes are encrypted as specified in RFC 2548.
Authenticator uses send key to sign and recv key to encrypt the WEP key
to the station (when Authenticator generates the WEP keys).

To STA:

MPPE keys are derived from the secret (between Supplicant and AS)
generated during TLS exchange, so the keys are not send explicitly in
any message, but equal keys are derived both in STA and AS.

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Sat Oct 12 01:45:15 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Oct 2002 11:45:15 +0300
Subject: [HostAP] Re: Changing iwconfig parameters in C file
In-Reply-To: <Pine.SOL.4.33.0210061654170.20602-100000@acmex.gatech.edu>; from gte746m@mail.gatech.edu on Sun, Oct 06, 2002 at 04:55:01PM -0400
References: <Pine.SOL.4.33.0210061654170.20602-100000@acmex.gatech.edu>
Message-ID: <20021012114515.D23407@jm.epitest.fi>

On Sun, Oct 06, 2002 at 04:55:01PM -0400, Seng Oon Toh wrote:

> Anyone know how I can change iwconfig parameters from my own C program? Is
> there an API defined?

Sure.. the one iwconfig is using, i.e., wireless extensions ioctls.
Please check wireless tools source code. It includes iwlib that could
probably be used. Anyway, the ioctl use is quite simple and there are
also some examples in hostapd code on how to use these ioctls() without
any additional library.

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Sat Oct 12 01:53:41 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Oct 2002 11:53:41 +0300
Subject: [HostAP] Re: wireless to wired bridging on STA mode
In-Reply-To: <OMEALPIENAGADEEOHGBKOEDGCAAA.shlee@adams.gwu.ac.kr>; from shlee@adams.gwu.ac.kr on Mon, Oct 07, 2002 at 11:38:18AM +0900
References: <OMEALPIENAGADEEOHGBKOEDGCAAA.shlee@adams.gwu.ac.kr>
Message-ID: <20021012115341.E23407@jm.epitest.fi>

On Mon, Oct 07, 2002 at 11:38:18AM +0900, ?????? wrote:

> Has anyone found a way to get around wavelan not allowing anything but its own mac address?

Yes.

> (answer by Michael Renzmann (mrenzmann at compulan.de)) 
> Well, for 99% of computer users there will never be a way to get rid of this. For this function a special firmware is needed.

That is not the exact truth.. If you would like to use AP mode, you
would most probably need the special firmware. However, if you just want
to make a point-to-point link between two WaveLAN cards and, e.g.,
bridge two ethernet networks over this link, you could use WDS mode for
this. Current Host AP driver has support for this mode as 'iwconfig
wlan0 mode Repeater' (not really the best name for the mode, but anyway,
this is the WDS mode). If I remember correctly, this mode worked fine
with Prism2, Lucent/Orinoco/Agere, and Symbol -based cards.

In WDS mode you will need to setup p-t-p link between two cards (iwpriv
wlan0 wds_add <hwaddr>) and use wlan#wds# interfaces in the bridge
setup. This way you should be able to use Linux bridge code also with
WaveLAN cards. The WDS frames have four addresses and the transmitter
can thus use its own address since there is a separate address field for
the "original source".

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Sat Oct 12 01:55:28 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Oct 2002 11:55:28 +0300
Subject: [HostAP] Re: simple ques
In-Reply-To: <F68gZKOrzRUExF1zeCw00016130@hotmail.com>; from sharad_mittal12@hotmail.com on Mon, Oct 07, 2002 at 11:02:48AM -0400
References: <F68gZKOrzRUExF1zeCw00016130@hotmail.com>
Message-ID: <20021012115528.F23407@jm.epitest.fi>

On Mon, Oct 07, 2002 at 11:02:48AM -0400, Sharad Mittal wrote:

>    I was just beginning to understand wireless drivers. Can someone tell me 
> what does "BAP" refer to. It seems to be referring to the chipset but how?

BAP is Buffer Access Path, i.e., the method used to move buffers (TX/RX
frames, configuration data, etc.) between host system and the wlan card.

-- 
Jouni Malinen                                            PGP id EFC895FA




From proski  Sat Oct 12 01:59:08 2002
From: proski (Pavel Roskin)
Date: Sat, 12 Oct 2002 04:59:08 -0400 (EDT)
Subject: [HostAP] Re: New Host AP mailing list
In-Reply-To: <20021012103014.A22201@jm.epitest.fi>
Message-ID: <Pine.LNX.4.44.0210120452410.3298-100000@localhost.localdomain>

Hi, Jouni!

Thank you for setting up the new list!

Could you please disable adding that lame [HostAP] to the subject?  
Mailman provides enough hidden headers to facilitate sorting of messages
into folders.  If you don't disable [HostAP] in subject now, somebody will
use it and will complain if you decide to disable it later.

There are enough examples in other lists, when stupid mail clients turn
subjects into something like this:

Re: [lwlan-devel] RE: busy looping in interrupt context

-- 
Regards,
Pavel Roskin




From jkmaline  Sat Oct 12 03:37:32 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Oct 2002 13:37:32 +0300
Subject: [HostAP] Re: 0.7.6 plx card fixed
In-Reply-To: <001801c26d26$8d2d5b60$fa00a8c0@rex>; from kccheng@biblecrawler.com on Sun, Oct 06, 2002 at 06:53:02PM +0800
References: <20021004221403.A15357@jm.epitest.fi> <20021006093219.G14371@jm.epitest.fi> <001801c26d26$8d2d5b60$fa00a8c0@rex>
Message-ID: <20021012133732.A26535@jm.epitest.fi>

On Sun, Oct 06, 2002 at 06:53:02PM +0800, Ka Chun, Cheng wrote:

> the latest offical release couldn't start the card(kernel: wlan0: could not
> get own MAC address)  and I reported it a few weeks ago. the other day I
> downloaded from CVS and it worked!!

That's interesting.. I do not remember having changed anything that
could have any effect on this after 2002-09-12 release.

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Sat Oct 12 03:44:24 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Oct 2002 13:44:24 +0300
Subject: [HostAP] Re: mac address blocking question
In-Reply-To: <p05100300b9bdf1273532@[200.255.3.235]>; from lceglia@terenet.com.br on Mon, Sep 30, 2002 at 09:18:01AM -0300
References: <p05100300b9bdf1273532@[200.255.3.235]>
Message-ID: <20021012134424.B26535@jm.epitest.fi>

On Mon, Sep 30, 2002 at 09:18:01AM -0300, Luiz Felipe Ceglia wrote:

> I have the need to allow some devices only connected to the box's eth0 pass.

eth0?? That's the wired ethernet device, not wireless(?)

> I issued the following commands:
> 
> iwpriv wlan0 maccmd 1
> iwpriv wlan0 maccmd 4
> iwpriv wlan0 addmac 01:02:03:04:05:06

These seems to be correct, if you intend to kick out all associated
(wireless) stations and in the future allow only station with hwaddr
01:02:03:04:05:06 to authenticate in the future. If you had any
associated stations before issuing these commands, they should be
deauthenticated and no frames should be accepted from them.

> I can still ping the host I have connected to eth0

Ping from which host? If you are pinging from a station associated to
the wireless device (wlan0), it should not be able to ping any hosts in
eth0 after this (assuming you do not have another AP that would allow
this, etc.).

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Sat Oct 12 08:08:13 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Oct 2002 18:08:13 +0300
Subject: [HostAP] Prism2/2.5/3 Host AP - new release 2002-10-12
Message-ID: <20021012180813.A30651@jm.epitest.fi>

A new version of Prism2 Host AP driver was just released and it is now
available from http://hostap.epitest.fi/

2002-10-12

* added utils/hostap_diag tool for showing diagnostics information
  about wireless LAN card
  - moving debugging related code from kernel driver to user space
  - this replaces previously used
    /proc/net/hostap/wlan#/{rids,unknown_rids}
  - replaces utils/dump_mmi_dev0_status (hostap_diag -b wlan#)
* added configuration option for TX/RX antenna selection
  - prism2_param antsel_tx and antsel_rx
  - 0 = do not touch (default), 1 = use antenna diversity,
    2 = force AntSel Low, 3 = force AntSel High
* changed monitor mode configuration style
  - 'iwconfig wlan0 mode monitor' (this requires wireless tools
    versions 25 or newer) is now used to setup monitor mode
  - 'prism2_param wlan0 monitor_type <0/1>' configures which headers
    are included (0 = IEEE 802.11, 1 = Prism2 + IEEE 802.11)
  - old method 'iwpriv wlan0 monitor <2/3>' is now implemented as a
    wrapper for iwconfig mode command to provide backward compatibility
    (however, iwpriv command 'monitor' is now deprecated and it may be
    removed in the future versions)
* changed host_encrypt default in Host AP mode to be based on the
  station firmware version; f/w 1.4.9 seems to fix a bug that prevented
  firmware-based WEP encryption (although, decryption was working) to
  be used in Host AP mode; from now on, this can be configured with
  prism2_param also when using Host AP mode; the default is to use
  firmware-based encryption if f/w version is 1.4.9 or newer
* added new WDS frame options:
  - new prism2_param wds_type bitmap:
    bit0: 0 = use unicast RA/BSSID for broadcast/multicast frames to
      WDS link
      1 = use broadcast RA/BSSID for broadcast/multicast frames
          (Note! Prism2 firmware has limitations on this)
    bit1: AP client mode - if AP client mode is enabled and device is
      in Managed mode (i.e., associated to an AP), driver accepts
      4-addr WDS frames from current AP. In addition, outgoing
      frames that have a foreign source address in the Ethernet
      header are sent using 4-addr WDS frame to the AP. This allows
      station mode to perform layer 2 bridgeing. Please note, that
      due to firmware limitations Host AP in Master mode cannot
      operate with such station.
* fixed ap_bridge_packets to send broadcast/multicast packets back to
  wireless interface only in Master mode

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Sat Oct 12 08:19:21 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Oct 2002 18:19:21 +0300
Subject: [HostAP] Re: Retransmissions
In-Reply-To: <Pine.LNX.4.33.0210121014120.30569-100000@utz.cs.umd.edu>; from arun@cs.umd.edu on Sat, Oct 12, 2002 at 10:15:39AM -0400
References: <20021012112748.B23407@jm.epitest.fi> <Pine.LNX.4.33.0210121014120.30569-100000@utz.cs.umd.edu>
Message-ID: <20021012181921.A30893@jm.epitest.fi>

On Sat, Oct 12, 2002 at 10:15:39AM -0400, Arunchandar Vasan wrote:

> Is there anyway I can get the number of retransmissions a frame underwent 
> from  the driver ?

I'm not aware of such mechanism in the current firmware version. If this
were available, it would probably be stored in TX frame description that
can be read in TX event (i.e., successful transmit). TX desc has
retry_count field, but it is apparently not yet implemented.

Anyway, I modified the driver a bit to make it more clear where this
information would be available. hostap_hw.c now has a function,
prism2_tx_ev() that takes care of TX events. If prism2_param 'dump' is
set to have bit1 set (TX hdr dump), some fields from the TX descriptor
are shown in this function. Please note, that TX event is not used in
the default configuration; it can be enabled by defining
PRISM2_USE_TX_INTERRUPT (see hostap_config.h).

-- 
Jouni Malinen                                            PGP id EFC895FA




From Doug  Sat Oct 12 12:05:26 2002
From: Doug (Doug)
Date: Sat, 12 Oct 2002 12:05:26 -0700
Subject: Beacon Interval ?
Message-ID: <4.2.2.20021012120334.018563c8@pop.sbcglobal.net>

What should the beacon interval be set to. What is the default?

Thanks Doug




From gdead  Sat Oct 12 12:00:49 2002
From: gdead (Bruce Potter)
Date: Sat, 12 Oct 2002 15:00:49 -0400
Subject: [HostAP] Re: New Host AP mailing list
In-Reply-To: <Pine.LNX.4.44.0210120452410.3298-100000@localhost.localdomain>
Message-ID: <025e01c27221$b1471c70$a200a8c0@duffman>

Howdy,
The [Host-AP] prefix has been removed.  :)

later

bruce

> -----Original Message-----
> From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] 
> On Behalf Of Pavel Roskin
> Sent: Saturday, October 12, 2002 4:59 AM
> To: Jouni Malinen
> Cc: hostap at shmoo.com
> Subject: [HostAP] Re: New Host AP mailing list
> 
> 
> Hi, Jouni!
> 
> Thank you for setting up the new list!
> 
> Could you please disable adding that lame [HostAP] to the subject?  
> Mailman provides enough hidden headers to facilitate sorting 
> of messages into folders.  If you don't disable [HostAP] in 
> subject now, somebody will use it and will complain if you 
> decide to disable it later.
> 
> There are enough examples in other lists, when stupid mail 
> clients turn subjects into something like this:
> 
> Re: [lwlan-devel] RE: busy looping in interrupt context
> 
> -- 
> Regards,
> Pavel Roskin
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 





From gte746m  Sat Oct 12 12:42:10 2002
From: gte746m (Seng Oon Toh)
Date: Sat, 12 Oct 2002 15:42:10 -0400 (EDT)
Subject: Retransmissions
In-Reply-To: <20021012181921.A30893@jm.epitest.fi>
Message-ID: <Pine.SOL.4.33.0210121541160.3162-100000@acmez.gatech.edu>

How do I disable retransmissions, and wait for ACK in host AP? I'm trying
to transmit packets in monitor mode, the packets go out but it retransmits
a lot of times. I think its doing this because it can't hear the acks
while transmitting.

Thanks

Seng Oon Toh
Georgia Institute of Technology, Atlanta Georgia, 30332
Email: gte746m at prism.gatech.edu

On Sat, 12 Oct 2002, Jouni Malinen wrote:

> On Sat, Oct 12, 2002 at 10:15:39AM -0400, Arunchandar Vasan wrote:
>
> > Is there anyway I can get the number of retransmissions a frame underwent
> > from  the driver ?
>
> I'm not aware of such mechanism in the current firmware version. If this
> were available, it would probably be stored in TX frame description that
> can be read in TX event (i.e., successful transmit). TX desc has
> retry_count field, but it is apparently not yet implemented.
>
> Anyway, I modified the driver a bit to make it more clear where this
> information would be available. hostap_hw.c now has a function,
> prism2_tx_ev() that takes care of TX events. If prism2_param 'dump' is
> set to have bit1 set (TX hdr dump), some fields from the TX descriptor
> are shown in this function. Please note, that TX event is not used in
> the default configuration; it can be enabled by defining
> PRISM2_USE_TX_INTERRUPT (see hostap_config.h).
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>
>




From boavista54  Sat Oct 12 18:54:21 2002
From: boavista54 (Doug Bradford)
Date: Sat, 12 Oct 2002 18:54:21 -0700
Subject: Beacon Interval ?
Message-ID: <4.2.2.20021012185413.00af4dc8@mail.irdatacorp.com>

What should the beacon interval be set to. What is the default?

Thanks Doug 




From proski  Sat Oct 12 19:07:38 2002
From: proski (Pavel Roskin)
Date: Sat, 12 Oct 2002 22:07:38 -0400 (EDT)
Subject: OpenAP needs new maintainer?
Message-ID: <Pine.LNX.4.44.0210122147590.22368-100000@marabou.research.att.com>

Hello!

Sorry for writing to this list.  If there is a better place, please let me
know.

OpenAP project appears to be dead.  The mailing list stopped working on
September 17, the new messages to the list were not archived after
September 25.  Only one of the developers answered me in private saying
that he is too busy.  Two days ago the website went down.

The CVS still works (no wonder, it's on GNU), however, the code in CVS
doesn't work.  Essentially, there are many undocumented manual steps
required to build the image.  There are obvious bugs in some utilities,
that must have been fixed in the image, but the fixes never made it to
CVS.

This most obvious example is opening the flash image in update.c with the
flag O_RDWR, which fails on read-only filesystems.  It must have been
fixed in the image, or it would not work.  But it isn't in CVS.

File sramconfig is obviously needed to build the primary (i.e. SRAM) 
kernel, but it's not referenced in any script or document on CVS.  And the 
list goes on.

The fact is - the whole build system needs complete rewriting.  Somebody
should take over the maintenance.

I'm working on a new OpenAP implementation, with kernel PCMCIA, devfs,
really working build scripts, updated utilities, and of course, new
HostAP.  I'm very busy now and I don't have time to make a release or to
maintain it.  Don't even ask.

However, if somebody else wants to take over maintenance of OpenAP, please
let me know, and I'll send you what I have.  I made some fixes for the
kernel (devfs in MTD, crash in pcmcia), rewrote the perl script that
generates images (it won't ever tell you that you have -300kb free) and
made many other changes.

This is work in progress and I'm not going to support it in any form,
except explaining my changes to the person who takes over the maintenace 
of OpenAP.

-- 
Regards,
Pavel Roskin




From jkmaline  Sat Oct 12 22:15:06 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 13 Oct 2002 08:15:06 +0300
Subject: Beacon Interval ?
In-Reply-To: <4.2.2.20021012185413.00af4dc8@mail.irdatacorp.com>; from boavista54@sbcglobal.net on Sat, Oct 12, 2002 at 06:54:21PM -0700
References: <4.2.2.20021012185413.00af4dc8@mail.irdatacorp.com>
Message-ID: <20021013081506.B14125@jm.epitest.fi>

On Sat, Oct 12, 2002 at 06:54:21PM -0700, Doug Bradford wrote:

> What should the beacon interval be set to. What is the default?

Default is 100, i.e., ten beacons per second. With Host AP mode, the
most noticeable effect of beacon interval is latency in sending unicast
packets to power saving stations and broadcast/multicast packets in
general. I would set beacon interval depending on the environment where
the AP is operating.

If you have many stations using power saving, you might want to keep the
beacon interval quite small since larger interval adds latency to
AP->STA packets. Even without any stations using PS, Host AP mode seems
to often wait for next DTIM beacon frame before sending pending
broadcast/multicast frames. This might be an issue in some cases. On the
other hand, every beacon frame take a small portion of the maximum
bandwidth and using a larger beacon interval would save some bandwidth
for data frames. So, this will be a compromise between enlarged latency
and saved bandwidth. I would suggest experimenting with different values
since there is not really any one-value-fits-all solution for this.

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Sat Oct 12 22:24:19 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 13 Oct 2002 08:24:19 +0300
Subject: rids
In-Reply-To: <3DA687E1.60002@estudiant.upc.es>; from victor.aleo@estudiant.upc.es on Fri, Oct 11, 2002 at 10:12:17AM +0200
References: <3DA687E1.60002@estudiant.upc.es>
Message-ID: <20021013082419.C14125@jm.epitest.fi>

On Fri, Oct 11, 2002 at 10:12:17AM +0200, Victor Aleo wrote:

> I would like to know what exactly the file /proc/net/prism2/wlan#/rids 
> contains. It seems to me that is the information related to the MIBs 
> specified by the standard. Is that true?

That is a debug dump of all the known RIDS (FC?? being configurable
items and FD?? read-only info). Many of these do indeed map quite well
to MIBs.

Please note, that /proc/net/prism2/wlan#/rids is the old path to this
file, prism2 was changed to hostap in a newer version and the latest
release actually removed the whole file from the driver. The same
information is now available using user space program utils/hostap_diag.

> More precisely, I am interested in FD88 (by the way, what it means 
> FD88?) SCANRESULTSTABLE. I guess this is the APs that the STA has found 
> in the scanning process.

It is the RID number FD88 (0xfd88) and yes, this RID should have the
results of the last scan. However, it does not seem to be available
properly on all firmware versions so using ScanResults info frame in
host-based roaming mode might be better solution for getting the
scanning results.

> Can I request (e.g., SNMP request) from the AP to the associated STA 
> about this SCANRESULTSTABLE?

Sure you can request that ;-), but the station in question should have
some software running on the host system to reply to this.. Most
probably standards STAs do not have support for this. There is some kind
of protocol for asking the other end's signal quality and nick name
etc.. However, I haven't seen any standard describing this so I'm not
fully sure about the contents of the frames used for this query. Anyway,
I do not think they include full scanning results.

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Sat Oct 12 22:28:04 2002
From: jkmaline (Jouni Malinen)
Date: Sun, 13 Oct 2002 08:28:04 +0300
Subject: Retransmissions
In-Reply-To: <Pine.SOL.4.33.0210121541160.3162-100000@acmez.gatech.edu>; from gte746m@mail.gatech.edu on Sat, Oct 12, 2002 at 03:42:10PM -0400
References: <20021012181921.A30893@jm.epitest.fi> <Pine.SOL.4.33.0210121541160.3162-100000@acmez.gatech.edu>
Message-ID: <20021013082804.D14125@jm.epitest.fi>

On Sat, Oct 12, 2002 at 03:42:10PM -0400, Seng Oon Toh wrote:

> How do I disable retransmissions, and wait for ACK in host AP? I'm trying
> to transmit packets in monitor mode, the packets go out but it retransmits
> a lot of times. I think its doing this because it can't hear the acks
> while transmitting.

You can use 'iwconfig wlan0 retry 0' to remove retransmissions. I have
never tested this in monitor mode, so I do not know whether it does
exactly what is expected.. Anyway, the monitor mode is a testing mode
that disables many standard operations, so I wouldn't be that surprised
if there are some problems transmitting packets while in monitor mode.

-- 
Jouni Malinen                                            PGP id EFC895FA




From hostap  Mon Oct 14 03:29:44 2002
From: hostap (Robert Botha)
Date: Mon, 14 Oct 2002 12:29:44 +0200
Subject: Beacon Interval ?
In-Reply-To: <20021013081506.B14125@jm.epitest.fi>
References: <4.2.2.20021012185413.00af4dc8@mail.irdatacorp.com> <20021013081506.B14125@jm.epitest.fi>
Message-ID: <20021014102944.GA5966@flash.za.org>

Hi Jouni,

What's the size of this beacon, and how much bandwidth will it use up
with it's default setting. 
How much latency are we talking about (in ms)
Will this setting be usefull in PTP links (Ad-Hoc Mode)


Thanx,
-Robert.

On Sun, Oct 13, 2002 at 08:15:06AM +0300, Jouni Malinen wrote:
> On Sat, Oct 12, 2002 at 06:54:21PM -0700, Doug Bradford wrote:
> 
> > What should the beacon interval be set to. What is the default?
> 
> Default is 100, i.e., ten beacons per second. With Host AP mode, the
> most noticeable effect of beacon interval is latency in sending unicast
> packets to power saving stations and broadcast/multicast packets in
> general. I would set beacon interval depending on the environment where
> the AP is operating.
> 
> If you have many stations using power saving, you might want to keep the
> beacon interval quite small since larger interval adds latency to
> AP->STA packets. Even without any stations using PS, Host AP mode seems
> to often wait for next DTIM beacon frame before sending pending
> broadcast/multicast frames. This might be an issue in some cases. On the
> other hand, every beacon frame take a small portion of the maximum
> bandwidth and using a larger beacon interval would save some bandwidth
> for data frames. So, this will be a compromise between enlarged latency
> and saved bandwidth. I would suggest experimenting with different values
> since there is not really any one-value-fits-all solution for this.
> 
> -- 
> Jouni Malinen                                            PGP id EFC895FA
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 
> 

-- 
Robert Botha
jabber: flash at vitalclan.co.za




From jsnow  Mon Oct 14 13:56:03 2002
From: jsnow (Jim Snow)
Date: Mon, 14 Oct 2002 13:56:03 -0700 (PDT)
Subject: turning radio on and off without upsetting connections?
Message-ID: <Pine.SOL.3.96.1021014111946.18907A-100000@church.cse.ogi.edu>

I was wondering if there was some simple way to put a prism card into low
power mode from user space with hostap.  I'm attempting to write a
user-space quasi-token-ringish medium sharing algorithm to reduce
collisions and power consumption (at some cost to latency and bandwidth),
but to reduce power consumption I need a way to turn the card off for a
little while and then back on (without causing active tcp connections or
connection attempts to fail (just be delayed a little while) - thus
"ifconfig wlan0 down" is unacceptable, and the 802.11 power-save mode does
more than I'd like it to). 

-jim




From bruno  Mon Oct 14 14:04:10 2002
From: bruno (Bruno Lopes F. Cabral)
Date: Mon, 14 Oct 2002 18:04:10 -0300
Subject: 0.7.5 to 1.4.9 firmware upgrade??
Message-ID: <3DAB314A.8FF23BB0@openline.com.br>

Hi there

I have several USR2445 pccards, which are based on prism 
chipset with the following firmware info:

wlan0: NIC: id=0x8002 v1.0.0                                                    
wlan0: PRI: id=0x15 v0.3.0                                                      
wlan0: STA: id=0x1f v0.7.5

I'm using these cards with openap linux (on a USR2450
AP), hostap driver version 2002-05-19, kernel 2.4.17

hostap_cs: hostap_cs.c 0.0.0 2002-05-19 (SSH Communications Security Corp, Joun)
hostap_cs: (c) SSH Communications Security Corp <jkm at ssh.com>                   
hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f                         
hostap_cs: Registered netdevice wlan0                                           

I'd like to know if it is possible/recommended to upgrade 
them to a newer firmware (i.e. 1.4.9) or it would be 
better to stick with the one it has now. 

my goal is to use the firmware wep encription of 1.4.9 
because the  driver's wep make the unit run about 25% 
slower (this "beast" has a 486SX/33 running the system),
but only if it is safe to do so

thanks in advance for any hints/tips on this topic

Cheers, 
!3runo
from Brazil



From pedro.estrela  Mon Oct 14 17:37:16 2002
From: pedro.estrela (Pedro Estrela)
Date: Tue, 15 Oct 2002 01:37:16 +0100
Subject: 0.7.5 to 1.4.9 firmware upgrade??
References: <3DAB314A.8FF23BB0@openline.com.br>
Message-ID: <00a101c273e3$02f58350$bde116d5@pedropc>

Hello!

I've got the same problem, and i'm currently searching both the archives and
the developers websites for this information.

I have several compaq WL100 PCMCIA cards, based on Prism2 chipset (HFA3841,
NICID 0x8002). However, all the firmwares available at
http://www.netgate.com/support/prism_firmware are for the chipsets prism2.5
and prism3  (HFA3842, NICID 0x800A and higher).

I'm hoping that the firmware for the zoom card fixed by Alejandro Lamas
(http://hostap.epitest.fi/hostap/2002-08/1540.html) will work on the compaq
WL100 (and also WL200), as it is a prism2 card (HFA3841, NICID 0x8003)
(Alejandro: please confirm if you can).

To perform the actual flashing (tomorrow) I will be using the Intersil
windows utility (WinUpdate-0-5-1-0.exe) that is inside
(ftp://ftp.dlink.com/Wireless/DWL650/Firmware/dwl650_firmware_8c2.exe)  (see
http://hostap.epitest.fi/hostap/2002-07/1379.html)

Other option is to use the 1.3.4 firmware from netgear's MA401
(ftp://downloads.netgear.com/files/netgear1/MA401v200.zip) (see
http://hostap.epitest.fi/hostap/2002-07/1384.html)

As thus, i would ask the hostap users with ***prism2 chipset***, to confirm
both success and insucess experiences regarding the latest firmwares.

Thanks,
Pedro Estrela

----- Original Message -----
From: "Bruno Lopes F. Cabral" <bruno at openline.com.br>
To: <hostap at shmoo.com>
Sent: Monday, October 14, 2002 10:04 PM
Subject: 0.7.5 to 1.4.9 firmware upgrade??


> Hi there
>
> I have several USR2445 pccards, which are based on prism
> chipset with the following firmware info:
>
> wlan0: NIC: id=0x8002 v1.0.0
> wlan0: PRI: id=0x15 v0.3.0
> wlan0: STA: id=0x1f v0.7.5
>
> I'm using these cards with openap linux (on a USR2450
> AP), hostap driver version 2002-05-19, kernel 2.4.17
>
> hostap_cs: hostap_cs.c 0.0.0 2002-05-19 (SSH Communications Security Corp,
Joun)
> hostap_cs: (c) SSH Communications Security Corp <jkm at ssh.com>
> hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
> hostap_cs: Registered netdevice wlan0
>
> I'd like to know if it is possible/recommended to upgrade
> them to a newer firmware (i.e. 1.4.9) or it would be
> better to stick with the one it has now.
>






From jkmaline  Mon Oct 14 21:57:56 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 15 Oct 2002 07:57:56 +0300
Subject: No ESSID in beacon frame
In-Reply-To: <200210150156.28738.ml@blas.net>; from ml@blas.net on Tue, Oct 15, 2002 at 01:56:28AM +0200
References: <200210150156.28738.ml@blas.net>
Message-ID: <20021015075756.B15049@jm.epitest.fi>

On Tue, Oct 15, 2002 at 01:56:28AM +0200, Dominique Blas wrote:

> I didn't find any question about that in the archives.
> So I ask it. Sorry if already posted.

Search the archives for "hiding SSID" or "enhanced security".

> I'd like to know if Prism Chipset / fw offers the possibility to cancel ESSID 
> broadcast in beacon frames as Airnet can do it.

Yes, but ..

> If yes how to activate this feature through HostAP ?

.. it is not available in secondary (station) firmware. Only AP firmware
includes enhSecurity RID that can be used to configure SSID hiding from
beacon frames. Anyway, this is not really that much "enhanced" security.
SSID will still be available in probe requests and association
requests.. If there are any associated stations, it is trivial to send a
broadcast deauthentication frame and look the station associating
again..

-- 
Jouni Malinen                                            PGP id EFC895FA




From hostap  Mon Oct 14 22:55:11 2002
From: hostap (Robert Botha)
Date: Tue, 15 Oct 2002 07:55:11 +0200
Subject: 0.7.5 to 1.4.9 firmware upgrade??
In-Reply-To: <00a101c273e3$02f58350$bde116d5@pedropc>
References: <3DAB314A.8FF23BB0@openline.com.br> <00a101c273e3$02f58350$bde116d5@pedropc>
Message-ID: <20021015055511.GA7637@flash.za.org>

Why not first do a RAM download of the firmware to confirm if it's
working..if it doesn't..a simple power cycle will reset the card back to
its original firmware.

-Robert.

On Tue, Oct 15, 2002 at 01:37:16AM +0100, Pedro Estrela wrote:
> 
> Hello!
> 
> I've got the same problem, and i'm currently searching both the archives and
> the developers websites for this information.
> 
> I have several compaq WL100 PCMCIA cards, based on Prism2 chipset (HFA3841,
> NICID 0x8002). However, all the firmwares available at
> http://www.netgate.com/support/prism_firmware are for the chipsets prism2.5
> and prism3  (HFA3842, NICID 0x800A and higher).
> 
> I'm hoping that the firmware for the zoom card fixed by Alejandro Lamas
> (http://hostap.epitest.fi/hostap/2002-08/1540.html) will work on the compaq
> WL100 (and also WL200), as it is a prism2 card (HFA3841, NICID 0x8003)
> (Alejandro: please confirm if you can).
> 
> To perform the actual flashing (tomorrow) I will be using the Intersil
> windows utility (WinUpdate-0-5-1-0.exe) that is inside
> (ftp://ftp.dlink.com/Wireless/DWL650/Firmware/dwl650_firmware_8c2.exe)  (see
> http://hostap.epitest.fi/hostap/2002-07/1379.html)
> 
> Other option is to use the 1.3.4 firmware from netgear's MA401
> (ftp://downloads.netgear.com/files/netgear1/MA401v200.zip) (see
> http://hostap.epitest.fi/hostap/2002-07/1384.html)
> 
> As thus, i would ask the hostap users with ***prism2 chipset***, to confirm
> both success and insucess experiences regarding the latest firmwares.
> 
> Thanks,
> Pedro Estrela
> 
> ----- Original Message -----
> From: "Bruno Lopes F. Cabral" <bruno at openline.com.br>
> To: <hostap at shmoo.com>
> Sent: Monday, October 14, 2002 10:04 PM
> Subject: 0.7.5 to 1.4.9 firmware upgrade??
> 
> 
> > Hi there
> >
> > I have several USR2445 pccards, which are based on prism
> > chipset with the following firmware info:
> >
> > wlan0: NIC: id=0x8002 v1.0.0
> > wlan0: PRI: id=0x15 v0.3.0
> > wlan0: STA: id=0x1f v0.7.5
> >
> > I'm using these cards with openap linux (on a USR2450
> > AP), hostap driver version 2002-05-19, kernel 2.4.17
> >
> > hostap_cs: hostap_cs.c 0.0.0 2002-05-19 (SSH Communications Security Corp,
> Joun)
> > hostap_cs: (c) SSH Communications Security Corp <jkm at ssh.com>
> > hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
> > hostap_cs: Registered netdevice wlan0
> >
> > I'd like to know if it is possible/recommended to upgrade
> > them to a newer firmware (i.e. 1.4.9) or it would be
> > better to stick with the one it has now.
> >
> 
> 
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 
> 

-- 
Robert Botha
jabber: flash at vitalclan.co.za




From hostap  Mon Oct 14 22:58:49 2002
From: hostap (Robert Botha)
Date: Tue, 15 Oct 2002 07:58:49 +0200
Subject: AP Bridging
In-Reply-To: <001b01c273f6$29e7c780$0100000a@guido>
References: <001b01c273f6$29e7c780$0100000a@guido>
Message-ID: <20021015055849.GB7637@flash.za.org>

You're prolly looking for a WDS link between the two APs and running
Bridged mode on your linux box.

On Mon, Oct 14, 2002 at 11:54:11PM -0300, Guido Augustowski wrote:
> Hi! I would like to know if there is any method so I can make two wireless cards on AP mode to be connected, so all the clients can see each other, although they may be connected to two different AP?s. I know that I can connect them through Internet, with a VPN, but I mean a wireless connection.
> 
> Thanks in advance and sorry for my bad English.
> 
> Guido
> 
> P.S.: how can I subscribe myself to the list? Actually I read the mails on the hostap web, but I would like to receive them by mail.
> 
> ------------------------------------------------------------
> Guido H. Augustowski
>     guidoa at fibertel.com.ar
>     gaugustowski at unimoron.edu.ar
>     Cel.: 15-4446-4100
-- 
Robert Botha
jabber: flash at vitalclan.co.za




From hostap  Mon Oct 14 23:09:46 2002
From: hostap (Robert Botha)
Date: Tue, 15 Oct 2002 08:09:46 +0200
Subject: 0.7.5 to 1.4.9 firmware upgrade??
In-Reply-To: <3DABAECE.4080602@palaver.net>
References: <3DAB314A.8FF23BB0@openline.com.br> <00a101c273e3$02f58350$bde116d5@pedropc> <20021015055511.GA7637@flash.za.org> <3DABAECE.4080602@palaver.net>
Message-ID: <20021015060946.GC7637@flash.za.org>

in the hostap/utils dir there's a prism2_srec.c file.
just compile it by typing make in the utils dir
and then run ./prism2_srec -r wlan0 firmware.hex


On Tue, Oct 15, 2002 at 12:59:42AM -0500, Brian Capouch wrote:
> Robert Botha wrote:> Why not first do a RAM download of the firmware to 
> confirm if it's
> >working..if it doesn't..a simple power cycle will reset the card back to
> >its original firmware.
> >
> >-Robert.
> >
> 
> How?
> 
> B.
> 
> 
> 
> 

-- 
Robert Botha
jabber: flash at vitalclan.co.za




From jasonb  Tue Oct 15 00:07:30 2002
From: jasonb (Jason Boxman)
Date: Tue, 15 Oct 2002 03:07:30 -0400
Subject: Fw: 0.7.5 to 1.4.9 firmware upgrade??
In-Reply-To: <003e01c27413$1791d8b0$bde116d5@pedropc>
References: <003e01c27413$1791d8b0$bde116d5@pedropc>
Message-ID: <200210150307.30217.jasonb@edseek.com>

On Tuesday 15 October 2002 02:21 am, Pedro Estrela wrote:
> For HostAp users that didn't change to the new mailing list (yet):

I use PRI 1.0.7 and STA 1.3.5 without any issues.  WEP will be done in 
software, however, unless you're running 1.4.9 or manually turn on firmware 
based encryption.  It's off by default < 1.4.9 because it was buggy.

> ----- Original Message -----
> From: "Pedro Estrela" <pedro.estrela at inesc.pt>
> Sent: Tuesday, October 15, 2002 1:37 AM
> Subject: Re: 0.7.5 to 1.4.9 firmware upgrade??
>
> > Hello!
> >
> > I've got the same problem, and i'm currently searching both the archives
>
> and
>
> > the developers websites for this information.
> >
> > I have several compaq WL100 PCMCIA cards, based on Prism2 chipset
>
> (HFA3841,
>
> > NICID 0x8002). However, all the firmwares available at
> > http://www.netgate.com/support/prism_firmware are for the chipsets
>
> prism2.5
>
> > and prism3  (HFA3842, NICID 0x800A and higher).
> >
> > I'm hoping that the firmware for the zoom card fixed by Alejandro Lamas
> > (http://hostap.epitest.fi/hostap/2002-08/1540.html) will work on the
>
> compaq
>
> > WL100 (and also WL200), as it is a prism2 card (HFA3841, NICID 0x8003)
> > (Alejandro: please confirm if you can).
> >
> > To perform the actual flashing (tomorrow) I will be using the Intersil
> > windows utility (WinUpdate-0-5-1-0.exe) that is inside
> > (ftp://ftp.dlink.com/Wireless/DWL650/Firmware/dwl650_firmware_8c2.exe)
>
> (see
>
> > http://hostap.epitest.fi/hostap/2002-07/1379.html)
> >
> > Other option is to use the 1.3.4 firmware from netgear's MA401
> > (ftp://downloads.netgear.com/files/netgear1/MA401v200.zip) (see
> > http://hostap.epitest.fi/hostap/2002-07/1384.html)
> >
> > As thus, i would ask the hostap users with ***prism2 chipset***, to
>
> confirm
>
> > both success and insucess experiences regarding the latest firmwares.
> >
> > Thanks,
> > Pedro Estrela
> >
<snip>

-- 

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





From jkmaline  Tue Oct 15 01:23:36 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 15 Oct 2002 11:23:36 +0300
Subject: 0.7.5 to 1.4.9 firmware upgrade??
In-Reply-To: <3DAB314A.8FF23BB0@openline.com.br>; from bruno@openline.com.br on Mon, Oct 14, 2002 at 06:04:10PM -0300
References: <3DAB314A.8FF23BB0@openline.com.br>
Message-ID: <20021015112336.A17572@jm.epitest.fi>

On Mon, Oct 14, 2002 at 06:04:10PM -0300, Bruno Lopes F. Cabral wrote:

> I'd like to know if it is possible/recommended to upgrade 
> them to a newer firmware (i.e. 1.4.9) or it would be 
> better to stick with the one it has now. 

If it isn't broken, why fix it.. I haven't seen 1.4.9 f/w for old Prism2
cards (HFA3841). The latest version I have tested with such card is
1.3.4. Newer images might be available, but it might require some
searching.

> my goal is to use the firmware wep encription of 1.4.9 
> because the  driver's wep make the unit run about 25% 
> slower (this "beast" has a 486SX/33 running the system),
> but only if it is safe to do so

Are you sure that the wlan card would be any better in WEP processing?
Quite many of the older Prism2 cards have quite poor WEP performance
(throughput dropping from ca. 5.5 Mbps to 2.5 Mbps when enabling WEP)..
You might like to first confirm that you can get better results by
testing WEP e.g. in ad-hoc mode.

If the card-based WEP is fast enough and you manage to find 1.4.9 f/w
image for your card, remember also to upgrade Host AP driver since the
older versions were hard coded to use host-based WEP in Master mode no
matter what f/w version was used.

-- 
Jouni Malinen                                            PGP id EFC895FA




From martin.polak  Tue Oct 15 02:51:04 2002
From: martin.polak (Martin Polak)
Date: Tue, 15 Oct 2002 11:51:04 +0200
Subject: 0.7.5 to 1.4.9 firmware upgrade??
References: <3DAB314A.8FF23BB0@openline.com.br> <00a101c273e3$02f58350$bde116d5@pedropc>
Message-ID: <3DABE508.5060302@liwest.at>

Pedro Estrela schrieb:
> 
> I'm hoping that the firmware for the zoom card fixed by Alejandro Lamas
> (http://hostap.epitest.fi/hostap/2002-08/1540.html) will work on the compaq
> WL100 (and also WL200), as it is a prism2 card (HFA3841, NICID 0x8003)
> (Alejandro: please confirm if you can).

I've tried to use this firmware on my Netgear MA401 by downloading it with:
/prism2_srec -r eth2 01-S1010409.HEX

but it stated, that this file was no downloadable firmware, and flashing 
it right down without trying seem a bit risky to me.
Any suggestions?

> 
> To perform the actual flashing (tomorrow) I will be using the Intersil
> windows utility (WinUpdate-0-5-1-0.exe) that is inside
> (ftp://ftp.dlink.com/Wireless/DWL650/Firmware/dwl650_firmware_8c2.exe)  (see
> http://hostap.epitest.fi/hostap/2002-07/1379.html)

Please report your results!

> 
> Other option is to use the 1.3.4 firmware from netgear's MA401
> (ftp://downloads.netgear.com/files/netgear1/MA401v200.zip) (see
> http://hostap.epitest.fi/hostap/2002-07/1384.html)

This wouldn't make any big deal (e.g. firmwarebased WEP) I  believe?

I also could verify, that als 1.4.9 files I found so far, need a nic-id 
of 800A and greater :-(


Martin Polak




From hostap  Tue Oct 15 03:34:03 2002
From: hostap (Robert Botha)
Date: Tue, 15 Oct 2002 12:34:03 +0200
Subject: 0.7.5 to 1.4.9 firmware upgrade??
In-Reply-To: <3DABE508.5060302@liwest.at>
References: <3DAB314A.8FF23BB0@openline.com.br> <00a101c273e3$02f58350$bde116d5@pedropc> <3DABE508.5060302@liwest.at>
Message-ID: <20021015103403.GD7637@flash.za.org>

To upload firmware into RAM, you must use the RAM based firmware..in the
file on netgear there's 2 versions of the firware if I remember
correctly..one is flash based other is RAM based

-Robert

On Tue, Oct 15, 2002 at 11:51:04AM +0200, Martin Polak wrote:
> Pedro Estrela schrieb:
> >
> >I'm hoping that the firmware for the zoom card fixed by Alejandro Lamas
> >(http://hostap.epitest.fi/hostap/2002-08/1540.html) will work on the compaq
> >WL100 (and also WL200), as it is a prism2 card (HFA3841, NICID 0x8003)
> >(Alejandro: please confirm if you can).
> 
> I've tried to use this firmware on my Netgear MA401 by downloading it with:
> /prism2_srec -r eth2 01-S1010409.HEX
> 
> but it stated, that this file was no downloadable firmware, and flashing 
> it right down without trying seem a bit risky to me.
> Any suggestions?
> 
> >
> >To perform the actual flashing (tomorrow) I will be using the Intersil
> >windows utility (WinUpdate-0-5-1-0.exe) that is inside
> >(ftp://ftp.dlink.com/Wireless/DWL650/Firmware/dwl650_firmware_8c2.exe)  
> >(see
> >http://hostap.epitest.fi/hostap/2002-07/1379.html)
> 
> Please report your results!
> 
> >
> >Other option is to use the 1.3.4 firmware from netgear's MA401
> >(ftp://downloads.netgear.com/files/netgear1/MA401v200.zip) (see
> >http://hostap.epitest.fi/hostap/2002-07/1384.html)
> 
> This wouldn't make any big deal (e.g. firmwarebased WEP) I  believe?
> 
> I also could verify, that als 1.4.9 files I found so far, need a nic-id 
> of 800A and greater :-(
> 
> 
> Martin Polak
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 
> 

-- 
Robert Botha
jabber: flash at vitalclan.co.za




From martin.polak  Tue Oct 15 04:02:53 2002
From: martin.polak (Martin Polak)
Date: Tue, 15 Oct 2002 13:02:53 +0200
Subject: 0.7.5 to 1.4.9 firmware upgrade??
References: <3DAB314A.8FF23BB0@openline.com.br> <00a101c273e3$02f58350$bde116d5@pedropc> <3DABE508.5060302@liwest.at> <20021015103403.GD7637@flash.za.org>
Message-ID: <3DABF5DD.9080503@liwest.at>

Robert Botha schrieb:
> To upload firmware into RAM, you must use the RAM based firmware..in the
> file on netgear there's 2 versions of the firware if I remember
> correctly..one is flash based other is RAM based
> 
> -Robert
> 

Yes I know, but Netgear only has a flashable 1.3.4  version
and Netgate has RAM and Flash versions of 1.4.9, but only working
on NIC > 800a

Martin





From hostap  Tue Oct 15 04:09:04 2002
From: hostap (Robert Botha)
Date: Tue, 15 Oct 2002 13:09:04 +0200
Subject: 0.7.5 to 1.4.9 firmware upgrade??
In-Reply-To: <3DABF5DD.9080503@liwest.at>
References: <3DAB314A.8FF23BB0@openline.com.br> <00a101c273e3$02f58350$bde116d5@pedropc> <3DABE508.5060302@liwest.at> <20021015103403.GD7637@flash.za.org> <3DABF5DD.9080503@liwest.at>
Message-ID: <20021015110904.GG7637@flash.za.org>

Oops...my bad :)

That sucks :(

On Tue, Oct 15, 2002 at 01:02:53PM +0200, Martin Polak wrote:
> Robert Botha schrieb:
> >To upload firmware into RAM, you must use the RAM based firmware..in the
> >file on netgear there's 2 versions of the firware if I remember
> >correctly..one is flash based other is RAM based
> >
> >-Robert
> >
> 
> Yes I know, but Netgear only has a flashable 1.3.4  version
> and Netgate has RAM and Flash versions of 1.4.9, but only working
> on NIC > 800a
> 
> Martin
> 
> 
> 
> 

-- 
Robert Botha
jabber: flash at vitalclan.co.za




From pedro.estrela  Tue Oct 15 04:52:21 2002
From: pedro.estrela (Pedro Estrela)
Date: Tue, 15 Oct 2002 12:52:21 +0100
Subject: 0.7.5 to 1.4.9 firmware upgrade??
References: <3DAB314A.8FF23BB0@openline.com.br> <20021015112336.A17572@jm.epitest.fi>
Message-ID: <004f01c27441$51d476d0$e5e116d5@pedropc>

> > I'd like to know if it is possible/recommended to upgrade
> > them to a newer firmware (i.e. 1.4.9) or it would be
> > better to stick with the one it has now.
>
> If it isn't broken, why fix it.. I haven't seen 1.4.9 f/w for old Prism2
> cards (HFA3841). The latest version I have tested with such card is
> 1.3.4. Newer images might be available, but it might require some
> searching.

In my case, I'm only trying the latest firmware to test all possibilities
before asking the list of my __real__ prism2 problem.
Currently, with secondary 0.8.0 firmware (the most recent that compaq
provides), I'm getting a massive amount of INFDROP events, under very high
load conditions that I test IP DiffServ Quality of Service Traffic Control
in 802.11 Downstream. (this traffic is generated in UDP, creating much more
traffic than a flood ping).
Also, related to this problem, when these continous INFDROP events happen, I
can't get new stations associated to the AP, as the ASSOC frame doesn't seem
to get transmitted. This causes the station to send ASSOC frame every X
seconds in a loop. Unfortunatelly, I also need Associations under these very
high loads, to test both 802.11 handover and IP level handover (check
http://wuarchive.wustl.edu/doc/internet-drafts/draft-estrela-timip-00.txt.Z
or http://tenet.knu.ac.kr/research/seminar/jwkim_020712.ppt)

However, i'm trying the latest firmwares for my old PCMCIA cards, to check
if the situation improves before i try to rate-limit/packet-limit
transmissions in the driver.

Pedro Estrela




From rmiano  Tue Oct 15 09:13:22 2002
From: rmiano (Robert Miano)
Date: Tue, 15 Oct 2002 18:13:22 +0200
Subject: Firmware STA 1.5.4, R1010504.HEX
Message-ID: <3DAC3EA2.7070705@gmx.net>

Hi,

I just noticed that running the most recent Windows driver from
Intersil (ISL3PRDSUIT-EXE_WIN_(2-0-7).exe) downloads version STA 1.5.4
onto my COMPAQ WL100.

Now I wonder if there's a way to save the card's RAM into a hex file
for use with "prism2_srec -r" under Linux.

According to Intersil's WinUpdate, the filenames are as follows:

Primary: 0.3.0 P40003C0.HEX
Station: 1.5.4 R1010504.HEX

Maybe there's somebody who has the latter?

Thanks,

R.





From hyrax  Tue Oct 15 09:22:44 2002
From: hyrax (Scott Stapleton)
Date: Wed, 16 Oct 2002 00:22:44 +0800
Subject: WL200 + HostAP Problem
Message-ID: <000101c27467$18229bd0$03143c0a@hyrax>

Hi,

I'm having trouble getting my WL200 working with HostAP.

This is running on 2.4.18, pcmcia 3.2.1 and the latest HostAP.

I have read WL200 posts from the archive, WL200 + HostAP guides and
various other googled material, but cannot find a solution.

Following one of the guides, I recompiled without pcmcia. I then copied
hostap into pcmcia-cs. Installed pcmcia-cs, which seemed to go to plan.
Apon reboot, I was greeted with one loud beep and one softer. I'm told
the softer one is bad.

Dmesg returns these relevant lines:
______________________________________________________

Linux PCMCIA Card Services 3.2.1
  kernel build: 2.4.18-14custom #1 Tue Oct 15 12:06:41 WST 2002
  options:  [pci] [cardbus] [apm]
Intel ISA/PCI/CardBus PCIC probe:
PCI: Found IRQ 12 for device 00:10.0
  Cirrus PD6729 rev 00 PCI-to-PCMCIA at slot 00:10, port 0xe800
    host opts [0]: [ring] [pci irq 12] [1/5/0] [1/20/0]
    host opts [1]: [ring] [pci irq 12] [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: hostap_cs.c 0.0.0 2002-09-12 (SSH Communications Security
Corp, Jouni Malinen)
______________________________________________________



It recognises the CL bridge, but doesn't seem to see the PCMCIA card
on-board.

/var/log/messages returns these relevant lines:
______________________________________________________

Oct 16 00:07:35 thornlie cardmgr[504]: watching 2 sockets
Oct 16 00:07:35 thornlie pcmcia: cardmgr[504]: watching 2 sockets
Oct 16 00:07:36 thornlie cardmgr[505]: starting, version is 3.2.1
Oct 16 00:07:36 thornlie cardmgr[505]: socket 0: Compaq WL200
Oct 16 00:07:36 thornlie cardmgr[505]: executing: 'modprobe hostap_cs'
Oct 16 00:07:37 thornlie cardmgr[505]: bind 'hostap_cs' to socket 0
failed: Operation not permitted
_________________________________________________________


I have tried adding the following lines to pcmcia
PCIC_OPTS='irq_mode=1' 
PCIC_OPTS='irq_mode=1 irq_list=0'
PCIC_OPTS='irq_mode=1 irq_list=0 extra_sockets=1'

None seemed to help.

Can someone give me an idea as to my problem?

Regards,
Scott




From hyrax  Tue Oct 15 09:33:50 2002
From: hyrax (Scott Stapleton)
Date: Wed, 16 Oct 2002 00:33:50 +0800
Subject: WL200 + HostAP Problem
In-Reply-To: <000101c27467$18229bd0$03143c0a@hyrax>
Message-ID: <000601c27468$a5940fc0$03143c0a@hyrax>

<snip>
 
> Hi,
> 
> I'm having trouble getting my WL200 working with HostAP.
> 
> This is running on 2.4.18, pcmcia 3.2.1 and the latest HostAP.
> 
> I have read WL200 posts from the archive, WL200 + HostAP 
> guides and various other googled material, but cannot find a solution.
> 
> Following one of the guides, I recompiled without pcmcia. I 
> then copied hostap into pcmcia-cs. Installed pcmcia-cs, which 
> seemed to go to plan. Apon reboot, I was greeted with one 
> loud beep and one softer. I'm told the softer one is bad.
 
<snip>

One other thing I forgot to mention. Would the firmware version cause
this sort of problem. I plan on updating the f/w, but would like to get
her up and running first ( assuming f/w verison isn't the problem )

... Scott




From lyosha-hostap  Tue Oct 15 09:45:04 2002
From: lyosha-hostap (Alexey Marinichev)
Date: Tue, 15 Oct 2002 09:45:04 -0700
Subject: suspend/resume problems
Message-ID: <20021015164504.GB2409@lyosha.no-ip.org>

Hello,

I have a Proxim card which works fine with AP drivers.  I remember I was
able to do suspend/resume just fine, but since Sept. 12 version resume
doesn't work anymore.  Is this a known problem?  Should I send logs or
something?

Thanks,

	--Lyosha



From pizza  Tue Oct 15 09:40:10 2002
From: pizza (Stuffed Crust)
Date: Tue, 15 Oct 2002 12:40:10 -0400
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <3DAC3EA2.7070705@gmx.net>
References: <3DAC3EA2.7070705@gmx.net>
Message-ID: <20021015164010.GB13989@shaftnet.org>

On Tue, Oct 15, 2002 at 06:13:22PM +0200, Robert Miano wrote:
> I just noticed that running the most recent Windows driver from
> Intersil (ISL3PRDSUIT-EXE_WIN_(2-0-7).exe) downloads version STA 1.5.4
> onto my COMPAQ WL100.

Actually, the current release is 2.0.9, including STA 1.5.6.  But
Intersil seems to have um, difficulties in keeping their various web
sites up to date.   

1.5.4 is fairly solid, unless you like to issue scan requests and end
up locking up the card about half the time.    1.5.6 fixed that.
 
 - Pizza
-- 
Solomon Peachy                                   pizza at f*cktheusers.org
I'm not broke, but I'm badly bent.                         ICQ #1318344
Patience comes to those who wait.                         Melbourne, FL
               Quidquid latine dictum sit, altum viditur
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20021015/08d126ec/attachment.pgp 


From jasonb  Tue Oct 15 12:52:59 2002
From: jasonb (Jason Boxman)
Date: Tue, 15 Oct 2002 15:52:59 -0400
Subject: WL200 + HostAP Problem
In-Reply-To: <000601c27468$a5940fc0$03143c0a@hyrax>
References: <000601c27468$a5940fc0$03143c0a@hyrax>
Message-ID: <200210151552.59396.jasonb@edseek.com>

On Tuesday 15 October 2002 12:33 pm, Scott Stapleton wrote:
> <snip>
>
<snip>
> One other thing I forgot to mention. Would the firmware version cause
> this sort of problem. I plan on updating the f/w, but would like to get
> her up and running first ( assuming f/w verison isn't the problem )

Which firmware version is it?  I didn't notice a version in the previous post?  
You didn't include most of the HostAP initialization output.

> ... Scott
>

-- 

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





From proski  Tue Oct 15 12:53:48 2002
From: proski (Pavel Roskin)
Date: Tue, 15 Oct 2002 15:53:48 -0400 (EDT)
Subject: [PATCH] Support for DESTDIR, cp -f
Message-ID: <Pine.LNX.4.44.0210151525340.9421-100000@marabou.research.att.com>

Hello!

I'm working on the new forked version of OpenAP.  The idea is not just do
something that works, but something that can be reliably rebuilt by every
user from the source by the simple "make all" without suid mknod or
anything like that.  I'm trying to use the latest software and feed the
necessary patches back to the developers.  Below is one of such patches.

This patch makes it possible to install HostAP to a "staging area", i.e.  
prepend some path before every installed file.  Most software (and all
software using Automake) calls this variable DESTDIR, so that was the
obvious choice.

I also could not ignore the fact that "cp" is used without "-f".  Note
that cp without "-f" can ask questions.  It is not guaranteed to be
non-interactive.  On some systems, "cp" is an alias to "cp -i" for root,
which explicitly means to be intaractive.  I have repaced "cp" with "cp
-f" in the top-level Makefile.

The patch is against CVS version of HostAP.

==============================================
--- Makefile
+++ Makefile
@@ -11,6 +11,9 @@
 # Leave this blank for kernel-tree PCMCIA compilations (CONFIG_PCMCIA):
 PCMCIA_PATH=
 
+# This path will be prepended to every installed file
+DESTDIR=
+
 CC=gcc
 CFLAGS=-O2 -D__KERNEL__ -DMODULE -Wall -c $(EXTRA_CFLAGS)
 
@@ -20,7 +23,7 @@
 	else uname -r; fi)
 KERNELVER := $(shell echo "$(KERNELRELEASE)" | \
 	sed "s/\([0-9]*\.[0-9]*\.[0-9]*\).*/\1/")
-MODPATH := /lib/modules/$(KERNELRELEASE)
+MODPATH := $(DESTDIR)/lib/modules/$(KERNELRELEASE)
 MODULE_CS := hostap_cs.o
 MODULE_PLX := hostap_plx.o
 MODULE_PCI := hostap_pci.o
@@ -145,36 +148,38 @@
 install_hostap: $(MSRC)/hostap.o
 	@echo "Installing hostap.o to $(MODPATH_PCI)"
 	mkdir -p $(MODPATH_PCI)
-	cp $(MSRC)/hostap.o $(MODPATH_PCI)
+	cp -f $(MSRC)/hostap.o $(MODPATH_PCI)
 
 install_crypt: $(MSRC)/hostap_crypt.o $(MSRC)/hostap_crypt_wep.o
 	@echo "Installing hostap_crypt*.o to $(MODPATH_PCI)"
 	mkdir -p $(MODPATH_PCI)
-	cp $(MSRC)/hostap_crypt*.o $(MODPATH_PCI)
+	cp -f $(MSRC)/hostap_crypt*.o $(MODPATH_PCI)
 
 install_pccard: install_check install_crypt install_hostap
 	@echo "Installing $(MODULE_CS) to $(MODPATH_CS)"
 	mkdir -p $(MODPATH_CS)
-	cp $(MSRC)/$(MODULE_CS) $(MODPATH_CS)
+	cp -f $(MSRC)/$(MODULE_CS) $(MODPATH_CS)
+ifndef DESTDIR
 	/sbin/depmod -a
-	@if [ ! -r /etc/pcmcia/hostap_cs.conf ]; then \
-		echo "Installing /etc/pcmcia/hostap_cs.conf"; \
-		cp driver/etc/hostap_cs.conf /etc/pcmcia/hostap_cs.conf; \
+endif
+	@if [ ! -r $(DESTDIR)/etc/pcmcia/hostap_cs.conf ]; then \
+		echo "Installing $(DESTDIR)/etc/pcmcia/hostap_cs.conf"; \
+		cp -f driver/etc/hostap_cs.conf $(DESTDIR)/etc/pcmcia/hostap_cs.conf; \
 	fi
-	@if [ -r /etc/pcmcia/prism2.conf ]; then \
-		echo "You may need to remove old /etc/pcmcia/prism2.conf"; \
+	@if [ -r $(DESTDIR)/etc/pcmcia/prism2.conf ]; then \
+		echo "You may need to remove old $(DESTDIR)/etc/pcmcia/prism2.conf"; \
 	fi
 
 install_plx: install_check install_crypt install_hostap
 	@echo "Installing $(MODULE_PLX) to $(MODPATH_PLX)"
 	mkdir -p $(MODPATH_PLX)
-	cp $(MSRC)/$(MODULE_PLX) $(MODPATH_PLX)
+	cp -f $(MSRC)/$(MODULE_PLX) $(MODPATH_PLX)
 	/sbin/depmod -a
 
 install_pci: install_check install_crypt install_hostap
 	@echo "Installing $(MODULE_PCI) to $(MODPATH_PCI)"
 	mkdir -p $(MODPATH_PCI)
-	cp $(MSRC)/$(MODULE_PCI) $(MODPATH_PCI)
+	cp -f $(MSRC)/$(MODULE_PCI) $(MODPATH_PCI)
 	/sbin/depmod -a
 
 
==============================================

-- 
Regards,
Pavel Roskin




From jasonb  Tue Oct 15 13:04:28 2002
From: jasonb (Jason Boxman)
Date: Tue, 15 Oct 2002 16:04:28 -0400
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <20021015164010.GB13989@shaftnet.org>
References: <3DAC3EA2.7070705@gmx.net> <20021015164010.GB13989@shaftnet.org>
Message-ID: <200210151604.28603.jasonb@edseek.com>

On Tuesday 15 October 2002 12:40 pm, Stuffed Crust wrote:
> On Tue, Oct 15, 2002 at 06:13:22PM +0200, Robert Miano wrote:
> > I just noticed that running the most recent Windows driver from
> > Intersil (ISL3PRDSUIT-EXE_WIN_(2-0-7).exe) downloads version STA 1.5.4
> > onto my COMPAQ WL100.
>
> Actually, the current release is 2.0.9, including STA 1.5.6.  But
> Intersil seems to have um, difficulties in keeping their various web
> sites up to date.
>
> 1.5.4 is fairly solid, unless you like to issue scan requests and end
> up locking up the card about half the time.    1.5.6 fixed that.

And where might you acquire that version?

>  - Pizza

-- 

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





From marcb  Tue Oct 15 14:41:30 2002
From: marcb (marcb at softhome.net)
Date: Tue, 15 Oct 2002 15:41:30 -0600
Subject: Hostapd Compile problem
Message-ID: <courier.3DAC8B8A.00000A8A@softhome.net>

Hi, 

I'm trying to compile the userspace hostap daemon but I'm getting compile 
errors no matter what I try doing...   I'm sure this is a really simple 
problem but I'm just missing something.... 

What I've done so far... 

Defined DPRISM2_HOSTAPD in the driver hostap_config.h
Successfully compiled, installed and used the driver modules
Editted hostapd Makefile to set the Linux source directory correctly... 

Type make 

And I get the following output (below). 

Any help would be greatly appreciated... 

Regards,
Marc 

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



From Jacques.Caron  Tue Oct 15 14:47:58 2002
From: Jacques.Caron (Jacques Caron)
Date: Tue, 15 Oct 2002 23:47:58 +0200
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <3DAC3EA2.7070705@gmx.net>
Message-ID: <5.1.1.6.0.20021015232643.038afc10@pop.mail.yahoo.com>

Two things...

1. Aren't those two images in flash on the card? Which means that once 
updated with the Windows driver, you should be able to move it to a Linux 
box and still have the updated firmware images?
2. What about extracting the images from the Windows driver file? I've 
never looked at a firmware image, but the driver (PRISMNDS.SYS) contains a 
bunch of lines like:
S40500003A7E42
S311FF200000050001001500010001000100B1
S313FF2000000600020000000300010004000400B9
S313FF2000000600020001000200020001000100BE
S30BFF200000020003000000D0
S311FF200000050004000A800000010000003B
[...]
S317FF2000000700018041463031303130312E484558000084
S705003F0000BB
S311FF00000003000000B8127E000C00000098
[...]
S311FF100000FE177E0002000000000000004A
S315007E0000006490FF00F720FE006491FF01F720FE5A
S315007E0010006492FF02F720FE006493FF03F720FE42
[...]

Which look very much like firmware flashing instructions to me :-) Of 
course, once would have to find which bits are each of the two images, but 
anybody familiar with the firmware file format should be able to find that 
pretty easily... Actually, a very very quick look at those lines seems to 
indicate that it includes the images for:
AF010101.HEX
AB010101.HEX
PM010101.HEX
R1010504.HEX
RF010504.HEX
RU010504.HEX

(grep S317FF20000007 on the file and decode the hex and you should get the 
above)

Don't ask me what they are, though :-) And I have no idea either of the 
whereabouts of the primary firmware, but I believe it didn't change the one 
you had on the card, probably for some compatibility issue... Wild guess: 
it has images for primary 1.1.1 and station 1.5.4 for three different types 
of cards?

Just my 0.02 EUR...

Jacques.

At 18:13 15/10/2002, Robert Miano wrote:
>Hi,
>
>I just noticed that running the most recent Windows driver from
>Intersil (ISL3PRDSUIT-EXE_WIN_(2-0-7).exe) downloads version STA 1.5.4
>onto my COMPAQ WL100.
>
>Now I wonder if there's a way to save the card's RAM into a hex file
>for use with "prism2_srec -r" under Linux.
>
>According to Intersil's WinUpdate, the filenames are as follows:
>
>Primary: 0.3.0 P40003C0.HEX
>Station: 1.5.4 R1010504.HEX
>
>Maybe there's somebody who has the latter?
>
>Thanks,
>
>R.
>
>
>_______________________________________________
>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 pizza  Tue Oct 15 15:05:42 2002
From: pizza (Stuffed Crust)
Date: Tue, 15 Oct 2002 18:05:42 -0400
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <200210151604.28603.jasonb@edseek.com>
References: <3DAC3EA2.7070705@gmx.net> <20021015164010.GB13989@shaftnet.org> <200210151604.28603.jasonb@edseek.com>
Message-ID: <20021015220542.GA27892@shaftnet.org>

On Tue, Oct 15, 2002 at 04:04:28PM -0400, Jason Boxman wrote:
> > 1.5.4 is fairly solid, unless you like to issue scan requests and end
> > up locking up the card about half the time.    1.5.6 fixed that.
> 
> And where might you acquire that version?

One way is to have various NDAs and/or a support with Intersil.

Beyond that, I guess you'll have to wait for someone to leak it.   Or
you could extract the images from the windows driver if you're feeling
adventureous..

 - Pizza
-- 
Solomon Peachy                                   pizza at f*cktheusers.org
I'm not broke, but I'm badly bent.                         ICQ #1318344
Patience comes to those who wait.                         Melbourne, FL
               Quidquid latine dictum sit, altum viditur
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20021015/d045600e/attachment.pgp 


From sneeze  Tue Oct 15 15:23:46 2002
From: sneeze (Ryan Abbenhuys)
Date: Wed, 16 Oct 2002 08:23:46 +1000
Subject: Firmware STA 1.5.4, R1010504.HEX
Message-ID: <3dac9572.5913.0@alphalink.com.au>

http://www.intersil.com/design/prism/ss/crack-n-peel/prod-drvr/pcm-cnp-lic-win.asp


...and this little excerpt from the site...

"..With this driver PCMCIA and PCI platforms will automatically upgrade firmware
based on PDA information in the card, but USB devices that currently have Primary
firmware versions older than 1.1.1 will not be supported via RAM download. Users
must manually update the primary to version 1.1.1 or higher before they can
take advantage of RAM download features inherent in the 2.0.2 driver."



>On Tuesday 15 October 2002 12:40 pm, Stuffed Crust wrote:
>> On Tue, Oct 15, 2002 at 06:13:22PM +0200, Robert Miano wrote:
>> > I just noticed that running the most recent Windows driver from
>> > Intersil (ISL3PRDSUIT-EXE_WIN_(2-0-7).exe) downloads version STA 1.5.4

>> > onto my COMPAQ WL100.
>>
>> Actually, the current release is 2.0.9, including STA 1.5.6.  But
>> Intersil seems to have um, difficulties in keeping their various web
>> sites up to date.
>>
>> 1.5.4 is fairly solid, unless you like to issue scan requests and end
>> up locking up the card about half the time.    1.5.6 fixed that.
>
>And where might you acquire that version?
>
>>  - Pizza
>
>-- 
>
>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  Tue Oct 15 15:40:29 2002
From: jasonb (Jason Boxman)
Date: Tue, 15 Oct 2002 18:40:29 -0400
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <20021015220542.GA27892@shaftnet.org>
References: <3DAC3EA2.7070705@gmx.net> <200210151604.28603.jasonb@edseek.com> <20021015220542.GA27892@shaftnet.org>
Message-ID: <200210151840.29318.jasonb@edseek.com>

On Tuesday 15 October 2002 06:05 pm, Stuffed Crust wrote:
> On Tue, Oct 15, 2002 at 04:04:28PM -0400, Jason Boxman wrote:
> > > 1.5.4 is fairly solid, unless you like to issue scan requests and end
> > > up locking up the card about half the time.    1.5.6 fixed that.
> >
> > And where might you acquire that version?
>
> One way is to have various NDAs and/or a support with Intersil.
>
> Beyond that, I guess you'll have to wait for someone to leak it.   Or
> you could extract the images from the windows driver if you're feeling
> adventureous..

I'd be happy with the knowledge of a Windows utility that will flash a card to 
some more recent firmware version.  It seems different vendors decide whether 
or not to make available updated firmware versions for their products and 
that's the best you can hope for...

It sounds like upgrading to the most recent firmware is a mixed bag.  It 
sounds like there are different variants for different chipsets, some older 
ones don't have compatible newer firmware revisions, and some vendors don't 
care to make updates available even when the chipset revision has a matching 
firmware revision.

Or is that is a misinterpretation of reality?  Just trying to get a handle on 
firmware update options.

>  - Pizza

-- 

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





From flash  Tue Oct 15 14:54:24 2002
From: flash (Robert Botha)
Date: Tue, 15 Oct 2002 23:54:24 +0200
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <5.1.1.6.0.20021015232643.038afc10@pop.mail.yahoo.com>
Message-ID: <NJEEIGJGCHHCOHOGBEPICEMOCLAA.flash@flash.za.org>

Just use the Prism WinUpdate utility to dump the Firmware to file.
You won't be able to use this as a RAM upload tho...so there's not much
use..cept you can mabe make the .HEX file avail for others to
download..instead of having to install the driver.

-Robert

-----Original Message-----
From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com]On Behalf Of
Jacques Caron
Sent: 15 October 2002 23:48
To: Robert Miano
Cc: hostap at shmoo.com
Subject: Re: Firmware STA 1.5.4, R1010504.HEX


Two things...

1. Aren't those two images in flash on the card? Which means that once
updated with the Windows driver, you should be able to move it to a Linux
box and still have the updated firmware images?
2. What about extracting the images from the Windows driver file? I've
never looked at a firmware image, but the driver (PRISMNDS.SYS) contains a
bunch of lines like:
S40500003A7E42
S311FF200000050001001500010001000100B1
S313FF2000000600020000000300010004000400B9
S313FF2000000600020001000200020001000100BE
S30BFF200000020003000000D0
S311FF200000050004000A800000010000003B
[...]
S317FF2000000700018041463031303130312E484558000084
S705003F0000BB
S311FF00000003000000B8127E000C00000098
[...]
S311FF100000FE177E0002000000000000004A
S315007E0000006490FF00F720FE006491FF01F720FE5A
S315007E0010006492FF02F720FE006493FF03F720FE42
[...]

Which look very much like firmware flashing instructions to me :-) Of
course, once would have to find which bits are each of the two images, but
anybody familiar with the firmware file format should be able to find that
pretty easily... Actually, a very very quick look at those lines seems to
indicate that it includes the images for:
AF010101.HEX
AB010101.HEX
PM010101.HEX
R1010504.HEX
RF010504.HEX
RU010504.HEX

(grep S317FF20000007 on the file and decode the hex and you should get the
above)

Don't ask me what they are, though :-) And I have no idea either of the
whereabouts of the primary firmware, but I believe it didn't change the one
you had on the card, probably for some compatibility issue... Wild guess:
it has images for primary 1.1.1 and station 1.5.4 for three different types
of cards?

Just my 0.02 EUR...

Jacques.

At 18:13 15/10/2002, Robert Miano wrote:
>Hi,
>
>I just noticed that running the most recent Windows driver from
>Intersil (ISL3PRDSUIT-EXE_WIN_(2-0-7).exe) downloads version STA 1.5.4
>onto my COMPAQ WL100.
>
>Now I wonder if there's a way to save the card's RAM into a hex file
>for use with "prism2_srec -r" under Linux.
>
>According to Intersil's WinUpdate, the filenames are as follows:
>
>Primary: 0.3.0 P40003C0.HEX
>Station: 1.5.4 R1010504.HEX
>
>Maybe there's somebody who has the latter?
>
>Thanks,
>
>R.
>
>
>_______________________________________________
>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

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







From pedro.estrela  Tue Oct 15 23:23:20 2002
From: pedro.estrela (Pedro Estrela)
Date: Tue, 15 Oct 2002 23:23:20 -0700
Subject: 0.7.5 to 1.4.9 firmware upgrade?? [SOLVED]
References: <3DAB314A.8FF23BB0@openline.com.br>
Message-ID: <004201c274dc$85af71d0$2044fea9@inesc.pt>


hello all,

As part of the hostap documentation effort:

I've managed to upgrade the STA firmware to the latest 1.4.9 of my compaq
PCMCIA WL100 cards, based on Prism2 chipset (HFA3841, NICID 0x8002) using
the firmware that was posted ealier on this list for this chipset
(http://hostap.epitest.fi/hostap/2002-08/1540.html), (which, for reference,
I repeat on this message).
Also, please note that firmwares avaliable at www.Netgate.com are for
prism2.5 and prism3 only.

To perform the actual flashing I've used the Intersil windows utility
(WinUpdate-0-5-1-0.exe) that is inside
(ftp://ftp.dlink.com/Wireless/DWL650/Firmware/dwl650_firmware_8c2.exe)
(source: http://hostap.epitest.fi/hostap/2002-07/1379.html). As noted
before, this utility checks if the type of firmware is compatible with your
particular hardware.

Also, as a final test, i've used the latest Compaq firmware utility (inside
softpaq sp15584.exe) to revert the card back to 0.8.0, and i've performed
again the firmware update, without any problems. (i.e., 0.8.0 => 1.4.9 =>
0.8.0 => 1.4.9).

------------

Starting point:
Compaq WL100 with STA 0.8.0
Oct 16 01:21:18 estrela kernel: prism2_hw_config()
Oct 16 01:21:18 estrela kernel: prism2_hw_config: initialized in 9747
iterations
Oct 16 01:21:18 estrela kernel: wlan0: NIC: id=0x8002 v1.0.1
Oct 16 01:21:18 estrela kernel: wlan0: PRI: id=0x15 v0.3.0
Oct 16 01:21:18 estrela kernel: wlan0: STA: id=0x1f v0.8.0
Oct 16 01:21:18 estrela kernel: Using data::nullfunc ACK workaround -
firmware upgrade recommended

Problems:
a) data::nullfunc ACK workaround. (see above)
b) in high load situations there were many many INFDROP events generated on
the driver.

Ending Point:
Compaq WL100 with STA 1.4.9
Oct 15 19:28:17 estrela kernel: prism2_hw_init()
Oct 15 19:28:17 estrela kernel: prism2_hw_config: initialized in 9859
iterations
Oct 15 19:28:17 estrela kernel: wlan0: NIC: id=0x8002 v1.0.1
Oct 15 19:28:17 estrela kernel: wlan0: PRI: id=0x15 v0.3.0
Oct 15 19:28:17 estrela kernel: wlan0: STA: id=0x1f v1.4.9

Problems:
a) solved
b) in same high load situation, there are no INFDROP events.

Pedro Estrela

----- Original Message -----
From: "Bruno Lopes F. Cabral" <bruno at openline.com.br>
To: <hostap at shmoo.com>
Sent: Monday, October 14, 2002 2:04 PM
Subject: 0.7.5 to 1.4.9 firmware upgrade??

> Hi there
>
> I have several USR2445 pccards, which are based on prism
> chipset with the following firmware info:
>
> wlan0: NIC: id=0x8002 v1.0.0
> wlan0: PRI: id=0x15 v0.3.0
> wlan0: STA: id=0x1f v0.7.5
>
> I'm using these cards with openap linux (on a USR2450
> AP), hostap driver version 2002-05-19, kernel 2.4.17
>
> hostap_cs: hostap_cs.c 0.0.0 2002-05-19 (SSH Communications Security Corp,
Joun)
> hostap_cs: (c) SSH Communications Security Corp <jkm at ssh.com>
> hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
> hostap_cs: Registered netdevice wlan0
>
> I'd like to know if it is possible/recommended to upgrade
> them to a newer firmware (i.e. 1.4.9) or it would be
> better to stick with the one it has now.
>
> my goal is to use the firmware wep encription of 1.4.9
> because the  driver's wep make the unit run about 25%
> slower (this "beast" has a 486SX/33 running the system),
> but only if it is safe to do so
>
> thanks in advance for any hints/tips on this topic
>
> Cheers,
> !3runo
> from Brazil
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: STA 1.4.9 for prism2 chipset (HFA3861).zip
Type: application/x-zip-compressed
Size: 51304 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20021015/d3b86f04/attachment.bin 


From pizza  Tue Oct 15 16:19:23 2002
From: pizza (Stuffed Crust)
Date: Tue, 15 Oct 2002 19:19:23 -0400
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <200210151840.29318.jasonb@edseek.com>
References: <3DAC3EA2.7070705@gmx.net> <200210151604.28603.jasonb@edseek.com> <20021015220542.GA27892@shaftnet.org> <200210151840.29318.jasonb@edseek.com>
Message-ID: <20021015231923.GA28918@shaftnet.org>

On Tue, Oct 15, 2002 at 06:40:29PM -0400, Jason Boxman wrote:
> I'd be happy with the knowledge of a Windows utility that will flash a card to 
> some more recent firmware version.  It seems different vendors decide whether 
> or not to make available updated firmware versions for their products and 
> that's the best you can hope for...

Generally, the vendors are too lazy to bother with updates unless it
fixes specific problems their larger customers are complaining about.

> It sounds like upgrading to the most recent firmware is a mixed bag.  It 
> sounds like there are different variants for different chipsets, some older 
> ones don't have compatible newer firmware revisions, and some vendors don't 
> care to make updates available even when the chipset revision has a matching 
> firmware revision.

Intersil has current updates for every production chipset.  Going all
the way back to the earliest prism2 days.   For example, 1.5.6 is
available for prism2, but the newest you'll find on most vendor's sites
is 0.8.3, if they bother at all.

Of course, it's not that the vendors are necessarily lazy -- they have
to properly validate the firmware release on their hardware and driver
combination, and that takes time and costs money.   It may also require
PDA updates, but fortunately Intersil has been good lately about
providing sane defaults for missing records.

Generally, newer is better, but this isn't always the case..
 
 - Pizza
-- 
Solomon Peachy                                   pizza at f*cktheusers.org
I'm not broke, but I'm badly bent.                         ICQ #1318344
Patience comes to those who wait.                         Melbourne, FL
               Quidquid latine dictum sit, altum viditur
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20021015/154359d9/attachment.pgp 


From imp  Tue Oct 15 22:35:26 2002
From: imp (=?ks_c_5601-1987?B?udrI77+t?=)
Date: Wed, 16 Oct 2002 14:35:26 +0900
Subject: Why I can't login ?
Message-ID: <HIEILNBGFIFLDLBJCOLAGEFMCCAA.imp@airlinktek.com>

Dear all

the old cvs tree 
export CVSROOT=":pserver:anonymous at hostap.epitest.fi:/cvs"

seems not working correctly.. Is it moved other place ? 

Thanks.


From pedro.estrela  Wed Oct 16 06:32:25 2002
From: pedro.estrela (Pedro Estrela)
Date: Wed, 16 Oct 2002 06:32:25 -0700
Subject: management frames are lost during high load situations
Message-ID: <00f001c27518$79687930$2044fea9@inesc.pt>

Hello HostAP,

I'm having the following problem, which was NOT solved by using the latest
1.4.9 firmware.

Simply put, when the card is put in stress with a major downstream UDP flow
(greater than a flood ping), the AP is unable to process further
associations/reassociations. In this scenario, a station moving from one
unloaded AP to a loaded AP will keep on sending associations until the load
stops. (card details: NIC: id=0x8002 v1.0.1 , PRI: id=0x15 v0.3.0,  STA:
id=0x1f v0.8.0).


To try to solve this situation, i've tryed to insert an artificial busy loop
on prism2_send_mgmt when the queue is full, to try to artificially wait
until the interrupt appears that executes  wake_queue() in IRQ context.
However, my simple patch did not work as expected (see below both the patch
and the resulting log).
Previouly, i was using a old (April) version of the driver with the maximum
number of packets pending for transmition capped to a low value, by
controlling TX and TX_EV events, and calling wake_queues/stop_queues.
However, this solution incresases greatly the CPU usage, and also degrades
maximum 802.11 throughtpt.

Any ideas on this particular problem?



MODIFICATION:
at the end of
static void prism2_send_mgmt(struct net_device *dev,
                             int type, int subtype, char *body,
                             int body_len, int txevent, u8 *addr)

...

#define MAX_BUSY_WAIT 1000
        {
                int count = 0;

                if (in_interrupt())
                        printk("ERROR: send_management IN INTERUPT \n" );

                if (netif_queue_stopped(dev)){
                        printk("netif_queue_stopped while sending management
packet. will probably be lost. \n" );

                        count = 0;
                        while( (count < MAX_BUSY_WAIT) &&
(netif_queue_stopped(dev))){
                                count++;
                                udelay(100);

                                if((count % 100) == 1)
                                        printk("waiting... count == %d \n",
count );
                        }

                        if (!netif_queue_stopped(dev))
                                printk("netif_queue was waked \n" );
                        if (count >= MAX_BUSY_WAIT)
                                printk("TIMEOUT! %d \n", count );
                }
        }

        /* FIX: is it OK to call dev_queue_xmit() here? This can be called
...


RESULT:
Oct 16 03:22:49 estrela kernel: netif_queue_stopped while sending
management packet. will probably be  lost.
Oct 16 03:22:49 estrela kernel: waiting... count == 1
Oct 16 03:22:49 estrela kernel: waiting... count == 101
Oct 16 03:22:49 estrela kernel: waiting... count == 201
Oct 16 03:22:49 estrela kernel: waiting... count == 301
Oct 16 03:22:49 estrela kernel: waiting... count == 401
Oct 16 03:22:49 estrela kernel: waiting... count == 501
Oct 16 03:22:49 estrela kernel: waiting... count == 601
Oct 16 03:22:49 estrela kernel: waiting... count == 701
Oct 16 03:22:49 estrela kernel: waiting... count == 801
Oct 16 03:22:49 estrela kernel: waiting... count == 901
Oct 16 03:22:49 estrela kernel: TIMEOUT! 1000
Oct 16 03:22:49 estrela kernel: wlan0: 00:02:2d:02:2c:dc auth (alg=0
trans#=1 stat=0 len=6fc=00b0) == > 0 (authenticated)
... repeat until load is stopped ...





From wireless  Tue Oct 15 23:36:16 2002
From: wireless (Sam Tilders)
Date: Wed, 16 Oct 2002 16:36:16 +1000
Subject: D-Link DWL-520 hangs machine.
Message-ID: <200210161636.16276@goonumbla.ozonline.com.au>

Hi all,

I've just installed a DWL-520 (not the 520+) PCI card in one of my machines 
and tried both the prism2_pci driver and the hostap_pci driver.

With the prism2_pci driver I get wlan0 showing in ifconfig -a but if I try and 
configure it (eg: ifconfig wlan0 inet 10.1.1.1 netmask 255.255.255.0) it 
tells me "no such device". So I've momentarily given up there. I really 
wanted to use the HostAP driver anyway.

With the hostap_pci driver it hangs the machine. I don't get anything in the 
logs, I get no output on the console and it is a complete hang, no VT 
switching, no keyboard lights.

I have a suspicion it might have something to do with the PCI 2.2 compliance 
bit... My motherboard is supposed to be 2.2 (according to the manafacturer - 
gigabyte) but dmesg shows:
PCI: PCI BIOS revision 2.10 entry at 0xfdb71, last bus=3

The card shows in lspci -v as:
00:0c.0 Network controller: Harris Semiconductor: Unknown device 3873 (rev 01)
        Subsystem: D-Link System Inc: Unknown device 3501
        Flags: bus master, medium devsel, latency 64, IRQ 11
        Memory at ddbff000 (32-bit, prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2

Does anyone have any experience with this card? 

-- 
-- Sam



From jasonb  Wed Oct 16 00:15:00 2002
From: jasonb (Jason Boxman)
Date: Wed, 16 Oct 2002 03:15:00 -0400
Subject: D-Link DWL-520 hangs machine.
In-Reply-To: <200210161636.16276@goonumbla.ozonline.com.au>
References: <200210161636.16276@goonumbla.ozonline.com.au>
Message-ID: <200210160315.00844.jasonb@edseek.com>

On Wednesday 16 October 2002 02:36 am, Sam Tilders wrote:
> Hi all,
>
<snip>
> I have a suspicion it might have something to do with the PCI 2.2
> compliance bit... My motherboard is supposed to be 2.2 (according to the
> manafacturer - gigabyte) but dmesg shows:
> PCI: PCI BIOS revision 2.10 entry at 0xfdb71, last bus=3

It's possible.  I did talk with someone in September who has a confirmed PCI 
2.1 system and is using a DWL-520 without any problems on a stock RH 
2.4.18-10 kernel and HostAP 09/12/02.  I haven't used one personally in my 
PCI 2.1 system because I had read it may not function properly without PCI 
2.2 support.

> The card shows in lspci -v as:
> 00:0c.0 Network controller: Harris Semiconductor: Unknown device 3873 (rev
> 01) Subsystem: D-Link System Inc: Unknown device 3501
>         Flags: bus master, medium devsel, latency 64, IRQ 11
>         Memory at ddbff000 (32-bit, prefetchable) [size=4K]
>         Capabilities: [dc] Power Management version 2
>
> Does anyone have any experience with this card?

-- 

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





From jkmaline  Wed Oct 16 00:45:25 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 16 Oct 2002 10:45:25 +0300
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <5.1.1.6.0.20021015232643.038afc10@pop.mail.yahoo.com>; from Jacques.Caron@IPsector.com on Tue, Oct 15, 2002 at 11:47:58PM +0200
References: <3DAC3EA2.7070705@gmx.net> <5.1.1.6.0.20021015232643.038afc10@pop.mail.yahoo.com>
Message-ID: <20021016104525.A5702@jm.epitest.fi>

On Tue, Oct 15, 2002 at 11:47:58PM +0200, Jacques Caron wrote:

> 2. What about extracting the images from the Windows driver file? I've 
> never looked at a firmware image, but the driver (PRISMNDS.SYS) contains a 

> Which look very much like firmware flashing instructions to me :-) Of 
> course, once would have to find which bits are each of the two images, but 
> anybody familiar with the firmware file format should be able to find that 
> pretty easily...

Yes, those are indeed firmware images and even in the good old S3
format. prism2_srec did not support one firmware info record in the
images, but I just added support for it. In addition, I added a small
script (split_combined_hex) for automatic extraction of the separate
image files. Both the changes are now in CVS.

I was able to install Intersil drivers with WINE, so Windows is not even
needed for this.. Anyway, after getting the driver binary somewhere,
extracting the images just requires running following commands:

strings PRISMNDS.sys | grep '^S[0-9]' | split_combined_hex

Windows driver seemed to include three versions of both the primary and
station firmware (check split_combined_hex output for list of supported
platforms). All the ?mages are (obviously) RAM downloadable. Primary
images are for somewhat newer cards, but station firmware in
R1010504.HEX seems to support even older cards.

There seems to be something wrong in the interface compatibility
verification of prism2_srec. I have assumed that different variant in
interfaces is a fatal error, but it might not be in all cases. Anyway, I
added '-i' option for prism2_srec to ignore those errors. Use it at your
own risk..

I was able to upgrade (RAM download) Compaq WL200 with the 1.5.4 station
firmware ('-i' was required for prism2_srec) using R1010504.HEX. I
haven't tested the resulting image with any real data transfers, but at
least it initialized properly and RIDs can be retrieved with
hostap_diag.

I haven't yet experimented with RAM downloadable primary firmware (with
Prism2.5). It would be nice to get it working since this would probably
allow one to use RAM download even when the card has old primary image
in the flash.

-- 
Jouni Malinen                                            PGP id EFC895FA




From jasonb  Wed Oct 16 00:57:05 2002
From: jasonb (Jason Boxman)
Date: Wed, 16 Oct 2002 03:57:05 -0400
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <20021016104525.A5702@jm.epitest.fi>
References: <3DAC3EA2.7070705@gmx.net> <5.1.1.6.0.20021015232643.038afc10@pop.mail.yahoo.com> <20021016104525.A5702@jm.epitest.fi>
Message-ID: <200210160357.05092.jasonb@edseek.com>

On Wednesday 16 October 2002 03:45 am, Jouni Malinen wrote:
> On Tue, Oct 15, 2002 at 11:47:58PM +0200, Jacques Caron wrote:
> > 2. What about extracting the images from the Windows driver file? I've
> > never looked at a firmware image, but the driver (PRISMNDS.SYS) contains
> > a
> >
> > Which look very much like firmware flashing instructions to me :-) Of
> > course, once would have to find which bits are each of the two images,
> > but anybody familiar with the firmware file format should be able to find
> > that pretty easily...
>
<snip>
> I haven't yet experimented with RAM downloadable primary firmware (with
> Prism2.5). It would be nice to get it working since this would probably
> allow one to use RAM download even when the card has old primary image
> in the flash.

I have a Prism2.5 card here and a RAM downloadable primary firmware v1.1.0 
image.  Is it possible it already works?  If not, is there some output I can 
provide from a failure that would help get it working?

-- 

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





From jasonb  Wed Oct 16 01:02:21 2002
From: jasonb (Jason Boxman)
Date: Wed, 16 Oct 2002 04:02:21 -0400
Subject: hostap_crypt_conf
Message-ID: <200210160402.21388.jasonb@edseek.com>

I'm looking at the help output and I am unsure what exactly it's used for.

I'm guessing it offers additional options above and beyond what iwconfig key 
offers?

Thanks.

-- 

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





From jkmaline  Wed Oct 16 01:17:27 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 16 Oct 2002 11:17:27 +0300
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <200210160357.05092.jasonb@edseek.com>; from jasonb@edseek.com on Wed, Oct 16, 2002 at 03:57:05AM -0400
References: <3DAC3EA2.7070705@gmx.net> <5.1.1.6.0.20021015232643.038afc10@pop.mail.yahoo.com> <20021016104525.A5702@jm.epitest.fi> <200210160357.05092.jasonb@edseek.com>
Message-ID: <20021016111727.A6201@jm.epitest.fi>

On Wed, Oct 16, 2002 at 03:57:05AM -0400, Jason Boxman wrote:

> I have a Prism2.5 card here and a RAM downloadable primary firmware v1.1.0 
> image.  Is it possible it already works?  If not, is there some output I can 
> provide from a failure that would help get it working?

I have few Prism2.5-based PCI cards, so I do not probably need test
reports at this point. If I remember correctly, the download did not
work the last time I tried it.

I'm not fully sure about the proper procedure with primary image. There
are two possibilities: 1) download primary image to RAM, initialize
card, download station image to RAM, initialize card again; 2) download
combined primary image and station image data to RAM, initialize card. I
have mostly tested the second option, but it did not seem to work
correctly. First option requires some changes to the driver code so that
it will be able to initialize the card with only primary image and then
perform RAM download for the station image.
 
-- 
Jouni Malinen                                            PGP id EFC895FA




From jasonb  Wed Oct 16 01:27:18 2002
From: jasonb (Jason Boxman)
Date: Wed, 16 Oct 2002 04:27:18 -0400
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <20021016111727.A6201@jm.epitest.fi>
References: <3DAC3EA2.7070705@gmx.net> <200210160357.05092.jasonb@edseek.com> <20021016111727.A6201@jm.epitest.fi>
Message-ID: <200210160427.18766.jasonb@edseek.com>

On Wednesday 16 October 2002 04:17 am, Jouni Malinen wrote:
> On Wed, Oct 16, 2002 at 03:57:05AM -0400, Jason Boxman wrote:
> > I have a Prism2.5 card here and a RAM downloadable primary firmware
> > v1.1.0 image.  Is it possible it already works?  If not, is there some
> > output I can provide from a failure that would help get it working?
>
> I have few Prism2.5-based PCI cards, so I do not probably need test
> reports at this point. If I remember correctly, the download did not
> work the last time I tried it.

Ah, okay.  Then I'll mention that may not work in the HostAP 2002-10-12 
article I'm working on.

On a related note, can you fry your card if you download into flash (-f)?

<snip>

-- 

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





From Coursimault  Wed Oct 16 02:07:09 2002
From: Coursimault (Coursimault, Jean-marc)
Date: Wed, 16 Oct 2002 11:07:09 +0200
Subject: Does Netgear MA311 work with HostAP ?
Message-ID: <B792B80756A1D511B9BD00508BB8CDB29FDEC3@macedoine.grenoble.xrce.xerox.com>

Hello,

I'm thinking of using Netgear's MA311 PCI card for my wireless network
(Linux Mandrake 9.0) (rather than the PCMCIA MA401 + PCMCIA/PCI adapter)

This card has a Prism 2.0 chipset, it seems, but their tech support says 
that software AP is "not supported".

I don't have any more details yet.

Does anyone use this card ?
Thanks
-- Jean-Marc
____________________________________________________________
Jean-Marc Coursimault         |
Xerox Research Centre Europe  | Tel   +33 (0)4 76 61 51 82
Systems Dev. & Engineering    | Fax   +33 (0)4 76 61 51 99
6, chemin de Maupertuis       | 
38240 Meylan (France)         | coursimault at xrce.xerox.com
  



From wireless  Wed Oct 16 03:26:28 2002
From: wireless (Sam Tilders)
Date: Wed, 16 Oct 2002 20:26:28 +1000
Subject: Does Netgear MA311 work with HostAP ?
In-Reply-To: <B792B80756A1D511B9BD00508BB8CDB29FDEC3@macedoine.grenoble.xrce.xerox.com>
References: <B792B80756A1D511B9BD00508BB8CDB29FDEC3@macedoine.grenoble.xrce.xerox.com>
Message-ID: <200210162026.28348@goonumbla.ozonline.com.au>

> I'm thinking of using Netgear's MA311 PCI card for my wireless network
> (Linux Mandrake 9.0) (rather than the PCMCIA MA401 + PCMCIA/PCI adapter)

I had one of these cards for a couple of days.

> Does anyone use this card ?

I tried a variety of drivers including the prism2_pci driver and could get 
none of them to recognise the card though lspci showed it was definetely 
plugged in.

Also googling brought up amazingly few hits with this card related to anything 
linux or bsd'ish.

I ended up returning the card.

I'm not much help am I...

-- 
-- Sam



From jkmaline  Wed Oct 16 03:41:01 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 16 Oct 2002 13:41:01 +0300
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <200210160427.18766.jasonb@edseek.com>; from jasonb@edseek.com on Wed, Oct 16, 2002 at 04:27:18AM -0400
References: <3DAC3EA2.7070705@gmx.net> <200210160357.05092.jasonb@edseek.com> <20021016111727.A6201@jm.epitest.fi> <200210160427.18766.jasonb@edseek.com>
Message-ID: <20021016134101.A8981@jm.epitest.fi>

On Wed, Oct 16, 2002 at 04:27:18AM -0400, Jason Boxman wrote:

> On a related note, can you fry your card if you download into flash (-f)?

Well.. Yes, but not with the releases Host AP driver since I have not
included kernel-side support for non-volatile download. I have written
this code, but it has a bug somewhere so I haven't released it yet.

It is a bit difficult to fix a card with broken primary firmware
(especially, if it is HFA3841 card, which apparently requires somewhat
modified PC Card adapter to get the card in genesis mode). I don't think
I will be testing that flashing code before I either find the bug or get
a working system that can initialize the card firmware completely
(i.e., using genesis mode and flashing all new images).
 
-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Wed Oct 16 03:44:11 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 16 Oct 2002 13:44:11 +0300
Subject: hostap_crypt_conf
In-Reply-To: <200210160402.21388.jasonb@edseek.com>; from jasonb@edseek.com on Wed, Oct 16, 2002 at 04:02:21AM -0400
References: <200210160402.21388.jasonb@edseek.com>
Message-ID: <20021016134411.B8981@jm.epitest.fi>

On Wed, Oct 16, 2002 at 04:02:21AM -0400, Jason Boxman wrote:

> I'm guessing it offers additional options above and beyond what iwconfig key 
> offers?

Yes, you can configure different encryption algorithms (should you have
implemented one ;-) than WEP. In addition, you can use hostap_crypt_conf
to configure station-specific individual keys for unicast frames (i.e.,
different keys for each STA).
 
-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Wed Oct 16 03:46:54 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 16 Oct 2002 13:46:54 +0300
Subject: Why I can't login ?
In-Reply-To: <HIEILNBGFIFLDLBJCOLAGEFMCCAA.imp@airlinktek.com>; from imp@airlinktek.com on Wed, Oct 16, 2002 at 02:35:26PM +0900
References: <HIEILNBGFIFLDLBJCOLAGEFMCCAA.imp@airlinktek.com>
Message-ID: <20021016134654.C8981@jm.epitest.fi>

On Wed, Oct 16, 2002 at 02:35:26PM +0900, ?????? wrote:

> the old cvs tree 
> export CVSROOT=":pserver:anonymous at hostap.epitest.fi:/cvs"
> 
> seems not working correctly.. Is it moved other place ? 

Works fine for me and no, it has not been moved.

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Wed Oct 16 03:53:09 2002
From: jkmaline (Jouni Malinen)
Date: Wed, 16 Oct 2002 13:53:09 +0300
Subject: Binary attachments (was: 0.7.5 to 1.4.9 firmware upgrade??)
In-Reply-To: <004201c274dc$85af71d0$2044fea9@inesc.pt>; from pedro.estrela@inesc.pt on Tue, Oct 15, 2002 at 11:23:20PM -0700
References: <3DAB314A.8FF23BB0@openline.com.br> <004201c274dc$85af71d0$2044fea9@inesc.pt>
Message-ID: <20021016135309.D8981@jm.epitest.fi>

On Tue, Oct 15, 2002 at 11:23:20PM -0700, Pedro Estrela wrote:

> the firmware that was posted ealier on this list for this chipset
> (http://hostap.epitest.fi/hostap/2002-08/1540.html), (which, for reference,
> I repeat on this message).

Please, do _not_ send any binary attachments to the mailing list.
Patches to the driver are OK as an attachment, but please keep
executable binaries and firmware images away from the list. If you have
something like this to share, post the image on an FTP or WWW site and
just mail the URL. Current list configuration does apparently allow such
attachments, but I will ask this to be changed if I see more such
messages.

-- 
Jouni Malinen                                            PGP id EFC895FA




From Jacques.Caron  Wed Oct 16 04:03:52 2002
From: Jacques.Caron (Jacques Caron)
Date: Wed, 16 Oct 2002 13:03:52 +0200
Subject: D-Link DWL-520 hangs machine.
In-Reply-To: <200210160315.00844.jasonb@edseek.com>
References: <200210161636.16276@goonumbla.ozonline.com.au>
 <200210161636.16276@goonumbla.ozonline.com.au>
Message-ID: <5.1.1.6.0.20021016125925.00b357f0@pop.mail.yahoo.com>

I have the same card running in 7-year old Pentium 90 system, which I 
pretty much doubt is PCI2.2 compliant. And it works flawlessly with FreeBSD.

Note however that:
- I've seen reports that there are actually different versions of the same 
card, which might have different behaviors in terms of compatibility;
- I've had trouble with the same card in a Soekris box (Net4501) until I 
changed the power supply. The problems were a lot of "wi_cmd: timeout" and 
similar messages which hung the machine for a few seconds each time, and 
random complete hangs. So it looks like having not enough power or similar 
problems can cause quite some issues. This was also with FreeBSD.

Jacques.

At 09:15 16/10/2002, Jason Boxman wrote:
>On Wednesday 16 October 2002 02:36 am, Sam Tilders wrote:
> > Hi all,
> >
><snip>
> > I have a suspicion it might have something to do with the PCI 2.2
> > compliance bit... My motherboard is supposed to be 2.2 (according to the
> > manafacturer - gigabyte) but dmesg shows:
> > PCI: PCI BIOS revision 2.10 entry at 0xfdb71, last bus=3
>
>It's possible.  I did talk with someone in September who has a confirmed PCI
>2.1 system and is using a DWL-520 without any problems on a stock RH
>2.4.18-10 kernel and HostAP 09/12/02.  I haven't used one personally in my
>PCI 2.1 system because I had read it may not function properly without PCI
>2.2 support.
>
> > The card shows in lspci -v as:
> > 00:0c.0 Network controller: Harris Semiconductor: Unknown device 3873 (rev
> > 01) Subsystem: D-Link System Inc: Unknown device 3501
> >         Flags: bus master, medium devsel, latency 64, IRQ 11
> >         Memory at ddbff000 (32-bit, prefetchable) [size=4K]
> >         Capabilities: [dc] Power Management version 2
> >
> > Does anyone have any experience with this card?
>
>--
>
>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


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




From xdhuang  Wed Oct 16 00:28:31 2002
From: xdhuang (Huang Xiaodong)
Date: 16 Oct 2002 15:28:31 +0800
Subject: Unicast frame ACK time
Message-ID: <20021016152831.71542.qmail@eyou.com>

hi??

Need your help on following issues:

1)I dump the time stamp seperately when the function "prism2_transmit" and the
interrupt "HFA384X_EV_TX" are called. I consider the difference of these two
timestamps as the latency of a frame's ack, is it right?

2)The interrupt "HFA384X_EV_TX" is called when the unicast frame's acknowlege
is received (may be already several retransmittion happened ), and the
interrupt "HFA384X_EV_TXEXC"(RetryErr) is called when the unicast frame's
acknowlege is not received even maximum retranmission. Is it right?

If my comprehesion is right,Why the duration time (unicast frame) between the
calling of "prism2_transmit" and "HFA384X_EV_TX" is longer than the duration
time between the calling of "prism2_transmit" and interrupt
"HFA384X_EV_TXEXC"(RetryErr)?

Thanks in advance.

Huang Xiaodong





--http://www.eyou.com
--??????????????????????  ????????  ????????  ????????  ????????...????????





From imp  Wed Oct 16 05:48:21 2002
From: imp (???)
Date: Wed, 16 Oct 2002 21:48:21 +0900
Subject: CVS TREE ?
Message-ID: <HIEILNBGFIFLDLBJCOLAIEFOCCAA.imp@airlinktek.com>

Dear all..

I can't login the CVS tree.. Is it moved to other place ? 

Thanks.


From wireless  Wed Oct 16 07:16:42 2002
From: wireless (Sam Tilders)
Date: Thu, 17 Oct 2002 00:16:42 +1000
Subject: Card works - Was: Re: D-Link DWL-520 hangs machine.
Message-ID: <200210170016.42295@goonumbla.ozonline.com.au>

I updated the machine to mandrake 9.0 and thus kernel 2.4.19. The machine no 
longer hangs when i "modprobe hostap_pci".

Side note: I tried the prism2_pci driver in this new install as well, it fails 
when it tries to load the pcmcia card services... 

Did have some issues with modprobe though. Using "modprobe hostap_pci" 
fails... but using insmod to load the modules one at a time works fine. (Yes 
I did run "depmod -a" first).

so "modprobe hostap_pci" fails with "init module: No such device"
but 
"insmod hostap_crypt; insmod hostap; insmod hostap_pci"
works fine.

It now shows in ifconfig and the wireless tools can read the parameters.
-- 
-- Sam



From Coursimault  Wed Oct 16 07:16:11 2002
From: Coursimault (Coursimault, Jean-marc)
Date: Wed, 16 Oct 2002 16:16:11 +0200
Subject: Micronet SP906 A ?
Message-ID: <B792B80756A1D511B9BD00508BB8CDB29FDECE@macedoine.grenoble.xrce.xerox.com>

Hello,

Any feedback on using the PCI card Micronet SP906A
with hostAP ?

Thanks
Jean marc



From JFulmer  Wed Oct 16 07:39:21 2002
From: JFulmer (Fulmer, John)
Date: 16 Oct 2002 09:39:21 -0500
Subject: Card works - Was: Re: D-Link DWL-520 hangs machine.
In-Reply-To: <200210170016.42295@goonumbla.ozonline.com.au>
References: <200210170016.42295@goonumbla.ozonline.com.au>
Message-ID: <1034779168.19349.1.camel@muir.hrblock.net>

I found all my issues with the DWL-520 were PCI IRQ conflicts (the
DWL-520 doesn't like them...at all).

Just my 2 cents.

jf

On Wed, 2002-10-16 at 09:16, Sam Tilders wrote:
> I updated the machine to mandrake 9.0 and thus kernel 2.4.19. The machine no 
> longer hangs when i "modprobe hostap_pci".
> 
> Side note: I tried the prism2_pci driver in this new install as well, it fails 
> when it tries to load the pcmcia card services... 
> 
> Did have some issues with modprobe though. Using "modprobe hostap_pci" 
> fails... but using insmod to load the modules one at a time works fine. (Yes 
> I did run "depmod -a" first).
> 
> so "modprobe hostap_pci" fails with "init module: No such device"
> but 
> "insmod hostap_crypt; insmod hostap; insmod hostap_pci"
> works fine.
> 
> It now shows in ifconfig and the wireless tools can read the parameters.
> -- 
> -- Sam
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From hostap  Wed Oct 16 09:29:21 2002
From: hostap (Pablo Berra)
Date: Wed, 16 Oct 2002 13:29:21 -0300
Subject: WET11 & HostAP
Message-ID: <000501c27531$2f0529b0$de00010a@lq.com.ar>

Hi,

Did anybody test connectivity between a Linksys WET11 and a HostAP in master
mode?
There is a problem between the WAP11 and HostAP, I want to know if this
problem exists in the WET11 too.

Thanks in advance.
Pablo.




From ctodish  Wed Oct 16 09:51:07 2002
From: ctodish (Clint Todish)
Date: Wed, 16 Oct 2002 11:51:07 -0500
Subject: WET11 & HostAP
In-Reply-To: <000501c27531$2f0529b0$de00010a@lq.com.ar>
Message-ID: <000001c27534$38e22890$0500640a@ridgmar.net>

I've successfully deployed a WET11 as a client connected to my HostAP
machine to a house about 2000' away - works exceptionally well,
actually. These little boxes have 80mw xmit power with an RP-SMA
connector for an external antenna - so they work well in a sealed
enclosure using power over ethernet and a waterproof directional patch.

-C

-----Original Message-----
From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com] On Behalf
Of Pablo Berra
Sent: Wednesday, October 16, 2002 11:29 AM
To: hostap at shmoo.com
Subject: WET11 & HostAP


Hi,

Did anybody test connectivity between a Linksys WET11 and a HostAP in
master mode? There is a problem between the WAP11 and HostAP, I want to
know if this problem exists in the WET11 too.

Thanks in advance.
Pablo.

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




From benh  Wed Oct 16 12:06:32 2002
From: benh (Benjamin Herrenschmidt)
Date: Wed, 16 Oct 2002 21:06:32 +0200
Subject: MA401 & hostAP trouble
Message-ID: <20021016190632.8042@192.168.4.1>

Hi !

I'm experimenting on a ppc405-based embedded platform using an
a NetGeat MA401 card in an MA301 PCI adapter with the hostap
driver.

The card has a NIC id 0x800c, v1.0.0, PRI id 0x15 v1.0.7 and STA
id 0x1f v1.3.6 (though the firmware on the CDROM provided by
Netgear is only 1.3.4). I've tried updating it to 1.4.9 using
the firmware previously posted on this list, but it would
complain that firmware wasn't built for 0x800c.

My problem is quite simple: behaviour is erratic. I may be
missing something though so I would appreciate any help in
troubleshooting that..

I don't do any special setting after loading the hostap
driver (still at 2002-09-12 for now). I just up the interface
with some non routed IP, eventually set it's essid, and set
the channel to 10 (as I'm testing with an Apple airport card
bought in France, and thus limited to channel 10 and possibly
above).

The result is that it takes a very long time for the airport
card (which is an orinoco silver with firmware 8.70) to actually
see a link to the AP.  By very long I mean a random amount of
time that goes up to a couple of minutes (when they ever get a
link). The 2 cards are located less than 1 meter away.
Then, if I ping the AP machine from the airport, or setup some
routing, things usually just fail most of the time, that is most
packets are dropped (though some go through). Usually not enough
to establish a TCP connexion.

The AP machine keeps displaying in dmesg messages of the kind
"wlan0: <airport MAC addr> auth (alg=0 trans#=1 stat=0 len=6fc=08b0) => 0
(authenticated)
and some messages about lowering down Tx rate (too 55, then 20, then 10)

Any clue ? Should I try to find a newer firmware ? Is there
something else wrong ?

Regards, and thanks in advance for any help !

Ben.
Linux/PPC kernel bot





From benh  Wed Oct 16 12:50:40 2002
From: benh (Benjamin Herrenschmidt)
Date: Wed, 16 Oct 2002 21:50:40 +0200
Subject: MA401 & hostAP trouble
In-Reply-To: <20021016190632.8042@192.168.4.1>
References: <20021016190632.8042@192.168.4.1>
Message-ID: <20021016195041.32132@192.168.4.1>

>Any clue ? Should I try to find a newer firmware ? Is there
>something else wrong ?

I finally managed to update my firmware, I now have primary 1.1.0
and STA 1.4.9, and the problem remains.

Some more infos: in the hostAP dmesg, I also see some message
of the type "<MAC> assoc (len=16, prev_ap=00:00:00:00:00:00)
=> 0(0) (OK, old AID)

The station machine (airport card) shows a regulary increasing
number of "Tx excessive retries" in iwconfig (but no other error
in ifconfig),

The AP machine shows lots of TX errors in ifconfig (almost as
much as packets sent, 35 error for 40 packets sent in my latest
test)

Ben.





From proski  Wed Oct 16 13:49:08 2002
From: proski (Pavel Roskin)
Date: Wed, 16 Oct 2002 16:49:08 -0400
Subject: [PATCH] Warning fix for gcc 3.2
Message-ID: <1034801348.3dadd0c4f3006@webmail.spamcop.net>

An embedded and charset-unspecified text was scrubbed...
Name: not available
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20021016/68ae2739/attachment.txt 


From proski  Wed Oct 16 14:54:02 2002
From: proski (Pavel Roskin)
Date: Wed, 16 Oct 2002 17:54:02 -0400
Subject: [PATCH] Explicitly list dependencies in hostap_cs.conf
Message-ID: <1034805242.3daddffa6cbb3@webmail.spamcop.net>

An embedded and charset-unspecified text was scrubbed...
Name: not available
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20021016/da5771ed/attachment.txt 


From linux  Wed Oct 16 19:21:43 2002
From: linux (Yanghwee TAN)
Date: Thu, 17 Oct 2002 10:21:43 +0800
Subject: HostAP contributed docs URL link UPDATE.
Message-ID: <20021017102143.7e43989d.linux@comp-tech.com>

Hi all,

Please note that the url for 

Yanghwee's Wireless AP using HostAP 
on Jouni's hostap links reference has been changed.

the updated and valid link is,

 http://student.bii.a-star.edu.sg/~tanyh/How-To-wirelessAP.html



-- 
Cheers!

...=...=...=...=...=...=...=...=...=...
  Yanghwee <linux at comp-tech.com>
  alternate email <mx5yh at singnet.com.sg>
  http://www.comp-tech.com



From donp  Wed Oct 16 22:55:25 2002
From: donp (Don Park)
Date: Wed, 16 Oct 2002 22:55:25 -0700 (PDT)
Subject: hostapd / management frame processing
Message-ID: <Pine.LNX.4.44.0210162244090.19756-100000@amidala.klickitat.yi.org>

Hello,
	Im writing a GTK+ app(1) that makes use of the access point
scanning in wireless tools v15. Ive come to a problem in that gtk apps
cant be setuid, and it takes root privledges to make the scanning ioctl
call. In a way this is good because i have to rethink the app. right now
its using a polling mechanism to get an updated list of in-range APs. the
polling causes all wireless traffic to stop until the scan finishes. this
can take 1-5 seconds.

	What should happen is at the moment a beacon frame is received by
the wireless driver, a notice is sent to all interested parties with the
details of the AP. As far as I can tell, hostapd was made for just this
reason. To register my app with hostapd and be notified on reception of a
beacon frame(2) is much simpler to code for than trying to do my own
polling.  its also more efficient because im notified right when the AP
comes in range, and im waiting on a signal rather than polling over and
over.

	What i want to know is, can hostapd be modified to work with any
v15 wireless driver (airo_cs, orinoco_cs, etc)? id like to get this
functionality no matter what kind of wireless card is in use.

Don
(1)the AP is 'AP Radar' at http://apradar.sourceforge.net
(2)i understand that beacon rates can get pretty high, but hopefully it
wont be a problem
-- 
** irc: irc.freenode.net nick: don-o channels: #wireless, #java
** "For thirty years they've questioned the need for NASA. Today
** we're going to give them the answer." -- Armageddon




From azeta  Wed Oct 16 23:09:41 2002
From: azeta (Alejandro Lamas)
Date: Thu, 17 Oct 2002 08:09:41 +0200
Subject: 0.7.5 to 1.4.9 firmware upgrade??
In-Reply-To: <00a101c273e3$02f58350$bde116d5@pedropc>
References: <3DAB314A.8FF23BB0@openline.com.br> <00a101c273e3$02f58350$bde116d5@pedropc>
Message-ID: <20021017060942.788BE42E39@bichito>


> I have several compaq WL100 PCMCIA cards, based on Prism2 chipset (HFA3841,
> NICID 0x8002). However, all the firmwares available at
> http://www.netgate.com/support/prism_firmware are for the chipsets prism2.5
> and prism3  (HFA3842, NICID 0x800A and higher).
>
> I'm hoping that the firmware for the zoom card fixed by Alejandro Lamas
> (http://hostap.epitest.fi/hostap/2002-08/1540.html) will work on the compaq
> WL100 (and also WL200), as it is a prism2 card (HFA3841, NICID 0x8003)
> (Alejandro: please confirm if you can).

I cannot assure it, but like the characteristics of your cards differs is 
probably that the upgrade don't work. Really i don't know.

But... i didn't fix the firmware, simply i send it badly the first time. I 
ask Zoom for the firmware and they give me it.
The same form, you can ask Compaq to support an upgrade firmware.

> To perform the actual flashing (tomorrow) I will be using the Intersil
> windows utility (WinUpdate-0-5-1-0.exe) that is inside
> (ftp://ftp.dlink.com/Wireless/DWL650/Firmware/dwl650_firmware_8c2.exe) 
> (see http://hostap.epitest.fi/hostap/2002-07/1379.html)

This utility must tell you if the firmware image is a valid image before 
start to flash.. (i think)

(sorry if i respond too late)



From imp  Thu Oct 17 00:05:00 2002
From: imp (=?ks_c_5601-1987?B?udrI77+t?=)
Date: Thu, 17 Oct 2002 16:05:00 +0900
Subject: CVS ???
Message-ID: <HIEILNBGFIFLDLBJCOLACEGDCCAA.imp@airlinktek.com>

Dear all

I can not login to Current CVS Tree .. 
Are their any change on the server ? 
Please, let me know..

Thanks.


From martin.polak  Thu Oct 17 02:51:48 2002
From: martin.polak (Martin Polak)
Date: Thu, 17 Oct 2002 11:51:48 +0200
Subject: 0.7.5 to 1.4.9 firmware upgrade?? [SOLVED]
References: <3DAB314A.8FF23BB0@openline.com.br> <004201c274dc$85af71d0$2044fea9@inesc.pt>
Message-ID: <3DAE8834.9050905@liwest.at>

Pedro Estrela schrieb:
> hello all,
> 
> As part of the hostap documentation effort:
> 
> I've managed to upgrade the STA firmware to the latest 1.4.9 of my compaq
> PCMCIA WL100 cards, based on Prism2 chipset (HFA3841, NICID 0x8002) using
> the firmware that was posted ealier on this list for this chipset
> (http://hostap.epitest.fi/hostap/2002-08/1540.html), (which, for reference,
> I repeat on this message).
> Also, please note that firmwares avaliable at www.Netgate.com are for
> prism2.5 and prism3 only.
> 
> To perform the actual flashing I've used the Intersil windows utility
> (WinUpdate-0-5-1-0.exe) that is inside
> (ftp://ftp.dlink.com/Wireless/DWL650/Firmware/dwl650_firmware_8c2.exe)
> (source: http://hostap.epitest.fi/hostap/2002-07/1379.html). As noted
> before, this utility checks if the type of firmware is compatible with your
> particular hardware.
> 
> Also, as a final test, i've used the latest Compaq firmware utility (inside
> softpaq sp15584.exe) to revert the card back to 0.8.0, and i've performed
> again the firmware update, without any problems. (i.e., 0.8.0 => 1.4.9 =>
> 0.8.0 => 1.4.9).

Hi Pedro!

I've tried to use your method on my Netgear MA401
NIC: id=0x8003 v1.0.0
PRI: id=0x15 v0.3.0
STA: id=0x1f v0.8.3

to STA 1.4.9 using your hex-File and method. It doesn't work for me, see 
the dmesg output below. When I am using STA 1.3.4 from Netgear it works, 
but I'd like to use 1.4.9 (or above) for card-based WEP in hostap-mode.

Any suggestions anyone?


Oct 17 11:30:35 igate kernel: hostap_cs: hostap_cs.c 0.0.0 2002-10-12 
(SSH Communications Security Corp, Jouni Malinen)
Oct 17 11:30:35 igate kernel: hostap_cs: (c) Jouni Malinen 
<jkmaline at cc.hut.fi>
Oct 17 11:30:35 igate kernel: hostap_cs: setting Vcc=33 (constant)
Oct 17 11:30:35 igate kernel: hostap_cs: CS_EVENT_CARD_INSERTION
Oct 17 11:30:35 igate kernel: prism2_config()
Oct 17 11:30:35 igate kernel: hostap_cs: setting Vcc=50 (from config)
Oct 17 11:30:35 igate kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
Oct 17 11:30:35 igate kernel: IO window settings: cfg->io.nwin=1 
dflt.io.nwin=1
Oct 17 11:30:35 igate kernel: io->flags = 0x0046, io.base=0x0000, len=64
Oct 17 11:30:35 igate kernel: hostap_cs: index 0x01: Vcc 5.0, irq 5, io 
0x0100-0x013f
Oct 17 11:30:35 igate kernel: hostap_cs: Registered netdevice eth2
Oct 17 11:30:35 igate kernel: prism2_hw_init()
Oct 17 11:30:35 igate kernel: prism2_hw_config: initialized in 5736 
iterations
Oct 17 11:30:35 igate kernel: eth2: trying to read PDA from 0x007f0000: 
failed
  Oct 17 11:30:35 igate kernel: eth2: trying to read PDA from 
0x003f0000: failed
Oct 17 11:30:35 igate kernel: eth2: trying to read PDA from 0x00390000: OK
Oct 17 11:30:35 igate kernel: eth2: fid allocate, len=2364 - timeout
Oct 17 11:30:35 igate kernel: eth2: fid allocate, len=1600 - timeout
Oct 17 11:30:35 igate kernel: hostap_cs: Initialization failed
Oct 17 11:30:35 igate cardmgr[2961]: executing: './network start eth2'
Oct 17 11:30:36 igate cardmgr[2961]: + adress is SuSE,0,0,00:00:00:00:00:00
Oct 17 11:30:36 igate cardmgr[2961]: + allowing all MACs
Oct 17 11:30:37 igate kernel: eth2: prism2_open
Oct 17 11:30:39 igate kernel: eth2: hfa384x_cmd: entry still in list? 
(entry=c19e6fa0, type=0, res=0)
Oct 17 11:30:39 igate kernel: eth2: hfa384x_cmd: command was not 
completed (res=0, entry=c19e6fa0, type=0, cmd=0x0001, param0=0x0000)
Oct 17 11:30:39 igate kernel: eth2: MAC port 0 enabling failed
Oct 17 11:30:39 igate kernel: eth2: could not enable MAC port
Oct 17 11:30:39 igate kernel: eth2: prism2_close
Oct 17 11:30:39 igate kernel: eth2: prism2_open
Oct 17 11:30:41 igate kernel: eth2: hfa384x_cmd: entry still in list? 
(entry=c19e6a60, type=0, res=0)
Oct 17 11:30:41 igate kernel: eth2: hfa384x_cmd: command was not 
completed (res=0, entry=c19e6a60, type=0, cmd=0x0001, param0=0x0000)
Oct 17 11:30:41 igate kernel: eth2: MAC port 0 enabling failed
Oct 17 11:30:41 igate kernel: eth2: could not enable MAC port
Oct 17 11:30:41 igate kernel: eth2: prism2_close




From erosenst  Thu Oct 17 04:14:13 2002
From: erosenst (=?iso-8859-15?Q?Eerin_Rosenstr=F6m?=)
Date: Thu, 17 Oct 2002 14:14:13 +0300 (EET DST)
Subject: atmel support?
Message-ID: <Pine.OSF.4.44.0210171403260.26815-100000@kosh.hut.fi>

Is there future plans to support atmel chipset (AT76C502A) with hostap
driver?

These cards are cheap and common. Big companies like d-link and smc move
their prism2 based cards to atmel cards. Like smc2632w -> smc2632w v.2
d-link dwl-650 -> dwl-650+.
 It is dificult to find nowdays prism2 based cards...

-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

                    ****  Eerin Rosenstr?m          ****
                    **    Servinmaijantie 12 F 77     **
                    **    02150 Espoo                 **
                    **    p. +358 9 4682997           **
                    ****  p.+358 40 5205030         ****

-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*




From benh  Thu Oct 17 07:33:13 2002
From: benh (Benjamin Herrenschmidt)
Date: Thu, 17 Oct 2002 16:33:13 +0200
Subject: 0.7.5 to 1.4.9 firmware upgrade?? [SOLVED]
In-Reply-To: <3DAE8834.9050905@liwest.at>
References: <3DAE8834.9050905@liwest.at>
Message-ID: <20021017143313.16560@192.168.4.1>

>Hi Pedro!
>
>I've tried to use your method on my Netgear MA401
>NIC: id=0x8003 v1.0.0
>PRI: id=0x15 v0.3.0
>STA: id=0x1f v0.8.3
>
>to STA 1.4.9 using your hex-File and method. It doesn't work for me, see 
>the dmesg output below. When I am using STA 1.3.4 from Netgear it works, 
>but I'd like to use 1.4.9 (or above) for card-based WEP in hostap-mode.
>
>Any suggestions anyone?

I managed to update my MA401. I found a version of the WinUpdate tool
that takes .hex files (the one provided by Netgear only does .oem files)
and then, I used google to finally find the proper 1.4.9 firmware
and 1.1.0 primary firmwares for this card. Mine is a 0x800c, so it's
probably not the same you need, but once you have figured out the
naming convention of the firmware files, it's easy to find them
with a search engine ;)

Ben.





From erosenst  Thu Oct 17 06:36:27 2002
From: erosenst (=?iso-8859-15?Q?Eerin_Rosenstr=F6m?=)
Date: Thu, 17 Oct 2002 16:36:27 +0300 (EET DST)
Subject: d-link dwl-660
In-Reply-To: <20021017111501.59135.17204.Mailman@sisyphus.iocaine.com>
Message-ID: <Pine.OSF.4.44.0210171630300.26815-100000@kosh.hut.fi>

What is broblem with dwl-660?


Using /lib/modules/2.4.17/pcmciaIntel PCIC probe: /i82365.o

  Vadem VG-469 rev 00 ISA-to-PCMCIA at port 0x3e2 ofs 0x00
    host opts [0]: none
    host opts [1]: none
    ISA irqs (scanned) = 9,10,11,12,14,15 status change on irq 15
Using /lib/modules/2.4.17/pcmcia/ds.o
Using /lib/modules/2.4.17/pcmcia/hostap_cs.o
hostap_cs: hostap_cs.c 0.0.0 2002-05-19 (SSH Communications Security Corp,
Jouni Malinen)
hostap_cs: (c) SSH Communications Security Corp <jkm at ssh.com>
Jan  1 00:00:07 cardmgr[62]: starting, version is 3.1.28
Jan  1 00:00:07 cardmgr[62]: watching 2 sockets
Jan  1 00:00:07 cs: memory probe 0x0d0000-0x0dffff:cardmgr[62]: ini clean.
tializing socket 0
Jan  1 00:00:07 cardmgr[62]: socket 0: PRISM2 IEEE 802.11 PC-CARD
cs: IO port probe 0x0100-0x04ff: excluding 0x1f0-0x1f7 0x2e8-0x2ef
0x3c0-0x3e7 0x480-0x48f
cs: IO port probe 0x01f8-0x02e7: clean.
cs: IO port probe 0x02f0-0x03bf: clean.
cs: IO port probe 0x03e8-0x047f: clean.
cs: IO port probe 0x0490-0x04ff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
hostap_cs: index 0x01: Vcc 5.0, irq 9, io 0x0140-0x017f
hostap_cs: Registered netdevice wlan0
wlan0: NIC: id=0x01 v5.0.4
wlan0: PRI: id=0x15 v4.4.1
wlan0: STA: id=0x1f v8.10.1
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127)
wlan0: Beacon interval setting to 100 failed
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127)
wlan0: Basic rates setting failed
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127)
wlan0: Supported rates setting failed
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127)
wlan0: DTIM period setting to 1 failed
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127)
wlan0: could not configure encryption
Jan  1 00:00:08 cardmgr[62]: executing: './network start wlan0'
Jan  1 00:00:08 cardmgr[62]: + ./network: No such file or directory
Jan  1 00:00:08 cardmgr[62]: start cmd exited with status 127
Jan  1 00:00:08 cardmgr[wlan0: hfa384x_cmd - timeout2 - reg=0x8000
62]: exiting
wlan0: hfa384x_cmd - timeout2 - reg=0x8000
Error for wirelewlan0: hfa384x_cmd - timeout - reg=0x8000
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=-110)
ss request "Set hostap_cs: wlan0: resetting card
Tx Power" (8B26) :
    SET failed on device wlawlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127)
n0 ; Operation nwlan0: Beacon interval setting to 100 failed
ot supported on wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127)
transport endpoiwlan0: Basic rates setting failed
nt.
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127)
wlan0: Supported rates setting failed
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127)
wlan0: DTIM period setting to 1 failed
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127)
wlan0: could not configure encryption
wlan0: TXRateControl setting to 0x8 failed


This is from openAP ksmith 13. friday version.

-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

                    ****  Eerin Rosenstr?m          ****
                    **    Servinmaijantie 12 F 77     **
                    **    02150 Espoo                 **
                    **    p. +358 9 4682997           **
                    ****  p.+358 40 5205030         ****

-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*




From komarek  Thu Oct 17 08:10:44 2002
From: komarek (Paul Komarek)
Date: Thu, 17 Oct 2002 11:10:44 -0400 (EDT)
Subject: hostap, DWL-520, Soekris net4201
Message-ID: <Pine.LNX.4.44L-027.0210171107480.2189-100000@unix44.andrew.cmu.edu>

Jacques,

I'm just getting started with a DWL-520 in a net4501 for use with hostap.
Which power supply did you switch to?  I have the 'default' power supply
recommend by Soerin.

-Paul Komarek

> Date: Wed, 16 Oct 2002 13:03:52 +0200
> From: Jacques Caron <Jacques.Caron at IPsector.com>
> Subject: Re: D-Link DWL-520 hangs machine.
>
> I have the same card running in 7-year old Pentium 90 system, which I
> pretty much doubt is PCI2.2 compliant. And it works flawlessly with
> FreeBSD.
>
> Note however that:
> - I've seen reports that there are actually different versions of the same
> card, which might have different behaviors in terms of compatibility;
> - I've had trouble with the same card in a Soekris box (Net4501) until I
> changed the power supply. The problems were a lot of "wi_cmd: timeout"
> and similar messages which hung the machine for a few seconds each time, and
> random complete hangs. So it looks like having not enough power or
> similar problems can cause quite some issues. This was also with FreeBSD.
>
>Jacques.





From benh  Thu Oct 17 08:17:57 2002
From: benh (Benjamin Herrenschmidt)
Date: Thu, 17 Oct 2002 17:17:57 +0200
Subject: More hostap weird behaviour
Message-ID: <20021017151757.18987@192.168.4.1>

Hi !

I'm still trying to figure out what's wrong with hostap and
so have done more tests in various conditions, but couldn't
find some reasonable explanation for the results I'm getting.

First, did any of you already tried hostap on a big endian
platform (notably a PPC) ? Just in case....

The card is a Netgear MA401 updated to pri 1.1.0 and sta 1.4.9

I've done the following tests: (the tests in "Managed" mode are
done using an Apple airport card as the Master running Apple's
MacOS software base station). Using either channel 10 or 11

 - MA401 in "Master" mode in embedded box : nothing works. It
seems I can occasionally have a good packet and _sometimes_ the
test station gets properly authenticated, but that's quite rare.
I lost more than 90% of packets imho.

 - MA401 in "Managed" mode in embedded box : nothing works, it
doesn't manage to attach to the station

 - MA401 in "Master" mode in a desktop G4 PPC machine (an Apple
dual G4 SMP). In this config, I can usually attach to the master
from my test station (test station is an Apple airport) but an
overall transfer speed test using ftp barely gives 10 to 15Kbytes
per second, it seems most packets are dropped. Using dmesg, I
see that usually, ping packets only start going through after
the driver have reduced the TX speed to 1Mb/sec.

 - MA401 in "Managed" mode in a desktop G4 PPC. Here, it seems to
work a bit better. I can attach the the AP without too much problem,
then I do an ftp test and get about 50Kbytes/sec. (Note that
the nominal throughput of this test using 2 Apple airport cards,
one in linux with orinoco driver, one doing the AP in MacOS, is
about 500KBytes/sec). So it's still 1/10 of the speed it should
do. Using iwconfig, I see that it's never doing 11Mb/sec, it
starts at 2Mb/sec after a cor reset, but drops almost immediately
to 1Mb/sec as soon as I start transfering data

 - MA401 in "Managed" mode in an x86 PC. I got similar results
as above with the G4, though speed was double (about 100Kb),
but that may just be a side effect of better luck during
negociation.

 - Same test as above, but with Windows XP instead of Linux,
using the driver provided by NetGear (despite the firmware not
matching what NetGear bundled, I tried downgrading to 1.3.4 from
netgear CD but this didn't work, WinUpdate just hung). Similar
results. It attaches to the network without much trouble, but
then, I see TX speed constantly oscillating and actual byte
throughput as well, for an average of about 100Kb/sec.

At this point, I gave up, I haven't been able to decide what's
really going on. I suspect there must be some power supply problem
on my embedded box making it not work at all, but still, the card
seems to be having problems. I'm wondering if either the 1.4.9
firmware is not good for that Netgear card, or if the card itself
is just defective (unfortunately, I don't have another one to test).

Did other people tested a Netgear MA401 (0x800c) with 1.4.9 fw ?
What kind of results did you get ?

Thanks for any tips/clues about what may be going on,
Regards,

Ben.





From Jacques.Caron  Thu Oct 17 08:18:10 2002
From: Jacques.Caron (Jacques Caron)
Date: Thu, 17 Oct 2002 17:18:10 +0200
Subject: hostap, DWL-520, Soekris net4201
Message-ID: <5.1.1.6.0.20021017171805.0381acd8@pop.mail.yahoo.com>

Since I'm in Europe, I don't use the default US power supplies :-) I had 
two power supplies where you can select the voltage and polarity. The first 
one was set at 9V and I had lots of trouble with it. The second one was set 
at 12V and works like a charm. They're both 500 mA. Don't know if just 
changing the voltage (and hence the power) did it or if there's something 
else different with the power supply, though (haven't tried the first one 
set at 12V, actually).

Hope that helps,

Jacques.

At 17:10 17/10/2002, Paul Komarek wrote:

>Jacques,
>
>I'm just getting started with a DWL-520 in a net4501 for use with hostap.
>Which power supply did you switch to?  I have the 'default' power supply
>recommend by Soerin.
>
>-Paul Komarek
>
> > Date: Wed, 16 Oct 2002 13:03:52 +0200
> > From: Jacques Caron <Jacques.Caron at IPsector.com>
> > Subject: Re: D-Link DWL-520 hangs machine.
> >
> > I have the same card running in 7-year old Pentium 90 system, which I
> > pretty much doubt is PCI2.2 compliant. And it works flawlessly with
> > FreeBSD.
> >
> > Note however that:
> > - I've seen reports that there are actually different versions of the same
> > card, which might have different behaviors in terms of compatibility;
> > - I've had trouble with the same card in a Soekris box (Net4501) until I
> > changed the power supply. The problems were a lot of "wi_cmd: timeout"
> > and similar messages which hung the machine for a few seconds each 
> time, and
> > random complete hangs. So it looks like having not enough power or
> > similar problems can cause quite some issues. This was also with FreeBSD.
> >
> >Jacques.
>
>
>_______________________________________________
>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 msmith  Thu Oct 17 08:31:05 2002
From: msmith (Michael Smith)
Date: Thu, 17 Oct 2002 11:31:05 -0400 (EDT)
Subject: hostap, DWL-520, Soekris net4201
In-Reply-To: <Pine.LNX.4.44L-027.0210171107480.2189-100000@unix44.andrew.cmu.edu>
Message-ID: <Pine.LNX.4.44.0210171130120.10412-100000@juice.ott.ctd.com>

On Thu, 17 Oct 2002, Paul Komarek wrote:

> I'm just getting started with a DWL-520 in a net4501 for use with hostap.
> Which power supply did you switch to?  I have the 'default' power supply
> recommend by Soerin.

I'm using the recommended one (12VDC, 800 mA), no problems.

Mike




From pedro.estrela  Thu Oct 17 09:50:17 2002
From: pedro.estrela (Pedro Estrela)
Date: Thu, 17 Oct 2002 17:50:17 +0100
Subject: Netgear MA401: STA v0.8.3 => STA 1.4.9
References: <3DAB314A.8FF23BB0@openline.com.br> <004201c274dc$85af71d0$2044fea9@inesc.pt> <3DAE8834.9050905@liwest.at>
Message-ID: <002e01c275fd$45cbe040$192f5451@pedropc>



> Hi Pedro!
>
> I've tried to use your method on my Netgear MA401
> NIC: id=0x8003 v1.0.0
> PRI: id=0x15 v0.3.0
> STA: id=0x1f v0.8.3
>
> to STA 1.4.9 using your hex-File and method. It doesn't work for me, see
> the dmesg output below. When I am using STA 1.3.4 from Netgear it works,
> but I'd like to use 1.4.9 (or above) for card-based WEP in hostap-mode.

Try these:
a) flash your card in windows with the 1.4.9 firmware, AND the PDA file from
netgear that's inside the /firmware directory in the driver for the MA401

b) the same, but also include the PRI firmware from netgear

c) if still doesn't work, you'll have to make some changes to the PDA file
so that it matches what 1.4.9 needs. I've done that operations in a long,
long time, and i CAN be risky. I don't have the netgear driver right now
with me, but send me the PDA file for further inspection to try to see what
is happening.

Pedro


> Oct 17 11:30:35 igate kernel: eth2: trying to read PDA from 0x007f0000:
> failed
>   Oct 17 11:30:35 igate kernel: eth2: trying to read PDA from
> 0x003f0000: failed
> Oct 17 11:30:35 igate kernel: eth2: trying to read PDA from 0x00390000: OK
> Oct 17 11:30:35 igate kernel: eth2: fid allocate, len=2364 - timeout
> Oct 17 11:30:35 igate kernel: eth2: fid allocate, len=1600 - timeout
> Oct 17 11:30:35 igate kernel: hostap_cs: Initialization failed





From jasonb  Thu Oct 17 11:28:03 2002
From: jasonb (Jason Boxman)
Date: Thu, 17 Oct 2002 14:28:03 -0400
Subject: atmel support?
In-Reply-To: <Pine.OSF.4.44.0210171403260.26815-100000@kosh.hut.fi>
References: <Pine.OSF.4.44.0210171403260.26815-100000@kosh.hut.fi>
Message-ID: <200210171428.03334.jasonb@edseek.com>

On Thursday 17 October 2002 07:14 am, Eerin Rosenstr?m wrote:
> Is there future plans to support atmel chipset (AT76C502A) with hostap
> driver?
>
> These cards are cheap and common. Big companies like d-link and smc move
> their prism2 based cards to atmel cards. Like smc2632w -> smc2632w v.2
> d-link dwl-650 -> dwl-650+.
>  It is dificult to find nowdays prism2 based cards...

I thought the DWL-650+ was a Texas Instruments chipset?

HostAP works because of special hooks in the STA firmware.  Even if these 
exist in Atmel cards, I suspect implementation would be wildly different than 
for Prism2 cards.

<snip>

-- 

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





From ml  Thu Oct 17 15:08:14 2002
From: ml (Dominique Blas)
Date: Fri, 18 Oct 2002 00:08:14 +0200
Subject: No ESSID in beacon frame
In-Reply-To: <20021015075756.B15049@jm.epitest.fi>
References: <200210150156.28738.ml@blas.net> <20021015075756.B15049@jm.epitest.fi>
Message-ID: <200210180008.14702.ml@blas.net>

Le Mardi 15 Octobre 2002 06:57, Jouni Malinen a ?crit :
> On Tue, Oct 15, 2002 at 01:56:28AM +0200, Dominique Blas wrote:
> > I didn't find any question about that in the archives.
> > So I ask it. Sorry if already posted.
>
> Search the archives for "hiding SSID" or "enhanced security".
>
> > I'd like to know if Prism Chipset / fw offers the possibility to cancel
> > ESSID broadcast in beacon frames as Airnet can do it.
>
> Yes, but ..
>
> > If yes how to activate this feature through HostAP ?
>
> .. it is not available in secondary (station) firmware. Only AP firmware
> includes enhSecurity RID that can be used to configure SSID hiding from
> beacon frames. 

And I suppose that it's not possible (or dangerous for the sanity of the 
adapter) to insert a AP secondary firmware instead of a secondary station 
firmware into a station.

>Anyway, this is not really that much "enhanced" security.
> SSID will still be available in probe requests and association
> requests.. If there are any associated stations, it is trivial to send a
> broadcast deauthentication frame and look the station associating
> again..

Trivial yes but that's a matter of probability and months for now. It's easier 
to listen to beacon frames (a tcpdump or ethereal is enough) that occurs 10 
times per second than generating a deassociation frame. So it is more likely 
that the skills of pseudo-crackers are limited to sniffing than knowing how 
to send a deassociation frame.
But that's a matter of time for the skills to improve.

Thank you Jouni,

db



From krp2  Thu Oct 17 16:36:56 2002
From: krp2 (Kevin R. Porter)
Date: Thu, 17 Oct 2002 19:36:56 -0400
Subject: WL200 + HostAP Problem
Message-ID: <200210171936.56201.krp2@bellsouth.net>

I am successfully using a Compaq WL200 PCI card with Compaq's 0.8.0 firmware 
running under a 2.4.19 kernel custom built from Mandrake 9.0 sources, 
external pcmcia-cs 3.2.1, and HostAP 2002-10-12 with the following in 
/etc/sysconfig/pcmcia:
-------------------------------------------------------------
PCMCIA=yes
PCIC=i82365
PCIC_OPTS="irq_mode=1 pci_csc=0 poll_interval=100"
-------------------------------------------------------------


The kernel was a custom build with PCMCIA turned OFF in the kernel, and a 
bunch of stuff deselected because I'd never have any use for the excess code.  

Both pcmcia_cs and HostAP were essentially vanilla builds, (I did edit the 
HostAP makefile to define the PCMCIA_PATH string, but that's the only edit.)

It does complain a bit about the firmware, but what the hey, I can connect to 
it from my laptop just fine...
-------------------------------------------------------------
hostap_cs: index 0x01: Vcc 3.3, irq 18, io 0x0100-0x013f
hostap_cs: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_config: initialized in 9520 iterations
wlan0: NIC: id=0x8002 v1.0.1
wlan0: PRI: id=0x15 v0.3.0
wlan0: STA: id=0x1f v0.8.0
wlan0: defaulting to host-based encryption as a workaround for firmware bug in 
Host AP mode WEP
Using data::nullfunc ACK workaround - firmware upgrade recommended
-------------------------------------------------------------


I would be interested to know if anyone's found a way to flash one of these 
(Compaq WL200), up to more current firmware than the old 0.8.0 Compaq had.

-Kevin





From hueiping  Thu Oct 17 20:41:05 2002
From: hueiping (Huei-Ping Chen)
Date: Thu, 17 Oct 2002 20:41:05 -0700 (PDT)
Subject: IEEE 802.1X support with Host AP driver
Message-ID: <20021018034105.2727.qmail@web40705.mail.yahoo.com>

Hi, 

I would also like to try out hostapd with winXP with MD5,
the first thing come to my mind is that, do I need a 
cisco aironet 350 card ? some document seems to indicate
that I need cisco aironet 350.

I only have two linksys cards, one goes to hostAP, one
goes to winXP, would linksys in winXP do 802.1x ?

thanks,

-- Ping



On Fri, 6 Sep 2002, Jouni Malinen wrote: 

> On Sun, Sep 01, 2002 at 09:10:10PM +0300, Jouni Malinen wrote:
>
> > I used only Xsupplicant (from www.open1x.org) in testing. So if anyone
> > would be interested in testing hostapd with IEEE 802.1X and WinXP
> > Supplicant, I would be interested in hearing whether this works. Even
> > the minimal authentication server should provide useful information and
> > it should be trivial to setup.
>
> I have now implemented the needed EAPOL state machines for the .1X
> Authenticator in hostapd (few bugs were just fixed in CVS) and I did
> some testing with WinXP as the Supplicant and FreeRADIUS as the
> Authentication Server.
>
> EAP/MD5-Challenge seems to work fine both with FreeRADIUS and the
> minimal test auth. server included in hostapd. I was able to configure
> the user identification and password for FreeRADIUS and use the same
> info on WinXP Supplicant to get the port authorized.
>
> I'm not very familiar with WinXP certificate configuration and EAP/TLS
> seemed to miss something in the client side. I was able to add the
> trusted root certificate and a client certificate, but WinXP did not
> seem to find them when Supplicant needed certificates. Anyway, since the
> authenticator PAE and backend authentication state machines are now
> fully implemented, I would assume that also EAP/TLS would work with
> WinXP--assuming one were able to add suitable certificates for it.
>
> --
> Jouni Malinen PGP id EFC895FA
>
>



--------------------------------------------------------------------------------


__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com



From Jacques.Caron  Fri Oct 18 01:53:16 2002
From: Jacques.Caron (Jacques Caron)
Date: Fri, 18 Oct 2002 10:53:16 +0200
Subject: IEEE 802.1X support with Host AP driver
In-Reply-To: <20021018034105.2727.qmail@web40705.mail.yahoo.com>
Message-ID: <5.1.1.6.0.20021018104700.02790060@pop.mail.yahoo.com>

Any card NDIS 5.1-compliant drivers will work with XP. You can recognize 
those by looking at the properties of the card in XP. If you have a 
"Wireless" tab, it's NDIS 5.1 and you'll get full support (including 
dynamic keying).

If you don't have that tab, then I suppose the authentication bit should 
still work (not sure, actually), but you won't get dynamic keying. As 
EAP-MD5 doesn't provide session keys anyway, it shouldn't be a problem.

Important thing: you have to activate "show connection icon in taskbar" or 
whatever it's called, otherwise you will never get the notifications that 
you have to enter username/password information. And XP is pretty dumb 
about it, it doesn't even have an option to save that information... :-(

Jacques.

At 05:41 AM 10/18/2002, Huei-Ping Chen wrote:
>Hi,
>
>I would also like to try out hostapd with winXP with MD5,
>the first thing come to my mind is that, do I need a
>cisco aironet 350 card ? some document seems to indicate
>that I need cisco aironet 350.
>
>I only have two linksys cards, one goes to hostAP, one
>goes to winXP, would linksys in winXP do 802.1x ?
>
>thanks,
>
>-- Ping
>
>
>
>On Fri, 6 Sep 2002, Jouni Malinen wrote:
>
> > On Sun, Sep 01, 2002 at 09:10:10PM +0300, Jouni Malinen wrote:
> >
> > > I used only Xsupplicant (from www.open1x.org) in testing. So if anyone
> > > would be interested in testing hostapd with IEEE 802.1X and WinXP
> > > Supplicant, I would be interested in hearing whether this works. Even
> > > the minimal authentication server should provide useful information and
> > > it should be trivial to setup.
> >
> > I have now implemented the needed EAPOL state machines for the .1X
> > Authenticator in hostapd (few bugs were just fixed in CVS) and I did
> > some testing with WinXP as the Supplicant and FreeRADIUS as the
> > Authentication Server.
> >
> > EAP/MD5-Challenge seems to work fine both with FreeRADIUS and the
> > minimal test auth. server included in hostapd. I was able to configure
> > the user identification and password for FreeRADIUS and use the same
> > info on WinXP Supplicant to get the port authorized.
> >
> > I'm not very familiar with WinXP certificate configuration and EAP/TLS
> > seemed to miss something in the client side. I was able to add the
> > trusted root certificate and a client certificate, but WinXP did not
> > seem to find them when Supplicant needed certificates. Anyway, since the
> > authenticator PAE and backend authentication state machines are now
> > fully implemented, I would assume that also EAP/TLS would work with
> > WinXP--assuming one were able to add suitable certificates for it.
> >
> > --
> > Jouni Malinen PGP id EFC895FA
> >
> >
>
>
>
>--------------------------------------------------------------------------------
>
>
>__________________________________________________
>Do you Yahoo!?
>Faith Hill - Exclusive Performances, Videos & More
>http://faith.yahoo.com
>_______________________________________________
>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 naif  Fri Oct 18 03:04:30 2002
From: naif (Fabio Pietrosanti naif)
Date: Fri, 18 Oct 2002 12:04:30 +0200
Subject: DWL660 not working
Message-ID: <20021018100430.GA3313@inet.it>

Hi,

i got a ISA-to-PCMCIA adapter ( perfectly working with other pcmcia card ) and
i buyed 1 DWL660 pcmcia card from d-link .

I don't find any information neither on the web neither on news archive
regarding the dwl660 and linux :|

I'm trying to setup HostAP but i got the following error:

Linux ouch 2.4.18 #8 Thu Oct 17 09:51:17 CEST 2002 i586 unknown
hostap-2002-10-12
root at ouch:/data/software/hostap-2002-10-12/utils# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/3.1/specs
Configured with: ../gcc-3.1/configure --prefix=/usr --enable-shared
--with-gnu-ld --enable-threads --verbose --target=i386-slackware-linux
--host=i386-slackware-linux
Thread model: posix
gcc version 3.1


cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x360-0x36f 0x3b8-0x3e7 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: 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: setting Vcc=50 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
hostap_cs: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_config: initialized in 3749 iterations
wlan0: NIC: id=0x01 v5.0.4
wlan0: PRI: id=0x15 v4.4.1
wlan0: STA: id=0x1f v8.10.1
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127, rid=fc33, len=2)
wlan0: Beacon interval setting to 100 failed
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127, rid=fcb3, len=2)
wlan0: Basic rates setting failed
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127, rid=fcb4, len=2)
wlan0: Supported rates setting failed
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127, rid=fc10, len=2)
wlan0: DTIM period setting to 1 failed
wlan0: LinkStatus=2 (Disconnected)
wlan0: LinkStatus=1 (Connected)


root at ouch:/data/software/hostap-2002-10-12/utils# 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

root at ouch:/data/software/hostap-2002-10-12/utils# ./hostap_diag -a wlan0

Host AP driver diagnostics information for 'wlan0'

NICID: id=0x0001 v5.0.4 (unknown)
PRIID: id=0x0015 v4.4.1
STAID: id=0x001f v8.10.1 (station firmware)

Known RIDs (Resource IDentifiers)

FC00=CNFPORTTYPE=6
FC01=CNFOWNMACADDR=00:05:5d:25:33:cd
FC02=CNFDESIREDSSID=test
FC03=CNFOWNCHANNEL=3
FC04=CNFOWNSSID=test
FC05=CNFOWNATIMWINDOW=0
FC06=CNFSYSTEMSCALE=1
FC07=CNFMAXDATALEN=2304
FC08=CNFWDSADDRESS=00:00:00:00:00:00
FC09=CNFPMENABLED=0
FC0B=CNFMULTICASTRECEIVE=1
FC0C=CNFMAXSLEEPDURATION=100
FC0D=CNFPMHOLDOVERDURATION=100
FC0E=CNFOWNNAME=
FC20=UNKNOWN1=0
FC21=UNKNOWN2=1
FC23=CNFWEPDEFAULTKEYID=2
FC25=CNFDEFAULTKEY1=<00><00>
FC26=CNFDEFAULTKEY2=<01><00>
FC27=CNFDEFAULTKEY3=<01><00>
FC28=CNFWEPFLAGS=<00><00>
FC80=GROUPADDRESSES=
FC81=CREATEIBSS=1
FC83=RTSTHRESHOLD=2347
FC84=TXRATECONTROL=15
FC85=PROMISCUOUSMODE=0
FCB1=CNFEXCLUDELONGPREAMBLE=0
FCB2=CNFAUTHENTICATIONRSPTO=<INVALID RID_WORD LEN 34>
FCE0=TICKTIME=0
FD00=MAXLOADTIME=5000
FD01=DOWNLOADBUFFER=<60><00><00><00><00><20>
FD02=PRIID=0x15 v4.4.1
FD03=PRISUPRANGE=0 0x03 2 1-1
FD04=CFIACTRANGES=1 0x02 1 1-6
FD0A=NICSERNUM=UT22411187  
FD0B=NICID=0x01 v5.0.4
FD0C=MFISUPRANGE=0 0x01 4 6-6
FD0D=CFISUPRANGE=0 0x02 1 5-6
FD10=CHANNELLIST=<ff><07>
FD11=REGULATORYDOMAINS=<10> 012A
FD12=TEMPTYPE=1
FD13=CIS=<01><03><00><00><ff><17><04><67><5a><08><ff><1d><05><01><67><5a><08><ff><15><50><05><00><44><2d><4c><69><6e><6b><00><44><2d><4c><69><6e><6b><20><41><69><72><20><44><57><4c><2d><36><36><30><20><57><69><72><65><6c><65><73><73><20><50><43><20><43><61><72><64><00><56><65><72><73><69><6f><6e><20><30><31><2e><30><31><00><00><00><00><00><00><00><00><00><00><00><00><00><00><00><00><00><00><00><00><00><ff><20><04><56><01><02><00><21><02><06><00><22><02><01><07><22><05><02><40><42><0f><00><22><05><02><80><84><1e><00><22><05><02><60><ec><53><00><22><05><02><c0><d8><a7><00><22><02><03><07><22><08><04><06><00><05><5d><25><33><cd><22><02><05><01><1a><07><03><01><e0><03><00><00><01><1b><0f><c1><01><19><76><c5><4b><d5><19><36><36><05><46><7f><ff><ff><ff><00> + 292*<ff>
FD20=STAID=0x1f v8.10.1
FD21=STASUPRANGE=0 0x04 1 6-12
FD22=MFIACTRANGES=<INVALID RID_SUPRANGE LEN 40>
FD23=CFIACTRANGES2=1 0x02 1 1-6
FD40=PORTSTATUS=3
FD41=CURRENTSSID=test
FD42=CURRENTBSSID=02:0d:b5:2d:db:c5
FD43=COMMSQUALITY=<00><00><1b><00><1b><00>
FD44=CURRENTTXRATE=2
FD45=CURRENTBEACONINTERVAL=100
FD46=CURRENTSCALETHRESHOLDS=<40><00><32><00><32><00><0a><00><02><00><06><00>
FD47=PROTOCOLRSPTIME=100
FD48=SHORTRETRYLIMIT=4
FD49=LONGRETRYLIMIT=4
FD4A=MAXTRANSMITLIFETIME=512
FD4B=MAXRECEIVELIFETIME=512
FD4C=CFPOLLABLE=0
FD4D=AUTHENTICATIONALGORITHMS=<01><00><01><00>
FD4F=PRIVACYOPTIONIMPLEMENTED=1
FD51=DBMCOMMSQUALITY=<00><00>
FD88=SCANRESULTSTABLE=<14><00>
FDC0=PHYTYPE=2
FDC1=CURRENTCHANNEL=3
FDC2=CURRENTPOWERSTATE=1
FDC3=CCAMODE=2
FDC6=SUPPORTEDDATARATES=<82><84><0b><16>
FFFF=FWID=040400.HEX<00><00>S1081000.HEX<00><00><00><00>

Unknown RIDs (Resource IDentifiers)

FC86=<00><00>
FD09=<00><00><06><00><01><00><02><00><02><00>
FD14=<03><2e><03><00><2b><00>
FD50=<2b><00>
FD52=<01><00>

Baseband proccessor (BBP) Configuration Registers

CR0 (Part/Version Code): 0 - Part=0 (unknown) Version=0 (3863 Version)
CR1 (I/O Polarity): 0 (normal setting 0)
    Phase of RX carrier rotation sense: normal rotation (CCW)
    Phase of TX carrier rotation sense: normal rotation (CCW)
    Phase of TX output clock (TXCLK) pin: NON-Inverted TXCLK
    Active level of the Transmit Ready output: TX_RDY Active 1
    Active level of the transmit enable input: TX_PE Active 1
    Active level of the Clear Channel Assessment output: CCA Active 0
    Active level of the MD_RDY output: MD_RDY Active 1
    Phase of the RX_CLK output: Non-Inverted Clk
CR2 (I Cover Code): 12 (nominally 72)
CR3 (Q Cover Code): 0 (nominally 72)
CR4 (TX Preamble Length): 128 (IEEE 802.11: 128)
CR5 (TX Signal Field): 0
    Preamble mode: Normal
    TX data rate: 00 = DBPSK - 11 chip sequence (1Mbps)
CR6 (TX Service Field): 0
CR7 (TX Length Field, High): 0
CR8 (TX Length Field, Low): 0
    TX Length Field: 0 usec
CR9 (TX Configure): 0
    CCA sample mode time: 19.9 usec
    CCA mode: CCA is based only on ED
    TX test modes: Alternating bits for carrier suppression test
    Enable TX test modes: normal operation
    Antenna choice for TX: Set AntSel low
    TX Antenna Mode: set AntSel pin to value in choice above
CR10 (RX Configure): 0
    Initial CS2 estimate: Use dot product result
    CIR estimate/Dot product clock control: on during acquisition
    SFD Time-out values: 56 usec
    MD_RDY control: After CRC16
    Force Frequency Offset Estimating in all antenna diversity timelines: disabled
    Antenna choice for RX when single antenna acquisition is selected: AntSel pin low
    Antenna acquire: dual antenna for diversity acquisition
CR11 (RX/TX Configure): 0
    Continuous internal RX 22 and 44 MHZ clocks: 0
    A/D input coupling: DC
    TX filter / CMF weight select: US
    Ping Pong Differential Encode: disabled
    CCA mode: normal CCA; CCA will immediately respond to changes in ED, CS1, and SQ1
    Precursor value in CIR estimate: 0
CR12 (A/D Test Modes 1): 0
    All DAC and A/D clock source control: normal internal clocks
    TX DAC clock: enable
    RX DAC clock: enable
    I DAC clock: enable
    Q DAC clock: enable
    RF A/D clock: enable
    I A/D clock: enable
    Q A/D clock: enable
CR13 (A/D Test Modes 2): 0
    Standby: disable
    SLEEP TX: disable
    SLEEP RX: disable
    SLEEP IQ: disable
    Analog TX Shut_down: disable
    Analog RX Shut_down: disable
    Analog Standby: disable
    Manual control of mixed signal power down signals (other CR13 bits): disable
CR14 (A/D Test Modes 3): 0
    DFS - select straight binary output of I/Q and RF A/D converters: 0
    I/Q DAC input control: normal (TX filter)
    Enable test bus into RX and TX DAC: disable
    Enable RF A/D into RX DAC: disable
    VRbit1: 0
    VRbit0: 0
CR15 (AGC GainClip): 0
CR16 (AGC Sat Cpints): 0
    AGC mid Sat counts: 0
    AGC low Sat counts: 0
CR17 (AGC Update Control): 0
    AGC update during CIR injest: disable
    AGC timer count: 0 (must be >31)
CR18 (AGC HiSat): 0
CR19 (AGC LockinLevel/CW detect threshold): 0
CR20 (AGC LockWindow, pos side): 0
CR21 (AGC Threshold): 0
CR22 (AGC Lookup Table Addr and Control): 0
CR23 (AGC Lookup Table Data): 0
CR24 (AGC LoopGain): 0
CR25 (AGC RX_IF): 0
CR26 (AGC Test Modes): 0
CR27 (AGC RX_RF Threshold): 0
CR28 (AGC Low SatAtten): 0
CR29 (AGC LockWindow, negative side): 0
CR30 (Carrier Sense 2): 0
CR31 (Manual TX Power Control): 0
CR32 (Test Modes 1): 0
CR33 (Test Modes 2): 0
CR34 (Test Bus Address): 244
CR35 (CMF Coefficient Control): 0
CR36 (Scrambler Seed, Long Preamble Option): 118
CR37 (Scrambler Seed, Short Preamble Option): 0
CR38 (ED Threshold): 0
CR39 (CMF Gain Threshold): 0
CR40 (Threshold for antenna decision): 0
CR41 (Preamble tracking loop lead coefficient): 0
CR42 (Preamble tracking loop lag coefficient): 0
CR43 (Header tracking loop lead coefficient): 0
CR44 (Header tracking loop lag coefficient): 0
CR45 (Data tracking loop lead coefficient): 0
CR46 (Data tracking loop lag coefficient): 0
CR47 (RF attenuator value): 0
CR48 (ED and SQ1 control and SQ1 scale factor): 0
CR49 (Read only register mux control for registers 50 to 63): 0
    CW RSSI threshold: 0
    CR50..CR63: 'b' value
CR50 (Test Bus Read): 0
CR51 (Signal Quality Measure Based on Carrier Tracking): 0
CR52 (Received Signal Field): 0
CR53 (Received Service Field): 0
CR54 (Received Length Field, Low): 0
CR55 (Received Length Field, High): 0
CR56 (Calculated CRC on Received Header, Low): 0
CR57 (Calculated CRC on Received Header, High): 0
CR58 (TX Power Measurement): 0
CR59 (RX Mean Power): 0
CR60 (RX_IF AGC): 0
CR61 (RX Status Reg): 0
CR62 (RSSI): 0
CR63 (RX Status Reg): 0

and in the log i'm continuosly getting this message:

wlan0: LinkStatus=1 (Connected)

Does this card is supported or there's some hack to make it working?

Regards

Fabio Pietrosanti (naif)
e-mail: naif at inet.it




From gte746m  Fri Oct 18 09:58:24 2002
From: gte746m (Seng Oon Toh)
Date: Fri, 18 Oct 2002 12:58:24 -0400 (EDT)
Subject: Setting retry limit using ioctl
In-Reply-To: <20021012180813.A30651@jm.epitest.fi>
Message-ID: <Pine.SOL.4.33.0210181256230.6402-100000@acmez.gatech.edu>

Hi,

I modified hostapd.c to try to set the retry limit to 0 using these liens

struct iwreq iwr;
iwr.u.retry.flags = IW_RETRY_LIMIT;
iwr.u.retry.value = 0;
iwr.u.retry.disabled = 0;
if (ioct(hapd.sock, SIOCGISWRETRY, &iwr) < 0) {
	perror("ioctl SIOCGISWRETRY");
	return -1;
}

When I run it I get a
ioctl SIOCGISWRETRY: No such device

What is the proper way to do this?

Thanks

Seng Oon Toh
Georgia Institute of Technology, Atlanta Georgia, 30332
Email: gte746m at prism.gatech.edu





From pedro.estrela  Fri Oct 18 10:56:38 2002
From: pedro.estrela (Pedro Estrela)
Date: Fri, 18 Oct 2002 18:56:38 +0100
Subject: DWL660 not working
References: <20021018100430.GA3313@inet.it>
Message-ID: <004c01c276cf$b4ca9b80$192f5451@pedropc>


> I don't find any information neither on the web neither on news archive
> regarding the dwl660 and linux :|
>
> I'm trying to setup HostAP but i got the following error:
>
> wlan0: NIC: id=0x01 v5.0.4
> wlan0: PRI: id=0x15 v4.4.1
> wlan0: STA: id=0x1f v8.10.1
> wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
> wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127, rid=fc33,
len=2)
...

Hello,
there is something very strange with this card,
the firmware it reports is surely not correct; in all prism2/2.5 cards used
the firmware is always at version 0.x.x or 1.x.x
and never _ever_ PRI 4.x.x or STA 8.x.x

are you sure that this is a prism card?
Pedro Estrela






From proski  Fri Oct 18 14:02:36 2002
From: proski (Pavel Roskin)
Date: Fri, 18 Oct 2002 17:02:36 -0400 (EDT)
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <20021016111727.A6201@jm.epitest.fi>
Message-ID: <Pine.LNX.4.44.0210181652140.15990-100000@marabou.research.att.com>

Hi, Jouni!

> I'm not fully sure about the proper procedure with primary image. There
> are two possibilities: 1) download primary image to RAM, initialize
> card, download station image to RAM, initialize card again; 2) download
> combined primary image and station image data to RAM, initialize card. I
> have mostly tested the second option, but it did not seem to work
> correctly. First option requires some changes to the driver code so that
> it will be able to initialize the card with only primary image and then
> perform RAM download for the station image.

I don't know how relevant it is, but the spectrum_cs driver does something 
similar.  The steps are:

1) stop firmware (just in case)
2) download primary firmware
3) run firmware
4) reset the card (hermes_reset() fails, but it's OK)
5) read the pda
6) download secondary firmware
7) patch secondary firmware directly in the card (gross, but saves us a 
read-write buffer in the memory)
8) run firmware

This logic can be found in the functions spectrum_dl_image() and
spectrum_dl_firmware().  The source of the driver can be found online:
http://www.red-bean.com/~proski/symbol/spectrum_cs.c.html

-- 
Regards,
Pavel Roskin




From jkmaline  Fri Oct 18 22:44:39 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 19 Oct 2002 08:44:39 +0300
Subject: No ESSID in beacon frame
In-Reply-To: <200210180008.14702.ml@blas.net>; from ml@blas.net on Fri, Oct 18, 2002 at 12:08:14AM +0200
References: <200210150156.28738.ml@blas.net> <20021015075756.B15049@jm.epitest.fi> <200210180008.14702.ml@blas.net>
Message-ID: <20021019084439.C7203@jm.epitest.fi>

On Fri, Oct 18, 2002 at 12:08:14AM +0200, Dominique Blas wrote:

> And I suppose that it's not possible (or dangerous for the sanity of the 
> adapter) to insert a AP secondary firmware instead of a secondary station 
> firmware into a station.

I have never head or a secondary image with AP code. AP firmware is
usually a RAM downloadable image that is loaded during initialization to
the card (and at that point it replaces the station firmware that was
loaded from flash).

-- 
Jouni Malinen                                            PGP id EFC895FA




From jkmaline  Fri Oct 18 22:52:31 2002
From: jkmaline (Jouni Malinen)
Date: Sat, 19 Oct 2002 08:52:31 +0300
Subject: d-link dwl-660
In-Reply-To: <Pine.OSF.4.44.0210171630300.26815-100000@kosh.hut.fi>; from erosenst@cc.hut.fi on Thu, Oct 17, 2002 at 04:36:27PM +0300
References: <20021017111501.59135.17204.Mailman@sisyphus.iocaine.com> <Pine.OSF.4.44.0210171630300.26815-100000@kosh.hut.fi>
Message-ID: <20021019085231.D7203@jm.epitest.fi>

On Thu, Oct 17, 2002 at 04:36:27PM +0300, Eerin Rosenstr?m wrote:

> What is broblem with dwl-660?

> wlan0: NIC: id=0x01 v5.0.4
> wlan0: PRI: id=0x15 v4.4.1
> wlan0: STA: id=0x1f v8.10.1

As far as Host AP driver is concerned, that is the problem: it is not a
Prism2/2.5/3 card. I have newer used dwl-660, but based on those version
numbers and a picture of the card, I would guess it is a relabeled Agere
card.

-- 
Jouni Malinen                                            PGP id EFC895FA




From hyrax  Fri Oct 18 23:10:34 2002
From: hyrax (Scott Stapleton)
Date: Sat, 19 Oct 2002 14:10:34 +0800
Subject: Best F/W and how to flash
Message-ID: <000901c27736$3d2d1820$03143c0a@hyrax>

Hi,

What is the best firmware version to use on a WL200 ( Prism2 )? Also, is
the flshing util windows based / linux based?

Regards,
Scott




From jasonb  Sat Oct 19 00:37:15 2002
From: jasonb (Jason Boxman)
Date: Sat, 19 Oct 2002 03:37:15 -0400
Subject: Best F/W and how to flash
In-Reply-To: <000901c27736$3d2d1820$03143c0a@hyrax>
References: <000901c27736$3d2d1820$03143c0a@hyrax>
Message-ID: <200210190337.15983.jasonb@edseek.com>

On Saturday 19 October 2002 02:10 am, Scott Stapleton wrote:
> Hi,
>
> What is the best firmware version to use on a WL200 ( Prism2 )? Also, is
> the flshing util windows based / linux based?

Flashing can only be done under Windows afaik.  You can load STA firmware into 
RAM under Linux, though, if you have the HEX STA file.

What firmware does the card have now?  You need at least STA v0.8.3 for things 
to really work.

> Regards,
> Scott
>

-- 

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





From bestb  Sat Oct 19 15:54:00 2002
From: bestb (Bruce)
Date: Sat, 19 Oct 2002 18:54:00 -0400
Subject: Config file for hostap_pci??
Message-ID: <200210191854.00741.bestb@sympatico.ca>

I have recently installed the hostap driver for a couple of machines, after 
having some trouble with the wlan-ng drivers.

These are client machines, so I am not using the hostap function; just using 
them for general client usage. The clients are connecting to an AP, from 
which they get their IP via DHCP. 

I managed to figure out (though not without some head scratching - is this 
documented??) that in order to set up a client, I would have to edit the 
/etc/pcmcia/wireless.opts file to expressly set "ESSID="any" (or "myap")", 
and "MODE="managed"". Prior to this, the interface could be brought up but I 
could not get an IP from the DHCP server. Works great now for pcmcia wireless 
card clients.

I also have a desktop with a native PCI prism2 card (the notorious D-Link 
DWL-520). As it does not use pcmcia (and there is therefore no 
/etc/pcmcia/wireless.opts file), I am not sure where to make the above 
configuration changes. 

What is the equivalent to /etc/pcmcia/wireless.opts for Prism 2.5 PCI wireless 
cards??

Thanks,

Bruce



From gallir  Sat Oct 19 16:44:47 2002
From: gallir (Ricardo Galli)
Date: Sun, 20 Oct 2002 01:44:47 +0200
Subject: Config file for hostap_pci??
In-Reply-To: <200210191854.00741.bestb@sympatico.ca>
References: <200210191854.00741.bestb@sympatico.ca>
Message-ID: <200210200138.58605.gallir@uib.es>

On Sunday 20 October 2002 00:54, Bruce shaped the electrons to shout:
> I have recently installed the hostap driver for a couple of machines, after
> having some trouble with the wlan-ng drivers.
>
> These are client machines, so I am not using the hostap function; just
> using them for general client usage. The clients are connecting to an AP,
> from which they get their IP via DHCP.
>
> I managed to figure out (though not without some head scratching - is this
> documented??) that in order to set up a client, I would have to edit the

In PCMCIA package or in the distributions, for example in Debian you could do 
it in /etc/network/interfaces. In Red Hat you can also do it via 
/etc/sysconfig/networks-scripts/ifcfg-wlanX

> /etc/pcmcia/wireless.opts file to expressly set "ESSID="any" (or "myap")",
> and "MODE="managed"". Prior to this, the interface could be brought up but
> I could not get an IP from the DHCP server. Works great now for pcmcia
> wireless card clients.

...or, you can also do it in the PCMCIA conf files... as you did it.

>
> I also have a desktop with a native PCI prism2 card (the notorious D-Link
> DWL-520). As it does not use pcmcia (and there is therefore no
> /etc/pcmcia/wireless.opts file), I am not sure where to make the above
> configuration changes.
>
> What is the equivalent to /etc/pcmcia/wireless.opts for Prism 2.5 PCI
> wireless cards??

See above.


-- 
  ricardo galli       GPG id C8114D34
       A paperless office has about as much a chance as a paperless bathroom



From milli  Sat Oct 19 22:27:20 2002
From: milli (Michael Milligan)
Date: Sat, 19 Oct 2002 23:27:20 -0600
Subject: Config file for hostap_pci??
References: <200210191854.00741.bestb@sympatico.ca> <200210200138.58605.gallir@uib.es>
Message-ID: <3DB23EB8.3050702@acmeps.com>

Ricardo Galli wrote:
> On Sunday 20 October 2002 00:54, Bruce shaped the electrons to shout:
> 
>>I have recently installed the hostap driver for a couple of machines, after
>>having some trouble with the wlan-ng drivers.
>>
>>These are client machines, so I am not using the hostap function; just
>>using them for general client usage. The clients are connecting to an AP,
>>from which they get their IP via DHCP.
>>
>>I managed to figure out (though not without some head scratching - is this
>>documented??) that in order to set up a client, I would have to edit the
> 
> 
> In PCMCIA package or in the distributions, for example in Debian you could do 
> it in /etc/network/interfaces.

For example, add something like this to bottom of /etc/network/interfaces, 
fix up <ID> and 1234-5678-9A (or delete the key line if you don't run WEP)..

# Wireless interface (hostap_pci)
auto wlan0
iface wlan0 inet dhcp
     pre-up /sbin/modprobe hostap_pci || true
     pre-up /sbin/iwconfig wlan0 mode Master essid <ID> channel 1
     pre-up /sbin/iwconfig wlan0 key 1234-5678-9A

Regards,
Mike

-- 
Michael Milligan  --  Free Agent  --  milli at acmeps.com




From gallir  Sun Oct 20 01:14:01 2002
From: gallir (Ricardo Galli)
Date: Sun, 20 Oct 2002 10:14:01 +0200
Subject: Config file for hostap_pci??
In-Reply-To: <3DB23EB8.3050702@acmeps.com>
References: <200210191854.00741.bestb@sympatico.ca> <200210200138.58605.gallir@uib.es> <3DB23EB8.3050702@acmeps.com>
Message-ID: <200210201014.01216.gallir@uib.es>

On Sunday 20 October 2002 07:27, Michael Milligan shaped the electrons to 
shout:
> For example, add something like this to bottom of /etc/network/interfaces,
> fix up <ID> and 1234-5678-9A (or delete the key line if you don't run
> WEP)..
>
> # Wireless interface (hostap_pci)
> auto wlan0
> iface wlan0 inet dhcp
>      pre-up /sbin/modprobe hostap_pci || true
>      pre-up /sbin/iwconfig wlan0 mode Master essid <ID> channel 1
>      pre-up /sbin/iwconfig wlan0 key 1234-5678-9A

There is no need of the pre-up commands for setting up iwconfig's paramaters. 
For example in my laptop I have:

auto eth1
iface eth1 inet dhcp
        wireless_essid  Antoli
        wireless_mode   Managed
        wireless_key    s:mykey
        wireless_rate   auto
        wireless_nick   sofi
#       wireless_power  period 2
#       wireless_power  1
#       wireless_power  timeout 300u all


-- 
  ricardo galli       GPG id C8114D34
       A paperless office has about as much a chance as a paperless bathroom



From hyrax  Sun Oct 20 07:03:32 2002
From: hyrax (Scott Stapleton)
Date: Sun, 20 Oct 2002 22:03:32 +0800
Subject: Setting txpower above the power of your card
Message-ID: <000001c27841$7b6d6750$04143c0a@hyrax>

Hi,

After setting hostap up, I noticed the default txpower from my card was
4dbm ( 2.5mW ). I procedded to set my card to 20dbm ( 100mW ), as this
is what it outputs ( WL200 ). I noticed the NS graph on my lappy shoot
up, as expected.

I then thought I'd try setting it to 150mW to see what happened. I never
expected it to increase, but it did somewhat. I then proceded to try
30mW, then 100mW again. The signal did not increase this time after I
changed from 30mW to 100mW.

Is it possible to overpower these cards? I have not used the card a lot
since, but it still seems to be working. I only left it at the 150mW for
30 sec's max. 

Is it possible I have damaged the card.

A friend did a similar thing previously and left the power set higher
for a much longer period ( days even ). His card is a Dlink running
HostAP and the box now dies and a reset is needed to get it working
again.

Whats the chance of damage and if it is possible, why is it allowed,
either by the card or driver?

Regards,
Scott




From bestb  Sun Oct 20 08:09:47 2002
From: bestb (Bruce Best CRO)
Date: Sun, 20 Oct 2002 11:09:47 -0400
Subject: Config file for hostap_pci??
Message-ID: <55675C2D7AA8D411A94500508B66062D0345C89A@CHEETAH>

Thanks! 

By the way, using Michael's suggestions worked, but not Ricardo's (I
received an error regarding the essid line). Not sure if this is due to the
driver being used; I note Ricardo referred to eth1, so presumably you are
using the kernel drivers, not hostap or wlan-ng.

As it turns out, I may have been a bit hasty blaming the wlan-ng drivers for
my connection problems, as the hostap driver has the same symptoms (my
problem is with trying to establish a connection to a Citrix server).


Bruce



From gallir  Sun Oct 20 09:52:30 2002
From: gallir (Ricardo Galli)
Date: Sun, 20 Oct 2002 18:52:30 +0200
Subject: Config file for hostap_pci??
In-Reply-To: <55675C2D7AA8D411A94500508B66062D0345C89A@CHEETAH>
References: <55675C2D7AA8D411A94500508B66062D0345C89A@CHEETAH>
Message-ID: <200210201852.30959.gallir@uib.es>

On Sunday 20 October 2002 17:09, Bruce Best (CRO) shaped the electrons to 
shout:
> Thanks!
>
> By the way, using Michael's suggestions worked, but not Ricardo's (I
> received an error regarding the essid line). Not sure if this is due to the
> driver being used; I note Ricardo referred to eth1, so presumably you are
> using the kernel drivers, not hostap or wlan-ng.

Yup, it was a Debian on an Apple iBook (I just wantet to show the interfaces' 
file). 

But the following is a Debian with hostap, running as Master.

/etc/network/interfaces
...
auto wlan0

iface wlan0 inet static
    address 192.168.0.1
    netmask 255.255.255.0
    network 192.168.0.0

/etc/pcmcia/wireless.opts

*,*,*,*)
    INFO="Red Antoli"
    ESSID="Antoli"
    MODE="Master"
    RATE="auto"
    CHANNEL="11"
    KEY="s:my_key"
    ;;



-- 
  ricardo galli       GPG id C8114D34
       A paperless office has about as much a chance as a paperless bathroom



From TroyMcClure  Sun Oct 20 12:56:58 2002
From: TroyMcClure (Martin Troester)
Date: Sun, 20 Oct 2002 21:56:58 +0200
Subject: Problems with hostap_plx and US Robotics 2415
Message-ID: <19598086460.20021020215658@web.de>

Hi,

I am currently having trouble getting a US Robotics 2410 PC-card
working in a US Robotics 2415 PC-Card/PCI-bridge. I followed the
installation description in the README files and in
http://www.trekweb.com/~jasonb/articles/linux_wireless2.shtml.

I have to admit that I am relatively new to this topic, since up to
this point all wireless-adapters I used were pure PCMCIA-cards in a
notebook, working without any problem with the linux-ng drivers. So if
this problem is well-known or if I am annoying anyone with this mail,
please excuse me for this, but I could not find any information on
this problem searching the web and newsgroups with google.

The scenario:

PC 1 (Linux)
- Debian 3.0 r0 woody - Kernel 2.4.18
- hostap-2002-10-12.tar as hostap driver source
- US-Robotics PC-Card/PCI adapter (equiv. to PLX) with 2410 PC Card
- wireless tools 23-2

PC 2 (Windows)
- Windows XP Professional
- Compaq WL 1000 PCMCIA Card

For both PCs the drivers have been set up properly. The output for the
Linux PC after modprobe hostap_plx:
======================================================================
hostap_plx: hostap_plx.c 0.0.0 2002-10-12 (SSH Communications Security
Corp, Jouni Malinen)
hostap_plx: (c) Jouni Malinen <jkmaline at cc.hut.fi>
PLX 9052 PCI/PCMCIA adapter: mem=0xfedfe000, plx_io=0xfc00 irq=10,
pccard_io=0xfc00
hostap_plx: Registered netdevice wlan0
wlan0: NIC: id=0x8002 v1.0.0
wlan0: PRI: id=0x15 v0.3.0
wlan0: STA: id=0x1f v0.7.6
======================================================================

After that, I assign:

======================================================================
ifconfig wlan0 192.168.0.1
iwconfig wlan0 essid bla
iwconfig wlan0 channel 11
iwconfig wlan0 mode Master
======================================================================

With this, I get when calling iwconfig wlan0:

======================================================================
iwconfig wlan0
wlan0     IEEE 802.11-DS  ESSID:"bla"
          Mode:Master  Frequency:2.422GHz
          Access Point: 00:90:D2:08:50:86
          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
======================================================================

Letting the Windows XP PC scan for available nets (all
encryption/authorization etc. deactivated) I find the net "bla"
without any problems in the list of available nets. Assigning the
WinXP pc-card a static IP like 192.168.0.2, it should then be no
problem to get the two devices communicating, but now I don't know how
to proceed: both cards have found each other, are both transmitting on
the same channel #11, but it is not possible to PING each other.

What I can say is that the Windows XP system with the COMPAQ card is
working in different wireless environments without any problems.

One of my colleagues has the same problem with getting the USR PC-Card
in the PLX-Adapter to work, but using the wireless-ng drivers. It is
exactly the same phenomenon: both cards find the net, but cannot
communicate, for example by simply sending pings to the other side.

I really do not know what to try any more, so please let me know if
you have any suggestions about how to get the PLX-Card version
running.

Thanks!

Regards
Martin




From jasonb  Sun Oct 20 13:42:26 2002
From: jasonb (Jason Boxman)
Date: Sun, 20 Oct 2002 16:42:26 -0400
Subject: Problems with hostap_plx and US Robotics 2415
In-Reply-To: <19598086460.20021020215658@web.de>
References: <19598086460.20021020215658@web.de>
Message-ID: <200210201642.27301.jasonb@edseek.com>

On Sunday 20 October 2002 03:56 pm, Martin Troester wrote:
> Hi,
>
<snip>
> The scenario:
>
> PC 1 (Linux)
> - Debian 3.0 r0 woody - Kernel 2.4.18
> - hostap-2002-10-12.tar as hostap driver source
> - US-Robotics PC-Card/PCI adapter (equiv. to PLX) with 2410 PC Card
> - wireless tools 23-2

You can probably snag wireless tools v25 from Sarge, but that's not the 
problem. :)

(Now that I think about it, if you get wireless tools v25 iwconfig will 
probably complain your kernel wireless extensions aren't recent enough.  You 
need to patch a 2.4.20-pre* kernel to get the latest wireless extensions, 
version 15.)

> PC 2 (Windows)
> - Windows XP Professional
> - Compaq WL 1000 PCMCIA Card
>
<snip>
> hostap_plx: Registered netdevice wlan0
> wlan0: NIC: id=0x8002 v1.0.0
> wlan0: PRI: id=0x15 v0.3.0
> wlan0: STA: id=0x1f v0.7.6

Your STA firmware revision is suspiciously low.  I'd recommend upgrading to at 
least revision 0.8.3.  You can use a utility on the Windows box to do the 
flashing, since both cards are just PC Cards.  Having to flash a PCI card is 
a bit more challenging, since you may need to move it to a Windows box -- but 
you won't have that problem. :)

<snip>
> Letting the Windows XP PC scan for available nets (all
> encryption/authorization etc. deactivated) I find the net "bla"
> without any problems in the list of available nets. Assigning the
> WinXP pc-card a static IP like 192.168.0.2, it should then be no
> problem to get the two devices communicating, but now I don't know how
> to proceed: both cards have found each other, are both transmitting on
> the same channel #11, but it is not possible to PING each other.

My guess is it's the firmware revision.  If I'm wrong I know someone will set 
me straight, though.

<snip>
> I really do not know what to try any more, so please let me know if
> you have any suggestions about how to get the PLX-Card version
> running.

On a fact finding note, it's interesting to see your PLX card works as PLX.  I 
talked to someone a few weeks ago who's PLX-style card was recognized as a PC 
Card and he used the usual PC Card stuff to initialize it instead.

Anyone know how/when this difference presents itself?

> Thanks!
>
> Regards
> Martin

-- 

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





From jasonb  Sun Oct 20 13:47:07 2002
From: jasonb (Jason Boxman)
Date: Sun, 20 Oct 2002 16:47:07 -0400
Subject: Setting txpower above the power of your card
In-Reply-To: <000001c27841$7b6d6750$04143c0a@hyrax>
References: <000001c27841$7b6d6750$04143c0a@hyrax>
Message-ID: <200210201647.07818.jasonb@edseek.com>

On Sunday 20 October 2002 10:03 am, Scott Stapleton wrote:
> Hi,
>
> After setting hostap up, I noticed the default txpower from my card was
> 4dbm ( 2.5mW ). I procedded to set my card to 20dbm ( 100mW ), as this
> is what it outputs ( WL200 ). I noticed the NS graph on my lappy shoot
> up, as expected.
>
> I then thought I'd try setting it to 150mW to see what happened. I never
> expected it to increase, but it did somewhat. I then proceded to try
> 30mW, then 100mW again. The signal did not increase this time after I
> changed from 30mW to 100mW.

I had a similiar experience with my LinkSys (pre BroadCom chipset) card.  I 
can change the txpower to its max, 32mW, and my signal quality increases on 
my laptop, but then I can change it to anything from 1, to 31mW and there is 
no decrease in signal quality.  It's very odd.  It's like the initial 
increase just maxes the card (or increases it noticably) and then thereafter 
no further modifications are acknowledged.

> Is it possible to overpower these cards? I have not used the card a lot
> since, but it still seems to be working. I only left it at the 150mW for
> 30 sec's max.
>
> Is it possible I have damaged the card.

I've wondered about that myself.

> A friend did a similar thing previously and left the power set higher
> for a much longer period ( days even ). His card is a Dlink running
> HostAP and the box now dies and a reset is needed to get it working
> again.

I had that happen with the HostAP release immediately before 2002-10-12.  I 
forget I did, it mightly been playing with the power, but I had to turn the 
box off and on a couple times.  The card simply refused to work.  I went back 
to the May release, nothing, then finally it started working again an hour 
later.  I can't explain what had happened.  At the time, the cards seemed 
partially fried, but it's working 100% since it came back to me.

> Whats the chance of damage and if it is possible, why is it allowed,
> either by the card or driver?
>
> Regards,
> Scott

-- 

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





From jasonb  Sun Oct 20 13:49:34 2002
From: jasonb (Jason Boxman)
Date: Sun, 20 Oct 2002 16:49:34 -0400
Subject: Config file for hostap_pci??
In-Reply-To: <200210201014.01216.gallir@uib.es>
References: <200210191854.00741.bestb@sympatico.ca> <3DB23EB8.3050702@acmeps.com> <200210201014.01216.gallir@uib.es>
Message-ID: <200210201649.34109.jasonb@edseek.com>

On Sunday 20 October 2002 04:14 am, Ricardo Galli wrote:
> On Sunday 20 October 2002 07:27, Michael Milligan shaped the electrons to
>
<snip>
> auto eth1
> iface eth1 inet dhcp
>         wireless_essid  Antoli
>         wireless_mode   Managed
>         wireless_key    s:mykey
>         wireless_rate   auto
>         wireless_nick   sofi
> #       wireless_power  period 2
> #       wireless_power  1
> #       wireless_power  timeout 300u all

It was always my impression those needed to be prefixed with "up":

auto wlan0
iface wlan0 inet static
        address 192.168.1.1
        netmask 255.255.255.0
        up /sbin/iwconfig wlan0 essid vortex && \
        /sbin/iwconfig wlan0 channel 1

The above works for me on boot for a PCI card.

-- 

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





From hueiping  Sun Oct 20 14:01:11 2002
From: hueiping (Huei-Ping Chen)
Date: Sun, 20 Oct 2002 14:01:11 -0700 (PDT)
Subject: IEEE 802.1X support with Host AP driver
In-Reply-To: <5.1.1.6.0.20021018104700.02790060@pop.mail.yahoo.com>
Message-ID: <20021020210111.6596.qmail@web40708.mail.yahoo.com>

Jacques,

great! thanks for the information, I will give it a try
with the linksys card, 

-- Ping

--- Jacques Caron <Jacques.Caron at IPsector.com> wrote:
> Any card NDIS 5.1-compliant drivers will work with XP. You can recognize 
> those by looking at the properties of the card in XP. If you have a 
> "Wireless" tab, it's NDIS 5.1 and you'll get full support (including 
> dynamic keying).
> 
> If you don't have that tab, then I suppose the authentication bit should 
> still work (not sure, actually), but you won't get dynamic keying. As 
> EAP-MD5 doesn't provide session keys anyway, it shouldn't be a problem.
> 
> Important thing: you have to activate "show connection icon in taskbar" or 
> whatever it's called, otherwise you will never get the notifications that 
> you have to enter username/password information. And XP is pretty dumb 
> about it, it doesn't even have an option to save that information... :-(
> 
> Jacques.
> 
> At 05:41 AM 10/18/2002, Huei-Ping Chen wrote:
> >Hi,
> >
> >I would also like to try out hostapd with winXP with MD5,
> >the first thing come to my mind is that, do I need a
> >cisco aironet 350 card ? some document seems to indicate
> >that I need cisco aironet 350.
> >
> >I only have two linksys cards, one goes to hostAP, one
> >goes to winXP, would linksys in winXP do 802.1x ?
> >
> >thanks,
> >
> >-- Ping
> >
> >
> >
> >On Fri, 6 Sep 2002, Jouni Malinen wrote:
> >
> > > On Sun, Sep 01, 2002 at 09:10:10PM +0300, Jouni Malinen wrote:
> > >
> > > > I used only Xsupplicant (from www.open1x.org) in testing. So if anyone
> > > > would be interested in testing hostapd with IEEE 802.1X and WinXP
> > > > Supplicant, I would be interested in hearing whether this works. Even
> > > > the minimal authentication server should provide useful information and
> > > > it should be trivial to setup.
> > >
> > > I have now implemented the needed EAPOL state machines for the .1X
> > > Authenticator in hostapd (few bugs were just fixed in CVS) and I did
> > > some testing with WinXP as the Supplicant and FreeRADIUS as the
> > > Authentication Server.
> > >
> > > EAP/MD5-Challenge seems to work fine both with FreeRADIUS and the
> > > minimal test auth. server included in hostapd. I was able to configure
> > > the user identification and password for FreeRADIUS and use the same
> > > info on WinXP Supplicant to get the port authorized.
> > >
> > > I'm not very familiar with WinXP certificate configuration and EAP/TLS
> > > seemed to miss something in the client side. I was able to add the
> > > trusted root certificate and a client certificate, but WinXP did not
> > > seem to find them when Supplicant needed certificates. Anyway, since the
> > > authenticator PAE and backend authentication state machines are now
> > > fully implemented, I would assume that also EAP/TLS would work with
> > > WinXP--assuming one were able to add suitable certificates for it.
> > >
> > > --
> > > Jouni Malinen PGP id EFC895FA
> > >
> > >
> >
> >
> >
>
>--------------------------------------------------------------------------------
> >
> >
> >__________________________________________________
> >Do you Yahoo!?
> >Faith Hill - Exclusive Performances, Videos & More
> >http://faith.yahoo.com
> >_______________________________________________
> >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
> 


__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/



From milli  Sun Oct 20 17:56:05 2002
From: milli (Michael Milligan)
Date: Sun, 20 Oct 2002 18:56:05 -0600
Subject: Config file for hostap_pci??
References: <200210191854.00741.bestb@sympatico.ca> <3DB23EB8.3050702@acmeps.com> <200210201014.01216.gallir@uib.es> <200210201649.34109.jasonb@edseek.com>
Message-ID: <3DB350A5.9080406@acmeps.com>

Jason Boxman wrote:
> On Sunday 20 October 2002 04:14 am, Ricardo Galli wrote:
>>On Sunday 20 October 2002 07:27, Michael Milligan shaped the electrons to
>>
> 
> <snip>
> 
>>auto eth1
>>iface eth1 inet dhcp
>>        wireless_essid  Antoli
>>        wireless_mode   Managed
>>        wireless_key    s:mykey
>>        wireless_rate   auto
>>        wireless_nick   sofi
>>#       wireless_power  period 2
>>#       wireless_power  1
>>#       wireless_power  timeout 300u all
> 
> 
> It was always my impression those needed to be prefixed with "up":
> 
> auto wlan0
> iface wlan0 inet static
>         address 192.168.1.1
>         netmask 255.255.255.0
>         up /sbin/iwconfig wlan0 essid vortex && \
>         /sbin/iwconfig wlan0 channel 1
> 

As I understand them, both approaches are essentially the same, and 
unfortunately both do *not* work reliably for me.  Unless you also add this 
to the recipe:

   up sleep 1 || /sbin/iwpriv wlan0 reset 2 || true

This could certainly just be a quirk of the card (Intel 2011B PCI), but 
using pre-up statements work for me.

Regards,
Mike

-- 
Michael Milligan  --  Free Agent  --  milli at acmeps.com




From jharana  Sun Oct 20 20:42:35 2002
From: jharana (Jharana Mehta)
Date: Mon, 21 Oct 2002 09:12:35 +0530
Subject: driver performs poorly in hostapd mode
References: <200210150156.28738.ml@blas.net> <20021015075756.B15049@jm.epitest.fi> <200210180008.14702.ml@blas.net> <20021019084439.C7203@jm.epitest.fi>
Message-ID: <3DB37859.975F39D3@mahindrabt.com>

Hi Jouni,
earlier I had written a mail about the slow performance of Linksys WPC11 cards
when the hostap driver was compiled in hostapd mode. I was using the sept 2002
release of the driver
I downloaded the latest release 2002-10-12 and that works fine in hostapd mode.

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
-------------- 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/20021021/4696f04a/attachment.vcf 


From imp  Mon Oct 21 01:33:15 2002
From: imp (=?ks_c_5601-1987?B?udrI77+t?=)
Date: Mon, 21 Oct 2002 17:33:15 +0900
Subject: Are there any plan for 1f ? 
Message-ID: <HIEILNBGFIFLDLBJCOLAMEHACCAA.imp@airlinktek.com>

Dear  All

Are there any plan to implementation for IAPP (802.11f) standard into hostap ? 

I think It is important aspect of hostap functionality isn't it ? 

Thanks for your attention..

Park.


From xdhuang  Mon Oct 21 06:09:13 2002
From: xdhuang (Huang Xiaodong)
Date: 21 Oct 2002 21:09:13 +0800
Subject: Active and Passive Scan
Message-ID: <20021021210913.50775.qmail@eyou.com>

Where can I control the station's scan mode in the hostap driver program ,
active or passive?

#define PASSIVE_SCAN          1
#define ACTIVE_SCAN           1

I can find the above defination, but didn't find their references or caller.
Where can I find them?

Thanks in advance.
Huang Xiaodong





--http://www.eyou.com
--??????????????????????  ????????  ????????  ????????  ????????...????????





From don  Sun Oct 20 23:31:59 2002
From: don (don)
Date: 21 Oct 2002 07:31:59 +0100
Subject: continuous transmit utility
In-Reply-To: <20021021005700.25274.72852.Mailman@sisyphus.iocaine.com>
References: <20021021005700.25274.72852.Mailman@sisyphus.iocaine.com>
Message-ID: <1035181920.28295.23.camel@k7.a>

I am experimenting with long distance networking using various aerials
connected to wireless LAN cards. There is an Intersil utility that puts
the card into continuous transmit mode for testing purposes. But it only
works with windows.

The Intersil utility just seems to send packets with no gaps between
them but still using spread spectrum modulation. This gives a very wide
bandwidth signal that isn't ideal for signal strength tests.

Is there a utility to do this with Linux. Ideally I would like to send
an unmodulated carrier, but continuous packets will do.

If there isn't a utility already available, is there a suitable routine
in the drivers that could be called repetitively to send test packets?



Don Magee






From xdhuang  Mon Oct 21 07:40:44 2002
From: xdhuang (Huang Xiaodong)
Date: 21 Oct 2002 22:40:44 +0800
Subject: How to select a special AP to communicate in a multiple APs' area?
Message-ID: <20021021224044.53242.qmail@eyou.com>

Hi,

I want to set a flag bit in the beacon frame's reserved fileds of APs. In this
way the STA's can use the special AP specified by the flag bit.

I think it is easy to set the flag bit in the beacon frame in hostap driver,
but how to make STAs to select a specified AP to communicate according to the
flag bit.

Any one can tell me?

Thanks a lot.

Huang Xiaodong





--http://www.eyou.com
--??????????????????????  ????????  ????????  ????????  ????????...????????





From collord  Mon Oct 21 08:07:51 2002
From: collord (Jerritt Collord)
Date: Mon, 21 Oct 2002 08:07:51 -0700
Subject: d-link dwl-660
In-Reply-To: <20021019085231.D7203@jm.epitest.fi>
References: <20021017111501.59135.17204.Mailman@sisyphus.iocaine.com>
	<Pine.OSF.4.44.0210171630300.26815-100000@kosh.hut.fi>
	<20021019085231.D7203@jm.epitest.fi>
Message-ID: <20021021080751.746ba3c5.collord@linuxfund.org>

Sorry, I couldn't find pictures of this card. Link? (Unless you're talking about the 660W CF card?)

Note that DLink has entries in the FCC database for cards based on Atmel
(PCMCIA) and both ADMtek and Broadcom (Cardbus) chipsets, but no Agere. 

Is it Cardbus or PCMCIA (or CF)? What does the CIS report via cardctl?

Jerritt

> As far as Host AP driver is concerned, that is the problem: it is not a
> Prism2/2.5/3 card. I have newer used dwl-660, but based on those version
> numbers and a picture of the card, I would guess it is a relabeled Agere
> card.




From naif  Mon Oct 21 08:28:51 2002
From: naif (Fabio Pietrosanti naif)
Date: Mon, 21 Oct 2002 17:28:51 +0200
Subject: d-link dwl-660
In-Reply-To: <20021021080751.746ba3c5.collord@linuxfund.org>
References: <20021017111501.59135.17204.Mailman@sisyphus.iocaine.com> <Pine.OSF.4.44.0210171630300.26815-100000@kosh.hut.fi> <20021019085231.D7203@jm.epitest.fi> <20021021080751.746ba3c5.collord@linuxfund.org>
Message-ID: <20021021152851.GH8404@inet.it>

I buyed it from an italian reseller of D-link:

http://www.dlink.it/prodotti/prod/DWL-660/view.html

Fabio Pietrosanti (naif)
naif at inet.it

On Mon, Oct 21, 2002 at 08:07:51AM -0700, Jerritt Collord wrote:
> 
> Sorry, I couldn't find pictures of this card. Link? (Unless you're talking about the 660W CF card?)
> 
> Note that DLink has entries in the FCC database for cards based on Atmel
> (PCMCIA) and both ADMtek and Broadcom (Cardbus) chipsets, but no Agere. 
> 
> Is it Cardbus or PCMCIA (or CF)? What does the CIS report via cardctl?
> 
> Jerritt




From collord  Mon Oct 21 08:59:09 2002
From: collord (Jerritt Collord)
Date: Mon, 21 Oct 2002 08:59:09 -0700
Subject: d-link dwl-660
In-Reply-To: <20021021152851.GH8404@inet.it>
References: <20021017111501.59135.17204.Mailman@sisyphus.iocaine.com>
	<Pine.OSF.4.44.0210171630300.26815-100000@kosh.hut.fi>
	<20021019085231.D7203@jm.epitest.fi>
	<20021021080751.746ba3c5.collord@linuxfund.org>
	<20021021152851.GH8404@inet.it>
Message-ID: <20021021085909.53ebf137.collord@linuxfund.org>


The card picture is of what is sold as the 650+ in the US... based on the TI chipset, capable of the proprietary 22Mb PBCC baseband.  Definitely not HostAP material.

Jerritt

> I buyed it from an italian reseller of D-link:
> 
> http://www.dlink.it/prodotti/prod/DWL-660/view.html
> 
> Fabio Pietrosanti (naif)
> naif at inet.it




From muditgoel  Mon Oct 21 11:38:54 2002
From: muditgoel (Mudit Goel)
Date: Mon, 21 Oct 2002 11:38:54 -0700 (PDT)
Subject: ERROR: CardServices release does not match!
Message-ID: <20021021183854.32626.qmail@web13113.mail.yahoo.com>

Hi,

I am new to hostap and was trying to install and run
hostap for the first time, when I get the above
runtime error. This is what I did:

hardware: Toshiba satellite 1555CDS laptop
linux: Mandrake 8.1 (comes with kernel 2.4.8)
hostap version: I downloaded the release a month ago.
I think it is the 2002-09-12 release.
pcmcia card: Proxim rangelan ds 8430

I did the following steps:
1. make pccard as <user>
2. make install_pccard as <root>

I did not get any build related errors. Now I
restarted the cardmgr services using:
> service pcmcia restart

The log entries in /var/logs/message is:
--------------------------------------------------
Oct 20 13:08:06 toshiba cardmgr[7198]: exiting
Oct 20 13:08:06 toshiba kernel: unloading PCMCIA Card
Services
Oct 20 13:08:07 toshiba kernel: Linux PCMCIA Card
Services 3.1.29
Oct 20 13:08:07 toshiba kernel:   kernel build:
2.4.8-26mdk #1 Sun Sep 23 17:06:39 CEST 2001
Oct 20 13:08:07 toshiba kernel:   options:  [pci]
[cardbus] [apm]
Oct 20 13:08:07 toshiba kernel: Intel ISA/PCI/CardBus
PCIC probe:
Oct 20 13:08:07 toshiba kernel: PCI: No IRQ known for
interrupt pin A of device 00:13.0. Please try using
pci=biosirq.
Oct 20 13:08:07 toshiba kernel: PCI: No IRQ known for
interrupt pin B of device 00:13.1. Please try using
pci=biosirq.
Oct 20 13:08:07 toshiba kernel:   Toshiba ToPIC97 rev
07 PCI-to-CardBus at slot 00:13, mem 0x10000000
Oct 20 13:08:07 toshiba kernel:     host opts [0]:
[slot 0xf0] [ccr 0x11] [cdr 0x86] [rcr 0x00] [no pci
irq] [lat 168/176] [bus 20/20]
Oct 20 13:08:07 toshiba kernel:     host opts [1]:
[slot 0xf0] [ccr 0x21] [cdr 0x86] [rcr 0x00] [no pci
irq] [lat 168/176] [bus 21/21]
Oct 20 13:08:07 toshiba kernel:     ISA irqs (default)
= 4,5,7,9,10 polling interval = 1000 ms
Oct 20 13:08:07 toshiba cardmgr[7264]: starting,
version is 3.1.29
Oct 20 13:08:07 toshiba cardmgr[7264]: watching 2
sockets

------------------------------------------------

Then I inserted the proxim rangelan ds 8430 card (this
seems to be supported in the host_conf file) and got
the following entries in the log:

-------------------------------------------------

Oct 20 13:09:01 toshiba cardmgr[7264]: socket 0:
Proxim RangeLAN
Oct 20 13:09:01 toshiba kernel: cs: memory probe
0x0d0000-0x0dffff: clean.
Oct 20 13:09:01 toshiba cardmgr[7264]: executing:
'modprobe hostap_cs'
Oct 20 13:09:02 toshiba kernel: hostap_cs: hostap_cs.c
0.0.0 2002-09-12 (SSH Communications Security Corp,
Jouni Malinen)
Oct 20 13:09:02 toshiba kernel: hostap_cs: (c) Jouni
Malinen <jkmaline at cc.hut.fi>
Oct 20 13:09:02 toshiba kernel: hostap_cs:
CardServices release does not match!
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
init_module: Operation not permitted
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o: insmod
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o failed
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o: insmod
hostap_cs failed
Oct 20 13:09:02 toshiba cardmgr[7264]: + Hint: insmod
errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
Oct 20 13:09:02 toshiba cardmgr[7264]: modprobe exited
with status 255
Oct 20 13:09:02 toshiba cardmgr[7264]: executing:
'insmod /lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o'
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_handle_sta_release_R27df6133
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_free_data_R11be3a66
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_netif_stop_queues_R453794d8
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_handle_sta_rx_R360fd54c
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_init_proc_Reb9a0dd6
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_handle_sta_tx_exc_R1bdddfc1
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_set_string_R6b689ee2
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_set_encryption_Rcc6867c1
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_set_word_R0b32ec9f
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_remove_proc_R57e744ee
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_handle_sta_crypto_R02fc42b1
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_rx_R4714f058
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_netif_wake_queues_R791e64c0
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol
hostap_check_sta_fw_version_Rb6f48fad
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_is_sta_assoc_R9496031d
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_handle_sta_tx_R1e7aff02
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_setup_dev_Rdf897f59
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_get_porttype_R2e8dc8d6
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_init_data_Ra5d3e76d
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_get_stats_Rbcf6483b
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_dump_rx_header_R27a069d6
Oct 20 13:09:02 toshiba cardmgr[7264]: +
/lib/modules/2.4.8-26mdk/pcmcia/hostap_cs.o:
unresolved symbol hostap_dump_tx_header_R3abcbf80
Oct 20 13:09:02 toshiba cardmgr[7264]: insmod exited
with status 1
Oct 20 13:09:03 toshiba cardmgr[7264]: get dev info on
socket 0 failed: Resource temporarily unavailable
----------------------------------------------------

Any ideas about what I should do?

BTW, I did not compile the kernel or the pcmcia
sources. I am using the one that is part of the
mandrake distribution. I think the pcmcia version is:
3.1.29

I am trying to run hostap on a very limited hard
drive. So I would prefer if I do not have to recompile
the kernel (I tried downloading the source, but I
donot have enough hard disk left to untar the source
:|). 
Thus, I would prefer if I can install and run hostap
without having to compile the kernel from sources. If
I should use any distribution (other than mandrake
8.1) please let me know and I can try with that.

BTW, I also tried the above with a 3Com airconnect
3CRWE737A pcmcia card with the same results.

Thanks,
Mudit

__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/



From proski  Mon Oct 21 13:19:40 2002
From: proski (Pavel Roskin)
Date: Mon, 21 Oct 2002 16:19:40 -0400 (EDT)
Subject: Resending missing patches
Message-ID: <Pine.LNX.4.44.0210211558250.7241-100000@marabou.research.att.com>

Hello!

Sorry, some of my previous messages didn't have the attachments.  So I'm
resending all my patches together with one more patch - an entry for
Linksys CompactFlash cards.

The changes are:

1) Support for DESTDIR in Makefile
2) Using "cp -f" in Makefile
3) Listing all required modules in hostap_cs.conf
4) gcc 3.2 warning fix in hostap_hw.c

========================================
--- Makefile
+++ Makefile
@@ -11,6 +11,9 @@
 # Leave this blank for kernel-tree PCMCIA compilations (CONFIG_PCMCIA):
 PCMCIA_PATH=
 
+# This path will be prepended to every installed file
+DESTDIR=
+
 CC=gcc
 CFLAGS=-O2 -D__KERNEL__ -DMODULE -Wall -c $(EXTRA_CFLAGS)
 
@@ -20,7 +23,7 @@
 	else uname -r; fi)
 KERNELVER := $(shell echo "$(KERNELRELEASE)" | \
 	sed "s/\([0-9]*\.[0-9]*\.[0-9]*\).*/\1/")
-MODPATH := /lib/modules/$(KERNELRELEASE)
+MODPATH := $(DESTDIR)/lib/modules/$(KERNELRELEASE)
 MODULE_CS := hostap_cs.o
 MODULE_PLX := hostap_plx.o
 MODULE_PCI := hostap_pci.o
@@ -145,36 +148,38 @@
 install_hostap: $(MSRC)/hostap.o
 	@echo "Installing hostap.o to $(MODPATH_PCI)"
 	mkdir -p $(MODPATH_PCI)
-	cp $(MSRC)/hostap.o $(MODPATH_PCI)
+	cp -f $(MSRC)/hostap.o $(MODPATH_PCI)
 
 install_crypt: $(MSRC)/hostap_crypt.o $(MSRC)/hostap_crypt_wep.o
 	@echo "Installing hostap_crypt*.o to $(MODPATH_PCI)"
 	mkdir -p $(MODPATH_PCI)
-	cp $(MSRC)/hostap_crypt*.o $(MODPATH_PCI)
+	cp -f $(MSRC)/hostap_crypt*.o $(MODPATH_PCI)
 
 install_pccard: install_check install_crypt install_hostap
 	@echo "Installing $(MODULE_CS) to $(MODPATH_CS)"
 	mkdir -p $(MODPATH_CS)
-	cp $(MSRC)/$(MODULE_CS) $(MODPATH_CS)
+	cp -f $(MSRC)/$(MODULE_CS) $(MODPATH_CS)
+ifndef DESTDIR
 	/sbin/depmod -a
-	@if [ ! -r /etc/pcmcia/hostap_cs.conf ]; then \
-		echo "Installing /etc/pcmcia/hostap_cs.conf"; \
-		cp driver/etc/hostap_cs.conf /etc/pcmcia/hostap_cs.conf; \
+endif
+	@if [ ! -r $(DESTDIR)/etc/pcmcia/hostap_cs.conf ]; then \
+		echo "Installing $(DESTDIR)/etc/pcmcia/hostap_cs.conf"; \
+		cp -f driver/etc/hostap_cs.conf $(DESTDIR)/etc/pcmcia/hostap_cs.conf; \
 	fi
-	@if [ -r /etc/pcmcia/prism2.conf ]; then \
-		echo "You may need to remove old /etc/pcmcia/prism2.conf"; \
+	@if [ -r $(DESTDIR)/etc/pcmcia/prism2.conf ]; then \
+		echo "You may need to remove old $(DESTDIR)/etc/pcmcia/prism2.conf"; \
 	fi
 
 install_plx: install_check install_crypt install_hostap
 	@echo "Installing $(MODULE_PLX) to $(MODPATH_PLX)"
 	mkdir -p $(MODPATH_PLX)
-	cp $(MSRC)/$(MODULE_PLX) $(MODPATH_PLX)
+	cp -f $(MSRC)/$(MODULE_PLX) $(MODPATH_PLX)
 	/sbin/depmod -a
 
 install_pci: install_check install_crypt install_hostap
 	@echo "Installing $(MODULE_PCI) to $(MODPATH_PCI)"
 	mkdir -p $(MODPATH_PCI)
-	cp $(MSRC)/$(MODULE_PCI) $(MODPATH_PCI)
+	cp -f $(MSRC)/$(MODULE_PCI) $(MODPATH_PCI)
 	/sbin/depmod -a
 
 
--- driver/etc/hostap_cs.conf
+++ driver/etc/hostap_cs.conf
@@ -1,5 +1,5 @@
 device "hostap_cs"
-   class "network" module "hostap_cs"
+   class "network" module "hostap_crypt", "hostap", "hostap_cs"
 
 card "Intersil PRISM2 Reference Design 11Mb/s WLAN Card"
    version "INTERSIL", "HFA384x/IEEE"
@@ -30,6 +30,10 @@
    manfid 0x0274, 0x1613
    bind "hostap_cs"
 
+card "Linksys WCF12 Wireless CompactFlash Card"
+   version "Linksys", "Wireless CompactFlash Card"
+   bind "hostap_cs"
+
 card "D-Link DWL-650 11Mbps WLAN Card"
    version "D", "Link DWL-650 11Mbps WLAN Card", "Version 01.02"
    bind "hostap_cs"
--- driver/modules/hostap_hw.c
+++ driver/modules/hostap_hw.c
@@ -3063,7 +3063,7 @@ static void prism2_alloc_ev(struct net_d
 			    netif_queue_stopped(dev))
 				hostap_netif_wake_queues(dev);
 
-			goto out;
+			return;
 		}
 
 		idx++;
@@ -3074,7 +3074,6 @@ static void prism2_alloc_ev(struct net_d
 	printk(KERN_WARNING "%s: could not find matching txfid (0x%04x) for "
 	       "alloc event\n", dev->name, HFA384X_INW(HFA384X_ALLOCFID_OFF));
 
- out:
 }
 
 
========================================

-- 
Regards,
Pavel Roskin




From mark  Mon Oct 21 16:27:13 2002
From: mark (Mark Glines)
Date: Mon, 21 Oct 2002 16:27:13 -0700
Subject: Switching between adhoc/master fails?
Message-ID: <20021021232713.GB22624@glines.org>

Hi, I've noticed an odd problem with a Prism2.5 PCI card... here's what
I do to cause it.

I load the hostap driver (version 2002-10-12).  The card has secondary
firmware version 1.4.2, so I download secondary firmware 1.5.6 into RAM.
I iwconfig it for mode master, channel 11, essid test423, and so forth,
and ifconfig it up with an IP address.  It works fine, other stations can
come on as clients and talk to it.

But when I type "iwconfig wlan0 mode adhoc", and
"iwconfig wlan0 mode master" again, it ceases to work.  Nothing I
try short of reloading the driver/firmware again seems to fix it.

I can't figure out why.  Is this a known issue?

Ad-hoc mode works fine, consistently.  It's just that I can't switch into
it without breaking access-point mode from that point forward.  Is there
a way to switch back without having to reload the driver entirely?  Does
this issue exist for other versions of hostap and/or firmware?

Mark
-- 
http://www.glines.org:8000/pubkey.txt - use it.



From gbritton  Mon Oct 21 19:39:08 2002
From: gbritton (Gerald Britton)
Date: Mon, 21 Oct 2002 22:39:08 -0400
Subject: Switching between adhoc/master fails?
In-Reply-To: <20021021232713.GB22624@glines.org>; from mark@glines.org on Mon, Oct 21, 2002 at 04:27:13PM -0700
References: <20021021232713.GB22624@glines.org>
Message-ID: <20021021223908.A26265@nevermore.toe.doomcom.org>

On Mon, Oct 21, 2002 at 04:27:13PM -0700, Mark Glines wrote:
> Hi, I've noticed an odd problem with a Prism2.5 PCI card... here's what
> I do to cause it.
 
> Ad-hoc mode works fine, consistently.  It's just that I can't switch into
> it without breaking access-point mode from that point forward.  Is there
> a way to switch back without having to reload the driver entirely?  Does
> this issue exist for other versions of hostap and/or firmware?

I've recently had a similar problem.. putting the card into managed mode
then clearing the essid (associate to anything), it all works fine.. if the
card then tries to change back to master or into monitor mode, things all
lock up.  reloading the card fixes it.  if i beat on it for a while, hostap
decides to reset it and it works too.

				-- Gerald




From victor.aleo  Tue Oct 22 03:38:31 2002
From: victor.aleo (Victor Aleo)
Date: Tue, 22 Oct 2002 12:38:31 +0200
Subject: Poll stations from AP transparently 
Message-ID: <3DB52AA7.9090009@estudiant.upc.es>

Hi everybody!

I already know, from multiple emails with this list and especially with 
Jouni, that is not possible to know from the AP side if a station 
(client) can reach other APs in the same ESS. The reason to get this 
knowledge is very simple: if an AP knows that a STA can reach other APs 
it will be potentially possible to reject this station "safely". Thus, 
with the security that the station will be able to reassociate with at 
least another AP.

However, I still think that this can be implemented without the aid of 
any special software in the station side (transparent to the clients). 
Thus, only the AP will be "modified". The key question is how? It is 
clear to me that there are not specific methods to perform this task 
(mainly because the standard specified mobile based handoff but not 
network based). But I think there are "indirect" methods to find out the 
answer:

1) If the AP can poll, by means of beacon frames for instance, the 
stations. In this case, the APs in the  same ESS send beacon frames to a 
specified STA. If the STA answer to this beacon frames, it means that 
can be associated to more than one AP. Therefore, if it is rejected by 
its current AP it will not have problems to reassociate with  another.

My questions are: is this feasible with Prism2? Have you thought about 
other mechanisms to find out this information?

Sorry to write such a long email, but I think this is a key issue to 
implement load balancing algorithms in WLAN networks and I am working in 
it :)

Thanks a lot for your comments or suggestions,

Victor





From Jacques.Caron  Tue Oct 22 04:09:59 2002
From: Jacques.Caron (Jacques Caron)
Date: Tue, 22 Oct 2002 13:09:59 +0200
Subject: Poll stations from AP transparently 
In-Reply-To: <3DB52AA7.9090009@estudiant.upc.es>
Message-ID: <5.1.1.6.0.20021022124732.02729338@pop.mail.yahoo.com>

Hi,

As far as I know, there is no response to beacon frames, so you can't 
listen for them (it would generate too much traffic for no useful purpose).

If you want to know if a station can reach other APs, I think the only 
solution (other than adding software on the clients) would be to have your 
AP communicate with neighbouring APs, asking them to poll them somehow. But 
I'm not sure there are ways for an AP to poll a station associated with 
another AP that will always work (it depends on CF-Pollable settings and 
similar things). Alternatively, if the clients are using active scanning, 
the neighboring APs could have a cache of recently seen probe requests. But 
again, that won't work with clients using passive scanning only.

A slightly different question: why do you want your AP to reject clients? A 
scalability issue to achieve some form of load-balancing?

Jacques.

At 12:38 PM 10/22/2002, Victor Aleo wrote:
>Hi everybody!
>
>I already know, from multiple emails with this list and especially with 
>Jouni, that is not possible to know from the AP side if a station (client) 
>can reach other APs in the same ESS. The reason to get this knowledge is 
>very simple: if an AP knows that a STA can reach other APs it will be 
>potentially possible to reject this station "safely". Thus, with the 
>security that the station will be able to reassociate with at least another AP.
>
>However, I still think that this can be implemented without the aid of any 
>special software in the station side (transparent to the clients). Thus, 
>only the AP will be "modified". The key question is how? It is clear to me 
>that there are not specific methods to perform this task (mainly because 
>the standard specified mobile based handoff but not network based). But I 
>think there are "indirect" methods to find out the answer:
>
>1) If the AP can poll, by means of beacon frames for instance, the 
>stations. In this case, the APs in the  same ESS send beacon frames to a 
>specified STA. If the STA answer to this beacon frames, it means that can 
>be associated to more than one AP. Therefore, if it is rejected by its 
>current AP it will not have problems to reassociate with  another.
>
>My questions are: is this feasible with Prism2? Have you thought about 
>other mechanisms to find out this information?
>
>Sorry to write such a long email, but I think this is a key issue to 
>implement load balancing algorithms in WLAN networks and I am working in it :)
>
>Thanks a lot for your comments or suggestions,
>
>Victor
>
>
>_______________________________________________
>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 victor.aleo  Tue Oct 22 05:58:37 2002
From: victor.aleo (Victor Aleo)
Date: Tue, 22 Oct 2002 14:58:37 +0200
Subject: Poll stations from AP transparently
References: <5.1.1.6.0.20021022124732.02729338@pop.mail.yahoo.com>
Message-ID: <3DB54B7D.5040903@estudiant.upc.es>

Jacques Caron wrote:

> If you want to know if a station can reach other APs, I think the only 
> solution (other than adding software on the clients) would be to have 
> your AP communicate with neighbouring APs, asking them to poll them 
> somehow.

Yes, you are right. Currently, in my system the APs communicate between 
each other (in order to share load metrics information). Therefore, 
communication among APs is not a limitation.

> But I'm not sure there are ways for an AP to poll a station associated 
> with another AP that will always work (it depends on CF-Pollable 
> settings and similar things).

Uhmm...If I am not wrong, the CF-Pollable settings are designed only for 
the PCF mode and the current WLAN cards only implement DCF mode. So I do 
not think this could be a solution.

But this is exactly the problem I want to solve: how an AP can poll a 
station that is associated to another AP? If somehow, the station answer 
to this "query" (note here that the query itself is not important at 
all, but the fact of finding out that the station was "able" to answer 
the query) the problem is solved!

> Alternatively, if the clients are using active scanning, the 
> neighboring APs could have a cache of recently seen probe requests. 
> But again, that won't work with clients using passive scanning only. 

Yes, and there is still another problem with this solution: the active 
scanning is not performed periodically. Therefore, it can happen that 
the potentially APs to associate changes (in function of the radio 
quality, multipath, etc.) and therefore the information stored at the AP 
will not be anymore representative.

> A slightly different question: why do you want your AP to reject 
> clients? A scalability issue to achieve some form of load-balancing? 

Rejecting stations from the AP is a mechanism to distribute the load (to 
achieve load balanced scenario in a WLAN network). For instance, if an 
AP "knows" that there are other APs in the same ESS less loaded, it will 
reject  a station  in order to achieve a better performance for each 
user and for the network.

Thanks a lot for your comments,

Victor

> At 12:38 PM 10/22/2002, Victor Aleo wrote:
>
>> Hi everybody!
>>
>> I already know, from multiple emails with this list and especially 
>> with Jouni, that is not possible to know from the AP side if a 
>> station (client) can reach other APs in the same ESS. The reason to 
>> get this knowledge is very simple: if an AP knows that a STA can 
>> reach other APs it will be potentially possible to reject this 
>> station "safely". Thus, with the security that the station will be 
>> able to reassociate with at least another AP.
>>
>> However, I still think that this can be implemented without the aid 
>> of any special software in the station side (transparent to the 
>> clients). Thus, only the AP will be "modified". The key question is 
>> how? It is clear to me that there are not specific methods to perform 
>> this task (mainly because the standard specified mobile based handoff 
>> but not network based). But I think there are "indirect" methods to 
>> find out the answer:
>>
>> 1) If the AP can poll, by means of beacon frames for instance, the 
>> stations. In this case, the APs in the  same ESS send beacon frames 
>> to a specified STA. If the STA answer to this beacon frames, it means 
>> that can be associated to more than one AP. Therefore, if it is 
>> rejected by its current AP it will not have problems to reassociate 
>> with  another.
>>
>> My questions are: is this feasible with Prism2? Have you thought 
>> about other mechanisms to find out this information?
>>
>> Sorry to write such a long email, but I think this is a key issue to 
>> implement load balancing algorithms in WLAN networks and I am working 
>> in it :)
>>
>> Thanks a lot for your comments or suggestions,
>>
>> Victor
>>
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>

-- 
Victor





From Jacques.Caron  Tue Oct 22 06:30:26 2002
From: Jacques.Caron (Jacques Caron)
Date: Tue, 22 Oct 2002 15:30:26 +0200
Subject: Poll stations from AP transparently
In-Reply-To: <3DB54B7D.5040903@estudiant.upc.es>
References: <5.1.1.6.0.20021022124732.02729338@pop.mail.yahoo.com>
Message-ID: <5.1.1.6.0.20021022150912.024d14d8@wheresmymailserver.com>

At 02:58 PM 10/22/2002, Victor Aleo wrote:
>>Alternatively, if the clients are using active scanning, the neighboring 
>>APs could have a cache of recently seen probe requests. But again, that 
>>won't work with clients using passive scanning only.
>
>Yes, and there is still another problem with this solution: the active 
>scanning is not performed periodically. Therefore, it can happen that the 
>potentially APs to associate changes (in function of the radio quality, 
>multipath, etc.) and therefore the information stored at the AP will not 
>be anymore representative.

That's why I said "recently seen" :-)

One solution might be to listen for all traffic received by the AP, even 
from stations not associated. But I believe that means having the card in 
monitor mode, and on the same channel as the neighboring AP(s). In short, 
that means having several cards in each AP, only one being used in AP mode, 
the others being in monitor mode. Then each AP can know which stations it 
can "hear" (which doesn't necessarily mean the station can "hear" the AP, 
though, but with proper thresholds on signal levels it should be possible 
to get something consistent).

>>A slightly different question: why do you want your AP to reject clients? 
>>A scalability issue to achieve some form of load-balancing?
>
>Rejecting stations from the AP is a mechanism to distribute the load (to 
>achieve load balanced scenario in a WLAN network). For instance, if an AP 
>"knows" that there are other APs in the same ESS less loaded, it will 
>reject  a station  in order to achieve a better performance for each user 
>and for the network.

When you say "reject", do you mean at initial association, or later on 
(forced disassociation)?

If the stations are more or less stationnary, you only care about initial 
association, and you can be sure all stations are using active polling 
rather than passive, then all APs should get the probe request, after which 
you can decide which one should accept the association (or even better, 
which one should send back a probe response, though I don't believe this 
would be possible with hostap mode).

If they are using passive scanning, you might try the following approach, 
though I'm not sure it will work with all clients: when a station tries to 
associate to a given AP, refuse. The station should (?) try another one, 
which should refuse also. Once it has tried all APs (and you thus have 
information about all APs it can reach, along with signal level etc.), I 
guess it should start again (maybe after some timeout?) and then you can 
pick which AP will accept the association. Of course if the station is "too 
intelligent" and caches those APs which rejected the association and never 
tries those again you have a problem...

Other than that, there might be other solutions for the AP to poll the 
stations, though I have to admit I don't know very well all the low-level 
mechanisms like RTS, CTS, ACK, CF-Poll and so on, but others on the list 
probably do :-)

One thing that could help is to know what the scenario is exactly: public 
or private use, pre-determined set of stations or not (i.e. standardized 
enterprise-provided laptops or random student-owned ones), ability to 
impose some settings or not, stationnary or moving, etc.

Jacques.


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




From victor.aleo  Tue Oct 22 07:20:21 2002
From: victor.aleo (Victor Aleo)
Date: Tue, 22 Oct 2002 16:20:21 +0200
Subject: Poll stations from AP transparently
References: <5.1.1.6.0.20021022124732.02729338@pop.mail.yahoo.com> <5.1.1.6.0.20021022150912.024d14d8@wheresmymailserver.com>
Message-ID: <3DB55EA5.5060500@estudiant.upc.es>

Jacques Caron wrote:

> One solution might be to listen for all traffic received by the AP, 
> even from stations not associated. But I believe that means having the 
> card in monitor mode, and on the same channel as the neighboring 
> AP(s). In short, that means having several cards in each AP, only one 
> being used in AP mode, the others being in monitor mode. Then each AP 
> can know which stations it can "hear" (which doesn't necessarily mean 
> the station can "hear" the AP, though, but with proper thresholds on 
> signal levels it should be possible to get something consistent). 

Yes, it is a possible solution. However, in my scenario (3 APs with 
overlapping coverage cells using non-interference channels 1, 6 and 11) 
the APs only have one WLAN card.

>> Rejecting stations from the AP is a mechanism to distribute the load 
>> (to achieve load balanced scenario in a WLAN network). For instance, 
>> if an AP "knows" that there are other APs in the same ESS less 
>> loaded, it will reject  a station  in order to achieve a better 
>> performance for each user and for the network.
>
>
> When you say "reject", do you mean at initial association, or later on 
> (forced disassociation)? 
Good question! The term "reject" is not adequate. The exact term is 
"disassociation". Thus, the APs distribute the load disassociating the 
stations, but not "rejecting" initial associations. The main reason: my 
algorithm that decides the load distribution takes into account the load 
of the last association.

> If the stations are more or less stationnary, you only care about 
> initial association, and you can be sure all stations are using active 
> polling rather than passive, then all APs should get the probe 
> request, after which you can decide which one should accept the 
> association (or even better, which one should send back a probe 
> response, though I don't believe this would be possible with hostap 
> mode). 

Yes, but in this case you are not considering that the traffic pattern 
in WLAN networks is highly dynamic. As I have said before, considering 
only initial associations does not take into account that each station 
can generate a very different type and quantity of traffic.

> If they are using passive scanning, you might try the following 
> approach, though I'm not sure it will work with all clients: when a 
> station tries to associate to a given AP, refuse. The station should 
> (?) try another one, which should refuse also. Once it has tried all 
> APs (and you thus have information about all APs it can reach, along 
> with signal level etc.), I guess it should start again (maybe after 
> some timeout?) and then you can pick which AP will accept the 
> association. Of course if the station is "too intelligent" and caches 
> those APs which rejected the association and never tries those again 
> you have a problem... 

Uhmm... it seems interesting, but what about these issues:

    1) Initial necessary time to get the available APs since it is 
required that the station must be rejected by     all the APs that can 
reach and therefore, it can represent a initial delay for the user to 
connect to the         network.

    2) It does not contemplate station movement (if the station moves to 
another position where only can     reach one AP this information will 
not be anymore valid).

Therefore, I still think it is necessary to find out this information 
whenever it is required and not only at some initial phase (as it it 
based your mechanism).

> Other than that, there might be other solutions for the AP to poll the 
> stations, though I have to admit I don't know very well all the 
> low-level mechanisms like RTS, CTS, ACK, CF-Poll and so on, but others 
> on the list probably do :-) 

Well, I guess the solution I am looking for is much related with those 
mechanisms. Anyway, thanks a lot for your comments. Overall, this is my 
final degree project in Electrical Engineering therefore I must 
consider, analyse and compare all the possible solutions to solve the 
problem.

> One thing that could help is to know what the scenario is exactly: 
> public or private use, pre-determined set of stations or not (i.e. 
> standardized enterprise-provided laptops or random student-owned 
> ones), ability to impose some settings or not, stationnary or moving, 
> etc. 

My scenario is composed of 3 APs with overlapped coverage areas placed 
in an indoor laboratory. There are not special requirements for the 
stations (this one of the main features of my solution) due to the load 
distribution system must be transparent for them. Therefore, all the 
modifications have to be implemented in the network side (at the APs). 
Indeed, I should consider the movement of the stations so the APs must 
know in advance if a station can reassociate with another AP in the same 
ESS.

Victor




From rickard  Tue Oct 22 09:28:42 2002
From: rickard (Rickard Gunnarsson)
Date: Tue, 22 Oct 2002 18:28:42 +0200
Subject: RequestIRQ: Resource in use
Message-ID: <002501c279e8$1742c2e0$de0010ac@don>

Hi,

using Debian and kernel 2.4.2 I had hostap working nicely with a D-Link
DWL-650 card and a Ricoh-based PCI->PCMCIA bridge. Now I've moved everything
to a new machine, using the same bridge and card, the same kernel (and
kernel config) and the same hostap version but it's not working any more.
Inserting the card results in hostap reporting "RequestIRQ: Resource in use"
and the freeze or the cardmgr crash. (see dump). Anyone know what to do?

Oct 22 18:35:12 portello cardmgr[201]: socket 0: D-Link DWL-650 11Mbps WLAN
Card
Oct 22 18:35:12 portello cardmgr[201]: executing: 'modprobe hostap_cs'
Oct 22 18:35:12 portello kernel: hostap_crypt: registered algorithm 'NULL'
Oct 22 18:35:12 portello kernel: hostap_cs: hostap_cs.c 0.0.0 CVS (SSH
Communications Security Corp, Jouni Malinen)
Oct 22 18:35:12 portello kernel: hostap_cs: (c) SSH Communications Security
Corp <jkm at ssh.com>
Oct 22 18:35:12 portello kernel: hostap_cs: setting Vcc=33 (constant)
Oct 22 18:35:12 portello kernel: hostap_cs: CS_EVENT_CARD_INSERTION
Oct 22 18:35:12 portello kernel: prism2_config()
Oct 22 18:35:12 portello kernel: hostap_cs: setting Vcc=33 (from config)
Oct 22 18:35:12 portello kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
Oct 22 18:35:12 portello kernel: IO window settings: cfg->io.nwin=1
dflt.io.nwin=1
Oct 22 18:35:12 portello kernel: io->flags = 0x0046, io.base=0x0000, len=64
Oct 22 18:35:12 portello kernel: hostap_cs: RequestIRQ: Resource in use
Oct 22 18:35:12 portello kernel: prism2_release
Oct 22 18:35:12 portello kernel: : card already removed or not configured
during shutdown
Oct 22 18:35:12 portello kernel: release - done
Oct 22 18:35:13 portello cardmgr[201]: get dev info on socket 0 failed:
Resource temporarily unavailable
Oct 22 18:35:13 portello kernel: prism2_detach
Oct 22 18:35:13 portello kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000000
Oct 22 18:35:13 portello kernel:  printing eip:
Oct 22 18:35:13 portello kernel: d89a0ef5
Oct 22 18:35:13 portello kernel: *pde = 00000000
Oct 22 18:35:13 portello kernel: Oops: 0000
Oct 22 18:35:13 portello kernel: CPU:    0
Oct 22 18:35:13 portello kernel: EIP:    0010:[<d89a0ef5>]
Oct 22 18:35:13 portello kernel: EFLAGS: 00010017
Oct 22 18:35:13 portello kernel: eax: 00000000   ebx: d78c2804   ecx:
00000246   edx: 00000000
Oct 22 18:35:13 portello kernel: esi: d78c2804   edi: d78c2800   ebp:
d7dcaa54   esp: d4d53c38
Oct 22 18:35:13 portello kernel: ds: 0018   es: 0018   ss: 0018
Oct 22 18:35:13 portello kernel: Process cardmgr (pid: 201,
stackpage=d4d53000)
Oct 22 18:35:13 portello kernel: Stack: d7dca9a4 d7dca9a4 d7dca800 d7dcaa54
00000000 d7844880 d78c2e5c d78c2e88
Oct 22 18:35:13 portello kernel:        d7dca800 c0246b24 00000001 d89b4540
d78c2800 00000001 d7844780 00000286
Oct 22 18:35:13 portello kernel:        00000000 d7844880 d89b88e0 d7dc9ce0
00000001 00000287 d783fce0 d89b4a87
Oct 22 18:35:13 portello kernel: Call Trace: [<d89b4540>] [<d89b88e0>]
[<d89b4a87>] [<c01a6ca1>] [<c01a6cda>] [<c01a6d2b>] [<c01a6ec2>]
Oct 22 18:35:13 portello kernel:        [<c01a7710>] [<c01b9bb6>]
[<c01b9856>] [<c01eb259>] [<c01b7275>] [<c01b7eeb>] [<c010fdf6>]
[<c010fdf6>]
Oct 22 18:35:13 portello kernel:        [<c010fdf6>] [<c0119dc9>]
[<c0138da7>] [<c0108d6b>] [<c010002b>]
Oct 22 18:35:13 portello kernel:
Oct 22 18:35:13 portello kernel: Code: 8b 02 ff 4b 08 89 58 04 89 03 c7 02
00 00 00 00 c7 42 04 00






From victor.aleo  Tue Oct 22 16:14:27 2002
From: victor.aleo (Victor Aleo)
Date: Wed, 23 Oct 2002 01:14:27 +0200
Subject: How to get the station bit rate from the AP?
Message-ID: <3DB5DBD3.3020404@estudiant.upc.es>

Hi everybody,

I use the version Prism2-2002-05-19 of the driver and the WLAN card 
configured in Master mode (AP). I would like to get, for each station 
associated with the AP, the bit rate that the stations are using (1, 2, 
5.5 or 11). How can I get this information?

I have seen that in the file 
"/proc/net/prism2/wlan#/IEEE_MAC_STATION_ADDRESS" it is possible to 
check the even the bytes transmitted and received at each bit rate but I 
have not seen any field with the information: "Current bit rate of the 
station = 11 Mbps", for instance.

Thanks,

Victor




From jasonb  Tue Oct 22 16:47:10 2002
From: jasonb (Jason Boxman)
Date: Tue, 22 Oct 2002 19:47:10 -0400
Subject: How to get the station bit rate from the AP?
In-Reply-To: <3DB5DBD3.3020404@estudiant.upc.es>
References: <3DB5DBD3.3020404@estudiant.upc.es>
Message-ID: <200210221947.10600.jasonb@edseek.com>

On Tuesday 22 October 2002 07:14 pm, Victor Aleo wrote:
> Hi everybody,
>
> I use the version Prism2-2002-05-19 of the driver and the WLAN card
> configured in Master mode (AP). I would like to get, for each station
> associated with the AP, the bit rate that the stations are using (1, 2,
> 5.5 or 11). How can I get this information?

You really ought to upgrade to 2002-10-12.

> I have seen that in the file
> "/proc/net/prism2/wlan#/IEEE_MAC_STATION_ADDRESS" it is possible to
> check the even the bytes transmitted and received at each bit rate but I
> have not seen any field with the information: "Current bit rate of the
> station = 11 Mbps", for instance.
>
> Thanks,
>
> Victor
>

-- 

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





From tanyh  Tue Oct 22 18:47:57 2002
From: tanyh (Yanghwee Tan)
Date: Wed, 23 Oct 2002 09:47:57 +0800 (SGT)
Subject: essid missing.
Message-ID: <Pine.GSO.4.43L0.0210230944120.24399-100000@marcus.krdl-core.bii>

hi,

i've posted this query before,
wondering why has the essid gone missing
when i do "iwconfig wlan0".
(which was previously there b4 i upgraded the packages below)

this happens after i upgraded:
 - hostap to 2002-09-12 version
 - wireless tools v25

previously using:
 - hostap 2002-05-19
 - wireless tools v25 pre8
 - pcmcia-cs 3.2.0


anyone got any clue what must i do to get back the ESSID on
the ap please kindly share with me asap?

thanks in advance,
Yanghwee.




From jasonb  Tue Oct 22 19:18:48 2002
From: jasonb (Jason Boxman)
Date: Tue, 22 Oct 2002 22:18:48 -0400
Subject: essid missing.
In-Reply-To: <Pine.GSO.4.43L0.0210230944120.24399-100000@marcus.krdl-core.bii>
References: <Pine.GSO.4.43L0.0210230944120.24399-100000@marcus.krdl-core.bii>
Message-ID: <200210222218.48662.jasonb@edseek.com>

On Tuesday 22 October 2002 09:47 pm, Yanghwee Tan wrote:
> hi,
>
> i've posted this query before,
> wondering why has the essid gone missing
> when i do "iwconfig wlan0".
> (which was previously there b4 i upgraded the packages below)
>
> this happens after i upgraded:
>  - hostap to 2002-09-12 version
>  - wireless tools v25
>
> previously using:
>  - hostap 2002-05-19
>  - wireless tools v25 pre8
>  - pcmcia-cs 3.2.0

What version of the wireless extensions does your kernel have?

>
> anyone got any clue what must i do to get back the ESSID on
> the ap please kindly share with me asap?
>
> thanks in advance,
> Yanghwee.
>

-- 

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





From duncan  Tue Oct 22 19:54:50 2002
From: duncan (Duncan Robertson)
Date: Wed, 23 Oct 2002 12:54:50 +1000
Subject: soundcard and hostap wierdness
Message-ID: <20021023125450.37d47fb4.duncan@minihub.org>

Hi,

I am a new member of this list, and firstly would like to say thanks for
the excellent drivers, using them with two machines (AP server and client,
plus two laptops with orinoco cards with excellent results).

I am using the current CVS hostap drivers with 2.4.19 (debian, AMD K6) and
a dlink dwl 520. All works VERY well, except when I play mp3s (using
mpg321 or some other player) the network response basicly dies, though
starts up again perfectly as soon as I kill the mp3 playback. The sound
cards and dwl-520 are all on seperate interrupts etc. The machine is used
with X11, (and ethernet until the wireless proved reliable enough to
remove it) all the time no problems, it is only audio playback that
temporarily kills wireless. Any ideas on this? There are two soundcards in
the box but I have been only testing one at a time so far. I have tried
few different downloads of the hostap drivers and moved the cards around
in various slots on the board, PCI BIOS settings etc with no change in
behaviour.

For example running a ping whilst playing an mp3 gives:

64 bytes from 192.168.5.60: icmp_seq=27 ttl=64 time=4.5 ms
64 bytes from 192.168.5.60: icmp_seq=28 ttl=64 time=5.2 ms
wrong data byte #48 should be 0x30 but was 0x32
        14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29
2a 2b 2c 2d 2e 2f 32 33 32 33 
        34 35 36 37 0 0 0 0 98 d5 5 8 ff ff ff ff 
64 bytes from 192.168.5.60: icmp_seq=30 ttl=64 time=5.1 ms
64 bytes from 192.168.5.60: icmp_seq=31 ttl=64 time=7.1 ms
64 bytes from 192.168.5.60: icmp_seq=32 ttl=64 time=5.0 ms

Modules loaded:

Module                  Size  Used by    Not tainted
sr_mod                 11512   0 (autoclean)
sg                     24100   0 (autoclean)
ipsec                 241312   2
ide-scsi                7456   0
scsi_mod               80168   3 [sr_mod sg ide-scsi]
hostap_pci             38316   1
hostap_crypt_wep        3040   1
hostap                 49092   0 [hostap_pci]
hostap_crypt            1412   0 [hostap_crypt_wep hostap]
es1371                 25856   1
ac97_codec              9536   0 [es1371]
unix                   13380 172 (autoclean)

Interrupts:

           CPU0       
  0:     292726          XT-PIC  timer
  1:      13020          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  4:      34997          XT-PIC  serial
 10:          0          XT-PIC  es1371
 11:      66069          XT-PIC  wlan0
 12:      35064          XT-PIC  es1371
 14:      18433          XT-PIC  ide0
 15:        742          XT-PIC  ide1


wlan0     IEEE 802.11-b  ESSID:"church1"  
          Mode:Managed  Frequency:2.422GHz  Access Point:
00:05:5D:5B:C2:CD
          Bit Rate:11Mb/s   Tx-Power:6 dBm   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:46/92  Signal level:-73 dBm  Noise level:-100 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:242   Missed beacon:0





-- 

Duncan Robertson
Chief Technician - Minihub Communications
http://www.minihub.org/ ph (+61)412117159

"We may say most aptly that the Analytical Engine weaves algebraic
patterns just as the Jacquard loom weaves flowers and leaves"
                                   Countess Ada of Lovelace 



From anishnair  Tue Oct 22 22:40:11 2002
From: anishnair (ANISH NAIR)
Date: Wed, 23 Oct 2002 11:10:11 +0530
Subject: EAP-TLS authentication fails with WinXP
Message-ID: <273ED687CFB4D411986100306E0013BC02AFB16F@pdc1.nestec.net>

Hi,
I am trying out hostapd with WinXP supplicant using EAP-TLS. The RADIUS
server being IAS on Windows 2000 server (domain controller). I was able to
add the client certificates. But when the WInXP supplicant tries to
authenticate, IAS reports the errors in the following sequence:
1) Event Type: Error
Description: The user "domain/username" has connected and failed to
authenticate because of the following error. The supplied message is
incomplete. The signature was not verified.

2) Event Type: Warning
Description: user "username at domain" was denied access.
Reason: This was an authentication failure because of an unknown user name
or a bad password.	

Any idea on what went wrong. I am using the hostap driver version
2002-10-12.

Thanking in advance.

Best Regards
Anish




From victor.aleo  Wed Oct 23 01:41:25 2002
From: victor.aleo (Victor Aleo)
Date: Wed, 23 Oct 2002 10:41:25 +0200
Subject: How to get the station bit rate from the AP?
References: <3DB5DBD3.3020404@estudiant.upc.es> <200210221947.10600.jasonb@edseek.com>
Message-ID: <3DB660B5.7050705@estudiant.upc.es>

Jason Boxman wrote:

>On Tuesday 22 October 2002 07:14 pm, Victor Aleo wrote:
>  
>
>>Hi everybody,
>>
>>I use the version Prism2-2002-05-19 of the driver and the WLAN card
>>configured in Master mode (AP). I would like to get, for each station
>>associated with the AP, the bit rate that the stations are using (1, 2,
>>5.5 or 11). How can I get this information?
>>    
>>
>
>You really ought to upgrade to 2002-10-12.
>  
>
Indeed, to upgrade it is an option but I cannot (by several reasons) so 
my question it was exactly refered to version 2002-05-19.

Any idea how can I get this information with Prism-2002-05-19 version?

-- 
Victor





From victor.aleo  Wed Oct 23 03:49:13 2002
From: victor.aleo (Victor Aleo)
Date: Wed, 23 Oct 2002 12:49:13 +0200
Subject: How to get the station bit rate from the AP?
References: <3DB5DBD3.3020404@estudiant.upc.es> <200210221947.10600.jasonb@edseek.com> <3DB660B5.7050705@estudiant.upc.es>
Message-ID: <3DB67EA9.9010302@estudiant.upc.es>

Victor Aleo wrote:

> Jason Boxman wrote:
>
>> On Tuesday 22 October 2002 07:14 pm, Victor Aleo wrote:
>>  
>>
>>> Hi everybody,
>>>
>>> I use the version Prism2-2002-05-19 of the driver and the WLAN card
>>> configured in Master mode (AP). I would like to get, for each station
>>> associated with the AP, the bit rate that the stations are using (1, 2,
>>> 5.5 or 11). How can I get this information?
>>>   
>>
>>
>> You really ought to upgrade to 2002-10-12.
>>  
>>
> Indeed, to upgrade it is an option but I cannot (by several reasons) 
> so my question it was exactly refered to version 2002-05-19.
>
> Any idea how can I get this information with Prism-2002-05-19 version?
>
I have found this field: is at line 18 and the field id is "rate". I was 
a bit confused because for some reason the driver appends a zero after 
the bit rate (except for the 5.5 case that is equal to 55). Thus, if the 
rate is 2Mbps the contents of this field is 20.

-- 
Victor 





From xdhuang  Wed Oct 23 05:08:38 2002
From: xdhuang (Huang Xiaodong)
Date: 23 Oct 2002 20:08:38 +0800
Subject: About prism2_host_roaming?
Message-ID: <20021023200838.41324.qmail@eyou.com>

Hi, 
Need your help.

1.What does it mean in function "handle_info_queue(void *data)" of
hostap_hw.c, if:
PRISM2_INFO_PENDING_LINKSTATUS =0, and
PRISM2_INFO_PENDING_SCANRESULTS = 1, and 
local->pending_info = 2

2.In which case the function "prism2_host_roaming(local_info_t *local)" should
be called?

3.If I have two APs whose ESSID is the same "test", how I view the process of
scanning. I have run command "prism2_param wlan0 host_roaming 1".

Thanks in advance.
Huang Xiaodong





--http://www.eyou.com
--??????????????????????  ????????  ????????  ????????  ????????...????????





From tanyh  Tue Oct 22 19:24:59 2002
From: tanyh (Yanghwee Tan)
Date: Wed, 23 Oct 2002 10:24:59 +0800 (SGT)
Subject: essid missing.
In-Reply-To: <200210222218.48662.jasonb@edseek.com>
Message-ID: <Pine.GSO.4.43L0.0210231021530.24399-100000@marcus.krdl-core.bii>

there was a warning everytime i do "iwconfig"
it says...

  Warning: Driver for device wlan0 recommend version 13 of Wireless
  Extension, but has been compiled with version 12, therefore some driver
  features may not be available...

previously before i use wireless tools v25 pre8, it was ok.
hmm... can't recall if i did anything wrong when i upgrade to Wireless
Tools ver25.

do u have any suggestion what i should check on?
i'm really clueless now. :(


-Yanghwee-


On Tue, 22 Oct 2002, Jason Boxman wrote:

> On Tuesday 22 October 2002 09:47 pm, Yanghwee Tan wrote:
> > hi,
> >
> > i've posted this query before,
> > wondering why has the essid gone missing
> > when i do "iwconfig wlan0".
> > (which was previously there b4 i upgraded the packages below)
> >
> > this happens after i upgraded:
> >  - hostap to 2002-09-12 version
> >  - wireless tools v25
> >
> > previously using:
> >  - hostap 2002-05-19
> >  - wireless tools v25 pre8
> >  - pcmcia-cs 3.2.0
>
> What version of the wireless extensions does your kernel have?
>
> >
> > anyone got any clue what must i do to get back the ESSID on
> > the ap please kindly share with me asap?
> >
> > thanks in advance,
> > Yanghwee.
> >
>
> --
>
> 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 a.boegl  Wed Oct 23 04:50:33 2002
From: a.boegl (=?ISO-8859-1?Q?Alexander_B=F6gl?=)
Date: Wed, 23 Oct 2002 13:50:33 +0200
Subject: Special Wireless ISP wish
Message-ID: <3DB68D09.5020003@comteam.at>

Is it possible to modify the driver to deny access
between the stations?
The stations should only be able to communicate with
the "AP".

Any Ideas?

============
Alexander B?gl
comteam IT solutions





From martin.whitlock  Wed Oct 23 07:15:03 2002
From: martin.whitlock (Martin Whitlock)
Date: Wed, 23 Oct 2002 16:15:03 +0200
Subject: Special Wireless ISP wish
In-Reply-To: <3DB68D09.5020003@comteam.at>
Message-ID: <IGEFLKICPOFMEIOAMHNGGELMCCAA.martin.whitlock@possio.com>

prism2_param wlan0 ap_bridge_packets 0

/martin

> -----Original Message-----
> From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com]On Behalf Of
> Alexander B?gl
> Sent: den 23 oktober 2002 13:51
> To: hostap at shmoo.com
> Subject: Special Wireless ISP wish
>
>
> Is it possible to modify the driver to deny access
> between the stations?
> The stations should only be able to communicate with
> the "AP".
>
> Any Ideas?
>
> ============
> Alexander B?gl
> comteam IT solutions
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From pedro.estrela  Wed Oct 23 07:29:13 2002
From: pedro.estrela (Pedro Estrela)
Date: Wed, 23 Oct 2002 15:29:13 +0100
Subject: Special Wireless ISP wish
References: <3DB68D09.5020003@comteam.at>
Message-ID: <000f01c27aa0$8f4f7360$90e016d5@pedropc>

the way things are constructed in IP routing makes that stations will always
try to contact each other directly if they are on the same IP subnet,
starting by an ARP request.
you could make proxy ARP for all possible MAC addressess, but that would
simply be a race condition scenario, because the target station would also
reply with his own MAC address.

if you have the colaboration of the stations, the simpler way is to define
for the stations a IP routing configuration with a closed netmask
(255.255.255.255), and the default GW being the AP. This way all traffic
will get forward to the AP. The later has a normal configuration, which
sends the packet to the destination as normal. Note that this can be made
trivially with DHCP configuration.

if you don't have the colaboration of the stations, and you wish to enforce
a policy of not allowing direct inter-station communication, please note
that "prism2_param wlan0 ap_bridge_packets 0" will simply NOT solve your
problem, because it will only stop bridging inside the driver the packets
captured by the AP and destinated to the same wireless cell; it does not
prevent that stations comunicate directly, if they are in range, because
it's IP netmask (255.255.255.0 ou whatever) tells them to proceed that way,
and there is nothing in the 802.11  standard that enforces what you want (as
fair as i know).

Pedro Estrela

> Is it possible to modify the driver to deny access
> between the stations?
> The stations should only be able to communicate with
> the "AP".
>
> Any Ideas?
>
> ============
> Alexander B?gl
> comteam IT solutions
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>





From jasonb  Wed Oct 23 07:42:53 2002
From: jasonb (Jason Boxman)
Date: Wed, 23 Oct 2002 10:42:53 -0400
Subject: essid missing.
In-Reply-To: <Pine.GSO.4.43L0.0210231021530.24399-100000@marcus.krdl-core.bii>
References: <Pine.GSO.4.43L0.0210231021530.24399-100000@marcus.krdl-core.bii>
Message-ID: <200210231042.53198.jasonb@edseek.com>

On Tuesday 22 October 2002 10:24 pm, Yanghwee Tan wrote:
> there was a warning everytime i do "iwconfig"
> it says...
>
>   Warning: Driver for device wlan0 recommend version 13 of Wireless
>   Extension, but has been compiled with version 12, therefore some driver
>   features may not be available...
>
> previously before i use wireless tools v25 pre8, it was ok.
> hmm... can't recall if i did anything wrong when i upgrade to Wireless
> Tools ver25.
>
> do u have any suggestion what i should check on?
> i'm really clueless now. :(

I don't know if it'll fix the ESSID problem, but you can eliminate the 
wireless extension error by upgrading to a kernel with v13 of the wireless 
extensions.  Or you can get a very recent kernel and patch it to version 15 
of the wireless extensions.

>
> -Yanghwee-
>
<snip>

-- 

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





From gbritton  Wed Oct 23 11:29:53 2002
From: gbritton (Gerald Britton)
Date: Wed, 23 Oct 2002 14:29:53 -0400
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <20021016104525.A5702@jm.epitest.fi>; from jkmaline@cc.hut.fi on Wed, Oct 16, 2002 at 10:45:25AM +0300
References: <3DAC3EA2.7070705@gmx.net> <5.1.1.6.0.20021015232643.038afc10@pop.mail.yahoo.com> <20021016104525.A5702@jm.epitest.fi>
Message-ID: <20021023142953.A31073@nevermore.toe.doomcom.org>

On Wed, Oct 16, 2002 at 10:45:25AM +0300, Jouni Malinen wrote:
> Yes, those are indeed firmware images and even in the good old S3
> format. prism2_srec did not support one firmware info record in the
> images, but I just added support for it. In addition, I added a small
> script (split_combined_hex) for automatic extraction of the separate
> image files. Both the changes are now in CVS.

These don't appear to actually be in CVS.  Did you add and remove them
for some reason? or did they just not actually make it into CVS?

				-- Gerald




From msmith  Wed Oct 23 12:48:49 2002
From: msmith (Michael Smith)
Date: Wed, 23 Oct 2002 15:48:49 -0400 (EDT)
Subject: Setting txpower above the power of your card
In-Reply-To: <000001c27841$7b6d6750$04143c0a@hyrax>
Message-ID: <Pine.LNX.4.44.0210231546311.5075-100000@juice.ott.ctd.com>

On Sun, 20 Oct 2002, Scott Stapleton wrote:

> I then thought I'd try setting it to 150mW to see what happened. I never
> expected it to increase, but it did somewhat.

I was curious (I've been setting my txpower to 200 for months now, on
cards that only do 23 dBm :) so I did a quick grep and it looks like the
driver scales the value supplied by the user, in the range -43 to 20, to
the minimum and maximum values supported by the hardware.

ChangeLog:
2002-01-03
          current mapping: minimum power with 'iwconfig wlan0 txpower -43'
          and maximum with 'iwconfig wlan0 txpower 20'

hostap_ioctl.c:
static u16 prism2_txpower_dBm_to_hfa386x(int val)
{
        signed char tmp;

        if (val > 20)
                return 128;
        else if (val < -43)
                return 127;

        tmp = val;
        tmp = -12 - tmp;
        tmp <<= 2;

        return (unsigned char) tmp;
}




From jasonb  Wed Oct 23 17:04:22 2002
From: jasonb (Jason Boxman)
Date: Wed, 23 Oct 2002 20:04:22 -0400
Subject: mostly complete hostap 2002-10-12 guide
Message-ID: <200210232004.22749.jasonb@edseek.com>

It's mostly complete.  I haven't had time to add stuff about mac address 
filtering and I don't have anything to play with WDS stuff.  The wlan on boot 
stuff is missing setup information for RH style start ups and anything 
related to pcmcia as well (I don't have one).

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

Jouni:

You can replace the link on the links page with

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

with the one above, as it is targeted at the latest release.

Thanks.

-- 

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





From gha  Wed Oct 23 19:06:05 2002
From: gha (Guido Augustowski)
Date: Wed, 23 Oct 2002 23:06:05 -0300
Subject: =?iso-8859-1?Q?AP=B4s_Bridging?=
Message-ID: <005d01c27b01$e9bc2300$0100000a@guido>

Hi! I would like to know if there is any method so I can make two wireless cards on AP mode to be connected, so all the clients can see each other, although they may be connected to two different AP?s. I know that I can connect them through Internet, with a VPN, but I mean a wireless connection. 
Thanks in advance and sorry for my bad English. 

Guido 



------------------------------------------------------------
Guido H. Augustowski
    guidoa at fibertel.com.ar
    gaugustowski at unimoron.edu.ar
    Cel.: 15-4446-4100
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021023/a06d9cc9/attachment.htm 


From jt  Wed Oct 23 19:28:50 2002
From: jt (Jean Tourrilhes)
Date: Wed, 23 Oct 2002 19:28:50 -0700
Subject: mostly complete hostap 2002-10-12 guide
Message-ID: <20021024022850.GA25388@bougret.hpl.hp.com>

Jason Boxman wrote :
>
> It's mostly complete.  I haven't had time to add stuff about mac address=20
> filtering and I don't have anything to play with WDS stuff.  The wlan on bo=
> ot=20
> stuff is missing setup information for RH style start ups and anything=20
> related to pcmcia as well (I don't have one).
> 
> http://trekweb.com/~jasonb/articles/hostap_20021012.shtml

	Nice document.

	Comments :
	You don't use the proper Debian Wireless Extension
support. For this, and Red-Hat support, please check the file called
DISTRIBUTIONS.txt in the Wireless Tools package. You will see that
Debian has in fact quite nice support.
	Also, I don't know why you insist on Wireless Extensions v15,
when you don't seem to use any of its feature, and you could get away
with v12. v15 adds more private ioctl support, used mostly for WDS
stuff. v14 adds the scanning support (cf. APradar), but I think it's
not yet supported in AP/master mode.

	I also try to keep a indication of what is and what is not a
PrismII card, but I admit it's tough :
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.drivers.html#Prism2

	Have fun...

	Jean





From dragoonak  Thu Oct 24 00:52:18 2002
From: dragoonak (Aaron Kurtz)
Date: 24 Oct 2002 00:52:18 -0700
Subject: soundcard and hostap wierdness
In-Reply-To: <20021023125450.37d47fb4.duncan@minihub.org>
References: <20021023125450.37d47fb4.duncan@minihub.org>
Message-ID: <1035445939.1069.2.camel@rydia.hardsun.net>

On Tue, 2002-10-22 at 19:54, Duncan Robertson wrote: 

> I am using the current CVS hostap drivers with 2.4.19 (debian, AMD K6) and
> a dlink dwl 520. All works VERY well, except when I play mp3s (using
> mpg321 or some other player) the network response basicly dies, though
> starts up again perfectly as soon as I kill the mp3 playback. The sound

I have the same problem where any played audio just kills the
connection, but I've seen it with multiple wireless Linux drivers, so
it's not just hostap. Hardware is a Abit Bp6, es1371 soundcard, DVD and
CD-R drives, and a Linksys wmp11. No IRQ conflict, and moving the card
didn't work. Only thing I can I add is that I've seen one other person
have the same problem while using Windows and a wireless card. I suspect
the motherboard's the problem, but until this gets fixed, I'm getting
reacquainted with my CD collection. 

-- 
Aaron Kurtz - GnuPG Key ID ED588CF2
 "Hey, sexy mama. Wanna kill all the humans?" -Bender 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20021024/38247a7d/attachment.pgp 


From a.boegl  Thu Oct 24 00:07:24 2002
From: a.boegl (=?ISO-8859-1?Q?Alexander_B=F6gl?=)
Date: Thu, 24 Oct 2002 09:07:24 +0200
Subject: Special Wireless ISP wish
References: <IGEFLKICPOFMEIOAMHNGGELMCCAA.martin.whitlock@possio.com>
Message-ID: <3DB79C2C.9090809@comteam.at>

Excellent!

Thanks a lot!

Alex

Martin Whitlock schrieb:

>prism2_param wlan0 ap_bridge_packets 0
>
>/martin
>
>  
>
>>-----Original Message-----
>>From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com]On Behalf Of
>>Alexander B?gl
>>Sent: den 23 oktober 2002 13:51
>>To: hostap at shmoo.com
>>Subject: Special Wireless ISP wish
>>
>>
>>Is it possible to modify the driver to deny access
>>between the stations?
>>The stations should only be able to communicate with
>>the "AP".
>>
>>Any Ideas?
>>
>>============
>>Alexander B?gl
>>comteam IT solutions
>>
>>
>>_______________________________________________
>>HostAP mailing list
>>HostAP at shmoo.com
>>http://lists.shmoo.com/mailman/listinfo/hostap
>>
>>    
>>
>
>  
>






From bruno  Tue Oct 22 14:53:41 2002
From: bruno (Bruno Lopes F. Cabral)
Date: Tue, 22 Oct 2002 18:53:41 -0300
Subject: WEP troubles between Orinoco APs and hostap driver?
Message-ID: <3DB5C8E5.63015396@openline.com.br>

Hi there

I noticed something strange using hostap 2002-05-19
in managed mode (with wep enabled) and two orinoco
APs (AP200 and AP1000) with Data Security Enabled:

For some reason the linux client can associate with
the AP but will not exchange traffic with it. iwconfig
will show Link Quality: 0/92 (zero/92) and a simple
ping test will not succeed

I did tests with both a prism2 card with station
firmware 0.7.5 and a (desktop) Linksys WMP11 (PCI)
with station firmware 1.3.4. Both using driver's wep,
same behaviour appears

If I change one (i.e. the WMP11 card) to master mode 
the other prism2 client associates just fine (and the 
ping test works)

Using orinoco_cs with a orinoco silver card on my notebook
(with wep enabled) also works with both a hostap in master
mode and the orinoco APs without any problems

Is this a know bug or feature??

Hints on what I could be doing wrong would be greattelly 
appreciated

Cheers
!3runo
from Brazil





From jkmaline  Thu Oct 24 02:49:48 2002
From: jkmaline (Jouni Malinen)
Date: Thu, 24 Oct 2002 12:49:48 +0300
Subject: Firmware STA 1.5.4, R1010504.HEX
In-Reply-To: <20021023142953.A31073@nevermore.toe.doomcom.org>; from gbritton@doomcom.org on Wed, Oct 23, 2002 at 02:29:53PM -0400
References: <3DAC3EA2.7070705@gmx.net> <5.1.1.6.0.20021015232643.038afc10@pop.mail.yahoo.com> <20021016104525.A5702@jm.epitest.fi> <20021023142953.A31073@nevermore.toe.doomcom.org>
Message-ID: <20021024124948.G9487@jm.epitest.fi>

On Wed, Oct 23, 2002 at 02:29:53PM -0400, Gerald Britton wrote:

> These don't appear to actually be in CVS.  Did you add and remove them
> for some reason? or did they just not actually make it into CVS?

I added them and even remembered to run the script to update public CVS
repository. However, this did not work.. It looks like new tar version
decided that it would be better to overwrite symlink with a new
directory instead of using the symlink.. Well, I modified the script and
the changes are now visible also in the public CVS repository.

-- 
Jouni Malinen                                            PGP id EFC895FA




From sharad_mittal12  Thu Oct 24 04:54:38 2002
From: sharad_mittal12 (Sharad Mittal)
Date: Thu, 24 Oct 2002 07:54:38 -0400
Subject: prism2 cards
Message-ID: <F35xOEBWEVTPStw7Tsv0000c6a9@hotmail.com>

Hi,
    Does anyone know of of any Prism2 based 3.3 V Pcmcia cards with external 
antenna support (no hacked stuff)? Please mail me a list if possible.

Thanks,
Sharad





_________________________________________________________________
Unlimited Internet access for only $21.95/month.? Try MSN! 
http://resourcecenter.msn.com/access/plans/2monthsfree.asp




From collord  Thu Oct 24 09:14:06 2002
From: collord (Jerritt Collord)
Date: Thu, 24 Oct 2002 09:14:06 -0700
Subject: prism2 cards
In-Reply-To: <F35xOEBWEVTPStw7Tsv0000c6a9@hotmail.com>
References: <F35xOEBWEVTPStw7Tsv0000c6a9@hotmail.com>
Message-ID: <20021024091406.26a28cec.collord@linuxfund.org>

http://www.personaltelco.net/index.cgi?Prism2Card

According to this list the card that fits your requirements is the
Proxim Rangelan-DS.

Jerritt

On Thu, 24 Oct 2002 07:54:38 -0400
"Sharad Mittal" <sharad_mittal12 at hotmail.com> wrote:

> Hi,
>     Does anyone know of of any Prism2 based 3.3 V Pcmcia cards with
>     external antenna support (no hacked stuff)? Please mail me a list
>     if possible.
> 
> Thanks,
> Sharad
> 
> 
> 
> 
> 
> _________________________________________________________________
> Unlimited Internet access for only $21.95/month.? Try MSN! 
> http://resourcecenter.msn.com/access/plans/2monthsfree.asp
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap



From hlchou  Thu Oct 24 09:25:54 2002
From: hlchou (HungLin)
Date: Fri, 25 Oct 2002 00:25:54 +0800 (CST)
Subject: About Dynamic-WEP Key in CISCO AP350 and Windows XP
Message-ID: <1035476754.40507.hlchou@mail2000.com.tw>

hi all....

 Do anybody know whether Windows XP and CSICO AP350 not follow "draft-congdon-radius-8021x-20.txt" ?

 When I sniffer the packet of CISCO AP350 in dynamic-Wep Key,I see my Windows XP received two EAPOL-Key packet.

 One is for BroadcastKey (WEP Index is 1)==> With Key field
 One is for SessionKey   (WEP Index is 131)==>Bit 8 =1 is for Session Key  and no Key Field

 And I modify Windows XP WLAN WDM Driver to monitor "OID_802_11_ADD_WEP" event.
 
 I see the Windows XP will change its Broadcast and Session WEP Key when receive those two EAPOL-Key Packet from CISCO AP350.
 
 So we know the CISCO AP350 can support Broadcast/Session Dynamic WEP Key .   
    
 But I couldn't make the same "Key Signature" and "Key" field as CISCO AP350 in EAPOL-Key packet.
 
 CISCO AP350 make those two field not follow "draft-congdon-radius-8021x-20.txt".(I guess.....)
 
 Do you have any idea about "Key Signature" and "Key" field?
 
 How could I make the same field vaule like CISCO AP350?.
 
 Could you give me any suggestion or document to achieve it?.       

 Very very very thanks for your help....... at _ at ..
 
 This bug trouble me for a long time........~_~


 HungLin.



From pfolk-hostap  Thu Oct 24 11:28:16 2002
From: pfolk-hostap (pfolk-hostap at gargtech.com)
Date: Thu, 24 Oct 2002 13:28:16 -0500
Subject: Disabling/modifying Auto-rate fallback
Message-ID: <20021024182816.GA16723@gargtech.com>

Hello all,

We've recently started using the HostAP driver in our WISP access points,
ane we're experienceing suboptimal performance (compared, for example, to
the same node operating in ad-hoc mode).  One thing that seems odd is we
get a lot of messages about the driver deciding to drop a client to 1mbit
instead of the normal 11mbit, despite the fact that the client's signal is
fine and its 11mbit packets are overwhelmingly getting through.  I've tried
playing with the prism2_param txratectrl with basically no success, and
I've tried pegging the clients at 11mbits (that results in no traffic getting
through).

Can anyone give some hints regarding how to correct this issue?  Pointers
to possibly-suboptimal code would be great.

Peter



From pfolk  Thu Oct 24 11:24:49 2002
From: pfolk (pfolk at gargtech.com)
Date: Thu, 24 Oct 2002 13:24:49 -0500
Subject: Disabling/modifying Auto-rate fallback
Message-ID: <20021024182449.GA16688@gargtech.com>

Hello all,

We've recently started using the HostAP driver in our WISP access points,
ane we're experienceing suboptimal performance (compared, for example, to
the same node operating in ad-hoc mode).  One thing that seems odd is we
get a lot of messages about the driver deciding to drop a client to 1mbit
instead of the normal 11mbit, despite the fact that the client's signal is
fine and its 11mbit packets are overwhelmingly getting through.  I've tried
playing with the prism2_param txratectrl with basically no success, and
I've tried pegging the clients at 11mbits (that results in no traffic getting
through).

Can anyone give some hints regarding how to correct this issue?  Pointers
to possibly-suboptimal code would be great.

Peter



From pedro.estrela  Thu Oct 24 18:55:26 2002
From: pedro.estrela (Pedro Estrela)
Date: Fri, 25 Oct 2002 02:55:26 +0100
Subject: Disabling/modifying Auto-rate fallback
References: <20021024182449.GA16688@gargtech.com>
Message-ID: <006501c27bc9$97da1510$fae016d5@pedropc>

i would suggest to use hostap rate support, and change this function

void hostap_handle_sta_tx_exc(local_info_t *local, struct hfa384x_tx_frame
*txdesc)

as you can see in this funcion, as soon there is a lost packet, the driver
decreases rate for this particular station immediatly;
you change this function quite easely to only lower the data rate when there
is several lost packts in a row...
another option is to simply disable the loweing code, so that all stations
would lock at 11 Mbit/s forever.

Pedro Estrela

----- Original Message -----
From: <pfolk at gargtech.com>
To: <hostap at shmoo.com>
Sent: Thursday, October 24, 2002 7:24 PM
Subject: Disabling/modifying Auto-rate fallback


> Hello all,
>
> We've recently started using the HostAP driver in our WISP access points,
> ane we're experienceing suboptimal performance (compared, for example, to
> the same node operating in ad-hoc mode).  One thing that seems odd is we
> get a lot of messages about the driver deciding to drop a client to 1mbit
> instead of the normal 11mbit, despite the fact that the client's signal is
> fine and its 11mbit packets are overwhelmingly getting through.  I've
tried
> playing with the prism2_param txratectrl with basically no success, and
> I've tried pegging the clients at 11mbits (that results in no traffic
getting
> through).
>
> Can anyone give some hints regarding how to correct this issue?  Pointers
> to possibly-suboptimal code would be great.
>
> Peter
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>





From imp  Thu Oct 24 21:49:54 2002
From: imp (=?ks_c_5601-1987?B?udrI77+t?=)
Date: Fri, 25 Oct 2002 13:49:54 +0900
Subject: Tx power  setting 
Message-ID: <HIEILNBGFIFLDLBJCOLAMEHPCCAA.imp@airlinktek.com>

Dear all

As I know.. prism 2.x hardware can make maximum 16 +/- 1dbm power..
What is the default tx power of hostap ? 
and how can I set it to make maximum tx power ? 

Thanks.


From a.boegl  Thu Oct 24 23:45:34 2002
From: a.boegl (=?ISO-8859-1?Q?Alexander_B=F6gl?=)
Date: Fri, 25 Oct 2002 08:45:34 +0200
Subject: Special Wireless ISP wish
References: <IGEFLKICPOFMEIOAMHNGGELMCCAA.martin.whitlock@possio.com> <3DB79C2C.9090809@comteam.at> <000f01c27bc0$74873330$fae016d5@pedropc>
Message-ID: <3DB8E88E.7060901@comteam.at>

Hmm, i think the best way is to combine the two things.
The most of our customers are too far away from another to
colaborate without the AP.

Alex B?gl


Pedro Estrela schrieb:

> the way things are constructed in IP routing makes that stations will always
> try to contact each other directly if they are on the same IP subnet,
> starting by an ARP request.
> you could make proxy ARP for all possible MAC addressess, but that would
> simply be a race condition scenario, because the target station would also
> reply with his own MAC address.

> if you have the colaboration of the stations, the simpler way is to define
> for the stations a IP routing configuration with a closed netmask
> (255.255.255.255), and the default GW being the AP. This way all traffic
> will get forward to the AP. The later has a normal configuration, which
> sends the packet to the destination as normal. Note that this can be made
> trivially with DHCP configuration.

> if you don't have the colaboration of the stations, and you wish to enforce
> a policy of not allowing direct inter-station communication, please note
> that "prism2_param wlan0 ap_bridge_packets 0" will simply NOT solve your
> problem, because it will only stop bridging inside the driver the packets
> captured by the AP and destinated to the same wireless cell; it does not
> prevent that stations comunicate directly, if they are in range, because
> it's IP netmask (255.255.255.0 ou whatever) tells them to proceed that way,
> and there is nothing in the 802.11  standard that enforces what you want (as
> fair as i know).

> Pedro Estrela
>
>
> >/ Is it possible to modify the driver to deny access
/> >/ between the stations?
/> >/ The stations should only be able to communicate with
/> >/ the "AP".
/> >/
/> >/ Any Ideas?
/> >/
/> >/ ============
/> >/ Alexander B?gl
/> >/ comteam IT solutions
/> >/
/> >
>
>








From ted  Fri Oct 25 14:23:39 2002
From: ted (Ted Kuo)
Date: Fri, 25 Oct 2002 14:23:39 -0700
Subject: Linksys WPC11 1.4.7 firmware?
Message-ID: <3DB9B65B.9060203@vovtel.com>

Hi,
My understanding from the list is I need v1.4.7 firmware for my
WPC11 to work with HostAP as an AP and Linksys is currently
testing v1.4.7 but not yet release it.

Is there any other alternative to solve this problem? I found someone
post an unofficial one for linksys WMP11. Any such code for WPC11?
Thanks.

Ted




From ted  Fri Oct 25 14:26:43 2002
From: ted (Ted Kuo)
Date: Fri, 25 Oct 2002 14:26:43 -0700
Subject: 802.11 fragments
Message-ID: <3DB9B713.30509@vovtel.com>

Hi,
It seems 802.11 sends out packet fragments in a reverse order.
That is, the last frag is sent first and the first one (the one with
L3 packet header) is sent last.

I cannot find such behavior specified in the spec but I tried
linksys, dlink products, and ethereal and they seem to operate
based on such assumption.

Anyone knows the rationale behiend? Thanks in advance.

Ted




From brad  Fri Oct 25 15:22:24 2002
From: brad (Brad Colbert)
Date: 25 Oct 2002 15:22:24 -0700
Subject: Info on 802.1x
Message-ID: <1035584544.2261.1.camel@otis.rni.net>

Hi folks,

Where can I go and find out information on 802.1x?  I'm assuming it's a
fix to the WEP problem but haven't read much about it.  Also, am I
correct in understanding that HostAP supports this now?

Thanks,
Brad





From ted  Fri Oct 25 13:52:59 2002
From: ted (Ted Kuo)
Date: Fri, 25 Oct 2002 13:52:59 -0700
Subject: Linksys WPC11 1.4.7 firmware?
Message-ID: <3DB9AF2B.9090808@vovtel.com>

Hi,
Does anyone know where I can download a 1.4.7 firmware for
Linksys WPC11?

Last time I checked the list and someone said Linksys is testing
1.4.7 but not yet released. Any unofficial one available somewhere?
Thanks.

Ted
-------------- next part --------------
An embedded message was scrubbed...
From: MAILER-DAEMON at lists.ssh.com
Subject: failure notice
Date: 25 Oct 2002 17:48:09 -0000
Size: 2537
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20021025/7776c2c0/attachment.eml 


From ted  Fri Oct 25 13:55:52 2002
From: ted (Ted Kuo)
Date: Fri, 25 Oct 2002 13:55:52 -0700
Subject: 802.11 Fragments
Message-ID: <3DB9AFD8.4080307@vovtel.com>

Hi,
I noticed that when a packet is fragmented by 802.11. The last
fragment of the packet is sent out first and the one with L3 header
is sent last.

Does anyone know the rationale behind this behavior?

Ted




From jasonb  Fri Oct 25 18:38:23 2002
From: jasonb (Jason Boxman)
Date: Fri, 25 Oct 2002 21:38:23 -0400
Subject: Linksys WPC11 1.4.7 firmware?
In-Reply-To: <3DB9AF2B.9090808@vovtel.com>
References: <3DB9AF2B.9090808@vovtel.com>
Message-ID: <200210252138.23297.jasonb@edseek.com>

On Friday 25 October 2002 04:52 pm, Ted Kuo wrote:
> Hi,

Ted:

> Does anyone know where I can download a 1.4.7 firmware for
> Linksys WPC11?
>
> Last time I checked the list and someone said Linksys is testing
> 1.4.7 but not yet released. Any unofficial one available somewhere?
> Thanks.

You can download 1.4.9 into RAM as I describe in my recent HostAP tutorial.

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

> Ted

-- 

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





From milli  Fri Oct 25 23:56:44 2002
From: milli (Michael Milligan)
Date: Sat, 26 Oct 2002 00:56:44 -0600
Subject: Driver getting into wierd state...  stress test of 2002-10-12 version
Message-ID: <3DBA3CAC.4010602@acmeps.com>

Hello,

Got around to stress testing the 2002-10-12 driver, which had been working 
flawlessly for a few weeks now.  Ran into some trouble with the driver 
freezing up on my server (hostap_pci) running in Master mode.  Client is 
also running hostap, but under PCMCIA (hostap_cs) and in Managed mode.  The 
driver didn't crash the server, just hosed up wlan0.  I'm using a 40-bit WEP 
key.

The server...  Dual-Pentium III box (SMP), kernel version 2.4.19, Debian 
"sarge" (a.k.a., testing), compiled Hostap by patching kernel.  Only change 
I made was to enable download support in the hostap_config.h file.  Only 
running hostap_pci.  The card...  Intel 2011B PCI card (which is a MiniPCI 
card in a carrier, Prism 2.5 chipset).

# lsmod
Module                  Size  Used by    Not tainted
hostap_crypt_wep        3020   1 (autoclean)
hostap_pci             43028   1
hostap                 54852   0 [hostap_pci]
hostap_crypt            1776   0 [hostap_crypt_wep hostap]
...

# dmesg
...
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>
hostap_pci: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_config: initialized in 17316 iterations
wlan0: trying to read PDA from 0x007f0000: failed
wlan0: trying to read PDA from 0x003f0000: failed
wlan0: trying to read PDA from 0x00390000: failed
wlan0: NIC: id=0x8013 v1.0.0
wlan0: PRI: id=0x15 v1.0.7
wlan0: STA: id=0x1f v1.3.5
wlan0: defaulting to host-based encryption as a workaround for firmware bug 
in Host AP mode WEP
wlan0: LinkStatus=2 (Disconnected)
wlan0: Intersil Prism2.5 PCI: mem=0xfc0ff000, irq=18
wlan0: dropped received packet from non-associated STA 00:05:5d:da:c5:0c 
(type=0x02, subtype=0x04)
handle_ap_item - data frame
wlan0: prism2_send_mgmt - device is not UP - cannot send frame
wlan0: LinkStatus=2 (Disconnected)
wlan0: LinkStatus=2 (Disconnected)
hostap_crypt: registered algorithm 'WEP'
wlan0: LinkStatus=2 (Disconnected)
wlan0: prism2_open
wlan0: dropped received packet from non-associated STA 00:05:5d:da:c5:0c 
(type=0x02, subtype=0x00)
handle_ap_item - data frame
wlan0: 00:05:5d:da:c5:0c auth (alg=0 trans#=1 stat=0 len=6fc=00b0) ==> 0 
(authenticated)
wlan0: 00:05:5d:da:c5:0c assoc (len=22 prev_ap=00:00:00:00:00:00) => 0(0) 
(OK, new AID)
wlan0: STA 00:05:5d:da:c5:0c TX rate lowered to 55
wlan0: STA 00:05:5d:da:c5:0c TX rate raised to 110
wlan0: STA 00:05:5d:da:c5:0c TX rate lowered to 55
wlan0: STA 00:05:5d:da:c5:0c TX rate raised to 110
wlan0: STA 00:05:5d:da:c5:0c TX rate lowered to 55
wlan0: STA 00:05:5d:da:c5:0c TX rate raised to 110
wlan0: INFDROP event
wlan0: INFDROP event
...

The client... laptop running same kernel (but not SMP).  The card... Dlink 
DWL-650 card.  The laptop never froze up.  Resetting the server side always 
resumed connectivity.

# lsmod
Module                  Size  Used by    Tainted: PF
hostap_cs              43696   1
hostap                 49156   0 [hostap_cs]
hostap_crypt_wep        2956   1 (autoclean)
hostap_crypt            1360   0 [hostap hostap_crypt_wep]
openafs               410592   2
opl3sa2                 7856   2 (autoclean)
mpu401                 18404   0 (autoclean) [opl3sa2]
ad1848                 20684   0 (autoclean) [opl3sa2]
sound                  52332   2 (autoclean) [opl3sa2 mpu401 ad1848]
soundcore               3460   6 (autoclean) [sound]
xircom_tulip_cb        11512   0
ds                      6408   2 [hostap_cs]
yenta_socket            8704   2
pcmcia_core            38656   0 [hostap_cs ds yenta_socket]
ntfs                   48736   0 (unused)
vfat                    9276   0 (unused)
fat                    29112   0 [vfat]

# dmesg
...
wlan0: LinkStatus=4 (Access point out of range)
wlan0: LinkStatus: BSSID=00:05:3c:00:fb:c9
afs: Lost contact with file server 172.20.21.1 in cell ...
afs: Lost contact with file server 172.20.21.1 in cell ...
wlan0: LinkStatus=5 (Access point in range)
wlan0: LinkStatus: BSSID=00:05:3c:00:fb:c9
wlan0: LinkStatus=2 (Disconnected)
wlan0: LinkStatus: BSSID=00:05:3c:00:fb:c9
wlan0: LinkStatus=1 (Connected)
wlan0: LinkStatus: BSSID=00:05:3c:00:fb:c9
...
(repeated many times, corresponding to server resets)

# (from /var/log/messages)
Oct 25 21:17:45 chief cardmgr[341]: socket 1: Intersil PRISM2 11 Mbps 
Wireless Adapter
Oct 25 21:17:45 chief cardmgr[341]: executing: 'modprobe hostap_cs'
Oct 25 21:17:46 chief kernel: hostap_cs: hostap_cs.c 0.0.0 2002-10-12 (SSH 
Communications Security Corp, Jouni Malinen)
Oct 25 21:17:46 chief kernel: hostap_cs: (c) Jouni Malinen <jkmaline at cc.hut.fi>
Oct 25 21:17:46 chief kernel: hostap_cs: index 0x01: Vcc 3.3, irq 7, io 
0x0100-0x013f
Oct 25 21:17:46 chief kernel: hostap_cs: Registered netdevice wlan0
Oct 25 21:17:46 chief kernel: wlan0: NIC: id=0x800c v1.0.0
Oct 25 21:17:46 chief kernel: wlan0: PRI: id=0x15 v1.0.7
Oct 25 21:17:46 chief kernel: wlan0: STA: id=0x1f v1.3.5
Oct 25 21:17:46 chief /etc/hotplug/net.agent: invoke ifup wlan0


Stess testing...  ripping and enconding CDs (to ogg of course ;-) using a 
directory within the AFS file system on the server for temporary (.wav) and 
final storage (.ogg).  Also downloading files from the Internet (http) and 
reading mail (imap) all at the same time.  Found no correlation of any of 
these activities to the driver failures.  Also tried wget (http) directly 
between server and the client, saw between 550 and 600K/s transfer rates. 
That causes the problem after about 20Meg of a 100Meg file.

Log messages on server while under load:

Oct 25 21:56:01 phantom kernel: NETDEV WATCHDOG: wlan0: transmit timed out
Oct 25 21:56:01 phantom kernel: wlan0 Tx timed out! Resetting card
Oct 25 21:56:01 phantom kernel: hostap_pci: wlan0: resetting card
Oct 25 22:02:03 phantom kernel: NETDEV WATCHDOG: wlan0: transmit timed out
Oct 25 22:02:03 phantom kernel: wlan0 Tx timed out! Resetting card
Oct 25 22:02:03 phantom kernel: hostap_pci: wlan0: resetting card
Oct 25 22:02:24 phantom kernel: Already released txfid found at idx 5
Oct 25 22:02:24 phantom last message repeated 5 times
Oct 25 22:02:24 phantom kernel: hostap_pci: wlan0: resetting card
Oct 25 22:02:38 phantom ntpd[686]: synchronisation lost
Oct 25 22:06:32 phantom kernel: Already released txfid found at idx 0
Oct 25 22:06:33 phantom last message repeated 2 times
Oct 25 22:06:33 phantom kernel: hostap_pci: wlan0: resetting card
Oct 25 22:06:33 phantom kernel: prism2_enable_aux_port: was not disabled!?
Oct 25 22:06:33 phantom kernel: hostap_pci: Initialization failed

at this point, turning down the interface and rmmod'ing the hostap* modules, 
then bringing it back up clears things:

Oct 25 22:08:19 phantom kernel: hostap_pci: Netdevice wlan0 unregistered
Oct 25 22:08:19 phantom kernel: hostap_pci: Driver unloaded
Oct 25 22:08:19 phantom /etc/hotplug/net.agent: invoke ifdown wlan0
Oct 25 22:08:24 phantom kernel: hostap_pci: hostap_pci.c 0.0.0 2002-10-12 
(SSH Communications Security Corp, Jouni Malinen)
Oct 25 22:08:24 phantom kernel: hostap_pci: (c) Jouni Malinen 
<jkmaline at cc.hut.fi>
Oct 25 22:08:25 phantom kernel: hostap_pci: Registered netdevice wlan0
Oct 25 22:08:25 phantom kernel: wlan0: NIC: id=0x8013 v1.0.0
Oct 25 22:08:25 phantom kernel: wlan0: PRI: id=0x15 v1.0.7
Oct 25 22:08:25 phantom kernel: wlan0: STA: id=0x1f v1.3.5
Oct 25 22:08:25 phantom kernel: wlan0: Intersil Prism2.5 PCI: 
mem=0xfc0ff000, irq=18
Oct 25 22:08:25 phantom /etc/hotplug/net.agent: invoke ifup wlan0

Any ideas?  Need more info, lemme know.

Regards,
Mike

-- 
Michael Milligan  --  Free Agent  --  milli at acmeps.com




From ml  Sat Oct 26 06:35:29 2002
From: ml (Dominique Blas)
Date: Sat, 26 Oct 2002 15:35:29 +0200
Subject: No ESSID in beacon frame
In-Reply-To: <20021019084439.C7203@jm.epitest.fi>
References: <200210150156.28738.ml@blas.net> <200210180008.14702.ml@blas.net> <20021019084439.C7203@jm.epitest.fi>
Message-ID: <200210261535.29902.ml@blas.net>

Le Samedi 19 Octobre 2002 07:44, Jouni Malinen a ?crit :
> On Fri, Oct 18, 2002 at 12:08:14AM +0200, Dominique Blas wrote:
> > And I suppose that it's not possible (or dangerous for the sanity of the
> > adapter) to insert a AP secondary firmware instead of a secondary station
> > firmware into a station.
>
> I have never head or a secondary image with AP code. AP firmware is
> usually a RAM downloadable image that is loaded during initialization to
> the card (and at that point it replaces the station firmware that was
> loaded from flash).

This RAM downlodable replaces the primary and secondary firmware stored in 
flash or only the secondary firmware ?
Is it possible to retrieve an AP RAM image on the Net (an upgrade for a 
Prism-based AP) and download it into the RAM of a classic Prism station 
adapter ?

db






From ml  Sat Oct 26 07:00:28 2002
From: ml (Dominique Blas)
Date: Sat, 26 Oct 2002 16:00:28 +0200
Subject: Viabiliy of prism hooks
Message-ID: <200210261600.28123.ml@blas.net>

Hi everybody,

I suppose this question was asked at the early beginning of the hostap project 
but it's hard to find the question in the archive and, of course, the answer.

Well, hostap, thanks to Jouni, is becoming more and more critical to a few 
applications.

So what is the warranty that tomorrow or the day after, a new version of the 
secondary firmware, a new version of the primary firmware (I don't know what 
is the exact possibility of each) or a new version of the chipset (v. 4) 
won't forbid the way hostap hooks in the system ? 

An so far ruins all the benefit hostap has for us all.

Thanks for your comments,

db





From ml  Sat Oct 26 07:37:48 2002
From: ml (Dominique Blas)
Date: Sat, 26 Oct 2002 16:37:48 +0200
Subject: hostap for 802.11g and 802.11a
Message-ID: <200210261637.48125.ml@blas.net>

Hi again,

I'd like to know (and only a developper borrowing the adhoc documentation from 
Intersil can answer so Jouni ?) if hostap will be usable with the next 
generation of MAC/BBP processors from Intersil.

	That is ISL 3880 for 802.11g (PRISM GT) 
	and ISL 3877 for 802.11a (PRISM Indigo).

It should (or could) be critical in a matter of months,

db





From ml  Sat Oct 26 07:38:11 2002
From: ml (Dominique Blas)
Date: Sat, 26 Oct 2002 16:38:11 +0200
Subject: hostap for 802.11g and 802.11a
Message-ID: <200210261637.48125.ml@blas.net>

Hi again,

I'd like to know (and only a developper borrowing the adhoc documentation from 
Intersil can answer so Jouni ?) if hostap will be usable with the next 
generation of MAC/BBP processors from Intersil.

	That is ISL 3880 for 802.11g (PRISM GT) 
	and ISL 3877 for 802.11a (PRISM Indigo).

It should (or could) be critical in a matter of months,

Thanks for your comments,

db





From ml  Sat Oct 26 08:11:58 2002
From: ml (Dominique Blas)
Date: Sat, 26 Oct 2002 17:11:58 +0200
Subject: hostap for Prism Duette
Message-ID: <200210261637.48125.ml@blas.net>

Hi again,

Same question as above but for Prism Duette this time.

It should (or could) also be critical in a matter of months,

Thanks for your comments,

db





From Jacques.Caron  Sat Oct 26 10:09:51 2002
From: Jacques.Caron (Jacques Caron)
Date: Sat, 26 Oct 2002 19:09:51 +0200
Subject: Info on 802.1x
In-Reply-To: <1035584544.2261.1.camel@otis.rni.net>
Message-ID: <5.1.1.6.0.20021026184941.01b3ab10@pop.mail.yahoo.com>

Hi,

802.1X is an IEEE standard for port based access control for all 802 media. 
Its purpose is to provide authentication services (using EAP, the 
Extensible Authentication Protocol) before letting packets go through the 
port (or association in the case of 802.11). 802.1X is mostly just an 
encapsulation of EAP over 802 media (EAPOL, EAP over LAN), really, but it 
also adds key distribution features.

802.1X is particularly useful for 802.11 networks, as it provides a key 
management system, allowing for dynamic keys (in most cases per-session 
keys), and authentication of users, but it can also be useful for wired media.

802.1X is not "a fix for WEP", it adds some of the features that are needed 
to make WEP really practical (the key management system). However, since 
you can change keys frequently when using 802.1X, you can make sure that a 
key is never used long enough that anyone could capture enough packets to 
find the key, and even if they found the key, it wouldn't be usable for a 
long time. But that's really just a workaround, not a real fix.

You can find some info about 802.1X on www.open1x.org, and a lot more on 
Bernard Aboba's excellent 802.11 security page at www.drizzle.com/~aboba/IEEE/

Note however that the full interaction between 802.1X and 802.11 is still 
in flux, as 802.11's Task Group i (Enhanced Security) is working on that 
(that includes new Key descriptor messages, new encryption based on AES, 
the removal of the 802.11 authentication, TKIP, and a lot more...).

Hope that helps,

Jacques.

At 00:22 26/10/2002, Brad Colbert wrote:
>Hi folks,
>
>Where can I go and find out information on 802.1x?  I'm assuming it's a
>fix to the WEP problem but haven't read much about it.  Also, am I
>correct in understanding that HostAP supports this now?
>
>Thanks,
>Brad
>
>
>_______________________________________________
>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 da.silva  Sun Oct 27 07:04:08 2002
From: da.silva (da.silva at free.fr)
Date: Sun, 27 Oct 2002 16:04:08 +0100 (CET)
Subject: hostap/utils/ & RedHat 7.3
Message-ID: <1035731048.3dbc0068c34e3@imp.free.fr>

With a RedHat 7.3 I have somme warmings/errors when compling utils :

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:243: parse error before `}'
make: *** [prism2_srec.o] Error 1

I have to touch some of hostap files :

 hostap/utils/util.h 
 hostap/utils/util.c
 hostap/utils/hostap_crypt_conf.c
 hostap/utils/prism2_srec.c

Here are the changes :


hostap/utils/util.h :
--------before--------
int hostap_ioctl_readmif(const char *dev, int cr);

#endif /* UTIL_H */
----------------------
--------after--------
int hostap_ioctl_readmif(const char *dev, int cr);

typedef unsigned long long u64;

#endif /* UTIL_H */
---------------------


hostap/utils/hostap_crypt_conf.c :
--------before--------
#include <linux/if_ether.h>
#include <linux/wireless.h>

#if WIRELESS_EXT < 9
#error "Linux Wireless Extensions version 9 or newer required"
#endif

typedef unsigned int u32;
typedef unsigned short u16;
typedef unsigned char u8;

#define DEFAULT_KEYS "ff:ff:ff:ff:ff:ff"
---------------------
--------after--------
#include <linux/if_ether.h>

typedef unsigned long long u64;
typedef unsigned int u32;
typedef unsigned short u16;
typedef unsigned char u8;

#include <linux/wireless.h>

#if WIRELESS_EXT < 9
#error "Linux Wireless Extensions version 9 or newer required"
#endif

#define DEFAULT_KEYS "ff:ff:ff:ff:ff:ff"
---------------------

hostap/utils/prism2_srec.c :
--------before--------
#include <sys/socket.h>
#include <linux/wireless.h>
#include <errno.h>

#if WIRELESS_EXT < 9
#error "Linux Wireless Extensions version 9 or newer required"
#endif

#include "util.h"


static int verbose = 0;
----------------------
--------after--------
#include <sys/socket.h>
#include "util.h"
#include <linux/wireless.h>
#include <errno.h>

#if WIRELESS_EXT < 9
#error "Linux Wireless Extensions version 9 or newer required"
#endif

static int verbose = 0;
---------------------


hostap/utils/util.c :
--------before--------

#include <linux/if_ether.h>
#include "util.h"
#include <linux/wireless.h>

#if WIRELESS_EXT < 9
#error "Linux Wireless Extensions version 9 or newer required"
#endif

struct hostap_nicid_rec {
---------------------
--------before--------
#include <linux/if_ether.h>
#include <linux/wireless.h>

#if WIRELESS_EXT < 9
#error "Linux Wireless Extensions version 9 or newer required"
#endif

#include "util.h"

struct hostap_nicid_rec {
---------------------



From da.silva  Sun Oct 27 07:06:53 2002
From: da.silva (da.silva at free.fr)
Date: Sun, 27 Oct 2002 16:06:53 +0100 (CET)
Subject: depmod
Message-ID: <1035731213.3dbc010decc73@imp.free.fr>

/sbin/depmod -a
depmod: *** Unresolved symbols in /lib/modules/2.4.18-
17.7.x/kernel/drivers/atm/unicorn_atm.o
depmod: *** Unresolved symbols in /lib/modules/2.4.18-
17.7.x/kernel/drivers/atm/unicorn_pci.o


Is it possible to replace in hostap/Makefiles file :

/sbin/depmod -a

by

/sbin/depmod -ae -F /boot/System.map

Thanks,




From da.silva  Sun Oct 27 13:47:57 2002
From: da.silva (da.silva at free.fr)
Date: Sun, 27 Oct 2002 22:47:57 +0100 (MET)
Subject: label in hostap_hw.c
Message-ID: <1035755277.3dbc5f0d5ae0f@imp.free.fr>

to prevent a warming (Redhat 8.0) with the label "ou:" is it possible to 
replace in hostap/driver/modules/hostap_hw.c :

--before----------------
                        goto out;
                }

                idx++;
                if (idx >= PRISM2_TXFID_COUNT)
                        idx = 0;
        } while (idx != local->next_alloc);

        printk(KERN_WARNING "%s: could not find matching txfid (0x%04x) for "
               "alloc event\n", dev->name, HFA384X_INW(HFA384X_ALLOCFID_OFF));

 out:
}
------------------------

--after----------------
                        return;
                }

                idx++;
                if (idx >= PRISM2_TXFID_COUNT)
                        idx = 0;
        } while (idx != local->next_alloc);

        printk(KERN_WARNING "%s: could not find matching txfid (0x%04x) for "
               "alloc event\n", dev->name, HFA384X_INW(HFA384X_ALLOCFID_OFF));

}
------------------------

Thanks.



From salga  Sun Oct 27 16:17:39 2002
From: salga (Luca Salgarelli)
Date: 27 Oct 2002 19:17:39 -0500
Subject: Weird problems with hostapd and 802.1x
Message-ID: <1035764259.19548.30.camel@gandalf>

Hi.

I am trying to make 802.1x work with the HostAP driver and hostapd, but
I am having some weird problems.

When hostapd tries to enable 1x support in the driver, the
'PRISM2_PARAM_IEEE_802_1X' ioctl call fails with an OPNOTSUPP error.

The weird part is this: I am pretty sure that the first few times I
tried the setup, it initialized correctly in 1x "testing" mode (-xm). It
started suddenly to show this behavior after a few times I restarted
hostapd, without, as far as I remember, that I changed anything.

The second weird thing is that enabling 1x support in the driver with
iwpriv works fine. So much that for now I have substituted the calls to
the relevant ioctl's in hostapd.c with system calls to iwpriv, and now
it starts up correctly.

Has anyone any idea of what might be wrong? (Details about my setup
follow).

Also, this might be related or not, but I also have another problem with
hostapd: using xsupplicant on my client, I can see hostapd receiving the
EAPOL-start packet. It then says that it is sending a Request-Identity
packet back. However, xsupplicant doesn't receive it, and I can't see it
with tcpdump either, although I do see the EAPOL-Start sent by the
client. Any idea about what's wrong here as well?

Could the firmware of my Prism card be the problem? Note that the AP and
my client talk to each other happily the Prism card is in non-1x mode.

This is my setup:

AP: DWL-520 card, running in open mode.
        NIC: id=0x8013 v1.0.0
        PRI: id=0x15 v1.0.5
        STA: id=0x1f v1.3.4
    HostAP 2002-10-12
    kernel 2.4.20-pre11 with wireless_ext v15, but I also tried a stock
kernel 2.4.19 (wireless ext v13) with the same (bad) results.

Client: latest CVS version of xsupplicant, stock kernel 2.4.18 RH 8.0,
Orinoco card. 

Thanks in advance for your help.
Luca




From evilbunny  Sun Oct 27 21:00:24 2002
From: evilbunny (evilbunny)
Date: Mon, 28 Oct 2002 16:00:24 +1100
Subject: DHCP
Message-ID: <1455856517.20021028160024@groth.net>

Hello hostap,

  I've updated to the latest stable version of HostAP (as well as
  the previous version) couldn't get DHCP addresses via that interface...

  When I ngrep on the linux box, I can see the request coming in via
  the wlan0 interface, but no response is being sent out, have I
  stuffed the config, or anything similarly stupid or is this a bug
  and I'm chasing my tail trying to track it down...

  The May version was issuing dhcp addresses fine...

  Also the September version made the cabletron card think it was
  talking to a hermes based AP, and was showing the link test section
  in the client... However this seems to be not happening in the
  October release...

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

http://www.cacert.org - Free Security Certificates
http://www.sydneywireless.com - Telecommunications Freedom
-------------- 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/20021028/c43f1fec/attachment.bin 


From rfo  Sun Oct 27 21:26:54 2002
From: rfo (Rob Fowler)
Date: Mon, 28 Oct 2002 16:26:54 +1100
Subject: DHCP
References: <1455856517.20021028160024@groth.net>
Message-ID: <00cb01c27e42$a5c44580$f465a8c0@sydcw0477>

I use DHCP on the head (as of a few days ago) and versions since the Sept
crasher fix, it seems to work fine.

What dhcp server are you using?
Is the DHCP server running on the wlan interface? In my case it's not, I
route/NAT my wireless into my wired segment so I run a dhcp relay agent
which relays onto my master dhcp server (which registers the ip into the
DNS) so I can use host names to route to the wireless box. Works like a
dream and completely dynamic.
I have used a local dhcp server bound to the wlan interface on the AP box
when I was testing, that works fine as well. I use the ISC DHCP server.
Mail me off the list if you want some more help. I don't really think you
are having a hostap issue here (but you may, who knows).

Rob Fowler - Sydney
(p.s. I am in your wireless db as 'honeypot')
----- Original Message -----
From: "evilbunny" <evilbunny at sydneywireless.com>
To: <hostap at shmoo.com>
Sent: Monday, October 28, 2002 4:00 PM
Subject: DHCP


> Hello hostap,
>
>   I've updated to the latest stable version of HostAP (as well as
>   the previous version) couldn't get DHCP addresses via that interface...
>
>   When I ngrep on the linux box, I can see the request coming in via
>   the wlan0 interface, but no response is being sent out, have I
>   stuffed the config, or anything similarly stupid or is this a bug
>   and I'm chasing my tail trying to track it down...
>
>   The May version was issuing dhcp addresses fine...
>
>   Also the September version made the cabletron card think it was
>   talking to a hermes based AP, and was showing the link test section
>   in the client... However this seems to be not happening in the
>   October release...
>
> --
> Best regards,
>  evilbunny                          mailto:evilbunny at sydneywireless.com
>
> http://www.cacert.org - Free Security Certificates
> http://www.sydneywireless.com - Telecommunications Freedom
>




From evilbunny  Sun Oct 27 21:45:50 2002
From: evilbunny (evilbunny)
Date: Mon, 28 Oct 2002 16:45:50 +1100
Subject: DHCP
In-Reply-To: <00cb01c27e42$a5c44580$f465a8c0@sydcw0477>
References: <1455856517.20021028160024@groth.net>
 <00cb01c27e42$a5c44580$f465a8c0@sydcw0477>
Message-ID: <10158582006.20021028164550@groth.net>

Hello Rob,

Running the debian binary version of the ISC server, and it works fine
on the ethernet interface, as well as on the previous version of the
hostap drivers... I've added wlan0 to the startup script....

Ok at this point I'll eat my own words due to the fact that the debian
version if you add the interface to the startup script will be
overwritten by the instance loaded from /etc/default/dhcp...

problem solved...

Thanks anyways :)

PS side note: another neat example you can add for use of bridging is
to bridge 2 wireless interfaces, currently I have an SMC pcmcia nic
(built in antenna) and a dwl520 (external antenna slotted wave guide),
and i can roam between the 2 networks and not require IP changes
etc...

I'm using the 2 interfaces for inside/outdoor (and shared) networks...

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

http://www.cacert.org - Free Security Certificates
http://www.sydneywireless.com - Telecommunications Freedom

Monday, October 28, 2002, 4:26:54 PM, you wrote:

RF> I use DHCP on the head (as of a few days ago) and versions since the Sept
RF> crasher fix, it seems to work fine.

RF> What dhcp server are you using?
RF> Is the DHCP server running on the wlan interface? In my case it's not, I
RF> route/NAT my wireless into my wired segment so I run a dhcp relay agent
RF> which relays onto my master dhcp server (which registers the ip into the
RF> DNS) so I can use host names to route to the wireless box. Works like a
RF> dream and completely dynamic.
RF> I have used a local dhcp server bound to the wlan interface on the AP box
RF> when I was testing, that works fine as well. I use the ISC DHCP server.
RF> Mail me off the list if you want some more help. I don't really think you
RF> are having a hostap issue here (but you may, who knows).

RF> Rob Fowler - Sydney
RF> (p.s. I am in your wireless db as 'honeypot')
RF> ----- Original Message -----
RF> From: "evilbunny" <evilbunny at sydneywireless.com>
RF> To: <hostap at shmoo.com>
RF> Sent: Monday, October 28, 2002 4:00 PM
RF> Subject: DHCP


>> Hello hostap,
>>
>>   I've updated to the latest stable version of HostAP (as well as
>>   the previous version) couldn't get DHCP addresses via that interface...
>>
>>   When I ngrep on the linux box, I can see the request coming in via
>>   the wlan0 interface, but no response is being sent out, have I
>>   stuffed the config, or anything similarly stupid or is this a bug
>>   and I'm chasing my tail trying to track it down...
>>
>>   The May version was issuing dhcp addresses fine...
>>
>>   Also the September version made the cabletron card think it was
>>   talking to a hermes based AP, and was showing the link test section
>>   in the client... However this seems to be not happening in the
>>   October release...
>>
>> --
>> Best regards,
>>  evilbunny                          mailto:evilbunny at sydneywireless.com
>>
>> http://www.cacert.org - Free Security Certificates
>> http://www.sydneywireless.com - Telecommunications Freedom
>>
-------------- 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/20021028/7390bb14/attachment.bin 


From tanyh  Tue Oct 29 00:40:23 2002
From: tanyh (Yanghwee TAN)
Date: Tue, 29 Oct 2002 16:40:23 +0800
Subject: wireless ext. patch
References: <20021024022850.GA25388@bougret.hpl.hp.com>
Message-ID: <001c01c27f26$d5e2a380$c67aa8c0@volkswagen>

hey jean,

where may i find the wireless extension patch for v12 to v13?
or to any further recent one from v12 will do as well.
is there a diff file somewhere that i can download?

with the current v12, can i just use the patch to v15?
i read the diff and its only for v14 to v15.  :(

well, jason suggested to me to patch the w.ext and
see if i can fix the missing essid problem that i'm still having.


cheers,
-yanghwee-
- - -
Updated URL to Yang-Hwee TAN's documentation:
http://student.bii.a-star.edu.sg/~tanyh/projects.html


----- Original Message -----
From: "Jean Tourrilhes" <jt at bougret.hpl.hp.com>
To: <hostap at shmoo.com>; <jasonb at edseek.com>
Sent: Thursday, October 24, 2002 10:28 AM
Subject: Re: mostly complete hostap 2002-10-12 guide


> Jason Boxman wrote :
> >
> > It's mostly complete.  I haven't had time to add stuff about mac
address=20
> > filtering and I don't have anything to play with WDS stuff.  The wlan on
bo=
> > ot=20
> > stuff is missing setup information for RH style start ups and
anything=20
> > related to pcmcia as well (I don't have one).
> >
> > http://trekweb.com/~jasonb/articles/hostap_20021012.shtml
>
> Nice document.
>
> Comments :
> You don't use the proper Debian Wireless Extension
> support. For this, and Red-Hat support, please check the file called
> DISTRIBUTIONS.txt in the Wireless Tools package. You will see that
> Debian has in fact quite nice support.
> Also, I don't know why you insist on Wireless Extensions v15,
> when you don't seem to use any of its feature, and you could get away
> with v12. v15 adds more private ioctl support, used mostly for WDS
> stuff. v14 adds the scanning support (cf. APradar), but I think it's
> not yet supported in AP/master mode.
>
> I also try to keep a indication of what is and what is not a
> PrismII card, but I admit it's tough :
>
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.drivers.
html#Prism2
>
> Have fun...
>
> Jean
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From scold  Mon Oct 28 02:09:26 2002
From: scold (Stone Cold)
Date: Mon, 28 Oct 2002 10:09:26 +0000
Subject: compile problem
Message-ID: <20021028100926.A9573@stackheap.org>

Hello - trying to install hostap and I'm running into a bit of a problem.

My existing setup is a laptop running RH 7.3 with 2.4.18-4, with which I
successfuly run kismet, airsnort, and wellenreiter.  Saw fakeap, which uses
hostap, and thought I'd give it a whirl.

I'm using a DWL-650, which by what I could find in the list archives, will
work.  I have that NIC configured and working as eth1.

My problem arises when I try to compile hostap.  I have kernel tree pcmcia
support, so all I should have to do is make sure I have the correct path
in my makefile (/usr/src/linux) and away I go.  However, out of the box, the
compile fails at line 43 which is an include for $KERNEL_PATH/.config - I do
not have this file.  Just for grins, I created a .config file there and make
appeared to work (make pccard that is).  However, when I did a make_pccard
install, it bailed telling me I had unresolved symbols in /lib/modules/2.4.18
-4/net/hostap.o and some other files.

Can someone please point me in the right direction?

Thanks,

scold



From victor.aleo  Mon Oct 28 09:02:17 2002
From: victor.aleo (Victor Aleo)
Date: Mon, 28 Oct 2002 18:02:17 +0100
Subject: Unexpected LinkStatus disconnection
Message-ID: <3DBD6D99.7020200@estudiant.upc.es>

Hi everybody,

I have been working without problems with Prism2 driver 
(Prism2-2002-05-1). I have installed 2 WLAN cards in my linux-box.

Suddenly, I get now this following message for the first WLAN card (wlan0):

wlan0: INFO - fid=0x039a - len=2 type=0xf200
  LinkStatus=2 (Disconnected)

When I show the config parameters with: iwconfig wlan0 the output is:

 Link Quality:0  Signal level:0  Noise level:0

I have tried to restart the module several times and the network 
configuration, but I cannot solve the problem. It seems there is 
something wrong with the card.

Any idea?
        
Thanks,

Victor





From jt  Mon Oct 28 09:15:18 2002
From: jt (Jean Tourrilhes)
Date: Mon, 28 Oct 2002 09:15:18 -0800
Subject: wireless ext. patch
In-Reply-To: <001c01c27f26$d5e2a380$c67aa8c0@volkswagen>
References: <20021024022850.GA25388@bougret.hpl.hp.com> <001c01c27f26$d5e2a380$c67aa8c0@volkswagen>
Message-ID: <20021028171518.GG30700@bougret.hpl.hp.com>

On Tue, Oct 29, 2002 at 04:40:23PM +0800, Yanghwee TAN wrote:
> hey jean,
> 
> where may i find the wireless extension patch for v12 to v13?
> or to any further recent one from v12 will do as well.
> is there a diff file somewhere that i can download?
> 
> with the current v12, can i just use the patch to v15?
> i read the diff and its only for v14 to v15.  :(

	You need each incremental patch, and all those patches are on
my web page (including v11 to v12).
	What I was telling is that, for most things people are doing
are currently doing, you don't need to upgrade and you can use
whatever is available in the kernel.

> well, jason suggested to me to patch the w.ext and
> see if i can fix the missing essid problem that i'm still having.

	I was not aware of this bug. Was it a driver bug ?

> cheers,
> -yanghwee-

	Jean



From Doug  Mon Oct 28 11:12:38 2002
From: Doug (Doug)
Date: Mon, 28 Oct 2002 11:12:38 -0800
Subject: Future Host AP Mode PRISM support details
Message-ID: <4.2.2.20021028110509.010cba00@pop.sbcglobal.net>

Got some good information to share with all. Seems that Intersil/PRISM will 
continue to support HostAP mode in all future chip sets. This means that 
a/b/g and a/b chip sets will support HostAP mode. Looks like there will be 
some new 802.11a/b/g PCI and PC Card/PCMCIA boards available next year with 
these chip sets. I can't wait to see Host AP at 54Mbits!

Doug




From collord  Mon Oct 28 11:59:53 2002
From: collord (Jerritt Collord)
Date: Mon, 28 Oct 2002 11:59:53 -0800
Subject: Future Host AP Mode PRISM support details
In-Reply-To: <4.2.2.20021028110509.010cba00@pop.sbcglobal.net>
References: <4.2.2.20021028110509.010cba00@pop.sbcglobal.net>
Message-ID: <20021028115953.15b4dd08.collord@linuxfund.org>

The next question is if there will be proper DMA in this hardware, as the HostAP architecture would certainly suffer at these higher rates without it.

Jerritt

On Mon, 28 Oct 2002 11:12:38 -0800
Doug <Doug at irdatacorp.com> wrote:

> Got some good information to share with all. Seems that Intersil/PRISM will 
> continue to support HostAP mode in all future chip sets. This means that 
> a/b/g and a/b chip sets will support HostAP mode. Looks like there will be 
> some new 802.11a/b/g PCI and PC Card/PCMCIA boards available next year with 
> these chip sets. I can't wait to see Host AP at 54Mbits!
> 
> Doug
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap



From ajs  Mon Oct 28 12:14:00 2002
From: ajs (Aron Silverton)
Date: Mon, 28 Oct 2002 14:14:00 -0600
Subject: Suggestions for starting hostapd
Message-ID: <3DBD9A88.1020701@labs.mot.com>

Hi all,

I am looking for suggestions as to an appropriate location for starting 
hostapd.  I would like for it to start so that the wlan0ap interface has 
been created before /etc/pcmcia/network runs.  I create my eth0 to wlan 
interface bridge in /etc/pcmcia/network.

Currently, I have eth0 and wlan0 brought up at boot by the 
/etc/init.d/network script.  By the time /etc/pcmcia/network runs, both 
interfaces are present.

With hostapd, is it still necessary to have /etc/init.d/network bring up 
wlan0?  Is it necessary to have a"lias wlan0 hostap_cs" in 
/etc/modules.conf?

Any and all suggestions and explanations are appreciated.

Thanks,

Aron




From Joshua.Wright  Mon Oct 28 13:43:33 2002
From: Joshua.Wright (Joshua Wright)
Date: Mon, 28 Oct 2002 16:43:33 -0500
Subject: Sequence numbers jumping - question
Message-ID: <156AA90517398D479A3473C35CE99EDD010968@pvdexc99.jwu.edu>

I am doing some research for wireless intrusion analysis and was hoping someone could fill me in on a question I have regarding hostap drivers and sequence numbers.

Using FakeAP and the 2002-10-12 hostap drivers on my Slackware 8.1 machine (using pcmcia-cs 3.2.1), I generated a series of beacon frames using changing ESSIDs.  I captured this traffic on another Slack machine using a Cisco Aironet 350 card in RFMON mode.

When analyzing the traffic pattern, the sequence numbers seem to hop quite a bit between changing the ESSID with fakeap (which works by using iwconfig to do the IOCTL stuff).  Basically, fakeap does this (perl):

    system( $IWCONFIG, $interface_opt, "ESSID",   $essid );
    system( $IWCONFIG, $interface_opt, "channel", $channel );
    system( $IFCONFIG, $interface_opt, "hw",      "ether", $mac );

to change the ESSID, frequency and MAC address.  Some of my traces look like this:

IEEE 802.11
    Type/Subtype: Beacon frame (8)
    Frame Control: 0x0080
<snip>
    Destination address: ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff)
    Source address: 00:40:ae:76:4d:bc (00:40:ae:76:4d:bc)
    BSS Id: 00:40:ae:76:4d:bc (00:40:ae:76:4d:bc)
    Fragment number: 0
    Sequence number: 2089
IEEE 802.11 wireless LAN management frame
<snip>
    Tagged parameters (23 bytes)
        Tag Number: 0 (SSID parameter set)
        Tag length: 6
        Tag interpretation: Lilaea
        Tag Number: 1 (Supported Rates)
        Tag length: 4
<snip>

IEEE 802.11
    Type/Subtype: Beacon frame (8)
    Frame Control: 0x0080
<snip>
    Destination address: ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff)
    Source address: 00:04:76:ed:64:91 (00:04:76:ed:64:91)
    BSS Id: 00:04:76:ed:64:91 (00:04:76:ed:64:91)
    Fragment number: 0
    Sequence number: 2090
IEEE 802.11 wireless LAN management frame
<snip>
    Tagged parameters (21 bytes)
        Tag Number: 0 (SSID parameter set)
        Tag length: 4
        Tag interpretation: urim
        Tag Number: 1 (Supported Rates)


In this case, the sequence number moves from 2089 to 2090, like I would expect.

However, I have several instances where the sequence number jumps by as much 22:

IEEE 802.11
    Type/Subtype: Beacon frame (8)
    Frame Control: 0x0080
<snip>
    Destination address: ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff)
    Source address: 00:40:33:fa:77:74 (00:40:33:fa:77:74)
    BSS Id: 00:40:33:fa:77:74 (00:40:33:fa:77:74)
    Fragment number: 0
    Sequence number: 1974
IEEE 802.11 wireless LAN management frame
<snip>
    Tagged parameters (24 bytes)
        Tag Number: 0 (SSID parameter set)
        Tag length: 7
        Tag interpretation: ladonna
        Tag Number: 1 (Supported Rates)

IEEE 802.11
    Type/Subtype: Beacon frame (8)
    Frame Control: 0x0080
<snip>
    Destination address: ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff)
    Source address: 00:40:33:fa:77:74 (00:40:33:fa:77:74)
    BSS Id: 00:40:33:fa:77:74 (00:40:33:fa:77:74)
    Fragment number: 0
    Sequence number: 1996
IEEE 802.11 wireless LAN management frame
<snip>
    Tagged parameters (24 bytes)
        Tag Number: 0 (SSID parameter set)
        Tag length: 7
        Tag interpretation: ladonna
        Tag Number: 1 (Supported Rates)
<snip>


Is their any reasons the HostAP drivers would skip some of the sequence number values when changing the frequency or ESSID?  It could be my data capture implementation or the Cisco internal channel hopping mechanism that is preventing me from seeing all the frames, but I don't have a way to confirm this.

Can anyone shed some light on how sequence numbers are handled in HostAP?  I didn't see an obvious reference to it in the code - if someone can point me to the right general area instead, that would be good too. :)

Many thanks.

-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




From jkmaline  Mon Oct 28 15:27:30 2002
From: jkmaline (Jouni Malinen)
Date: Tue, 29 Oct 2002 01:27:30 +0200
Subject: Sequence numbers jumping - question
In-Reply-To: <156AA90517398D479A3473C35CE99EDD010968@pvdexc99.jwu.edu>; from Joshua.Wright@jwu.edu on Mon, Oct 28, 2002 at 04:43:33PM -0500
References: <156AA90517398D479A3473C35CE99EDD010968@pvdexc99.jwu.edu>
Message-ID: <20021029012730.A1033@jm.epitest.fi>

On Mon, Oct 28, 2002 at 04:43:33PM -0500, Joshua Wright wrote:

> Is their any reasons the HostAP drivers would skip some of the sequence number values when changing the frequency or ESSID?  It could be my data capture implementation or the Cisco internal channel hopping mechanism that is preventing me from seeing all the frames, but I don't have a way to confirm this.

I would assume that the "missing" sequence numbers were used on some
other frames that were not seen in the capture.

> Can anyone shed some light on how sequence numbers are handled in HostAP?  I didn't see an obvious reference to it in the code - if someone can point me to the right general area instead, that would be good too. :)

They aren't, so no wonder you didn't find any obvious references to
them.. Firmware takes care of assigning seq# for the outgoing frames. I
don't think anything breaks by skipping some sequence numbers, so it
might also be that the firmware happens to skip them when configuration
(like channel or ssid) is changed.

-- 
Jouni Malinen                                            PGP id EFC895FA



From bdoga  Mon Oct 28 21:19:11 2002
From: bdoga (Randall Hinton)
Date: Mon, 28 Oct 2002 22:19:11 -0700
Subject: Problems with current host_ap drivers
Message-ID: <3DBE1A4F.3020809@infowest.com>

I have a Zcomax XI-325H PC-card
firmware 1.3.6

it worked fine with the driver release from 5-19-2002, but when I try 
and load the
10-12-2002 driver release, I get this output to the screen

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: Registered netdevice wlan0
wlan0: could not get own MAC address
wlan0: Port type setting to 6 failed
wlan0: MAC port 0 enabling failed
wlan0: TXRateControl setting to 0x8 failed

syslog output:

Oct 28 21:10:20 gateway cardmgr[479]: socket 0: Zcomax XI-325H 200mW
Oct 28 21:10:20 gateway cardmgr[479]: executing: 'modprobe hostap_cs 
channel=7 iw_mode=3 essid=test ignore_cis_vcc=0'
Oct 28 21:10:20 gateway kernel: hostap_crypt: registered algorithm 'NULL'
Oct 28 21:10:20 gateway kernel: hostap_cs: hostap_cs.c 0.0.0 2002-10-12 
(SSH Communications Security Corp, Jouni Malinen)
Oct 28 21:10:20 gateway kernel: hostap_cs: (c) Jouni Malinen 
<jkmaline at cc.hut.fi>
Oct 28 21:10:20 gateway kernel: hostap_cs: setting Vcc=33 (constant)
Oct 28 21:10:20 gateway kernel: hostap_cs: CS_EVENT_CARD_INSERTION
Oct 28 21:10:20 gateway kernel: prism2_config()
Oct 28 21:10:20 gateway kernel: hostap_cs: setting Vcc=50 (from config)
Oct 28 21:10:20 gateway kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
Oct 28 21:10:20 gateway kernel: IO window settings: cfg->io.nwin=1 
dflt.io.nwin=1
Oct 28 21:10:20 gateway kernel: io->flags = 0x0046, io.base=0x0000, len=64
Oct 28 21:10:20 gateway kernel: hostap_cs: index 0x01: Vcc 5.0, irq 12, 
io 0x0100-0x013f
Oct 28 21:10:20 gateway kernel: hostap_cs: Registered netdevice wlan0
Oct 28 21:10:20 gateway kernel: prism2_hw_init()
Oct 28 21:10:20 gateway kernel: prism2_hw_config: initialized in 17129 
iterations
Oct 28 21:10:22 gateway kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=df94a160, type=0, res=0)
Oct 28 21:10:22 gateway kernel: wlan0: hfa384x_cmd: command was not 
completed (res=0, entry=df94a160, type=0, cmd=0x0021, param0=0xfd0b)
Oct 28 21:10:22 gateway kernel: wlan0: hfa384x_get_rid: CMDCODE_ACCESS 
failed (res=-110, rid=fd0b, len=8)
Oct 28 21:10:22 gateway kernel: Could not get RID for component NIC
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=df94a160, type=0, res=0)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: command was not 
completed (res=0, entry=df94a160, type=0, cmd=0x0021, param0=0xfd02)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_get_rid: CMDCODE_ACCESS 
failed (res=-110, rid=fd02, len=8)
Oct 28 21:10:24 gateway kernel: Could not get RID for component PRI
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
busy for 1000 usec
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue - timeout - 
reg=0x8021
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=df94a160, type=0, res=-1)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: interrupted; err=-110
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_get_rid: CMDCODE_ACCESS 
failed (res=-110, rid=fd20, len=8)
Oct 28 21:10:24 gateway kernel: Could not get RID for component STA
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
busy for 1000 usec
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue - timeout - 
reg=0x8021
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=df94a160, type=0, res=-1)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: interrupted; err=-110
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_get_rid: CMDCODE_ACCESS 
failed (res=-110, rid=fd20, len=8)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
busy for 1000 usec
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue - timeout - 
reg=0x8021
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=df94a160, type=0, res=-1)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: interrupted; err=-110
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_get_rid: CMDCODE_ACCESS 
failed (res=-110, rid=fc01, len=6)
Oct 28 21:10:24 gateway kernel: wlan0: could not get own MAC address
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
busy for 1000 usec
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue - timeout - 
reg=0x8000
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=df94a160, type=0, res=-1)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: interrupted; err=-110
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_set_rid: 
CMDCODE_ACCESS_WRITE failed (res=-110, rid=fc00, len=2)
Oct 28 21:10:24 gateway kernel: wlan0: Port type setting to 6 failed
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
busy for 1000 usec
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue - timeout - 
reg=0x8000
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=df94a160, type=0, res=-1)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: interrupted; err=-110
Oct 28 21:10:24 gateway kernel: wlan0: MAC port 0 enabling failed
Oct 28 21:10:24 gateway cardmgr[479]: executing: './network start wlan0'
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
busy for 1000 usec
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue - timeout - 
reg=0x8000
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=dd51d160, type=0, res=-1)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: interrupted; err=-110
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_set_rid: 
CMDCODE_ACCESS_WRITE failed (res=-110, rid=fc0e, len=34)
Oct 28 21:10:24 gateway cardmgr[479]: + /sbin/iwconfig wlan0 nwid 1
Oct 28 21:10:24 gateway cardmgr[479]: + Error for wireless request "Set 
NWID" (8B02) :
Oct 28 21:10:24 gateway cardmgr[479]: +     SET failed on device wlan0 ; 
Operation not supported.
Oct 28 21:10:24 gateway cardmgr[479]: + /sbin/iwconfig wlan0 channel 7
Oct 28 21:10:24 gateway cardmgr[479]: + Error for wireless request "Set 
Frequency" (8B04) :
Oct 28 21:10:24 gateway cardmgr[479]: +     SET failed on device wlan0 ; 
Invalid argument.
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
busy for 1000 usec
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue - timeout - 
reg=0x8000
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=dd51d2a0, type=0, res=-1)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: interrupted; err=-110
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_set_rid: 
CMDCODE_ACCESS_WRITE failed (res=-110, rid=fc84, len=2)
Oct 28 21:10:24 gateway kernel: wlan0: TXRateControl setting to 0x8 failed
Oct 28 21:10:24 gateway cardmgr[479]: + /sbin/iwconfig wlan0 key 
fj9tp-r93vx-x4yxm-4kycj-q362j
Oct 28 21:10:24 gateway cardmgr[479]: + Error for wireless request "Set 
Encode" (8B2A) :
Oct 28 21:10:24 gateway cardmgr[479]: +     invalid argument 
"fj9tp-r93vx-x4yxm-4kycj-q362j".
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
busy for 1000 usec
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue - timeout - 
reg=0x8000
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=dd51d2a0, type=0, res=-1)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: interrupted; err=-110
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_set_rid: 
CMDCODE_ACCESS_WRITE failed (res=-110, rid=fc83, len=2)
Oct 28 21:10:24 gateway cardmgr[479]: + /sbin/iwconfig wlan0 rts 500
Oct 28 21:10:24 gateway cardmgr[479]: + Error for wireless request "Set 
RTS Threshold" (8B22) :
Oct 28 21:10:24 gateway cardmgr[479]: +     SET failed on device wlan0 ; 
Invalid argument.
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
busy for 1000 usec
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue - timeout - 
reg=0x8000
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=dd51d2a0, type=0, res=-1)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: interrupted; err=-110
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_set_rid: 
CMDCODE_ACCESS_WRITE failed (res=-110, rid=fc82, len=2)
Oct 28 21:10:24 gateway cardmgr[479]: + /sbin/iwconfig wlan0 frag 1000
Oct 28 21:10:24 gateway cardmgr[479]: + Error for wireless request "Set 
Fragmentation Threshold" (8B24) :
Oct 28 21:10:24 gateway cardmgr[479]: +     SET failed on device wlan0 ; 
Invalid argument.
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
busy for 1000 usec
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd_issue - timeout - 
reg=0x8000
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: entry still in list? 
(entry=dd51d160, type=0, res=-1)
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_cmd: interrupted; err=-110
Oct 28 21:10:24 gateway kernel: wlan0: hfa384x_set_rid: 
CMDCODE_ACCESS_WRITE failed (res=-110, rid=fc02, len=34)
Oct 28 21:10:24 gateway cardmgr[479]: + /sbin/iwconfig wlan0 essid 
"dreamwire.net"
Oct 28 21:10:24 gateway cardmgr[479]: + Error for wireless request "Set 
ESSID" (8B1A) :
Oct 28 21:10:24 gateway cardmgr[479]: +     SET failed on device wlan0 ; 
Invalid argument.
Oct 28 21:10:24 gateway kernel: wlan0: prism2_open

Any Ideas on what the difference could be?

Thanx,
Bdoga




From xdhuang  Mon Oct 28 21:20:39 2002
From: xdhuang (Huang Xiaodong)
Date: 29 Oct 2002 13:20:39 +0800
Subject: Sending Beacon function in Hostap driver?
Message-ID: <20021029132039.29458.qmail@eyou.com>

Hi all,

Does the hostap driver care the Beacon frame sending function?
If it does, where is it in the driver?

Thanks in advance.

Huang Xiaodong





--http://www.eyou.com
--??????????????????????  ????????  ????????  ????????  ????????...????????





From xdhuang  Mon Oct 28 21:46:42 2002
From: xdhuang (Huang Xiaodong)
Date: 29 Oct 2002 13:46:42 +0800
Subject: Sending&nbsp;Beacon&nbsp;function&nbsp;in&nbsp;Hostap&nbsp;driver?
Message-ID: <20021029134642.71702.qmail@eyou.com>

in the file README.prism2, it says:

... the firmware takes care of time critical tasks
like beacon sending and ...

can't it be done by driver?

In your mail:
>Hi all,
>
>Does the hostap driver care the Beacon frame sending function?
>If it does, where is it in the driver?
>
>Thanks in advance.
>
>Huang Xiaodong
>
>
> 





--http://www.eyou.com
--??????????????????????  ????????  ????????  ????????  ????????...????????





From xdhuang  Mon Oct 28 21:47:49 2002
From: xdhuang (Huang Xiaodong)
Date: 29 Oct 2002 13:47:49 +0800
Subject: Sending&nbsp;Beacon&nbsp;function&nbsp;in&nbsp;Hostap&nbsp;driver?
Message-ID: <20021029134749.73563.qmail@eyou.com>

in the file README.prism2, it says:

... the firmware takes care of time critical tasks
like beacon sending and ...

can't it be done by driver?

In your mail:
>Hi all,
>
>Does the hostap driver care the Beacon frame sending function?
>If it does, where is it in the driver?
>
>Thanks in advance.
>
>Huang Xiaodong
>
>
> 





--http://www.eyou.com
--??????????????????????  ????????  ????????  ????????  ????????...????????





From xdhuang  Mon Oct 28 22:21:52 2002
From: xdhuang (Huang Xiaodong)
Date: 29 Oct 2002 14:21:52 +0800
Subject: Use reserved field of beacon frame - a question
Message-ID: <20021029142152.30014.qmail@eyou.com>

Hi all,

If I want to fill some identify value in the reserved field(capability) of
Beacon frame before a Beacon is send, how to? I know the Beacon frame is send
by firmware,but can't the value of the field be changed by driver
periodically?

Thanks in advance.

Huang Xiaodong





--http://www.eyou.com
--??????????????????????  ????????  ????????  ????????  ????????...????????





From jharana  Tue Oct 29 02:19:50 2002
From: jharana (Jharana Mehta)
Date: Tue, 29 Oct 2002 15:49:50 +0530
Subject: Mobile IP with hostap
Message-ID: <3DBE615C.71442D28@mahindrabt.com>

Hi Jouni,
We tested a Mobile IP setup built on the hostap driver. We used a
linksys WAP11 as an AP for the home network, and configured a laptop
with hostap as the AP on the Foriegn network using Linksys WPC11.
Bridging is enabled on the laptop and works properly. Our mobile Node is
a hostap WPC11 in Managed mode.
We are using the open source dynamics-0.8.1 as the mobile IP package and
using teh single FA model.
we find that the link quality is pretty good without mobile IP, but as
soon as we start mobile IP it deteriorates, with ping reporting too many
duplicate packets and internet access is also too slow. The hostap
driver is running in hostapd -dd mode, but it doesnt seem to indicate
any error.the hostapd is running on channel 11, and linksys WAP11 on
channel 1, and they are pretty far away from each other.
are there any particluar settings that i would have to tweak for a
better performance? what do you suggest?
thanks, 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
-------------- 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/20021029/8b5eb204/attachment.vcf 


From victor.aleo  Tue Oct 29 02:47:15 2002
From: victor.aleo (Victor Aleo)
Date: Tue, 29 Oct 2002 11:47:15 +0100
Subject: Measuring Handoff time transition
Message-ID: <3DBE6733.70701@estudiant.upc.es>

Hi,

I am trying to measure the handoff time transition in WLAN network with 
2 APs and 1 station. The problem I have is that when I force the handoff 
(executing "iwconfig wlan# kickmac ieee_mac_address_sta") I think the 
station tries to reassociate again with the same AP. Because of this, I 
do not allow the station to authenticate again with the same AP (by 
means of the ACL). But I still think this is not working because when 
the MAC layer handoff is produced there is an interruption of the 
communications of several seconds (from 1 to 3 seconds) and this is not 
permissible (typically handoff within WLAN networks should not be higher 
than 100 ms).

How can I avoid that the STA will request the reassociation with the 
same AP?

I have running for both the APs and the stations the Prism2-2002-05-1 
driver version.

Thanks a lot,

Victor




From Joshua.Wright  Tue Oct 29 06:23:14 2002
From: Joshua.Wright (Joshua Wright)
Date: Tue, 29 Oct 2002 09:23:14 -0500
Subject: Sequence numbers jumping - question - follow up
Message-ID: <156AA90517398D479A3473C35CE99EDD9331C4@pvdexc99.jwu.edu>

Jouni's suggestion that the firmware of my card (which is a SMC 2632W, fw 1.02 - sorry for forgetting to mention earlier) is skipping sequence numbers when changing the channel appears to be correct.

I ran another test with FakeAP using a single channel instead of hopping through 11 channels and sequence numbers remained consistent, always incrementing by 1.

Thanks for the assistance.

-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: Jouni Malinen [mailto:jkmaline at cc.hut.fi]
> Sent: Monday, October 28, 2002 6:28 PM
> To: hostap at shmoo.com
> Subject: Re: Sequence numbers jumping - question
> 
> 
> On Mon, Oct 28, 2002 at 04:43:33PM -0500, Joshua Wright wrote:
> 
> > Is their any reasons the HostAP drivers would skip some of 
> the sequence number values when changing the frequency or 
> ESSID?  It could be my data capture implementation or the 
> Cisco internal channel hopping mechanism that is preventing 
> me from seeing all the frames, but I don't have a way to confirm this.
> 
> I would assume that the "missing" sequence numbers were used on some
> other frames that were not seen in the capture.
> 
> > Can anyone shed some light on how sequence numbers are 
> handled in HostAP?  I didn't see an obvious reference to it 
> in the code - if someone can point me to the right general 
> area instead, that would be good too. :)
> 
> They aren't, so no wonder you didn't find any obvious references to
> them.. Firmware takes care of assigning seq# for the outgoing 
> frames. I
> don't think anything breaks by skipping some sequence numbers, so it
> might also be that the firmware happens to skip them when 
> configuration
> (like channel or ssid) is changed.
> 
> -- 
> Jouni Malinen                                            PGP 
> id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 



From gha  Tue Oct 29 08:47:16 2002
From: gha (Guido Augustowski)
Date: Tue, 29 Oct 2002 13:47:16 -0300
Subject: Bridging
Message-ID: <003501c27f6a$dbdc3d20$0100000a@guido>

Hi! I have read the changelog between version 2002-09-12 and 2002-10-12, but I don?t understand something: 

"AP client mode - if AP client mode is enabled and device is
		  in Managed mode (i.e., associated to an AP), driver accepts
		  4-addr WDS frames from current AP. In addition, outgoing
		  frames that have a foreign source address in the Ethernet
		  header are sent using 4-addr WDS frame to the AP. This allows
		  station mode to perform layer 2 bridgeing. Please note, that
		  due to firmware limitations Host AP in Master mode cannot
		  operate with such station."


What does this mean? Can I use this to bridge packets between two machines in Master mode? My English is not very good, and I?m not sure what does this mean. Or is it equivalent to a Hardware AP in Client mode?

Please, this is very important for me, I would really apreciate your answers.

Thanks in advance

Guido

------------------------------------------------------------
Guido H. Augustowski
    guidoa at fibertel.com.ar
    gaugustowski at unimoron.edu.ar
    Cel.: 15-4446-4100
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021029/00f0f131/attachment.htm 


From pymanju  Tue Oct 29 20:30:18 2002
From: pymanju (Manjunathan PY)
Date: Wed, 30 Oct 2002 10:00:18 +0530
Subject: Layer 2 Update!
Message-ID: <00a201c27fcd$0dde2240$468101d9@pcwks356>

Hi,
  I would like to know how "Layer 2 Update" is done,
when a Mobile Station moves from the radio range of an Access point to
another Access point.

Does HostAP do such an update to support roaming of mobile station between
Access Point ? How!

Thanks,
Manjunathan PY


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20021030/51171a86/attachment.htm 


From imp  Tue Oct 29 21:25:54 2002
From: imp (=?euc-kr?B?udrI77+t?=)
Date: Wed, 30 Oct 2002 14:25:54 +0900
Subject: mail is broken... 
Message-ID: <HIEILNBGFIFLDLBJCOLAAEINCCAA.imp@airlinktek.com>

Dear all

I just test my mail character set.. because I never success to send mail to new hostap address..

Is this character broken ? (just test) using (EUC) format...

Sorry..


From tanyh  Tue Oct 29 22:50:17 2002
From: tanyh (Yanghwee Tan)
Date: Wed, 30 Oct 2002 14:50:17 +0800 (SGT)
Subject: wireless ext. patch
In-Reply-To: <20021028171518.GG30700@bougret.hpl.hp.com>
Message-ID: <Pine.GSO.4.43L0.0210301441520.22717-100000@marcus.krdl-core.bii>


On Mon, 28 Oct 2002, Jean Tourrilhes wrote:

<sniped>
>
> 	You need each incremental patch, and all those patches are on
> my web page (including v11 to v12).
> 	What I was telling is that, for most things people are doing
> are currently doing, you don't need to upgrade and you can use
> whatever is available in the kernel.
>
> > well, jason suggested to me to patch the w.ext and
> > see if i can fix the missing essid problem that i'm still having.
>
> 	I was not aware of this bug. Was it a driver bug ?
>

Oh yes sometime ago, i wrote an email to you about this before,
u did mention to check out if it is a driver bug.
but i don't know which driver u refer to. was it hostap driver ?

the version i'm using now is still the sept'02 copy.
my kernel wireless ext. is v12 and pcmcia-cs is v3.2.0 and
my wireless tools v25.


problem explanation:

in the past, using Wireless Tools v25pre8 with "IWCONFIG WLAN0" run, you
will get all the info on wep keys, signal, many others and ESSID (Network
Name).

after i upgrade the wireless tools to v25 release, ESSID is now missing
from the command "IWCONFIG WLAN0" return result.


what should i check on now? any other driver to probe on?


-Yanghwee-





From marcel  Wed Oct 30 02:09:58 2002
From: marcel (Marcel Prisi)
Date: 30 Oct 2002 11:09:58 +0100
Subject: 1.4.9 firmware & Tekram PC400
Message-ID: <1035972599.32394.8.camel@leguman.aubonne.virtua.ch>

Hi all !

I have a Tekram PC400 PCI card (Prism 2.5) with release 1.3.4 of the
firmware.

I wanted to update it using prism2_srec but got an error ... have a look
:

ap:/usr/src/hostap-2002-10-12/utils# ./prism2_srec wlan0
/root/temp/1.4.9/RF010409.HEX
srec summary for RF010409.HEX
Component: 0x001f 1.4.9 (station firmware)
Supported platforms:
  0x800a 1.0.0,  0x800b 1.0.0,  0x800c 1.0.0,  0x800d 1.0.0,  0x8012
1.0.0
  0x8013 1.0.0,  0x8014 1.0.0,  0x8016 1.0.0,  0x8017 1.0.0,  0x8018
1.0.0
  0x801a 1.0.0,  0x801b 1.0.0,  0x801c 1.0.0,  0x8021 1.0.0,  0x8022
1.0.0
  0x8023 1.0.0,  0x800a 1.0.0,  0x800e 1.0.0,  0x8015 1.0.0,  0x8019
1.0.0
  0x801d 1.0.0,  0x8024 1.0.0
Separate S3 data areas:
  addr 0x007E1800..0x007ED199 (len 47514)
  addr 0x007F0800..0x007F1875 (len 4214)
  addr 0x007FE000..0x007FECE7 (len 3304)
Total data length: 55032 bytes
Start address 0x003f0c01

Wireless LAN card information:
Components:
  NICID: 0x8013 v1.0.0
  PRIID: 0x0015 v1.0.5
  STAID: 0x001f v1.3.4

Verifying update compatibility and combining data:
Incompatible interfaces:
  SREC: role=Actor    variant=1 range=4-4 iface=Primary Firmware-Driver
  card: role=Supplier variant=1 range=1-3 iface=Primary Firmware-Driver
Incompatible updata data.

What is incompatible ? Is it the range (European vs. American ??) or the
role (what is it btw ?)

Thanks for your help.




From johnr  Wed Oct 30 10:46:50 2002
From: johnr (John Roark)
Date: Wed, 30 Oct 2002 13:46:50 -0500
Subject: extending a HostAP networks range
Message-ID: <3DC0291A.8000006@wirelessocean.com>

Besides the obvious solution of increasing the wattage and using a 
larger antenae... how would I extend the range of my wireless network. 
Is there a way to link HostAps so that where one ap's range ends another 
starts and extends the range by 50%? Some kind of dumb forwarder that 
simply repeats whatever it picks up (without NAT)? I want it to look 
like the client is talking directly to the main hostap, when in fact it 
is talking to another box that is merely extending the range of the 
hostap... is this possible?

eth0 : AP-A : wlan0 -- <wireless network> -- wlan0 : "Extender"
                                                |
                                   <extended wireless network>
                                                |
                                              wlan0 : Client

Is this a repeater? a bridge? does RDS do this (what is RDS?)? I want it 
all to be on the same network (192.168.1.0/24)... and I need it to 
preserve MACs and IPs.

Thanks,
John

-- 
Hmm.  Your ideas are intriguing to me and I wish to
subscribe to your newsletter.

-Homer J. Simpson




From martin.polak  Wed Oct 30 11:27:04 2002
From: martin.polak (Martin Polak)
Date: Wed, 30 Oct 2002 20:27:04 +0100
Subject: extending a HostAP networks range
References: <3DC0291A.8000006@wirelessocean.com>
Message-ID: <3DC03288.1080309@liwest.at>

John Roark schrieb:
> Besides the obvious solution of increasing the wattage and using a 
> larger antenae... how would I extend the range of my wireless network. 
> Is there a way to link HostAps so that where one ap's range ends another 
> starts and extends the range by 50%? Some kind of dumb forwarder that 
> simply repeats whatever it picks up (without NAT)? I want it to look 
> like the client is talking directly to the main hostap, when in fact it 
> is talking to another box that is merely extending the range of the 
> hostap... is this possible?
> 
> eth0 : AP-A : wlan0 -- <wireless network> -- wlan0 : "Extender"
>                                                |
>                                   <extended wireless network>
>                                                |
>                                              wlan0 : Client
> 
> Is this a repeater? a bridge? does RDS do this (what is RDS?)? I want it 
> all to be on the same network (192.168.1.0/24)... and I need it to 
> preserve MACs and IPs.
> 

I think what you are looking for is a feature called WDS as far as I 
see. See hostap docs for details. I think what you are looking for is
a WDS-Link between AP-A and wlan0. Only problem is, that afaik WDS only 
works between two hostap-boxes.

Greets
Martin





From johnr  Wed Oct 30 12:19:21 2002
From: johnr (John Roark)
Date: Wed, 30 Oct 2002 15:19:21 -0500
Subject: extending a HostAP networks range
Message-ID: <3DC03EC9.5000101@wirelessocean.com>

 >John Roark schrieb:
 >> Besides the obvious solution of increasing the wattage and using a
 >> larger antenae... how would I extend the range of my wireless network.
 >> Is there a way to link HostAps so that where one ap's range ends 
another
 >> starts and extends the range by 50%? Some kind of dumb forwarder that
 >> simply repeats whatever it picks up (without NAT)? I want it to look
 >> like the client is talking directly to the main hostap, when in fact it
 >> is talking to another box that is merely extending the range of the
 >> hostap... is this possible?
 >>
 >> eth0 : AP-A : wlan0 -- <wireless network> -- wlan0 : "Extender"
 >>                                                |
 >>                                   <extended wireless network>
 >>                                                |
 >>                                              wlan0 : Client
 >>
 >> Is this a repeater? a bridge? does RDS do this (what is RDS?)? I 
want it
 >> all to be on the same network (192.168.1.0/24)... and I need it to
 >> preserve MACs and IPs.
 >>
 >
 >I think what you are looking for is a feature called WDS as far as I
 >see. See hostap docs for details. I think what you are looking for is
 >a WDS-Link between AP-A and wlan0. Only problem is, that afaik WDS only
 >works between two hostap-boxes.
 >
 >Greets
 >Martin
 >

Thanks for a quick reply,
I looked at the HostAP docs... and read the example they used for WDS. 
In my situation would I then want to do something like this? If I had 
the following:

AP-A has wlan0 with MAC 00:11:11:11:11:11 IP: 192.168.1.1
(AP-A also has eth0 that I will do NAT from the wireless over)
AP-B (the extender) has wlan0 with MAC 00:22:22:22:22:22 IP: 192.168.1.2
(AP-B has only wlan0 no other eth devs)

to set them in wds and extend AP-As range I would do the following:

AP-A config:
------------
iwpriv wlan0 wds_add 00:22:22:22:22:22
brctl addbr br0
#brctl addif br0 eth0 # don't bridge with eth0 because I will use NAT
brctl addif wlan0
brctl addif wlan0wds0
#ifconfig eth0 0.0.0.0 # also because eth0 is not part of the bridge dev
ifconfig wlan0 0.0.0.0
ifconfig wlan0wds0 0.0.0.0
ifconfig br0 192.168.1.1 up

AP-B (extender) config:
-----------------------
iwpriv wlan0 wds_add 00:11:11:11:11:11
# do I need to do any bridging here?
# or bring up wlan0wds0 or is that linked to AP-A's wlan0wds0?

This will not mangle the ethernet/IP packets (i.e. it will not change 
the mac or ip in the eth/ip headers... right?). I hope that makes some 
sense...

Thanks,
John

-- 
Hmm.  Your ideas are intriguing to me and I wish to
subscribe to your newsletter.

-Homer J. Simpson




From df_co  Wed Oct 30 12:29:06 2002
From: df_co (john extra)
Date: Wed, 30 Oct 2002 13:29:06 -0700
Subject: Roaming and WDS
Message-ID: <F156FCHOzyfyz5b6KZm0000003d@hotmail.com>

Hi All!

I was wondering about the relationship between WDS and Roaming and how 
roaming works in HostAP. In order for there to be roaming, must there be a 
WDS link in place between all of your APs before your clients can roam? If 
so, can the wlan0wds0 interface be routed over say wired ethernet or maybe 
over another ad-hoc like wireless link to extend the coverage of the two 
aps? That way even if the two APs can't directly talk to each other 
(distance problems) the clients can still roam.

I am greatly impressed by the people working on this driver...keep up the 
good work! Thank you all so much for your help on this problem!

John





_________________________________________________________________
Unlimited Internet access -- and 2 months free!? Try MSN. 
http://resourcecenter.msn.com/access/plans/2monthsfree.asp




From jsun  Wed Oct 30 13:49:26 2002
From: jsun (Jun Sun)
Date: Wed, 30 Oct 2002 13:49:26 -0800
Subject: Roaming and WDS
In-Reply-To: <F156FCHOzyfyz5b6KZm0000003d@hotmail.com>; from df_co@hotmail.com on Wed, Oct 30, 2002 at 01:29:06PM -0700
References: <F156FCHOzyfyz5b6KZm0000003d@hotmail.com>
Message-ID: <20021030134926.A17429@gateway.junsun.net>

On Wed, Oct 30, 2002 at 01:29:06PM -0700, john extra wrote:
> Hi All!
> 
> I was wondering about the relationship between WDS and Roaming

Those are two orthognal issues.  Roaming means multiple APs with
the same ESSID allowing client to move around them.  Those APs,
for example, can be connected through ethernet LAN and involves no
WDS at all.

WDS implies multiple APs connected through the radio (instead of ehternet
LAN in the previous case).  I think in WDS case APs are even allowed
to have different ESSIDs, which will actually disallow roaming .

Jun



From marcel  Wed Oct 30 15:04:54 2002
From: marcel (Marcel Prisi)
Date: Thu, 31 Oct 2002 00:04:54 +0100
Subject: Using "software" WEP encryption
Message-ID: <002701c28068$c31e1d40$c200a8c0@huggy>

Hi again !

I finally successfully updated my Tekram PC400's to latest firmwares (1.4.9)
using Intersil's WinUpdate tool.

I then tried a ftp transfer from the machine running hostap in Master mode
(linux-2.4.20pre11 P233MMX) and a FreeBSD 4.7 server (Celeron 333) both
using the same PC400 cards, and got 543.7kB/s, both machines in the same
room ...

I then added 128bit wep encryption and transfered the same file ... 94.1kB/s
... well ... WEP seems to slow things really much !

As I am running v 1.4.9 of the card's firmware, hostap kindly used
hardware-based WEP encryption. Is there a way to revert to software-based
WEP encryption, in order to "benchmark" it ?

I think I'll finally fire up openvpn instead of WEP :-)




From jkmaline  Wed Oct 30 15:31:27 2002
From: jkmaline (Jouni Malinen)
Date: Thu, 31 Oct 2002 01:31:27 +0200
Subject: Using "software" WEP encryption
In-Reply-To: <002701c28068$c31e1d40$c200a8c0@huggy>; from marcel@virtua.ch on Thu, Oct 31, 2002 at 12:04:54AM +0100
References: <002701c28068$c31e1d40$c200a8c0@huggy>
Message-ID: <20021031013127.A5265@jm.epitest.fi>

On Thu, Oct 31, 2002 at 12:04:54AM +0100, Marcel Prisi wrote:

> As I am running v 1.4.9 of the card's firmware, hostap kindly used
> hardware-based WEP encryption. Is there a way to revert to software-based
> WEP encryption, in order to "benchmark" it ?

Yes, host_decrypt and host_encrypt parameters for prism2_param. You
will need to set both to 1 in order to use software-based encryption and
decryption.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jasonb  Wed Oct 30 15:32:03 2002
From: jasonb (Jason Boxman)
Date: Wed, 30 Oct 2002 19:32:03 -0400
Subject: Using "software" WEP encryption
In-Reply-To: <002701c28068$c31e1d40$c200a8c0@huggy>
References: <002701c28068$c31e1d40$c200a8c0@huggy>
Message-ID: <200210301832.03481.jasonb@edseek.com>

On Wednesday 30 October 2002 06:04 pm, Marcel Prisi wrote:
> Hi again !
>
<snip>
> As I am running v 1.4.9 of the card's firmware, hostap kindly used
> hardware-based WEP encryption. Is there a way to revert to software-based
> WEP encryption, in order to "benchmark" it ?

Absolutely.  The prism2_param utility has an option to enable software WEP I 
believe.

> I think I'll finally fire up openvpn instead of WEP :-)
>

host_encrypt:
  0 = do not use host encryption unless in Host AP mode
  1 = use host encryption in all modes

-- 

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





From victor.aleo  Wed Oct 30 15:55:46 2002
From: victor.aleo (Victor Aleo)
Date: Thu, 31 Oct 2002 00:55:46 +0100
Subject: Handoff time measurement
Message-ID: <3DC07182.8070800@estudiant.upc.es>

Hi,

Any one knows how much time it takes the handoff in a very simple WLAN 
network with 2 APs (running the Prism2 driver as Master mode) and using 
a station (as Managed mode) with also running Prism2?

I refer to the MAC (layer-2 handoff), without using MobileIP or anything 
else. I have tried to measured it, but the results I have got are very 
high: between 1 and 2 seconds!!! When it should be around a few hundred 
milliseconds (200 at much, maybe). Of course, the handoff time depends 
of the beacon period that in my case is the default, thus 100 ms.

I would appreciate any suggestions,

Thanks

-- 
Victor





From df_co  Wed Oct 30 16:09:06 2002
From: df_co (john extra)
Date: Wed, 30 Oct 2002 17:09:06 -0700
Subject: Roaming and WDS
Message-ID: <F173vg58w1Dxvq7t2JI0000af87@hotmail.com>

Thanx for the insight Jun!

I hope my new understanding isn't too oversimplified...If roaming was really 
only about ESSIDs then would it be safe to say that any AP that has support 
for ESSIDs would allow clients to roam from AP to AP? So my clients could 
roam from my netgear AP to my HostAP AP if on the same subnet with the same 
ESSIDs and that's it?

I sure hope it's that simple...

John

>From: Jun Sun <jsun at junsun.net>
>To: john extra <df_co at hotmail.com>
>CC: hostap at shmoo.com
>Subject: Re: Roaming and WDS
>Date: Wed, 30 Oct 2002 13:49:26 -0800
>
>On Wed, Oct 30, 2002 at 01:29:06PM -0700, john extra wrote:
> > Hi All!
> >
> > I was wondering about the relationship between WDS and Roaming
>
>Those are two orthognal issues.  Roaming means multiple APs with
>the same ESSID allowing client to move around them.  Those APs,
>for example, can be connected through ethernet LAN and involves no
>WDS at all.
>
>WDS implies multiple APs connected through the radio (instead of ehternet
>LAN in the previous case).  I think in WDS case APs are even allowed
>to have different ESSIDs, which will actually disallow roaming .
>
>Jun


_________________________________________________________________
Choose an Internet access plan right for you -- try MSN! 
http://resourcecenter.msn.com/access/plans/default.asp




From jsun  Wed Oct 30 16:36:48 2002
From: jsun (Jun Sun)
Date: Wed, 30 Oct 2002 16:36:48 -0800
Subject: Roaming and WDS
In-Reply-To: <F173vg58w1Dxvq7t2JI0000af87@hotmail.com>; from df_co@hotmail.com on Wed, Oct 30, 2002 at 05:09:06PM -0700
References: <F173vg58w1Dxvq7t2JI0000af87@hotmail.com>
Message-ID: <20021030163648.A17603@gateway.junsun.net>

On Wed, Oct 30, 2002 at 05:09:06PM -0700, john extra wrote:
> Thanx for the insight Jun!
> 
> I hope my new understanding isn't too oversimplified...If roaming was really 
> only about ESSIDs then would it be safe to say that any AP that has support 
> for ESSIDs would allow clients to roam from AP to AP? So my clients could 
> roam from my netgear AP to my HostAP AP if on the same subnet with the same 
> ESSIDs and that's it?
>

Yes.  

Just make sure they are also on the same channel (Not sure what
happens if APs have the same ESSID but on different channel.  Hmm, looks
like an interesting experiment to do...)

> I sure hope it's that simple...
>

Things don't have to be that complicated ... :-)

Jun



From victor.aleo  Wed Oct 30 18:27:42 2002
From: victor.aleo (Victor Aleo)
Date: Thu, 31 Oct 2002 03:27:42 +0100
Subject: SCANREQUEST and JOINREQUEST
Message-ID: <3DC0951E.2050802@estudiant.upc.es>

Hi,

I have running the Prism2 version 2002-05-1 and I would like to know if 
I can modify the SCANREQUEST and JOINREQUEST functions due to it seems 
to me that is this the main cause for the slow handoff.

BTW, when a station is disassociated from an AP: it always tries to 
associate again with it before selecting another one? I guess so, and I 
think this is the main reason for the slow handoff with this version of 
the Prism2 driver.

Could anyone confirm me these points?

Thanks a lot,

Victor

-- 
Victor





From pymanju  Wed Oct 30 20:10:49 2002
From: pymanju (Manjunathan PY)
Date: Thu, 31 Oct 2002 09:40:49 +0530
Subject: Info on Layer 2 Update
Message-ID: <00b501c28093$7f76dfc0$468101d9@pcwks356>

Hi,
  I would like to know how "Layer 2 Update" is done,
when a Mobile Station moves from the radio range of an Access point to
another Access point.

Does HostAP do such an update to support roaming of mobile station between
Access Point ? How!

Thanks,
Manjunathan PY






From tanyh  Thu Oct 31 01:38:53 2002
From: tanyh (Yanghwee Tan)
Date: Thu, 31 Oct 2002 17:38:53 +0800 (SGT)
Subject: missing essid? Fixed!
In-Reply-To: <Pine.GSO.4.43L0.0210301441520.22717-100000@marcus.krdl-core.bii>
Message-ID: <Pine.GSO.4.43L0.0210311735300.1485-100000@marcus.krdl-core.bii>

hi,

about the missing id problem that i previously
had sometime ago...

i got it fixed by doing the following upgrade:

* Wireless Tools remains at ver25
* Kernel upgraded from 2.4.18-6 to 2.4.19
* Pcmcia-cs recompiled under kernel 2.4.19
* Hostap recompiled under kernel 2.4.19

and everything is okay now.
thanks to all who try to help mua.


Cheers,
Yanghwee




From ch_lei  Thu Oct 31 02:42:04 2002
From: ch_lei (Lei Chuanhua)
Date: Thu, 31 Oct 2002 18:42:4 +0800
Subject: Roaming and WDS
Message-ID: <200210311845194.SM00130@hualab>

in Wed, Oct 30, 2002 at 05:09:06PM -0700, john extra wrote:
> Thanx for the insight Jun!
> 
> I hope my new understanding isn't too oversimplified...If roaming was really 
> only about ESSIDs then would it be safe to say that any AP that has support 
> for ESSIDs would allow clients to roam from AP to AP? So my clients could 
> roam from my netgear AP to my HostAP AP if on the same subnet with the same 
> ESSIDs and that's it?
>

Yes.  

Just make sure they are also on the same channel (Not sure what
happens if APs have the same ESSID but on different channel.  Hmm, looks
like an interesting experiment to do...)
===>I have tested this case, and it worked very well.

> I sure hope it's that simple...
>
         hualab
  





From imp  Thu Oct 31 04:15:22 2002
From: imp (=?utf-7?B?K3ZCWFhaY1gwLQ==?=)
Date: Thu, 31 Oct 2002 21:15:22 +0900
Subject: watch dog time out
Message-ID: <HIEILNBGFIFLDLBJCOLAAEJECCAA.imp@airlinktek.com>

Dear all

Sum time the hostap stop the card service by transmit timed out error..
I was downloading some stream file.. after a few hours.. about 2,3 hours..

hostap stop by bellow debugging message.. 

Anyone comment me about it ? Thanks.
Best Regards 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0 Tx timed out! Resetting card
hostap_cs: wlan0: resetting card
cs: read_cis_mem(1, 0x1f0, 1)
cs:  0x41 0x60 0x76 0xfe ...
cs: write_cis_mem(1, 0x1f0, 1)
wlan0: Interrupt, but SWSUPPORT0 does not match: FFFF != 8A32 - card removed?
IRQ LOCK: IRQ6 is locking the system, disabled
cs: write_cis_mem(1, 0x1f0, 1)
prism2_hw_init()
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0 Tx timed out! Resetting card
wlan0: Port type setting to 6 failed
init led timer 
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0 Tx timed out! Resetting card
prism2_tx_timeout: wake up queue
hostap_cs: wlan0: resetting card
cs: read_cis_mem(1, 0x1f0, 1)
cs:  0x41 0x60 0x76 0xfe ...
cs: write_cis_mem(1, 0x1f0, 1)
cs: write_cis_mem(1, 0x1f0, 1)
prism2_hw_init()
wlan0: Port type setting to 6 failed
init led timer 
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0 Tx timed out! Resetting card
wlan0: MAC port 0 enabling failed
prism2_tx_timeout: wake up queue
hostap_cs: wlan0: resetting card
cs: read_cis_mem(1, 0x1f0, 1)
cs:  0x41 0x60 0x76 0xfe ...
cs: write_cis_mem(1, 0x1f0, 1)
cs: write_cis_mem(1, 0x1f0, 1)
prism2_hw_init()
wlan0: MAC data length setting to 2304 failed
init led timer 
wlan0: MAC port 0 enabling failed


From xdhuang  Thu Oct 31 05:47:26 2002
From: xdhuang (Huang Xiaodong)
Date: 31 Oct 2002 21:47:26 +0800
Subject: Info on Layer 2 Update
Message-ID: <20021031214726.28166.qmail@eyou.com>

Yes, of course, the hostap does.

You can see the function "static void prism2_host_roaming(local_info_t
*local)" for details in the file "hostap_hw.c".(i am using hostap-2002-10-12
version.)

Huang Xiaodong





--http://www.eyou.com
--??????????????????????  ????????  ????????  ????????  ????????...????????





From tischer  Thu Oct 31 05:02:30 2002
From: tischer (Ingo Tischer)
Date: Thu, 31 Oct 2002 14:02:30 +0100
Subject: Both AP and Bridge-Mode
Message-ID: <20021031130230.14032.qmail@turing.mathematik.uni-ulm.de>

Hi there,

is is possible to use the HostAP Software to manage the following:

net1 ----Wired----Server1   +++++++++++++   Server2----Wired - net2
                    +                           +
                Laptop1(wireless           Laptop2(wireless on server2)
                on server1)

Can I use HostAP to connect the two wired lans(servers) AND different
wireless clients on each server?

Please reply.

Kind regards

Ingo Tischer



From jt  Thu Oct 31 09:49:39 2002
From: jt (Jean Tourrilhes)
Date: Thu, 31 Oct 2002 09:49:39 -0800
Subject: Handoff time measurement
Message-ID: <20021031174939.GA2910@bougret.hpl.hp.com>

Victor Aleo wrote :
> 
> Hi,
> 
> Any one knows how much time it takes the handoff in a very simple WLAN 
> network with 2 APs (running the Prism2 driver as Master mode) and using 
> a station (as Managed mode) with also running Prism2?
> 
> I refer to the MAC (layer-2 handoff), without using MobileIP or anything 
> else. I have tried to measured it, but the results I have got are very 
> high: between 1 and 2 seconds!!! When it should be around a few hundred 
> milliseconds (200 at much, maybe). Of course, the handoff time depends 
> of the beacon period that in my case is the default, thus 100 ms.

	That sounds like the proper number. Few hundred ms is totally
unrealistic, I don't know where you go this idea.
	Just do the maths. You need to "probe" every channel to find a
new AP. If you use passive scanning, you need to wait at least one
beacon period on every single channel, so minimum 1.4s. If you use
active scanning, you can bring that down somewhat (two contention +
one max packet size per channel - depend on traffic), but I don't
expect the Intersil firmware to do that (at least, not without the
usual assortment of bugs).
	Not also that you don't want to trigger excessive handoffs, so
because of fading and interference (which may last in the order of
seconds), you will use a long term average to trigger handoff (like
SNR), which may delay the start of handoff in some situations. If you
try to trigger handoff faster (let say, every time you miss a beacon),
your system will become very unstable (so worthless).

> I would appreciate any suggestions,
> 
> Thanks
> 
> -- 
> Victor

	Good luck...

	Jean



From xdhuang  Thu Oct 31 23:25:21 2002
From: xdhuang (Huang Xiaodong)
Date: 1 Nov 2002 15:25:21 +0800
Subject: Trying to free nonexistent resource <00001800-0000183f>
Message-ID: <20021101152521.94611.qmail@eyou.com>

System pop up this message "Trying to free nonexistent resource
<00001800-0000183f>, when I using the "hostap-2001-10-12" version with Redhat
Linux 7.1. It seems like error of the driver.
Did you ever see that?

Please comment.

Huang Xiaodong





--http://www.eyou.com
--??????????????????????  ????????  ????????  ????????  ????????...????????





