headers
Peter Buelow | 1 Jan 2003 01:42

RE: Klogd messages

Actually, it would be nice if these were in some other log. syslog getting
full of this is not useful (well, to me anyway), but the information from
hostap is. Currently, I'm cutting a pasting this stuff out cause I want to
parse through it from time to time, but other syslog stuff that is as
important or more important get drowned out too easily. Any chance this
could go into some sort of other log file in /var/log?

> I am also experiencing the same fluctuation between 5.5 and 11Mbit (not
> as often though).
>
> I do value the messages and would not want to see them removed though.
>
> Sergio
>
>> -----Original Message-----
>> From: hostap-admin <at> shmoo.com [mailto:hostap-admin <at> shmoo.com] On Behalf
> Of
>> Michael Shuler
>> Sent: Tuesday, December 31, 2002 12:20 PM
>> To: hostap <at> shmoo.com
>> Subject: Klogd messages
>>
>> This is what my log files contains on our test AP:
>> Apr 28 12:24:41 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate lowered to 55
>> Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
> TX
>> rate raised to 110
>> Apr 28 12:24:42 (none) user.debug klogd: wlan0: STA 00:02:2d:3f:fe:ea
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jouni Malinen | 1 Jan 2003 02:23
Picon
Picon

Re: multiple reassociation at HostAP

On Mon, Dec 30, 2002 at 06:28:48AM -0800, Mohit bajpai wrote:

> I am using the hostapd driver released on 2002-10-12 for WLAN AP with Linksys WPC11 cards. While moving
between two APs it is observed that the number of times reassociation request comes is not constant,
sometimes more than one reassociation request comes when we move the STA to new AP area. 

Do you mean that the station sends reassociation request multiple times
to the same (new) AP? This could indicate that the previous
reassociation failed for some reason (e.g., timeout in getting
reassociation reply for the request).

> Though the new AP shows that the STA has associated with it , the STA shows the MAC address of the old AP for
several seconds before showing the new APs MAC address. Is it ok to have multiple reassociation requests?
How can we detect, at the hostap, that the STA is finally associated to it? 

IEEE 802.11 specifies that station can have only one association at any
given time, so at least stations should not send reassociation to
multiple APs at the same time. It is OK to authenticate with multiple
APs. From the AP view point, the station has completed association when
it acknowledges the association reply from the AP. 2002-10-12 release
does not check for this ACK frame, but latest CVS version does.

--

-- 
Jouni Malinen                                            PGP id EFC895FA
Permalink | Reply | 0 comments |
headers
Jouni Malinen | 1 Jan 2003 02:24
Picon
Picon

Re: reassosciation request comes more than once!

On Fri, Dec 27, 2002 at 07:54:04PM +0530, Mohit Bajpai wrote:

>     I have been trying out IAPP implementation with  latest hostap driver released on 2002-10-12.  I am using
the hostapd mode of the hostap driver.During testing the MOVE operation I found that when STA moves to new
AP the new AP detects reassociation of STA more than once. could you please tell that whether this multiple
detection of reassociating STA should happen or not because if it is so then it will send move signal more
than once which does not seem to be correct.

If the station sends reassociation request multiple times, current
hostapd will report each reassociation as a new one. If this is not
desired, some kind of timer could be used to skip higher-level
processing of reassociations (the request frame itself needs to be
replied to, but there is probably no need to use, e.g., IAPP for each
reassociation that is happening within a short period of time.

--

-- 
Jouni Malinen                                            PGP id EFC895FA
Permalink | Reply | 0 comments |
headers
Victor Aleo | 2 Jan 2003 19:37
Picon

Resetting card problem

Hi all,

I have the next problem using 2 APs and 1 station configured as wlan1 
(all of them running the latest release hostap-2002-10-12.tar.gz): when 
the station (which is associated with one AP and sending data) is 
disassociated (upon a "Disassociation" message from the AP) most of the 
times produces a reset of the station card (wlan1).

Has been this problem solved in the last CVS version?

Thanks,

Victor

wlan1: LinkStatus=2 (Disconnected)
wlan1: LinkStatus: BSSID=xx:xx:xx:xx:xx:xx
wlan1: hfa384x_setup_bap - timeout after
wlan1: TXEXC - fid=0x0258 - could not read txdesc
wlan1: scheduled card reset
hostap_pci: wlan1: resetting card
wlan1: removed pending cmd_queue entry (type=1, cmd=0x010b, param0=0x0138)
prism2_hw_init()
prism2_hw_config: initialized in 17874 iterations
prism2_tx_timeout: wake up queue
wlan0: xx:xx:xx:xx:xx:xx auth (alg=0 trans#=1 stat=0 len=6fc=00b0) ==> 1 
(authentication denied)
wlan1: LinkStatus=1 (Connected)
wlan1: LinkStatus: BSSID=xx:xx:xx:xx:xx:xx
Permalink | Reply | 0 comments |
headers
Jason Boxman | 2 Jan 2003 21:40

HostAP and D-Link 614+

I tired to use a WPC11v3 Prism2 card to speak to a D-Link 614+ to no
avail.  My syslog has the following entries.  I am using 2002-10-12.  It
associates, but when I send a DHCP discover things stop working.

Anyone have any thoughts on this encounter?

Jan  1 00:56:08 rachael kernel: hostap_cs: CS_EVENT_CARD_INSERTION
Jan  1 00:56:08 rachael kernel: prism2_config()
Jan  1 00:56:08 rachael kernel: hostap_cs: setting Vcc=50 (from config)
Jan  1 00:56:08 rachael kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
Jan  1 00:56:08 rachael kernel: IO window settings: cfg->io.nwin=1
dflt.io.nwin=1
Jan  1 00:56:08 rachael kernel: io->flags = 0x0046, io.base=0x0000, len=64
Jan  1 00:56:08 rachael kernel: hostap_cs: index 0x01: Vcc 5.0, irq 3, io
0x0100-0x013f
Jan  1 00:56:09 rachael kernel: hostap_cs: Registered netdevice wlan0
Jan  1 00:56:09 rachael kernel: prism2_hw_init()
Jan  1 00:56:09 rachael kernel: prism2_hw_config: initialized in 17300
iterations
Jan  1 00:56:09 rachael kernel: wlan0: NIC: id=0x801a v1.0.0
Jan  1 00:56:09 rachael kernel: wlan0: PRI: id=0x15 v1.0.5
Jan  1 00:56:09 rachael kernel: wlan0: STA: id=0x1f v1.3.4
Jan  1 00:56:09 rachael kernel: wlan0: defaulting to host-based encryption
as a workaround for firmware bug in Host AP mode WEP

Jan  1 01:01:26 rachael kernel: wlan0: LinkStatus=2 (Disconnected)
Jan  1 01:01:26 rachael kernel: wlan0: LinkStatus: BSSID=00:06:25:a9:f7:da
Jan  1 01:01:30 rachael kernel: wlan0: LinkStatus=2 (Disconnected)
Jan  1 01:01:30 rachael kernel: wlan0: LinkStatus: BSSID=44:44:44:44:44:44
Jan  1 01:01:34 rachael pumpd[7862]: starting at (uptime 0 days, 3:19:10)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Per Weisteen | 2 Jan 2003 22:36
Picon

Use Linksys WMP11 (PCI) with hostap ?


I feel there is some confusion re. the use of Linksys PCI WMP11 card as an Access Point.
I've seen some info indicating that the card is not compatible with the hostap driver
(http://trekweb.com/~jasonb/articles/hostap_20021012.shtml) while
AVS (http://www.linux-wlan.org/) in their compatibility list states that the card is a PRISM2
compatible card.

Could anyone enlighten me on this subject ?

If the WMP11 Card is not supported could anyone suggest a PCI card (preferrably with external antenna) that
is ?

Regards,

--
Per W.
Permalink | Reply | 3 comments |
headers
André Corrêa | 3 Jan 2003 00:33
Picon
Favicon

Association and Disassociation info


Hi list. I need to do something unusual and maybe somebody in this list
can help me.

I need to know, as quickly as possible, when a station disassociates from
the AP. Looking at /var/log/debug I've found that it takes 5 minutes for
the AP to realize that the station disassociated.

Is there a way for me to know quickly that a STA disassociated? I've
thought that I may be able to change hostap's code to decrease association
timeout to 1 minute or less. Are there any implications in doing this?

Is there a better way to know an station disassociated then looking at
/var/log/debug or to files created at the /proc/net/hostap/wlan0
directory?

Any help will be apreciated.

Tks in advance.

Andre
Permalink | Reply | 1 comment |
headers
Peter De Cleyn | 3 Jan 2003 00:48
Picon

Re: Use Linksys WMP11 (PCI) with hostap ?

On Thu, 2 Jan 2003, Per Weisteen wrote:

>
> I feel there is some confusion re. the use of Linksys PCI WMP11 card as an Access Point.
> I've seen some info indicating that the card is not compatible with the hostap driver
> (http://trekweb.com/~jasonb/articles/hostap_20021012.shtml) while
> AVS (http://www.linux-wlan.org/) in their compatibility list states that the card is a PRISM2
compatible card.

Per,

Only the firmware of your card is not compatible with the HostAP mode, so
other modes should work!.
This can easily be changed as is also described in the article ( or one of
the other 2 about wlans) on the site you mention. The trick is to load
another secondary firmware in RAM. I tried this with the WPC 11 (pcmcia version)
and this works pretty well.

Peter

>
> Could anyone enlighten me on this subject ?
>
> If the WMP11 Card is not supported could anyone suggest a PCI card (preferrably with external antenna)
that is ?
>
> Regards,
>
> --
> Per W.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jason Boxman | 3 Jan 2003 00:55

Re: Use Linksys WMP11 (PCI) with hostap ?

Per Weisteen said:

The WMP11 PCI card is no longer Prism2 chipset based.  It is now Broadcom
based.  This happened some months ago, so it's possible AVS hasn't updated
their compatibility list.

>
> I feel there is some confusion re. the use of Linksys PCI WMP11 card as an
> Access Point.
> I've seen some info indicating that the card is not compatible with the
> hostap driver
> (http://trekweb.com/~jasonb/articles/hostap_20021012.shtml) while
> AVS (http://www.linux-wlan.org/) in their compatibility list states that
> the card is a PRISM2 compatible card.
>
> Could anyone enlighten me on this subject ?
>
> If the WMP11 Card is not supported could anyone suggest a PCI card
> (preferrably with external antenna) that is ?
>
> Regards,
>
> --
> Per W.
>
Permalink | Reply | 0 comments |
headers
Jason Boxman | 3 Jan 2003 00:59

Re: Use Linksys WMP11 (PCI) with hostap ?

Peter De Cleyn said:

> On Thu, 2 Jan 2003, Per Weisteen wrote:
>
>>
>> I feel there is some confusion re. the use of Linksys PCI WMP11 card as
>> an Access Point.
>> I've seen some info indicating that the card is not compatible with the
>> hostap driver
>> (http://trekweb.com/~jasonb/articles/hostap_20021012.shtml) while
>> AVS (http://www.linux-wlan.org/) in their compatibility list states that
>> the card is a PRISM2 compatible card.
>
> Per,
>
> Only the firmware of your card is not compatible with the HostAP mode, so
> other modes should work!.

I think you're thinking of cards with STA v1.4.2.  That fails to function
with HostAP mode.

New the WMP11 (labeled v2.7 on the chipset itself, but you cannot tell
from the labeling) cards use the Broadcom chipset and fail to work at all.
 HostAP does not support them.

> This can easily be changed as is also described in the article ( or one of
> the other 2 about wlans) on the site you mention. The trick is to load
> another secondary firmware in RAM. I tried this with the WPC 11 (pcmcia
> version)
> and this works pretty well.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane