From jar  Fri Aug  1 01:26:02 2003
From: jar (jar)
Date: Fri, 01 Aug 2003 11:26:02 +0300
Subject: Flashing with prism2_srec
Message-ID: <3F2A241A.9000202@pcuf.fi>


Is the prism2_srec (coming with hostap-0.0.4) now safe enough to flash 
the prism2 card (0x8002 1.0.1, wl200) with e.g s1010506.hex file? At 
least the "-i" option is still needed ?

Regards, Jar



From lcaeiro  Fri Aug  1 02:59:48 2003
From: lcaeiro (caeiro)
Date: Fri, 1 Aug 2003 10:59:48 +0100
Subject: TX events
Message-ID: <001d01c35813$ac986fc0$6501a8c0@home>

How can I know when a data packet is sent from the card tx buffer? Can I receive TX ok and TX exc events in the driver? I need to activate something?

Thanks in advance

LC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030801/2feda804/attachment.htm 


From lphao  Fri Aug  1 01:51:24 2003
From: lphao (lphao)
Date: Fri, 1 Aug 2003 16:51:24 +0800
Subject: a question about sniffer
Message-ID: <200308010824.h718Oil32130@mail.tju.edu.cn>

hi,all

I want to dump the raw 802.11 frame(especially data type) and the ip layer header in my file , I set the DWL-650 card in monitor mode by "iwpriv wlan0 monitor 2",but I feel the number of  data frame is less than the real packets that I send from another pc.And how can I dump the upper layer infomation (eg. IP layer).Could you give me some suggestion? 
	

Regards!


 				

????????lphao
????????lphao at tju.edu.cn
??????????2003-08-01




From proski  Fri Aug  1 08:29:08 2003
From: proski (Pavel Roskin)
Date: Fri, 1 Aug 2003 11:29:08 -0400 (EDT)
Subject: Flashing with prism2_srec
In-Reply-To: <3F2A241A.9000202@pcuf.fi>
References: <3F2A241A.9000202@pcuf.fi>
Message-ID: <Pine.LNX.4.56.0308011127000.16027@marabou.research.att.com>

On Fri, 1 Aug 2003, jar wrote:

> Is the prism2_srec (coming with hostap-0.0.4) now safe enough to flash
> the prism2 card (0x8002 1.0.1, wl200) with e.g s1010506.hex file? At
> least the "-i" option is still needed ?

prism2_srec should be safe now.  Try without "-i" first.  If needed, use
"-i", but it's more risky, so it's up to you to decide.

-- 
Regards,
Pavel Roskin



From mrcool  Fri Aug  1 10:11:55 2003
From: mrcool (Jerry)
Date: Fri, 1 Aug 2003 12:11:55 -0500
Subject: off topic: Signal Strength in general...
Message-ID: <002601c35850$023a29a0$1e04000a@ns>

Hello all, i was wondering if you all had noticed some of the same things i have...

Does it seem like some days signal is better than others?   For instance, this morning (USA, CDT, 7ish), my signal was so weak that i couldnt get any webpages to come up at all ("Web site found, waiting for reply..." but nothing would load), trillian seems to work (I guess it doesnt need much bandwidth), but email definately doesnt.

Granted, i have a long link (12ish miles), but it usually works "better" in the morninig than later on in the day.  I read somewhere that sunlight has a tendency to reduce signal strength some, as well as sunspots being a problem.  I know that FM radio wouldnt necessarily be affected by the same things as 2.4Ghz, but the radio station i normally listen to wouldnt come in much either this morning, this being opposite to what i had observed prior  (poor FM recption, better 2.4, and vice-versa).

Sometimes at night my signal is as much as twice the strength of the daytime signal (which means at night my bandwidth has a tendency to increase, even though it may be peak inet usage in my area...southeast Kansas USA).  Are these observations roughly the same as you all find in the wild? or am i just crazy (matter of opinion  ;).

one last question... Is the info returned by wifimon accurate? as it said i had plenty (average) signal this morning, but it dint want to go anywhere... Sorry if this is off topic, but i will appreciate everyones input on this, and i think everyone can get some use from the discussion, as its the basis of all hostap does.

Thanks for all input...

Jerryf 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030801/1e1a10ce/attachment.htm 


From jiri.fojtasek  Fri Aug  1 10:31:22 2003
From: jiri.fojtasek (Jiri Fojtasek)
Date: Fri, 01 Aug 2003 19:31:22 +0200
Subject: TX events
In-Reply-To: <001d01c35813$ac986fc0$6501a8c0@home>
References: <001d01c35813$ac986fc0$6501a8c0@home>
Message-ID: <3F2AA3EA.7030504@hlohovec.net>

caeiro wrote:

> How can I know when a data packet is sent from the card tx buffer? Can 
> I receive TX ok and TX exc events in the driver? I need to activate 
> something?
>  
> Thanks in advance
>  
> LC
>
>------------------------------------------------------------------------
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
Hello

Activate kernel debug logging in to a file and use prism2_param wlanx 
dump command ....

Jiri





From jiri.fojtasek  Fri Aug  1 10:35:10 2003
From: jiri.fojtasek (Jiri Fojtasek)
Date: Fri, 01 Aug 2003 19:35:10 +0200
Subject: Flashable 1.5.6 for Prism 2 available
In-Reply-To: <Pine.LNX.4.56.0307311513360.8269@marabou.research.att.com>
References: <Pine.LNX.4.56.0307311513360.8269@marabou.research.att.com>
Message-ID: <3F2AA4CE.1030805@hlohovec.net>

Pavel Roskin wrote:

>Hello!
>
>A good guy has sent me flashable Intersil firmware 1.5.6 for Prism 2
>chipset.  It has been added to
>http://www.red-bean.com/~proski/firmware/1.5.6.tar.gz
>
>The file is called s1010506.hex, quite expectedly.
>
>Supported platforms:
>  0x8002 1.0.0,  0x8002 1.0.1,  0x8003 1.0.0,  0x8003 1.0.1,  0x8004 1.0.0
>  0x8008 1.0.0
>
>Primary firmware doesn't need to be upgraded, version 0.3.0 is OK (and I
>don't think there is a newer version).  I have tested the new firmware
>with ZoomAir 4100, and it works just fine with the latest HostAP.
>
>The latest firmware is currently:
>
>                   Flash          RAM
>
>Prism 2            1.5.6 (new!)   1.7.1
>Prism 2.5          1.7.4          1.7.4
>
>  
>
Wow thanks :) Ill try flash my 8003 pcmcia. Have anyone tested this 
combination ?

Jiri



From williamt  Fri Aug  1 11:02:27 2003
From: williamt (William Tai)
Date: Fri, 1 Aug 2003 11:02:27 -0700
Subject: Tx power conttrol issue
Message-ID: <000d01c35857$11c1f9f0$e6f0c53f@williamt>

Hi All:

    I try to control my tx power on my prism2 card; however I failed.
I notice that there are 4 types of power.
 enum {
  PRISM2_TXPOWER_AUTO = 0, PRISM2_TXPOWER_OFF,
  PRISM2_TXPOWER_FIXED, PRISM2_TXPOWER_UNKNOWN
 } txpower_type;
Before I try to call prism2_ioctl_siwtxpow( ), that power type should be on
this card?
Is there any body succeed to control tx power using hostap fw and wanna
share your experience with us?


Thanx a lot
William



From jt  Fri Aug  1 11:03:12 2003
From: jt (Jean Tourrilhes)
Date: Fri, 1 Aug 2003 11:03:12 -0700
Subject: TX events
Message-ID: <20030801180312.GA28131@bougret.hpl.hp.com>

caeiro wrote :
> 
> How can I know when a data packet is sent from the card tx buffer?

	/proc/net/dev will increase

> Can I receive TX ok and TX exc events in the driver?

	For most practical purpose, you only need "TX exc", and it is
available as an iwevent (WE-14 and later).

> I need to activate something?

	You need WE-14 (2.4.20 or later), Wireless Tools v24 or later,
and a driver that support Wireless Events (HostAP v0.0.1 or
later). And you need to read the man page of iwevent.

	Jean



From jsun  Fri Aug  1 11:04:38 2003
From: jsun (Jun Sun)
Date: Fri, 1 Aug 2003 11:04:38 -0700
Subject: Tx power conttrol issue
In-Reply-To: <000d01c35857$11c1f9f0$e6f0c53f@williamt>
References: <000d01c35857$11c1f9f0$e6f0c53f@williamt>
Message-ID: <20030801180438.GA20443@gateway.junsun.net>

On Fri, Aug 01, 2003 at 11:02:27AM -0700, William Tai wrote:
> Hi All:
> 
>     I try to control my tx power on my prism2 card; however I failed.
> I notice that there are 4 types of power.
>  enum {
>   PRISM2_TXPOWER_AUTO = 0, PRISM2_TXPOWER_OFF,
>   PRISM2_TXPOWER_FIXED, PRISM2_TXPOWER_UNKNOWN
>  } txpower_type;
> Before I try to call prism2_ioctl_siwtxpow( ), that power type should be on
> this card?
> Is there any body succeed to control tx power using hostap fw and wanna
> share your experience with us?
>

I believe txpower control is removed from v0.0.4 as Jouni thinks
the original implementation is flawed.  Search the mailing list
for an earlier post about txpower.

Jun



From williamt  Fri Aug  1 11:51:13 2003
From: williamt (William Tai)
Date: Fri, 1 Aug 2003 11:51:13 -0700
Subject: Tx power conttrol issue
References: <000d01c35857$11c1f9f0$e6f0c53f@williamt>
	<20030801180438.GA20443@gateway.junsun.net>
Message-ID: <003101c3585d$e1afe630$e6f0c53f@williamt>

Hi Jun:

Thanx for the quick response.
I search the previous post related to txpower.
There are a few talked about txpower.
However I get a little confused.
There is a post "txpower not working after reset [PATCH included]" posted in
Jun.
It looks like that txpower is working, but has a minor bug.
>From your mail, it seems that txpower is not working.
I download the hostap-0.0.4 and check it.
The txpower code is embraced by a MACRO RAW_TXPOWER_SETTING.
However this macro is not defined yet.
That's what you mean "I believe txpower control is removed from v0.0.4."


Thanx
William




----- Original Message ----- 
From: "Jun Sun" <jsun at junsun.net>
To: "William Tai" <williamt at arescom.com>
Cc: <hostap at shmoo.com>
Sent: Friday, August 01, 2003 11:04 AM
Subject: Re: Tx power conttrol issue


> On Fri, Aug 01, 2003 at 11:02:27AM -0700, William Tai wrote:
> > Hi All:
> >
> >     I try to control my tx power on my prism2 card; however I failed.
> > I notice that there are 4 types of power.
> >  enum {
> >   PRISM2_TXPOWER_AUTO = 0, PRISM2_TXPOWER_OFF,
> >   PRISM2_TXPOWER_FIXED, PRISM2_TXPOWER_UNKNOWN
> >  } txpower_type;
> > Before I try to call prism2_ioctl_siwtxpow( ), that power type should be
on
> > this card?
> > Is there any body succeed to control tx power using hostap fw and wanna
> > share your experience with us?
> >
>
> I believe txpower control is removed from v0.0.4 as Jouni thinks
> the original implementation is flawed.  Search the mailing list
> for an earlier post about txpower.
>
> Jun
>



From eharris  Fri Aug  1 11:47:43 2003
From: eharris (Evan Harris)
Date: Fri, 1 Aug 2003 13:47:43 -0500 (CDT)
Subject: hostap on Senao 2511 wireless cards
Message-ID: <Pine.LNX.4.44.0308011342140.25345-100000@kinison.puremagic.com>


I'm trying to get hostap running on some Senao 2511 cards, and am getting
some error messages when starting the card.  The Senao cards are supposed to
be Prism reference design cards, and have been working fine for us for a
long time with wlan-ng as the client side.

Any help or suggestions anyone can give would be greatly appreciated.

Linux PCMCIA Card Services 3.2.2
  kernel build: 2.4.20 unknown
  options:  [pci] [cardbus]
Intel ISA/PCI/CardBus PCIC probe:
PCI: Found IRQ 5 for device 00:10.0
  Ricoh RL5C475 rev 80 PCI-to-CardBus at slot 00:10, mem 0xf75ff000
    host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 5] [lat
168/176] [bus 2/5]
    ISA irqs (default) = 3,4,7,12 PCI status changes
cs: memory probe 0xa0000000-0xa0ffffff: clean.
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.0.4 - 2003-07-27 (Jouni Malinen <jkmaline at cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
prism2_config()
hostap_cs: setting Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x388-0x38f
0x3c0-0x3df 0x4d0-0x4d7
cs: IO port probe 0x0230-0x0387: clean.
cs: IO port probe 0x0390-0x03bf: clean.
cs: IO port probe 0x03e0-0x04cf: clean.
cs: IO port probe 0x04d8-0x04ff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
hostap_cs: index 0x01: Vcc 3.3, irq 3, io 0x0100-0x013f
hostap_cs: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_init: initialized in 190 ms
wlan0: hfa384x_cmd: entry still in list? (entry=c7ffdc60, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=c7ffdc60,
type=0, cmd=0x0021, param0=0xfd0b, EVSTAT=8010 INTEN=0010)
wlan0: interrupt delivery does not seem to work
wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd0b, len=8)
Could not get RID for component NIC
wlan0: hfa384x_cmd: entry still in list? (entry=c7ffdc60, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=c7ffdc60,
type=0, cmd=0x0021, param0=0xfd02, EVSTAT=8010 INTEN=0010)
wlan0: interrupt delivery does not seem to work
wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd02, len=8)
Could not get RID for component PRI
wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wlan0: hfa384x_cmd_issue - timeout - reg=0x8021
wlan0: hfa384x_cmd: entry still in list? (entry=c7ffdc60, type=0, res=-1)
wlan0: hfa384x_cmd: interrupted; err=-110
wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd20, len=8)
Could not get RID for component STA
wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wlan0: hfa384x_cmd_issue - timeout - reg=0x8021
wlan0: hfa384x_cmd: entry still in list? (entry=c7ffdc60, type=0, res=-1)
wlan0: hfa384x_cmd: interrupted; err=-110
wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd20, len=8)
wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wlan0: hfa384x_cmd_issue - timeout - reg=0x8021
wlan0: hfa384x_cmd: entry still in list? (entry=c7ffdc60, type=0, res=-1)
wlan0: hfa384x_cmd: interrupted; err=-110
wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fc01, len=6)
wlan0: could not get own MAC address
wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wlan0: hfa384x_cmd_issue - timeout - reg=0x8000
wlan0: hfa384x_cmd: entry still in list? (entry=c7ffdc60, type=0, res=-1)
wlan0: hfa384x_cmd: interrupted; err=-110
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=-110, rid=fce0,
len=2)
wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wlan0: hfa384x_cmd_issue - timeout - reg=0x8000
wlan0: hfa384x_cmd: entry still in list? (entry=c7ffdc60, type=0, res=-1)
wlan0: hfa384x_cmd: interrupted; err=-110
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=-110, rid=fc00,
len=2)
wlan0: Port type setting to 6 failed
wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wlan0: hfa384x_cmd_issue - timeout - reg=0x8000
wlan0: hfa384x_cmd: entry still in list? (entry=c7ffdc60, type=0, res=-1)
wlan0: hfa384x_cmd: interrupted; err=-110
wlan0: MAC port 0 enabling failed

Hostapd output is:

Configuration file: /etc/hostapd/hostapd.conf
Using interface wlan0ap with hwaddr 00:00:00:00:00:00 and ssid
'TxDOT_CST_ESG'
ioctl[SIOCSIWESSID]: Invalid argument
len=13
Could not set SSID for kernel driver

And here are the kernel messages from hostapd:

wlan0: enabling hostapd mode
wlan0: Registered netdevice wlan0ap for AP management
wlan0: Registered netdevice wlan0sta for STA use
wlan0ap: prism2_open
wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wlan0: hfa384x_cmd_issue - timeout - reg=0x8000
wlan0: hfa384x_cmd: entry still in list? (entry=c6dacbe0, type=0, res=-1)
wlan0: hfa384x_cmd: interrupted; err=-110
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=-110, rid=fc02,
len=34)
wlan0ap: prism2_close
wlan0: disabling hostapd mode
wlan0: Netdevice wlan0ap unregistered
wlan0: Netdevice wlan0sta unregistered

Thanks in advance.

Evan




From jbohac  Fri Aug  1 12:20:12 2003
From: jbohac (Jirka Bohac)
Date: Fri, 1 Aug 2003 21:20:12 +0200
Subject: Tx power conttrol issue
In-Reply-To: <003101c3585d$e1afe630$e6f0c53f@williamt>;
	from williamt@arescom.com on Fri, Aug 01, 2003 at 11:51:13AM -0700
References: <000d01c35857$11c1f9f0$e6f0c53f@williamt>
	<20030801180438.GA20443@gateway.junsun.net>
	<003101c3585d$e1afe630$e6f0c53f@williamt>
Message-ID: <20030801212012.A9587@twin.jikos.cz>

> The txpower code is embraced by a MACRO RAW_TXPOWER_SETTING.
> However this macro is not defined yet.
> That's what you mean "I believe txpower control is removed from v0.0.4."

Yes, up to 0.0.3, txpower can be controlled directly with "iwconfig xxx
txpower". However, there are a couple of problems. The setting does not
remain in effect after a "card reset", which is performed from time to
time by the driver. So after the first reset, the power is back on "auto".
Furthermore, the driver still thinks its on "fixed" and won't let you
set it to "fixed" again, until you first turn it to "auto" and then back
to "fixed" again.....

I tried to address these issues in my patch, located at
http://jikos.cz/~jbohac/hostap (tha patch also re-enables txpower
control for 0.0.4)


Maybe it's because of these problems that Jouni disabled the txpower
control support. He also says that the setting is not accurate - indeed,
the "decibells" you use in iwconfig have NOTHING TO DO with real output
power expressed in dBm. Jouni probably wants to use a special prism
power feedback register, CR58, for more accurate setting.

However, in our network where most people use the same kind of card, we
have our own calibrations, and we learned to live with the old system.
The absence of txpower control in 0.0.4 is a big pain for us :( 
Anything would be better than nothing at all.


????
	Jouni: 
	Is any help needed to get txpower control back in the driver?
????

regards,


Jirka
CZFree.Net, Czechia



From jiri.fojtasek  Fri Aug  1 13:49:09 2003
From: jiri.fojtasek (Jiri Fojtasek)
Date: Fri, 01 Aug 2003 22:49:09 +0200
Subject: Tx power conttrol issue
In-Reply-To: <20030801212012.A9587@twin.jikos.cz>
References: <000d01c35857$11c1f9f0$e6f0c53f@williamt>
	<20030801180438.GA20443@gateway.junsun.net>
	<003101c3585d$e1afe630$e6f0c53f@williamt> <20030801212012.A9587@twin.jikos.cz>
Message-ID: <3F2AD245.70901@hlohovec.net>

Jirka Bohac wrote:

>>The txpower code is embraced by a MACRO RAW_TXPOWER_SETTING.
>>However this macro is not defined yet.
>>That's what you mean "I believe txpower control is removed from v0.0.4."
>>    
>>
>
>Yes, up to 0.0.3, txpower can be controlled directly with "iwconfig xxx
>txpower". However, there are a couple of problems. The setting does not
>remain in effect after a "card reset", which is performed from time to
>time by the driver. So after the first reset, the power is back on "auto".
>Furthermore, the driver still thinks its on "fixed" and won't let you
>set it to "fixed" again, until you first turn it to "auto" and then back
>to "fixed" again.....
>
>I tried to address these issues in my patch, located at
>http://jikos.cz/~jbohac/hostap (tha patch also re-enables txpower
>control for 0.0.4)
>
>
>Maybe it's because of these problems that Jouni disabled the txpower
>control support. He also says that the setting is not accurate - indeed,
>the "decibells" you use in iwconfig have NOTHING TO DO with real output
>power expressed in dBm. Jouni probably wants to use a special prism
>power feedback register, CR58, for more accurate setting.
>
>However, in our network where most people use the same kind of card, we
>have our own calibrations, and we learned to live with the old system.
>The absence of txpower control in 0.0.4 is a big pain for us :( 
>Anything would be better than nothing at all.
>
>
>????
>	Jouni: 
>	Is any help needed to get txpower control back in the driver?
>????
>
>regards,
>
>
>Jirka
>CZFree.Net, Czechia
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>  
>
http://www.intersil.com/data/an/AN1037.pdf

Here is good explain hows ALC works. Maybe a testing of the CR58, an 
making feedback to the CR31 every TX frame will solve that txpower 
behaviour.

Jiri



From lcaeiro  Fri Aug  1 14:03:57 2003
From: lcaeiro (caeiro)
Date: Fri, 1 Aug 2003 22:03:57 +0100
Subject: TX events
References: <20030801180312.GA28131@bougret.hpl.hp.com>
Message-ID: <001101c35870$6cb55370$6501a8c0@home>

Thanks a lot, but I need to have this knowledge on driver level (I'm using a
version of  2-03-2003) because I want to control the tx buffers on the card.
Is that available on this level?

LC



----- Original Message -----
From: "Jean Tourrilhes" <jt at bougret.hpl.hp.com>
To: <hostap at shmoo.com>
Sent: Friday, August 01, 2003 7:03 PM
Subject: Re: TX events


&gt; caeiro wrote :<BR>
&gt; &gt; <BR>
&gt; &gt; How can I know when a data packet is sent from the card tx
buffer?<BR>
&gt; <BR>
&gt; 	/proc/net/dev will increase<BR>
&gt; <BR>
&gt; &gt; Can I receive TX ok and TX exc events in the driver?<BR>
&gt; <BR>
&gt; 	For most practical purpose, you only need &quot;TX exc&quot;, and it
is<BR>
&gt; available as an iwevent (WE-14 and later).<BR>
&gt; <BR>
&gt; &gt; I need to activate something?<BR>
&gt; <BR>
&gt; 	You need WE-14 (2.4.20 or later), Wireless Tools v24 or later,<BR>
&gt; and a driver that support Wireless Events (HostAP v0.0.1 or<BR>
&gt; later). And you need to read the man page of iwevent.<BR>
&gt; <BR>
&gt; 	Jean<BR>
&gt; _______________________________________________<BR>
&gt; HostAP mailing list<BR>
&gt; HostAP at shmoo.com<BR>
&gt; http://lists.shmoo.com/mailman/listinfo/hostap




From williamt  Fri Aug  1 14:22:34 2003
From: williamt (William Tai)
Date: Fri, 1 Aug 2003 14:22:34 -0700
Subject: Tx power conttrol issue
References: 	<000d01c35857$11c1f9f0$e6f0c53f@williamt><20030801180438.GA20443@gateway.junsun.net><003101c3585d$e1afe630$e6f0c53f@williamt>
	<20030801212012.A9587@twin.jikos.cz> <3F2AD245.70901@hlohovec.net>
Message-ID: <005d01c35873$06992910$e6f0c53f@williamt>

----- Original Message ----- 
From: "Jiri Fojtasek" <jiri.fojtasek at hlohovec.net>
To: <hostap at shmoo.com>
Sent: Friday, August 01, 2003 1:49 PM
Subject: Re: Tx power conttrol issue


> Jirka Bohac wrote:
>
> >>The txpower code is embraced by a MACRO RAW_TXPOWER_SETTING.
> >>However this macro is not defined yet.
> >>That's what you mean "I believe txpower control is removed from v0.0.4."
> >>
> >>
> >
> >Yes, up to 0.0.3, txpower can be controlled directly with "iwconfig xxx
> >txpower". However, there are a couple of problems. The setting does not
> >remain in effect after a "card reset", which is performed from time to
> >time by the driver. So after the first reset, the power is back on
"auto".
> >Furthermore, the driver still thinks its on "fixed" and won't let you
> >set it to "fixed" again, until you first turn it to "auto" and then back
> >to "fixed" again.....
> >
> >I tried to address these issues in my patch, located at
> >http://jikos.cz/~jbohac/hostap (tha patch also re-enables txpower
> >control for 0.0.4)
> >
> >
> >Maybe it's because of these problems that Jouni disabled the txpower
> >control support. He also says that the setting is not accurate - indeed,
> >the "decibells" you use in iwconfig have NOTHING TO DO with real output
> >power expressed in dBm. Jouni probably wants to use a special prism
> >power feedback register, CR58, for more accurate setting.
> >
> >However, in our network where most people use the same kind of card, we
> >have our own calibrations, and we learned to live with the old system.
> >The absence of txpower control in 0.0.4 is a big pain for us :(
> >Anything would be better than nothing at all.
> >
> >
> >????
> > Jouni:
> > Is any help needed to get txpower control back in the driver?
> >????
> >
> >regards,
> >
> >
> >Jirka
> >CZFree.Net, Czechia
> >_______________________________________________
> >HostAP mailing list
> >HostAP at shmoo.com
> >http://lists.shmoo.com/mailman/listinfo/hostap
> >
> >
> >
> http://www.intersil.com/data/an/AN1037.pdf
>
> Here is good explain hows ALC works. Maybe a testing of the CR58, an
> making feedback to the CR31 every TX frame will solve that txpower
> behaviour.
>
> Jiri
>
Hi Jiri:

    ALC is off when we try to config txpower. Am I right?
So the ALC you mentioned is another way to control txpower?
I noticed that there are some configuration stored in PDA.
So can I modified the content -PDR 0x0300 and PDR 0x0301 to force txpower
change?

William



Thanks


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



From jiri.fojtasek  Fri Aug  1 14:35:59 2003
From: jiri.fojtasek (Jiri Fojtasek)
Date: Fri, 01 Aug 2003 23:35:59 +0200
Subject: Tx power conttrol issue
In-Reply-To: <005d01c35873$06992910$e6f0c53f@williamt>
References: 	<000d01c35857$11c1f9f0$e6f0c53f@williamt><20030801180438.GA20443@gateway.junsun.net><003101c3585d$e1afe630$e6f0c53f@williamt>
	<20030801212012.A9587@twin.jikos.cz> <3F2AD245.70901@hlohovec.net>
	<005d01c35873$06992910$e6f0c53f@williamt>
Message-ID: <3F2ADD3F.7020508@hlohovec.net>

William Tai wrote:

>----- Original Message ----- 
>From: "Jiri Fojtasek" <jiri.fojtasek at hlohovec.net>
>To: <hostap at shmoo.com>
>Sent: Friday, August 01, 2003 1:49 PM
>Subject: Re: Tx power conttrol issue
>
>
>  
>
>>Jirka Bohac wrote:
>>
>>    
>>
>>>>The txpower code is embraced by a MACRO RAW_TXPOWER_SETTING.
>>>>However this macro is not defined yet.
>>>>That's what you mean "I believe txpower control is removed from v0.0.4."
>>>>
>>>>
>>>>        
>>>>
>>>Yes, up to 0.0.3, txpower can be controlled directly with "iwconfig xxx
>>>txpower". However, there are a couple of problems. The setting does not
>>>remain in effect after a "card reset", which is performed from time to
>>>time by the driver. So after the first reset, the power is back on
>>>      
>>>
>"auto".
>  
>
>>>Furthermore, the driver still thinks its on "fixed" and won't let you
>>>set it to "fixed" again, until you first turn it to "auto" and then back
>>>to "fixed" again.....
>>>
>>>I tried to address these issues in my patch, located at
>>>http://jikos.cz/~jbohac/hostap (tha patch also re-enables txpower
>>>control for 0.0.4)
>>>
>>>
>>>Maybe it's because of these problems that Jouni disabled the txpower
>>>control support. He also says that the setting is not accurate - indeed,
>>>the "decibells" you use in iwconfig have NOTHING TO DO with real output
>>>power expressed in dBm. Jouni probably wants to use a special prism
>>>power feedback register, CR58, for more accurate setting.
>>>
>>>However, in our network where most people use the same kind of card, we
>>>have our own calibrations, and we learned to live with the old system.
>>>The absence of txpower control in 0.0.4 is a big pain for us :(
>>>Anything would be better than nothing at all.
>>>
>>>
>>>????
>>>Jouni:
>>>Is any help needed to get txpower control back in the driver?
>>>????
>>>
>>>regards,
>>>
>>>
>>>Jirka
>>>CZFree.Net, Czechia
>>>_______________________________________________
>>>HostAP mailing list
>>>HostAP at shmoo.com
>>>http://lists.shmoo.com/mailman/listinfo/hostap
>>>
>>>
>>>
>>>      
>>>
>>http://www.intersil.com/data/an/AN1037.pdf
>>
>>Here is good explain hows ALC works. Maybe a testing of the CR58, an
>>making feedback to the CR31 every TX frame will solve that txpower
>>behaviour.
>>
>>Jiri
>>
>>    
>>
>Hi Jiri:
>
>    ALC is off when we try to config txpower. Am I right?
>So the ALC you mentioned is another way to control txpower?
>I noticed that there are some configuration stored in PDA.
>So can I modified the content -PDR 0x0300 and PDR 0x0301 to force txpower
>change?
>
>William
>
>
>
>Thanks
>
>
>  
>
>>_______________________________________________
>>HostAP mailing list
>>HostAP at shmoo.com
>>http://lists.shmoo.com/mailman/listinfo/hostap
>>    
>>
>
>  
>
PDR have manufacturer forced value for ALC calibration. It should be way 
, but i think more usefull should be made a software ALC calibration 
loop ...

Jiri



From vaio  Fri Aug  1 10:39:15 2003
From: vaio (Michael Vallaly)
Date: Fri, 1 Aug 2003 17:39:15 +0000
Subject: SMP Frequent Lockups
Message-ID: <20030801173915.68ab335e.vaio@nolatency.com>


Hello,

I am having issues with my WPC11 Linksys PCI card and a 2.4.21 SMP kernel. I recently upgraded the machine with another processor and recompiled the kernel to support SMP. Previously ive had only 1 or 2 lockups (non SMP kernel) using Hostap 0.0.3 under heavy traffic (FTP for instance) over a 3 month span. Now with the SMP kernel I have lockups with even light usage of the wireless AP (ssh or webbrowsing). These are hard lockups that require cycling the power via unplugging. I can verify that the lockups only happen with some sort of traffic on the wireless card, as I can keep the hostap module loaded with the interface down, and not crash. Anyone have a solution? 

Ive tried every patch I can get my hands on, as well as the Hostap CVS code.

I will have quite a bit of free time from now until Aug 25th or so, and I am willing to test any patches / ideas thrown my way ;)  


-Mike 

/var/log/dmesg

<snip>
hostap_crypt: registered algorithm 'NULL'
hostap_pci: 0.0.4 - 2003-07-27 (Jouni Malinen <jkmaline at cc.hut.fi>)
hostap_pci: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_init: initialized in 210 ms
wlan0: NIC: id=0x8013 v1.0.0
wlan0: PRI: id=0x15 v1.1.0
wlan0: STA: id=0x1f v1.4.9
wlan0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP                                                               mode WDS
wlan0: Intersil Prism2.5 PCI: mem=0xfd8ff000, irq=9

</snip>



From jkmaline  Fri Aug  1 19:11:47 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 1 Aug 2003 19:11:47 -0700
Subject: TX events
In-Reply-To: <001d01c35813$ac986fc0$6501a8c0@home>
References: <001d01c35813$ac986fc0$6501a8c0@home>
Message-ID: <20030802021147.GA3849@jm.kir.nu>

On Fri, Aug 01, 2003 at 10:59:48AM +0100, caeiro wrote:

> How can I know when a data packet is sent from the card tx buffer? Can I receive TX ok and TX exc events in the driver? I need to activate something?

Functions prism2_tx_ev() and prism2_txexc() (in hostap_hw.c) will be
called when these events occur.

-- 
Jouni Malinen                                            PGP id EFC895FA



From hempel.ralf  Fri Aug  1 15:50:09 2003
From: hempel.ralf (Ralf Hempel)
Date: 02 Aug 2003 00:50:09 +0200
Subject: busy  bit fixed
Message-ID: <1059778209.1712.4.camel@Medusa.HomeNet>

I've fixed my busy bit problem. ThanksPpavel

http://www.edv-info-service.de/busybit.html


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030802/6c1fa4d1/attachment.htm 


From nrimawi  Fri Aug  1 15:10:45 2003
From: nrimawi (Nimer Rimawi)
Date: Fri, 1 Aug 2003 18:10:45 -0400
Subject: management.c File & HostAP Question..
Message-ID: <000501c35879$c17b3470$ee42f69b@VALUEDB8142DE8>

Hello all,

I am looking at the hostap code, and I was looking at the management.c
file.. I am wondering, does it get compiled at all? If so, when do its
function run? I am particularily interested in seeing the work of
"show_capability_info" function.

Another question is regarding the driver itself,,, I can see in the file
hostap_wlan0.h the definition of the five original 802.11 bits of the
capability field from lines 757 to 761,, however, where are the 802.11b
extra 3 bits defined? (namely the Short, PBCC, and Agility ?)

Any help would be apprecaited in any of the matters.. Thanks a bunch

-Nimer



From jkmaline  Fri Aug  1 19:24:58 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 1 Aug 2003 19:24:58 -0700
Subject: Tx power conttrol issue
In-Reply-To: <20030801212012.A9587@twin.jikos.cz>
References: <000d01c35857$11c1f9f0$e6f0c53f@williamt>
	<20030801180438.GA20443@gateway.junsun.net>
	<003101c3585d$e1afe630$e6f0c53f@williamt> <20030801212012.A9587@twin.jikos.cz>
Message-ID: <20030802022458.GB3849@jm.kir.nu>

On Fri, Aug 01, 2003 at 09:20:12PM +0200, Jirka Bohac wrote:

> Yes, up to 0.0.3, txpower can be controlled directly with "iwconfig xxx
> txpower". However, there are a couple of problems. The setting does not
> remain in effect after a "card reset", which is performed from time to
> time by the driver. So after the first reset, the power is back on "auto".

> Maybe it's because of these problems that Jouni disabled the txpower
> control support. He also says that the setting is not accurate - indeed,
> the "decibells" you use in iwconfig have NOTHING TO DO with real output
> power expressed in dBm. Jouni probably wants to use a special prism
> power feedback register, CR58, for more accurate setting.

No, removal of txpower command has nothing to do with either of these
issues. First one can be fixed easily and accuracy is not that much of a
problem. Just read the v0.0.4 entry in ChangeLog for the real reason.

> However, in our network where most people use the same kind of card, we
> have our own calibrations, and we learned to live with the old system.
> The absence of txpower control in 0.0.4 is a big pain for us :( 
> Anything would be better than nothing at all.

It's not like "nothing at all"; Prism2/2.5/3 cards have TX power control
in the firmware. Host AP driver has always defaulted to let the firmware
take care of TPC. Newer firmware versions include a command for limiting
maximum power, but Host AP driver does not yet support it.

> 	Is any help needed to get txpower control back in the driver?

I will probably take a look at implementing proper feedback loop from
the TX power measurements. However, I do not know when I will have time
for doing this. Clean and tested patch to implement this would be
accepted gladly ;-).

-- 
Jouni Malinen                                            PGP id EFC895FA



From williamt  Fri Aug  1 19:35:27 2003
From: williamt (William Tai)
Date: Fri, 1 Aug 2003 19:35:27 -0700
Subject: writing PDA
Message-ID: <00b101c3589e$bb958040$e6f0c53f@williamt>

Hi All:

    If I modify PDA I read from card and reload to card, do i also
re-calculate the CRC of the PDA end record?

Thanx
William



From jkmaline  Fri Aug  1 19:28:58 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 1 Aug 2003 19:28:58 -0700
Subject: Flashing with prism2_srec
In-Reply-To: <Pine.LNX.4.56.0308011127000.16027@marabou.research.att.com>
References: <3F2A241A.9000202@pcuf.fi>
	<Pine.LNX.4.56.0308011127000.16027@marabou.research.att.com>
Message-ID: <20030802022858.GC3849@jm.kir.nu>

On Fri, Aug 01, 2003 at 11:29:08AM -0400, Pavel Roskin wrote:

> prism2_srec should be safe now.  Try without "-i" first.  If needed, use
> "-i", but it's more risky, so it's up to you to decide.

prism2_srec does not allow "-i" options to be used when downloading to
flash. It can only be used in RAM downloads, and for a good reason. I
know cases where firmware works without any problems even though "-i"
was required, but I also know cases in which the card dies horribly when
"-i" was used to ignore incompatible commands. With RAM downloads you
can always reset the card to fix this, but I would suggest being quite
careful when writing to flash.

-- 
Jouni Malinen                                            PGP id EFC895FA



From matrix  Fri Aug  1 19:56:30 2003
From: matrix (Francois Gurin)
Date: Fri, 1 Aug 2003 22:56:30 -0400
Subject: problems with 0.0.4 and gcc-3.2/3.3
Message-ID: <20030802025630.GM8799@shot.org>



I've been working on 0.0.4 for a few days now and have encountered 
problems compiling hostap with gcc 3.2 and 3.3.  When i use 2.95 
everything works as expected.
I had thought 3.2 was working fine until fairly recently.

The system is debian sid/unstable on i386 with kernel 2.4.21-pre3.  

3.2 compiles cleanly and loads without errors and intitalizes the card, 
then immediately locks the system.  

3.3 shows the attached errors when compiling.  
when the module loads, the kernel panics and the system becomes unstable.

any ideas?

--francois

-------------- next part --------------
/usr/bin/make KERNELRELEASE=2.4.21-pre3-fg4 KERNEL_PATH=/usr/src/kernel-source-2.4.21-pre3 \
	DESTDIR=/usr/src/modules/hostap-source/debian/hostap-modules-2.4.21-pre3-fg4 pccard
make[1]: Entering directory `/usr/src/modules/hostap-source'
gcc-3.3 -I/usr/src/kernel-source-2.4.21-pre3/include -O2 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS -include /usr/src/kernel-source-2.4.21-pre3/include/linux/modversions.h -fomit-frame-pointer -E -D__GENKSYMS__ driver/modules/hostap.c | \
	/sbin/genksyms -k 2.4.21 > driver/modules/hostap.ver
In file included from driver/modules/hostap.c:21:
/usr/src/kernel-source-2.4.21-pre3/include/linux/module.h:15:1: warning: "_set_ver" redefined
In file included from /usr/src/kernel-source-2.4.21-pre3/include/linux/modversions.h:3,
                 from <command line>:8:
/usr/src/kernel-source-2.4.21-pre3/include/linux/modsetver.h:9:1: warning: this is the location of the previous definition
gcc-3.3 -I/usr/src/kernel-source-2.4.21-pre3/include -O2 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS -include /usr/src/kernel-source-2.4.21-pre3/include/linux/modversions.h -fomit-frame-pointer -E -D__GENKSYMS__ driver/modules/hostap_crypt.c | \
	/sbin/genksyms -k 2.4.21 > driver/modules/hostap_crypt.ver
In file included from driver/modules/hostap_crypt.c:18:
/usr/src/kernel-source-2.4.21-pre3/include/linux/module.h:15:1: warning: "_set_ver" redefined
In file included from /usr/src/kernel-source-2.4.21-pre3/include/linux/modversions.h:3,
                 from <command line>:8:
/usr/src/kernel-source-2.4.21-pre3/include/linux/modsetver.h:9:1: warning: this is the location of the previous definition
gcc-3.3 -I/usr/src/kernel-source-2.4.21-pre3/include -include driver/modules/hostap_crypt.ver -include driver/modules/hostap.ver -O2 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS -include /usr/src/kernel-source-2.4.21-pre3/include/linux/modversions.h -fomit-frame-pointer -o driver/modules/hostap_cs.o driver/modules/hostap_cs.c
In file included from /usr/src/kernel-source-2.4.21-pre3/include/asm/semaphore.h:39,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/fs.h:200,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/capability.h:17,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/binfmts.h:5,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/sched.h:9,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/skbuff.h:19,
                 from driver/modules/hostap_cs.c:13:
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h: In function `__set_64bit_var':
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h:190: warning: dereferencing type-punned pointer will break strict-aliasing rules
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h:190: warning: dereferencing type-punned pointer will break strict-aliasing rules
gcc-3.3 -I/usr/src/kernel-source-2.4.21-pre3/include -include driver/modules/hostap_crypt.ver -include driver/modules/hostap.ver -O2 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS -include /usr/src/kernel-source-2.4.21-pre3/include/linux/modversions.h -fomit-frame-pointer -o driver/modules/hostap.o driver/modules/hostap.c
In file included from /usr/src/kernel-source-2.4.21-pre3/include/asm/semaphore.h:39,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/fs.h:200,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/capability.h:17,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/binfmts.h:5,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/sched.h:9,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/mm.h:4,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/slab.h:14,
                 from driver/modules/hostap.c:23:
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h: In function `__set_64bit_var':
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h:190: warning: dereferencing type-punned pointer will break strict-aliasing rules
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h:190: warning: dereferencing type-punned pointer will break strict-aliasing rules
gcc-3.3 -I/usr/src/kernel-source-2.4.21-pre3/include -include driver/modules/hostap_crypt.ver -include driver/modules/hostap.ver -O2 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS -include /usr/src/kernel-source-2.4.21-pre3/include/linux/modversions.h -fomit-frame-pointer -o driver/modules/hostap_crypt.o driver/modules/hostap_crypt.c
In file included from /usr/src/kernel-source-2.4.21-pre3/include/asm/semaphore.h:39,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/fs.h:200,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/capability.h:17,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/binfmts.h:5,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/sched.h:9,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/mm.h:4,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/slab.h:14,
                 from driver/modules/hostap_crypt.c:20:
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h: In function `__set_64bit_var':
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h:190: warning: dereferencing type-punned pointer will break strict-aliasing rules
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h:190: warning: dereferencing type-punned pointer will break strict-aliasing rules
gcc-3.3 -I/usr/src/kernel-source-2.4.21-pre3/include -include driver/modules/hostap_crypt.ver -include driver/modules/hostap.ver -O2 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS -include /usr/src/kernel-source-2.4.21-pre3/include/linux/modversions.h -fomit-frame-pointer -o driver/modules/hostap_crypt_wep.o driver/modules/hostap_crypt_wep.c
In file included from /usr/src/kernel-source-2.4.21-pre3/include/asm/semaphore.h:39,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/fs.h:200,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/capability.h:17,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/binfmts.h:5,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/sched.h:9,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/mm.h:4,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/slab.h:14,
                 from driver/modules/hostap_crypt_wep.c:16:
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h: In function `__set_64bit_var':
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h:190: warning: dereferencing type-punned pointer will break strict-aliasing rules
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h:190: warning: dereferencing type-punned pointer will break strict-aliasing rules

Run 'make install_pccard' as root to install hostap_cs.o
Run 'make install_plx' as root to install hostap_plx.o
Run 'make install_pci' as root to install hostap_pci.o

make[1]: Leaving directory `/usr/src/modules/hostap-source'
/usr/bin/make KERNELRELEASE=2.4.21-pre3-fg4 KERNEL_PATH=/usr/src/kernel-source-2.4.21-pre3 \
	DESTDIR=/usr/src/modules/hostap-source/debian/hostap-modules-2.4.21-pre3-fg4 plx
make[1]: Entering directory `/usr/src/modules/hostap-source'
gcc-3.3 -I/usr/src/kernel-source-2.4.21-pre3/include -include driver/modules/hostap_crypt.ver -include driver/modules/hostap.ver -O2 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS -include /usr/src/kernel-source-2.4.21-pre3/include/linux/modversions.h -fomit-frame-pointer -o driver/modules/hostap_plx.o driver/modules/hostap_plx.c
In file included from /usr/src/kernel-source-2.4.21-pre3/include/asm/semaphore.h:39,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/fs.h:200,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/capability.h:17,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/binfmts.h:5,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/sched.h:9,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/skbuff.h:19,
                 from driver/modules/hostap_plx.c:15:
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h: In function `__set_64bit_var':
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h:190: warning: dereferencing type-punned pointer will break strict-aliasing rules
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h:190: warning: dereferencing type-punned pointer will break strict-aliasing rules

Run 'make install_pccard' as root to install hostap_cs.o
Run 'make install_plx' as root to install hostap_plx.o
Run 'make install_pci' as root to install hostap_pci.o

make[1]: Leaving directory `/usr/src/modules/hostap-source'
/usr/bin/make KERNELRELEASE=2.4.21-pre3-fg4 KERNEL_PATH=/usr/src/kernel-source-2.4.21-pre3 \
	DESTDIR=/usr/src/modules/hostap-source/debian/hostap-modules-2.4.21-pre3-fg4 pci
make[1]: Entering directory `/usr/src/modules/hostap-source'
gcc-3.3 -I/usr/src/kernel-source-2.4.21-pre3/include -include driver/modules/hostap_crypt.ver -include driver/modules/hostap.ver -O2 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS -include /usr/src/kernel-source-2.4.21-pre3/include/linux/modversions.h -fomit-frame-pointer -o driver/modules/hostap_pci.o driver/modules/hostap_pci.c
In file included from /usr/src/kernel-source-2.4.21-pre3/include/asm/semaphore.h:39,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/fs.h:200,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/capability.h:17,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/binfmts.h:5,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/sched.h:9,
                 from /usr/src/kernel-source-2.4.21-pre3/include/linux/skbuff.h:19,
                 from driver/modules/hostap_pci.c:12:
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h: In function `__set_64bit_var':
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h:190: warning: dereferencing type-punned pointer will break strict-aliasing rules
/usr/src/kernel-source-2.4.21-pre3/include/asm/system.h:190: warning: dereferencing type-punned pointer will break strict-aliasing rules

Run 'make install_pccard' as root to install hostap_cs.o
Run 'make install_plx' as root to install hostap_plx.o
Run 'make install_pci' as root to install hostap_pci.o

-------------- next part --------------
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.0.4 - 2003-07-27 (Jouni Malinen <jkmaline at cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
prism2_config()
hostap_cs: setting Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: index 0x01: Vcc 3.3, irq 3, io 0x0100-0x013f
divert: allocating divert_blk for wlan0
hostap_cs: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_init: initialized in 100 ms
Unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
c0114462
*pde = 00000000
Oops: 0002
CPU:    0
EIP:    0010:[<c0114462>]    Not tainted
EFLAGS: 00010082
eax: cc1dd81c   ebx: 00000000   ecx: 00000202   edx: cd26f71c
esi: cd26f714   edi: cd26e000   ebp: 00000000   esp: cd26f6f8
ds: 0018   es: 0018   ss: 0018
Process cardmgr (pid: 1075, stackpage=cd26f000)
Stack: cc1dd810 cd26f714 c0105ad5 c5208200 cc1dd810 cc1dd800 c5208200 00000001 
       cd26e000 cc1dd81c 00000000 c0105b9b cc1dd810 0000fd0b cf908462 0000a7bc 
       cd26f764 ce1b2260 c5208200 cf90ac4b c5208200 cd26fb84 cf902e52 c5208200 
Call Trace:    [<c0105ad5>] [<c0105b9b>] [<cf908462>] [<cf90ac4b>] [<cf902e52>]
  [<c0113e46>] [<cf902d9d>] [<c0115e50>] [<cf9035dc>] [<cf90ac4b>] [<cf9037e7>]
  [<c0115e50>] [<cf907c86>] [<cf8eaafb>] [<cf8eabe2>] [<cf8ebe9d>] [<cf8eaafb>]
  [<cf8eabe2>] [<cf8ec010>] [<c011d6ab>] [<c011330e>] [<c011330e>] [<c011c89d>]
  [<c011964b>] [<c011959a>] [<c01193cc>] [<cf8eaafb>] [<cf8eabe2>] [<cf8ebe9d>]
  [<cf8eaafb>] [<cf8eabe2>] [<cf8ec010>] [<c011d6ab>] [<c011330e>] [<c0115ce3>]
  [<c0115e50>] [<cf907f99>] [<cf90b1e0>] [<cf907ecc>] [<cf8ef04c>] [<cf906e80>]
  [<c0115f01>] [<cf8f00d8>] [<cf907609>] [<cf90b1e0>] [<cf907ecc>] [<cf8ee528>]
  [<cf8fb615>] [<cf8fb655>] [<cf8fc005>] [<c01ebb89>] [<c01eb262>] [<c01e9d5c>]
  [<c022e83b>] [<c01136c8>] [<c0125973>] [<c0125ce9>] [<c013e68d>] [<c0106b8f>]

Code: 89 13 51 9d 5b 5e c3 56 53 89 d6 9c 5a fa 8d 5e 08 8b 4b 04 
 <7>wlan0: hfa384x_cmd: entry still in list? (entry=c81d7760, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=c81d7760, type=0, cmd=0x0021, param0=0xfdc6, EVSTAT=8000 INTEN=0010)
wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fdc6, len=12)
Unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
c0113715
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c0113715>]    Not tainted
EFLAGS: 00210097
eax: cc1dd81c   ebx: cc1dd818   ecx: 00000000   edx: 00000003
esi: cc1dd810   edi: 00000001   ebp: ca3d7e40   esp: ca3d7e28
ds: 0018   es: 0018   ss: 0018
Process wmwave (pid: 1353, stackpage=ca3d7000)
Stack: ffffff92 cc1dd810 cc1dd800 cc1dd81c 00200286 00000003 c5208200 c01059f6 
       c0105bb4 cc1dd810 00000001 0000004e cf90846c 0000fdc6 33323130 37363534 
       ca3d7f5c c5208200 ca3d7ecc cf93fed8 cf93fe94 c5208200 0000fdc6 ca3d7e9c 
Call Trace:    [<c01059f6>] [<c0105bb4>] [<cf90846c>] [<cf93fed8>] [<cf93fe94>]
  [<c022e83b>] [<cf93fef0>] [<c01136c8>] [<c01f5c70>] [<cf93fed8>] [<c01f05ac>]
  [<c021bfc9>] [<c01e941a>] [<c013e68d>] [<c0106b8f>]

Code: 8b 01 85 45 fc 74 4c 31 c0 9c 5e fa c7 01 00 00 00 00 83 79 
 <7>hostap_cs: CS_EVENT_CARD_REMOVAL
wlan0: Interrupt, but dev not OK
prism2_release
wlan0: card already removed or not configured during shutdown
release - done


From williamt  Fri Aug  1 20:28:31 2003
From: williamt (William Tai)
Date: Fri, 1 Aug 2003 20:28:31 -0700
Subject: Tx power conttrol issue
References: 	<000d01c35857$11c1f9f0$e6f0c53f@williamt><20030801180438.GA20443@gateway.junsun.net><003101c3585d$e1afe630$e6f0c53f@williamt>
	<20030801212012.A9587@twin.jikos.cz> <20030802022458.GB3849@jm.kir.nu>
Message-ID: <00c901c358a6$25882280$e6f0c53f@williamt>


----- Original Message ----- 
From: "Jouni Malinen" <jkmaline at cc.hut.fi>
To: <hostap at shmoo.com>
Sent: Friday, August 01, 2003 7:24 PM
Subject: Re: Tx power conttrol issue


> On Fri, Aug 01, 2003 at 09:20:12PM +0200, Jirka Bohac wrote:
>
> > Yes, up to 0.0.3, txpower can be controlled directly with "iwconfig xxx
> > txpower". However, there are a couple of problems. The setting does not
> > remain in effect after a "card reset", which is performed from time to
> > time by the driver. So after the first reset, the power is back on
"auto".
>
> > Maybe it's because of these problems that Jouni disabled the txpower
> > control support. He also says that the setting is not accurate - indeed,
> > the "decibells" you use in iwconfig have NOTHING TO DO with real output
> > power expressed in dBm. Jouni probably wants to use a special prism
> > power feedback register, CR58, for more accurate setting.
>
> No, removal of txpower command has nothing to do with either of these
> issues. First one can be fixed easily and accuracy is not that much of a
> problem. Just read the v0.0.4 entry in ChangeLog for the real reason.
>
> > However, in our network where most people use the same kind of card, we
> > have our own calibrations, and we learned to live with the old system.
> > The absence of txpower control in 0.0.4 is a big pain for us :(
> > Anything would be better than nothing at all.
>
> It's not like "nothing at all"; Prism2/2.5/3 cards have TX power control
> in the firmware. Host AP driver has always defaulted to let the firmware
> take care of TPC. Newer firmware versions include a command for limiting
> maximum power, but Host AP driver does not yet support it.
>
> > Is any help needed to get txpower control back in the driver?
>
> I will probably take a look at implementing proper feedback loop from
> the TX power measurements. However, I do not know when I will have time
> for doing this. Clean and tested patch to implement this would be
> accepted gladly ;-).
>
> -- 
> Jouni Malinen                                            PGP id EFC895FA

First of all, thanks for the valuable information so that I can control my
txpower now.
Now I can control txpower by set ALC to 0 every time before I call
 if (hfa384x_cmd(dev, HFA384X_CMDCODE_WRITEMIF,
        HFA386X_CR_MANUAL_TX_POWER, &val, NULL))
  ret = -EOPNOTSUPP;.
But from log change of Jouni, it seems that this txpower control will
introduce some interference.

Is it because we turn ALC off so that txpower compensation is disabled?
Am I right?

There is another way to control txpower by config PDR 0x0300 and 0x0301.
ALC is enabled in this way.
Is this means that we have a better txpower control?
Now I am working on this.
Maybe this is a better way to control txpower.
To implement this, it is supposed to have 3 steps.

1. load PDA from card ** use prism2_read_pda( )
2. modify PDR 0x0300 and PDR 0x0301
3. relaod modified PDA to card ** use prism2_download_volatile( )

Now I have a question in step 3.
The the last sector of PDA is PDR 0x0000.
The last word of this PDR is CRC16.
So after I modify PDR 0x0300 and PDR 0x0301, do I have to re-calculate CRC16
and then re-load it to card?
And how do I know the new PDA working properly?

 local->hw_downloading = 0;
 if (prism2_hw_config(dev, 2)) {
  printk(KERN_WARNING "%s: Card configuration after RAM "
         "download failed\n", dev->name);  <---Does this indicate download
PDA failure?
  ret = -1;
  goto out2;
 }
Now I am working on this.
Any advice is welcome.

Thanx
William



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



From lcaeiro  Sat Aug  2 04:05:13 2003
From: lcaeiro (caeiro)
Date: Sat, 2 Aug 2003 12:05:13 +0100
Subject: TX events
Message-ID: <00f401c358e5$f2e4ecb0$6501a8c0@home>

When I send some data packets with mgen I can't see that functions to be called (I put a printk in the begining of prism2_tx_ev and prism2_txexc). Shouldn't that functions to be called in this case?
 
LC 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030802/5ac4ad11/attachment.htm 


From john  Sat Aug  2 05:55:21 2003
From: john (John Leach)
Date: 02 Aug 2003 13:55:21 +0100
Subject: SMP Frequent Lockups
In-Reply-To: <20030801173915.68ab335e.vaio@nolatency.com>
References: <20030801173915.68ab335e.vaio@nolatency.com>
Message-ID: <1059828921.4227.24.camel@peppard.dark.lan>

I've had the same with my Netgear PCI card with kernel 2.4.20 (I tried
the provided kernel RPMs (rebuilt for SMP of course) and tried with the
latest (030722) hostap from cvs patched in to the same kernel.

The machine works fine (no lockups in weeks of use) with a UP kernel,
but in SMP it will hard lock requiring a powercycle within a few
minutes.

 localhost kernel: hostap_pci: Registered netdevice wlan0
 localhost kernel: prism2_hw_init() 
 localhost kernel: prism2_hw_init: initialized in 17954 iterations
 localhost kernel: wlan0: NIC: id=0x8013 v1.0.0
 localhost kernel: wlan0: PRI: id=0x15 v1.0.7
 localhost kernel: wlan0: STA: id=0x1f v1.3.6
 localhost kernel: wlan0: defaulting to host-based encryption as a workaround for firmware bug in Host AP mode WEP
 localhost kernel: wlan0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
 localhost kernel: wlan0: Intersil Prism2.5 PCI: mem=0xe4000000, irq=16
 localhost kernel: hostap_crypt: registered algorithm 'WEP'

I've now moved to a uniprocessor machine, but if you need me to I could
swap cards back and do some tests (if nobody else can).

Thanks for the great work so far.

John.

On Fri, 2003-08-01 at 18:39, Michael Vallaly wrote:
> Hello,
> 
> I am having issues with my WPC11 Linksys PCI card and a 2.4.21 SMP kernel. I recently upgraded the machine with another processor and recompiled the kernel to support SMP. Previously ive had only 1 or 2 lockups (non SMP kernel) using Hostap 0.0.3 under heavy traffic (FTP for instance) over a 3 month span. Now with the SMP kernel I have lockups with even light usage of the wireless AP (ssh or webbrowsing). These are hard lockups that require cycling the power via unplugging. I can verify that the lockups only happen with some sort of traffic on the wireless card, as I can keep the hostap module loaded with the interface down, and not crash. Anyone have a solution? 
> 
> Ive tried every patch I can get my hands on, as well as the Hostap CVS code.
> 
> I will have quite a bit of free time from now until Aug 25th or so, and I am willing to test any patches / ideas thrown my way ;)  
> 
> 
> -Mike 

-- 
GPG KEY: B89C D450 5B2C 74D8 58FB A360 9B06 B5C2 26F0 3047
   HTTP: http://www.johnleach.co.uk
-------------- 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/20030802/f5a5329b/attachment.pgp 


From jbohac  Sat Aug  2 05:57:17 2003
From: jbohac (Jirka Bohac)
Date: Sat, 2 Aug 2003 14:57:17 +0200
Subject: Tx power conttrol issue
In-Reply-To: <20030802022458.GB3849@jm.kir.nu>;
	from jkmaline@cc.hut.fi on Fri, Aug 01, 2003 at 07:24:58PM -0700
References: <000d01c35857$11c1f9f0$e6f0c53f@williamt>
	<20030801180438.GA20443@gateway.junsun.net>
	<003101c3585d$e1afe630$e6f0c53f@williamt> <20030801212012.A9587@twin.jikos.cz>
	<20030802022458.GB3849@jm.kir.nu>
Message-ID: <20030802145717.A18332@twin.jikos.cz>

hello,

> No, removal of txpower command has nothing to do with either of these
> issues. First one can be fixed easily and accuracy is not that much of a
> problem. Just read the v0.0.4 entry in ChangeLog for the real reason.

well, I did, but I can't understand what you mean: 
	
"the experimental algorithm in the driver did not include any feedback
from the measured TX power and could allow TX power values that cause
interference or signal quality issues"

What algorithm? The "dBm" value is simply transformed into the
128-255,0-127 range and written to CR31.

How can that cause interference/poor quality? By setting the power too
high/low? Well, I thought that this was the aim of txpower control - to
let the user take over the txpower setting and test the signal quality
and interference herself, not relying on some strange firmware
behaviour.

> I will probably take a look at implementing proper feedback loop from
> the TX power measurements. 

What is is supposed to do? Isn't the feedback value in CR58 only a
result of the CR31 (txpower)? Or can it be influeced by something else
as well? (If not, what would be the point of using the feedback? - how
would that improve interference/signal quality?)

> Clean and tested patch to implement this would be accepted gladly ;-).

Once I find out what you're trying to achieve.... I might try :)

regards,

Jirka
CZFree.Net



From jkmaline  Sat Aug  2 09:32:30 2003
From: jkmaline (Jouni Malinen)
Date: Sat, 2 Aug 2003 09:32:30 -0700
Subject: SMP Frequent Lockups
In-Reply-To: <20030801173915.68ab335e.vaio@nolatency.com>
References: <20030801173915.68ab335e.vaio@nolatency.com>
Message-ID: <20030802163230.GA3470@jm.kir.nu>

On Fri, Aug 01, 2003 at 05:39:15PM +0000, Michael Vallaly wrote:

> I am having issues with my WPC11 Linksys PCI card and a 2.4.21 SMP kernel. I recently upgraded the machine with another processor and recompiled the kernel to support SMP. Previously ive had only 1 or 2 lockups (non SMP kernel) using Hostap 0.0.3 under heavy traffic (FTP for instance) over a 3 month span. Now with the SMP kernel I have lockups with even light usage of the wireless AP (ssh or webbrowsing). These are hard lockups that require cycling the power via unplugging. I can verify that the lockups only happen with some sort of traffic on the wireless card, as I can keep the hostap module loaded with the interface down, and not crash. Anyone have a solution? 

Could you please first verify couple of things:

1) if you boot non-SMP kernel and try the latest CVS version of Host AP
   driver, the host does not crash (at least frequently)
2) can you enable NMI watchdog? (see Linux kernel
   Documentation/nmi_watchdog.txt; verify that NMI counter increases in
   /proc/interrupts)

Unfortunately, I have been only able to test with hostap_cs and
hostap_plx on an SMP host and I was unable to crash the box. Since you
have a card using hostap_pci, it would be nice to get more testing on
that.

Before doing any changes to the driver, I would like to know whether you
can get any output from the lockup when using SMP-kernel. I would
suggest enabling NMI watchdog, moving to text mode, setting console
logging level to maximum ('dmesg -n 8'). Then do whatever is needed to
hang the system. Wait about 10 seconds and hope that something will be
printed on screen.

-- 
Jouni Malinen                                            PGP id EFC895FA



From eduardo  Sat Aug  2 09:56:52 2003
From: eduardo (Eduardo Kaftanski)
Date: Sat, 2 Aug 2003 12:56:52 -0400
Subject: SMP Frequent Lockups
In-Reply-To: <20030802163230.GA3470@jm.kir.nu>
References: <20030801173915.68ab335e.vaio@nolatency.com>
	<20030802163230.GA3470@jm.kir.nu>
Message-ID: <20030802165652.GA27323@enriqueto.nn.cl>

> 
> Could you please first verify couple of things:
> 
> 1) if you boot non-SMP kernel and try the latest CVS version of Host AP
>    driver, the host does not crash (at least frequently)
> 2) can you enable NMI watchdog? (see Linux kernel
>    Documentation/nmi_watchdog.txt; verify that NMI counter increases in
>    /proc/interrupts)
> 
> Unfortunately, I have been only able to test with hostap_cs and
> hostap_plx on an SMP host and I was unable to crash the box. Since you
> have a card using hostap_pci, it would be nice to get more testing on
> that.
> 
> Before doing any changes to the driver, I would like to know whether you
> can get any output from the lockup when using SMP-kernel. I would
> suggest enabling NMI watchdog, moving to text mode, setting console
> logging level to maximum ('dmesg -n 8'). Then do whatever is needed to
> hang the system. Wait about 10 seconds and hope that something will be
> printed on screen.
> 

I can do that tonight and report... how can I enable the watchdog?


-- 
Eduardo Kaftanski
eduardo at linuxcenter.cl
Red Hat Certified Engineer
Gerente Ingenieria LinuxCenter S.A.
Canada 239 5to Piso, Providencia, Stgo de Chile.
http://www.linuxcenter.cl 2745000



From jkmaline  Sat Aug  2 10:05:53 2003
From: jkmaline (Jouni Malinen)
Date: Sat, 2 Aug 2003 10:05:53 -0700
Subject: SMP Frequent Lockups
In-Reply-To: <20030802165652.GA27323@enriqueto.nn.cl>
References: <20030801173915.68ab335e.vaio@nolatency.com>
	<20030802163230.GA3470@jm.kir.nu> <20030802165652.GA27323@enriqueto.nn.cl>
Message-ID: <20030802170553.GA3780@jm.kir.nu>

On Sat, Aug 02, 2003 at 12:56:52PM -0400, Eduardo Kaftanski wrote:

> > 2) can you enable NMI watchdog? (see Linux kernel
> >    Documentation/nmi_watchdog.txt; verify that NMI counter increases in
> >    /proc/interrupts)

> I can do that tonight and report... how can I enable the watchdog?

By reading the documentation file I mentioned.. ;-) With SMP systems,
kernel should be ready for this, so appending "nmi_watchdog=1" to
kernel command line should be enough.

-- 
Jouni Malinen                                            PGP id EFC895FA



From maillists  Sat Aug  2 10:16:00 2003
From: maillists (Ray)
Date: Sat, 2 Aug 2003 10:16:00 -0700
Subject: hostap on Senao 2511 wireless cards
In-Reply-To: <Pine.LNX.4.44.0308011342140.25345-100000@kinison.puremagic.com>
References: <Pine.LNX.4.44.0308011342140.25345-100000@kinison.puremagic.com>
Message-ID: <20030802171600.GA7831@sonictech.net>

On Fri, Aug 01, 2003 at 01:47:43PM -0500, Evan Harris wrote:
> 
> I'm trying to get hostap running on some Senao 2511 cards, and am getting
> some error messages when starting the card.  The Senao cards are supposed to
> be Prism reference design cards, and have been working fine for us for a
> long time with wlan-ng as the client side.
> 
> Any help or suggestions anyone can give would be greatly appreciated.

I can't really tell much from the output provided but I can say that I've
been using HostAP with these Senao 2511 cards (and recently with the same
kernel version) so it's probably not the card.  You say you've used wlan-ng
but was this on the same machine and with the same pcmcia adapter?  

-- 
Ray



From eharris  Sat Aug  2 10:36:25 2003
From: eharris (Evan Harris)
Date: Sat, 2 Aug 2003 12:36:25 -0500 (CDT)
Subject: hostap on Senao 2511 wireless cards
In-Reply-To: <20030802171600.GA7831@sonictech.net>
Message-ID: <Pine.LNX.4.44.0308021221230.25345-100000@kinison.puremagic.com>


While we've been running wlan-ng for quite a while in other machines, after
I had problems setting up hostap in the new machine, I tried the wlan-ng
stuff on the same machine/same PCI card just to test it wasn't a problem
with the pci bridge.  Wlan-ng loads and initializes the card just fine using
the bridge, but hostap gives all those errors.  I tried changing the port
and interrupt being used with pcmcia-cs in case that might be the cause, all
to no effect.  wlan-ng still works, and hostap doesn't.

The PCMCIA card and PCI bridge card are the same ones that NetGate sells,
and they had a direct link to the hostap stuff, which made me think it was
supported.  Unfortunately, doesn't seem to work here, or I've got a config
issue that I can't find.

If there's any other output that would be more helpful, please let me know,
and I will provide it.

Evan


On Sat, 2 Aug 2003, Ray wrote:

> On Fri, Aug 01, 2003 at 01:47:43PM -0500, Evan Harris wrote:
> >
> > I'm trying to get hostap running on some Senao 2511 cards, and am getting
> > some error messages when starting the card.  The Senao cards are supposed to
> > be Prism reference design cards, and have been working fine for us for a
> > long time with wlan-ng as the client side.
> >
> > Any help or suggestions anyone can give would be greatly appreciated.
>
> I can't really tell much from the output provided but I can say that I've
> been using HostAP with these Senao 2511 cards (and recently with the same
> kernel version) so it's probably not the card.  You say you've used wlan-ng
> but was this on the same machine and with the same pcmcia adapter?
>
> --
> Ray
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From jkmaline  Sat Aug  2 12:42:40 2003
From: jkmaline (Jouni Malinen)
Date: Sat, 2 Aug 2003 12:42:40 -0700
Subject: Primary Firmware Download
In-Reply-To: <Pine.LNX.4.56.0307311641270.8658@marabou.research.att.com>
References: <EF5625F9F795C94BA28B150706A21548A053D0@MAIL>
	<Pine.LNX.4.56.0307311641270.8658@marabou.research.att.com>
Message-ID: <20030802194240.GA4756@jm.kir.nu>

On Thu, Jul 31, 2003 at 04:57:10PM -0400, Pavel Roskin wrote:

> I don't know why you think that flashing primary firmware is not reliable.
> It has always worked for me.  The problem is that HostAP cannot flash the
> secondary firmware after that, so it was disabled in prism2_srec.

Yes, that was the case before today ;-).

> prism2dl with linux-wlan-ng flashes primary and secondary firmware just
> fine.  On the other hand, loading primary firmware into the RAM has newer
> worked for me with any driver, including linux-wlan-ng.

I think I have seen this working fine with Windows drivers from
Intersil, so s/any driver/any Linux driver/..

> 1) Figure out how to load primary firmware into the RAM.  I have no idea
> how.  Try setting genesis mode.  You may need to ask Intersil, but it may
> be very expensive and not very helpful.

My current guess is to 1) set Genesis mode, 2) load PRI to RAM, 3) soft
reset to PRI without Genesis mode, 4) RAM download secondary f/w using
PRI. I have done some experiments with this and have added a new
"download using Genesis mode" option for prism2_srec and the driver
(although these are not yet in CVS). The problem is, this just does not
seem to work the way I expect it to work; or I just cannot start/use the
PRI-only card correctly.

> 2) Fix HostAP to support flashing when only primary firmware is in the
> card (note that flashing primary firmware disables secondary firmware).
> That's the most realistic option and really needs to be done.  It's being
> asked all the time, but nobody seems to be working on it.

Yes, PRI-only operations should be implemented at some point. Btw, I
would assume that removing the two octets that override "CRC-16
signature" (0xC0DE) from the PRI f/w could work if the secondary
firmware is able to handle new PRI interface..

I have been somewhat reluctant to work with this since fixing the card
I use in testing requires me to find a suitable Windows box somewhere
and move the PCI card to it or changing drivers, etc.. Maybe I should
just "kill" one card (by replacing that 0xC0DE signature with 0xFFFF) so
that it is known to have working PRI, but no secondary firmware. That
could be enough motivation to work on PRI-only mode to get the card
fixed ;-).

> 3) Combine primary and secondary firmware into one image and flash it in
> one operation.  This gives you the easiest procedure, but requires a lot
> of work to be done to create the image.

Not really that much work.. prism2_srec already had most functions that
were needed for this. After some code cleanup it was quite easy to add
support for loading two srec files and merging them together.
Verification of interface compatibility needed some small changes, too,
but that was it. Current CVS snapshot version of prism2_srec seems to be
able to do the job correctly.

I have been able to download both primary and secondary firmware to
flash with one command. I tested firmware upgrades and downgrades
between (PRI 1.0.5, STA 1.3.4) and (PRI 1.1.1, STA 1.7.4) using a PCI
Prism2.5 card. Since this has not yet been tested thoroughly, I would of
course suggest being somewhat cautious about it, but I'm not aware of
any issues with the operation. Anyway, please do report results if you
test it.

The new version of prism2_srec accepts two srec files in the command
line:

# test compatibility without writing anything to flash
./prism2_srec wlan0 pk010101.hex sf010704.hex

# download to flash
./prism2_srec -f wlan0 pk010101.hex sf010704.hex

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Aug  2 12:49:18 2003
From: jkmaline (Jouni Malinen)
Date: Sat, 2 Aug 2003 12:49:18 -0700
Subject: hostap on Senao 2511 wireless cards
In-Reply-To: <Pine.LNX.4.44.0308021221230.25345-100000@kinison.puremagic.com>
References: <20030802171600.GA7831@sonictech.net>
	<Pine.LNX.4.44.0308021221230.25345-100000@kinison.puremagic.com>
Message-ID: <20030802194918.GB4756@jm.kir.nu>

On Sat, Aug 02, 2003 at 12:36:25PM -0500, Evan Harris wrote:

> While we've been running wlan-ng for quite a while in other machines, after
> I had problems setting up hostap in the new machine, I tried the wlan-ng
> stuff on the same machine/same PCI card just to test it wasn't a problem
> with the pci bridge.  Wlan-ng loads and initializes the card just fine using
> the bridge, but hostap gives all those errors.

Could you please send the 'dmesg' output of a successful linux-wlan-ng
initialization for comparison. The log entries you send of hostap_cs
indicated that interrupt delivery was not working. The card had set
CmdCompl event and this was not masked, but the driver still did not
receive interrupt. Usually this is caused by invalid pcmcia-cs
configuration, but since you have it working with another driver, this
seems to be something else.

-- 
Jouni Malinen                                            PGP id EFC895FA



From proski  Sat Aug  2 16:55:53 2003
From: proski (Pavel Roskin)
Date: Sat, 02 Aug 2003 19:55:53 -0400 (EDT)
Subject: Primary Firmware Download
In-Reply-To: <20030802194240.GA4756@jm.kir.nu>
Message-ID: <Pine.LNX.4.44.0308021949001.658-100000@portland.hansa.lan>

On Sat, 2 Aug 2003, Jouni Malinen wrote:

> On Thu, Jul 31, 2003 at 04:57:10PM -0400, Pavel Roskin wrote:
>
> > I don't know why you think that flashing primary firmware is not reliable.
> > It has always worked for me.  The problem is that HostAP cannot flash the
> > secondary firmware after that, so it was disabled in prism2_srec.
>
> Yes, that was the case before today ;-).

Jouni, you are the man!!!

> > 1) Figure out how to load primary firmware into the RAM.  I have no idea
> > how.  Try setting genesis mode.  You may need to ask Intersil, but it may
> > be very expensive and not very helpful.
>
> My current guess is to 1) set Genesis mode, 2) load PRI to RAM, 3) soft
> reset to PRI without Genesis mode, 4) RAM download secondary f/w using
> PRI. I have done some experiments with this and have added a new
> "download using Genesis mode" option for prism2_srec and the driver
> (although these are not yet in CVS). The problem is, this just does not
> seem to work the way I expect it to work; or I just cannot start/use the
> PRI-only card correctly.

Incidentally, linux-wlan-ng 0.2.1-pre11 was released yesterday, and one of
the new features is genesis mode support.  Genesis mode is turned on
automatically if the "start" address from the S7 record is 0x3f0000.  I
tried to load some primary firmwares into DWL-520 rev. A, but it didn't
work.

Anyway, I'm yet to see any Prism hardware without flash, where anything
like that would be really useful.

> Yes, PRI-only operations should be implemented at some point. Btw, I
> would assume that removing the two octets that override "CRC-16
> signature" (0xC0DE) from the PRI f/w could work if the secondary
> firmware is able to handle new PRI interface..

Maybe.  Once we do it, it will be OK to ditch prism2dl forever.

> I have been somewhat reluctant to work with this since fixing the card I
> use in testing requires me to find a suitable Windows box somewhere and
> move the PCI card to it or changing drivers, etc.. Maybe I should just
> "kill" one card (by replacing that 0xC0DE signature with 0xFFFF) so that
> it is known to have working PRI, but no secondary firmware. That could
> be enough motivation to work on PRI-only mode to get the card fixed ;-).

I don't know what Windows has to do with it.  Disable the check in
prism2_srec that disallows programming primary firmware and program it.
You can always use linux-wlan-ng and prism2dl, preferably from
http://www.red-bean.com/~proski/prism2dl/ to program the secondary
firmware if you give up and need the card.

> > 3) Combine primary and secondary firmware into one image and flash it in
> > one operation.  This gives you the easiest procedure, but requires a lot
> > of work to be done to create the image.
>
> Not really that much work..

Except that I meant combining the text by hand and completely forgot that
it can be done by prism2_srec.

> I have been able to download both primary and secondary firmware to
> flash with one command. I tested firmware upgrades and downgrades
> between (PRI 1.0.5, STA 1.3.4) and (PRI 1.1.1, STA 1.7.4) using a PCI
> Prism2.5 card. Since this has not yet been tested thoroughly, I would of
> course suggest being somewhat cautious about it, but I'm not aware of
> any issues with the operation. Anyway, please do report results if you
> test it.

I downgraded my DWL-520 Rev. A to PRI 1.0.4, STA 1.1.0, but now hostap_pci
crashes on load.  That's a theme for a separate thread once I do at least
minimal debugging.

> The new version of prism2_srec accepts two srec files in the command
> line:

Thank you very much!

-- 
Regards,
Pavel Roskin



From proski  Sat Aug  2 17:37:10 2003
From: proski (Pavel Roskin)
Date: Sat, 02 Aug 2003 20:37:10 -0400 (EDT)
Subject: [PATCH] Kernel panic in hostap_pci
Message-ID: <Pine.LNX.4.44.0308022028460.883-200000@portland.hansa.lan>

Hello!

If the secondary firmware is not functioning properly and fid allocation
fails, hostap_pci decides that it should not serve the device, tries to
free all resources and crashes.

There are two issues here.  One is that the driver should still accept the
device and mark it as "braindead" to allow firmware download, but no
network operations.  This may fix loading secondary firmware after the
primary firmware was loaded in a separate operation.

The other issue is the crash itself.  That was easy.  free_irq uses
dev->irq, but dev is allocated inside local, which is freed already at
that point.  hostap_plx does it right, by the way.

The patch is attached.

-- 
Regards,
Pavel Roskin
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pci_crash.diff
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20030802/0b3ad314/attachment.txt 


From jkmaline  Sat Aug  2 22:46:29 2003
From: jkmaline (Jouni Malinen)
Date: Sat, 2 Aug 2003 22:46:29 -0700
Subject: [PATCH] Kernel panic in hostap_pci
In-Reply-To: <Pine.LNX.4.44.0308022028460.883-200000@portland.hansa.lan>
References: <Pine.LNX.4.44.0308022028460.883-200000@portland.hansa.lan>
Message-ID: <20030803054629.GA8276@jm.kir.nu>

On Sat, Aug 02, 2003 at 08:37:10PM -0400, Pavel Roskin wrote:

> There are two issues here.  One is that the driver should still accept the
> device and mark it as "braindead" to allow firmware download, but no
> network operations.  This may fix loading secondary firmware after the
> primary firmware was loaded in a separate operation.

Look at CVS.. ;-)

> The other issue is the crash itself.  That was easy.  free_irq uses
> dev->irq, but dev is allocated inside local, which is freed already at
> that point.  hostap_plx does it right, by the way.
> 
> The patch is attached.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Aug  2 23:01:26 2003
From: jkmaline (Jouni Malinen)
Date: Sat, 2 Aug 2003 23:01:26 -0700
Subject: Primary Firmware Download
In-Reply-To: <Pine.LNX.4.44.0308021949001.658-100000@portland.hansa.lan>
References: <20030802194240.GA4756@jm.kir.nu>
	<Pine.LNX.4.44.0308021949001.658-100000@portland.hansa.lan>
Message-ID: <20030803060126.GB8276@jm.kir.nu>

On Sat, Aug 02, 2003 at 07:55:53PM -0400, Pavel Roskin wrote:

> > My current guess is to 1) set Genesis mode, 2) load PRI to RAM, 3) soft
> > reset to PRI without Genesis mode, 4) RAM download secondary f/w using
> > PRI.

That guess was correct. I used to test Genesis mode with hostap_pci, but
I decided to quickly test with hostap_cs. Everything started working
suddenly :-). I was able to enable the Genesis mode and load Primary f/w
to RAM. This forced me to finally fix PRI-only operation ;-). With this,
I was able to load secondary f/w into RAM while the card was running in
PRI-only mode. I have not yet tested, whether this works when PRI is
actually loaded from flash, but I would assume it would work equally
well.

I haven't yet fixed hostap_pci, so Genesis mode can now be used only
with hostap_cs. However, PRI-only mode should work even with hostap_pci.
I will take a look at fixing this. If someone is interested in working
with this, the only missing part should be in adding
prism2_pci_genesis_reset() into hostap_pci.c. hostap_plx can wait for
the time being, since I do not have my PLX adapter easily available.

> Anyway, I'm yet to see any Prism hardware without flash, where anything
> like that would be really useful.

RAM downloading Primary can be quite useful even with flash. I feel much
more confident flashing a new version after I have been able to first
verify that it actually works using RAM download. Having PRI f/w older
than 1.0.7 on hfa3842 used to make this quite difficult (at least with
Host AP driver) before Genesis mode support.

> I downgraded my DWL-520 Rev. A to PRI 1.0.4, STA 1.1.0, but now hostap_pci
> crashes on load.  That's a theme for a separate thread once I do at least
> minimal debugging.

I assume your patch fixed the crash. Do you know why that firmware
combination does not work?


And the new magic prism2_srec commands:

# Download primary firmware into RAM using Genesis mode
./prism2_srec -g wlan0 ak010100.hex
# card is now in PRI-only mode with very limited functionality

# download station firmware into RAM
./prism2_srec -r wlan0 rf010409.hex
# card is now in normal mode

-- 
Jouni Malinen                                            PGP id EFC895FA



From proski  Sun Aug  3 00:18:52 2003
From: proski (Pavel Roskin)
Date: Sun, 03 Aug 2003 03:18:52 -0400 (EDT)
Subject: Primary Firmware Download
In-Reply-To: <20030803060126.GB8276@jm.kir.nu>
Message-ID: <Pine.LNX.4.44.0308030259350.1445-100000@portland.hansa.lan>

On Sat, 2 Aug 2003, Jouni Malinen wrote:

> That guess was correct. I used to test Genesis mode with hostap_pci, but
> I decided to quickly test with hostap_cs. Everything started working
> suddenly :-). I was able to enable the Genesis mode and load Primary f/w
> to RAM. This forced me to finally fix PRI-only operation ;-). With this,
> I was able to load secondary f/w into RAM while the card was running in
> PRI-only mode. I have not yet tested, whether this works when PRI is
> actually loaded from flash, but I would assume it would work equally
> well.

Very impressive.  Now the world is a better place to live :-)

> I haven't yet fixed hostap_pci, so Genesis mode can now be used only
> with hostap_cs. However, PRI-only mode should work even with hostap_pci.
> I will take a look at fixing this. If someone is interested in working
> with this, the only missing part should be in adding
> prism2_pci_genesis_reset() into hostap_pci.c. hostap_plx can wait for
> the time being, since I do not have my PLX adapter easily available.

Well, I have a PLX card and I can put a Prism 2.5 card into it.  I also
have a PCI card that needs resurrection.

I'm not sure if you did something to allow the driver initialization to go
ahead if the FID allocation (or some other part of initialization) fails.
Right now, hostap_pci refuses to serve a card with STA 1.1.0.

By the way, the "idle" argument is unused and should be removed.  hcr
already determines if the card should be idle upon reset.

> > I downgraded my DWL-520 Rev. A to PRI 1.0.4, STA 1.1.0, but now
> > hostap_pci crashes on load.  That's a theme for a separate thread once
> > I do at least minimal debugging.
>
> I assume your patch fixed the crash. Do you know why that firmware
> combination does not work?

Yes, the crash is fixed now.  I don't know why it doesn't work.  I cannot
believe Intersil would release firmware that doesn't work at all.  Maybe
it's incompatible with PCI cards that appeared later.

On the other hand, I know a Prism2 (SMC 2632W) card that used to work
with STA firmware 0.7.6, but then "degraded" and worked only sporadically.
When I tried to update the firmware using prism2_srec, I saw exactly the
same error with allocating FIDs.  I had to use prism2dl to flash it.

Maybe older firmware has a problem with some parameters fluctuating with
time, temperature, radio interference or the phase of the Moon :-)

-- 
Regards,
Pavel Roskin



From jkmaline  Sun Aug  3 00:46:36 2003
From: jkmaline (Jouni Malinen)
Date: Sun, 3 Aug 2003 00:46:36 -0700
Subject: Primary Firmware Download
In-Reply-To: <Pine.LNX.4.44.0308030259350.1445-100000@portland.hansa.lan>
References: <20030803060126.GB8276@jm.kir.nu>
	<Pine.LNX.4.44.0308030259350.1445-100000@portland.hansa.lan>
Message-ID: <20030803074636.GA10544@jm.kir.nu>

On Sun, Aug 03, 2003 at 03:18:52AM -0400, Pavel Roskin wrote:

> Well, I have a PLX card and I can put a Prism 2.5 card into it.  I also
> have a PCI card that needs resurrection.

Feel free to implement prism2_plx_genesis_reset() for it..

> I'm not sure if you did something to allow the driver initialization to go
> ahead if the FID allocation (or some other part of initialization) fails.
> Right now, hostap_pci refuses to serve a card with STA 1.1.0.

Yes, I was wrong about PRI-only mode working with hostap_pci.. It is not
supposed to try FID allocation. I fixed it now. In addition, I managed
to get Genesis mode working also with hostap_pci. It was just getting
confused about AUX port being enabled twice.

I did also couple of fixes for flash downloading when in PRI-only mode
and since it seems to work, I enabled flash download of Primary firmware
without secondary. It is now possible to flash secondary separately.

> By the way, the "idle" argument is unused and should be removed.  hcr
> already determines if the card should be idle upon reset.

Yes, it was left there from some of my early tests. The code needs some
more cleaning anyway, but it can wait till tomorrow ;-).

-- 
Jouni Malinen                                            PGP id EFC895FA



From proski  Sun Aug  3 00:52:21 2003
From: proski (Pavel Roskin)
Date: Sun, 03 Aug 2003 03:52:21 -0400 (EDT)
Subject: Primary Firmware Download
In-Reply-To: <Pine.LNX.4.44.0308030259350.1445-100000@portland.hansa.lan>
Message-ID: <Pine.LNX.4.44.0308030341370.2162-100000@portland.hansa.lan>

On Sun, 3 Aug 2003, Pavel Roskin wrote:

> I'm not sure if you did something to allow the driver initialization to go
> ahead if the FID allocation (or some other part of initialization) fails.
> Right now, hostap_pci refuses to serve a card with STA 1.1.0.

P.S. This could be worked around by using the "delayed_enable=1"
parameter.  I could resurrect DWL-520 and flash it back to PRI 1.1.1 and
STA 1.7.4.  I also could load both PRI and STA firmware in RAM by
following commands:

prism2_srec -g wlan0 ak010104.hex
prism2_srec -r wlan0 rf010704.hex

>From the kernel log:

wlan0: trying to read PDA from 0x007f0000: OK
wlan0: NIC: id=0x8013 v1.0.0
wlan0: PRI: id=0x15 v1.1.4
wlan0: STA: id=0x1f v1.7.4
wlan0: prism2_open

"1.1.4" confirms that the new primary firmware has been loaded.
Excellent!

-- 
Regards,
Pavel Roskin



From proski  Sun Aug  3 01:19:19 2003
From: proski (Pavel Roskin)
Date: Sun, 03 Aug 2003 04:19:19 -0400 (EDT)
Subject: [TRIVIAL PATCH] Removal of attr_mem and cor_offset for PCI
Message-ID: <Pine.LNX.4.44.0308030413510.2797-200000@portland.hansa.lan>

Hello!

Fields attr_mem and cor_offset are not needed in the PCI version of the
driver.  PCI devices have no attribute memory.  The COR offset is a
constant value 0x5C.  Accidental use of the uninitialized cor_offset field
would be very bad.  It's better to remove both fields.

-- 
Regards,
Pavel Roskin
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pci_cor_offset.diff
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20030803/af2468a5/attachment.txt 


From proski  Sun Aug  3 01:43:19 2003
From: proski (Pavel Roskin)
Date: Sun, 03 Aug 2003 04:43:19 -0400 (EDT)
Subject: [PATCH] PLX genesis mode support
Message-ID: <Pine.LNX.4.44.0308030422530.2797-200000@portland.hansa.lan>

Hello!

This patch enables genesis mode support on cards using PLX and TMD
adapters.  I cannot test it on my PLX board until Monday, but I'm 80%
confident that it would work.  The patch should be safe to apply - it
doesn't affect existing functionality.

I'll not be able to test this patch on a TMD board, so volunteers are
needed.

Since the COR and HCR registers are actually located on the PCMCIA card, I
decided to preserve COR except the reset bit as it's done in hostap_cs
rather than use fixed values as in hostap_pci.

To test this code, a Prism 2.5 card should be used in the PLX or TMD slot.
Prism 2 cards won't work.  Try loading primary firmware into RAM by using
this command:

prism2_srec -g wlan0 ak010104.hex

ak010104.hex can be taken from
http://www.red-bean.com/~proski/firmware/1.7.4.tar.gz

-- 
Regards,
Pavel Roskin
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: plx_genesis.diff
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20030803/dd5e4d89/attachment.txt 


From sits  Sun Aug  3 03:44:38 2003
From: sits (Sitsofe Wheeler)
Date: 03 Aug 2003 11:44:38 +0100
Subject: Hostap 0.0.4 interrupt problems
Message-ID: <1059907478.1957.45.camel@galvatron.localdomain>

Hi,

I have just compiled and installed Hostap 0.0.4 on my Compaq iPAQ and
initially thought that the driver was failing to work until I did a
manual reset by using "iwpriv wlan0 reset 1". After this the card
started working until it was suspended or removed and reinserted. On the
odd occasion I will insert the card and everything will work from the
off. Neither the orinoco (0.13e) nor the linux-wlan (0.2.1-pre9) drivers
have this problem. I have attached dmesg output of hostap and
linux-wlan.

I also see a problem when downloading a 10Mb file at a high speed (>
500KB/s) using wget. After about two seconds, the transfer will stop,
Hostap will print error messages to the console and the card is not
reset until I try and ping another machine (at which point it
successfully resets the card only to get into trouble again a second or
two later). I have tried the orinoco drivers and they too have a similar
problem (transfer a little bit then lock up and print error messages)
but the orinoco drivers seem more successful at resetting the card
without prompting. However, the linux-wlan drivers don't even lock up in
the first place and can transfer the entire file at speed (> 550KB/s)
without incident. I've attached the dmesg output which occurs during the
transfer.

Can anyone shed any light on the above problems or why linux-wlan
doesn't suffer the lockups the other drivers do when downloading at
speed? 

-- 
Sitsofe | http://sucs.org/~sits/
-------------- next part --------------
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.0.4 - 2003-07-27 (Jouni Malinen <jkmaline at cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
prism2_config()
hostap_cs: ignoring Vcc=33 (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 3.3, irq 42, io 0xcaa80000-0xcaa8003f
hostap_cs: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_init: initialized in 100 ms
wlan0: NIC: id=0x8003 v1.0.0
wlan0: PRI: id=0x15 v0.3.0
wlan0: STA: id=0x1f v1.4.9
wlan0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AS
wlan0: hfa384x_cmd: entry still in list? (entry=c1e498e4, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=c1e498e4, type=0, c)
wlan0: interrupt delivery does not seem to work
wlan0: reset port failed to disable port
wlan0: MAC port 0 reseting failed
prism2: wlan0: operating mode changed 3 -> 2
wlan0: hfa384x_cmd: entry still in list? (entry=c1e412b4, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=c1e412b4, type=0, c)
wlan0: interrupt delivery does not seem to work
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=-110, rid=fc00, len=2)
wlan0: hfa384x_cmd: entry still in list? (entry=c1e413d4, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=c1e413d4, type=0, c)
wlan0: interrupt delivery does not seem to work
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=-110, rid=fc0e, len=34)
wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wlan0: hfa384x_cmd_issue - timeout - reg=0x8000
wlan0: hfa384x_cmd: entry still in list? (entry=c1e413d4, type=0, res=-1)
wlan0: hfa384x_cmd: interrupted; err=-110
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=-110, rid=fc02, len=34)
wlan0: prism2_open
wlan0: manual reset request(1)
hostap_cs: wlan0: resetting card
prism2_pccard_cor_sreset: original COR 41
prism2_hw_init()
prism2_hw_init: initialized in 110 ms
wlan0: LinkStatus=1 (Connected)
wlan0: LinkStatus: BSSID=00:30:ab:22:7f:0b
-------------- next part --------------
prism2_init: prism2_cs.o: 0.2.1-pre9 Loaded
prism2_init: dev_info is: prism2_cs
prism2_cs: index 0x01: Vcc 3.3, irq 42, io 0xcaa80000-0xcaa8003f
ident: nic h/w: id=0x8003 1.0.0
ident: pri f/w: id=0x15 0.3.0
ident: sta f/w: id=0x1f 1.4.9
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
CFI:SUP:role=0x00:id=0x02:var=0x01:b/t=1/1
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/2
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/9
PRI-CFI:ACT:role=0x01:id=0x02:var=0x01:b/t=1/1
STA-CFI:ACT:role=0x01:id=0x02:var=0x01:b/t=1/1
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Prism2 card SN: 011000000533
linkstatus=CONNECTED
Attempt to kill tasklet from interrupt
hfa384x_cmd_access: Call to hfa384x_docmd_wait failed (127 31354)
prism2_cs.o: 0.2.1-pre9 Unloaded
p80211.o: 0.2.1-pre9 Unloaded
-------------- next part --------------
wlan0: LinkStatus=2 (Disconnected)
wlan0: LinkStatus: BSSID=44:44:44:44:44:44
wlan0: prism2_open
wlan0: LinkStatus=1 (Connected)
wlan0: LinkStatus: BSSID=00:30:ab:22:7f:0b
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0 Tx timed out! Resetting card
wlan0: CMD=010b EVSTAT=8019 OFFSET0=0000 OFFSET1=0000 SWSUPPORT0=8a32
wlan0: scheduled card reset
hostap_cs: wlan0: resetting card
prism2_pccard_cor_sreset: original COR 41
wlan0: removed pending cmd_queue entry (type=1, cmd=0x010b, param0=0x0138)
prism2_hw_init()
prism2_hw_init: initialized in 110 ms
wlan0: LinkStatus=1 (Connected)
wlan0: LinkStatus: BSSID=00:30:ab:22:7f:0b
(did a ping here)
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0 Tx timed out! Resetting card
wlan0: CMD=010b EVSTAT=8099 OFFSET0=0000 OFFSET1=0000 SWSUPPORT0=8a32
wlan0: scheduled card reset
hostap_cs: wlan0: resetting card
prism2_pccard_cor_sreset: original COR 41
wlan0: removed pending cmd_queue entry (type=1, cmd=0x010b, param0=0x0123)
prism2_hw_init()
prism2_hw_init: initialized in 110 ms
wlan0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
   A1=00:30:ab:22:7f:0b A2=00:04:db:00:02:15 A3=00:d0:70:01:a0:79 A4=00:00:00:00
wlan0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
   A1=00:30:ab:22:7f:0b A2=00:04:db:00:02:15 A3=00:d0:70:01:a0:79 A4=00:00:00:00
wlan0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
   A1=00:30:ab:22:7f:0b A2=00:04:db:00:02:15 A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00


From hostap  Sun Aug  3 04:15:05 2003
From: hostap (Wilfried Klaebe)
Date: Sun, 3 Aug 2003 13:15:05 +0200
Subject: [PATCH] Kernel panic in hostap_pci
In-Reply-To: <20030803054629.GA8276@jm.kir.nu>
References: <Pine.LNX.4.44.0308022028460.883-200000@portland.hansa.lan>
	<20030803054629.GA8276@jm.kir.nu>
Message-ID: <20030803111505.GA23197@orion.toppoint.de>

Am Sat, Aug 02, 2003 at 10:46:29PM -0700 schrieb Jouni Malinen:
> On Sat, Aug 02, 2003 at 08:37:10PM -0400, Pavel Roskin wrote:
> 
> > There are two issues here.  One is that the driver should still accept the
> > device and mark it as "braindead" to allow firmware download, but no
> > network operations.  This may fix loading secondary firmware after the
> > primary firmware was loaded in a separate operation.
> 
> Look at CVS.. ;-)

I played around a little and found out that it is now possible to
ram-download primary firmware in genesis mode, and then secondary
firmware on top of that, and it all works perfectly! Just

prism2_srec -g wlan0 ak010104.hex
prism2_srec -r wlan0 rf010704.hex

and done...

Thanks, guys!

Regards, Wilfried
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20030803/9ab7a939/attachment.pgp 


From jkmaline  Sun Aug  3 08:54:02 2003
From: jkmaline (Jouni Malinen)
Date: Sun, 3 Aug 2003 08:54:02 -0700
Subject: [TRIVIAL PATCH] Removal of attr_mem and cor_offset for PCI
In-Reply-To: <Pine.LNX.4.44.0308030413510.2797-200000@portland.hansa.lan>
References: <Pine.LNX.4.44.0308030413510.2797-200000@portland.hansa.lan>
Message-ID: <20030803155402.GA3426@jm.kir.nu>

On Sun, Aug 03, 2003 at 04:19:19AM -0400, Pavel Roskin wrote:

> Fields attr_mem and cor_offset are not needed in the PCI version of the
> driver.  PCI devices have no attribute memory.  The COR offset is a
> constant value 0x5C.  Accidental use of the uninitialized cor_offset field
> would be very bad.  It's better to remove both fields.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Aug  3 08:56:53 2003
From: jkmaline (Jouni Malinen)
Date: Sun, 3 Aug 2003 08:56:53 -0700
Subject: [PATCH] PLX genesis mode support
In-Reply-To: <Pine.LNX.4.44.0308030422530.2797-200000@portland.hansa.lan>
References: <Pine.LNX.4.44.0308030422530.2797-200000@portland.hansa.lan>
Message-ID: <20030803155653.GB3426@jm.kir.nu>

On Sun, Aug 03, 2003 at 04:43:19AM -0400, Pavel Roskin wrote:

> This patch enables genesis mode support on cards using PLX and TMD
> adapters.  I cannot test it on my PLX board until Monday, but I'm 80%
> confident that it would work.  The patch should be safe to apply - it
> doesn't affect existing functionality.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From lcaeiro  Sun Aug  3 08:58:05 2003
From: lcaeiro (Luisa Caeiro)
Date: Sun, 3 Aug 2003 16:58:05 +0100
Subject: Tx process
Message-ID: <007b01c359d8$14360b40$6401a8c0@netcabo>

Hi all,

According to Prism2 Driver Programmer's Manual to MAC PRISM transmit (after write a packet in the buffer):
    . the driver need to write tx command to Command register
    . the firmware puts frame (referenced by FID) on the transmit queue for further processing and waits for transmit to complete
    . the firmware ackowledge frame transmition with a TX bit on EVSTAT or indicates failure with TXEXC on EVSTAT.   

In the driver (according my understand):
    . prism2_transmit function writes the TX command to Command register
    . prism2_cmd_ev function is called from prism2_interrupt 
after a event command generated by the firmware
    . prism2_interrupt gives the event stat generated by the firmware (I suppose the TX or TXexc after the transmit command) 
    . according to the event identified calls the correspondig function or schedules the corresponding tasklet (for tx events prism2_tx_ev or prism2_txexc). 
Is this correct? Do I need to activate some parameter to have this behaviour?
Because, I'm trying to follow this procedure and after a prism2_transmit call I can't see any tx or txexc event.


Thanks in advance

LC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030803/157b6b08/attachment.htm 


From jkmaline  Sun Aug  3 09:18:48 2003
From: jkmaline (Jouni Malinen)
Date: Sun, 3 Aug 2003 09:18:48 -0700
Subject: Tx process
In-Reply-To: <007b01c359d8$14360b40$6401a8c0@netcabo>
References: <007b01c359d8$14360b40$6401a8c0@netcabo>
Message-ID: <20030803161848.GA4661@jm.kir.nu>

On Sun, Aug 03, 2003 at 04:58:05PM +0100, Luisa Caeiro wrote:

> In the driver (according my understand):
>     . prism2_transmit function writes the TX command to Command register
>     . prism2_cmd_ev function is called from prism2_interrupt 
> after a event command generated by the firmware
>     . prism2_interrupt gives the event stat generated by the firmware (I suppose the TX or TXexc after the transmit command) 
>     . according to the event identified calls the correspondig function or schedules the corresponding tasklet (for tx events prism2_tx_ev or prism2_txexc). 
> Is this correct? Do I need to activate some parameter to have this behaviour?
> Because, I'm trying to follow this procedure and after a prism2_transmit call I can't see any tx or txexc event.

Yes, that is correct. Although, I forgot to mention one detail about
this.. Host AP driver does not use TX (OK) event with most frames to
save some CPU time. It is only used for management frames. If you want
to receive TX events for all frames, you will need to add
HFA384X_TX_CTRL_TX_OK to tx_control field. Modifying
HFA384X_TX_CTRL_FLAGS in hostap_hw.c is probably the easiest way of
doing this or you can also OR that flag into local->tx_control.

-- 
Jouni Malinen                                            PGP id EFC895FA



From hostap  Sun Aug  3 09:43:36 2003
From: hostap (Santiago Garcia Mantinan)
Date: Sun, 3 Aug 2003 18:43:36 +0200
Subject: problems with 0.0.4 and gcc-3.2/3.3
In-Reply-To: <20030802025630.GM8799@shot.org>
References: <20030802025630.GM8799@shot.org>
Message-ID: <20030803164336.GA3814@man.beta.es>

> 3.3 shows the attached errors when compiling.  
> when the module loads, the kernel panics and the system becomes unstable.

I'm compiling with gcc 3.3-2 as in Debian unstable right now and it shows
some warnings but compiles ok and works ok, I know that older 2.4 kernels
give compile probles, but 2.4.21 final should be ok, why are you using a
pre3 instead of the final release? Maybe that is your hole problem.

Regards...
-- 
Manty/BestiaTester -> http://manty.net



From mike  Sun Aug  3 10:03:23 2003
From: mike (Michael Guntsche)
Date: Sun, 3 Aug 2003 19:03:23 +0200
Subject: Flaky connection with latest CVS version
Message-ID: <20030803190323.02c69ed1.mike@it-loops.com>

Hi,

I changed from an older CVS-version (~3 weeks old) to a recent one to test 
the new 32bit tallies.
The good news is that I no longer get INFDROP events during larger file transfers,
the bad news is that the connection seems flaky.

AP-Machine:
Netgear MA311 PCI
kernel 2.4.21 + CVS-hostap
master mode

syslog-message:
Aug  3 18:51:06 douglas kernel: wlan0: prism2_tx: short skb (len=0)
Aug  3 18:51:07 douglas kernel: wlan0: sending disassociation info to STA 00:09:5b:3d:1f:9e(last=1693154, jiffies=1723254)
Aug  3 18:51:08 douglas kernel: wlan0: sending deauthentication info to STA 00:09:5b:3d:1f:9e(last=1693154, jiffies=1723354)
Aug  3 18:51:08 douglas kernel: wlan0: Could not find STA 00:09:5b:3d:1f:9e for this TX error (@1723354)
Aug  3 18:51:09 douglas kernel: wlan0: 00:09:5b:3d:1f:9e auth_cb - STA authenticated
Aug  3 18:51:09 douglas kernel: wlan0: 00:09:5b:3d:1f:9e assoc_cb - STA associated

Client-Machine (notebook):
Netgear MA401 pccard
kernel 2.4.22-pre10 (for ACPI) + CVS-hostap
managed mode

syslog-message:
Aug  3 18:51:07 roadrunner kernel: wlan0: LinkStatus=2 (Disconnected)
Aug  3 18:51:07 roadrunner kernel: wlan0: LinkStatus: BSSID=00:09:5b:2f:13:1f
Aug  3 18:51:09 roadrunner kernel: wlan0: LinkStatus=1 (Connected)
Aug  3 18:51:09 roadrunner kernel: wlan0: LinkStatus: BSSID=00:09:5b:2f:13:1f

AFAIK I haven't seen this problem before the 32bit tallies change.
Jouni, do you think that this change is responsible for the errors?

Cheers,
michael





From jkmaline  Sun Aug  3 10:40:15 2003
From: jkmaline (Jouni Malinen)
Date: Sun, 3 Aug 2003 10:40:15 -0700
Subject: Flaky connection with latest CVS version
In-Reply-To: <20030803190323.02c69ed1.mike@it-loops.com>
References: <20030803190323.02c69ed1.mike@it-loops.com>
Message-ID: <20030803174015.GA6507@jm.kir.nu>

On Sun, Aug 03, 2003 at 07:03:23PM +0200, Michael Guntsche wrote:

> I changed from an older CVS-version (~3 weeks old) to a recent one to test 
> the new 32bit tallies.
> The good news is that I no longer get INFDROP events during larger file transfers,
> the bad news is that the connection seems flaky.

How often did the connection get disconnected? Do you notice long
periods of data packets not being sent or just extra re-associations?

> AFAIK I haven't seen this problem before the 32bit tallies change.
> Jouni, do you think that this change is responsible for the errors?

I would find it surprising; these should be unrelated.. Anyway, could
you please test the same new version with 32-bit tallies disabled?
Attached patch should be enough to just change this part and leave
everything else as is.

-- 
Jouni Malinen                                            PGP id EFC895FA
-------------- next part --------------
Index: driver/modules/hostap_hw.c
===================================================================
RCS file: /home/jm/cvsroot/hostap/driver/modules/hostap_hw.c,v
retrieving revision 1.136
diff -u -p -B -4 -r1.136 hostap_hw.c
--- driver/modules/hostap_hw.c	3 Aug 2003 16:45:59 -0000	1.136
+++ driver/modules/hostap_hw.c	3 Aug 2003 17:33:54 -0000
@@ -1016,16 +1016,18 @@ static int prism2_setup_rids(struct net_
 	 * This has been fixed in 0.8.2, so enable 32-bit tallies only
 	 * beginning with that firmware version. Another bug fix for 32-bit
 	 * tallies in 1.4.0; should 16-bit tallies be used for some other
 	 * versions, too? */
+#if 0
 	if (local->sta_fw_ver >= PRISM2_FW_VER(0,8,2)) {
 		if (hostap_set_word(dev, HFA384X_RID_CNFTHIRTY2TALLY, 1)) {
 			printk(KERN_INFO "%s: cnfThirty2Tally setting "
 			       "failed\n", dev->name);
 			local->tallies32 = 0;
 		} else
 			local->tallies32 = 1;
 	} else
+#endif
 		local->tallies32 = 0;
 
 	if (local->ap &&
 	    hostap_set_word(dev, HFA384X_RID_CNFAUTHENTICATION,


From jkmaline  Sun Aug  3 10:48:21 2003
From: jkmaline (Jouni Malinen)
Date: Sun, 3 Aug 2003 10:48:21 -0700
Subject: problems with 0.0.4 and gcc-3.2/3.3
In-Reply-To: <20030802025630.GM8799@shot.org>
References: <20030802025630.GM8799@shot.org>
Message-ID: <20030803174821.GB6507@jm.kir.nu>

On Fri, Aug 01, 2003 at 10:56:30PM -0400, Francois Gurin wrote:

> I've been working on 0.0.4 for a few days now and have encountered 
> problems compiling hostap with gcc 3.2 and 3.3.  When i use 2.95 
> everything works as expected.
> I had thought 3.2 was working fine until fairly recently.

Did you compile your kernel with the exact same gcc version? I have been
using gcc v3.2.3 without any problems.

> 3.3 shows the attached errors when compiling.  
> when the module loads, the kernel panics and the system becomes unstable.

gcc 3.3 is quite new and it might have issues compiling Linux kernel.
All the warning messages seemed to have been from kernel headers, not
from Host AP code. I would tend to not care about gcc 3.3 yet unless you
can report that everything else is working fine in your kernel (i.e.,
everything compiled with gcc 3.3) and it is only Host AP driver that
shows issues.

> Unable to handle kernel NULL pointer dereference at virtual address 00000000
>  printing eip:
> c0114462
> *pde = 00000000
> Oops: 0002
> CPU:    0
> EIP:    0010:[<c0114462>]    Not tainted

Please always try to resolve addresses in kernel oops messages with
ksymoops. See Linux kernel Documentation/oops-tracing.txt for more
details. Without this, the oops messages are usually quite useless.

-- 
Jouni Malinen                                            PGP id EFC895FA



From mike  Sun Aug  3 11:15:12 2003
From: mike (Michael Guntsche)
Date: Sun, 3 Aug 2003 20:15:12 +0200
Subject: Flaky connection with latest CVS version
In-Reply-To: <20030803174015.GA6507@jm.kir.nu>
References: <20030803190323.02c69ed1.mike@it-loops.com>
	<20030803174015.GA6507@jm.kir.nu>
Message-ID: <20030803201512.6305d917.mike@it-loops.com>

On Sun, 3 Aug 2003 10:40:15 -0700
Jouni Malinen <jkmaline at cc.hut.fi> wrote:

> How often did the connection get disconnected? Do you notice long
> periods of data packets not being sent or just extra re-associations?

Looking through my syslog it seems that those re-associations only happen
while the system is idling (no network traffic at all)
For testing purposes I left the notebook running this afternoon
without doing anything.
I noticed that the master machine started dropping and re-associating the notebook
in a pattern.
5 minutes connection,re-associate, 10 minutes con, re-associate, 5 min, re, 10 min......
Yeah, I know what you think right now Jouni. WTF????????????? ;)

> I would find it surprising; these should be unrelated.. Anyway, could
> you please test the same new version with 32-bit tallies disabled?
> Attached patch should be enough to just change this part and leave
> everything else as is.
I patched my AP and notebook and start idling after sending this mail.


Mike



From joshk  Sun Aug  3 11:26:25 2003
From: joshk (Joshua Kwan)
Date: Sun, 3 Aug 2003 11:26:25 -0700
Subject: Weird badness in 2.6.0-test2
Message-ID: <20030803182625.GA11226@nasledov.com>

Hi,

Attached is a log of some oops I received when shutting down my laptop
using HostAP kernel modules for my wireless card in kernel
2.6.0-test2-mm2. Is this a known problem?

Thanks,
Josh
-------------- next part --------------
kobject 'statistics' does not have a release() function, it is broken and must be fixed.
Badness in kobject_cleanup at lib/kobject.c:402
Call Trace:
 [kobject_cleanup+95/133] kobject_cleanup+0x5f/0x85
 [netdev_unregister_sysfs+57/59] netdev_unregister_sysfs+0x39/0x3b
 [netdev_run_todo+262/366] netdev_run_todo+0x106/0x16e
 [_end+307373442/1069392712] prism2_free_local_data+0x320/0x3c6 [hostap_cs]
 [_end+307374510/1069392712] prism2_detach+0x81/0x11c [hostap_cs]
 [_end+307374381/1069392712] prism2_detach+0x0/0x11c [hostap_cs]
 [unbind_request+200/212] unbind_request+0xc8/0xd4
 [ds_ioctl+967/1658] ds_ioctl+0x3c7/0x67a
 [unix_dgram_sendmsg+1132/1366] unix_dgram_sendmsg+0x46c/0x556
 [journal_dirty_metadata+327/519] journal_dirty_metadata+0x147/0x207
 [buffered_rmqueue+214/386] buffered_rmqueue+0xd6/0x182
 [sock_sendmsg+195/222] sock_sendmsg+0xc3/0xde
 [__ext3_journal_stop+36/80] __ext3_journal_stop+0x24/0x50
 [do_anonymous_page+307/548] do_anonymous_page+0x133/0x224
 [autoremove_wake_function+0/79] autoremove_wake_function+0x0/0x4f
 [schedule+645/1272] schedule+0x285/0x4f8
 [zap_pte_range+327/380] zap_pte_range+0x147/0x17c
 [default_wake_function+0/46] default_wake_function+0x0/0x2e
 [zap_pmd_range+71/97] zap_pmd_range+0x47/0x61
 [unmap_page_range+67/105] unmap_page_range+0x43/0x69
 [unmap_vmas+220/521] unmap_vmas+0xdc/0x209
 [unmap_region+155/222] unmap_region+0x9b/0xde
 [unmap_vma+64/125] unmap_vma+0x40/0x7d
 [unmap_vma_list+28/40] unmap_vma_list+0x1c/0x28
 [do_munmap+326/387] do_munmap+0x146/0x183
 [ds_ioctl+0/1658] ds_ioctl+0x0/0x67a
 [sys_ioctl+253/626] sys_ioctl+0xfd/0x272
 [sys_munmap+68/100] sys_munmap+0x44/0x64
 [syscall_call+7/11] syscall_call+0x7/0xb

Device class 'wlan0' does not have a release() function, it is broken and must be fixed.
Badness in class_dev_release at drivers/base/class.c:201
Call Trace:
 [kobject_cleanup+131/133] kobject_cleanup+0x83/0x85
 [class_device_unregister+19/35] class_device_unregister+0x13/0x23
 [netdev_run_todo+262/366] netdev_run_todo+0x106/0x16e
 [_end+307373442/1069392712] prism2_free_local_data+0x320/0x3c6 [hostap_cs]
 [_end+307374510/1069392712] prism2_detach+0x81/0x11c [hostap_cs]
 [_end+307374381/1069392712] prism2_detach+0x0/0x11c [hostap_cs]
 [unbind_request+200/212] unbind_request+0xc8/0xd4
 [ds_ioctl+967/1658] ds_ioctl+0x3c7/0x67a
 [unix_dgram_sendmsg+1132/1366] unix_dgram_sendmsg+0x46c/0x556
 [journal_dirty_metadata+327/519] journal_dirty_metadata+0x147/0x207
 [buffered_rmqueue+214/386] buffered_rmqueue+0xd6/0x182
 [sock_sendmsg+195/222] sock_sendmsg+0xc3/0xde
 [__ext3_journal_stop+36/80] __ext3_journal_stop+0x24/0x50
 [do_anonymous_page+307/548] do_anonymous_page+0x133/0x224
 [autoremove_wake_function+0/79] autoremove_wake_function+0x0/0x4f
 [schedule+645/1272] schedule+0x285/0x4f8
 [zap_pte_range+327/380] zap_pte_range+0x147/0x17c
 [default_wake_function+0/46] default_wake_function+0x0/0x2e
 [zap_pmd_range+71/97] zap_pmd_range+0x47/0x61
 [unmap_page_range+67/105] unmap_page_range+0x43/0x69
 [unmap_vmas+220/521] unmap_vmas+0xdc/0x209
 [unmap_region+155/222] unmap_region+0x9b/0xde
 [unmap_vma+64/125] unmap_vma+0x40/0x7d
 [unmap_vma_list+28/40] unmap_vma_list+0x1c/0x28
 [do_munmap+326/387] do_munmap+0x146/0x183
 [ds_ioctl+0/1658] ds_ioctl+0x0/0x67a
 [sys_ioctl+253/626] sys_ioctl+0xfd/0x272
 [sys_munmap+68/100] sys_munmap+0x44/0x64
 [syscall_call+7/11] syscall_call+0x7/0xb

kobject 'class_obj' does not have a release() function, it is broken and must be fixed.
Badness in kobject_cleanup at lib/kobject.c:402
Call Trace:
 [kobject_cleanup+95/133] kobject_cleanup+0x5f/0x85
 [netdev_run_todo+262/366] netdev_run_todo+0x106/0x16e
 [_end+307373442/1069392712] prism2_free_local_data+0x320/0x3c6 [hostap_cs]
 [_end+307374510/1069392712] prism2_detach+0x81/0x11c [hostap_cs]
 [_end+307374381/1069392712] prism2_detach+0x0/0x11c [hostap_cs]
 [unbind_request+200/212] unbind_request+0xc8/0xd4
 [ds_ioctl+967/1658] ds_ioctl+0x3c7/0x67a
 [unix_dgram_sendmsg+1132/1366] unix_dgram_sendmsg+0x46c/0x556
 [journal_dirty_metadata+327/519] journal_dirty_metadata+0x147/0x207
 [buffered_rmqueue+214/386] buffered_rmqueue+0xd6/0x182
 [sock_sendmsg+195/222] sock_sendmsg+0xc3/0xde
 [__ext3_journal_stop+36/80] __ext3_journal_stop+0x24/0x50
 [do_anonymous_page+307/548] do_anonymous_page+0x133/0x224
 [autoremove_wake_function+0/79] autoremove_wake_function+0x0/0x4f
 [schedule+645/1272] schedule+0x285/0x4f8
 [zap_pte_range+327/380] zap_pte_range+0x147/0x17c
 [default_wake_function+0/46] default_wake_function+0x0/0x2e
 [zap_pmd_range+71/97] zap_pmd_range+0x47/0x61
 [unmap_page_range+67/105] unmap_page_range+0x43/0x69
 [unmap_vmas+220/521] unmap_vmas+0xdc/0x209
 [unmap_region+155/222] unmap_region+0x9b/0xde
 [unmap_vma+64/125] unmap_vma+0x40/0x7d
 [unmap_vma_list+28/40] unmap_vma_list+0x1c/0x28
 [do_munmap+326/387] do_munmap+0x146/0x183
 [ds_ioctl+0/1658] ds_ioctl+0x0/0x67a
 [sys_ioctl+253/626] sys_ioctl+0xfd/0x272
 [sys_munmap+68/100] sys_munmap+0x44/0x64
 [syscall_call+7/11] syscall_call+0x7/0xb

hostap_cs: Netdevice wlan0 unregistered



From lists  Sun Aug  3 11:42:14 2003
From: lists (Daves Lists)
Date: Sun, 03 Aug 2003 14:42:14 -0400
Subject: Unresolved Symbols
Message-ID: <E19jNo6-0000pw-00@Miroku.super-serv.com>

I tried to upgrade to 0.0.4 from 0.0.3 but am getting unresolved symbols 
when trying to load the module. I'm using the same kernel(2.4.18) and 
pcmcia-cs(3.2.4) as before. The unresolved symbol is yield which I also get 
the following compiler warning in hostap_cs.c. 

In file included from hostap_cs.c:203:
hostap_hw.c: In function 'hfa384x_allocate_fid':
hostap_hw.c:801: warning: implicit declatarion of function 'yield' 

Any clues?? 

Thanks,
Dave



From jkmaline  Sun Aug  3 11:56:52 2003
From: jkmaline (Jouni Malinen)
Date: Sun, 3 Aug 2003 11:56:52 -0700
Subject: Unresolved Symbols
In-Reply-To: <E19jNo6-0000pw-00@Miroku.super-serv.com>
References: <E19jNo6-0000pw-00@Miroku.super-serv.com>
Message-ID: <20030803185652.GA3650@jm.kir.nu>

On Sun, Aug 03, 2003 at 02:42:14PM -0400, Daves Lists wrote:

> I tried to upgrade to 0.0.4 from 0.0.3 but am getting unresolved symbols 
> when trying to load the module. I'm using the same kernel(2.4.18) and 
> pcmcia-cs(3.2.4) as before. The unresolved symbol is yield which I also get 
> the following compiler warning in hostap_cs.c. 

Read mailing list archives, move '#define yield() schedule' in
hostap_compat.h, or update to the latest CVS snapshot.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Aug  3 12:02:30 2003
From: jkmaline (Jouni Malinen)
Date: Sun, 3 Aug 2003 12:02:30 -0700
Subject: Flaky connection with latest CVS version
In-Reply-To: <20030803201512.6305d917.mike@it-loops.com>
References: <20030803190323.02c69ed1.mike@it-loops.com>
	<20030803174015.GA6507@jm.kir.nu> <20030803201512.6305d917.mike@it-loops.com>
Message-ID: <20030803190230.GB3650@jm.kir.nu>

On Sun, Aug 03, 2003 at 08:15:12PM +0200, Michael Guntsche wrote:

> Looking through my syslog it seems that those re-associations only happen
> while the system is idling (no network traffic at all)
> For testing purposes I left the notebook running this afternoon
> without doing anything.
> I noticed that the master machine started dropping and re-associating the notebook
> in a pattern.
> 5 minutes connection,re-associate, 10 minutes con, re-associate, 5 min, re, 10 min......

Host AP verifies STA activity every five minutes by sending a poll frame
to the STA. If STA does not reply, it will be disassociated. It looks
like this verification is not working in your setup. Which station
firmware version are you using? Are you using hostapd or only kernel
driver for 802.11 management?

-- 
Jouni Malinen                                            PGP id EFC895FA



From gbritton  Sun Aug  3 12:18:27 2003
From: gbritton (Gerald Britton)
Date: Sun, 3 Aug 2003 15:18:27 -0400
Subject: Flaky connection with latest CVS version
In-Reply-To: <20030803190230.GB3650@jm.kir.nu>
References: <20030803190323.02c69ed1.mike@it-loops.com>
	<20030803174015.GA6507@jm.kir.nu> <20030803201512.6305d917.mike@it-loops.com>
	<20030803190230.GB3650@jm.kir.nu>
Message-ID: <20030803191827.GA30290@fog.sekrit.org>

On Sun, Aug 03, 2003 at 12:02:30PM -0700, Jouni Malinen wrote:
> Host AP verifies STA activity every five minutes by sending a poll frame
> to the STA. If STA does not reply, it will be disassociated. It looks

Would it be possible to have this only done if the station is idle for five
minutes and have active network use count as "STA activity" perhaps?

				-- Gerald



From mike  Sun Aug  3 12:30:54 2003
From: mike (Michael Guntsche)
Date: Sun, 3 Aug 2003 21:30:54 +0200
Subject: Flaky connection with latest CVS version
In-Reply-To: <20030803190230.GB3650@jm.kir.nu>
References: <20030803190323.02c69ed1.mike@it-loops.com>
	<20030803174015.GA6507@jm.kir.nu>
	<20030803201512.6305d917.mike@it-loops.com>
	<20030803190230.GB3650@jm.kir.nu>
Message-ID: <20030803213054.141badc2.mike@it-loops.com>

Jouni,

> Host AP verifies STA activity every five minutes by sending a poll frame
> to the STA. If STA does not reply, it will be disassociated. It looks
> like this verification is not working in your setup. Which station
> firmware version are you using? Are you using hostapd or only kernel
> driver for 802.11 management?

I am using volatile PRI 1.1.4 + volatile STA 1.7.4 thanks to the latest changes in CVS,
and kernel driver 802.11 management.

I did further tests and I think I found out whats causing the problem.
It is related to power management.

If I enable power management on the PCCARD (my default set-up) via 

	iwconfig power timeout 3

(No PM on the AP-Machine)

and let the connection idle for some time, I get the re-association.
I cannot reproduce the behaviour if I disable power management with

	iwconfig power off

Since you said that hostap is sending a poll frame every 5 minutes I think the following is happening.

1.) PCCARD goes to "sleep" after three seconds.
2.) My AP sends a poll after 5 minutes
3.) For some reason the PCCARD is not answering and the AP kicks it out, sending a message.
4.) PCCARD wakes up and re-associates itself.

Could this be the problem?


Cheers,
Mike







From jkmaline  Sun Aug  3 12:48:06 2003
From: jkmaline (Jouni Malinen)
Date: Sun, 3 Aug 2003 12:48:06 -0700
Subject: Flaky connection with latest CVS version
In-Reply-To: <20030803191827.GA30290@fog.sekrit.org>
References: <20030803190323.02c69ed1.mike@it-loops.com>
	<20030803174015.GA6507@jm.kir.nu> <20030803201512.6305d917.mike@it-loops.com>
	<20030803190230.GB3650@jm.kir.nu> <20030803191827.GA30290@fog.sekrit.org>
Message-ID: <20030803194806.GA4404@jm.kir.nu>

On Sun, Aug 03, 2003 at 03:18:27PM -0400, Gerald Britton wrote:

> Would it be possible to have this only done if the station is idle for five
> minutes and have active network use count as "STA activity" perhaps?

Yes, that is exactly the way it is done in the current implementation.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Aug  3 13:46:46 2003
From: jkmaline (Jouni Malinen)
Date: Sun, 3 Aug 2003 13:46:46 -0700
Subject: Flaky connection with latest CVS version
In-Reply-To: <20030803213054.141badc2.mike@it-loops.com>
References: <20030803190323.02c69ed1.mike@it-loops.com>
	<20030803174015.GA6507@jm.kir.nu> <20030803201512.6305d917.mike@it-loops.com>
	<20030803190230.GB3650@jm.kir.nu> <20030803213054.141badc2.mike@it-loops.com>
Message-ID: <20030803204646.GA7635@jm.kir.nu>

On Sun, Aug 03, 2003 at 09:30:54PM +0200, Michael Guntsche wrote:

> I did further tests and I think I found out whats causing the problem.
> It is related to power management.

Yes, indeed. Host AP driver was unable to send buffered inactivity poll
frame when hostapd was not used. Thus, all idle power saving STAs
appeared to not answer polls and they were disassociated. This is now
fixed in CVS.

-- 
Jouni Malinen                                            PGP id EFC895FA



From mike  Sun Aug  3 14:14:35 2003
From: mike (Michael Guntsche)
Date: Sun, 3 Aug 2003 23:14:35 +0200
Subject: Flaky connection with latest CVS version
In-Reply-To: <20030803204646.GA7635@jm.kir.nu>
References: <20030803190323.02c69ed1.mike@it-loops.com>
	<20030803174015.GA6507@jm.kir.nu>
	<20030803201512.6305d917.mike@it-loops.com>
	<20030803190230.GB3650@jm.kir.nu>
	<20030803213054.141badc2.mike@it-loops.com>
	<20030803204646.GA7635@jm.kir.nu>
Message-ID: <20030803231435.30c940da.mike@it-loops.com>

On Sun, 3 Aug 2003 13:46:46 -0700
Jouni Malinen <jkmaline at cc.hut.fi> wrote:

> Yes, indeed. Host AP driver was unable to send buffered inactivity poll
> frame when hostapd was not used. Thus, all idle power saving STAs
> appeared to not answer polls and they were disassociated. This is now
> fixed in CVS.
> 

Just tested it with my setup and latest CVS. No problems so far.
Thanks a lot Jouni.

Michael



From alexh  Sun Aug  3 15:44:30 2003
From: alexh (Alexander Hoogerhuis)
Date: 04 Aug 2003 00:44:30 +0200
Subject: Weird badness in 2.6.0-test2
In-Reply-To: <20030803182625.GA11226@nasledov.com>
References: <20030803182625.GA11226@nasledov.com>
Message-ID: <873cgigy41.fsf@lapper.ihatent.com>

A non-text attachment was scrubbed...
Name: .config
Type: application/octet-stream
Size: 34651 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20030804/3d2f398f/attachment.obj 


From gbritton  Sun Aug  3 14:46:09 2003
From: gbritton (Gerald Britton)
Date: Sun, 3 Aug 2003 17:46:09 -0400
Subject: Flaky connection with latest CVS version
In-Reply-To: <20030803194806.GA4404@jm.kir.nu>
References: <20030803190323.02c69ed1.mike@it-loops.com>
	<20030803174015.GA6507@jm.kir.nu> <20030803201512.6305d917.mike@it-loops.com>
	<20030803190230.GB3650@jm.kir.nu> <20030803191827.GA30290@fog.sekrit.org>
	<20030803194806.GA4404@jm.kir.nu>
Message-ID: <20030803214609.GB30290@fog.sekrit.org>

On Sun, Aug 03, 2003 at 12:48:06PM -0700, Jouni Malinen wrote:
> On Sun, Aug 03, 2003 at 03:18:27PM -0400, Gerald Britton wrote:
> 
> > Would it be possible to have this only done if the station is idle for five
> > minutes and have active network use count as "STA activity" perhaps?
> 
> Yes, that is exactly the way it is done in the current implementation.

Doh.  i should have read the initial message about it only happening when
idle :P

				-- Gerald



From eduardo  Sun Aug  3 16:15:09 2003
From: eduardo (Eduardo Kaftanski)
Date: Sun, 3 Aug 2003 19:15:09 -0400
Subject: SMP report
Message-ID: <20030803231509.GA1560@enriqueto.nn.cl>


	I upgraded from kernel 2.4.18 to 2.4.20-19.8 (redhat 8.0) and
from hostap 0.0.3 to hostap 0.0.4. I first run uniprocesor for 24 hours
to test stability (perfect so far) and know rebboted with the smp 
kernel.

	Its running, has not lock up in hal an hour, but this messages are
coming on the console:

wlan0wds0: driver bug - prism2_transmit() called when previous TX was pending
wlan0wds0: prism2_tx - to BAP0 failed
wlan0: scheduled card reset
hostap_pci: wlan0: resetting card
prism2_hw_init()
prism2_hw_init: initialized in 210 ms
wlan0: trying to read PDA from 0x007f0000: OK
wlan0: STA 00:06:25:25:2b:59 TX rate lowered to 55

So far twice. Low traffic.


-- 
Eduardo Kaftanski
eduardo at linuxcenter.cl
Red Hat Certified Engineer
Gerente Ingenieria LinuxCenter S.A.
Canada 239 5to Piso, Providencia, Stgo de Chile.
http://www.linuxcenter.cl 2745000



From eduardo  Sun Aug  3 17:23:59 2003
From: eduardo (Eduardo Kaftanski)
Date: Sun, 3 Aug 2003 20:23:59 -0400
Subject: SMP report
In-Reply-To: <20030803231509.GA1560@enriqueto.nn.cl>
References: <20030803231509.GA1560@enriqueto.nn.cl>
Message-ID: <20030804002359.GA1561@enriqueto.nn.cl>

> 
> 	Its running, has not lock up in hal an hour, but this messages are
> coming on the console:
> 

after another reset, it stopped transmiting and receiving. Machine
did NOT lock up. The one other station online was a WDS bridge. Maybe
the reset reverted the card to 1.4.9?


-- 
Eduardo Kaftanski
eduardo at linuxcenter.cl
Red Hat Certified Engineer
Gerente Ingenieria LinuxCenter S.A.
Canada 239 5to Piso, Providencia, Stgo de Chile.
http://www.linuxcenter.cl 2745000



From proski  Sun Aug  3 20:20:24 2003
From: proski (Pavel Roskin)
Date: Sun, 03 Aug 2003 23:20:24 -0400 (EDT)
Subject: SMP report
In-Reply-To: <20030804002359.GA1561@enriqueto.nn.cl>
Message-ID: <Pine.LNX.4.44.0308032315350.792-100000@portland.hansa.lan>

On Sun, 3 Aug 2003, Eduardo Kaftanski wrote:

> > 	Its running, has not lock up in hal an hour, but this messages are
> > coming on the console:
> >
>
> after another reset, it stopped transmiting and receiving. Machine
> did NOT lock up. The one other station online was a WDS bridge. Maybe
> the reset reverted the card to 1.4.9?

Yes, I think so.  prism2_hw_init() is a very hard reset.

In case you missed it, you can flash firmware 1.5.6 to Prism 2 cards now.
Get s1010506.hex from
http://www.red-bean.com/~proski/firmware/1.5.6.tar.gz

-- 
Regards,
Pavel Roskin





From proski  Sun Aug  3 20:43:21 2003
From: proski (Pavel Roskin)
Date: Sun, 03 Aug 2003 23:43:21 -0400 (EDT)
Subject: problems with 0.0.4 and gcc-3.2/3.3
In-Reply-To: <20030803174821.GB6507@jm.kir.nu>
Message-ID: <Pine.LNX.4.44.0308032337240.792-100000@portland.hansa.lan>

On Sun, 3 Aug 2003, Jouni Malinen wrote:

> > 3.3 shows the attached errors when compiling.
> > when the module loads, the kernel panics and the system becomes unstable.
>
> gcc 3.3 is quite new and it might have issues compiling Linux kernel.

Just for the record, I'm running Linux 2.6.0-test2 compiled by "3.3.1
20030626 (Debian prerelease)" from Debian testing.  I'm not aware of any
compiler related problems.  I can also compile CVS HostAP without
warnings, and of course it's working for me.

gcc 3.3 may be new and may have problems with 2.4 kernels, but it appears
that HostAP per se is doing just fine with gcc 3.3.

-- 
Regards,
Pavel Roskin



From proski  Sun Aug  3 20:48:58 2003
From: proski (Pavel Roskin)
Date: Sun, 03 Aug 2003 23:48:58 -0400 (EDT)
Subject: [PATCH] Kernel panic in hostap_pci
In-Reply-To: <20030803111505.GA23197@orion.toppoint.de>
Message-ID: <Pine.LNX.4.44.0308032345550.792-100000@portland.hansa.lan>

On Sun, 3 Aug 2003, Wilfried Klaebe wrote:

> I played around a little and found out that it is now possible to
> ram-download primary firmware in genesis mode, and then secondary
> firmware on top of that, and it all works perfectly! Just
>
> prism2_srec -g wlan0 ak010104.hex
> prism2_srec -r wlan0 rf010704.hex
>
> and done...

But wouldn't it be nice to do it in one command?  Maybe prism2_srec could
interpret "-g" like "-r" for STA firmware?

-- 
Regards,
Pavel Roskin



From jkmaline  Sun Aug  3 21:55:13 2003
From: jkmaline (Jouni Malinen)
Date: Sun, 3 Aug 2003 21:55:13 -0700
Subject: [PATCH] Kernel panic in hostap_pci
In-Reply-To: <Pine.LNX.4.44.0308032345550.792-100000@portland.hansa.lan>
References: <20030803111505.GA23197@orion.toppoint.de>
	<Pine.LNX.4.44.0308032345550.792-100000@portland.hansa.lan>
Message-ID: <20030804045513.GE5010@jm.kir.nu>

On Sun, Aug 03, 2003 at 11:48:58PM -0400, Pavel Roskin wrote:

> > prism2_srec -g wlan0 ak010104.hex
> > prism2_srec -r wlan0 rf010704.hex

> But wouldn't it be nice to do it in one command?  Maybe prism2_srec could
> interpret "-g" like "-r" for STA firmware?

What's the benefit of doing this in one command? Those images cannot be
merged in the same way as in non-volatile download of PRI and STA
firmwares. I will not change the device driver for this and even
modifying prism2_srec to perform two download ioctl()s sounds
unneccessary.

If you need one command, what about:

#!/bin/sh
prism2_srec -g $1 $2 &&
prism2_srec -r $1 $3

;-)

-- 
Jouni Malinen                                            PGP id EFC895FA



From eduardo  Mon Aug  4 07:10:55 2003
From: eduardo (Eduardo Kaftanski)
Date: Mon, 4 Aug 2003 10:10:55 -0400
Subject: SMP report
In-Reply-To: <Pine.LNX.4.44.0308032315350.792-100000@portland.hansa.lan>
References: <20030804002359.GA1561@enriqueto.nn.cl>
	<Pine.LNX.4.44.0308032315350.792-100000@portland.hansa.lan>
Message-ID: <20030804141055.GA10653@enriqueto.nn.cl>

> 
> In case you missed it, you can flash firmware 1.5.6 to Prism 2 cards now.
> Get s1010506.hex from
> http://www.red-bean.com/~proski/firmware/1.5.6.tar.gz
> 

Downloaded... I have  DLINK DWL520. Will this work with that card?
Should I upgrade to latest CVS ar 0.0.4 is enough?

thanks.

-- 
Eduardo Kaftanski
eduardo at linuxcenter.cl
Red Hat Certified Engineer
Gerente Ingenieria LinuxCenter S.A.
Canada 239 5to Piso, Providencia, Stgo de Chile.
http://www.linuxcenter.cl 2745000



From vicente.paredes  Mon Aug  4 07:22:59 2003
From: vicente.paredes (Vicente Paredes)
Date: Mon, 4 Aug 2003 09:22:59 -0500 (CDT)
Subject: prism cards
Message-ID:      <1081.200.63.198.49.1060006979.squirrel@webmail.linuxpowered.org>

Hello

I have been looking for prism based wireless cards, but i havent find
them. Actually exists card with this chip?

Please tell me because all i have found are new versions of the cards
which dont use this chip.

Plese help me, or tell me if exist another option like a gateway for
example with other cards.

Thanks in advance

-- 
Atentamente

Vicente Paredes
Departamento de ?ngenier?a
GRUEIN Cia. Ltda.
PBX 593-42690888
CEL 593-98412868



From markus.baumeister  Mon Aug  4 08:10:15 2003
From: markus.baumeister (markus.baumeister at philips.com)
Date: Mon, 4 Aug 2003 17:10:15 +0200
Subject: Modulation rate for broadcast packets
Message-ID: <OF45F6E4C5.4432CCC4-ONC1256D78.0052D756-C1256D78.00533A7B@diamond.philips.com>

Hello,

I'm wondering at which modulation rate broadcast frames are sent by the AP 
so that all stations have a chance to receive them. Is that rate 
user-configurable or maybe even self-adjusting (e.g. using the lowest 
modulation rate of all associated stations would be nice)?

Kind regards
        Markus Baumeister



From jzh  Mon Aug  4 08:44:27 2003
From: jzh (Jay Zhang)
Date: Mon, 04 Aug 2003 10:44:27 -0500
Subject: prism cards
In-Reply-To: <1081.200.63.198.49.1060006979.squirrel@webmail.linuxpowered.org>
References: <1081.200.63.198.49.1060006979.squirrel@webmail.linuxpowered.org>
Message-ID: <3F2E7F5B.806@yifan.net>

Prism based cards are hard to find now.

Helpful information about chip set:
http://www.linux-wlan.org/docs/wlan_adapters.html4.html

and don't buy anything mentioned in
http://www.wireless.org.au/~jhecker/atmeldrv/usbtable.html
Those are all Atmel based cards.

In addition, I confirm that Belkin F5D6050 USB is Atmel based now
And Netgear MA 111 USB is not Prism based anymore. I don't recommend 
Hawking cards neither as they never reply tech support requests.

I settled down with EnGenius/senoao EL-2511 UB card as I was looking for 
USB cards. I believe the 2511 PCMCIA version is also still prism based. 
And EnGenius is well know for its better range and sensitivity.

Search "engenius 2511" at shopping.yahoo.com will give you a good list 
of them.

Good luck

Jay.

Vicente Paredes wrote:
> Hello
> 
> I have been looking for prism based wireless cards, but i havent find
> them. Actually exists card with this chip?
> 
> Please tell me because all i have found are new versions of the cards
> which dont use this chip.
> 
> Plese help me, or tell me if exist another option like a gateway for
> example with other cards.
> 
> Thanks in advance
> 




From mrcool  Mon Aug  4 09:16:42 2003
From: mrcool (Jerry)
Date: Mon, 4 Aug 2003 11:16:42 -0500
Subject: Signal Strength...
Message-ID: <000a01c35aa3$cacce2e0$1e04000a@ns>

In a previous post, i was hoping to get some input as to what the rest of you were seeing in the wild as to how signal strength varies from day to day.  For example, Friday morning, i couldnt go anywhere. Signal strength appeared normal, but would not do anything, Aparently was dropping most packets.

By Friday evening, was working normal.  And over the weekend, worked better than ever, with signal strength higher than normal, and decent bandwidth (3 times avg).  Then again this morning (monday) is back to useless, with avg signal strength, but extreme packet loss (68% loss on a ping test this morning).  

Friday morning i reset the computer that is my router (reboot hostap machine), this didnt do any good at the time.  Has anyone else seen this kind of fluctuation?  (does anyone else care?) 

On topic question... is there a way to poll the card for the current image in use?  The reason i ask is: I wonder if the card is resetting itself then reverting back to original image (i ram upload 1.5.6 over 1.4.9), perhaps this has something to do with it.   Also, how "accurate" is the signal strength value returned with iwconfig?  As mine always seems to return the same value most every time... (32/92) <-- how would one interpret this value? 32 of 92 possible (or 1/3, roughly, signal?)  

Thanks

Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030804/1307fe80/attachment.htm 


From proski  Mon Aug  4 09:37:54 2003
From: proski (Pavel Roskin)
Date: Mon, 4 Aug 2003 12:37:54 -0400 (EDT)
Subject: [PATCH] Kernel panic in hostap_pci
In-Reply-To: <20030804045513.GE5010@jm.kir.nu>
References: <20030803111505.GA23197@orion.toppoint.de>
 <Pine.LNX.4.44.0308032345550.792-100000@portland.hansa.lan>
 <20030804045513.GE5010@jm.kir.nu>
Message-ID: <Pine.LNX.4.56.0308041233001.4517@marabou.research.att.com>

On Sun, 3 Aug 2003, Jouni Malinen wrote:

> On Sun, Aug 03, 2003 at 11:48:58PM -0400, Pavel Roskin wrote:
>
> > > prism2_srec -g wlan0 ak010104.hex
> > > prism2_srec -r wlan0 rf010704.hex
>
> > But wouldn't it be nice to do it in one command?  Maybe prism2_srec could
> > interpret "-g" like "-r" for STA firmware?
>
> What's the benefit of doing this in one command?

I just know that some people will try :-)

But if there are reasons why it cannot be done in one operation, let's
leave it as is and avoid adding kludges.  Thank you for your explanation.

-- 
Regards,
Pavel Roskin



From proski  Mon Aug  4 09:42:03 2003
From: proski (Pavel Roskin)
Date: Mon, 4 Aug 2003 12:42:03 -0400 (EDT)
Subject: SMP report
In-Reply-To: <20030804141055.GA10653@enriqueto.nn.cl>
References: <20030804002359.GA1561@enriqueto.nn.cl>
 <Pine.LNX.4.44.0308032315350.792-100000@portland.hansa.lan>
 <20030804141055.GA10653@enriqueto.nn.cl>
Message-ID: <Pine.LNX.4.56.0308041239410.4517@marabou.research.att.com>

On Mon, 4 Aug 2003, Eduardo Kaftanski wrote:

> > In case you missed it, you can flash firmware 1.5.6 to Prism 2 cards
> > now. Get s1010506.hex from
> > http://www.red-bean.com/~proski/firmware/1.5.6.tar.gz
>
> Downloaded... I have  DLINK DWL520. Will this work with that card?
> Should I upgrade to latest CVS ar 0.0.4 is enough?

Then you can update to 1.7.4 firmware, but you may need to update primary
firmware as well.  If you want to update primary firmware with
prism2_srec, you should upgrade to the CVS version.  See the list archives
for details.

-- 
Regards,
Pavel Roskin



From proski  Mon Aug  4 09:56:36 2003
From: proski (Pavel Roskin)
Date: Mon, 4 Aug 2003 12:56:36 -0400 (EDT)
Subject: [PATCH] PLX genesis mode support
In-Reply-To: <20030803155653.GB3426@jm.kir.nu>
References: <Pine.LNX.4.44.0308030422530.2797-200000@portland.hansa.lan>
 <20030803155653.GB3426@jm.kir.nu>
Message-ID: <Pine.LNX.4.56.0308041249550.5173@marabou.research.att.com>

On Sun, 3 Aug 2003, Jouni Malinen wrote:

> On Sun, Aug 03, 2003 at 04:43:19AM -0400, Pavel Roskin wrote:
>
> > This patch enables genesis mode support on cards using PLX and TMD
> > adapters.  I cannot test it on my PLX board until Monday, but I'm 80%
> > confident that it would work.  The patch should be safe to apply - it
> > doesn't affect existing functionality.
>
> Thanks, applied.

I confirm that it works for me.  Linux 2.6.0-test1, SMC2602W bridge
(plx9052 based), no-name engineering sample with Prism 2.5 chipset, CVS
HostAP.

-- 
Regards,
Pavel Roskin



From eharris  Mon Aug  4 10:05:06 2003
From: eharris (Evan Harris)
Date: Mon, 4 Aug 2003 12:05:06 -0500 (CDT)
Subject: hostap on Senao 2511 wireless cards
Message-ID: <Pine.LNX.4.44.0308041200520.10026-100000@kinison.puremagic.com>


For the rest of the list's benefit, this seems to have corrected the
problem.

Anyone know why the irq_mode=0 setting is necessary for these PCI/Cardbus
bridge cards to work properly?  Can this be added to the FAQ?

Evan


On Sun, 3 Aug 2003, Robert Davidson wrote:

> Evan Harris wrote:
> > While we've been running wlan-ng for quite a while in other machines, after
> > I had problems setting up hostap in the new machine, I tried the wlan-ng
> > stuff on the same machine/same PCI card just to test it wasn't a problem
> > with the pci bridge.  Wlan-ng loads and initializes the card just fine using
> > the bridge, but hostap gives all those errors.  I tried changing the port
> > and interrupt being used with pcmcia-cs in case that might be the cause, all
> > to no effect.  wlan-ng still works, and hostap doesn't.
> >
> > The PCMCIA card and PCI bridge card are the same ones that NetGate sells,
> > and they had a direct link to the hostap stuff, which made me think it was
> > supported.  Unfortunately, doesn't seem to work here, or I've got a config
> > issue that I can't find.
> >
>
> Have you tried irq_mode=0 as an option to the i82365 module?
>
> I had to do that to get my Veritech (Senao) VAC2511-D card working in my
> Ricoh RL5c475 (rev 80) PCI-to-CardBus cradle.
>
> Cya.
>
> --
> Regards,
> Robert Davidson.
> http://www.mlug.org.au/
> IRC: puttputt, AustNet, #mlug
>
>




From jjo-hostap  Mon Aug  4 10:21:08 2003
From: jjo-hostap (JuanJo Ciarlante)
Date: Mon, 4 Aug 2003 14:21:08 -0300
Subject: BUG: weird behaviour after killing hostapd in latest CVS.
Message-ID: <20030804142108.K31149@mendoza.gov.ar>

Hi... 
I've updated hostap to CVS to test prism2_srec new features, which worked Ok
(loading PRI and STA to prism2.5 PCI card).

While testing hostapd I could "reproduceable" get this behaviour: after
killing hostapd (run hostapd from cmdline and do ^C, ie kill -2) 
my Linux console gets stuck: no response to keys,  no Alt-Fn switching
_but_ I can do the magic sysrq S-U-B with expected results (no fsck in next
boot).

This does not happen with 0.0.4.

Attached hostapd.conf, the only "rare" thing is that I'm using
"assoc_ap_addr" to a working AP; and I _do_ get expected behaviour:
association  Ok and "local" AP via hostapd.

Regards ...

-- 
--Juanjo

#  Juan Jose Ciarlante (JuanJo PGP) jjo ;at; mendoza.gov.ar              #
#  Key fingerprint = 76 60 A5 76 FD D2 53 E3  50 C7 90 20 22 8C F1 2D    #
-------------- next part --------------
##### hostapd configuration file ##############################################
# Empty lines and lines starting with # are ignored

# AP netdevice name (without 'ap' prefix, i.e., wlan0 uses wlan0ap for
# management frames)
interface=wlan0

# Debugging: 0 = no, 1 = minimal, 2 = verbose, 3 = msg dumps
#debug=3

# Dump file for state information (on SIGUSR1)
dump_file=/tmp/hostapd.dump

# Daemonize hostapd process (i.e., fork to background)
#daemonize=1


##### IEEE 802.11 related configuration #######################################

# SSID to be used in IEEE 802.11 management frames
ssid=lugmen

# Station MAC address -based authentication
# 0 = accept unless in deny list
# 1 = deny unless in accept list
# 2 = use external RADIUS server (accept/deny lists are searched first)
macaddr_acl=0

# Accept/deny lists are read from separate files (containing list of
# MAC addresses, one per line). Use absolute path name to make sure that the
# files can be read on SIGHUP configuration reloads.
#accept_mac_file=/etc/hostapd.accept
#deny_mac_file=/etc/hostapd.deny

# Associate as a station to another AP while still acting as an AP on the same
# channel.
#assoc_ap_addr=00:E0:03:04:B0:A2
assoc_ap_addr=00:e0:03:04:b0:a2



##### IEEE 802.1X (and IEEE 802.1aa/D4) related configuration #################

# Require IEEE 802.1X authorization
#ieee8021x=1
ieee8021x=0

# Use internal minimal EAP Authentication Server for testing IEEE 802.1X.
# This should only be used for testing since it authorizes all users that
# suppot IEEE 802.1X without any keys or certificates.
#minimal_eap=1

# Optional displayable message sent with EAP Request-Identity
#eap_message=hello

# WEP rekeying (disabled if key lengths are not set or are set to 0)
# Key lengths for default/broadcast and individual/unicast keys:
# 5 = 40-bit WEP (also known as 64-bit WEP with 40 secret bits)
# 13 = 104-bit WEP (also known as 128-bit WEP with 104 secret bits)
#wep_key_len_broadcast=5
#wep_key_len_unicast=5
# Rekeying period in seconds. 0 = do not rekey (i.e., set keys only once)
#wep_rekey_period=300

# EAPOL-Key index workaround (set bit7) for WinXP Supplicant (needed only if
# only broadcast keys are used)
#eapol_key_index_workaround=0


##### IEEE 802.11f - Inter-Access Point Protocol (IAPP) #######################

# Interface to be used for IAPP broadcast packets
#iapp_interface=eth0


##### RADIUS configuration ####################################################
# for IEEE 802.1X with external Authentication Server, IEEE 802.11
# authentication with external ACL for MAC addresses, and accounting

# The own IP address of the access point (used as NAS-IP-Address)
own_ip_addr=127.0.0.1

# RADIUS authentication server
#auth_server_addr=127.0.0.1
#auth_server_port=1812
#auth_server_shared_secret=secret

# RADIUS accounting server
#acct_server_addr=127.0.0.1
#acct_server_port=1813
#acct_server_shared_secret=secret


From williamt  Mon Aug  4 11:00:52 2003
From: williamt (William Tai)
Date: Mon, 4 Aug 2003 11:00:52 -0700
Subject: modify PDA to control txpower
Message-ID: <014001c35ab2$58356a40$e6f0c53f@williamt>

Hi All:

    I am trying modify PDR 0x0300 and PDR 0x0301 to control txpower by
calling prism2_download_volatile( ).
However I do not know the param0 and param1.
I know the starting addr of PDA is 0x7f0000.

/*     part of function  prism2_download_volatile( )
*/
 param0 = param->start_addr & 0xffff;
 param1 = param->start_addr >> 16;

 HFA384X_OUTW(0, HFA384X_PARAM2_OFF);
 HFA384X_OUTW(param1, HFA384X_PARAM1_OFF);
 if (hfa384x_cmd_wait(dev, HFA384X_CMDCODE_DOWNLOAD |
        (HFA384X_PROGMODE_ENABLE_VOLATILE << 8),
        param0)) {
  //printk(KERN_WARNING "%s: Download command execution failed\n",
  //       dev->name);
  ret = -1;
  goto out;
 }
/*************************************************/

So param->start_addr is also 0x7f0000?
William




From matrix  Mon Aug  4 11:00:35 2003
From: matrix (Francois Gurin)
Date: Mon, 4 Aug 2003 14:00:35 -0400
Subject: problems with 0.0.4 and gcc-3.2/3.3
In-Reply-To: <20030803174821.GB6507@jm.kir.nu>
References: <20030802025630.GM8799@shot.org> <20030803174821.GB6507@jm.kir.nu>
Message-ID: <20030804180035.GO8799@shot.org>

On Sun, Aug 03, 2003 at 10:48:21AM -0700, Jouni Malinen wrote:
> > I've been working on 0.0.4 for a few days now and have encountered 
> > problems compiling hostap with gcc 3.2 and 3.3.  When i use 2.95 
> > everything works as expected.
> > I had thought 3.2 was working fine until fairly recently.
> 
> Did you compile your kernel with the exact same gcc version? I have been
> using gcc v3.2.3 without any problems.

I think this may be the crux of the issue.  I don't recall what i compiled
the kernel with, but it may have been 2.95.  I'm working on rebuilding the
kernel to see what happens.  If this is the case, I'll have some egg on my
face, but at least it will be in the archives for anyone else having similar
issues.

> Please always try to resolve addresses in kernel oops messages with
> ksymoops. See Linux kernel Documentation/oops-tracing.txt for more
> details. Without this, the oops messages are usually quite useless.

I was trying to be complete, but this slipped my mind.  Others have 
responded having similar setups working, and I spent the weekend eliminating
hardware faults as a possibility.  

If it persists, I'll be sure to include more details.  

Thanks to the list for all the input I've recieved.

--francois



From greg  Mon Aug  4 11:00:46 2003
From: greg (Greg KH)
Date: Mon, 4 Aug 2003 11:00:46 -0700
Subject: Weird badness in 2.6.0-test2
In-Reply-To: <873cgigy41.fsf@lapper.ihatent.com>
References: <20030803182625.GA11226@nasledov.com>
	<873cgigy41.fsf@lapper.ihatent.com>
Message-ID: <20030804180046.GD3826@kroah.com>

On Mon, Aug 04, 2003 at 12:44:30AM +0200, Alexander Hoogerhuis wrote:
> Kinda similar with test2-mm[23] on my laptop and the orinoco_usb
> driver:

Should be fixed in Linus's latest tree.

thanks,

greg k-h



From greg  Mon Aug  4 11:00:07 2003
From: greg (Greg KH)
Date: Mon, 4 Aug 2003 11:00:07 -0700
Subject: Weird badness in 2.6.0-test2
In-Reply-To: <20030803182625.GA11226@nasledov.com>
References: <20030803182625.GA11226@nasledov.com>
Message-ID: <20030804180007.GC3826@kroah.com>

On Sun, Aug 03, 2003 at 11:26:25AM -0700, Joshua Kwan wrote:
> Hi,
> 
> Attached is a log of some oops I received when shutting down my laptop
> using HostAP kernel modules for my wireless card in kernel
> 2.6.0-test2-mm2. Is this a known problem?

Known problem, see the archives :)

thanks,

greg k-h



From krusty  Sun Aug  3 20:36:20 2003
From: krusty (James Nedila)
Date: Sun, 03 Aug 2003 20:36:20 -0700
Subject: 802.1x vs. open access?
Message-ID: <3F2DD4B4.30803@telus.net>

Maybe a stupid question, but can you have a single hostap access point 
with both of these methods of access available?

I would like to offer 802.1x to those who are able to use it.
Otherwise, all other access would be using a captive portal...


Thanks,
James





From pfoy  Mon Aug  4 06:14:10 2003
From: pfoy (Foy, Patrick)
Date: Mon, 4 Aug 2003 09:14:10 -0400 
Subject: Primary Firmware Download
Message-ID: <EF5625F9F795C94BA28B150706A21548A053D3@MAIL>

I've been pursing a few options in parallel.  One of the options is to use
your prism2dl utility to flash the primary and secondary images.  Is it
necessary to do anything with the PDA when loading the primary and secondary
images?

Thanks.

Patrick

-----Original Message-----
From: Pavel Roskin [mailto:proski at gnu.org]
Sent: Thursday, July 31, 2003 4:57 PM
To: Foy, Patrick
Cc: hostap at shmoo.com
Subject: RE: Primary Firmware Download


On Thu, 31 Jul 2003, Foy, Patrick wrote:

> We are shipping APs with Senao cards (2511CD-Plus), some with primary
> firmware 1.0.5 and others with 1.1.0.  We need secondary 1.7.4 for WDS,
> Enhanced security, scanning, etc which requires primary of 1.1.0 or
> newer.

I see.  That's indeed a good reason.

> The reason that I need to upgrade the primary with hostap (either into
> RAM or flash) is because we have shipped 100s of units and they need
> upgraded "in the field" (and we don't want to open the cases to re-flash
> the cards using winupdate).  I've read that updating the primary into
> flash isn't reliable, so I wanted to take the least risky route, which
> is uploading to RAM.

I don't know why you think that flashing primary firmware is not reliable.
It has always worked for me.  The problem is that HostAP cannot flash the
secondary firmware after that, so it was disabled in prism2_srec.

prism2dl with linux-wlan-ng flashes primary and secondary firmware just
fine.  On the other hand, loading primary firmware into the RAM has newer
worked for me with any driver, including linux-wlan-ng.

Here are your options:

1) Figure out how to load primary firmware into the RAM.  I have no idea
how.  Try setting genesis mode.  You may need to ask Intersil, but it may
be very expensive and not very helpful.

2) Fix HostAP to support flashing when only primary firmware is in the
card (note that flashing primary firmware disables secondary firmware).
That's the most realistic option and really needs to be done.  It's being
asked all the time, but nobody seems to be working on it.

3) Combine primary and secondary firmware into one image and flash it in
one operation.  This gives you the easiest procedure, but requires a lot
of work to be done to create the image.

4) Install linux-wlan-ng temporarily and flash primary and secondary
firmware, then replace it with the new HostAP driver.  This gives you the
hardest procedure in the field, but it's something that is working now and
requires no coding or firmware hacking.

-- 
Regards,
Pavel Roskin



From andreaf  Mon Aug  4 11:41:51 2003
From: andreaf (Andrea G. Forte)
Date: Mon, 4 Aug 2003 14:41:51 -0400 (EDT)
Subject: Host AP and PCI troubles.
Message-ID: <200308041841.h74Ifp01011595@cisalpino.cs.columbia.edu>

Hi everyone,
I do not know why but when after recompiling the kernel and installing all the 
modules and hostAP, the mopdprobe command gives me a message saying that no 
device was detected. I have done a lspci and it gives me only a "Unknown 
ethernet controller/device". Doing dmesg, it says that no device and no DRIVERs 
were found....shouldn't hostAP be the driver???
I am confused...I am using an Athlon 1.7+ and a PCI wireless card DWL-AG520.
Anybody can help please????
Andrea



From proski  Mon Aug  4 11:43:06 2003
From: proski (Pavel Roskin)
Date: Mon, 4 Aug 2003 14:43:06 -0400 (EDT)
Subject: hostap on Senao 2511 wireless cards
In-Reply-To: <Pine.LNX.4.44.0308041200520.10026-100000@kinison.puremagic.com>
References: <Pine.LNX.4.44.0308041200520.10026-100000@kinison.puremagic.com>
Message-ID: <Pine.LNX.4.56.0308041430510.5276@marabou.research.att.com>

On Mon, 4 Aug 2003, Evan Harris wrote:

> Anyone know why the irq_mode=0 setting is necessary for these
> PCI/Cardbus bridge cards to work properly?  Can this be added to the
> FAQ?

It's not trivial to figure out if the bridge is connected to the ISA
interrupt controller or not.  If it's connected, ISA interrupts are
preferred because some PCMCIA drivers have problems sharing interrupts
with the bridge itself.

If the bridge is a PCI card, it's not connected to the ISA interrupt
controller.  Then the only option is to use the PCI interrupt line that is
already used for the card insertion events.

The i82365 driver from pcmcia-cs used the existing state of the bridge if
irq_mode is not specified.  This works fine for most laptops, but not for
standalone PCI cards.

The pcmcia-cs package is in the late maintenance mode, and I don't expect
it to be improved to determine irq_mode automatically.

On the other hand, the kernel driver is being actively developed, and it
should do the right thing.  If the kernel driver is not working for you,
report it to the PCMCIA mailing list: linux-pcmcia at lists.infradead.org

-- 
Regards,
Pavel Roskin



From alexh  Mon Aug  4 11:07:48 2003
From: alexh (Alexander Hoogerhuis)
Date: 04 Aug 2003 20:07:48 +0200
Subject: Weird badness in 2.6.0-test2
In-Reply-To: <20030804180046.GD3826@kroah.com>
References: <20030803182625.GA11226@nasledov.com>
	<873cgigy41.fsf@lapper.ihatent.com> <20030804180046.GD3826@kroah.com>
Message-ID: <87fzkhjnyj.fsf@lapper.ihatent.com>

Greg KH <greg at kroah.com> writes:

> On Mon, Aug 04, 2003 at 12:44:30AM +0200, Alexander Hoogerhuis wrote:
> > Kinda similar with test2-mm[23] on my laptop and the orinoco_usb
> > driver:
> 
> Should be fixed in Linus's latest tree.
> 

Still in test2-mm4, but not sure if that's recent enough :)

> thanks,
> 
> greg k-h
> 

mvh,
A
-- 
Alexander Hoogerhuis                               | alexh at ihatent.com
CCNP - CCDP - MCNE - CCSE                          | +47 908 21 485
"You have zero privacy anyway. Get over it."  --Scott McNealy



From bapper  Mon Aug  4 11:53:55 2003
From: bapper (Brian Pomerantz)
Date: Mon, 4 Aug 2003 11:53:55 -0700
Subject: Host AP and PCI troubles.
In-Reply-To: <200308041841.h74Ifp01011595@cisalpino.cs.columbia.edu>
References: <200308041841.h74Ifp01011595@cisalpino.cs.columbia.edu>
Message-ID: <20030804185355.GA7024@skull.piratehaven.org>

On Mon, Aug 04, 2003 at 02:41:51PM -0400, Andrea G. Forte wrote:
> Hi everyone,
> I do not know why but when after recompiling the kernel and installing all the 
> modules and hostAP, the mopdprobe command gives me a message saying that no 
> device was detected. I have done a lspci and it gives me only a "Unknown 
> ethernet controller/device". Doing dmesg, it says that no device and no DRIVERs 
> were found....shouldn't hostAP be the driver???
> I am confused...I am using an Athlon 1.7+ and a PCI wireless card DWL-AG520.

The WEL-AG520 looks to be an Atheros card which is not supported by
hostap (only prsim chipsets).  My guess is you won't see a driver for
this until fall '03 or so.


BAPper



From proski  Mon Aug  4 13:09:31 2003
From: proski (Pavel Roskin)
Date: Mon, 4 Aug 2003 16:09:31 -0400 (EDT)
Subject: [PATCH] Better error reporting, printing PDA
Message-ID: <Pine.LNX.4.56.0308041557110.5725@marabou.research.att.com>

Hello!

Here are some minor fixes for the utilities that I put together because
they are trivial.

Errors in ioctl calls are reported by perror with the name on the ioctl,
but there are two cases when the name of the ioctl is not printed.

Also, "hostap_diag -a" is supposed to print all information, but it
doesn't print the PDA.

-- 
Regards,
Pavel Roskin
-------------- next part --------------
--- utils/hostap_crypt_conf.c
+++ utils/hostap_crypt_conf.c
@@ -191,7 +191,7 @@ static int do_ioctl(const char *dev, str
 
 	if (ioctl(s, PRISM2_IOCTL_HOSTAPD, &iwr) < 0) {
 		if (show_err) {
-			perror("ioctl");
+			perror("ioctl[PRISM2_IOCTL_HOSTAPD]");
 			show_error(param);
 		}
 		return -1;
--- utils/hostap_diag.c
+++ utils/hostap_diag.c
@@ -938,6 +938,7 @@ int main(int argc, char *argv[])
 			show_known_rids = 1;
 			show_unknown_rids = 1;
 			show_bbp = 1;
+			show_pda = 1;
 		} else if (c == 'b')
 			show_bbp = 1;
 		else if (c == 'h')
--- utils/util.c
+++ utils/util.c
@@ -172,7 +172,7 @@ int hostapd_ioctl(const char *dev, struc
 		close(s);
 		ret = errno;
 		if (show_err) 
-			perror("ioctl");
+			perror("ioctl[PRISM2_IOCTL_HOSTAPD]");
 		return ret;
 	}
 	close(s);


From bbeers  Mon Aug  4 09:46:47 2003
From: bbeers (Bob Beers)
Date: Mon, 04 Aug 2003 12:46:47 -0400
Subject: Primary Firmware Download
Message-ID: <3F2E8DF7.8070802@edgeaccess.net>

Hi Jouni, Pavel, and list

I've been reading with keen interest this thread on flashing firmware,
since I have some Netgear MA311 PCI cards 'in the field' with 1.0.7/1.3.6
that I would like to upgrade to 1.1.0/1.7.4 for the enhanced security
features and whatever else comes down the pike.

I have only used the windows update utility up to now.
So, before I try this, I want to ask a dumb question or two ...

What is the exact procedure to follow to make this happen on an
already deployed box?  

More specifically, should the hostap driver be loaded or unloaded
before I issue the prism2_srec wlan0 PK010101.HEX SF010704.HEX
and prism2_srec wlan0 -f PK010101.HEX SF010704.HEX commands?

Are there any (other) preliminary steps to take?  

I just want to be safe.

Thanks,

-Bob



From proski  Mon Aug  4 14:03:57 2003
From: proski (Pavel Roskin)
Date: Mon, 4 Aug 2003 17:03:57 -0400 (EDT)
Subject: Primary Firmware Download
In-Reply-To: <3F2E8DF7.8070802@edgeaccess.net>
References: <3F2E8DF7.8070802@edgeaccess.net>
Message-ID: <Pine.LNX.4.56.0308041655240.6082@marabou.research.att.com>

On Mon, 4 Aug 2003, Bob Beers wrote:

> What is the exact procedure to follow to make this happen on an
> already deployed box?
[snip]
> I just want to be safe.

I don't think anybody can write this procedure without careful testing
with your hardware.  Testing is the key to being safe.  That said, the
sequence should be approximately following:

update the driver and prism2_srec
bring the interface down
unload the hostap_pci module
load the hostap_pci module
run "prism2_srec wlan0 PK010101.HEX SF010704.HEX"
check output for errors
run "prism2_srec -f wlan0 PK010101.HEX SF010704.HEX"
check the kernel log to make sure the firmware has been updated
restart the software working with interface
test that the interface is functioning

-- 
Regards,
Pavel Roskin



From matrix  Mon Aug  4 14:45:21 2003
From: matrix (Francois Gurin)
Date: Mon, 4 Aug 2003 17:45:21 -0400
Subject: [HostAP]  Re: problems with 0.0.4 and gcc-3.2/3.3
In-Reply-To: <20030804180035.GO8799@shot.org>
References: <20030802025630.GM8799@shot.org> <20030803174821.GB6507@jm.kir.nu>
	<20030804180035.GO8799@shot.org>
Message-ID: <20030804214521.GU8799@shot.org>

> > Did you compile your kernel with the exact same gcc version? I have been
> > using gcc v3.2.3 without any problems.
> 
> I think this may be the crux of the issue.  I don't recall what i compiled
> the kernel with, but it may have been 2.95.  I'm working on rebuilding the
> kernel to see what happens.  If this is the case, I'll have some egg on my
> face, but at least it will be in the archives for anyone else having similar
> issues.

This was in fact the problem.  With the kernel rebuilt with the same
gcc there are no crashes or lockups.

In summary, as others pointed out, there are no problems with 0.0.4
and gcc-3.3 aside from the benign warnings from the kernel-headers.

It's all back to working quite nicely.  Thank you all for the assitance.

--francois





From eaglecz  Mon Aug  4 15:54:08 2003
From: eaglecz (Tomas Charvat)
Date: Tue, 5 Aug 2003 00:54:08 +0200
Subject: fw problem
Message-ID: <017301c35adb$5097a900$050314ac@rip>

this was a bit too much for me :)

[root at brouter utils]# ./prism2_srec -r PK010101.HEX SF010704.HEX
srec summary for SF010704.HEX
Component: 0x001f 1.7.4 (station firmware)

ioctl: No such device
Missing wlan component info
Could not read wlan RIDs
[root at brouter utils]# ./prism2_srec -r wlan0 PK010101.HEX SF010704.HEX
srec summary for PK010101.HEX
Component: 0x0015 1.1.1 (primary firmware)

srec summary for SF010704.HEX
Component: 0x001f 1.7.4 (station firmware)


Verifying update compatibility and combining data:
Plug record length mismatch (PDR=0x0001): 12 != 16
==> extend from default
PRI: old iface 1:4-4 new iface 1:4-4
Allowing S3 overlap due to CRC-16 signature at 0x007e17fe (was: ffff)

This image is not meant to be downloaded to volatile memory.
Incompatible update data.

my Syslog

Aug  5 00:48:09 brouter kernel: prism2_download: dl_cmd=3
start_addr=0x00000000 num_areas=5
Aug  5 00:48:09 brouter kernel:   area 0: addr=0x007e0000 len=2902
ptr=0x08052690
Aug  5 00:48:09 brouter kernel:   area 1: addr=0x007e0c00 len=2336
ptr=0x080531f0
Aug  5 00:48:09 brouter kernel:   area 2: addr=0x007e17fe len=51934
ptr=0x08062860
Aug  5 00:48:09 brouter kernel:   area 3: addr=0x007f0800 len=3974
ptr=0x080618d0
Aug  5 00:48:09 brouter kernel:   area 4: addr=0x007fe000 len=3270
ptr=0x08051480
Aug  5 00:48:09 brouter kernel: wlan0: non-volatile downloading not enabled
Aug  5 00:50:50 brouter modprobe: modprobe: Can't locate module PK010101.HEX


i have Z com Xi 626, and i used same FW in all cards, but i flashed them
under Win, but this one must be done remote
latest CVS (15 mins old)

any help is welcome

tomas



From jim  Mon Aug  4 18:28:51 2003
From: jim (Jim TerWee)
Date: Mon, 4 Aug 2003 20:28:51 -0500 (CDT)
Subject: Host AP and PCI troubles.
In-Reply-To: <20030804185355.GA7024@skull.piratehaven.org>
References: <200308041841.h74Ifp01011595@cisalpino.cs.columbia.edu>
        <20030804185355.GA7024@skull.piratehaven.org>
Message-ID: <4284.207.41.65.10.1060046931.squirrel@207.41.64.133>



>
> The WEL-AG520 looks to be an Atheros card which is not supported by
> hostap (only prsim chipsets).  My guess is you won't see a driver for
> this until fall '03 or so.
>
>
If it is a Atheros you can find the driver here

http://sourceforge.net/projects/madwifi/


-- 
Jim TerWee       | Our capacity for understanding is
jim at terwee.com   | inversely proportional to how
Invisimax        | much we think we know. The more I
                 | know, the more I don't know!




From jkmaline  Mon Aug  4 19:27:49 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 4 Aug 2003 19:27:49 -0700
Subject: BUG: weird behaviour after killing hostapd in latest CVS.
In-Reply-To: <20030804142108.K31149@mendoza.gov.ar>
References: <20030804142108.K31149@mendoza.gov.ar>
Message-ID: <20030805022749.GC3211@jm.kir.nu>

On Mon, Aug 04, 2003 at 02:21:08PM -0300, JuanJo Ciarlante wrote:

> While testing hostapd I could "reproduceable" get this behaviour: after
> killing hostapd (run hostapd from cmdline and do ^C, ie kill -2) 
> my Linux console gets stuck: no response to keys,  no Alt-Fn switching
> _but_ I can do the magic sysrq S-U-B with expected results (no fsck in next
> boot).
> 
> This does not happen with 0.0.4.

I did change wlan0ap and wlan0sta interface unregistering, so that might
have caused some issues. I tested this only with Linux 2.6.0-test2..
Which kernel version are you using?

> Attached hostapd.conf, the only "rare" thing is that I'm using
> "assoc_ap_addr" to a working AP; and I _do_ get expected behaviour:
> association  Ok and "local" AP via hostapd.

Which station firmware version are you using?

Did you have wlan0sta interface UP when killing hostapd? If yes, what
happens if you first set it down and only after that kill hostapd?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug  4 19:31:12 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 4 Aug 2003 19:31:12 -0700
Subject: modify PDA to control txpower
In-Reply-To: <014001c35ab2$58356a40$e6f0c53f@williamt>
References: <014001c35ab2$58356a40$e6f0c53f@williamt>
Message-ID: <20030805023112.GD3211@jm.kir.nu>

On Mon, Aug 04, 2003 at 11:00:52AM -0700, William Tai wrote:

>     I am trying modify PDR 0x0300 and PDR 0x0301 to control txpower by
> calling prism2_download_volatile( ).

You are trying to modify PDA by using _volatile_ download?? PDA is a
block in flash.. In addition, please note that changing the PDA values
does not really change anything unless you download a new image after
that. In many cases, it would probably be easier to just modify
prism2_srec to overrite card PDA with something else when plugging PDRs.

> However I do not know the param0 and param1.
> I know the starting addr of PDA is 0x7f0000.

You cannot load PDA that way with volatile download.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug  4 19:36:03 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 4 Aug 2003 19:36:03 -0700
Subject: fw problem
In-Reply-To: <017301c35adb$5097a900$050314ac@rip>
References: <017301c35adb$5097a900$050314ac@rip>
Message-ID: <20030805023603.GE3211@jm.kir.nu>

On Tue, Aug 05, 2003 at 12:54:08AM +0200, Tomas Charvat wrote:

> [root at brouter utils]# ./prism2_srec -r wlan0 PK010101.HEX SF010704.HEX

-r = volatile download (i.e., RAM; not flash)

> This image is not meant to be downloaded to volatile memory.
> Incompatible update data.

And reason for the failure..

PK010101.HEX and SF010704.HEX are for non-volatile (flash) downloading
only.

> Aug  5 00:48:09 brouter kernel: wlan0: non-volatile downloading not enabled

Hey.. you did not include the prism2_srec command that you used to
produce that one ;-). Flash download is disabled in the default driver
build. You will need to define PRISM2_NON_VOLATILE_DOWNLOAD in addition
to PRISM2_DOWNLOAD_SUPPORT (see hostap_config.h) to get the possibility
of frying your flash ;-).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug  4 19:44:51 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 4 Aug 2003 19:44:51 -0700
Subject: [PATCH] Better error reporting, printing PDA
In-Reply-To: <Pine.LNX.4.56.0308041557110.5725@marabou.research.att.com>
References: <Pine.LNX.4.56.0308041557110.5725@marabou.research.att.com>
Message-ID: <20030805024451.GF3211@jm.kir.nu>

On Mon, Aug 04, 2003 at 04:09:31PM -0400, Pavel Roskin wrote:

> Here are some minor fixes for the utilities that I put together because
> they are trivial.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From williamt  Mon Aug  4 19:57:30 2003
From: williamt (William Tai)
Date: Mon, 4 Aug 2003 19:57:30 -0700
Subject: modify PDA to control txpower
References: <014001c35ab2$58356a40$e6f0c53f@williamt>
	<20030805023112.GD3211@jm.kir.nu>
Message-ID: <01a001c35afd$4fb16f40$e6f0c53f@williamt>


----- Original Message ----- 
From: "Jouni Malinen" <jkmaline at cc.hut.fi>
To: <hostap at shmoo.com>
Sent: Monday, August 04, 2003 7:31 PM
Subject: Re: modify PDA to control txpower


> On Mon, Aug 04, 2003 at 11:00:52AM -0700, William Tai wrote:
>
> >     I am trying modify PDR 0x0300 and PDR 0x0301 to control txpower by
> > calling prism2_download_volatile( ).
>
> You are trying to modify PDA by using _volatile_ download?? PDA is a
> block in flash.. In addition, please note that changing the PDA values
> does not really change anything unless you download a new image after
> that. In many cases, it would probably be easier to just modify
> prism2_srec to overrite card PDA with something else when plugging PDRs.
>

I add two lines of the codes in prism2_read_pda( ) and then it works.


/*static*/ u8 * prism2_read_pda(struct device *dev)
{
 u8 *buf;
 int res, i, found = 0;
#define NUM_PDA_ADDRS 3
 unsigned int pda_addr[NUM_PDA_ADDRS] = {
  0x7f0000 /* others than HFA3841 */,
  0x3f0000 /* HFA3841 */,
  0x390000 /* apparently used in older cards */
 };
 u16 setpoint[14]={0x00c0, 0x00c0, 0x00c0, 0x00c0, 0x00c0, 0x00c0, 0x00c0,
0x00c0, 0x00c0, 0x00c0, 0x00c0, 0x00c0, 0x00c0, 0x00c0};

// buf = (u8 *) kmalloc(PRISM2_PDA_SIZE, GFP_KERNEL);
 buf = (u8 *) malloc(PRISM2_PDA_SIZE);
 if (buf == NULL)
  return NULL;

 /* Note: wlan card should be in initial state (just after init cmd)
  * and no other operations should be performed concurrently. */

 prism2_enable_aux_port(dev, 1);

 for (i = 0; i < NUM_PDA_ADDRS; i++) {
  //printk(KERN_DEBUG "%s: trying to read PDA from 0x%08x",
  //       dev->name, pda_addr[i]);
  res = hfa384x_from_aux(dev, pda_addr[i], PRISM2_PDA_SIZE, buf);
//  if (res)
//   continue;
  if (res == 0 && prism2_pda_ok(buf)) {
   //printk(": OK\n");
   found = 1;
   break;
  } else {
   //printk(": failed\n");
  }
 }
#if 0
 res = hfa384x_to_aux(dev, 0x7f01be, 28, (void *)setpoint);  <----new added
  res = hfa384x_from_aux(dev, 0x7f01be, 28, buf);                <---- 
newadded
#endif
 prism2_enable_aux_port(dev, 0);

 if (!found) {
  kfree(buf);
  buf = NULL;
 }

 return buf;
}



> > However I do not know the param0 and param1.
> > I know the starting addr of PDA is 0x7f0000.
>
> You cannot load PDA that way with volatile download.
>
> -- 
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From sits  Tue Aug  5 00:17:02 2003
From: sits (Sitsofe Wheeler)
Date: 05 Aug 2003 08:17:02 +0100
Subject: prism cards
In-Reply-To: <1081.200.63.198.49.1060006979.squirrel@webmail.linuxpowered.org>
References: 	 <1081.200.63.198.49.1060006979.squirrel@webmail.linuxpowered.org>
Message-ID: <1060067821.1949.3.camel@galvatron.localdomain>

On Mon, 2003-08-04 at 15:22, Vicente Paredes wrote:
> Hello
> 
> I have been looking for prism based wireless cards, but i havent find
> them. Actually exists card with this chip?
Try checking the linux-wlan wifi card list:
http://www.linux-wlan.org/docs/wlan_adapters.html4.html

-- 
Sitsofe | http://sucs.org/~sits/



From vda  Tue Aug  5 06:13:56 2003
From: vda (Denis Vlasenko)
Date: Tue, 5 Aug 2003 16:13:56 +0300
Subject: [PATCH] implement sensitivity control (resend)
Message-ID: <200308051304.h75D4Pj19969@Port.imtp.ilyichevsk.odessa.ua>

I haven't seen any comments, maybe a resend is in order

==============================================================
From: Denis Vlasenko <vda at port.imtp.ilyichevsk.odessa.ua>
To: Jouni Malinen <jkmaline at cc.hut.fi>, Pavel Roskin <proski at gnu.org>
Subject: [PATCH] implement sensitivity control
Date: Thu, 3 Jul 2003 12:29:43 +0300
 
Hi Jouni, Pavel, folks.

I made a patch which implements sensitivity control for hostap.
Currently it does not program sensitivity at card initialization
(you'll need explicit iwconfig wlan# sens N or card remains
programmed as per default (max sens)) and sens settings do not
survive card reset. These can be fixed later.

Applies to today's CVS.

After iwconfig wlan0 sens 117:
wlan0     IEEE 802.11b
          Mode:Master  Frequency:2.422GHz
          Bit Rate:11Mb/s   Tx-Power=-1 dBm   Sensitivity=117/127

Untouched by iwconfig sens N:
wlan1     IEEE 802.11b
          Mode:Managed  Frequency:2.462GHz
          Bit Rate:2Mb/s   Tx-Power:5 dBm   Sensitivity=0/127

(this is wrong, should show 127/127. later...)

This is what I get in my logs with these patches:
=================================================
01:21:45 kernel:    A1=01:02:2d:61:49:cd A2=00:02:2d:51:3e:ab A3=00:00:00:00:00:00 A4=aa:aa:03:00:20:f6
01:21:45 kernel: wlan0: dropped received packet from 00:02:2d:51:3e:ab with no ToDS flag (type=0x02, subtype=0x00)
01:21:45 kernel: wlan0: RX signal=163 noise=156 rate=20 len=118 jiffies=16877
01:21:45 kernel:    FC=0x0008 (type=2:0) dur=0x0000 seq=0xdca0
01:21:45 kernel:    A1=01:02:2d:61:49:cd A2=00:02:2d:51:3e:ab A3=00:00:00:00:00:00 A4=aa:aa:03:00:20:f6
01:21:46 kernel: wlan0: dropped received packet from 00:02:2d:51:3e:ab with no ToDS flag (type=0x02, subtype=0x00)
01:21:46 kernel: wlan0: RX signal=163 noise=156 rate=20 len=281 jiffies=16892
01:21:46 kernel:    FC=0x0008 (type=2:0) dur=0x0000 seq=0xdd20
01:21:46 kernel:    A1=01:02:2d:61:49:cd A2=00:02:2d:51:3e:ab A3=00:00:00:00:00:00 A4=aa:aa:03:00:20:f6
01:21:46 kernel: wlan0: dropped received packet from 00:02:2d:51:3e:ab with no ToDS flag (type=0x02, subtype=0x00)

these are 'foreign' packets which I do not want to receive...

01:21:46 kernel: wlan0: RX signal=163 noise=156 rate=20 len=118 jiffies=16897
01:21:46 kernel:    FC=0x0008 (type=2:0) dur=0x0000 seq=0xdd40
01:21:46 kernel:    A1=01:02:2d:61:49:cd A2=00:02:2d:51:3e:ab A3=00:00:00:00:00:00 A4=aa:aa:03:00:20:f6
01:21:47 kernel: wlan0: dropped received packet from 00:02:2d:51:3e:ab with no ToDS flag (type=0x02, subtype=0x00)
01:21:47 kernel: wlan0: RX signal=163 noise=156 rate=20 len=50 jiffies=17030
01:21:47 kernel:    FC=0x0008 (type=2:0) dur=0x0000 seq=0xe240
01:21:47 kernel:    A1=01:02:2d:61:49:cd A2=00:02:2d:51:3e:ab A3=00:00:00:00:00:00 A4=aa:aa:03:00:20:f6

I do 'iwconfig wlan0 sens 117'

01:21:52 kernel: wlan0: ED_THRESHOLD: ->0a
01:21:52 kernel: wlan0: ACQUISITION_THRESHOLDS: 1e->5e

and no more bad packets seen ;)
--
vda

Now iwconfig sens N (0..127) does indeed have some effect

diff -ur hostap-2003-06-16/driver/modules/hostap_ioctl.c hostap-2003-06-16.sens/driver/modules/hostap_ioctl.c
--- hostap-2003-06-16/driver/modules/hostap_ioctl.c     Fri Jun  6 06:07:01 2003
+++ hostap-2003-06-16.sens/driver/modules/hostap_ioctl.c        Thu Jul  3 01:13:48 2003
@@ -503,14 +503,75 @@
                                struct iw_param *sens, char *extra)
 {
        local_info_t *local = (local_info_t *) dev->priv;
-
-       /* Set the desired AP density */
-       if (sens->value < 1 || sens->value > 3)
+       u16 val,newv;
+       
+       /* Energy Detected threshold: 0..127 <-> Sensitivity 127..0 */
+       
+       /* NB:  by default ED seen programmed to 127 (maxed out, lowest sens)
+       *       but ignored in both TX_CONFIGURE and ACQ_THRESH regs
+       *       That's how hw was prgrammed in my DWL-520
+       *       before I started to have fun with sens.
+       * TODO: special case sens 128: do not make Acquisition Thresholds
+       *       honour Energy Detected threshold.
+       *       Maybe it can pick weaker signals with that setting
+       * TODO: set max sens 127 (128) at init.
+       * TODO: teach driver to set sens after hw reset.
+       */
+       /* Set Energy Detected threshold */
+       if(sens->value < 0 || sens->value > 127)
+               return -EINVAL;
+       val = 127 - sens->value; /* bit 7=0 - threshold is rel to noise */
+       printk(KERN_DEBUG "%s: ED_THRESHOLD: ->%02x\n", dev->name, val);
+       if(local->func->cmd(dev, HFA384X_CMDCODE_WRITEMIF,
+         HFA386X_CR_ED_THRESHOLD, &val, NULL)) {
+               printk(KERN_ERR "%s: failure writing ED_THRESHOLD\n",
+                       dev->name);
                return -EINVAL;
-
-       if (hostap_set_word(dev, HFA384X_RID_CNFSYSTEMSCALE, sens->value) ||
-           local->func->reset_port(dev))
+       }
+#if 0  /* Seems like it has no effect (on my hw/fw conf) */
+       /* Make Clear Channel Assessment honour Energy Detected threshold */
+       if(local->func->cmd(dev, HFA384X_CMDCODE_READMIF,
+         HFA386X_CR_TX_CONFIGURE, NULL, &val)) {
+               printk(KERN_ERR "%s: failure reading TX_CONFIGURE\n",
+                       dev->name);
                return -EINVAL;
+       }
+       /* bits 6:5
+       * 00 - CCA is based only on ED. 
+       * 01 - CCA is based on (CS1 OR SQ1). 
+       * 10 - CCA is based on (ED AND (CS1 OR SQ1)). 
+       * 11 - CCA is based on (ED OR (CS1 OR SQ1)). */
+       newv = (val&0x9f)|0x40; /* 6:5=10 */
+       printk(KERN_DEBUG "%s: TX_CONFIGURE: %02x->%02x\n",
+               dev->name, val, newv);
+       if(val != newv) {
+               if(local->func->cmd(dev, HFA384X_CMDCODE_WRITEMIF,
+                 HFA386X_CR_TX_CONFIGURE, &newv, NULL)) {
+                       printk(KERN_ERR "%s: failure writing TX_CONFIGURE\n",
+                               dev->name);
+                       return -EINVAL;
+               }
+       }
+#endif
+       /* Make Acquisition Thresholds honour Energy Detected threshold */
+       if(local->func->cmd(dev, HFA384X_CMDCODE_READMIF,
+         HFA386X_CR_ACQUISITION_THRESHOLDS, NULL, &val)) {
+               printk(KERN_ERR "%s: failure reading ACQUISITION_THRESHOLDS\n",
+                       dev->name);
+               return -EINVAL;
+       }
+       /* bit 6 - ED and SQ1 control for acquisition. 0 = SQ1. 1 = ED and SQ1. */
+       newv = val|0x40;
+       printk(KERN_DEBUG "%s: ACQUISITION_THRESHOLDS: %02x->%02x\n",
+               dev->name, val, newv);
+       if(val != newv) {
+               if(local->func->cmd(dev, HFA384X_CMDCODE_WRITEMIF,
+                 HFA386X_CR_ACQUISITION_THRESHOLDS, &newv, NULL)) {
+                       printk(KERN_ERR "%s: failure writing "
+                               "ACQUISITION_THRESHOLDS\n", dev->name);
+                       return -EINVAL;
+               }
+       }
 
        return 0;
 }
@@ -520,14 +581,15 @@
                                struct iw_param *sens, char *extra)
 {
        local_info_t *local = (local_info_t *) dev->priv;
-       u16 val;
-
-       /* Get the current AP density */
-       if (local->func->get_rid(dev, HFA384X_RID_CNFSYSTEMSCALE, &val, 2, 1) <
-           0)
-               return -EINVAL;
 
-       sens->value = __le16_to_cpu(val);
+       u16 val;
+       if (local->func->cmd(dev, HFA384X_CMDCODE_READMIF,
+         HFA386X_CR_ED_THRESHOLD, NULL, &val)) {
+               printk(KERN_ERR "%s: failure reading ED_THRESHOLD\n",
+                       dev->name);
+               return -EINVAL;         /* or what? */
+       }
+       sens->value = 127-(val&0x7f);
        sens->fixed = 1;
 
        return 0;
@@ -932,7 +994,7 @@
        range->max_qual.qual = 92; /* 0 .. 92 */
        range->max_qual.level = 154; /* 27 .. 154 */
        range->max_qual.noise = 154; /* 27 .. 154 */
-       range->sensitivity = 3;
+       range->sensitivity = 127;
 
        range->max_encoding_tokens = WEP_KEYS;
        range->num_encoding_sizes = 2;
diff -ur hostap-2003-06-16/driver/modules/hostap_wlan.h hostap-2003-06-16.sens/driver/modules/hostap_wlan.h
--- hostap-2003-06-16/driver/modules/hostap_wlan.h      Fri May 23 05:23:48 2003
+++ hostap-2003-06-16.sens/driver/modules/hostap_wlan.h Sat Jun 28 23:38:54 2003
@@ -681,6 +681,8 @@
 #define HFA386X_CR_RX_CONFIGURE 0x14
 #define HFA386X_CR_A_D_TEST_MODES2 0x1A
 #define HFA386X_CR_MANUAL_TX_POWER 0x3E
+#define HFA386X_CR_ED_THRESHOLD 0x46
+#define HFA386X_CR_ACQUISITION_THRESHOLDS 0x5E
 
 /* IEEE 802.11 defines */
 



From jlaraujo  Tue Aug  5 07:10:16 2003
From: jlaraujo (Jose Araujo)
Date: Tue, 05 Aug 2003 15:10:16 +0100
Subject: NICID 8002 1.7.1 firmware upgrade 
Message-ID: <3F2FBAC8.7040002@dti.pga.pt>

Hi, i tried to upgrade my USRobotics 1410 to the latest firmware (1.7.1).

After some tries, prism2_srec always failed with a timeout error.
I then upgraded to CSV version, same timeout error.

My setup was:

NICID: 0x8002 1.0.0
PRI: 0x15          0.3.0
STA: 0x1f          1.4.9

After a ram upgrade to 1.5.6 it was:

NICID: 0x8002 1.0.0
PRI: 0x15          0.3.0
STA: 0x1f          1.5.6

While browsing the mailing list archives i found a flash upgrade for 
0x8002 and tried it.

It worked, my setup was then:
PRI: 0x15          0.3.0
STA: 0x1f          1.5.6

After that i tried again to flash upgrade to 1.7.1.
To my surprise it worked, so this message is meant to help everyone who 
may have the same problem.
Thanks to the comunity for their effort in this mailing list.
And a special thanks to Pavel Roskin who maintains a firmware page where 
i downloaded all firmware versions 
http://www.red-bean.com/~proski/firmware/.

Jos? Ara?jo






From bbeers  Tue Aug  5 07:10:29 2003
From: bbeers (Bob Beers)
Date: Tue, 05 Aug 2003 10:10:29 -0400
Subject: Primary Firmware Download
References: <3F2E8DF7.8070802@edgeaccess.net>
	<Pine.LNX.4.56.0308041655240.6082@marabou.research.att.com>
Message-ID: <3F2FBAD5.2050707@edgeaccess.net>

Pavel Roskin wrote:
> On Mon, 4 Aug 2003, Bob Beers wrote:
> 
> 
>>What is the exact procedure to follow to make this happen on an
>>already deployed box?
> 
> [snip]
> 
>>I just want to be safe.
> 
> 
> I don't think anybody can write this procedure without careful testing
> with your hardware.  Testing is the key to being safe.  That said, the
> sequence should be approximately following:

Thanks, I agree.  But I haven't seen it spelled out in the list or in 
the documentation, so I thought I'd ask the question.  Perhaps I should 
have asked recommended vs. exact.

> 
> update the driver and prism2_srec

A few more details for the record (correct me if I'm wrong anywhere).
Get CVS snapshot dated >= 2003-08-0? (Aug. 3rd?)
And, if you haven't already built your hostap driver modules
to support firmware download, uncomment the line:
#define PRISM2_DOWNLOAD_SUPPORT
in hostap/driver/modules/hostap_config.h (~line number 43).

Then make your hostap modules and utils.

Transfer the download capable driver modules, the prism2_srec,
and the .hex files to the deployed box.


> bring the interface down
> unload the hostap_pci module
> load the hostap_pci module

Load the firmware download capable driver :-)

> run "prism2_srec wlan0 PK010101.HEX SF010704.HEX"
> check output for errors
> run "prism2_srec -f wlan0 PK010101.HEX SF010704.HEX"
> check the kernel log to make sure the firmware has been updated
> restart the software working with interface
> test that the interface is functioning
> 

I'll be trying this out today.

Thanks again,

-Bob Beers



From wim  Mon Aug  4 14:01:00 2003
From: wim (Wim Osterholt)
Date: Mon, 04 Aug 2003 21:01:00 -0000
Subject: prism cards
In-Reply-To: <3F2E7F5B.806@yifan.net> from "Jay Zhang" at Aug 4, 3 10:44:27 am
Message-ID: <200308042054.WAA10046@sdc.djo.tudelft.nl>

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 1582 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20030804/c02c623e/attachment.txt 


From proski  Tue Aug  5 09:26:14 2003
From: proski (Pavel Roskin)
Date: Tue, 5 Aug 2003 12:26:14 -0400 (EDT)
Subject: Primary Firmware Download
In-Reply-To: <3F2FBAD5.2050707@edgeaccess.net>
References: <3F2E8DF7.8070802@edgeaccess.net>
 <Pine.LNX.4.56.0308041655240.6082@marabou.research.att.com>
 <3F2FBAD5.2050707@edgeaccess.net>
Message-ID: <Pine.LNX.4.56.0308051223040.11840@marabou.research.att.com>

On Tue, 5 Aug 2003, Bob Beers wrote:

> A few more details for the record (correct me if I'm wrong anywhere).
> Get CVS snapshot dated >= 2003-08-0? (Aug. 3rd?)

2003-08-05 should be OK.

> And, if you haven't already built your hostap driver modules
> to support firmware download, uncomment the line:
> #define PRISM2_DOWNLOAD_SUPPORT
> in hostap/driver/modules/hostap_config.h (~line number 43).

Also uncomment PRISM2_NON_VOLATILE_DOWNLOAD in the same file.

-- 
Regards,
Pavel Roskin



From eaglecz  Tue Aug  5 09:29:41 2003
From: eaglecz (Tomas Charvat)
Date: Tue, 5 Aug 2003 18:29:41 +0200
Subject: freez
Message-ID: <001e01c35b6e$c59ee180$050314ac@rip>

greeting guys
i have zcom xi 626, 1.1.0 /1.7.4 , CVS from yesterday
and following things happen
machine sometimes hang few senconds after i issue

    iwpriv wlan3 reset 1
    iwpriv wlan3 reset 2
    iwpriv wlan3 maccmd 1
    iwpriv wlan3 addmac 00:06:25:1B:C2:6A # cobra
    iwpriv wlan3 addmac 00:02:72:02:47:68 # murin
    iwconfig wlan3 mode master
    iwconfig wlan3 essid cobraac channel 5 retry 30





and this appear in syslog before freez, freez come after last line

Aug  5 17:43:15 nest kernel: NETDEV WATCHDOG: wlan3wds1: transmit timed out
Aug  5 17:43:15 nest kernel: wlan3wds1 Tx timed out! Resetting card
Aug  5 17:43:15 nest kernel: wlan3wds1: CMD=010b EVSTAT=0000 OFFSET0=0000
OFFSET1=0000 SWSUPPORT0=8a32
Aug  5 17:43:15 nest kernel: wlan3: scheduled card reset
Aug  5 17:43:15 nest kernel: hostap_pci: wlan3: resetting card
Aug  5 17:43:15 nest kernel: wlan3: STA 00:02:72:02:47:68 TX rate lowered to
55
Aug  5 17:44:18 nest kernel: wlan3: 00:06:25:1b:c2:6a auth_cb - STA
authenticated
Aug  5 17:44:18 nest kernel: wlan3: 00:06:25:1b:c2:6a assoc_cb - STA
associated
Aug  5 17:51:53 nest kernel: wlan3: STA 00:02:72:02:47:68 TX rate lowered to
20
Aug  5 17:52:22 nest kernel: wlan3: Deauthenticate all stations
Aug  5 17:52:23 nest kernel: wlan3: manual reset request(1)
Aug  5 17:52:23 nest kernel: hostap_pci: wlan3: resetting card
Aug  5 17:52:23 nest kernel: wlan3: manual reset request(2)
Aug  5 17:52:23 nest kernel: wlan3: TXEXC - status=0x0004 ([Discon])
tx_control=002c


any tips ?


regards
tomas



From proski  Tue Aug  5 09:53:37 2003
From: proski (Pavel Roskin)
Date: Tue, 5 Aug 2003 12:53:37 -0400 (EDT)
Subject: NICID 8002 1.7.1 firmware upgrade 
In-Reply-To: <3F2FBAC8.7040002@dti.pga.pt>
References: <3F2FBAC8.7040002@dti.pga.pt>
Message-ID: <Pine.LNX.4.56.0308051248360.11910@marabou.research.att.com>

On Tue, 5 Aug 2003, Jose Araujo wrote:

> It worked, my setup was then:
> PRI: 0x15          0.3.0
> STA: 0x1f          1.5.6
>
> After that i tried again to flash upgrade to 1.7.1.
> To my surprise it worked, so this message is meant to help everyone who
> may have the same problem.

I'll appreciate if you send me the flash firmware 1.7.1 for Prism 2 or
give me a pointer where to download it.  It will be added to my
collection.

I'm sure users on Prism 2 cards will appreciate the possibility to hide
ESSID in beacons without having to load firmware into the RAM every time.

-- 
Regards,
Pavel Roskin



From bbeers  Tue Aug  5 10:32:05 2003
From: bbeers (Bob Beers)
Date: Tue, 05 Aug 2003 13:32:05 -0400
Subject: Primary Firmware Download
References: <3F2E8DF7.8070802@edgeaccess.net>
	<Pine.LNX.4.56.0308041655240.6082@marabou.research.att.com>
	<3F2FBAD5.2050707@edgeaccess.net>
Message-ID: <3F2FEA15.2090101@edgeaccess.net>

Bob Beers wrote:

> I'll be trying this out today.
> 

Ok, seems to work, what is "Plug record length mismatch"?
Should I worry?  Card is working fine after the upgrade.
Here's the screen capture:


bash-2.05# hostap_diag wlan0
Host AP driver diagnostics information for 'wlan0'

NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.0.7
STAID: id=0x001f v1.3.6 (station firmware)
bash-2.05# ./prism2_srec wlan0 PK010101.HEX SF010704.HEX
srec summary for PK010101.HEX
Component: 0x0015 1.1.1 (primary firmware)

srec summary for SF010704.HEX
Component: 0x001f 1.7.4 (station firmware)


Verifying update compatibility and combining data:
Plug record length mismatch (PDR=0x0001): 12 != 16
==> extend from default
PRI: old iface 1:4-4 new iface 1:4-4
Allowing S3 overlap due to CRC-16 signature at 0x007e17fe (was: ffff)
OK.
bash-2.05# ./prism2_srec -f wlan0 PK010101.HEX SF010704.HEX
srec summary for PK010101.HEX
Component: 0x0015 1.1.1 (primary firmware)

srec summary for SF010704.HEX
Component: 0x001f 1.7.4 (station firmware)


Verifying update compatibility and combining data:
Plug record length mismatch (PDR=0x0001): 12 != 16
==> extend from default
PRI: old iface 1:4-4 new iface 1:4-4
Allowing S3 overlap due to CRC-16 signature at 0x007e17fe (was: ffff)
OK.

Downloading to non-volatile memory (flash).
Note! This can take about 30 seconds. Do _not_ remove card during download.
OK.
Components after download:
   NICID: 0x8013 v1.0.0
   PRIID: 0x0015 v1.1.1
   STAID: 0x001f v1.7.4
bash-2.05#


What a great thing!

-Bob Beers



From proski  Tue Aug  5 12:41:42 2003
From: proski (Pavel Roskin)
Date: Tue, 5 Aug 2003 15:41:42 -0400 (EDT)
Subject: Primary Firmware Download
In-Reply-To: <3F2FEA15.2090101@edgeaccess.net>
References: <3F2E8DF7.8070802@edgeaccess.net>
 <Pine.LNX.4.56.0308041655240.6082@marabou.research.att.com>
 <3F2FBAD5.2050707@edgeaccess.net> <3F2FEA15.2090101@edgeaccess.net>
Message-ID: <Pine.LNX.4.56.0308051522590.12515@marabou.research.att.com>

On Tue, 5 Aug 2003, Bob Beers wrote:

> Ok, seems to work, what is "Plug record length mismatch"? Should I
> worry?  Card is working fine after the upgrade. Here's the screen
> capture:

The length of the data to be substituted in the firmware is not equal to
the length of the corresponding item in the PDA.  The Intersil
documentation says it's not OK, but it looks like they allow some
sloppiness in their own designs.

> srec summary for PK010101.HEX
> Component: 0x0015 1.1.1 (primary firmware)
[snip]
> Verifying update compatibility and combining data:
> Plug record length mismatch (PDR=0x0001): 12 != 16
> ==> extend from default

PDR 1 is present only in the primary firmware:
S311FF00000001000000CC147E001000000080

                            ^^
This means that the length of the data is 16 bytes.  Your PDA provides
only 12 bytes.  I've seen it myself and I haven't had any problems with
such cards.

Since PDR 1 is merely the manufacturing part number, it shouldn't be a big
deal.

If you find address 0x7E14CC in the primary firmware, you'll see that all
16 bytes starting at that address are binary zeroes.  The first 12 bytes
are filled with the data from the PDA.  The rest are zeroes.

-- 
Regards,
Pavel Roskin



From andreaf  Tue Aug  5 13:59:51 2003
From: andreaf (Andrea G. Forte)
Date: Tue, 5 Aug 2003 16:59:51 -0400 (EDT)
Subject: Linksys Firmware problem.
Message-ID: <200308052059.h75Kxp01018368@cisalpino.cs.columbia.edu>

I have finally installed the hostAP on a laptop with a Linksys WPC11 pcmcia 
card. Everything seemed to work but after rebooting I got a message saying that 
"the secondary card with firmware 1.4.2 does not seem to work in host AP 
mode"..or something similar. I then went on the Linksys site but there is not 
firmware available for the card.
What does all of this mean?
Any suggestions?
Thanks a lot guys.
Andrea



From proski  Tue Aug  5 14:25:41 2003
From: proski (Pavel Roskin)
Date: Tue, 5 Aug 2003 17:25:41 -0400 (EDT)
Subject: Linksys Firmware problem.
In-Reply-To: <200308052059.h75Kxp01018368@cisalpino.cs.columbia.edu>
References: <200308052059.h75Kxp01018368@cisalpino.cs.columbia.edu>
Message-ID: <Pine.LNX.4.56.0308051718480.13264@marabou.research.att.com>

On Tue, 5 Aug 2003, Andrea G. Forte wrote:

> I have finally installed the hostAP on a laptop with a Linksys WPC11
> pcmcia card. Everything seemed to work but after rebooting I got a
> message saying that "the secondary card with firmware 1.4.2 does not
> seem to work in host AP mode"..or something similar. I then went on the
> Linksys site but there is not firmware available for the card. What does
> all of this mean? Any suggestions?

Firmware 1.4.2 has a bug fatal for the Host AP mode.  Linksys doesn't
care about this bug because they sell their cards to be used as stations,
not as access points.

Linksys cards use Prism 2.5 chipset.  The best firmware for this chipset
is 1.7.4.  Primary firmware should also be updated, to version 1.1.1.

You can extract both from
http://www.red-bean.com/~proski/firmware/1.7.4.tar.gz and flash them:

prism2_srec -f wlan0 pk010101.hex sf010704.hex

You need the CVS version of HostAP to do it.  Alternatively, you can use
some other software to upgrade the firmware, for example winupdate.

You can read list archives and this HOWTO:
http://linux.junsun.net/intersil-prism/index.html

-- 
Regards,
Pavel Roskin



From jared  Tue Aug  5 16:53:40 2003
From: jared (Jared Brokaw)
Date: Tue, 5 Aug 2003 17:53:40 -0600
Subject: prism cards
References: <1081.200.63.198.49.1060006979.squirrel@webmail.linuxpowered.org>
	<1060067821.1949.3.camel@galvatron.localdomain>
Message-ID: <016301c35bac$cbd51db0$0201a8c0@VECTOR>

SMC recently released a 200mW card based on prism 2.5.  Model number escapes
me but I think it's the only 200mW card they have.

jb

----- Original Message ----- 
From: "Sitsofe Wheeler" <sits at sucs.org>
To: "Vicente Paredes" <vicente.paredes at gruein.com>
Cc: <hostap at shmoo.com>
Sent: Tuesday, August 05, 2003 1:17 AM
Subject: Re: prism cards


> On Mon, 2003-08-04 at 15:22, Vicente Paredes wrote:
> > Hello
> >
> > I have been looking for prism based wireless cards, but i havent find
> > them. Actually exists card with this chip?
> Try checking the linux-wlan wifi card list:
> http://www.linux-wlan.org/docs/wlan_adapters.html4.html
>
> -- 
> Sitsofe | http://sucs.org/~sits/
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
>



From jkmaline  Tue Aug  5 20:12:42 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 5 Aug 2003 20:12:42 -0700
Subject: Workaround for some SMP stability issues - request for testing
Message-ID: <20030806031242.GA4734@jm.kir.nu>

Thanks to all the testing Michael Vallaly did with couple of patches to
Host AP driver, I think I now have quite a bit more information about
the stability issues with hostap_pci on SMP systems. It looks like there
are two separate issues. 1) Something is corrupting the information
transfered between card and driver which then results in frequent wlan
hw resets. 2) hw_reset with hostap_pci on SMP system seems to hang the
system completely in some cases (completely enough to even prevent NMI
watchdog from detecting hang).

It looks like the major cause for frequent resets was in fid register
(RX, TX, TX Error, AllocFid) getting corrupted. I do not have any
explanation for this apart from hardware/firmware bug. It looks like
consecutive reads of the fid registers results in different results even
though that register should not change before the event is acknowledged.

I added code that will try its best to make sure that the fid register
read will return correct fid number. This workaround will read the
register three times and will return the value only if at least two of
the reads returns the same value. This will be repeated up to five
times.

The workaround seemed to eliminate more or less all corrupted fid values
in the test system. Consequently, there was no need to reset the
hardware and no host system hangs.

I added the workaround and test code into CVS and I would like to ask
people with SMP systems to test the CVS snapshot version and report what
they see in kernel log ('dmesg' output) and whether they see any system
hangs or in general changes to the previous versions of the driver.

In addition to the fid read workaround, I also changed TX fid array
handling to use heavier locking. Previously used locking may have been
insufficient on SMP systems. This change alone was also able to reduce
the number of hardware resets, but this may have been do to changed
timing (added latency due to heavier locking). Anyway, fid reads were
still producing corrupted results.


So far, I have mostly concentrated on findind out what is causing the
resets. I will next try to figure out what could be done about the
hw_reset and its relation to complete host system lockup.

-- 
Jouni Malinen                                            PGP id EFC895FA



From mrcool  Tue Aug  5 20:44:36 2003
From: mrcool (Jerry)
Date: Tue, 5 Aug 2003 22:44:36 -0500
Subject: Failed flash.  Prism2.5 Senaeo 2511cd plus  
Message-ID: <002001c35bcd$0f572ae0$bf00a8c0@Liza>

I would appreciate some guidance please:

tried to flash my Senaeo card to 1.7.4, failed.  I was pumped by the recent posts about flashing to the most recent firmware, so i gathered what i thought i needed to flash to 1.7.4.
Latest CVS, and prism2_srec, firmware files pk010101.hex, and sf010704.hex.  The card is a NCCID:  800c, so, to the best of my knowledge  those were (are) the proper firmware files for this card.  It was in a PLX adapter, and ram dl to 1.5.6 at the time of the "incedent".

Well, without -f to test it gave what looked like a common output, mentioned something about a few small things that looked like they were more warnings than anything else (sorry, it was remote, i dont have that mesg at this point if i can find it in a log somewhere ill post it), and it ended with 'OK' which i incorrectly took to mean that this was ok to use.
After many second thoughts (but not enough ;) i put the -f in.  flash failed. ...sigh...

Please, no flames, just some guidance.   I have been searching the archives (more recent stuff) and have all sorts of firmware, winupdate (2), and even the dos util (i havent tried this yet, but i will).  Windows will find the card and make the "beep beep" sounds, but it has a blat on device managler (driver installs win98), both the winupdates do nothing but make the cursor go to the hourglass for a few seconds then nothing, doenst even install, aparently. (0.5, and 0.7 winupdates).

Do i need special hardware to fix this? pcmcia? PLX? I have googled it, with most pointing back to the same documentation, (pavel's or raf's, and sown.org).  I seen to remember some more about dead cards from earlier hostap mesgs, so ill search them more tomorrow, in the meantime, if anyone has some specific ideas or advice, all help will be appreciated.

Thanks.

Jerry  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030805/4f89a6be/attachment.htm 


From jkmaline  Tue Aug  5 21:04:53 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 5 Aug 2003 21:04:53 -0700
Subject: Failed flash.  Prism2.5 Senaeo 2511cd plus
In-Reply-To: <002001c35bcd$0f572ae0$bf00a8c0@Liza>
References: <002001c35bcd$0f572ae0$bf00a8c0@Liza>
Message-ID: <20030806040453.GA29767@jm.kir.nu>

On Tue, Aug 05, 2003 at 10:44:36PM -0500, Jerry wrote:

> tried to flash my Senaeo card to 1.7.4, failed.  I was pumped by the recent posts about flashing to the most recent firmware, so i gathered what i thought i needed to flash to 1.7.4.
> Latest CVS, and prism2_srec, firmware files pk010101.hex, and sf010704.hex.  The card is a NCCID:  800c, so, to the best of my knowledge  those were (are) the proper firmware files for this card.  It was in a PLX adapter, and ram dl to 1.5.6 at the time of the "incedent".

What where the firmware versions (PRI and STA) in the flash? Did you try
downloading both PRI and STA images with one prism2_srec command? I
don't think I have tested flash download when running RAM-downloaded
image, so that is a possible reason for problems.

> Well, without -f to test it gave what looked like a common output, mentioned something about a few small things that looked like they were more warnings than anything else (sorry, it was remote, i dont have that mesg at this point if i can find it in a log somewhere ill post it), and it ended with 'OK' which i incorrectly took to mean that this was ok to use.

Getting the exact list of those few small things would be useful for
finding out what went wrong. That OK is supposed to mean that the
firmware image is indeed suitable for the card.

> After many second thoughts (but not enough ;) i put the -f in.  flash failed.

Did you happen to have the error message anywhere? Both from prism2_srec
and the driver ('dmesg')? They would be quite useful in figurin out what
happened.

> Please, no flames, just some guidance.   I have been searching the archives (more recent stuff) and have all sorts of firmware, winupdate (2), and even the dos util (i havent tried this yet, but i will).  Windows will find the card and make the "beep beep" sounds, but it has a blat on device managler (driver installs win98), both the winupdates do nothing but make the cursor go to the hourglass for a few seconds then nothing, doenst even install, aparently. (0.5, and 0.7 winupdates).

So, Windows fails to initialize the driver. What about Linux (with the
latest CVS snapshot of Host AP driver)? Does hostap_plx report "no
device found"? What do you get in kernel log ('dmesg')?

> Do i need special hardware to fix this?

Prism2.5 should have software controlled Genesis mode, so no special
hardware should be needed. If the primary is still OK and able to start
without STA firmware, Host AP driver should be able to initialize the
card. If this is not the case, you would need to initialize the card by
first downloading initial firmware to RAM using Genesis mode. Host AP
driver does not support this, so you would probably need to use the DOS
tools for this.

-- 
Jouni Malinen                                            PGP id EFC895FA



From sardana  Tue Aug  5 22:22:36 2003
From: sardana (Bobby Sardana)
Date: Tue, 05 Aug 2003 22:22:36 -0700
Subject: Failed flash.  Prism2.5 Senaeo 2511cd plus
References: <002001c35bcd$0f572ae0$bf00a8c0@Liza>
Message-ID: <3F30909C.8010305@obsoft.com>

Hello Jerry,

Jerry wrote:
> tried to flash my Senaeo card to 1.7.4, failed.  I was pumped by the 
> recent posts about flashing to the most recent firmware, so i gathered 
> what i thought i needed to flash to 1.7.4.

I have been able to flash the 0x800c NIC. Check the following URL:

http://lists.shmoo.com/pipermail/hostap/2003-July/003575.html

regards,

Bobby Sardana.
sardana at obsoft.com




From lanev007  Tue Aug  5 23:19:35 2003
From: lanev007 (=?iso-8859-1?q?veronica=20lane?=)
Date: Wed, 6 Aug 2003 07:19:35 +0100 (BST)
Subject: hostap distro cd
Message-ID: <20030806061935.22621.qmail@web80710.mail.yahoo.com>

hi! i have created my pc as an access point using a zcomax card. i have also installed wireless tools so that i can be able to play around with my hostap. 
 
im planning of doing something that could develop and improve the features of hostap.  is there somebody who can help me with this? 
 
here are plans of what to do with my hostap:
1.  I'm planning to develop a gui based monitoring system for my hostap so that i can track down my clients. i have tried these viewing through the command "iwspy" but it only indicates the MAC addresses of the clients. is there some kind of software (opensource) that i can download inorder for me to view my clients through their ip_address other than MAC address?
 
2.  As of the moment, im also trying to research on how i can take control on these clients. such as how can i limit the bandwidth that they consume using my pc as their hostap.  i wanted someone to give me websites and other resources on how i can be able to view the consumption of bandwidth of my clients.
 
3.  lastly, me and a group of mine wants to create a hostap distribution cd. in this cd, it will already contain the configured kernel for the pc to run on a hostap mode and the driver itself.  probably, we will create this through various rpm's or autoconfiguration strategy. at this point in time, i have no idea yet on how to start. can somebody also assist me with this.
 
with these in mind, i would definitely be needing help. i would appreciate all your assistance. thank you very much and i will hoping for a reply ASAP.


---------------------------------
Want to chat instantly with your online friends??Get the FREE Yahoo!Messenger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030806/84025d3e/attachment.htm 


From xfesty  Wed Aug  6 00:12:23 2003
From: xfesty (Ryan Verner)
Date: Wed, 6 Aug 2003 16:42:23 +0930
Subject: hostap distro cd
In-Reply-To: <20030806061935.22621.qmail@web80710.mail.yahoo.com>
References: <20030806061935.22621.qmail@web80710.mail.yahoo.com>
Message-ID: <20030806071223.M10166@computeraddictions.com.au>

Hiya,

> 3.  lastly, me and a group of mine wants to create a hostap 
> distribution cd. in this cd, it will already contain the configured 
> kernel for the pc to run on a hostap mode and the driver itself. 
>  probably, we will create this through various rpm's or 
> autoconfiguration strategy. at this point in time, i have no idea 
> yet on how to start. can somebody also assist me with this.

SydneyWireless (evilbunny) made something like this going back a year or so now, maybe more - 
preconfigured Debian with hostap and all goodies.  I personally never used it, but the ISO was only 
40MB or so.

I'm sure plenty of other wireless groups have done this as well.

I'd research this before going ahead with yours...

R

--
Open WebMail Project (http://openwebmail.org)



From bjoern  Wed Aug  6 00:51:31 2003
From: bjoern (=?ISO-8859-1?Q?Bj=F6rn_Giesler?=)
Date: Wed, 6 Aug 2003 09:51:31 +0200
Subject: HostAP & Ethernet Converter
Message-ID: <CB5AD84A-C7E2-11D7-A951-003065B28BDE@giesler.de>

Hi,

I've been running HostAP for a while (Prism 2.5) with several clients 
in my home net, and first of all, it works great! Thanks a lot!

Now, I'm trying to hook up my trusty old NeXT using a Lucent/Orinoco 
Ethernet Converter, which "kind of" works -- I get the first few 
packets of any TCP connection, followed by a "reset by peer". Hooking 
the machine up using TP cable works, so I'm pretty certain that the EC 
is to blame. Pings work, btw.

Are there any known incompatibilities at work here? Which firmware 
should I be using? Does anyone have a similar setup working?

Thanks in advance,
		--Bj?rn


From jjo-hostap  Wed Aug  6 05:32:42 2003
From: jjo-hostap (JuanJo Ciarlante)
Date: Wed, 6 Aug 2003 09:32:42 -0300
Subject: BUG: weird behaviour after killing hostapd in latest CVS.
In-Reply-To: <20030805022749.GC3211@jm.kir.nu>;
	from jkmaline@cc.hut.fi on Mon, Aug 04, 2003 at 07:27:49PM -0700
References: <20030804142108.K31149@mendoza.gov.ar>
	<20030805022749.GC3211@jm.kir.nu>
Message-ID: <20030806093242.H18154@mendoza.gov.ar>

On Mon, Aug 04, 2003 at 07:27:49PM -0700, Jouni Malinen wrote:
> ...
> Which kernel version are you using?
> Which station firmware version are you using?
> Did you have wlan0sta interface UP when killing hostapd? If yes, what
> happens if you first set it down and only after that kill hostapd?

Kernel 2.4.20, firmware 1.7.4 (flashed prism2.5 PCI)  forced promisc for
hostapd+assoc_ap_addr (set_rid_word 64645 1) on a P166.

Indeed ... setting down wlan0 and wlan0sta interface BEFORE killing hostapd
behaves correctly as 0.0.4 did (recall I'm using assoc_ap_addr feature).

Some side albeit useful notes: 
 Our wireless community uses a Nokia A032 AP as a master wireless bridge,
 it doesn't  have its eth interface connected at all.
  - suspiciuosly TX speed (to AP) _seems_ somewhat better, about 20%
    (informally tested with netperf) with hostapd+assoc_ap_addr instead of
    managed mode (?)
  - hostapd+assoc_ap_addr works Ok if my macaddr is declared 
    as "normal" sta ("nid" in a032's config); if I declare my macaddr as
    "bridge" in the a032 my frames don't get re-TX by the AP.

Thanks for the excellent work... regards!

-- 
--Juanjo

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



From vda  Wed Aug  6 06:06:58 2003
From: vda (Denis Vlasenko)
Date: Wed, 6 Aug 2003 16:06:58 +0300
Subject: Workaround for some SMP stability issues - request for testing
In-Reply-To: <20030806031242.GA4734@jm.kir.nu>
References: <20030806031242.GA4734@jm.kir.nu>
Message-ID: <200308061257.h76CvQp28550@Port.imtp.ilyichevsk.odessa.ua>

On 6 August 2003 06:12, Jouni Malinen wrote:
> Thanks to all the testing Michael Vallaly did with couple of patches to
> Host AP driver, I think I now have quite a bit more information about
> the stability issues with hostap_pci on SMP systems. It looks like there
> are two separate issues. 1) Something is corrupting the information
> transfered between card and driver which then results in frequent wlan
> hw resets. 2) hw_reset with hostap_pci on SMP system seems to hang the
> system completely in some cases (completely enough to even prevent NMI
> watchdog from detecting hang).

Thank you guys sooo much for attacking this!
 
> It looks like the major cause for frequent resets was in fid register
> (RX, TX, TX Error, AllocFid) getting corrupted. I do not have any
> explanation for this apart from hardware/firmware bug. It looks like
> consecutive reads of the fid registers results in different results even
> though that register should not change before the event is acknowledged.
> 
> I added code that will try its best to make sure that the fid register
> read will return correct fid number. This workaround will read the
> register three times and will return the value only if at least two of
> the reads returns the same value. This will be repeated up to five
> times.

You are obviously talking about this code:

/* Some SMP systems have reported number of odd errors with hostap_pci. fid
 * register has changed values between consecutive reads for an unknown reason.
 * This should really not happen, so more debugging is needed. This test
 * version is a big slower, but it will detect most of such register changes
 * and will try to get the correct fid eventually. */
#define EXTRA_FID_READ_TESTS

static inline u16 prism2_read_fid_reg(struct net_device *dev, u16 reg)
{
#ifdef EXTRA_FID_READ_TESTS
        u16 val, val2, val3;
        int i;

        for (i = 0; i < 10; i++) {
                val = HFA384X_INW(reg);
                val2 = HFA384X_INW(reg);
                val3 = HFA384X_INW(reg);

                if (val == val2 && val == val3)
                        return val;

                printk(KERN_DEBUG "%s: detected fid change (try=%d, reg=%04x):"
                       " %04x %04x %04x\n",
                       dev->name, i, reg, val, val2, val3);
                if ((val == val2 || val == val3) && val != 0)
                        return val;
                if (val2 == val3 && val2 != 0)
                        return val2;
        }
        printk(KERN_WARNING "%s: Uhhuh.. could not read good fid from reg "
               "%04x (%04x %04x %04x)\n", dev->name, reg, val, val2, val3);
        return val;
#else /* EXTRA_FID_READ_TESTS */
        return HFA384X_INW(reg);
#endif /* EXTRA_FID_READ_TESTS */
}

> The workaround seemed to eliminate more or less all corrupted fid values
> in the test system. Consequently, there was no need to reset the
> hardware and no host system hangs.

Corruption must be triggered by something. Most probably other CPU.

Maybe this patch will give us some insights. Tries to show irq
races and which processor did it.
Applies to CVS. Compile tested.
--
vda

--- hostap_hw.c.orig	Wed Aug  6 05:50:00 2003
+++ hostap_hw.c	Wed Aug  6 16:03:12 2003
@@ -2199,11 +2199,16 @@
  * and will try to get the correct fid eventually. */
 #define EXTRA_FID_READ_TESTS
 
+#ifdef EXTRA_FID_READ_TESTS
+static int interrupts_nested=0; 
+static int intr_cpu[16];
+#endif
+
 static inline u16 prism2_read_fid_reg(struct net_device *dev, u16 reg)
 {
 #ifdef EXTRA_FID_READ_TESTS
 	u16 val, val2, val3;
-	int i;
+	int i,j;
 
 	for (i = 0; i < 10; i++) {
 		val = HFA384X_INW(reg);
@@ -2214,8 +2219,14 @@
 			return val;
 
 		printk(KERN_DEBUG "%s: detected fid change (try=%d, reg=%04x):"
-		       " %04x %04x %04x\n",
-		       dev->name, i, reg, val, val2, val3);
+		       " %04x %04x %04x. cpu %d. interrupts nested: %d\n",
+		       dev->name, i, reg, val, val2, val3,
+		       smp_processor_id(),
+		       interrupts_nested
+		       );
+		for(j=0; j<interrupts_nested; j++)
+			printk(KERN_DEBUG "intr_cpu[%d]=%d\n", j, intr_cpu[j]);
+			
 		if ((val == val2 || val == val3) && val != 0)
 			return val;
 		if (val2 == val3 && val2 != 0)
@@ -2957,13 +2968,17 @@
 	local_info_t *local = (local_info_t *) dev->priv;
 	int events = 0;
 	u16 ev;
+	
+#ifdef EXTRA_FID_READ_TESTS
+	intr_cpu[interrupts_nested++] = smp_processor_id();
+#endif
 
 	prism2_io_debug_add(dev, PRISM2_IO_DEBUG_CMD_INTERRUPT, 0, 0);
 
 	if (local->func->card_present && !local->func->card_present(local)) {
 		printk(KERN_DEBUG "%s: Interrupt, but dev not OK\n",
 		       dev->name);
-		return IRQ_HANDLED;
+		goto return_IRQ_HANDLED;
 	}
 
 	prism2_check_magic(local);
@@ -2972,11 +2987,11 @@
 		ev = HFA384X_INW(HFA384X_EVSTAT_OFF);
 		if (ev == 0xffff) {
 			if (local->shutdown)
-				return IRQ_HANDLED;
+				goto return_IRQ_HANDLED;
 			HFA384X_OUTW(0xffff, HFA384X_EVACK_OFF);
 			printk(KERN_DEBUG "%s: prism2_interrupt: ev=0xffff\n",
 			       dev->name);
-			return IRQ_HANDLED;
+			goto return_IRQ_HANDLED;
 		}
 
 		ev &= HFA384X_INW(HFA384X_INTEN_OFF);
@@ -2997,7 +3012,7 @@
 			if (ev & HFA384X_EV_CMD)
 				goto next_event;
 			if ((ev & HFA384X_EVENT_MASK) == 0)
-				return IRQ_HANDLED;
+				goto return_IRQ_HANDLED;
 			if (local->dev_enabled && (ev & ~HFA384X_EV_TICK) &&
 			    net_ratelimit()) {
 				printk(KERN_DEBUG "%s: prism2_interrupt: hw "
@@ -3012,7 +3027,7 @@
 				       " (!dev_enabled)" : "");
 			}
 			HFA384X_OUTW(ev, HFA384X_EVACK_OFF);
-			return IRQ_HANDLED;
+			goto return_IRQ_HANDLED;
 		}
 
 		if (ev & HFA384X_EV_TICK) {
@@ -3071,7 +3086,17 @@
 		}
 	}
 	prism2_io_debug_add(dev, PRISM2_IO_DEBUG_CMD_INTERRUPT, 0, 1);
+
+#ifdef EXTRA_FID_READ_TESTS
+	interrupts_nested--;
+#endif
 	return IRQ_RETVAL(events);
+	
+return_IRQ_HANDLED:
+#ifdef EXTRA_FID_READ_TESTS
+	interrupts_nested--;
+#endif
+	return IRQ_HANDLED;
 }
 
 



From mrcool  Wed Aug  6 07:02:41 2003
From: mrcool (Jerry)
Date: Wed, 6 Aug 2003 09:02:41 -0500
Subject: Failed flash: Senaeo 2511 cd plus.  Follow-up
Message-ID: <002001c35c23$6a87c7c0$4104000a@ns>

I got lucky.

The dos based flash utility worked.  The utility I used, I understood to be for the prism2, as with the firmware included with it.  Well, in order to get into genesis mode, you need to load initial firmware first which allows genesis mode.  Initial firmware is named with an "i" first, just like "p" is for primary, and "s" is for secondary.  I didnt find any besides the 2 hex files included with the flash utility, the files have a different naming convention than what the primary or secondary have, but one had a "1" in it and the other had a "4", so I guessed that the 4 was a later version and tried it.

To use the flash utility, you need to load a legacy driver for the bridge.  To do this you run the "legacy.exe" file included with the flash utility.  When I initially ran this, it gave a short message then asked if a wanted to reboot, I told it no...which apparently works.  The sequence of commands to accomplish the resurrection of the card follows.  Im at work, so the firmware filenames I'll use may not be 100% accurate, but the command itself will be correct...

legacy                                   <-- a must for the pcmcia bridge to work
flash -5v -i ic4000c0.hex          <-- load initial fw and enter genesis mode.  No problems...
flash -5v -g -d pk010101.hex    <-- this ended with a "download failed" !!! 
flash -5v -g -d sf010506.hex     <-- so did this...

At this point I figured that i had done no good and everything was basically the same, if not worse...So I issued this command to show the status of the card...

flash -5v -s                             

I had done this once before flashing anything and had gotten some memory and pda dumps that scrolled out of sight before they could be useful, and ended with some debug info...(I presume that is what it was).  Well, this time, I got the dumps but they seemed to be shorter, and no debug info.  It ended showing the nccid, primary, and secondary as 800C, 1.1.1, and 1.5.6 respectively!!  Which would be correct! But it HAD said that both downloads had failed, so I was skeptical, but I ctrl-alt-del and rebooted into windows... no blat!!  AND the light was on and flashing looking for a network.   whoot!! whoot!!  :)  

At this point I took the card and put it back into the machine it belonged in, and booted it up.  I had my wlan0 interface back, dmesg reported correct pri and sec firmware, and it was looking for the network.  I figured that I could fix it, so I went ahead and flashed on up to 1.7.4 (what I was trying to do to begin with) with prism2_srec.

prism2_srec wlan0 -f sf010704.hex

This went smoothly, with no errors reported, and ended showing the proper pri and sec firmware.  I then rebooted to make sure that everything comes back up properly, which it did with 1.7.4 firmware!!  YAY!!

Unfortunately I have to climb back up my tower to put my machine back in place, so I dont REALLY know if everything works properly or not, but the software/drivers load and seem to work properly, so Im hoping everything's fine, I'll let you know.

As far as debug info on why it failed in the first place.  Im sorry I didnt save it at the time, but that wasnt what was on my mind then.  I dont know that much linux log files, if anyone does, and knows where this info might be, (SuSE 8.0, minimum install, everything "stock" except hostap) let me know, and ill try to find and post it for you all... 

Thanks everyone for your help and attention, and if this helps anyone either NOT kill their card, or resurrect a dead one, then alls not in vain...

Thanks all

Jerryf

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030806/00c468cc/attachment.htm 


From zach  Wed Aug  6 07:17:58 2003
From: zach (Zach Chambers)
Date: Wed, 06 Aug 2003 10:17:58 -0400
Subject: Question about Noise/Interference
References: <CB5AD84A-C7E2-11D7-A951-003065B28BDE@giesler.de>
Message-ID: <3F310E16.6080202@skystratus.com>


This is probably the wrong forum for this question, however, some of 
this may or may not be specific to the hostap driver.  I have a few 
access points running hostap-0.0.3 which have been running great for 
nearly a year. I'm graphing the signal and silence levels of each access 
point. Lately  I seem to be receiving interference from external 
sources.  The interference incidents seem to fall into two categories:

1) Elevated noise (silence- as reported by the hostap driver in 
/proc/net/hostap/wlan0/macaddress) levels reaching up to 35 on whatever 
scale is used there.  (I'm guessing around 166.)  For this type of 
incident there is no change in the signal level reported (it usually 
hovers around 111.)  During this type of incident there is no apparent 
affect on the connectivity.  The following observations have been made 
during the incidents:
    * No additional 802.11b devices have been detected on or near the 
same channel.
    * No additional 802.11b devices have been detected at all.
    * The noise does seem to be limited to one channel.

2) Elevated noise (silence- as reported by the hostap driver in 
/proc/net/hostap/wlan0/macaddress) levels reaching up to 35 on whatever 
scale is used there.  (I'm guessing around 166.) For this type of 
incident there is a proportional gain in the reported signal level. 
 During this type of incident there is severe packet loss on the 
connection, and the hostap driver attempts to lower the connection rate. 
 The following observations have been made during the incidents.
    * No additional 802.11b devices have been detected on or near the 
same channel.
    * No additional 802.11b devices have been detected at all.
    * The noise does seem to be limited to one channel.

I would like to begin documenting this type of interference and possible 
work-arounds.  If anyone is willing to comment on this, or can suggest a 
better forum, it would be greatly appreciated.

Thanks,

-Zach.



From chrisc  Wed Aug  6 07:29:06 2003
From: chrisc (Chris Cox)
Date: Wed, 6 Aug 2003 09:29:06 -0500 (CDT)
Subject: Question about Noise/Interference
In-Reply-To: <3F310E16.6080202@skystratus.com>
Message-ID: <Pine.LNX.4.44.0308060928160.7019-100000@smudge.chris.org>

On Wed, 6 Aug 2003, Zach Chambers wrote:
>     * No additional 802.11b devices have been detected on or near the 
> same channel.
>     * No additional 802.11b devices have been detected at all.
>     * The noise does seem to be limited to one channel.

My guess would be some other part 15 device, most probably a new cordless 
telephone.
-- 
73  Chris Cox  N0UK, G4JEC, ex-AB0CN, ex-G8PTC  RNARS #1157  EN34jv

chrisc at Chris.Org        Ping Jockey's do it until they HEAR the burn...
  WWW Home Page: http://WWW.Chris.Org/   http://www.pingjockey.net 
Cultural observation:
	Europeans think 100 miles is a long way;
	Americans think 100 years is a long time!



From proski  Wed Aug  6 09:53:31 2003
From: proski (Pavel Roskin)
Date: Wed, 6 Aug 2003 12:53:31 -0400 (EDT)
Subject: BUG: weird behaviour after killing hostapd in latest CVS.
In-Reply-To: <20030806093242.H18154@mendoza.gov.ar>
References: <20030804142108.K31149@mendoza.gov.ar>
	<20030805022749.GC3211@jm.kir.nu>
	<20030806093242.H18154@mendoza.gov.ar>
Message-ID: <Pine.LNX.4.56.0308061246340.3486@marabou.research.att.com>

On Wed, 6 Aug 2003, JuanJo Ciarlante wrote:

> On Mon, Aug 04, 2003 at 07:27:49PM -0700, Jouni Malinen wrote:
> > ...
> > Which kernel version are you using?
> > Which station firmware version are you using?
> > Did you have wlan0sta interface UP when killing hostapd? If yes, what
> > happens if you first set it down and only after that kill hostapd?
>
> Kernel 2.4.20, firmware 1.7.4 (flashed prism2.5 PCI)  forced promisc for
> hostapd+assoc_ap_addr (set_rid_word 64645 1) on a P166.

I could reproduce the panic on Linux 2.6.0-test2-bk5 with CVS HostAP.  The
sequence:

cardctl insert
hostapd hostapd.conf
ifconfig wlan0 up
killall hostapd

It's not needed to bring wlan0sta up.  wlan0ap was up already.

The panic has been captured on the serial console.  It's attached.  I'm
not sure if I'll be able to debug it soon.

It appears that the crash happens very early in prism2_rx_80211.

-- 
Regards,
Pavel Roskin
-------------- next part --------------
wlan0: enabling hostapd mode          
wlan0: Registered netdevice wlan0ap for AP management
wlan0: Registered netdevice wlan0sta for STA use     
wlan0: disabling hostapd mode                   
wlan0: Netdevice wlan0ap unregistered
wlan0: Netdevice wlan0sta unregistered
wlan0: enabling host<1>Unable to handle kernel NULL pointer dereference at virtual address
 00000060
 printing eip:
d0883772      
*pde = 00000000
Oops: 0000 [#1]
CPU:    0      
EIP:    0060:[<d0883772>]    Not tainted
EFLAGS: 00010282                        
EIP is at prism2_rx_80211+0x12/0x540 [hostap]
eax: 00000000   ebx: cf56bac4   ecx: cc5fdc20   edx: 00000000
esi: cf56bac4   edi: cf0910fc   ebp: cc5fdb08   esp: cc5fdac4
ds: 007b   es: 007b   ss: 0068                               
Process hostapd (pid: 1052, threadinfo=cc5fc000 task=ca308780)
Stack: c0289505 cfee8308 00000282 cf0b3cb0 cf0910fc cf0910fc cc5fdaf0 c0289505 
       cfee75c8 cf0b3cb0 00000000 cc5fdb08 c0289576 cf0b3cb0 cf56bac4 cf0910fc 
       cf0910fc cc5fdc00 d0884236 00000000 cf56bac4 cc5fdc20 00000001 cf56bac4 
Call Trace:                                                                    
 [<c0289505>] kfree_skbmem+0x25/0x30
 [<c0289505>] kfree_skbmem+0x25/0x30
 [<c0289576>] __kfree_skb+0x66/0xe0 
 [<d0884236>] hostap_80211_rx+0x1a6/0x1610 [hostap]
 [<c02c302a>] tcp_v4_do_rcv+0x12a/0x130            
 [<c014a944>] check_poison_obj+0x54/0x1d0
 [<c014cc3d>] __kmalloc+0x17d/0x1d0      
 [<c0289308>] alloc_skb+0x48/0xf0  
 [<d08976a9>] hostap_rx_skb+0x159/0x190 [hostap_cs]
 [<c012aeb6>] update_process_times+0x46/0x50       
 [<d08977d9>] hostap_rx_tasklet+0xf9/0x190 [hostap_cs]
 [<c0111c58>] timer_interrupt+0x88/0x220              
 [<c0126176>] tasklet_action+0x46/0x70  
 [<c0125f95>] do_softirq+0xb5/0xc0    
 [<c010c3dc>] do_IRQ+0x20c/0x350  
 [<c010a26c>] common_interrupt+0x18/0x20
 [<c023d7c9>] serial_in+0x29/0x70       
 [<c01e1814>] __delay+0x14/0x20  


From chhabra  Wed Aug  6 10:25:46 2003
From: chhabra (Madhusudan Singh)
Date: Wed, 06 Aug 2003 13:25:46 -0400
Subject: Netgear MA311
Message-ID: <3F313A1A.3020700@eecs.umich.edu>

Hi
	I recently purchased an MA311 Netgear Wireless PCI card. I wish to set 
it up as an Access Point using hostap drivers, and use WEP encryption so 
that my communications are secure.

	Any pointers ?

Thanks,

MS



From jared  Wed Aug  6 11:26:06 2003
From: jared (JB)
Date: Wed, 6 Aug 2003 12:26:06 -0600
Subject: Netgear MA311
References: <3F313A1A.3020700@eecs.umich.edu>
Message-ID: <04e901c35c48$3349a150$0201a8c0@VECTOR>

> it up as an Access Point using hostap drivers, and use WEP encryption so 
> that my communications are secure.
> 

WEP or no WEP, your communications will not be secure.



From eduardo  Wed Aug  6 18:22:25 2003
From: eduardo (Eduardo Kaftanski)
Date: Wed, 6 Aug 2003 21:22:25 -0400
Subject: Workaround for some SMP stability issues - request for testing
In-Reply-To: <20030806031242.GA4734@jm.kir.nu>
References: <20030806031242.GA4734@jm.kir.nu>
Message-ID: <20030807012225.GA27893@enriqueto.nn.cl>

> 
> The workaround seemed to eliminate more or less all corrupted fid values
> in the test system. Consequently, there was no need to reset the
> hardware and no host system hangs.
> 
> I added the workaround and test code into CVS and I would like to ask
> people with SMP systems to test the CVS snapshot version and report what
> they see in kernel log ('dmesg' output) and whether they see any system
> hangs or in general changes to the previous versions of the driver.
> 

I am upgrading to CVS, will flash 1.7.4 and the try the SMP version.
Will report ASAP.


-- 
Eduardo Kaftanski
eduardo at linuxcenter.cl
Red Hat Certified Engineer
Gerente Ingenieria LinuxCenter S.A.
Canada 239 5to Piso, Providencia, Stgo de Chile.
http://www.linuxcenter.cl 2745000



From chhabra  Wed Aug  6 18:27:03 2003
From: chhabra (Madhusudan Singh)
Date: Wed, 06 Aug 2003 21:27:03 -0400
Subject: Problem compiling hostap for a PCI card
Message-ID: <3F31AAE7.5090508@eecs.umich.edu>

Hi
    I am trying to set up at Access Point using a Netgear  MA311 PCI 
card. An attempt to compile fails spectacularly :

    [root at sggs hostap-0.0.4]# make hostap
Makefile:38: WARNING: No kernel PCMCIA support found and PCMCIA_PATH is 
not defined
gcc -I/usr/src/linux/include -O2 -D__KERNEL__ -DMODULE -Wall -g -c  
-DMODVERSIONS -include /usr/src/linux/include/linux/modversions.h 
-fomit-frame-pointer -E -D__GENKSYMS__ driver/modules/hostap.c | \
        /sbin/genksyms -k 2.4.20 > driver/modules/hostap.ver
In file included from driver/modules/hostap.c:21:
/usr/src/linux/include/linux/module.h:15:1: warning: "_set_ver" redefined
In file included from /usr/src/linux/include/linux/modversions.h:3,
                 from <command line>:1:
/usr/src/linux/include/linux/modsetver.h:9:1: warning: this is the 
location of the previous definition
gcc -I/usr/src/linux/include -O2 -D__KERNEL__ -DMODULE -Wall -g -c  
-DMODVERSIONS -include /usr/src/linux/include/linux/modversions.h 
-fomit-frame-pointer -E -D__GENKSYMS__ driver/modules/hostap_crypt.c | \
        /sbin/genksyms -k 2.4.20 > driver/modules/hostap_crypt.ver
In file included from driver/modules/hostap_crypt.c:18:
/usr/src/linux/include/linux/module.h:15:1: warning: "_set_ver" redefined
In file included from /usr/src/linux/include/linux/modversions.h:3,
                 from <command line>:1:
/usr/src/linux/include/linux/modsetver.h:9:1: warning: this is the 
location of the previous definition
gcc -I/usr/src/linux/include -include driver/modules/hostap_crypt.ver 
-include driver/modules/hostap.ver -O2 -D__KERNEL__ -DMODULE -Wall -g 
-c  -DMODVERSIONS -include /usr/src/linux/include/linux/modversions.h 
-fomit-frame-pointer -o driver/modules/hostap.o driver/modules/hostap.c
[root at sggs hostap-0.0.4]# make hostap_pci
Makefile:38: WARNING: No kernel PCMCIA support found and PCMCIA_PATH is 
not defined
make: *** No rule to make target `hostap_pci'.  Stop.


    The machine is a desktop machine. What is all this business about 
PCMCIA support ?

MS

PS : I am now having doubts about whether MA311 is appropriate as an 
Access Point. I have found a few links on the web which state that it is 
so, but nothing in the accompanying documentation says that. I received 
the card earlier today, so I can return it for something else. My 
Netgear MA401 card on my laptop (which is going to be the client) works 
perfectly.



From proski  Wed Aug  6 19:13:39 2003
From: proski (Pavel Roskin)
Date: Wed, 6 Aug 2003 22:13:39 -0400 (EDT)
Subject: Problem compiling hostap for a PCI card
In-Reply-To: <3F31AAE7.5090508@eecs.umich.edu>
References: <3F31AAE7.5090508@eecs.umich.edu>
Message-ID: <Pine.LNX.4.56.0308062200530.690@marabou.research.att.com>

On Wed, 6 Aug 2003, Madhusudan Singh wrote:

> [root at sggs hostap-0.0.4]# make hostap_pci
> Makefile:38: WARNING: No kernel PCMCIA support found and PCMCIA_PATH is
> not defined
> make: *** No rule to make target `hostap_pci'.  Stop.
>
>     The machine is a desktop machine. What is all this business about
> PCMCIA support ?

If a message says "warning", it's not a fatal error.  Most wireless cards
are PCMCIA.  Users are reminded that if they don't have PCMCIA support in
the kernel, they should define PCMCIA_PATH.

The real problem is that you are running "make hostap_pci".  You should
just run "make" for 2.4 and newer kernels or "make pci" for 2.4 and older
kernels.

README clearly needs to be updated for the makefile changes (or maybe
"make pci" and other separate targets should be allowed for 2.6 kernels).

However, I don't see where you found "make hostap_pci".  It's like running
"make foo" and blaming the failure an innocent warning rather than on the
real error message.

-- 
Regards,
Pavel Roskin



From yr.ohm  Wed Aug  6 19:20:03 2003
From: yr.ohm (=?EUC-KR?B?vva/tbb1?=)
Date: Thu, 07 Aug 2003 11:20:03 +0900
Subject: How to change idle-timeout, session-timeout?
Message-ID: <0HJ80002O95J5Z@ms6.samsung.com>


I am using hostap-0.0.3 on AP-side.

>From my test result, the value of idle-timeout is 300 seconds

and I don't know that of session-timeout.

I want to change values and test. 

How to change idle-timeout and session-timeout?

Please help me. 




From chhabra  Wed Aug  6 19:30:47 2003
From: chhabra (Madhusudan Singh)
Date: Wed, 06 Aug 2003 22:30:47 -0400
Subject: Problem compiling hostap for a PCI card
In-Reply-To: <Pine.LNX.4.56.0308062200530.690@marabou.research.att.com>
References: <3F31AAE7.5090508@eecs.umich.edu>
	<Pine.LNX.4.56.0308062200530.690@marabou.research.att.com>
Message-ID: <3F31B9D7.8080209@eecs.umich.edu>



Pavel Roskin wrote:

>On Wed, 6 Aug 2003, Madhusudan Singh wrote:
>
>  
>
>>[root at sggs hostap-0.0.4]# make hostap_pci
>>Makefile:38: WARNING: No kernel PCMCIA support found and PCMCIA_PATH is
>>not defined
>>make: *** No rule to make target `hostap_pci'.  Stop.
>>
>>    The machine is a desktop machine. What is all this business about
>>PCMCIA support ?
>>    
>>
>
>If a message says "warning", it's not a fatal error.  Most wireless cards
>are PCMCIA.  Users are reminded that if they don't have PCMCIA support in
>the kernel, they should define PCMCIA_PATH.
>
>The real problem is that you are running "make hostap_pci".  You should
>just run "make" for 2.4 and newer kernels or "make pci" for 2.4 and older
>kernels.
>
>README clearly needs to be updated for the makefile changes (or maybe
>"make pci" and other separate targets should be allowed for 2.6 kernels).
>
>However, I don't see where you found "make hostap_pci".  It's like running
>"make foo" and blaming the failure an innocent warning rather than on the
>real error message.
>
>  
>
Thanks for the message. I guess I made a typo and then got confused.

I have compiled it successfully now. How do I configure it to act as an 
access point ?

According to :
http://www.unixcircle.com/features/802.11b_freebsd.php

MA311 has an Access Point mode.


Thanks.




From proski  Wed Aug  6 19:59:15 2003
From: proski (Pavel Roskin)
Date: Wed, 6 Aug 2003 22:59:15 -0400 (EDT)
Subject: Problem compiling hostap for a PCI card
In-Reply-To: <3F31B9D7.8080209@eecs.umich.edu>
References: <3F31AAE7.5090508@eecs.umich.edu>
	<Pine.LNX.4.56.0308062200530.690@marabou.research.att.com>
	<3F31B9D7.8080209@eecs.umich.edu>
Message-ID: <Pine.LNX.4.56.0308062258170.1903@marabou.research.att.com>

On Wed, 6 Aug 2003, Madhusudan Singh wrote:

> Thanks for the message. I guess I made a typo and then got confused.
>
> I have compiled it successfully now. How do I configure it to act as an
> access point ?

It's described in the same document as "make pci".  It's called README.

-- 
Regards,
Pavel Roskin



From brock  Wed Aug  6 20:59:20 2003
From: brock (Brock Eastman)
Date: Wed, 6 Aug 2003 20:59:20 -0700
Subject: Issues w/ WDS links in Bridge -- crashes 0.0.4
References: <20030806031242.GA4734@jm.kir.nu>
Message-ID: <00d901c35c98$49d24fd0$9900a8c0@TOSHIBARDLAP>

Hi All,

We have seen hostap in bridge mode doing wds link crash.  If we have 10 wds
links active and we add an 11th, the ping times and latency
go way up to the point the system is not useful.  I have verified this in
hostap 0.0.4.

We have verified this with two separate systems w/ different hardware.

It has to do with adding the wds device to the bridge.  You can add X number
of links manually through
iwpriv wlan0 wds_add 00:xx:xx:xx:xx:xx and the bridge stays up fine.  Once
you actually add these to the bridge group and activate
them do we have a problem.  It is on the 11th wds device that it always
crashes in the bridge.  Latency goes from 3ms to 500ms + and packet
loss.  However, while the one card does not work in the bridge that we add
the 11th wds link on; the other card sitting in the same bridge
still works fine.  It makes me believe this is a hostap issue because the
bridge still functions on the other card just fine.  If I do iwpriv wlan0
wds_del mac
and remove the device from the bridge things return back to normal.

I am not sure at this point whether this is a bridge issue ( probably not
since bridge hasn't been changed in 1.5 years ) or in hostap.

I have been trying to isolate the event down to a smaller portion of the
code and even looked at the bridge code to find nothing that refernces
10 devices as a buffer in the spanning tree.  According to the ethernet
standard RFC a bridge should be able to have 256 devices or ports attached
w/o a problem.  This is the same for the bridge-utils package and the RFC
for spanning tree protocol.

If anyone else could help shed light on this I would be appreciative.  I
have not been able to reproduce these exact results with hostap 0.0.3 which
makes me believe it is hostap 0.0.4.  I will do some more testing with 0.0.3
and see if I can reproduce the results.

Brock Eastman






----- Original Message -----
From: "Jouni Malinen" <jkmaline at cc.hut.fi>
To: <hostap at shmoo.com>
Sent: Tuesday, August 05, 2003 8:12 PM
Subject: Workaround for some SMP stability issues - request for testing


> Thanks to all the testing Michael Vallaly did with couple of patches to
> Host AP driver, I think I now have quite a bit more information about
> the stability issues with hostap_pci on SMP systems. It looks like there
> are two separate issues. 1) Something is corrupting the information
> transfered between card and driver which then results in frequent wlan
> hw resets. 2) hw_reset with hostap_pci on SMP system seems to hang the
> system completely in some cases (completely enough to even prevent NMI
> watchdog from detecting hang).
>
> It looks like the major cause for frequent resets was in fid register
> (RX, TX, TX Error, AllocFid) getting corrupted. I do not have any
> explanation for this apart from hardware/firmware bug. It looks like
> consecutive reads of the fid registers results in different results even
> though that register should not change before the event is acknowledged.
>
> I added code that will try its best to make sure that the fid register
> read will return correct fid number. This workaround will read the
> register three times and will return the value only if at least two of
> the reads returns the same value. This will be repeated up to five
> times.
>
> The workaround seemed to eliminate more or less all corrupted fid values
> in the test system. Consequently, there was no need to reset the
> hardware and no host system hangs.
>
> I added the workaround and test code into CVS and I would like to ask
> people with SMP systems to test the CVS snapshot version and report what
> they see in kernel log ('dmesg' output) and whether they see any system
> hangs or in general changes to the previous versions of the driver.
>
> In addition to the fid read workaround, I also changed TX fid array
> handling to use heavier locking. Previously used locking may have been
> insufficient on SMP systems. This change alone was also able to reduce
> the number of hardware resets, but this may have been do to changed
> timing (added latency due to heavier locking). Anyway, fid reads were
> still producing corrupted results.
>
>
> So far, I have mostly concentrated on findind out what is causing the
> resets. I will next try to figure out what could be done about the
> hw_reset and its relation to complete host system lockup.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From jkmaline  Wed Aug  6 21:30:20 2003
From: jkmaline (Jouni Malinen)
Date: Wed, 6 Aug 2003 21:30:20 -0700
Subject: BUG: weird behaviour after killing hostapd in latest CVS.
In-Reply-To: <Pine.LNX.4.56.0308061246340.3486@marabou.research.att.com>
References: <20030804142108.K31149@mendoza.gov.ar>
	<20030805022749.GC3211@jm.kir.nu> <20030806093242.H18154@mendoza.gov.ar>
	<Pine.LNX.4.56.0308061246340.3486@marabou.research.att.com>
Message-ID: <20030807043019.GA3967@jm.kir.nu>

On Wed, Aug 06, 2003 at 12:53:31PM -0400, Pavel Roskin wrote:

> I could reproduce the panic on Linux 2.6.0-test2-bk5 with CVS HostAP.  The
> sequence:
> 
> cardctl insert
> hostapd hostapd.conf
> ifconfig wlan0 up
> killall hostapd
> 
> It's not needed to bring wlan0sta up.  wlan0ap was up already.

Odd, I cannot reproduce this by setting wlan0 up.. However, I can
certainly produce it by setting wlan0sta up and then killing hostapd.
wlan0ap is not an issue, since hostapd is supposed to close it before
asking the driver to remove that interface. Anyway, I can reproduce this
with WDS links too, so there is something odd with the new netdev
unregistering code in Host AP driver. It is just not immediately clear
what is wrong.

> The panic has been captured on the serial console.  It's attached.  I'm
> not sure if I'll be able to debug it soon.
> 
> It appears that the crash happens very early in prism2_rx_80211.

Hmm.. Actually, in my tests this was a deadlock (of rtnl_lock?), not
NULL pointer dereference..

After some more debugging, it is looking like delayed unregisteration
function is called too early or something similar. I tried to fix this
by unregistering the netdev immediately when and just delaying kfree..
Of course I managed to produce deadlock that prevented even hostapd
killing without setting any interfaces up ;-). I'm too tired to even
think about this now, so I'll take a closer look tomorrow.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jphstap  Thu Aug  7 09:14:08 2003
From: jphstap (Joe Parks)
Date: 07 Aug 2003 12:14:08 -0400
Subject: [PATCH] implement sensitivity control (resend)
In-Reply-To: <200308051304.h75D4Pj19969@Port.imtp.ilyichevsk.odessa.ua>
References: <200308051304.h75D4Pj19969@Port.imtp.ilyichevsk.odessa.ua>
Message-ID: <1060272848.2541.139.camel@scrodconumulus>

On Tue, 2003-08-05 at 09:13, Denis Vlasenko wrote:
> I haven't seen any comments, maybe a resend is in order
> 
> ==============================================================
> From: Denis Vlasenko <vda at port.imtp.ilyichevsk.odessa.ua>
> To: Jouni Malinen <jkmaline at cc.hut.fi>, Pavel Roskin <proski at gnu.org>
> Subject: [PATCH] implement sensitivity control
> Date: Thu, 3 Jul 2003 12:29:43 +0300
>  
> Hi Jouni, Pavel, folks.
> 
> I made a patch which implements sensitivity control for hostap.
> Currently it does not program sensitivity at card initialization
> (you'll need explicit iwconfig wlan# sens N or card remains
> programmed as per default (max sens)) and sens settings do not
> survive card reset. These can be fixed later.

I haven't tested this patch yet, but I plan to.  It looks like it may be
able to help improve throughput and eliminate the "Cross-channel" WDS
connections I've been getting in situations where two or more APs are in
close proximity on different channels.



From chhabra  Thu Aug  7 11:09:18 2003
From: chhabra (Madhusudan Singh)
Date: Thu, 07 Aug 2003 14:09:18 -0400
Subject: Seeting up access point - can detect signal
Message-ID: <3F3295CE.70402@eecs.umich.edu>

Hi
    Thanks to all, especially Pavel for responding.

    I have a Netgear MA311 PCI card installed and properly recognized on 
my desktop machine. I compiled hostap-0.0.4 and also the hostapd daemon 
(my /etc/hostapd.conf is at the end of this email).
    I am trying to set up this card as an Access Point.

    My client is a properly configured and working Netgear MA401 PCMCIA 
card in my notebook. (see 
http;//www.eecs.umich.edu/~chhabra/netgearwireless.html ).

    I get the following messages on console on the DHCP server :

Received 30 bytes management frame
MGMT
mgmt::auth
authentication: STA=cl:cl:cl:cl:cl:cl auth_alg=0 auth_transaction=1 
status_code=0 wep=0
Unsupported authentication algorithm (0)
authentication reply: STA=cl:cl:cl:cl:cl:cl auth_alg=0 
auth_transaction=2 resp=13

cl:cl:cl:cl:cl:cl are the hex bits of the correct MAC address of my 
client Netgear card. (obfuscated here for security).

    On the client, my wireless link monitor shows a signal strength of 
about 89 % and /sbin/iwconfig indicates the correct MAC address (I hope 
its not my neighbour's access point but the essid is "something" on both 
client and server and that gives me some confidence !) in the Access 
Point o/p. That means that it is picking up the signal from my desktop.  
But I can't seem to use ssh or anything like that.

    What could be wrong ? A misconfiguration of the DHCP server ? (I am 
using two different subnets - one (192.168.0.1/24) for the crossover 
cable and the other (10.0.0.1/24) for the wireless).)
    One ancillary question - when I use WEP, what extra stuff do I need 
to do for the client ?

Any hints would be welcome.

Thanks,

MS.

-----------/etc/hostapd.conf---------------------------------

interface=wlan0
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=2
dump_file=/tmp/hostapd.dump
daemonize=1
ssid=something
macaddr_acl=1
auth_algs=0
minimal_eap=0
eap_message=hello
wep_key_len_broadcast=13
eapol_key_index_workaround=0
own_ip_addr=127.0.0.1 (should this be 10.0.0.1 ??)

-------------------------------------------------------------------------------
cl:cl:cl:cl:cl:cl is listed in /etc/hostapd.allow






From mrcool  Thu Aug  7 19:36:09 2003
From: mrcool (Jerry)
Date: Thu, 7 Aug 2003 21:36:09 -0500
Subject: quick question.
Message-ID: <006201c35d55$d3292c00$bf00a8c0@Home>

Do you need bridging (brctl) to make an ap work so that you can talk to a wired network?

also, if anyone cares, My ressurrected card seems to work fine. 

thanks for your help everyone.

Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030807/7b0ffdd6/attachment.htm 


From vda  Thu Aug  7 22:36:47 2003
From: vda (Denis Vlasenko)
Date: Fri, 8 Aug 2003 08:36:47 +0300
Subject: quick question.
In-Reply-To: <006201c35d55$d3292c00$bf00a8c0@Home>
References: <006201c35d55$d3292c00$bf00a8c0@Home>
Message-ID: <200308080527.h785RFd07061@Port.imtp.ilyichevsk.odessa.ua>

On 8 August 2003 05:36, Jerry wrote:
> Do you need bridging (brctl) to make an ap work so that you can talk to a wired network?

No. I have no idea why everybody is obsessed with bridging.
Properly set up routing will work just fine.

I have a gut feeling that a reason for "bridge everything"
syndrome is a broadcast name resolution used by
some OSes ;) ;) ;)
--
vda



From vda  Thu Aug  7 22:40:38 2003
From: vda (Denis Vlasenko)
Date: Fri, 8 Aug 2003 08:40:38 +0300
Subject: Seeting up access point - can detect signal
In-Reply-To: <3F3295CE.70402@eecs.umich.edu>
References: <3F3295CE.70402@eecs.umich.edu>
Message-ID: <200308080531.h785V6d07093@Port.imtp.ilyichevsk.odessa.ua>

On 7 August 2003 21:09, Madhusudan Singh wrote:
>     I have a Netgear MA311 PCI card installed and properly recognized on 
> my desktop machine. I compiled hostap-0.0.4 and also the hostapd daemon 
> (my /etc/hostapd.conf is at the end of this email).
>     I am trying to set up this card as an Access Point.
> 
>     My client is a properly configured and working Netgear MA401 PCMCIA 
> card in my notebook. (see 
> http;//www.eecs.umich.edu/~chhabra/netgearwireless.html ).
> 
>     I get the following messages on console on the DHCP server :
> 
> Received 30 bytes management frame
> MGMT
> mgmt::auth
> authentication: STA=cl:cl:cl:cl:cl:cl auth_alg=0 auth_transaction=1 
> status_code=0 wep=0
> Unsupported authentication algorithm (0)
> authentication reply: STA=cl:cl:cl:cl:cl:cl auth_alg=0 
> auth_transaction=2 resp=13

This does not look like DHCP for me.
 
> cl:cl:cl:cl:cl:cl are the hex bits of the correct MAC address of my 
> client Netgear card. (obfuscated here for security).
> 
>     On the client, my wireless link monitor shows a signal strength of 
> about 89 % and /sbin/iwconfig indicates the correct MAC address (I hope 
> its not my neighbour's access point but the essid is "something" on both 
> client and server and that gives me some confidence !) in the Access 
> Point o/p. That means that it is picking up the signal from my desktop.  
> But I can't seem to use ssh or anything like that.
> 
>     What could be wrong ? A misconfiguration of the DHCP server ? (I am 
> using two different subnets - one (192.168.0.1/24) for the crossover 
> cable and the other (10.0.0.1/24) for the wireless).)

Use static IPs (no DHCP), no WEP, and try to make this simple configuration
work first.

>     One ancillary question - when I use WEP, what extra stuff do I need 
> to do for the client ?
--
vda



From jupo  Fri Aug  8 01:28:05 2003
From: jupo (JUPO)
Date: Fri, 8 Aug 2003 10:28:05 +0200
Subject: problem with sparklan Wl360f
Message-ID: <001e01c35d86$fd7b6870$345fa83e@administrator>

Hello,
I have a problem with this station.
MAC addr have i in accept list ( and any others).
All others clients works fine, but only this MAC not. ( not ever....)
Can anyone help me?
Thanx

Peter

Aug  8 10:23:58 ns kernel: AP: drop packet to non-associated STA
00:90:4b:23:8a:d6
Aug  8 10:23:58 ns kernel: wlan0: Could not find STA 00:90:4b:23:8a:d6 for
this TX error (@39044)
Aug  8 10:23:58 ns hostapd: wlan0: STA 00:90:4b:23:8a:d6 IEEE 802.11: did
not acknowledge authentication response



From sndbeat  Fri Aug  8 05:21:53 2003
From: sndbeat (Vic Berdin)
Date: Fri, 8 Aug 2003 05:21:53 -0700 (PDT)
Subject: Symbol Spectrum 24 LA4111 report
Message-ID: <20030808122153.71407.qmail@web10404.mail.yahoo.com>

Hi everyone,

I know this has been posted way back... about hostap 
working with Symbol Spectrum24 in Ad-Hoc and 
Managed modes. I'd like to add not only did it work,
but it's way-way more stable than the current 
orinoco_cs modules. I've upgraded my Symbol card fw
just recently, and lo and behold, the performance is 
even better (ftp tested on above 100MB files)! Not 
even a single error message has been spurred/logged. 
Excellent project, the HostAp indded! Such an
excellent developer Jouni is! Thanks!


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com



From jsun  Fri Aug  8 07:07:19 2003
From: jsun (Jun Sun)
Date: Fri, 8 Aug 2003 07:07:19 -0700
Subject: quick question.
In-Reply-To: <200308080527.h785RFd07061@Port.imtp.ilyichevsk.odessa.ua>
References: <006201c35d55$d3292c00$bf00a8c0@Home>
	<200308080527.h785RFd07061@Port.imtp.ilyichevsk.odessa.ua>
Message-ID: <20030808140719.GA846@gateway.junsun.net>

On Fri, Aug 08, 2003 at 08:36:47AM +0300, Denis Vlasenko wrote:
> On 8 August 2003 05:36, Jerry wrote:
> > Do you need bridging (brctl) to make an ap work so that you can talk to a wired network?
> 
> No. I have no idea why everybody is obsessed with bridging.
> Properly set up routing will work just fine.
> 
> I have a gut feeling that a reason for "bridge everything"
> syndrome is a broadcast name resolution used by
> some OSes ;) ;) ;)

Well, to be fair, briding is the easiest and most widely used
way to connect wired LAN and WLAN.  It is probably the most efficient
way too.  Yes, in that sense, you do want brctl.

Jun



From andreaf  Fri Aug  8 11:49:26 2003
From: andreaf (Andrea G. Forte)
Date: Fri, 8 Aug 2003 14:49:26 -0400 (EDT)
Subject: HostAP beginner.
Message-ID: <200308081849.h78InQ01008116@cisalpino.cs.columbia.edu>

Hi guys,
I finally got hostAp to work on my laptop...(after firmware upgrades and wrong 
cards).
Now, the mobile station can see the hostAP, but it seems like the hostAP cant 
see the mobile station. What can I do? How can the hostAP acquire the mac 
address of the mobile station and grant a connection? The hostAP is also 
connected (with wire) to a LAN...how can I grant for the mobile system to the 
LAN by the hostAP?
Thanks a lot everybody, I know these are basic questions, but you got to start 
from somewhere!
Andrea



From proski  Fri Aug  8 12:25:17 2003
From: proski (Pavel Roskin)
Date: Fri, 8 Aug 2003 15:25:17 -0400 (EDT)
Subject: HostAP beginner.
In-Reply-To: <200308081849.h78InQ01008116@cisalpino.cs.columbia.edu>
References: <200308081849.h78InQ01008116@cisalpino.cs.columbia.edu>
Message-ID: <Pine.LNX.4.56.0308081517470.7864@marabou.research.att.com>

On Fri, 8 Aug 2003, Andrea G. Forte wrote:

> Now, the mobile station can see the hostAP, but it seems like the hostAP
> cant see the mobile station. What can I do? How can the hostAP acquire
> the mac address of the mobile station and grant a connection? The hostAP
> is also connected (with wire) to a LAN...how can I grant for the mobile
> system to the LAN by the hostAP?

You must be misinterpreting something.  Association is a bilateral
process.  It cannot happen if the AP cannot see the station.

Bring the interface up on the AP side and set the IP address on it.  See
the kernel log by running "dmesg".  Please include relevant parts of the
kernel log in the future reports if you still have problems.

It generally recommended to include the exact text you are seeing rather
than your interpretation of it.  Even if you are 100% sure that your
interpretation is correct, other people may still doubt it.

-- 
Regards,
Pavel Roskin



From roger.cox  Fri Aug  8 12:56:09 2003
From: roger.cox (roger.cox at telex.com)
Date: Fri, 8 Aug 2003 14:56:09 -0500
Subject: Prism TX power control in Test Appliance
Message-ID: <OFC59D51C2.CE30B94C-ON86256D7C.006D2E09-86256D7C.006DFC10@telex.com>

In the RF Testing Tool for the Prism 2.5 cards (v1.7.0), how can I set the 
TX power?  The default value is "C2" in Cont. Tx Power.  Does this 
correspond to a certain power output, or to the default power of the Prism 
radio card?

Roger Cox



From andreaf  Fri Aug  8 14:24:09 2003
From: andreaf (Andrea G. Forte)
Date: Fri, 8 Aug 2003 17:24:09 -0400 (EDT)
Subject: Bridge missing in kernel 2.4.18?
Message-ID: <200308082124.h78LO901008732@cisalpino.cs.columbia.edu>

Things are starting to work....the only thing is that I have the 
kernel version 2.4.18, I have recompiled the kernel with the bridging option on, 
but still does not see any of the commands.
brctl command not found.
What could it be?
Thanks,
Andrea



From williamt  Fri Aug  8 14:54:52 2003
From: williamt (William Tai)
Date: Fri, 8 Aug 2003 14:54:52 -0700
Subject: Prism TX power control in Test Appliance
References: <OFC59D51C2.CE30B94C-ON86256D7C.006D2E09-86256D7C.006DFC10@telex.com>
Message-ID: <00fd01c35df7$b2863130$e6f0c53f@williamt>


----- Original Message ----- 
From: <roger.cox at telex.com>
To: <hostap at shmoo.com>
Sent: Friday, August 08, 2003 12:56 PM
Subject: Prism TX power control in Test Appliance


> In the RF Testing Tool for the Prism 2.5 cards (v1.7.0), how can I set the
> TX power?
You can call prism2_ioctl_siwtxpow( ).
Set the txpower mode to fixed mode first.
Does any body know how to control txpower by modify PDA?
I try to modify PDR 0x0300 and PDR 0x0301; however the txpower not changed.
I notoice PDA is only records.
Maybe that's the reason txpower control not working.
Does anybody know how to control txpower by PDA?


The default value is "C2" in Cont. Tx Power.  Does this
> correspond to a certain power output, or to the default power of the Prism
> radio card?
>
> Roger Cox
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From williamt  Fri Aug  8 15:03:53 2003
From: williamt (William Tai)
Date: Fri, 8 Aug 2003 15:03:53 -0700
Subject: modify PDA to control txpower
References: <014001c35ab2$58356a40$e6f0c53f@williamt>
	<20030805023112.GD3211@jm.kir.nu>
Message-ID: <010901c35df8$f4927f60$e6f0c53f@williamt>


----- Original Message ----- 
From: "Jouni Malinen" <jkmaline at cc.hut.fi>
To: <hostap at shmoo.com>
Sent: Monday, August 04, 2003 7:31 PM
Subject: Re: modify PDA to control txpower


> On Mon, Aug 04, 2003 at 11:00:52AM -0700, William Tai wrote:
>
> >     I am trying modify PDR 0x0300 and PDR 0x0301 to control txpower by
> > calling prism2_download_volatile( ).
>
> You are trying to modify PDA by using _volatile_ download?? PDA is a
> block in flash.. In addition, please note that changing the PDA values
> does not really change anything unless you download a new image after
> that. In many cases, it would probably be easier to just modify
> prism2_srec to overrite card PDA with something else when plugging PDRs.
>
Hi Jouni:

Could you explain more detailly in how to just modify prism2_src to
overwrite card PDA
with somethins else when plugging PDRs?
I do not works on linux machine.
Hence coulf you tell me which functions invloved?

Thanx
William





> > However I do not know the param0 and param1.
> > I know the starting addr of PDA is 0x7f0000.
>
> You cannot load PDA that way with volatile download.
>
> -- 
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From kiloman  Fri Aug  8 15:01:22 2003
From: kiloman (Brad Davidson)
Date: Fri, 08 Aug 2003 15:01:22 -0700
Subject: Bridge missing in kernel 2.4.18?
In-Reply-To: <200308082124.h78LO901008732@cisalpino.cs.columbia.edu>
References: <200308082124.h78LO901008732@cisalpino.cs.columbia.edu>
Message-ID: <3F341DB2.9040606@oatmail.org>

Andrea G. Forte wrote:
> Things are starting to work....the only thing is that I have the 
> kernel version 2.4.18, I have recompiled the kernel with the bridging option on, 
> but still does not see any of the commands.
> brctl command not found.

The kernel modules are not the same thing as the user-space 
configuration tools. The modules allow the OS to actually bridge 
packets. The tools tell the OS what packets to bridge and where. The 
tool source can be downloaded at the following location:

http://www.math.leidenuniv.nl/~buytenh/bridge/

Compile and install those tools, and the 'brctl' command will be 
available to you.

-Brad



From kiloman  Fri Aug  8 15:06:12 2003
From: kiloman (Brad Davidson)
Date: Fri, 08 Aug 2003 15:06:12 -0700
Subject: Prism PCMCIA Cards Available?
Message-ID: <3F341ED4.1060306@oatmail.org>

I know this gets asked every so often, but since the market tends to 
change fairly rapidly I'm asking again...

What's the best Prism2/2.5/3 PCMCIA card out there? Is there more than 
one? Last I heard, Microsoft (of all people) had one that worked well 
with wlan-ng and hostap, but I can't remember if it was USB or PCMCIA. 
I'm particularly looking for a card that has an antenna jack on it, lack 
of one is almost a dealbreaker. Any feedback / info / rumours / links to 
e-bay auctions are appreciated.

-Brad



From jens  Fri Aug  8 16:42:07 2003
From: jens (Jens Willmroth)
Date: Sat, 9 Aug 2003 01:42:07 +0200
Subject: Prism PCMCIA Cards Available?
In-Reply-To: <3F341ED4.1060306@oatmail.org>
References: <3F341ED4.1060306@oatmail.org>
Message-ID: <200308090142.07264.jens@willmroth.local>

Am Samstag, 9. August 2003 00:06 schrieb Brad Davidson:
> What's the best Prism2/2.5/3 PCMCIA card out there? Is there more than
> one? Last I heard, Microsoft (of all people) had one that worked well
> with wlan-ng and hostap, but I can't remember if it was USB or PCMCIA.
> I'm particularly looking for a card that has an antenna jack on it, lack
> of one is almost a dealbreaker. Any feedback / info / rumours / links to
> e-bay auctions are appreciated.

Have a look at this one.
It's the only Prism 2.5 card I know which has external antenna jacks on it.

BTW I don't know any PCMCIA Prism 3 cards. I think Prism 3 is just a USB 
chipset. Correct me if I'm wrong.

Jens



From brianc  Sat Aug  9 00:38:54 2003
From: brianc (Brian Capouch)
Date: Sat, 09 Aug 2003 02:38:54 -0500
Subject: Primary Firmware Download
In-Reply-To: <20030803060126.GB8276@jm.kir.nu>
References: <20030802194240.GA4756@jm.kir.nu>
	<Pine.LNX.4.44.0308021949001.658-100000@portland.hansa.lan>
	<20030803060126.GB8276@jm.kir.nu>
Message-ID: <3F34A50E.3050002@palaver.net>

Jouni Malinen wrote:
> 
> And the new magic prism2_srec commands:
> 
> # Download primary firmware into RAM using Genesis mode
> ./prism2_srec -g wlan0 ak010100.hex
> # card is now in PRI-only mode with very limited functionality
> 
> # download station firmware into RAM
> ./prism2_srec -r wlan0 rf010409.hex
> # card is now in normal mode
> 

After earlier tonight having trashed a Zcomax XI-325 trying to upgrade 
to station firmware 1.7.4, I suddenly took a very great interest in this 
mail :-)

I downloaded the latest CVS, but couldn't get it to build against 
2.6.0-test1 until I had added "#define HOSTAP_CRYPT_MODULE" to hostap.c 
and hostap_crypt.c

I don't reckon that was the right way to do it, but things built afterwards.

I *sort of* saved my card, which now reports the following:

NIC: 0x800c	v1.0.0
PRI  0x15 	v1.1.1
STA  0x1f	v1.7.4

On the surface this seems to work OK, but when I did a bandwidth check 
(Ad-hoc mode, to a machine a few feet away) the card repeatedly wrote 
alternate Connected/Disconnected messages into the logfiles, and 
reported only 24kbs of throughput.

I'm assuming the problem is firmware-related; I have another card of

NIC: 0x8003	v1.0.0
PRI  0x15	v0.3.0
STA  0x1f	v.1.5.6

And it works perfectly.

I'm sure I've done something wrong with the firmware, and if anyone can 
point me in the right direction I'd sure be much obliged.

Thanks.

B.



From ml  Sat Aug  9 03:56:43 2003
From: ml (Dominique Blas)
Date: Sat, 9 Aug 2003 12:56:43 +0200
Subject: Another access method than CSMA/CA
Message-ID: <200308091256.43842@db>

Hi guys,

I wondered if it could be possible, with HostAp and an adequate combination of primary/secondary to substitute another access method to the current MAC CSMA/CA method.
Why ? To avoid typically problem of hidden node that will ruin all attempt to make a WLAN hotspot with a few customers a correct point of presence with BW equally distributed among users.

Be careful, for obvious compatibility reasons, the system SHOULD NOT need any change to software on the station side (as Frottle or WICCP need it). As Infinet routers do.

Regards,

db




From jar  Sat Aug  9 10:38:57 2003
From: jar (jar)
Date: Sat, 09 Aug 2003 20:38:57 +0300
Subject: Two pci/pcmcia bridge cards
Message-ID: <3F3531B1.9040306@pcuf.fi>


I just wondering, if it is possible to install two pci/pcmcia bridge
type wlan cards (e.g. Compaq wl200) to one pc ?

Do I need some special parameters for the i82365 and hostap_cs modeles ?

Regards, Jar




From TyM949  Sat Aug  9 15:01:10 2003
From: TyM949 (Tyrone)
Date: Sat, 09 Aug 2003 18:01:10 -0400
Subject: WEP problem using Cisco 350 and hostap? 
Message-ID: <412FED05.14BDD30B.00055534@netscape.net>

Hi,

I have an AP setup using latest cvs of hostap ( tried other versions too ) on a ZCOM pcmcia Prism 2.5 card, using isa adaptor.  I'm using a 104 bit wep key on the AP and clients.

Seems to work great when I talk to it with my laptop that has a Prism2 based mini-pci card, or with my Orinoco Silver if I switch wep to 40 bit ( it doesn't support 104). 

However when I try to use my Cisco Airo 350 pcmcia card it acts like the WEP key is wrong.

If AP authentication is open I can associate with the AP ( see essid and HW address with iwconfig ) but can't pass traffic through it.  If I switch the  AP to shared, I can no longer associate ( the cisco card is set to talk to shared AP yes ).

Any ideas I haven't been able to find any answers so far and I'm stuck :(

any suggestions appreciated!
Kevin

__________________________________________________________________
McAfee VirusScan Online from the Netscape Network.
Comprehensive protection for your entire computer. Get your free trial today!
http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397

Get AOL Instant Messenger 5.1 free of charge.  Download Now!
http://aim.aol.com/aimnew/Aim/register.adp?promo=380455



From jiri.fojtasek  Sun Aug 10 02:43:25 2003
From: jiri.fojtasek (Jiri Fojtasek)
Date: Sun, 10 Aug 2003 11:43:25 +0200
Subject: [OT] Good reading about kernel drivers ... Linux Device Drivers,
 2nd Edition
Message-ID: <3F3613BD.8060103@hlohovec.net>

Hello all

I have found this interesting book about writing kernel drivers. IMHO, 
because this book freely available under the GNU Free
Documentation License, version 1.1, the link should be placed in to 
hostap main website ...

The link is:
http://www.xml.com/ldd/chapter/book/bookindexpdf.html

Jiri



From sgala  Mon Aug 11 01:50:43 2003
From: sgala (=?ISO-8859-1?Q?Santiago_Gala_P=E9rez?=)
Date: Mon, 11 Aug 2003 10:50:43 +0200
Subject: [OT] hostap for Darwin (Mac OS X)
Message-ID: <E497E851-CBD8-11D7-8EBD-000A958871C6@hisitech.com>

Sorry for the off-topic, but I can't find anything on this out there...

I have a new Mac PowerBook running OS X. I know for certain hostap has 
been ported to BSD. What I don't know, or can find information, is if 
someone has ported hostap to run in Mac OS X.

Any pointers?

Please reply to the list, so that the pointers get indexed and can be 
used by future "cyberspace wanderers"
;-)

Regards,
      Santiago Gala



From sgala  Mon Aug 11 02:18:21 2003
From: sgala (=?ISO-8859-1?Q?Santiago_Gala_P=E9rez?=)
Date: Mon, 11 Aug 2003 11:18:21 +0200
Subject: SMP related issues
In-Reply-To: <20030709074918.GB4066@jm.kir.nu>
Message-ID: <C0765CF5-CBDC-11D7-8EBD-000A958871C6@hisitech.com>


El mi?rcoles, 9 juli, 2003, a las 09:49 Europe/Madrid, Jouni Malinen 
escribi?:

> If anyone is still able to reproduce crashes more or less consistently
> on SMP systems using the latest CVS version of Host AP driver, I would
> be interested in knowing about these. I will have access to my SMP
> system for couple of weeks, so now would be a good time to (re-)report
> these issues.
>

I updated cvs yesterday (Aug 11, about 0:00 GMT), installed, and used my
standard trick:

prompt# ifdown wlan0; rmmod hostap_pci; rmmod hostap; rmmod 
hostap_crypt; ifup wlan0

for hot reloading the wlan driver.

I am crazy enough to do this from a client connected through wlan0, and 
it has always worked till now. The machine is a dual PentiumIII 1 GHz, 
running:

[root at webserver2 utils]# uname -a
Linux webserver2.intranet.hisitech.com 2.4.21-0.18mdkenterprise #1 SMP 
lun jun 16 14:56:25 CEST 2003 i686 unknown unknown GNU/Linux

with a pci card:

[root at webserver2 utils]# lspci -v -s 00:0b.0
00:0b.0 Network controller: Harris Semiconductor Prism 2.5 Wavelan 
chipset (rev 01)
         Subsystem: Unknown device 16a5:1601
         Flags: bus master, medium devsel, latency 64, IRQ 19
         Memory at dddff000 (32-bit, prefetchable) [size=4K]
         Capabilities: [dc] Power Management version 2


Yesterday, though, I got:

Aug 11 00:55:53 webserver2 kernel: wlan0: prism2_close
Aug 11 00:55:53 webserver2 kernel: wlan0: Deauthenticate all stations
Aug 11 00:55:54 webserver2 dhcpd: receive_packet failed on wlan0: 
Network is down
Aug 11 00:55:54 webserver2 kernel: hostap_pci: Netdevice wlan0 
unregistered
Aug 11 00:55:54 webserver2 kernel: hostap_pci: Driver unloaded
Aug 11 00:55:54 webserver2 kernel: hostap_crypt: unregistered algorithm 
'NULL' (deinit)
Aug 11 00:55:54 webserver2 /etc/hotplug/net.agent: NET unregister event 
not supported
Aug 11 00:55:54 webserver2 kernel: hostap_crypt: registered algorithm 
'NULL'
Aug 11 00:55:54 webserver2 kernel: hostap_pci: CVS (Jouni Malinen 
<jkmaline at cc.h
ut.fi>)
Aug 11 00:55:54 webserver2 kernel: hostap_pci: Registered netdevice 
wlan0
Aug 11 00:55:54 webserver2 /etc/hotplug/net.agent: invoke ifup wlan0
Aug 11 00:55:54 webserver2 kernel: prism2_hw_init: initialized in 200 ms
Aug 11 00:55:54 webserver2 kernel: wlan0: trying to read PDA from 
0x007f0000: OK
Aug 11 00:55:56 webserver2 kernel: wlan0: hfa384x_cmd: entry still in 
list? (entry=ca6582a0, type=0, res=0)
Aug 11 00:55:56 webserver2 kernel: wlan0: hfa384x_cmd: command was not 
completed
  (res=0, entry=ca6582a0, type=0, cmd=0x0021, param0=0xfdc6, EVSTAT=8000 
INTEN=00
10)
Aug 11 00:55:56 webserver2 kernel: wlan0: hfa384x_get_rid: 
CMDCODE_ACCESS failed
  (res=-110, rid=fdc6, len=12)
Aug 11 00:55:58 webserver2 kernel: wlan0: hfa384x_cmd: entry still in 
list? (ent
ry=ca6582a0, type=0, res=0)
Aug 11 00:55:58 webserver2 kernel: wlan0: hfa384x_cmd: command was not 
completed
  (res=0, entry=ca6582a0, type=0, cmd=0x0021, param0=0xfdc6, EVSTAT=8000 
INTEN=00
10)
Aug 11 00:55:58 webserver2 kernel: wlan0: hfa384x_get_rid: 
CMDCODE_ACCESS failed
  (res=-110, rid=fdc6, len=12)
Aug 11 00:56:00 webserver2 kernel: wlan0: hfa384x_cmd: entry still in 
list? (ent
ry=ca6582a0, type=0, res=0)
Aug 11 00:56:00 webserver2 kernel: wlan0: hfa384x_cmd: command was not 
completed
  (res=0, entry=ca6582a0, type=0, cmd=0x0021, param0=0xfdc1, EVSTAT=8000 
INTEN=00
10)
Aug 11 00:56:00 webserver2 kernel: wlan0: hfa384x_get_rid: 
CMDCODE_ACCESS failed
  (res=-110, rid=fdc1, len=2)
Aug 11 00:56:02 webserver2 kernel: wlan0: hfa384x_cmd: entry still in 
list? (ent
ry=ca6582a0, type=0, res=0)
Aug 11 00:56:02 webserver2 kernel: wlan0: hfa384x_cmd: command was not 
completed
  (res=0, entry=ca6582a0, type=0, cmd=0x0021, param0=0xfc06, EVSTAT=8000 
INTEN=00
10)
Aug 11 00:56:02 webserver2 kernel: wlan0: hfa384x_get_rid: 
CMDCODE_ACCESS failed
  (res=-110, rid=fc06, len=2)
Aug 11 00:56:04 webserver2 kernel: wlan0: hfa384x_cmd: entry still in 
list? (ent
ry=ca6582a0, type=0, res=0)
Aug 11 00:56:04 webserver2 kernel: wlan0: hfa384x_cmd: command was not 
completed
  (res=0, entry=ca6582a0, type=0, cmd=0x0021, param0=0xfd42, EVSTAT=8000 
INTEN=00
10)
Aug 11 00:56:04 webserver2 kernel: wlan0: hfa384x_get_rid: 
CMDCODE_ACCESS failed
  (res=-110, rid=fd42, len=6)
Aug 11 00:56:06 webserver2 kernel: wlan0: hfa384x_cmd: entry still in 
list? (ent
ry=eb558ce0, type=0, res=0)
Aug 11 00:56:06 webserver2 kernel: wlan0: hfa384x_cmd: command was not 
completed
  (res=0, entry=eb558ce0, type=0, cmd=0x0021, param0=0xfc0e, EVSTAT=8000 
INTEN=00
10)
Aug 11 00:56:06 webserver2 kernel: wlan0: hfa384x_get_rid: 
CMDCODE_ACCESS failed
  (res=-110, rid=fc0e, len=34)
Aug 11 00:56:08 webserver2 kernel: wlan0: hfa384x_cmd: entry still in 
list? (ent
ry=ca6582a0, type=0, res=0)
Aug 11 00:56:08 webserver2 kernel: wlan0: hfa384x_cmd: command was not 
completed
  (res=0, entry=ca6582a0, type=0, cmd=0x0021, param0=0xfc84, EVSTAT=8000 
INTEN=00
10)
Aug 11 00:56:08 webserver2 kernel: wlan0: hfa384x_get_rid: 
CMDCODE_ACCESS failed
  (res=-110, rid=fc84, len=2)
Aug 11 00:56:10 webserver2 kernel: wlan0: hfa384x_cmd: entry still in 
list? (ent
ry=ca6582a0, type=0, res=0)
Aug 11 00:56:10 webserver2 kernel: wlan0: hfa384x_cmd: command was not 
completed
  (res=0, entry=ca6582a0, type=0, cmd=0x0021, param0=0xfc83, EVSTAT=8000 
INTEN=00
10)
Aug 11 00:56:10 webserver2 kernel: wlan0: hfa384x_get_rid: 
CMDCODE_ACCESS failed
  (res=-110, rid=fc83, len=2)
Aug 11 00:56:12 webserver2 kernel: wlan0: hfa384x_cmd: entry still in 
list? (ent
ry=ca6582a0, type=0, res=0)
Aug 11 00:56:12 webserver2 kernel: wlan0: hfa384x_cmd: command was not 
completed
  (res=0, entry=ca6582a0, type=0, cmd=0x0021, param0=0xfc82, EVSTAT=8000 
INTEN=00
10)
Aug 11 00:56:12 webserver2 kernel: wlan0: hfa384x_get_rid: 
CMDCODE_ACCESS failed
  (res=-110, rid=fc82, len=2)
Aug 11 00:56:14 webserver2 kernel: wlan0: hfa384x_cmd: entry still in 
list? (ent
ry=ca6582a0, type=0, res=0)
Aug 11 00:56:14 webserver2 kernel: wlan0: hfa384x_cmd: command was not 
completed
  (res=0, entry=ca6582a0, type=0, cmd=0x0021, param0=0xfc09, EVSTAT=8000 
INTEN=00
10)
Aug 11 00:56:14 webserver2 kernel: wlan0: hfa384x_get_rid: 
CMDCODE_ACCESS failed
  (res=-110, rid=fc09, len=2)
Aug 11 00:56:16 webserver2 kernel: wlan0: hfa384x_cmd: entry still in 
list? (ent
ry=ca6582a0, type=0, res=0)
Aug 11 00:56:16 webserver2 kernel: wlan0: hfa384x_cmd: command was not 
completed
  (res=0, entry=ca6582a0, type=0, cmd=0x0021, param0=0xfd48, EVSTAT=8000 
INTEN=00
10)
Aug 11 00:56:16 webserver2 kernel: wlan0: hfa384x_get_rid: 
CMDCODE_ACCESS failed
  (res=-110, rid=fd48, len=2)
Aug 11 00:56:18 webserver2 kernel: wlan0: hfa384x_cmd: entry still in 
list? (ent
ry=eb3c63e0, type=0, res=0)
Aug 11 00:56:18 webserver2 kernel: wlan0: hfa384x_cmd: command was not 
completed
  (res=0, entry=eb3c63e0, type=0, cmd=0x0021, param0=0xfd0b, EVSTAT=8000 
INTEN=00
10)
Aug 11 00:56:18 webserver2 kernel: wlan0: hfa384x_get_rid: 
CMDCODE_ACCESS failed
  (res=-110, rid=fd0b, len=8)
Aug 11 00:56:18 webserver2 kernel: Could not get RID for component NIC
Aug 11 00:56:18 webserver2 kernel: hostap_pci: Initialization failed
Aug 11 00:56:18 webserver2 kernel: hostap_pci: hardware initialization 
failed
Aug 11 00:56:18 webserver2 kernel: wlan0: removed pending cmd_queue 
entry (type=
1, cmd=0x0011, param0=0xf100)
Aug 11 00:56:18 webserver2 kernel: wlan0: removed pending cmd_queue 
entry (type=
1, cmd=0x0011, param0=0xf100)
Aug 11 00:56:18 webserver2 kernel: wlan0: removed pending cmd_queue 
entry (type=
0, cmd=0x0021, param0=0xfc28)
Aug 11 00:56:20 webserver2 kernel: Unable to handle kernel paging 
request at vir
tual address f911e060
Aug 11 00:56:20 webserver2 kernel:  printing eip:
Aug 11 00:56:20 webserver2 kernel: f91113c2
Aug 11 00:56:20 webserver2 kernel: *pde = 37b49067
Aug 11 00:56:20 webserver2 kernel: *pte = 00000000
Aug 11 00:56:20 webserver2 kernel: Oops: 0000
Aug 11 00:56:20 webserver2 kernel: hostap_pci hostap binfmt_misc 
af_packet ip_vs
_rr ip_vs_lblc ip_vs_wlc ip_vs eeprom lm80 i2c-proc i2c-viapro i2c-core 
button t
hermal processor fan ac battery iptable_filter ipt_REDIRECT 
iptable_mangle 8139t
oo mii ide-cd cdrom ide-scsi scsi_mod ip_nat_irc ip_nat_ftp iptable_nat 
ip_table
s ip_conntrack_irc ip_conntrack_ftp ip_conntrack tun usb-uhci usbcore 
rtc ext3 j
bd raid1
Aug 11 00:56:20 webserver2 kernel: CPU:    1
Aug 11 00:56:20 webserver2 kernel: EIP:    
0010:[hostap_pci:__insmod_hostap_pci_
O/lib/modules/2.4.21-0.18mdkenterprise/+-39998/96]    Not tainted
Aug 11 00:56:20 webserver2 kernel: EIP:    0010:[<f91113c2>]    Not 
tainted
Aug 11 00:56:20 webserver2 kernel: EFLAGS: 00010286
Aug 11 00:56:20 webserver2 kernel: EIP is at hfa384x_cmd+0x222/0x450 
[hostap_pci
]
Aug 11 00:56:20 webserver2 kernel: eax: f911e000   ebx: e89f2000   ecx: 
eb3c63ec
    edx: cc944200
Aug 11 00:56:20 webserver2 kernel: esi: eb3c63e0   edi: f5b68000   ebp: 
e89f3df4
    esp: e89f3d90
Aug 11 00:56:20 webserver2 kernel: ds: 0018   es: 0018   ss: 0018
Aug 11 00:56:20 webserver2 kernel: Process iwconfig (pid: 21301, 
stackpage=e89f3
000)
Aug 11 00:56:20 webserver2 kernel: Stack: f5b68000 e89f3df4 00000296 
eb3c63e8 00
000296 00000000 00000000 00000000
Aug 11 00:56:20 webserver2 kernel:        0000fc28 00000021 0021e9a0 
00000000 e8
9f2000 00000000 00000000 00000000
Aug 11 00:56:20 webserver2 kernel:        e89f2000 00000000 00000000 
c0108123 f5
b68028 00000000 f5b68000 f5b68020
Aug 11 00:56:20 webserver2 kernel: Call Trace:
Aug 11 00:56:20 webserver2 kernel:  [__down_interruptible+211/256] 
__down_interr
uptible+0xd3/0x100 [kernel]
Aug 11 00:56:20 webserver2 kernel:  [<c0108123>] 
__down_interruptible+0xd3/0x100
  [kernel]
Aug 11 00:56:20 webserver2 kernel:  
[hostap_pci:__insmod_hostap_pci_O/lib/module
s/2.4.21-0.18mdkenterprise/+-38158/96] hfa384x_get_rid+0x52/0x1f0 
[hostap_pci]
Aug 11 00:56:20 webserver2 kernel:  [<f9111af2>] 
hfa384x_get_rid+0x52/0x1f0 [hos
tap_pci]
Aug 11 00:56:20 webserver2 kernel:  
[hostap_pci:__insmod_hostap_pci_O/lib/module
s/2.4.21-0.18mdkenterprise/+-11022/96] 
.text.lock.KBUILD_BASENAME+0x46/0x234 [ho
stap_pci]
Aug 11 00:56:20 webserver2 kernel:  [<f91184f2>] 
.text.lock.KBUILD_BASENAME+0x46
/0x234 [hostap_pci]
Aug 11 00:56:20 webserver2 kernel:  [activate_page+204/224] 
activate_page+0xcc/0
xe0 [kernel]
Aug 11 00:56:20 webserver2 kernel:  [<c013d95c>] 
activate_page+0xcc/0xe0 [kernel
]
Aug 11 00:56:20 webserver2 kernel:  
[hostap_crypt:__insmod_hostap_crypt_S.bss_L4
+1058676/11853024] hostap_set_encryption_Rsmp_51a9bfcb+0x40/0x280 
[hostap]
Aug 11 00:56:20 webserver2 kernel:  [<f921c380>] 
hostap_set_encryption_Rsmp_51a9
bfcb+0x40/0x280 [hostap]
Aug 11 00:56:20 webserver2 kernel:  [do_no_page+114/592] 
do_no_page+0x72/0x250 [
kernel]
Aug 11 00:56:20 webserver2 kernel:  [<c0132ec2>] do_no_page+0x72/0x250 
[kernel]
Aug 11 00:56:20 webserver2 kernel:  
[hostap_crypt:__insmod_hostap_crypt_S.bss_L4
+1034884/11876816] prism2_ioctl_siwencode+0x1a0/0x2c0 [hostap]
Aug 11 00:56:20 webserver2 kernel:  [<f9216690>] 
prism2_ioctl_siwencode+0x1a0/0x
2c0 [hostap]
Aug 11 00:56:20 webserver2 kernel:  
[hostap_crypt:__insmod_hostap_crypt_S.bss_L4
+1034468/11877232] prism2_ioctl_siwencode+0x0/0x2c0 [hostap]
Aug 11 00:56:20 webserver2 kernel:  [<f92164f0>] 
prism2_ioctl_siwencode+0x0/0x2c
0 [hostap]
Aug 11 00:56:20 webserver2 kernel:  [ioctl_standard_call+423/736] 
ioctl_standard
_call+0x1a7/0x2e0 [kernel]
Aug 11 00:56:20 webserver2 kernel:  [<c022cda7>] 
ioctl_standard_call+0x1a7/0x2e0
  [kernel]
Aug 11 00:56:20 webserver2 kernel:  [wireless_process_ioctl+137/480] 
wireless_pr
ocess_ioctl+0x89/0x1e0 [kernel]
Aug 11 00:56:20 webserver2 kernel:  [<c022c809>] 
wireless_process_ioctl+0x89/0x1
e0 [kernel]
Aug 11 00:56:20 webserver2 kernel:  
[hostap_crypt:__insmod_hostap_crypt_S.bss_L4
+1034468/11877232] prism2_ioctl_siwencode+0x0/0x2c0 [hostap]
Aug 11 00:56:20 webserver2 kernel:  [<f92164f0>] 
prism2_ioctl_siwencode+0x0/0x2c
0 [hostap]
Aug 11 00:56:20 webserver2 kernel:  [dev_ioctl+507/800] 
dev_ioctl+0x1fb/0x320 [k
ernel]
Aug 11 00:56:20 webserver2 kernel:  [<c022593b>] dev_ioctl+0x1fb/0x320 
[kernel]
Aug 11 00:56:20 webserver2 kernel:  [sock_ioctl+63/128] 
sock_ioctl+0x3f/0x80 [ke
rnel]
Aug 11 00:56:20 webserver2 kernel:  [<c021bfbf>] sock_ioctl+0x3f/0x80 
[kernel]
Aug 11 00:56:20 webserver2 kernel:  [sys_ioctl+245/688] 
sys_ioctl+0xf5/0x329 [ke
rnel]
Aug 11 00:56:20 webserver2 kernel:  [<c0158595>] sys_ioctl+0xf5/0x329 
[kernel]
Aug 11 00:56:20 webserver2 kernel:  [system_call+51/56] 
system_call+0x33/0x38 [k
ernel]
Aug 11 00:56:20 webserver2 kernel:  [<c010962f>] system_call+0x33/0x38 
[kernel]
Aug 11 00:56:20 webserver2 kernel:
Aug 11 00:56:20 webserver2 kernel: Code: 66 8b 58 60 66 8b 40 64 25 ff 
ff 00 00
50 89 d8 25 ff ff 00


I had to reset the machine after. the driver seems to be working nicely 
since then.

I send this FWIW. The card has firmware 1.3.6, which I update (in RAM, 
by hand) to 1.4.7 each time I reboot. When it hanged, then, it was 
running 1.3.6

Regards, and thanks for the good work
      Santiago


From vicente.paredes  Mon Aug 11 07:16:35 2003
From: vicente.paredes (Vicente Paredes)
Date: Mon, 11 Aug 2003 09:16:35 -0500 (CDT)
Subject: Another chipset
Message-ID:      <3565.200.63.198.49.1060611395.squirrel@webmail.linuxpowered.org>

Hello friends

I want to know when you can change the chipset because i cant find the
prism 2 based card.
I buy two SMC 2632W cards but they are version 3.0 and have Atmel chipset,
or exist another option.

Please tell me.

Urgetn!!!!

-- 
Atentamente

Vicente Paredes
Departamento de ?ngenier?a
GRUEIN Cia. Ltda.
PBX 593-42690888
CEL 593-98412868



From david.goodenough  Mon Aug 11 08:14:20 2003
From: david.goodenough (David Goodenough)
Date: Mon, 11 Aug 2003 16:14:20 +0100
Subject: Another chipset
In-Reply-To: <3565.200.63.198.49.1060611395.squirrel@webmail.linuxpowered.org>
References: <3565.200.63.198.49.1060611395.squirrel@webmail.linuxpowered.org>
Message-ID: <200308111614.20980.david.goodenough@btconnect.com>

On Monday 11 August 2003 15:16, Vicente Paredes wrote:
> Hello friends
>
> I want to know when you can change the chipset because i cant find the
> prism 2 based card.
> I buy two SMC 2632W cards but they are version 3.0 and have Atmel chipset,
> or exist another option.
>
> Please tell me.
>
> Urgetn!!!!

The Senao/EnGenius cards all use the right chips.

David



From jhiller  Mon Aug 11 08:15:12 2003
From: jhiller (James B. Hiller)
Date: Mon, 11 Aug 2003 11:15:12 -0400 (EDT)
Subject: Need advice:  whether to flash DLink DWL-520
Message-ID: <200308111515.h7BFFC3B000667@bassett.home.org>

Hi!

Been searching around this list and other related ones off and on for
about a month, and have yet to run into a clear answer as to under
what conditions a DWL-520 flash (volatile or non-volatile) should be
accomplished.  Am new in wireless, so please be kind :-)

My environment:

Machine A - linux-2.4.21 on an older Tyan SMP (dual processor) PPro
board.  This machine is set up to be my WAP and router.  I have
a DWL-520 in it, and it seems to generally be working ok with
hostap-0.0.4 and wireless-tools.26.  The kernel is compiled by me,
monolithically except for the hostap modules.  Just for giggles,
I also compiled in the Prism 2.5 driver available with the kernel.

I have IP masquerading and firewalling set up.  No broadband
connection, just pppd for a regular dialup.  Yesterday I moved several
gigabytes of files from this machine to B, C, and D below via ftp,
and also between the windows machines (B and C) using Win networking.

Generally all ok - the Win networking seems to move files more slowly
than ftp (go figure), and after many gigabytes moved from this
machine to the other linux box (D) using ftp, something plugged up,
but not worried about that right now.  Using the DLink utility on
machines B and C below, saw that basic ftp was moving files at
about 5 Mbps, which seems fine to me.

Machines B, C - Each running Win98, to be served/supported by
machine A, and interoperable with Machine D which runs both linux
(primarily) and Win2000 (when needed).  Each running with a
DLink DWL-520+, since I don't have to care about Prism in these
machines.

Machine D - Newer Tyan SMP (dual) running AMD Palomino 1.2 CPUs.
Running linux-2.4.21, compiled monolithically, with Prism 2.5 support
compiled in.  At this moment, have a Zcomax XI-626 PCI WLAN card in
it (also Prism 2.5), but plan to send that back and get another
DLink DWL-520 (cost of Zcomax cards seems not warranted, little/no
evident signal strength, quality, or throughput.  Good external
antennas, though - keeping those).

The DWL-520 in Machine A performing the host function has:

NIC ID=x8013 v1.0.0
PRI ID=x15 v1.0.5
STA ID=x1f v1.3.4

So my questions are:

a.  Is there a good reason to upgrade the firmware on this card
serving as the host AP/router?  If so, to which versions, using
which tool, available where (firmware and tool)?  Should I do only
the volatile, and if so, would I need to do the non-volatile to get
to a version which supports non-volatile?  If the answers to these
questions are already elaborated, pointers are fine.  I've seen
a number of pieces/parts, just not sure of the direct answer/decision
point.

b.  Is there a good reason to upgrade the firmware on the DWL-520 that
will be here this week to go into my Machine D?  Don't know until it
arrives whether it will be same versions of stuff, but expect it
will, as it's coming from the same vendor as the first, just a few
weeks later (probably has a single block of cards).

c.  Should I be compiling the Prism 2.5 kernel driver into the kernel
on the host ap machine as I've been doing, should I not be, or does
it not matter?

d.  Believe I should continue compiling the Prism 2.5 kernel driver
into the kernel on Machine D, otherwise there would be no support
for the card, but just want to verify.

e.  Is there a reason I should go with the Zcomax cards in either
Machine A or D (if so, I won't send them back)?  So far, I've not
witnessed a performance/functionality improvement, other than
the fact that when I ran the Zcomax card in the host AP machine
for a few hours to play with it, I noticed it had slightly newer
firmware (1.3.5/1.1.0, I believe).

f.  Are there any other questions I should be asking?  I have no
desire to go to linux-wlan-ng driver unless someone says I should,
instead of kernel driver for the Prism chipset.

Thx!

jbh



From eduardo  Mon Aug 11 10:28:14 2003
From: eduardo (Eduardo Kaftanski)
Date: Mon, 11 Aug 2003 13:28:14 -0400
Subject: Need advice:  whether to flash DLink DWL-520
In-Reply-To: <200308111515.h7BFFC3B000667@bassett.home.org>
References: <200308111515.h7BFFC3B000667@bassett.home.org>
Message-ID: <20030811172814.GA6126@enriqueto.nn.cl>


This looks like my card, out of the box:

> 
> The DWL-520 in Machine A performing the host function has:
> 
> NIC ID=x8013 v1.0.0
> PRI ID=x15 v1.0.5
> STA ID=x1f v1.3.4
> 
> f.  Are there any other questions I should be asking?  I have no
> desire to go to linux-wlan-ng driver unless someone says I should,
> instead of kernel driver for the Prism chipset.
>

If so, you should flash it to 1.4.9 and then flash it to 1.7.4 to
get the latest enhancements and to properly support WDS. Why the two step
flash? Don't know... but I tried to flash 1.5.6 directly to it and the 
flashing failed. Flashing 1.4.9 first made it work ok again... 



-- 
Eduardo Kaftanski
eduardo at linuxcenter.cl
Red Hat Certified Engineer
Gerente Ingenieria LinuxCenter S.A.
Canada 239 5to Piso, Providencia, Stgo de Chile.
http://www.linuxcenter.cl 2745000



From proski  Mon Aug 11 15:42:45 2003
From: proski (Pavel Roskin)
Date: Mon, 11 Aug 2003 18:42:45 -0400 (EDT)
Subject: Need advice:  whether to flash DLink DWL-520
In-Reply-To: <20030811172814.GA6126@enriqueto.nn.cl>
References: <200308111515.h7BFFC3B000667@bassett.home.org>
 <20030811172814.GA6126@enriqueto.nn.cl>
Message-ID: <Pine.LNX.4.56.0308111836100.6604@marabou.research.att.com>

On Mon, 11 Aug 2003, Eduardo Kaftanski wrote:

> If so, you should flash it to 1.4.9 and then flash it to 1.7.4 to
> get the latest enhancements and to properly support WDS. Why the two step
> flash? Don't know... but I tried to flash 1.5.6 directly to it and the
> flashing failed. Flashing 1.4.9 first made it work ok again...

Your failure may be related to the fact that you didn't update primary
firmware.

If you check the archives, I was able to flash DWL-520 from secondary
PRI 1.0.4 and STA 1.1.0 (much older than 1.3.4) straight to PRI 1.1.1
and STA 1.7.4.

You should flash primary and secondary firmware in the same time, and use
CVS HostAP because version 0.0.4 cannot flash primary firmware.  That
includes updating prism2_srec to the CVS version, too.

Sorry for repeating the same things over and over again, but if it's not
done, urban legends start appearing :-)

-- 
Regards,
Pavel Roskin



From proski  Mon Aug 11 15:50:26 2003
From: proski (Pavel Roskin)
Date: Mon, 11 Aug 2003 18:50:26 -0400 (EDT)
Subject: Two pci/pcmcia bridge cards
In-Reply-To: <3F3531B1.9040306@pcuf.fi>
References: <3F3531B1.9040306@pcuf.fi>
Message-ID: <Pine.LNX.4.56.0308111849450.6604@marabou.research.att.com>

On Sat, 9 Aug 2003, jar wrote:

> I just wondering, if it is possible to install two pci/pcmcia bridge
> type wlan cards (e.g. Compaq wl200) to one pc ?

Yes.

> Do I need some special parameters for the i82365 and hostap_cs modeles ?

You may need "irq_mode=0" for i82365.

-- 
Regards,
Pavel Roskin



From proski  Mon Aug 11 16:01:09 2003
From: proski (Pavel Roskin)
Date: Mon, 11 Aug 2003 19:01:09 -0400 (EDT)
Subject: Primary Firmware Download
In-Reply-To: <3F34A50E.3050002@palaver.net>
References: <20030802194240.GA4756@jm.kir.nu>
 <Pine.LNX.4.44.0308021949001.658-100000@portland.hansa.lan>
 <20030803060126.GB8276@jm.kir.nu> <3F34A50E.3050002@palaver.net>
Message-ID: <Pine.LNX.4.56.0308111854010.6604@marabou.research.att.com>

On Sat, 9 Aug 2003, Brian Capouch wrote:

> I *sort of* saved my card, which now reports the following:
>
> NIC: 0x800c	v1.0.0
> PRI  0x15 	v1.1.1
> STA  0x1f	v1.7.4

Congratulations.

> On the surface this seems to work OK, but when I did a bandwidth check
> (Ad-hoc mode, to a machine a few feet away) the card repeatedly wrote
> alternate Connected/Disconnected messages into the logfiles, and
> reported only 24kbs of throughput.
>
> I'm assuming the problem is firmware-related; I have another card of
>
> NIC: 0x8003	v1.0.0
> PRI  0x15	v0.3.0
> STA  0x1f	v.1.5.6
>
> And it works perfectly.

You may want to check the recent thread about sensitivity control:
http://sisyphus.iocaine.com/pipermail/hostap/2003-August/003825.html

As I understand it, setting sensitivity using RIDs doesn't work correctly,
so it should be done directly through the communication processor.

> I'm sure I've done something wrong with the firmware, and if anyone can
> point me in the right direction I'd sure be much obliged.

I don't think _you_ did anything wrong.  It's more like the firmwares have
some differences and possibly bugs.

-- 
Regards,
Pavel Roskin



From jkmaline  Mon Aug 11 18:34:11 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 11 Aug 2003 18:34:11 -0700
Subject: Need advice:  whether to flash DLink DWL-520
In-Reply-To: <200308111515.h7BFFC3B000667@bassett.home.org>
References: <200308111515.h7BFFC3B000667@bassett.home.org>
Message-ID: <20030812013410.GA4120@jm.kir.nu>

On Mon, Aug 11, 2003 at 11:15:12AM -0400, James B. Hiller wrote:

> The DWL-520 in Machine A performing the host function has:
> 
> NIC ID=x8013 v1.0.0
> PRI ID=x15 v1.0.5
> STA ID=x1f v1.3.4

> a.  Is there a good reason to upgrade the firmware on this card
> serving as the host AP/router?  If so, to which versions, using
> which tool, available where (firmware and tool)?  Should I do only
> the volatile, and if so, would I need to do the non-volatile to get
> to a version which supports non-volatile?

Yes, you should consider upgrading the firmware. That combination of
PRI/STA firmware is known to have a bug that causes corruption of data
on PCI bus. This was fixed in PRI 1.0.7 / STA 1.3.5, so it or anything
newer is probably better solution.

I would recommend first testing with volatile upgrade to make sure that
the new firmware version actually works with your card and there are no
unpleasant surprises waiting to happen. At least some people have
reported dropped signal strength/quality with new firmware versions. It
is possible that the PDA on the card does not include all new
configuration values and the defaults in the firmware image are not
optimal for that card, etc.

If you are going to download firmware images with Host AP driver, please
use the latest CVS snapshot of it.


> c.  Should I be compiling the Prism 2.5 kernel driver into the kernel
> on the host ap machine as I've been doing, should I not be, or does
> it not matter?

What do you mean with "Prism 2.5 kernel driver"? orinoco_pci?
hostap_pci? If you plan to use two different drivers for the same PCI
card, I would not link them into the kernel image.. If it is only one
driver, then it should be OK to link it in.

-- 
Jouni Malinen                                            PGP id EFC895FA



From brock  Mon Aug 11 22:13:29 2003
From: brock (Brock Eastman)
Date: Mon, 11 Aug 2003 22:13:29 -0700
Subject: strange behavior w/ 16 wds links but not 15
References: <200308111515.h7BFFC3B000667@bassett.home.org>
	<20030812013410.GA4120@jm.kir.nu>
Message-ID: <002801c36090$78b7e2a0$9900a8c0@TOSHIBARDLAP>

We have been having issues w/ hostap 0.0.4 when we have 16 wds links off of
it.  It will in fact crash the system every time
even with the prism2_param wlan0 max_wds ## set to 16 or higher.

We have a true 16 wds links running in our test environment.  We believe the
problem is somewhere with the bridge code or the 2.4.20 kernel. We
are using debian. We have searched the bridge code for a pseudo device and
have come up with no results.  The bridge actually is what crashes
when it goes into a forwarding state.

Has anyone been able to run any more links than this? We are using a Zycomax
card prism2.5 w/ hostap 1.7.4 firmware.

Brock Eastman
----- Original Message -----
From: "Jouni Malinen" <jkmaline at cc.hut.fi>
To: <hostap at shmoo.com>
Sent: Monday, August 11, 2003 6:34 PM
Subject: Re: Need advice: whether to flash DLink DWL-520


> On Mon, Aug 11, 2003 at 11:15:12AM -0400, James B. Hiller wrote:
>
> > The DWL-520 in Machine A performing the host function has:
> >
> > NIC ID=x8013 v1.0.0
> > PRI ID=x15 v1.0.5
> > STA ID=x1f v1.3.4
>
> > a.  Is there a good reason to upgrade the firmware on this card
> > serving as the host AP/router?  If so, to which versions, using
> > which tool, available where (firmware and tool)?  Should I do only
> > the volatile, and if so, would I need to do the non-volatile to get
> > to a version which supports non-volatile?
>
> Yes, you should consider upgrading the firmware. That combination of
> PRI/STA firmware is known to have a bug that causes corruption of data
> on PCI bus. This was fixed in PRI 1.0.7 / STA 1.3.5, so it or anything
> newer is probably better solution.
>
> I would recommend first testing with volatile upgrade to make sure that
> the new firmware version actually works with your card and there are no
> unpleasant surprises waiting to happen. At least some people have
> reported dropped signal strength/quality with new firmware versions. It
> is possible that the PDA on the card does not include all new
> configuration values and the defaults in the firmware image are not
> optimal for that card, etc.
>
> If you are going to download firmware images with Host AP driver, please
> use the latest CVS snapshot of it.
>
>
> > c.  Should I be compiling the Prism 2.5 kernel driver into the kernel
> > on the host ap machine as I've been doing, should I not be, or does
> > it not matter?
>
> What do you mean with "Prism 2.5 kernel driver"? orinoco_pci?
> hostap_pci? If you plan to use two different drivers for the same PCI
> card, I would not link them into the kernel image.. If it is only one
> driver, then it should be OK to link it in.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From ognjen  Tue Aug 12 01:17:07 2003
From: ognjen (Ognjen)
Date: Tue, 12 Aug 2003 10:17:07 +0200
Subject: Cisco and Prism2 AP wds
Message-ID: <200308121017.07501.ognjen@mediaworks.co.yu>

Has anyone managed to create a functional WDS between Cisco 350 Bridge and the 
Linux box with Prism2 card acting as an AP? I've been working on this for a 
long time but still no luck. I totally shut down the aironet extensions and 
the other things that might cause the problems. With any other piece of 
wireless equipment (3COM Office Connect, Allied Telesyn) WDS works.

Ognjen Seslija



From proski  Tue Aug 12 06:14:33 2003
From: proski (Pavel Roskin)
Date: Tue, 12 Aug 2003 09:14:33 -0400 (EDT)
Subject: Cisco and Prism2 AP wds
In-Reply-To: <200308121017.07501.ognjen@mediaworks.co.yu>
Message-ID: <Pine.LNX.4.44.0308120910550.2117-100000@portland.hansa.lan>

On Tue, 12 Aug 2003, Ognjen wrote:

> Has anyone managed to create a functional WDS between Cisco 350 Bridge and the
> Linux box with Prism2 card acting as an AP? I've been working on this for a
> long time but still no luck. I totally shut down the aironet extensions and
> the other things that might cause the problems. With any other piece of
> wireless equipment (3COM Office Connect, Allied Telesyn) WDS works.

You need recent firmware (secondary firmware 1.5.6 or newer) to support
WDS frames in the HostAP mode.  See list archives for details how to flash
the firmware and where to find it.

If you report problems with software, please include its version and error
messages.

-- 
Regards,
Pavel Roskin



From eduardo  Tue Aug 12 07:15:17 2003
From: eduardo (Eduardo Kaftanski)
Date: Tue, 12 Aug 2003 10:15:17 -0400
Subject: Need advice:  whether to flash DLink DWL-520
In-Reply-To: <Pine.LNX.4.56.0308111836100.6604@marabou.research.att.com>
References: <200308111515.h7BFFC3B000667@bassett.home.org>
	<20030811172814.GA6126@enriqueto.nn.cl>
	<Pine.LNX.4.56.0308111836100.6604@marabou.research.att.com>
Message-ID: <20030812141517.GA20838@enriqueto.nn.cl>

> 
> You should flash primary and secondary firmware in the same time, and use
> CVS HostAP because version 0.0.4 cannot flash primary firmware.  That
> includes updating prism2_srec to the CVS version, too.
> 

I already did that last weekend. I had tried to flash the card when the 
newest hostap was 0.0.1 or .2 :) I just was impatient.

For the record, latest CVS works perfectly and the CVS prism2_srec
flashed my card without a hitch.


-- 
Eduardo Kaftanski
eduardo at linuxcenter.cl
Red Hat Certified Engineer
Gerente Ingenieria LinuxCenter S.A.
Canada 239 5to Piso, Providencia, Stgo de Chile.
http://www.linuxcenter.cl 2745000



From prossi  Tue Aug 12 11:59:23 2003
From: prossi (Paolo Rossi)
Date: Tue, 12 Aug 2003 20:59:23 +0200
Subject: WInXP +SP1 Hostap and 802.1x authentications
Message-ID: <3F39390B.9090207@mbigroup.it>

Hi all,

I've problem with 802.1x authentication.
I have WinXp + SP1 client and a linux debian box with hostap in master 
mode. I want use 802.1x to authenticate the users. I have compiled 
hostapd and change my configuration file hostapd.conf, but i have a 
trouble. The output of hostapd is:
"nasso:/home/paolo/hostap-0.0.4/hostapd# ./hostapd hostapd.conf
Configuration file: hostapd.conf
Opening raw packet socket for ifindex 32
Using interface wlan0ap with hwaddr 00:60:b3:68:c1:3f and ssid 'test2'
Default WEP key - hexdump(len=13): 4e 43 56 0c b0 57 9a 00 47 7f 66 32 35
Flushing old station entries
Deauthenticate all stations
Received 30 bytes management frame
MGMT
mgmt::auth
authentication: STA=00:40:05:29:11:cc auth_alg=1 auth_transaction=1 
status_code=0 wep=0
Unsupported authentication algorithm (1)
authentication reply: STA=00:40:05:29:11:cc auth_alg=1 
auth_transaction=2 resp=13
Received 30 bytes management frame
MGMT (TX callback) ACK
mgmt::auth cb
handle_auth_cb: STA 00:40:05:29:11:cc not found
Received 30 bytes management frame
MGMT
mgmt::auth
authentication: STA=00:40:05:29:11:cc auth_alg=0 auth_transaction=1 
status_code=0 wep=0
Unsupported authentication algorithm (0)
authentication reply: STA=00:40:05:29:11:cc auth_alg=0 
auth_transaction=2 resp=13
Received 30 bytes management frame
MGMT (TX callback) ACK
mgmt::auth cb
handle_auth_cb: STA 00:40:05:29:11:cc not found"


Can someone help me?


Best Regards Paolo




-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: hostapd.conf
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20030812/e37f6fa9/attachment.txt 


From wireless  Tue Aug 12 10:06:48 2003
From: wireless (wireless at isabeldeespana.org)
Date: Tue, 12 Aug 2003 18:06:48 +0100
Subject: problem to install hostap-0.0.4
Message-ID: <20030812170648.26910.qmail@servidor1.isabeldeespana.org>


I have a stable debian release with a 2.4.18 kernel. I have compiled kernel 
without pcmcia support, bat with Wireless LAN support (just Wireless LAN 
support, none of the drivers under that option).
I have instaled pcmcia-source, and I have build with make-pkpg a particular 
kernel and pcmcia-cs packages.
My wireless card is Engenius NL-2511CDPlus ext2, people say that is same 
card that Senao SL-2511CDPLUS.
This card is on a pci slot with a Carbus Ricoh RL5C475. 

I have download hostap-0.0.4.tar.gz. I have read README and FAQ files. 

After read README file I execute: 

make plx, and I get following: 


make plx
gcc -I/usr/src/modules/pcmcia-cs/include 
 -I/usr/src/kernel-source-2.4.18/include -O2 -D__KERNEL__ -DMODULE -Wall -g 
 -c  -DMODVERSIONS -include 
/usr/src/kernel-source-2.4.18/include/linux/modversions.h 
 -fomit-frame-pointer -E -D__GENKSYMS__ driver/modules/hostap.c | \
       /sbin/genksyms -k 2.4.18 > driver/modules/hostap.ver
In file included from 
/usr/src/kernel-source-2.4.18/include/linux/prefetch.h:13,
                from /usr/src/kernel-source-2.4.18/include/linux/list.h:6,
                from 
/usr/src/kernel-source-2.4.18/include/linux/module.h:12,
                from /usr/src/modules/pcmcia-cs/include/linux/module.h:5,
                from driver/modules/hostap.c:21:
/usr/src/kernel-source-2.4.18/include/asm/processor.h:254: warning: 
`EISA_bus' redefined
/usr/src/kernel-source-2.4.18/include/linux/modules/i386_ksyms.ver:10: 
warning: this is the location of the previous definition
In file included from /usr/src/modules/pcmcia-cs/include/linux/module.h:5,
                from driver/modules/hostap.c:21:
/usr/src/kernel-source-2.4.18/include/linux/module.h:15: warning: `_set_ver' 
redefined
/usr/src/kernel-source-2.4.18/include/linux/modsetver.h:9: warning: this is 
the location of the previous definition
gcc -I/usr/src/modules/pcmcia-cs/include 
 -I/usr/src/kernel-source-2.4.18/include -O2 -D__KERNEL__ -DMODULE -Wall -g 
 -c  -DMODVERSIONS -include 
/usr/src/kernel-source-2.4.18/include/linux/modversions.h 
 -fomit-frame-pointer -E -D__GENKSYMS__ driver/modules/hostap_crypt.c | \
       /sbin/genksyms -k 2.4.18 > driver/modules/hostap_crypt.ver
In file included from 
/usr/src/kernel-source-2.4.18/include/linux/prefetch.h:13,
                from /usr/src/kernel-source-2.4.18/include/linux/list.h:6,
                from 
/usr/src/kernel-source-2.4.18/include/linux/module.h:12,
                from /usr/src/modules/pcmcia-cs/include/linux/module.h:5,
                from driver/modules/hostap_crypt.c:18:
/usr/src/kernel-source-2.4.18/include/asm/processor.h:254: warning: 
`EISA_bus' redefined
/usr/src/kernel-source-2.4.18/include/linux/modules/i386_ksyms.ver:10: 
warning: this is the location of the previous definition
In file included from /usr/src/modules/pcmcia-cs/include/linux/module.h:5,
                from driver/modules/hostap_crypt.c:18:
/usr/src/kernel-source-2.4.18/include/linux/module.h:15: warning: `_set_ver' 
redefined
/usr/src/kernel-source-2.4.18/include/linux/modsetver.h:9: warning: this is 
the location of the previous definition
gcc -I/usr/src/modules/pcmcia-cs/include 
 -I/usr/src/kernel-source-2.4.18/include -include 
driver/modules/hostap_crypt.ver -include driver/modules/hostap.ver -O2 
 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS -include 
/usr/src/kernel-source-2.4.18/include/linux/modversions.h 
 -fomit-frame-pointer -o driver/modules/hostap_plx.o 
driver/modules/hostap_plx.c
In file included from 
/usr/src/kernel-source-2.4.18/include/linux/prefetch.h:13,
                from /usr/src/kernel-source-2.4.18/include/linux/list.h:6,
                from 
/usr/src/kernel-source-2.4.18/include/linux/module.h:12,
                from /usr/src/modules/pcmcia-cs/include/linux/module.h:5,
                from driver/modules/hostap_plx.c:12:
/usr/src/kernel-source-2.4.18/include/asm/processor.h:254: warning: 
`EISA_bus' redefined
/usr/src/kernel-source-2.4.18/include/linux/modules/i386_ksyms.ver:10: 
warning: this is the location of the previous definition
In file included from driver/modules/hostap_plx.c:243:
driver/modules/hostap_hw.c: In function `hfa384x_allocate_fid':
driver/modules/hostap_hw.c:801: warning: implicit declaration of function 
`yield'
gcc -I/usr/src/modules/pcmcia-cs/include 
 -I/usr/src/kernel-source-2.4.18/include -include 
driver/modules/hostap_crypt.ver -include driver/modules/hostap.ver -O2 
 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS -include 
/usr/src/kernel-source-2.4.18/include/linux/modversions.h 
 -fomit-frame-pointer -o driver/modules/hostap.o driver/modules/hostap.c
In file included from 
/usr/src/kernel-source-2.4.18/include/linux/prefetch.h:13,
                from /usr/src/kernel-source-2.4.18/include/linux/list.h:6,
		  from /usr/src/kernel-source-2.4.18/include/linux/module.h:12,
                from /usr/src/modules/pcmcia-cs/include/linux/module.h:5,
                from driver/modules/hostap.c:21:
/usr/src/kernel-source-2.4.18/include/asm/processor.h:254: warning: 
`EISA_bus' redefined
/usr/src/kernel-source-2.4.18/include/linux/modules/i386_ksyms.ver:10: 
warning: this is the location of the previous definition
gcc -I/usr/src/modules/pcmcia-cs/include 
 -I/usr/src/kernel-source-2.4.18/include -include 
driver/modules/hostap_crypt.ver -include driver/modules/hostap.ver -O2 
 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS -include 
/usr/src/kernel-source-2.4.18/include/linux/modversions.h 
 -fomit-frame-pointer -o driver/modules/hostap_crypt.o 
driver/modules/hostap_crypt.c
In file included from 
/usr/src/kernel-source-2.4.18/include/linux/prefetch.h:13,
                from /usr/src/kernel-source-2.4.18/include/linux/list.h:6,
                from 
/usr/src/kernel-source-2.4.18/include/linux/module.h:12,
                from /usr/src/modules/pcmcia-cs/include/linux/module.h:5,
                from driver/modules/hostap_crypt.c:18:
/usr/src/kernel-source-2.4.18/include/asm/processor.h:254: warning: 
`EISA_bus' redefined
/usr/src/kernel-source-2.4.18/include/linux/modules/i386_ksyms.ver:10: 
warning: this is the location of the previous definition
gcc -I/usr/src/modules/pcmcia-cs/include 
 -I/usr/src/kernel-source-2.4.18/include -include 
driver/modules/hostap_crypt.ver -include driver/modules/hostap.ver -O2 
 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS -include 
/usr/src/kernel-source-2.4.18/include/linux/modversions.h 
 -fomit-frame-pointer -o driver/modules/hostap_crypt_wep.o 
driver/modules/hostap_crypt_wep.c
In file included from 
/usr/src/kernel-source-2.4.18/include/linux/prefetch.h:13,
                from /usr/src/kernel-source-2.4.18/include/linux/list.h:6,
                from 
/usr/src/kernel-source-2.4.18/include/linux/module.h:12,
                from /usr/src/modules/pcmcia-cs/include/linux/module.h:5,
                from driver/modules/hostap_crypt_wep.c:14:
/usr/src/kernel-source-2.4.18/include/asm/processor.h:254: warning: 
`EISA_bus' redefined
/usr/src/kernel-source-2.4.18/include/linux/modules/i386_ksyms.ver:10: 
warning: this is the location of the previous definition 

Run 'make install_pccard' as root to install hostap_cs.o
Run 'make install_plx' as root to install hostap_plx.o
Run 'make install_pci' as root to install hostap_pci.o
bota:~/hostap/hostap-0.0.4# 

 

After I run make install_plx and so I get: 

bota:~/hostap/hostap-0.0.4# make install_plx
Installing hostap_crypt*.o to /lib/modules/2.4.18/net
mkdir -p /lib/modules/2.4.18/net
cp -f driver/modules/hostap_crypt*.o /lib/modules/2.4.18/net
Installing hostap.o to /lib/modules/2.4.18/net
mkdir -p /lib/modules/2.4.18/net
cp -f driver/modules/hostap.o /lib/modules/2.4.18/net
Installing hostap_plx.o to /lib/modules/2.4.18/net
mkdir -p /lib/modules/2.4.18/net
cp -f driver/modules/hostap_plx.o /lib/modules/2.4.18/net
/sbin/depmod -ae
depmod: *** Unresolved symbols in /lib/modules/2.4.18/net/hostap_plx.o
depmod:         yield
make: *** [install_plx] Error 1 


I attach you too the system log when I start /etc/init.d/pcmcia: 


Aug 12 17:19:47 bota kernel: Linux PCMCIA Card Services 3.1.33
Aug 12 17:19:47 bota kernel:   kernel build: 2.4.18 unknown
Aug 12 17:19:47 bota kernel:   options:  [pci] [cardbus] [apm]
Aug 12 17:19:47 bota kernel: Intel ISA/PCI/CardBus PCIC probe:
Aug 12 17:19:47 bota kernel: PCI: Found IRQ 5 for device 00:10.0
Aug 12 17:19:47 bota kernel:   Ricoh RL5C475 rev 80 PCI-to-CardBus at slot 
00:10, mem 0xf75fe000
Aug 12 17:19:47 bota kernel:     host opts [0]: [isa irq] [io 3/6/1] [mem 
3/6/1] [pci irq 5] [lat 168/176] [bus 2/5]
Aug 12 17:19:47 bota kernel:     ISA irqs (default) = 3,4,7,10,11,12 PCI 
status changes
Aug 12 17:19:47 bota cardmgr[25080]: starting, version is 3.1.33
Aug 12 17:19:47 bota cardmgr[25080]: watching 1 sockets
Aug 12 17:19:48 bota kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Aug 12 17:19:48 bota cardmgr[25080]: socket 0: Senao SL-2511CD/SL-2511CDPLUS
Aug 12 17:19:48 bota cardmgr[25080]: executing: 'modprobe hostap_crypt'
Aug 12 17:19:48 bota kernel: hostap_crypt: registered algorithm 'NULL'
Aug 12 17:19:48 bota cardmgr[25080]: executing: 'modprobe hostap'
Aug 12 17:19:48 bota cardmgr[25080]: executing: 'modprobe hostap_cs'
Aug 12 17:19:48 bota cardmgr[25080]: + modprobe: Can't locate module 
hostap_cs
Aug 12 17:19:48 bota cardmgr[25080]: modprobe exited with status 255
Aug 12 17:19:48 bota cardmgr[25080]: module 
/lib/modules/2.4.18/pcmcia/hostap_cs.o not available
Aug 12 17:19:50 bota cardmgr[25080]: get dev info on socket 0 failed: 
Resource temporarily unavailable 


On the FAQ file you can read 

What is causing 'Unresolved symbols' in depmod/modprobe? 

This not my problem since I configure, compile and install the kernel
my self (with debian make-kpkg utility). 


On the README file in Installation and Configuration section you read : 

If you are using hostap_plx.o version, prism2_plx_known_manfids table
in driver/modules/hostap_plx.c needs to have an entry for the PC Card
you are using. 

I added the line:
{ 0x0156, 0x0002 } /* Senao SL-2511CDPLUS */,
to prism2_plx_known_manfids on hostap_plx.c file. 

Could somebody help me to compile hostap successfully. 

Thanks in advance. 



From proski  Tue Aug 12 11:26:31 2003
From: proski (Pavel Roskin)
Date: Tue, 12 Aug 2003 14:26:31 -0400 (EDT)
Subject: problem to install hostap-0.0.4
In-Reply-To: <20030812170648.26910.qmail@servidor1.isabeldeespana.org>
References: <20030812170648.26910.qmail@servidor1.isabeldeespana.org>
Message-ID: <Pine.LNX.4.56.0308121423390.1695@marabou.research.att.com>

On Tue, 12 Aug 2003 wireless at isabeldeespana.org wrote:

> /sbin/depmod -ae
> depmod: *** Unresolved symbols in /lib/modules/2.4.18/net/hostap_plx.o
> depmod:         yield
> make: *** [install_plx] Error 1

This was fixed in CVS.  Newer kernels have "yield" function, but not
2.4.18.  You can replace "yield" with "schedule" as a workaround.

-- 
Regards,
Pavel Roskin



From thomas  Tue Aug 12 11:46:55 2003
From: thomas (Thomas Rulmont)
Date: Tue, 12 Aug 2003 20:46:55 +0200
Subject: AP mode
Message-ID: <001901c36102$1a38e130$0b00a8c0@nexusinformatique.com>

Does the AP mode that your card implements use any chip funtion, or is it full software ?
In other words: Do you think other chipset could allow AP mode ?

Thomas Rulmont 
-----

thomas at nexus-informatique.com 
trulmont at hotmail.com 
+32 486 863216 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030812/6ed9ec6f/attachment.htm 


From wireless  Tue Aug 12 13:15:52 2003
From: wireless (wireless at isabeldeespana.org)
Date: Tue, 12 Aug 2003 21:15:52 +0100
Subject: problem to install hostap-0.0.4
In-Reply-To: <Pine.LNX.4.56.0308121423390.1695@marabou.research.att.com>
References: <20030812170648.26910.qmail@servidor1.isabeldeespana.org>
            <Pine.LNX.4.56.0308121423390.1695@marabou.research.att.com>
Message-ID: <20030812201552.27352.qmail@servidor1.isabeldeespana.org>

Ok I have downloaded hostap.tar.gz, the snapshot of the driver source code. 

I install it and works, but if I try "modprobe hostap_plx"  I get: 


modprobe hostap_plx
/lib/modules/2.4.18/net/hostap_plx.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including 
invalid IO or IRQ parameters
/lib/modules/2.4.18/net/hostap_plx.o: insmod 
/lib/modules/2.4.18/net/hostap_plx.o failed
/lib/modules/2.4.18/net/hostap_plx.o: insmod hostap_plx failed 


Could you help me again? 

 

 

 

 

Pavel Roskin wrote: 

 


> On Tue, 12 Aug 2003 wireless at isabeldeespana.org wrote: 
> 
>> /sbin/depmod -ae
>> depmod: *** Unresolved symbols in /lib/modules/2.4.18/net/hostap_plx.o
>> depmod:         yield
>> make: *** [install_plx] Error 1
> 
> This was fixed in CVS.  Newer kernels have "yield" function, but not
> 2.4.18.  You can replace "yield" with "schedule" as a workaround. 
> 
> -- 
> Regards,
> Pavel Roskin
 



From proski  Tue Aug 12 13:33:38 2003
From: proski (Pavel Roskin)
Date: Tue, 12 Aug 2003 16:33:38 -0400 (EDT)
Subject: problem to install hostap-0.0.4
In-Reply-To: <20030812201552.27352.qmail@servidor1.isabeldeespana.org>
References: <20030812170648.26910.qmail@servidor1.isabeldeespana.org>      
      <Pine.LNX.4.56.0308121423390.1695@marabou.research.att.com>
 <20030812201552.27352.qmail@servidor1.isabeldeespana.org>
Message-ID: <Pine.LNX.4.56.0308121629100.15875@marabou.research.att.com>

On Tue, 12 Aug 2003 wireless at isabeldeespana.org wrote:

> Ok I have downloaded hostap.tar.gz, the snapshot of the driver source code.
>
> I install it and works, but if I try "modprobe hostap_plx"  I get:
>
>
> modprobe hostap_plx
> /lib/modules/2.4.18/net/hostap_plx.o: init_module: No such device
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters

In the original message you said that your card is PCMCIA, not PLX.  It
was clear from the log that you were trying to load the PCMCIA driver.
Now you are trying the PLX driver, and of course it cannot find the
device.  I think we are going in circles.

-- 
Regards,
Pavel Roskin



From wireless  Tue Aug 12 13:49:54 2003
From: wireless (wireless at isabeldeespana.org)
Date: Tue, 12 Aug 2003 21:49:54 +0100
Subject: problem to install hostap-0.0.4
In-Reply-To: <Pine.LNX.4.56.0308121629100.15875@marabou.research.att.com>
References: <20030812170648.26910.qmail@servidor1.isabeldeespana.org>
            <Pine.LNX.4.56.0308121423390.1695@marabou.research.att.com>
            <20030812201552.27352.qmail@servidor1.isabeldeespana.org>
            <Pine.LNX.4.56.0308121629100.15875@marabou.research.att.com>
Message-ID: <20030812204954.27491.qmail@servidor1.isabeldeespana.org>

Well... I have a pcmcia in a CArdbus Ricoh Adapter pci for pcmcia. I thought
that I had to load the plx module... 

In the log you see the pcmcia driver because every time I execute 

/etc/init.d/pcmcia start, is pcmcia driver which is loaded and not the plx
driver. 

Anyway, there is a way to solve the problem and load the correct module. 

And somebody could help me to find out which is the correct module? 

 


Pavel Roskin wrote: 

> On Tue, 12 Aug 2003 wireless at isabeldeespana.org wrote: 
> 
>> Ok I have downloaded hostap.tar.gz, the snapshot of the driver source code. 
>>
>> I install it and works, but if I try "modprobe hostap_plx"  I get: 
>>
>>
>> modprobe hostap_plx
>> /lib/modules/2.4.18/net/hostap_plx.o: init_module: No such device
>> Hint: insmod errors can be caused by incorrect module parameters, including
>> invalid IO or IRQ parameters
> 
> In the original message you said that your card is PCMCIA, not PLX.  It
> was clear from the log that you were trying to load the PCMCIA driver.
> Now you are trying the PLX driver, and of course it cannot find the
> device.  I think we are going in circles. 
> 
> -- 
> Regards,
> Pavel Roskin
 



From sleibt  Tue Aug 12 13:56:36 2003
From: sleibt (SLeiBt)
Date: 12 Aug 2003 22:56:36 +0200
Subject: SMP troubles w PCI card
Message-ID: <1060721796.6459.14.camel@act.irishseb.dyndns.org>

Hi list!

I finaly got a chance to test my netgear PCI card (that would be MA311 I
think) with hostap and a wifi-enabled laptop.

With the card as sold this spring, abit BP6 with 2 333 celerons and
512Mb ram (nothing overclocked), kernel 2.4.21 smp and hostap 0.0.3 as
in debian unstable, I got twice hard lookups exactly the same as
described in the list, within 2 or maybe 3mn of connecting with the
laptop. Very quick, very little data exchanged, both computers very
close.

I then removed one CPU, changed nothing else (still SMP kernel, but with
only the one cpu), and used the link for 2 hours and more than 300Mb
without a hitch even while moving around.

I will test cvs as soon as I can think in front of my computer rather
than just melt. Hope this will be soon, thank you all for that piece of
software.

Regards,

Sebastien



From izh  Tue Aug 12 15:15:40 2003
From: izh (Oleg Izhvanov)
Date: Wed, 13 Aug 2003 02:15:40 +0400
Subject: WInXP +SP1 Hostap and 802.1x authentications
In-Reply-To: <3F39390B.9090207@mbigroup.it>
References: <3F39390B.9090207@mbigroup.it>
Message-ID: <3F39670C.1050005@openlan.ru>

Paolo Rossi wrote:

> Hi all,
>
> I've problem with 802.1x authentication.
> I have WinXp + SP1 client and a linux debian box with hostap in master 
> mode. I want use 802.1x to authenticate the users. I have compiled 
> hostapd and change my configuration file hostapd.conf, but i have a 
> trouble. The output of hostapd is:
> "nasso:/home/paolo/hostap-0.0.4/hostapd# ./hostapd hostapd.conf
> Configuration file: hostapd.conf
> Opening raw packet socket for ifindex 32
> Using interface wlan0ap with hwaddr 00:60:b3:68:c1:3f and ssid 'test2'
> Default WEP key - hexdump(len=13): 4e 43 56 0c b0 57 9a 00 47 7f 66 32 35
> Flushing old station entries
> Deauthenticate all stations
> Received 30 bytes management frame
> MGMT
> mgmt::auth
> authentication: STA=00:40:05:29:11:cc auth_alg=1 auth_transaction=1 
> status_code=0 wep=0 

It seems that your SP1 client uses Shared Authentication algorithm, but 
support for it
disabled in your hostapd.conf config file. Either disable Shared 
Authentication on the client or
enable it in the hostapd by setting auth_algs variable to 3 (with Open 
Authentication algoritm
enables), or to 1 (with Open Authentication algorithm disabled).

>
> Unsupported authentication algorithm (1)
> authentication reply: STA=00:40:05:29:11:cc auth_alg=1 
> auth_transaction=2 resp=13
> Received 30 bytes management frame
> MGMT (TX callback) ACK
> mgmt::auth cb
> handle_auth_cb: STA 00:40:05:29:11:cc not found
> Received 30 bytes management frame
> MGMT
> mgmt::auth
> authentication: STA=00:40:05:29:11:cc auth_alg=0 auth_transaction=1 
> status_code=0 wep=0
> Unsupported authentication algorithm (0)
> authentication reply: STA=00:40:05:29:11:cc auth_alg=0 
> auth_transaction=2 resp=13
> Received 30 bytes management frame
> MGMT (TX callback) ACK
> mgmt::auth cb
> handle_auth_cb: STA 00:40:05:29:11:cc not found"
>
>
> Can someone help me?
>
>
> Best Regards Paolo
>
>
>
>
>------------------------------------------------------------------------
>
>##### hostapd configuration file ##############################################
># Empty lines and lines starting with # are ignored
>
># AP netdevice name (without 'ap' prefix, i.e., wlan0 uses wlan0ap for
># management frames)
>interface=wlan0
>
># hostapd event logger configuration
>#
># Two output method: syslog and stdout (only usable if not forking to
># background).
>#
># Module bitfield (ORed bitfield of modules that will be logged; -1 = all
># modules):
># bit 0 (1) = IEEE 802.11
># bit 1 (2) = IEEE 802.1X
># bit 2 (4) = RADIUS
>#
># Levels (minimum value for logged events):
>#  0 = verbose debugging
>#  1 = debugging
>#  2 = informational messages
>#  3 = notification
>#  4 = warning
>#
>logger_syslog=4
>logger_syslog_level=3
>logger_stdout=4
>logger_stdout_level=3
>
># Debugging: 0 = no, 1 = minimal, 2 = verbose, 3 = msg dumps
>debug=2
>
># Dump file for state information (on SIGUSR1)
>dump_file=/tmp/hostapd.dump
>
># Daemonize hostapd process (i.e., fork to background)
>daemonize=1
>
>
>##### IEEE 802.11 related configuration #######################################
>
># SSID to be used in IEEE 802.11 management frames
>ssid=test2
>
># Station MAC address -based authentication
># 0 = accept unless in deny list
># 1 = deny unless in accept list
># 2 = use external RADIUS server (accept/deny lists are searched first)
>macaddr_acl=2
>
># Accept/deny lists are read from separate files (containing list of
># MAC addresses, one per line). Use absolute path name to make sure that the
># files can be read on SIGHUP configuration reloads.
>#accept_mac_file=/etc/hostapd.accept
>#deny_mac_file=/etc/hostapd.deny
>
># IEEE 802.11 specifies two authentication algorithms. hostapd can be
># configured to allow both of these or only one. Open system authentication
># should be used with IEEE 802.1X.
># Bit fields of allowed authentication algorithms:
># bit 0 = Open System Authentication
># bit 1 = Shared Key Authentication (requires WEP)
>auth_algs=0
>
># Associate as a station to another AP while still acting as an AP on the same
># channel.
>#assoc_ap_addr=00:12:34:56:78:9a
>
>
>##### IEEE 802.1X (and IEEE 802.1aa/D4) related configuration #################
>
># Require IEEE 802.1X authorization
>ieee8021x=1
>
># Use internal minimal EAP Authentication Server for testing IEEE 802.1X.
># This should only be used for testing since it authorizes all users that
># suppot IEEE 802.1X without any keys or certificates.
>#minimal_eap=0
>
># Optional displayable message sent with EAP Request-Identity
>#eap_message=hello
>
># WEP rekeying (disabled if key lengths are not set or are set to 0)
># Key lengths for default/broadcast and individual/unicast keys:
># 5 = 40-bit WEP (also known as 64-bit WEP with 40 secret bits)
># 13 = 104-bit WEP (also known as 128-bit WEP with 104 secret bits)
>wep_key_len_broadcast=13
>wep_key_len_unicast=13
># Rekeying period in seconds. 0 = do not rekey (i.e., set keys only once)
>wep_rekey_period=1800
>
># EAPOL-Key index workaround (set bit7) for WinXP Supplicant (needed only if
># only broadcast keys are used)
>eapol_key_index_workaround=64
>
>
>##### IEEE 802.11f - Inter-Access Point Protocol (IAPP) #######################
>
># Interface to be used for IAPP broadcast packets
>#iapp_interface=eth0
>
>
>##### RADIUS configuration ####################################################
># for IEEE 802.1X with external Authentication Server, IEEE 802.11
># authentication with external ACL for MAC addresses, and accounting
>
># The own IP address of the access point (used as NAS-IP-Address)
>own_ip_addr=192.168.x.xx
>
># RADIUS authentication server
>auth_server_addr=192.168.x.xx
>auth_server_port=1812
>auth_server_shared_secret=password
>
># RADIUS accounting server
>#acct_server_addr=127.0.0.1
>#acct_server_port=1813
>#acct_server_shared_secret=secret
>
># Secondary RADIUS servers; to be used if primary one does not reply to
># RADIUS packets. These are optional and there can be more than one secondary
># server listed.
>#auth_server_addr=127.0.0.2
>#auth_server_port=1812
>#auth_server_shared_secret=secret2
>#
>#acct_server_addr=127.0.0.2
>#acct_server_port=1813
>#acct_server_shared_secret=secret2
>
># Retry interval for trying to return to the primary RADIUS server (in
># seconds). RADIUS client code will automatically try to use the next server
># when the current server is not replying to requests. If this interval is set,
># primary server will be retried after configured amount of time even if the
># currently used secondary server is still working.
>radius_retry_primary_interval=600
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
--
Best Regards, Oleg Izhvanov



From williamt  Tue Aug 12 15:40:59 2003
From: williamt (William Tai)
Date: Tue, 12 Aug 2003 15:40:59 -0700
Subject: Txpower control by PDA modification
Message-ID: <008001c36122$cd365c20$e6f0c53f@williamt>

Hi All:

    I've tried to control Tx power by modifying PDR 0x301 and PDR x0300.
How do I do after modification of PDA so that card knows it's time to change
set points and integrator value.

Thanx
William



From proski  Tue Aug 12 15:35:03 2003
From: proski (Pavel Roskin)
Date: Tue, 12 Aug 2003 18:35:03 -0400 (EDT)
Subject: problem to install hostap-0.0.4
In-Reply-To: <20030812204954.27491.qmail@servidor1.isabeldeespana.org>
References: <20030812170648.26910.qmail@servidor1.isabeldeespana.org>      
      <Pine.LNX.4.56.0308121423390.1695@marabou.research.att.com>          
  <20030812201552.27352.qmail@servidor1.isabeldeespana.org>           
 <Pine.LNX.4.56.0308121629100.15875@marabou.research.att.com>
 <20030812204954.27491.qmail@servidor1.isabeldeespana.org>
Message-ID: <Pine.LNX.4.56.0308121822240.25885@marabou.research.att.com>

On Tue, 12 Aug 2003 wireless at isabeldeespana.org wrote:

> Well... I have a pcmcia in a CArdbus Ricoh Adapter pci for pcmcia. I thought
> that I had to load the plx module...

You must have been mislead by somebody or by some document.  It's better
that you explain why you think so, so that the misleading document could
be fixed.  It's better to do it once than to explain the same thing over
and over again to different users.

hostap_plx is only for PLX and TMD adapters, not for Ricoh or any other
full-featured PCMCIA or CardBus adapter.

> In the log you see the pcmcia driver because every time I execute
>
> /etc/init.d/pcmcia start, is pcmcia driver which is loaded and not the
> plx driver.

That should work now.  It didn't work because you had unresolved symbols.

> Anyway, there is a way to solve the problem and load the correct module.
> And somebody could help me to find out which is the correct module?

It's described in README.  The module is called hostap_cs.  It should be
loaded by cardmgr, not manually.  "/etc/init.d/pcmcia start" should do the
right thing.

-- 
Regards,
Pavel Roskin



From heeyeoly  Tue Aug 12 16:01:55 2003
From: heeyeoly (Yu, Heeyeol)
Date: Tue, 12 Aug 2003 18:01:55 -0500
Subject: retry in hfa384x_tx_frame structure
Message-ID: <005e01c36125$bcff5480$3e88b383@yuatxp>

Hi hostAP

 

I found that retry member variable in hfa384x_tx_frame structure.

My question is that it's not implemented yet.

Furthermore is the purpose of retry is setting retry in every packet
while sending it?

 

Best regards

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


From jkmaline  Tue Aug 12 18:21:06 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 12 Aug 2003 18:21:06 -0700
Subject: WInXP +SP1 Hostap and 802.1x authentications
In-Reply-To: <3F39390B.9090207@mbigroup.it>
References: <3F39390B.9090207@mbigroup.it>
Message-ID: <20030813012106.GA3898@jm.kir.nu>

On Tue, Aug 12, 2003 at 08:59:23PM +0200, Paolo Rossi wrote:

> Unsupported authentication algorithm (1)
> Unsupported authentication algorithm (0)


> ##### hostapd configuration file ##############################################
> # IEEE 802.11 specifies two authentication algorithms. hostapd can be
> # configured to allow both of these or only one. Open system authentication
> # should be used with IEEE 802.1X.
> # Bit fields of allowed authentication algorithms:
> # bit 0 = Open System Authentication
> # bit 1 = Shared Key Authentication (requires WEP)
> auth_algs=0

You seem to have disabled all authentication algorithms. In practice,
this means that no one is able to use your AP.. I should probably just
change hostapd to reject that kind of configuration. Anyway, auth_algs
is a bit field and it should be set to 1 (i.e., bit0 set) to allow Open
System Authentication when using IEEE 802.1X. Other possible values are
2 (only Shared Key Auth) and 3 (both Open System and Shared Key
accepted), but these should not be used with IEEE 802.1X.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Aug 12 18:22:07 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 12 Aug 2003 18:22:07 -0700
Subject: AP mode
In-Reply-To: <001901c36102$1a38e130$0b00a8c0@nexusinformatique.com>
References: <001901c36102$1a38e130$0b00a8c0@nexusinformatique.com>
Message-ID: <20030813012207.GB3898@jm.kir.nu>

On Tue, Aug 12, 2003 at 08:46:55PM +0200, Thomas Rulmont wrote:

> Does the AP mode that your card implements use any chip funtion, or is it full software ?
> In other words: Do you think other chipset could allow AP mode ?

I don't think that either of these questions would directly indicate
that the other one is true, too.. Anyway, answers to this: Host AP mode
requires some functionality from the Prism2 chipset/firmware and other
chipsets allow AP mode (not identical to Host AP mode in Prism2, but
similar).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jhiller  Tue Aug 12 20:01:13 2003
From: jhiller (James B. Hiller)
Date: Tue, 12 Aug 2003 23:01:13 -0400 (EDT)
Subject: Need advice:  whether to flash DLink DWL-520
In-Reply-To: <20030812013410.GA4120@jm.kir.nu> from "Jouni Malinen" at Aug 11,
	2003 06:34:11 PM
Message-ID: <200308130301.h7D31DbV004778@bassett.home.org>

> > The DWL-520 in Machine A performing the host function has:
> > 
> > NIC ID=x8013 v1.0.0
> > PRI ID=x15 v1.0.5
> > STA ID=x1f v1.3.4
> 
> > a.  Is there a good reason to upgrade the firmware on this card
> > serving as the host AP/router?  If so, to which versions, using
> > which tool, available where (firmware and tool)?  Should I do only
> > the volatile, and if so, would I need to do the non-volatile to get
> > to a version which supports non-volatile?
> 
> Yes, you should consider upgrading the firmware. That combination of
> PRI/STA firmware is known to have a bug that causes corruption of data
> on PCI bus. This was fixed in PRI 1.0.7 / STA 1.3.5, so it or anything
> newer is probably better solution.

I'd seen that reference before, I think on seattlewireless.org.
For my clarity:  is this something DLink themselves would be aware of,
or is it something they specifically would NOT be aware of (or would
disavow knowledge of) since it only happens in host ap mode, and they
don't market the card for that purpose?

Also, can you tell me anything about the likely observable behavior of
this bug happening?  Like, are we talking system crash, or slow card
throughput, or what?  (Not arguing; just learning).

> I would recommend first testing with volatile upgrade to make sure that
> the new firmware version actually works with your card and there are no
> unpleasant surprises waiting to happen. At least some people have
> reported dropped signal strength/quality with new firmware versions. It
> is possible that the PDA on the card does not include all new
> configuration values and the defaults in the firmware image are not
> optimal for that card, etc.

Ok.

> If you are going to download firmware images with Host AP driver, please
> use the latest CVS snapshot of it.

Yep, been told that.  (CVS intimidates me - any thought on when next
release will be out?)
> 
> 
> > c.  Should I be compiling the Prism 2.5 kernel driver into the kernel
> > on the host ap machine as I've been doing, should I not be, or does
> > it not matter?
> 
> What do you mean with "Prism 2.5 kernel driver"? orinoco_pci?

Kernel symbols are config_hermes and config_pci_hermes.

> hostap_pci? If you plan to use two different drivers for the same PCI
> card, I would not link them into the kernel image.. If it is only one
> driver, then it should be OK to link it in.

I have no particular desire/intent to use two different ones.  It had
just occurred to me that since I had at first been using the card just
in ad hoc mode, to get it running I compiled in these two items
above (config_hermes and config_pci_hermes); and then when I got
hostap (pci) and built it, I neglected to un-config these drivers, so
I was wondering if I should now go rebuild the kernel without them.

thx,
jbh



From jkmaline  Tue Aug 12 20:41:37 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 12 Aug 2003 20:41:37 -0700
Subject: Need advice:  whether to flash DLink DWL-520
In-Reply-To: <200308130301.h7D31DbV004778@bassett.home.org>
References: <20030812013410.GA4120@jm.kir.nu>
	<200308130301.h7D31DbV004778@bassett.home.org>
Message-ID: <20030813034137.GA8723@jm.kir.nu>

On Tue, Aug 12, 2003 at 11:01:13PM -0400, James B. Hiller wrote:

> > Yes, you should consider upgrading the firmware. That combination of
> > PRI/STA firmware is known to have a bug that causes corruption of data
> > on PCI bus. This was fixed in PRI 1.0.7 / STA 1.3.5, so it or anything
> > newer is probably better solution.

> I'd seen that reference before, I think on seattlewireless.org.
> For my clarity:  is this something DLink themselves would be aware of,
> or is it something they specifically would NOT be aware of (or would
> disavow knowledge of) since it only happens in host ap mode, and they
> don't market the card for that purpose?

Assuming they are following information available from Intersil about
changes in firmware versions, they most certainly should be aware of the
issues. This particular problem causes problems in all modes so it is
not limited to Host AP in any way.

> Also, can you tell me anything about the likely observable behavior of
> this bug happening?  Like, are we talking system crash, or slow card
> throughput, or what?  (Not arguing; just learning).

This issue corrupts at least contents of received frames. This can show
up in odd looking error messages from the driver (like unknown port or
invalid length of the packet, etc.) and corrupted data frames (likely to
be dropped by TCP/IP stack). Consequently, it can drop throughput quite
a bit. I do not remember exact numbers, but comparing card with
1.0.5/1.3.4 to one with 1.0.7/1.3.5 showed huge difference in one of my
test systems.

Host AP driver is not supposed to crash with any data corruption from
the card; if it does, it should be fixed not to crash ;-). Anyway, I
have never seen a crash that would have been explained by corruption
caused by this issue.

> Yep, been told that.  (CVS intimidates me - any thought on when next
> release will be out?)

Sorry, no.

> I have no particular desire/intent to use two different ones.  It had
> just occurred to me that since I had at first been using the card just
> in ad hoc mode, to get it running I compiled in these two items
> above (config_hermes and config_pci_hermes); and then when I got
> hostap (pci) and built it, I neglected to un-config these drivers, so
> I was wondering if I should now go rebuild the kernel without them.

Both driver are trying to control the same hardware if you have them
loaded at the same time. I have never tested that kind of configuration,
but I would guess that Linux PCI code would select one of them based on
the order they were registered.. You might have hard time overriding the
one linked into the kernel with a kernel module.

-- 
Jouni Malinen                                            PGP id EFC895FA



From williamt  Tue Aug 12 22:23:46 2003
From: williamt (William Tai)
Date: Tue, 12 Aug 2003 22:23:46 -0700
Subject: How to force client to associate another AP
Message-ID: <00ed01c3615b$11f34660$e6f0c53f@williamt>

Hi All:

    I can not force the client to associate with another AP with weak signal quality even though I send deauthencate packet to the client.
The client still try to associate with my AP.
IT looks like that client does not pick another AP to associate with.


Thanx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030812/ce9b1143/attachment.htm 


From timo.vanhatupa  Tue Aug 12 23:55:47 2003
From: timo.vanhatupa (Timo Vanhatupa)
Date: Wed, 13 Aug 2003 09:55:47 +0300
Subject: How to force client to associate another AP
In-Reply-To: <00ed01c3615b$11f34660$e6f0c53f@williamt>
References: <00ed01c3615b$11f34660$e6f0c53f@williamt>
Message-ID: <3F39E0F3.1020706@tut.fi>

Hi

I have done it using access control list and it seems to work.
First I set deny policy for access control list and then deny client's 
access and kick it out.

iwpriv wlan0 maccmd 2
iwpriv wlan0 addmac <mac addr>
iwpriv wlan0 kickmac <mac addr>

At least my clients seem to find their way to other APs. I would like to 
know if this does not work
with all clients.

Still I haven't figured out how to know which access points can be heard 
by the client.
Does anyone have ideas how an AP could scan/listen clients that are not 
associated with it and are on the different channel?
If this information would be available it would be easy to force clients 
to selected APs.

Best Regards,
    Timo Vanhatupa


William Tai wrote:

> Hi All:
>  
>     I can not force the client to associate with another AP *with 
> weak signal quality* even though I send deauthencate packet to the client.
> The client still try to associate with my AP.
> IT looks like that client does not pick another AP to associate with.
>  
>  
> Thanx
>
>------------------------------------------------------------------------
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>  
>



From chhabra  Wed Aug 13 00:16:01 2003
From: chhabra (Madhusudan Singh)
Date: Wed, 13 Aug 2003 03:16:01 -0400
Subject: Query about WEP and dynamic keys
Message-ID: <3F39E5B1.7010804@eecs.umich.edu>

Hi
    Thanks to all the help, I managed to set up my access point and get 
my DHCP server to issue leases, etc.

    I am using wep with a fixed key in the restricted mode, and was 
thinking if a better mechanism could be devised, say, something similar 
to the Kerberos ticket mechanism / ssh. I somehow do not like the idea 
of storing the key (even if the server be behind a hardened firewall) in 
short plain text form, which could compromise the security if the fixed 
key became accidently known.

    Also, if I have a large pool of users (say 6-8), this key would have 
to be given to all of them, increasing the risk of disclosure. I have 
MAC address matching in place, but I want to make it more secure in the 
fashion of ssh as mentioned earlier, including an RSA passphrase 
mechanism for each client that logs on.

    Forgive me if all this sounds rather vague. I am not exactly savvy 
with WEP.

Thanks,

MS



From askatti  Wed Aug 13 00:37:13 2003
From: askatti (Anand S. Katti)
Date: Wed, 13 Aug 2003 13:07:13 +0530 (IST)
Subject: Hostap+avaya pci-card+SURECOM PCMCIA-CARD(EP-9427)+RHL 9.0 
In-Reply-To: <20030813012921.9E89324592@mail.iocaine.com>
Message-ID: <Pine.LNX.4.33.0308131253090.32120-100000@ece.iisc.ernet.in>


Dear All,
This is my first mail to this mailing list. I believe you enjoy 
solving the problems.
Here is my problem hope u help me out.

Im trying to install Hostap ver 0.0.4 on RHL 9.0
I have

1.Avaya pci card
2.Surecom pcmcia card(I dont know how to find out the chipset for this 
card? does anyone know how to figure out? Well when i insert this card in 
to the RHL9.0 m/c and i do lsmod, it lists orinoco_cs module.

I untar the hostap.gz gile and went thru the README,
Since im using "pcmcia card with pci card" I followed the installation 
instructions given for "PCI CARDS BASED ON PRISM2.5  hostap_pci.o" section 
from README file.

i edited the KERNEL_PATH to point to /usr/src/linux-2.4.20-8
and typed "make pci"
I got the following error.

[root at ROUTERH hostap-0.0.4]# make pci
Makefile:20: /usr/src/linux-2.4.20-8//.config: No such file or directory
Makefile:38: WARNING: No kernel PCMCIA support found and PCMCIA_PATH is 
not defined
Makefile:45: WARNING: Linux wireless extensions, CONFIG_NET_RADIO, not 
enabled in the kernel
make: *** No rule to make target `/usr/src/linux-2.4.20-8//.config'.  
Stop.


Please tell me how to solve the abovce problems.

To get rid of error at line 38, shud i download and compile pcmcia-cs 
package?

why is the ".config" file not found in the kernel path OF rhl 9.0 ?
I've seen that file in the system running RHL 8.0.


-- 
--------------.				
With Regards,   
Anand S. Katti



From askatti  Wed Aug 13 04:26:11 2003
From: askatti (Anand S. Katti)
Date: Wed, 13 Aug 2003 16:56:11 +0530 (IST)
Subject: Hostap+avaya pci-card+SURECOM PCMCIA-CARD(EP-9427)+RHL 9.0 
In-Reply-To: <Pine.LNX.4.33.0308131253090.32120-100000@ece.iisc.ernet.in>
Message-ID: <Pine.LNX.4.33.0308131644350.6252-100000@ece.iisc.ernet.in>


Hello All,

I went thru some list and got hint, so i followed these steps...
since im using RHL 9.0

1. I copied the kernel---i686.config file from /config dir to 
/usr/src/linux-2.4.20-8/
2. Renamed the file to .config
3.cd /hostap-0.0.4
4.make pci
gcc -I/usr/src/linux-2.4.20-8//include -O2 -D__KERNEL__ -DMODULE -Wall -g 
-c  -DMODVERSIONS -i
nclude /usr/src/linux-2.4.20-8//include/linux/modversions.h 
-fomit-frame-pointer -E -D__GENKSY
MS__ driver/modules/hostap.c | \
        /sbin/genksyms -k 2.4.20 > driver/modules/hostap.ver
In file included from driver/modules/hostap.c:21:
/usr/src/linux-2.4.20-8/include/linux/module.h:15:1: warning: "_set_ver" 
redefined
In file included from 
/usr/src/linux-2.4.20-8/include/linux/modversions.h:4,
 
                 from <command line>:1:
/usr/src/linux-2.4.20-8/include/linux/modsetver.h:9:1: warning: this is 
the location of the pr
evious definition
gcc -I/usr/src/linux-2.4.20-8//include -O2 -D__KERNEL__ -DMODULE -Wall -g 
-c  -DMODVERSIONS -i
nclude /usr/src/linux-2.4.20-8//include/linux/modversions.h 
-fomit-frame-pointer -E -D__GENKSY
MS__ driver/modules/hostap_crypt.c | \
        /sbin/genksyms -k 2.4.20 > driver/modules/hostap_crypt.ver
In file included from driver/modules/hostap_crypt.c:18:
/usr/src/linux-2.4.20-8/include/linux/module.h:15:1: warning: "_set_ver" 
redefined
In file included from 
/usr/src/linux-2.4.20-8/include/linux/modversions.h:4,
                 from <command line>:1:
/usr/src/linux-2.4.20-8/include/linux/modsetver.h:9:1: warning: this is 
the location of the pr
evious definition
gcc -I/usr/src/linux-2.4.20-8//include -include 
driver/modules/hostap_crypt.ver -include drive
r/modules/hostap.ver -O2 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS 
-include /usr/src/li
nux-2.4.20-8//include/linux/modversions.h -fomit-frame-pointer -o 
driver/modules/hostap_pci.o
driver/modules/hostap_pci.c
gcc -I/usr/src/linux-2.4.20-8//include -include 
driver/modules/hostap_crypt.ver -include drive
r/modules/hostap.ver -O2 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS 
-include /usr/src/li
nux-2.4.20-8//include/linux/modversions.h -fomit-frame-pointer -o 
driver/modules/hostap.o driv
er/modules/hostap.c
gcc -I/usr/src/linux-2.4.20-8//include -include 
driver/modules/hostap_crypt.ver -include drive
/tmp/makepciop.txt
r/modules/hostap.ver -O2 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS 
-include /usr/src/li
nux-2.4.20-8//include/linux/modversions.h -fomit-frame-pointer -o 
driver/modules/hostap_crypt.
o driver/modules/hostap_crypt.c
gcc -I/usr/src/linux-2.4.20-8//include -include 
driver/modules/hostap_crypt.ver -include drive
r/modules/hostap.ver -O2 -D__KERNEL__ -DMODULE -Wall -g -c  -DMODVERSIONS 
-include /usr/src/li
nux-2.4.20-8//include/linux/modversions.h -fomit-frame-pointer -o 
driver/modules/hostap_crypt_
wep.o driver/modules/hostap_crypt_wep.c
  
Run 'make install_pccard' as root to install hostap_cs.o
Run 'make install_plx' as root to install hostap_plx.o
Run 'make install_pci' as root to install hostap_pci.o
==========================
make install_pci
=========================
4. [root at ROUTERH root]# make install_pci
make: *** No rule to make target `install_pci'.  Stop.
[root at ROUTERH root]# cd /tmp/hostap-0.0.4
[root at ROUTERH hostap-0.0.4]# make install_pci
Installing hostap_crypt*.o to /lib/modules/2.4.20-8/net
mkdir -p /lib/modules/2.4.20-8/net
cp -f driver/modules/hostap_crypt*.o /lib/modules/2.4.20-8/net
Installing hostap.o to /lib/modules/2.4.20-8/net
mkdir -p /lib/modules/2.4.20-8/net
[root at ROUTERH hostap-0.0.4]# modprobe hostap_pci
/lib/modules/2.4.20-8/net/hostap_pci.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, 
including invalid IO or IRQ parameters.
      You may find more information in syslog or the output from dmesg
:
/lib/modules/2.4.20-8/net/hostap_pci.o: insmod 
/lib/modules/2.4.20-8/net/hostap_pci.o failed
/lib/modules/2.4.20-8/net/hostap_pci.o: insmod hostap_pci failed
======================================================================
cp -f driver/modules/hostap.o /lib/modules/2.4.20-8/net
Installing hostap_pci.o to /lib/modules/2.4.20-8/net
mkdir -p /lib/modules/2.4.20-8/net
cp -f driver/modules/hostap_pci.o /lib/modules/2.4.20-8/net
/sbin/depmod -ae
[root at ROUTERH hostap-0.0.4]#
===========
                                                                                 
[root at ROUTERH linux-2.4]# insmod hostap_pci
Using /lib/modules/2.4.20-8/net/hostap_pci.o
/lib/modules/2.4.20-8/net/hostap_pci.o: unresolved symbol
hostap_80211_rx_Re43aa
b8d
/lib/modules/2.4.20-8/net/hostap_pci.o: unresolved symbol
hostap_80211_get_hdrle
n_R6903f16c
hostap_set_encryption_
R44417ac4
/lib/modules/2.4.20-8/net/hostap_pci.o: unresolved symbol
hostap_set_multicast_l
ist_queue_Rc089a779
/lib/modules/2.4.20-8/net/hostap_pci.o: unresolved symbol
hostap_set_antsel_R041
/lib/modules/2.4.20-8/net/hostap_pci.o: unresolved symbol
hostap_set_word_Rda4b0
====================
insmod hostap_pci
output of the dmesg
 
hostap_crypt: registered algorithm 'NULL'
hostap_pci: 0.0.4 - 2003-07-27 (Jouni Malinen <jkmaline at cc.hut.fi>)
hostap_pci: No devices found, driver not installed.
hostap_crypt: unregistered algorithm 'NULL' (deinit)
[root at ROUTERH net]#
==================================

Please guide me what step need i take now?


> This is my first mail to this mailing list. I believe you enjoy
> solving the problems. Here is my problem hope u help me out.
> 
> Im trying to install Hostap ver 0.0.4 on RHL 9.0 I have
> 
> 1.Avaya pci card
> 2.Surecom pcmcia card(I dont know how to find out the chipset for this 
> card? does anyone know how to figure out? Well when i insert this card in 
> to the RHL9.0 m/c and i do lsmod, it lists orinoco_cs module.
> 
> I untar the hostap.gz gile and went thru the README,
> Since im using "pcmcia card with pci card" I followed the installation 
> instructions given for "PCI CARDS BASED ON PRISM2.5  hostap_pci.o" section 
> from README file.
> 
> i edited the KERNEL_PATH to point to /usr/src/linux-2.4.20-8
> and typed "make pci"
> I got the following error.
> 
> [root at ROUTERH hostap-0.0.4]# make pci
> Makefile:20: /usr/src/linux-2.4.20-8//.config: No such file or directory
> Makefile:38: WARNING: No kernel PCMCIA support found and PCMCIA_PATH is 
> not defined
> Makefile:45: WARNING: Linux wireless extensions, CONFIG_NET_RADIO, not 
> enabled in the kernel
> make: *** No rule to make target `/usr/src/linux-2.4.20-8//.config'.  
> Stop.
> 
> 
> Please tell me how to solve the abovce problems.
> 
> To get rid of error at line 38, shud i download and compile pcmcia-cs 
> package?
> 
> why is the ".config" file not found in the kernel path OF rhl 9.0 ?
> I've seen that file in the system running RHL 8.0.
> 
> 
> 

-- 
--------------.				
With Regards,   
Anand S. Katti



From jsun  Wed Aug 13 07:02:25 2003
From: jsun (Jun Sun)
Date: Wed, 13 Aug 2003 07:02:25 -0700
Subject: How to force client to associate another AP
In-Reply-To: <3F39E0F3.1020706@tut.fi>
References: <00ed01c3615b$11f34660$e6f0c53f@williamt>
	<3F39E0F3.1020706@tut.fi>
Message-ID: <20030813140225.GC8847@gateway.junsun.net>

On Wed, Aug 13, 2003 at 09:55:47AM +0300, Timo Vanhatupa wrote:
> Hi
> 
> I have done it using access control list and it seems to work.
> First I set deny policy for access control list and then deny client's 
> access and kick it out.
> 
> iwpriv wlan0 maccmd 2
> iwpriv wlan0 addmac <mac addr>
> iwpriv wlan0 kickmac <mac addr>
>

Very interesting approach.
 
> At least my clients seem to find their way to other APs. I would like to 
> know if this does not work
> with all clients.
> 
> Still I haven't figured out how to know which access points can be heard 
> by the client.
> Does anyone have ideas how an AP could scan/listen clients that are not 
> associated with it and are on the different channel?
> If this information would be available it would be easy to force clients 
> to selected APs.
>

My understanding is that people are working on this as part of
inter-AP protocol.

Jun



From OIzhvanov  Wed Aug 13 03:35:46 2003
From: OIzhvanov (Oleg Izhvanov)
Date: Wed, 13 Aug 2003 14:35:46 +0400
Subject: WInXP +SP1 Hostap and 802.1x authentications
In-Reply-To: <20030813012106.GA3898@jm.kir.nu>
References: <3F39390B.9090207@mbigroup.it> <20030813012106.GA3898@jm.kir.nu>
Message-ID: <3F3A1482.7010101@rfmd.com>

Jouni Malinen wrote:

> You seem to have disabled all authentication algorithms. In practice,
> this means that no one is able to use your AP.. I should probably just
> change hostapd to reject that kind of configuration. Anyway, auth_algs
> is a bit field and it should be set to 1 (i.e., bit0 set) to allow Open
> System Authentication when using IEEE 802.1X. Other possible values are
> 2 (only Shared Key Auth) and 3 (both Open System and Shared Key
> accepted), but these should not be used with IEEE 802.1X.

But why ? It is not prohibited using shared key authentication with
802.1X enabled. It doesn't make much sense, though. For example, you
may use default key with index 0 for shared authentication and other key
indexes for key update via EAPOL-Key frames.

-- 
Best Regards, Oleg Izhvanov <oizhvanov at rfmd.com>



From OIzhvanov  Wed Aug 13 03:43:22 2003
From: OIzhvanov (Oleg Izhvanov)
Date: Wed, 13 Aug 2003 14:43:22 +0400
Subject: Query about WEP and dynamic keys
In-Reply-To: <3F39E5B1.7010804@eecs.umich.edu>
References: <3F39E5B1.7010804@eecs.umich.edu>
Message-ID: <3F3A164A.3010006@rfmd.com>

Greets,

This is quite common problem -- you should think about 802.1X and RADIUS
as the temporary solution and WPA as the final. The idea is that you
have certificate-based authentication system, and WEP keys are generated
on a per-session basis and ditributed via special EAPOL-Key messages, so
it is not a problem if the key for particular session becomes compromised.

You may read about 802.1X and RADIUS on:

    http://www.open1x.org/links

Madhusudan Singh wrote:
> Hi
>     Thanks to all the help, I managed to set up my access point and get 
> my DHCP server to issue leases, etc.
> 
>     I am using wep with a fixed key in the restricted mode, and was 
> thinking if a better mechanism could be devised, say, something similar 
> to the Kerberos ticket mechanism / ssh. I somehow do not like the idea 
> of storing the key (even if the server be behind a hardened firewall) in 
> short plain text form, which could compromise the security if the fixed 
> key became accidently known.
> 
>     Also, if I have a large pool of users (say 6-8), this key would have 
> to be given to all of them, increasing the risk of disclosure. I have 
> MAC address matching in place, but I want to make it more secure in the 
> fashion of ssh as mentioned earlier, including an RSA passphrase 
> mechanism for each client that logs on.
> 
>     Forgive me if all this sounds rather vague. I am not exactly savvy 
> with WEP.
> 
> Thanks,
> 
> MS
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

-- 
Best Regards, Oleg Izhvanov <oizhvanov at rfmd.com>



From robert  Tue Aug 12 21:20:17 2003
From: robert (Robert Kohler)
Date: Tue, 12 Aug 2003 23:20:17 -0500
Subject: DWL-650 rev K on RH9 
Message-ID: <3F39BC81.9090404@rkohler.com>

Does your hostAP code work for the PCMCIA card 11Mb, DWL-650 rev K?

I found ref to DWL-650 working, but after installing, I found ref
to /etc/pcmcia/hostap.conf using rev D.

For my tests, I have been unable to get it to recognize a driver.
Here is what I have sone so far.

RH9 full install.
Recompiled kernel 2.4.20-19.9 without PCMCIA support.
Installed pcmcia-cs-3.2.4 .
	Updated /etc/sysconfig/pcmcia
...
PCMCIA=yes
PCIC=i82365
PCIC_OPTS=
CORE_OPTS=
...

Installed hostap-0.0.4
	Ran "make pccard"

Copied /etc/pcmcia/hostap.conf to /etc/pcmcia/config
as it appears this is what cardmgr reads.

Restarted pcmcia services via /etc/init.d/pcmcia restart.

Messages I get in /var/log/messages when inserting card

Aug 12 22:49:13 roblap kernel:   O2Micro OZ6912 rev 00 PCI-to-CardBus at 
slot 00:0a, mem 0xd0003000
Aug 12 22:49:13 roblap kernel:     host opts [0]: [pci/way] [pci irq 11] 
[lat 64/176] [bus 3/3]
Aug 12 22:49:13 roblap kernel:     PCI irq 11 test failed
Aug 12 22:49:13 roblap kernel:     ISA irqs (default) = 3,4,7,9 polling 
interval = 1000 ms
Aug 12 22:49:13 roblap cardmgr[3773]: watching 1 sockets
Aug 12 22:49:13 roblap cardmgr[3774]: starting, version is 3.2.4
Aug 12 22:49:14 roblap kernel: cs: cb_alloc(bus 3): vendor 0x104c, 
device 0x8400Aug 12 22:49:14 roblap kernel: cs: could not allocate 4K 
memory for CardBus socket 0
Aug 12 22:49:14 roblap cardmgr[3774]: unsupported card in socket 0
Aug 12 22:49:14 roblap cardmgr[3774]:   no product info available
Aug 12 22:49:14 roblap cardmgr[3774]:   PCI id: 0x104c, 0x8400

Does this mean my card uses diff drivers.??

I noticed on D-Link's web site, they have drivers for WinXP and stress 
to NOT install the wrong DWL-650 driver rev. "D" vs. "K".  They say this
does not work and may possibly damage card inoperatable...

Anyone know what kind of chipset this card has?

TIA

Robert






From williamt  Wed Aug 13 10:54:24 2003
From: williamt (William Tai)
Date: Wed, 13 Aug 2003 10:54:24 -0700
Subject: How to force client to associate another AP
References: <00ed01c3615b$11f34660$e6f0c53f@williamt>
	<3F39E0F3.1020706@tut.fi> <20030813140225.GC8847@gateway.junsun.net>
Message-ID: <012a01c361c3$eea343e0$e6f0c53f@williamt>


----- Original Message ----- 
From: "Jun Sun" <jsun at junsun.net>
To: "Timo Vanhatupa" <timo.vanhatupa at tut.fi>
Cc: "william" <williamt at arescom.com>; <hostap at shmoo.com>
Sent: Wednesday, August 13, 2003 7:02 AM
Subject: Re: How to force client to associate another AP


> On Wed, Aug 13, 2003 at 09:55:47AM +0300, Timo Vanhatupa wrote:
> > Hi
> >
> > I have done it using access control list and it seems to work.
> > First I set deny policy for access control list and then deny client's
> > access and kick it out.
> >
> > iwpriv wlan0 maccmd 2
> > iwpriv wlan0 addmac <mac addr>
> > iwpriv wlan0 kickmac <mac addr>
> >
>
> Very interesting approach.


>
> > At least my clients seem to find their way to other APs. I would like to
> > know if this does not work
> > with all clients.
> >

I did this, but the client still tried to associated with my AP.
I guess the client will try to associate with the AP with highest singal
quality. Am I right?
The client still try to associate with my AP even though I already kick it
ouy.



> > Still I haven't figured out how to know which access points can be heard
> > by the client.
> > Does anyone have ideas how an AP could scan/listen clients that are not
> > associated with it and are on the different channel?
> > If this information would be available it would be easy to force clients
> > to selected APs.
> >
>
> My understanding is that people are working on this as part of
> inter-AP protocol.
>
> Jun
>



From lsantos  Wed Aug 13 12:28:09 2003
From: lsantos (Leonardo Pereira Santos)
Date: Wed, 13 Aug 2003 16:28:09 -0300
Subject: hostapd simple configuration
Message-ID: <200308131628.11673.lsantos@pd3.com.br>

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

Hi All!
	Sorry for the simple question, but I'm having some trouble setting up hostapd 
and xsupplicant, if anyoune could give me some pointers, I'd be very 
grateful.
	First, I've read the following pages:
Adam Sulmicki: HOWTO on EAP/TLS authentication between FreeRADIUS and 
XSupplicant http://www.missl.cs.umd.edu/wireless/eaptls/

Adam Sulmicki: HOWTO on EAP/TLS authentication between FreeRADIUS and 
XSupplicant with HostAP
http://www.missl.cs.umd.edu/Projects/wireless/hostap.html
And obviously the HostAP README file.

The message I get when starting hostapd is:

#hostapd -d /etc/hostapd.conf
Configuration file: /etc/hostapd.conf
Opening raw packet socket for ifindex 4
Using interface wlan0ap with hwaddr 00:02:dd:32:5b:46 and ssid 'test'
Flushing old station entries
Deauthenticate all stations
DATA
Data frame from not associated STA 00:02:78:e1:b0:49
mgmt::auth
authentication: STA=00:02:78:e1:b0:49 auth_alg=0 auth_transaction=1 
status_code=0 wep=0
  New STA
authentication reply: STA=00:02:78:e1:b0:49 auth_alg=0 auth_transaction=2 
resp=0
MGMT (TX callback) fail
mgmt::auth cb
wlan0: STA 00:02:78:e1:b0:49 IEEE 802.11: did not acknowledge authentication 
response
mgmt::auth
authentication: STA=00:02:78:e1:b0:49 auth_alg=0 auth_transaction=1 
status_code=0 wep=0
authentication reply: STA=00:02:78:e1:b0:49 auth_alg=0 auth_transaction=2 
resp=0
MGMT (TX callback) fail
mgmt::auth cb
wlan0: STA 00:02:78:e1:b0:49 IEEE 802.11: did not acknowledge authentication 
response

And so on...

While at the station, I get:

#xsupplicant -i wlan0
Setup on device wlan0 complete
set globals.
Done with init.
Sending EAPOL-Start #1
Sending EAPOL-Start #2
No authenticator found! Assuming the port is authorized!

The only diffs between the standard hostapd.conf and the one I'm using are:
- -debug=0
+debug=1

- -daemonize=1
+daemonize=0

- -#ieee8021x=1
+ieee8021x=1

- -minimal_eap=0
+minimal_eap=1


And the XSupplicant's conf file is simply:

test:id   = adam-ctl
test:auth = EAP


Thanks in advance!
- -- 
This is Linux country.
On a quiet night, you can hear Windows reboot.

Leonardo Pereira Santos
Engenheiro de Projetos
PD3 Tecnologia
av. Par? 330/202
(51) 3337 1237

Today Fortune tells us:
If it's Tuesday, this must be someone else's fortune.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/OpFK8uAMCTjfaxIRAjeAAKC3B8btk4k4fO4/kmJ1V5azYwzWUgCeIn8+
m/jEcsD6Lp9fdC/NtkbtROc=
=G7co
-----END PGP SIGNATURE-----



From dilip  Wed Aug 13 12:45:05 2003
From: dilip (Dilip Sundarraj)
Date: Wed, 13 Aug 2003 12:45:05 -0700 (PDT)
Subject: Suitable WLAN card for modifying Tx power 
Message-ID: <Pine.GSO.4.56.0308131239200.422@sirius.cs.pdx.edu>

Hi,

I'm working on a project where we require to reduce the Tx power well
below 0dBm for our experiments. I'd like to know which card would support this
feature when using the hostap driver.

Thanks,
Dilip



From jkmaline  Wed Aug 13 17:49:55 2003
From: jkmaline (Jouni Malinen)
Date: Wed, 13 Aug 2003 17:49:55 -0700
Subject: hostapd simple configuration
In-Reply-To: <200308131628.11673.lsantos@pd3.com.br>
References: <200308131628.11673.lsantos@pd3.com.br>
Message-ID: <20030814004955.GD3961@jm.kir.nu>

On Wed, Aug 13, 2003 at 04:28:09PM -0300, Leonardo Pereira Santos wrote:

> #hostapd -d /etc/hostapd.conf

Which version of hostapd (and driver) are you using?

> authentication reply: STA=00:02:78:e1:b0:49 auth_alg=0 auth_transaction=2 
> resp=0
> MGMT (TX callback) fail
> mgmt::auth cb
> wlan0: STA 00:02:78:e1:b0:49 IEEE 802.11: did not acknowledge authentication 
> response

For some reason, the client did not send IEEE 802.11 ACK frame for the
authentication frame that the AP sent. Usually this happens when too
much time is used between the authentication frames. Wi-Fi certification
requires that stations wait at least 100 ms for this, but I do not know
what timeout values are really used. Are you sending that debug output
through serial console? Did you test the same thing with debugging
disabled? Which Prism2 card are you using? How fast is the host system?

> While at the station, I get:
> 
> #xsupplicant -i wlan0
> Setup on device wlan0 complete
> set globals.
> Done with init.
> Sending EAPOL-Start #1
> Sending EAPOL-Start #2
> No authenticator found! Assuming the port is authorized!

Not much use in testing xsupplicant yet since even the IEEE 802.11
authentication failed.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Aug 13 17:49:45 2003
From: jkmaline (Jouni Malinen)
Date: Wed, 13 Aug 2003 17:49:45 -0700
Subject: How to force client to associate another AP
In-Reply-To: <012a01c361c3$eea343e0$e6f0c53f@williamt>
References: <00ed01c3615b$11f34660$e6f0c53f@williamt>
	<3F39E0F3.1020706@tut.fi> <20030813140225.GC8847@gateway.junsun.net>
	<012a01c361c3$eea343e0$e6f0c53f@williamt>
Message-ID: <20030814004945.GC3961@jm.kir.nu>

On Wed, Aug 13, 2003 at 10:54:24AM -0700, William Tai wrote:

> I did this, but the client still tried to associated with my AP.
> I guess the client will try to associate with the AP with highest singal
> quality. Am I right?
> The client still try to associate with my AP even though I already kick it
> ouy.

This depends on the client implementation. Some implementations may try
to always use the AP with highest signal quality while others will try
to change to another AP when they are disassociated or at least after
new associations fail number of times. Which client (model & version
numbers) were you using when testing this?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Aug 13 17:49:58 2003
From: jkmaline (Jouni Malinen)
Date: Wed, 13 Aug 2003 17:49:58 -0700
Subject: Hostap+avaya pci-card+SURECOM PCMCIA-CARD(EP-9427)+RHL 9.0
In-Reply-To: <Pine.LNX.4.33.0308131253090.32120-100000@ece.iisc.ernet.in>
References: <20030813012921.9E89324592@mail.iocaine.com>
	<Pine.LNX.4.33.0308131253090.32120-100000@ece.iisc.ernet.in>
Message-ID: <20030814004958.GE3961@jm.kir.nu>

On Wed, Aug 13, 2003 at 01:07:13PM +0530, Anand S. Katti wrote:

> 1.Avaya pci card
> 2.Surecom pcmcia card(I dont know how to find out the chipset for this 
> card? does anyone know how to figure out? Well when i insert this card in 
> to the RHL9.0 m/c and i do lsmod, it lists orinoco_cs module.
> 
> I untar the hostap.gz gile and went thru the README,
> Since im using "pcmcia card with pci card" I followed the installation 
> instructions given for "PCI CARDS BASED ON PRISM2.5  hostap_pci.o" section 
> from README file.

I'm not familiar with that Avaya PCI card, but it certainly not a PCI
card based on Prism2.5 and you cannot use hostap_pci with it. Based on
you mentioning orinoco_cs, it looks like Avaya card is a PC Card to PCI
adapter and you should use hostap_cs with pcmcia-cs.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jhiller  Wed Aug 13 21:45:06 2003
From: jhiller (James B. Hiller)
Date: Thu, 14 Aug 2003 00:45:06 -0400 (EDT)
Subject: Are there other sources of unresolved symbols?
Message-ID: <200308140445.h7E4j6AC001575@bassett.home.org>

Hi.

I got the CVS snapshot from the CVS site about 2 hours ago (like
11 pm Wed night) and compiled against my self-compiled kernel,
linux-2.4.21.  I have the source tree path set correctly in
the Makefile, and still get unresolved symbols.  In addition,
I completely cleaned out the /lib modules path, and cleaned out
the linux source tree (make clean) and did a fresh compilation of
everything, and I still get some in hostap_crypt_wep.

I'm no kernel wizard, and modules are something I usually avoid,
but haven't had any trouble with the release versions (0.0.3 and
0.0.4) of hostap.

Can anyone tell me what else I might do to get rid of these, or
should I not care?  When the kernel boots and I invoke iwconfig
in an init script, I get them.  When I insert them manually
with insmod (which is all I'm doing in the init script), I don't
get them.

thx,
jbh



From mike  Wed Aug 13 22:00:39 2003
From: mike (Michael Shuler)
Date: Thu, 14 Aug 2003 00:00:39 -0500
Subject: Distance Problems
Message-ID: <003301c36221$018fa5e0$4fe3dd0c@minime>

We are having a problem with ~20 mile PTP link using hostap as in AP
"master" mode on one side and Client "managed" mode on the other.  The AP
will show the association with good signal and noise levels but the client
will not associate.  We also tried using a WinXP laptop hooked up to the
same PCMCIA card (Zcomax/SMC) and antenna combination with no luck...we are
however able to associate to an Orinoco AP that is 10 ft. away from the
hostap AP system (on a different frequency of course) so we know the link is
physically possible.  We drove 10 miles close and tried the same config
standing on the ground instead of on the grain elevators (150' each) and it
worked great.  This would lead me to believe that there is some sort of
timing issue in the hostap driver that needs to be increased to support long
distance links.  I noticed that the AP appears to be receiving packets but
not transmitting any.  Any help would be appreciated.

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

Michael Shuler



From jkmaline  Wed Aug 13 22:13:38 2003
From: jkmaline (Jouni Malinen)
Date: Wed, 13 Aug 2003 22:13:38 -0700
Subject: Are there other sources of unresolved symbols?
In-Reply-To: <200308140445.h7E4j6AC001575@bassett.home.org>
References: <200308140445.h7E4j6AC001575@bassett.home.org>
Message-ID: <20030814051338.GA7469@jm.kir.nu>

On Thu, Aug 14, 2003 at 12:45:06AM -0400, James B. Hiller wrote:

> I got the CVS snapshot from the CVS site about 2 hours ago (like
> 11 pm Wed night) and compiled against my self-compiled kernel,
> linux-2.4.21.  I have the source tree path set correctly in
> the Makefile, and still get unresolved symbols.  In addition,
> I completely cleaned out the /lib modules path, and cleaned out
> the linux source tree (make clean) and did a fresh compilation of
> everything, and I still get some in hostap_crypt_wep.

How did you compile and install the Host AP driver (exact list of
commands)? Did that report any warnings or errors?

> Can anyone tell me what else I might do to get rid of these, or
> should I not care?  When the kernel boots and I invoke iwconfig
> in an init script, I get them.  When I insert them manually
> with insmod (which is all I'm doing in the init script), I don't
> get them.

Which symbols are reported as unresolved? What is the exact command you
used when you got the error? Which hw model (pci/cs/plx) are you using?
If cs, you should not be loading the modules yourself. If pci/plx you
should be using modprobe to load the module so that all the dependencies
(hostap.o) gets loaded properly. hostap_crypt_wep.o is loaded only when
needed; or to be more exact, Host AP driver asks it to be loaded if your
kernel module loader is working correctly.

-- 
Jouni Malinen                                            PGP id EFC895FA



From xfesty  Wed Aug 13 22:16:34 2003
From: xfesty (Ryan Verner)
Date: Thu, 14 Aug 2003 14:46:34 +0930
Subject: Distance Problems
In-Reply-To: <003301c36221$018fa5e0$4fe3dd0c@minime>
References: <003301c36221$018fa5e0$4fe3dd0c@minime>
Message-ID: <20030814051634.M62294@computeraddictions.com.au>

> We are having a problem with ~20 mile PTP link using hostap as in AP
> "master" mode on one side and Client "managed" mode on the other.  
> The AP will show the with good signal and noise levels 
> but the client will not associate.

I'm not sure what the problem is either, but I've had nothing but problems
trying 0.0.3 and 0.0.4 with long distance outdoor connections. not associating
was definitely one of the higher ones.

Try a shapshot; I'm using July 2002 for outdoor connections at the moment.

R

--
Open WebMail Project (http://openwebmail.org)



From askatti  Thu Aug 14 00:23:05 2003
From: askatti (Anand S. Katti)
Date: Thu, 14 Aug 2003 12:53:05 +0530 (IST)
Subject: Hostap+avaya pci-card+SURECOM PCMCIA-CARD(EP-9427)+RHL 9.0
In-Reply-To: <20030814005237.5BECD24561@mail.iocaine.com>
Message-ID: <Pine.LNX.4.33.0308141213400.1826-100000@ece.iisc.ernet.in>


Yes you are right, i took it like this
Avaya card( used to convert pci to pcmcia slot. so that i can put pcmcia 
card in to the pci slot through avaya card. Its a pci card bus manager.)
This led me to think that im using pci card, and i hesitated to use 
pccard.

Then i tried --
make pccard
make install_pccard
modprobe hostap_cs

iwconfig listed the wirless card, the o/p of the iwconfig is

Output from the lsmod
-------------------------
hostap_cs              41192   0  (unused)
hostap                 87524   0  [hostap_cs]
hostap_crypt            2768   0  [hostap]
ide-cd                 35708   0  (autoclean)
parport_pc             19076   1  (autoclean)
parport                37056   1  (autoclean) [parport_pc lp]
orinoco_cs              5864   1
orinoco                36024   0  [orinoco_cs]
hermes                  8196   0  [orinoco_cs orinoco]
ds                      8680   1  [hostap_cs orinoco_cs]
yenta_socket           13472   1
pcmcia_core            57216   0  [hostap_cs orinoco_cs ds yenta_socket]
8139too                18088   0

Output from the iwconfig
------------------------
eth2      IEEE 802.11-DS  ESSID:"default"  Nickname:"Prism  I"
          Mode:Managed  Frequency:2.437GHz  Access Point: 
00:40:05:C1:1C:F6
          Bit Rate:5.5Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0/92  Signal level:140/153  Noise level:107/153
          Rx invalid nwid:0  Rx invalid crypt:21  Rx invalid frag:0
          Tx excessive retries:440  Invalid misc:0   Missed beacon:0
Output from the dmesg
----------------------
eth2: Error -110 writing Tx descriptor to BAP
eth2: Error -110 writing Tx descriptor to BAP
eth2: Error -110 writing Tx descriptor to BAP
eth2: error -110 reading frame header. Frame dropped.
eth2: Error -110 writing Tx descriptor to BAP
eth2: Error -110 writing Tx descriptor to BAP
===========================================================

My test bed setup
1)
 A(hostap_cs)-------B
'A' is running above configuration with hostap.
It has only one interface that too eth2(pcmcia wirless card with hostap)
The ip is .55

 "B" is also having one wireless interface eth2 with ip .51
What shud be the default gw in the routing table of B?

The pings are showing 99% Packet loss
=======================================================================

                                                                                                                             
> 1.Avaya pci card
> 2.Surecom pcmcia card(I dont know how to find out the chipset for this
> card? does anyone know how to figure out? Well when i insert this card 
in
> to the RHL9.0 m/c and i do lsmod, it lists orinoco_cs module.
>
> I untar the hostap.gz gile and went thru the README,
> Since im using "pcmcia card with pci card" I followed the installation
> instructions given for "PCI CARDS BASED ON PRISM2.5  hostap_pci.o" 
section
> from README file.
                                                                                                                             
I'm not familiar with that Avaya PCI card, but it certainly not a PCI
card based on Prism2.5 and you cannot use hostap_pci with it. Based on
you mentioning orinoco_cs, it looks like Avaya card is a PC Card to PCI
adapter and you should use hostap_cs with pcmcia-cs.
                                                                                                                             
--
Jouni Malinen                                            PGP id EFC895FA
                                                                                                                             
------------------------------


-- 
--------------.				
With Regards,   
Anand S. Katti



From jphstap  Thu Aug 14 09:04:16 2003
From: jphstap (Joe Parks)
Date: 14 Aug 2003 12:04:16 -0400
Subject: Distance Problems
In-Reply-To: <003301c36221$018fa5e0$4fe3dd0c@minime>
References: <003301c36221$018fa5e0$4fe3dd0c@minime>
Message-ID: <1060877055.2543.92.camel@scrodconumulus>

On Thu, 2003-08-14 at 01:00, Michael Shuler wrote:
> We are having a problem with ~20 mile PTP link using hostap as in AP
> "master" mode on one side and Client "managed" mode on the other.  The AP
> will show the association with good signal and noise levels but the client
> will not associate.  We also tried using a WinXP laptop hooked up to the
> same PCMCIA card (Zcomax/SMC) and antenna combination with no luck...we are
> however able to associate to an Orinoco AP that is 10 ft. away from the
> hostap AP system (on a different frequency of course) so we know the link is
> physically possible.  We drove 10 miles close and tried the same config
> standing on the ground instead of on the grain elevators (150' each) and it
> worked great.  This would lead me to believe that there is some sort of
> timing issue in the hostap driver that needs to be increased to support long
> distance links.  I noticed that the AP appears to be receiving packets but
> not transmitting any.  Any help would be appreciated.

I seem to recall someone mentioning a while back (check the archives)
that the Prism chipset has a very tight timing that prevents links over
15 miles.   If there is a way to override this I haven't heard about it.



From jbreeden  Thu Aug 14 10:40:46 2003
From: jbreeden (John Breeden)
Date: Thu, 14 Aug 2003 07:40:46 -1000
Subject: Distance Problems
In-Reply-To: <1060877055.2543.92.camel@scrodconumulus>
Message-ID: <JGEMLPOAIENLAMPIADCLEEOHCCAA.jbreeden@plumhall.com>

It's not the Prism chipset, it's the 802.11b protocol itself. Transmissions
are ACK'd by the receiver. ROUND TRIP distances greater than 20-30 miles
will exceed the transmitter's timer.

The usual symtom is really low throughput due to retransmissions, though I
wouldn't rule out NO throughput given the distance :-)

The timer is locked in the Prism's firmware and as far as I know Jouni has
never adressesed this "feature" :-)

An interim "solution" is StarOs http://www.star-os.com/. It'll let you set
the timer's timeout - what StarOs calls "long distance links". I am not
associated with StarOs in any way, other than needing to "cure" the same
"problem".

StarOs IS NOT open source, though it's based on BSD, and BSD's license. It's
cheep - $30 and runs on Intel and Sokeris.

--
John Breeden
Kamuela, Hawaii
www.plumhall.com

> -----Original Message-----
> From: hostap-bounces at shmoo.com [mailto:hostap-bounces at shmoo.com]On
> Behalf Of Joe Parks
> Sent: Thursday, August 14, 2003 6:04 AM
> To: Michael Shuler
> Cc: hostap at shmoo.com
> Subject: Re: Distance Problems
>
>
> On Thu, 2003-08-14 at 01:00, Michael Shuler wrote:
> > We are having a problem with ~20 mile PTP link using hostap as in AP
> > "master" mode on one side and Client "managed" mode on the
> other.  The AP
> > will show the association with good signal and noise levels but
> the client
> > will not associate.  We also tried using a WinXP laptop hooked up to the
> > same PCMCIA card (Zcomax/SMC) and antenna combination with no
> luck...we are
> > however able to associate to an Orinoco AP that is 10 ft. away from the
> > hostap AP system (on a different frequency of course) so we
> know the link is
> > physically possible.  We drove 10 miles close and tried the same config
> > standing on the ground instead of on the grain elevators (150'
> each) and it
> > worked great.  This would lead me to believe that there is some sort of
> > timing issue in the hostap driver that needs to be increased to
> support long
> > distance links.  I noticed that the AP appears to be receiving
> packets but
> > not transmitting any.  Any help would be appreciated.
>
> I seem to recall someone mentioning a while back (check the archives)
> that the Prism chipset has a very tight timing that prevents links over
> 15 miles.   If there is a way to override this I haven't heard about it.
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From jhiller  Thu Aug 14 17:24:18 2003
From: jhiller (James B. Hiller)
Date: Thu, 14 Aug 2003 20:24:18 -0400 (EDT)
Subject: Are there other sources of unresolved symbols?
In-Reply-To: <20030814051338.GA7469@jm.kir.nu> from "Jouni Malinen" at Aug 13,
	2003 10:13:38 PM
Message-ID: <200308150024.h7F0OI22000698@bassett.home.org>

> > I got the CVS snapshot from the CVS site about 2 hours ago (like
> > 11 pm Wed night) and compiled against my self-compiled kernel,
> > linux-2.4.21.  I have the source tree path set correctly in
> > the Makefile, and still get unresolved symbols.  In addition,
> > I completely cleaned out the /lib modules path, and cleaned out
> > the linux source tree (make clean) and did a fresh compilation of
> > everything, and I still get some in hostap_crypt_wep.
> 
> How did you compile and install the Host AP driver (exact list of
> commands)? Did that report any warnings or errors?

Sorry for not having given more precise info.  Was away from
the compilation machine when sent the email.

a.  Compilation and installation of hostap;
b.  Did that report any warnings or errors?

Untar hostap.tar.gz in /usr/local/packages/incoming.

Change KERNEL_PATH in top Makefile from /usr/src/linux to
  /usr/src/linux-2.4.21.

Issue make pci

Makefile:38:  WARNING:  No kernel PCMCIA support found and PCMCIA path
  is not defined
..
In file included from driver/modules/hostap.c:21:
/usr/src/linux-2.4.21/include/linux/module.h:15: warning: `_set_ver' redefined
/usr/src/linux-2.4.21/include/linux/modsetver.h:9: warning: this is the location of the previous definition
..

then

make install_pci

which yields only one warning, the one from Makefile:38 above.  The
depmod in the Makefile echoes and completes fine.

c.  Which symbols are reported as unresolved?
d.  What is the exact command you used when you got the error?

In the shell script (/etc/rc.d/rc.local):

/sbin/insmod /lib/modules/2.4.21/net/hostap_crypt_wep.o

produces

/lib/modules/2.4.21/net/hostap_crypt_wep.o:  unresolved symbol hostap_register_crypto_ops_Rsmp_a6d832d1
/lib/modules/2.4.21/net/hostap_crypt_wep.o:  unresolved symbol hostap_unregister_crypto_ops_Rsmp_723f9bd0

f.  Which hardware model?

pci

Note that I was not using modprobe to load these, but rather insmod
(remember, no expert at kernel modules).  Also note that my rc.local
script does in fact include two subsequent insmods for the other two
hostap modules produced, but these do not generate any errors (granted,
however, that I should be doing

modprobe /lib/modules/2.4.21/net/hostap

in the rc.local script, if I undertand you correctly; and I will now
make that change).

thx,
jbh



From jkmaline  Thu Aug 14 19:22:28 2003
From: jkmaline (Jouni Malinen)
Date: Thu, 14 Aug 2003 19:22:28 -0700
Subject: Are there other sources of unresolved symbols?
In-Reply-To: <200308150024.h7F0OI22000698@bassett.home.org>
References: <20030814051338.GA7469@jm.kir.nu>
	<200308150024.h7F0OI22000698@bassett.home.org>
Message-ID: <20030815022228.GC3491@jm.kir.nu>

On Thu, Aug 14, 2003 at 08:24:18PM -0400, James B. Hiller wrote:

> /sbin/insmod /lib/modules/2.4.21/net/hostap_crypt_wep.o
> 
> produces
> 
> /lib/modules/2.4.21/net/hostap_crypt_wep.o:  unresolved symbol hostap_register_crypto_ops_Rsmp_a6d832d1

hostap_crypt_wep.o uses functions that are defined in hostap.o and it
cannot thus be loaded before hostap.o.

> Note that I was not using modprobe to load these, but rather insmod
> (remember, no expert at kernel modules).  Also note that my rc.local
> script does in fact include two subsequent insmods for the other two
> hostap modules produced, but these do not generate any errors (granted,
> however, that I should be doing
> 
> modprobe /lib/modules/2.4.21/net/hostap

Assuming your module dependencies are configured properly, it should be
enough to run:

modprobe hostap_pci

and if you need to manually load WEP algorithm, you can also run

modprobe hostap_crypt_wep

If you want to use insmod, you will need to first load hostap.o and then
hostap_pci.o or hostap_crypt_wep.o (order of these two last ones does
not matter). In addition, Host AP driver requests hostap_crypt_wep.o
module automatically, so you should not even need to load it manually.
You can also setup /etc/modules.conf to automatically load hostap_pci
when you try to use wlan0 interface.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Thu Aug 14 19:26:05 2003
From: jkmaline (Jouni Malinen)
Date: Thu, 14 Aug 2003 19:26:05 -0700
Subject: Hostap+avaya pci-card+SURECOM PCMCIA-CARD(EP-9427)+RHL 9.0
In-Reply-To: <Pine.LNX.4.33.0308141213400.1826-100000@ece.iisc.ernet.in>
References: <20030814005237.5BECD24561@mail.iocaine.com>
	<Pine.LNX.4.33.0308141213400.1826-100000@ece.iisc.ernet.in>
Message-ID: <20030815022605.GD3491@jm.kir.nu>

On Thu, Aug 14, 2003 at 12:53:05PM +0530, Anand S. Katti wrote:

> modprobe hostap_cs

You should not load PC Card modules manually. Let cardmgr take care of
that.

> Output from the lsmod
> -------------------------
> hostap_cs              41192   0  (unused)
> orinoco_cs              5864   1

You are not using Host AP driver, but orinoco_cs.

> Output from the iwconfig
> ------------------------
> eth2      IEEE 802.11-DS  ESSID:"default"  Nickname:"Prism  I"

> Output from the dmesg
> ----------------------
> eth2: Error -110 writing Tx descriptor to BAP

These are from orinoco driver..

> My test bed setup
> 1)
>  A(hostap_cs)-------B
> 'A' is running above configuration with hostap.
> It has only one interface that too eth2(pcmcia wirless card with hostap)

No, it is not running Host AP.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jhiller  Thu Aug 14 22:05:04 2003
From: jhiller (James B. Hiller)
Date: Fri, 15 Aug 2003 01:05:04 -0400 (EDT)
Subject: Understanding what files are what in a flash archive
Message-ID: <200308150505.h7F554B1002342@bassett.home.org>

Maybe this question isn't quite so ludicrous as my last.

As I prepare to flash my DLink DWL-520 to get beyond reported buggy
firmware, I have copied several firmware zip versions.  How does
one determine the differences and applicability among the several
types of files that seem to be included?

For example, 1.1.0 has a file with a pk prefix, and a number that
doesn't quite match the "version" number; as well as an sf number,
and a number that does resemble the version number.

>From this, all I can guess so far is the the sf file is the
"station firmware" of version 1.1.0, but no clue what that pk file
is, and no clue whether these files are suitable for volatile or
non-volatile application (or both?).

Then I look in the 1.7.4 archive, and I see that there are
7 files of all kinds of prefices, include the sf as one of them.
What are these various files for?

Is there a secret decoder ring out there for the file naming?  I've
gone through a little over 50% of the hostap archive, and so far
I remain clueless on this.

Thanks!

jbh



From eduardo  Thu Aug 14 22:41:10 2003
From: eduardo (Eduardo Kaftanski)
Date: Fri, 15 Aug 2003 01:41:10 -0400
Subject: Understanding what files are what in a flash archive
In-Reply-To: <200308150505.h7F554B1002342@bassett.home.org>
References: <200308150505.h7F554B1002342@bassett.home.org>
Message-ID: <20030815054110.GA3018@enriqueto.nn.cl>

> 
> Then I look in the 1.7.4 archive, and I see that there are
> 7 files of all kinds of prefices, include the sf as one of them.
> What are these various files for?
> 
> Is there a secret decoder ring out there for the file naming?  I've
> gone through a little over 50% of the hostap archive, and so far
> I remain clueless on this.
> 

This is what I did:

  prism2_srec wlan0 pk010101.hex sf010704.hex

to test. it said OK.

  prism2_srec -f wlan0 pk010101.hex sf010704.hex

to flash.



-- 
Eduardo Kaftanski
eduardo at linuxcenter.cl
Red Hat Certified Engineer
Gerente Ingenieria LinuxCenter S.A.
Canada 239 5to Piso, Providencia, Stgo de Chile.
http://www.linuxcenter.cl 2745000



From proski  Thu Aug 14 22:54:20 2003
From: proski (Pavel Roskin)
Date: Fri, 15 Aug 2003 01:54:20 -0400 (EDT)
Subject: Understanding what files are what in a flash archive
In-Reply-To: <200308150505.h7F554B1002342@bassett.home.org>
Message-ID: <Pine.LNX.4.44.0308150133470.2915-100000@portland.hansa.lan>

On Fri, 15 Aug 2003, James B. Hiller wrote:

> As I prepare to flash my DLink DWL-520 to get beyond reported buggy
> firmware, I have copied several firmware zip versions.  How does one
> determine the differences and applicability among the several types of
> files that seem to be included?

$ prism2_srec --help
[snip]
If -r, -g, or -f is not specified, image summary is shown and
compatibility with WLAN card is verified without downloading
anything.

> For example, 1.1.0 has a file with a pk prefix, and a number that
> doesn't quite match the "version" number; as well as an sf number,
> and a number that does resemble the version number.

This is described in http://home.eunet.cz/jt/wifi/Download.pdf by
Intersil.  It is also explained in simple terms in the mini-HOWTO at
http://linux.junsun.net/intersil-prism/

> Then I look in the 1.7.4 archive, and I see that there are 7 files of
> all kinds of prefices, include the sf as one of them. What are these
> various files for?

You forgot to say which archive.  If you have a problem, it may happen
that you are looking in a wrong place.

If you mean files under http://www.red-bean.com/~proski/firmware/, I put a
short explanation to http://www.red-bean.com/~proski/firmware/readme

> Is there a secret decoder ring out there for the file naming?  I've gone
> through a little over 50% of the hostap archive, and so far I remain
> clueless on this.

I'm sorry, the problem is that people who know enough to write
documentation spend their time on other things, including replies to the
mailing list, which may not give the complete picture.  But the mini-HOWTO
is a step in the right direction, and it was mentioned 3 times in the
mailing list.

-- 
Regards,
Pavel Roskin



From jhiller  Fri Aug 15 06:29:46 2003
From: jhiller (James B Hiller)
Date: Fri, 15 Aug 2003 09:29:46 -0400 (EDT)
Subject: Understanding what files are what in a flash archive
In-Reply-To: <Pine.LNX.4.44.0308150133470.2915-100000@portland.hansa.lan>
Message-ID: <Pine.GSO.4.05.10308150910370.7351-100000@ankara>

Hi!  Thanks for answering.

On Fri, 15 Aug 2003, Pavel Roskin wrote:

> On Fri, 15 Aug 2003, James B. Hiller wrote:
> 
> > firmware, I have copied several firmware zip versions.  How does one
> > determine the differences and applicability among the several types of
> > files that seem to be included?
> 
> $ prism2_srec --help
> [snip]
> If -r, -g, or -f is not specified, image summary is shown and
> compatibility with WLAN card is verified without downloading
> anything.

Yes, I did that with two of the zip archives, 1.1.0 and 1.7.4.  I
understand that this deals with the mechanics.  What I'm getting
at is more along the lines of "gee, there seem to be some naming
conventions going on here, maybe that differentiate between
a STA firmware and a PRI and maybe other kinds; but I've not a clue
what they would be."  For example, if my intent was to upgrade the
STA but not the PRI; or whatever.

And the 1.7.4 zip had so many different files, I had no idea conceptually
what they would each be for (maybe there are two each for three
different kinds of cards?  Point is, can't tell from names).

> > For example, 1.1.0 has a file with a pk prefix, and a number that
> > doesn't quite match the "version" number; as well as an sf number,
> > and a number that does resemble the version number.
> 
> This is described in http://home.eunet.cz/jt/wifi/Download.pdf by
> Intersil.  It is also explained in simple terms in the mini-HOWTO at
> http://linux.junsun.net/intersil-prism/

Ah!  Great!  Sorry if I missed these pointers in the list archive; believe
this would be exactly what I was looking for, but just couldn't come
up with it.

> > Then I look in the 1.7.4 archive, and I see that there are 7 files of
> > all kinds of prefices, include the sf as one of them. What are these
> > various files for?
> 
> You forgot to say which archive.  If you have a problem, it may happen
> that you are looking in a wrong place.

The 1.7.4.tar.gz archive from (in this case) your web site.

> If you mean files under http://www.red-bean.com/~proski/firmware/, I put a
> short explanation to http://www.red-bean.com/~proski/firmware/readme

Ah!  Outstanding!  Thx.  (Just to make sure my browser isn't flaky - those
details weren't in the readme last night, were they?  If they were, I
need a new netscape).

> > Is there a secret decoder ring out there for the file naming?  I've gone
> > through a little over 50% of the hostap archive, and so far I remain
> > clueless on this.
> 
> I'm sorry, the problem is that people who know enough to write
> documentation spend their time on other things, including replies to the
> mailing list, which may not give the complete picture.  But the mini-HOWTO
> is a step in the right direction, and it was mentioned 3 times in the
> mailing list.

I understand completely.  Wasn't doing any complaining; just didn't
want to bollix up my stuff due to my own ignorance, and after a long
time looking, I still hadn't found enough info to feel reasonably
clear on the concept.

On that note:  I greatly appreciate the amount of clarity you
and the other experts have had the time to shed, and your support
to the community on this topic.  Without it, I simply wouldn't
be able to any of what I've done at home.

thx,
jbh




From kiloman  Fri Aug 15 09:42:29 2003
From: kiloman (Brad Davidson)
Date: Fri, 15 Aug 2003 09:42:29 -0700
Subject: Understanding what files are what in a flash archive
In-Reply-To: <200308150505.h7F554B1002342@bassett.home.org>
References: <200308150505.h7F554B1002342@bassett.home.org>
Message-ID: <3F3D0D75.1010808@oatmail.org>

For the benefit of the archives, here's what the Intersil PDF says about 
the firmware naming scheme:

---
There are two types of firmware builds, developer builds and library 
release builds. Developer builds are firmware builds that are not 
reproducible and are not intended for external use.Library release 
builds are supported builds that have gone through the release and 
Quality Assurance process and are made available for external use.

Developer builds use the following naming convention:
<developer><type><date><platform><build_number>.HEX
where:
* developer is a single initial
* type can be I (Initial), P (Primary), S (Secondary), or T (Tertiary)
* date is a 4-character month/day combination
* platform is a 1-character platform ID
* build_number is a 1-character build number
For example, WS0126F0.HEX represents build 0 on 1/26 of Station firmware 
for the F platform.

Library releases use the following naming convention:
<type><platform><Version_Major/Minor><Version_Variant>.HEX
where:
* type can be I (Initial), P (Primary), S (Secondary), or T (Tertiary)
* platform is a 1-character platform ID
* Version_Major/Minor consists of a 2-character major version and 
2-character minor version
* Version_Variant is a 2-character version variant.
For example, SF010000.HEX represents a library release version 01.00.00 
of Station firmware for the F platform.
---

Hopefully that will save someone a bit of looking next time it's needed.

-Brad

James B. Hiller wrote:
> Is there a secret decoder ring out there for the file naming?  I've
> gone through a little over 50% of the hostap archive, and so far
> I remain clueless on this.



From landonc  Fri Aug 15 09:50:33 2003
From: landonc (Landon Chelf)
Date: Fri, 15 Aug 2003 12:50:33 -0400
Subject: Unable to Access Inet via HostAP
Message-ID: <006101c3634d$58bcb6a0$6901a8c0@Station13>

Hello,

Thanx in advance to anyone who can help me get this going.  I have
tinkered around and around with this and I have it functioning as a
visible access point that I can connect to.  My problem comes in when
trying to access the internet.  I'm not an iptables guru or anything but
I got the following as my iptables startup to supposedly masq the
connection correctly:

/etc/sysconfig/iptables file:

*filter

:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]

# Accept all traffic from the loopback interface.
-A INPUT -i lo -j ACCEPT

# Accept legitimate responses to traffic we generate.
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT

# Accept SSH connections from the wired network only.
-A INPUT -i eth0 -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT -i eth1 -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT -i wlan0 -p tcp -m tcp --dport 22 -j DROP

# Allow inbound DNS requests from the wireless network.
-A INPUT -s 0/0 -p udp --dport 53 -j ACCEPT
-A INPUT -s 0/0 -p tcp --dport 53 -j ACCEPT

# Allow inbound DHCP from the Local wireless network
-A INPUT -i wlan0 -p udp --dport 67:68 --sport 67:68 -j ACCEPT

# Allow all related traffic to/from non-privileged ports.
-A INPUT -p tcp -m tcp --sport 1024:65535 --dport 1024:65535 -m state
--state RELATED,ESTABLISHED -j ACCEPT

# Allow all traffic from the LAN to be forwarded to the WLAN.
-A FORWARD -i eth0 -o wlan0 -j ACCEPT

# Forward all legitimate responses to forwarded traffic.
-A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT

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

I've got my client computer setup connection to the AP and the wlan0 as
the gateway ip.  Please help.  You can IM me via MSN account
landonc at starrobbins.com.

Landon





From kiloman  Fri Aug 15 09:56:04 2003
From: kiloman (Brad Davidson)
Date: Fri, 15 Aug 2003 09:56:04 -0700
Subject: Unable to Access Inet via HostAP
In-Reply-To: <006101c3634d$58bcb6a0$6901a8c0@Station13>
References: <006101c3634d$58bcb6a0$6901a8c0@Station13>
Message-ID: <3F3D10A4.2020005@oatmail.org>

If people around here can't help you, you might have better luck over on 
the Linux Advanced Routing & Traffic Control (LARTC) mailing list. 
Firewall and routing rules are what they do over there. Help on this 
list drops off around the point you get the client connected to the 
Access Point :)

http://mailman.ds9a.nl/mailman/listinfo/lartc

-Brad

Landon Chelf wrote:
> Thanx in advance to anyone who can help me get this going.  I have
> tinkered around and around with this and I have it functioning as a
> visible access point that I can connect to.  My problem comes in when
> trying to access the internet.  I'm not an iptables guru or anything but
> I got the following as my iptables startup to supposedly masq the
> connection correctly:
> 
> /etc/sysconfig/iptables file:




From dilip  Fri Aug 15 14:36:23 2003
From: dilip (Dilip Sundarraj)
Date: Fri, 15 Aug 2003 14:36:23 -0700 (PDT)
Subject: Tx power in Linksys WPC 11 v3.0 
Message-ID: <Pine.GSO.4.56.0308151431560.12044@sirius.cs.pdx.edu>

Hi,

I read an earlier  mail in the hostap mailing list about the problem with
power control with Linksys WPC11. The minimum value of Tx power that was
observed had a transmission range of 8m. However, we require a shorter
range than this.  I was wondering if there is a card which can provide a
shorter Tx range than 8m.

I'd appreciate any reply.

Thanks
Dilip



From jphstap  Fri Aug 15 15:05:46 2003
From: jphstap (Joe Parks)
Date: 15 Aug 2003 18:05:46 -0400
Subject: Tx power in Linksys WPC 11 v3.0
In-Reply-To: <Pine.GSO.4.56.0308151431560.12044@sirius.cs.pdx.edu>
References: <Pine.GSO.4.56.0308151431560.12044@sirius.cs.pdx.edu>
Message-ID: <1060985146.2536.161.camel@scrodconumulus>

On Fri, 2003-08-15 at 17:36, Dilip Sundarraj wrote:
> Hi,
> 
> I read an earlier  mail in the hostap mailing list about the problem with
> power control with Linksys WPC11. The minimum value of Tx power that was
> observed had a transmission range of 8m. However, we require a shorter
> range than this.  I was wondering if there is a card which can provide a
> shorter Tx range than 8m.

You can try using an external antenna on a card that supports them, such
as the Zcomax cards.   If you use the foil from a gum wrapper as a
dipole that might be terrible enough to give you a very short range ;)

Dropping an ordinary plastic-coated dipole into a test-tube filled with
water should attenuate the signal quite nicely too.

If you're not just looking to shorten your range, but also to save
power, then my recommendations are just silly.   Sorry about that.



From tchen  Fri Aug 15 18:33:33 2003
From: tchen (Thomas Chen)
Date: Fri, 15 Aug 2003 18:33:33 -0700
Subject: HOSTAP for bluetooth
Message-ID: <BB62D7FD.D237%tchen@on-go.com>

is there any potential of making bluetooth access point using
a bluetooth pcmcia/cf card just like hostap did with wifi 802.11 ??




From jkmaline  Fri Aug 15 19:06:41 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 15 Aug 2003 19:06:41 -0700
Subject: Unable to Access Inet via HostAP
In-Reply-To: <006101c3634d$58bcb6a0$6901a8c0@Station13>
References: <006101c3634d$58bcb6a0$6901a8c0@Station13>
Message-ID: <20030816020640.GA3609@jm.kir.nu>

On Fri, Aug 15, 2003 at 12:50:33PM -0400, Landon Chelf wrote:

> Thanx in advance to anyone who can help me get this going.  I have
> tinkered around and around with this and I have it functioning as a
> visible access point that I can connect to.  My problem comes in when
> trying to access the internet.

You do not fully describe your network so one needs to guess some parts
of it.. And yes, this is somewhat off topic for Host AP mailing list,
since it sounds like the wireless part is actually working ;-).

> /etc/sysconfig/iptables file:
> :FORWARD DROP [0:0]
> -A FORWARD -i eth0 -o wlan0 -j ACCEPT
> -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT

These were all rules you had for FORWARD chain. In other words, you
allow connections to be started from eth0 to wlan0 and you allow packets
to existing connection from wlan0 to eth0. However, you do not allow any
new connections from wlan0 to any host that requires IP routing (i.e.,
to any other host apart from the AP).

-- 
Jouni Malinen                                            PGP id EFC895FA



From james.harper  Sat Aug 16 04:00:48 2003
From: james.harper (James Harper)
Date: Sat, 16 Aug 2003 21:00:48 +1000
Subject: 2.6.0-test3 (and -test2)
Message-ID: <000001c363e5$a6ac34b0$c7fda8c0@int.sbss.com.au>

All,

I can't get hostap to compile against 2.6.0-test3 (I didn't have any
luck with -test2 either but only tried that once). My kernel tree is
pretty much virgin. I'm using the cvs tree. I'm also compiling it all as
modules.

Does anyone have it going against this kernel? I get errors in
hostap_crypt, it appears that if HOSTAP_CRYPT_MODULE was defined I might
have more luck, or maybe my kernel tree is broken and I need a new one.

Any suggestions?

Thanks

James



From jkmaline  Sat Aug 16 09:04:35 2003
From: jkmaline (Jouni Malinen)
Date: Sat, 16 Aug 2003 09:04:35 -0700
Subject: 2.6.0-test3 (and -test2)
In-Reply-To: <000001c363e5$a6ac34b0$c7fda8c0@int.sbss.com.au>
References: <000001c363e5$a6ac34b0$c7fda8c0@int.sbss.com.au>
Message-ID: <20030816160435.GA3251@jm.kir.nu>

On Sat, Aug 16, 2003 at 09:00:48PM +1000, James Harper wrote:

> I can't get hostap to compile against 2.6.0-test3 (I didn't have any
> luck with -test2 either but only tried that once). My kernel tree is
> pretty much virgin. I'm using the cvs tree. I'm also compiling it all as
> modules.

Please always include the exact commands you used and error messages you
saw when reporting compilation problems. If you used any other command,
please also note that plain 'make' is the best (and probably only) way
to compile the driver for Linux 2.5/2.6.

> Does anyone have it going against this kernel? I get errors in
> hostap_crypt, it appears that if HOSTAP_CRYPT_MODULE was defined I might
> have more luck, or maybe my kernel tree is broken and I need a new one.

Yes, works fine with 2.6.0-test3 (and worked with -test2, too).
HOSTAP_CRYPT_MODULE should not be defined. hostap_crypt module is now
compined into hostap.o.

-- 
Jouni Malinen                                            PGP id EFC895FA



From james.harper  Sat Aug 16 20:35:29 2003
From: james.harper (James Harper)
Date: Sun, 17 Aug 2003 13:35:29 +1000
Subject: 2.6.0-test3 (and -test2)
References: <000001c363e5$a6ac34b0$c7fda8c0@int.sbss.com.au>
	<20030816160435.GA3251@jm.kir.nu>
Message-ID: <3F3EF801.4030101@bigpond.com>

Jouni Malinen wrote:

>On Sat, Aug 16, 2003 at 09:00:48PM +1000, James Harper wrote:
>
>  
>
>>I can't get hostap to compile against 2.6.0-test3 (I didn't have any
>>luck with -test2 either but only tried that once). My kernel tree is
>>pretty much virgin. I'm using the cvs tree. I'm also compiling it all as
>>modules.
>>    
>>
>
>Please always include the exact commands you used and error messages you
>saw when reporting compilation problems. If you used any other command,
>please also note that plain 'make' is the best (and probably only) way
>to compile the driver for Linux 2.5/2.6.
>
>  
>
>>Does anyone have it going against this kernel? I get errors in
>>hostap_crypt, it appears that if HOSTAP_CRYPT_MODULE was defined I might
>>have more luck, or maybe my kernel tree is broken and I need a new one.
>>    
>>
>
>Yes, works fine with 2.6.0-test3 (and worked with -test2, too).
>HOSTAP_CRYPT_MODULE should not be defined. hostap_crypt module is now
>compined into hostap.o.
>
>  
>
sorry, all i was asking for was a 'does it work?'... if there was a 
known problem then it's a bit of a waste of time me discovering it all 
over again.
I tracked it down earlier this morning though, once I excluded 
hostap_crypt.c from the Makefile it all worked fine. I'm running with 
2.6.0-test3 as I type this. I've always copied the files into the kernel 
tree and compiled from there with a 'make -j5 modules'. I believe the 
kernel patch for 2.6.0-test2 (and therefore also -test3) should have 
hostap_crypt.c removed from the makefile. It certainly works fine 
without it being there and doesn't work with it.

thanks

James





From zhengjr  Sun Aug 17 09:36:44 2003
From: zhengjr (???)
Date: Mon, 18 Aug 2003 00:36:44 +0800
Subject: how to make my AP work?
References: <20030815120037.F273C245B8@mail.iocaine.com>
Message-ID: <000b01c364dd$c0e4dc80$c8fdfea9@gigabyteli>

hello,i got some problem.
i have made a linux kernel supported with devfs.
and i load T1085800.hfw firmware ok!
so now.Other PC's wireless card can connect to my wireless card regarded
as AP.
But
They can't use my AP connect to LAN or Internet.
plz help me.
can anyone teach me how to make it as real AP working?
thx ur reply.

ps:my wire adpater is use DHCP to connect Internet. Is it a problem?

show my ifconfig:
Code:

eth0      Link encap:Ethernet  HWaddr 00:D0:59:0F:4F:1D
          inet addr:192.168.100.4  Bcast:192.168.100.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:59ff:fe0f:4f1d/10 Scope:Link
          inet6 addr: 3ffe:3600:1a:1:2d0:59ff:fe0f:4f1d/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:34312 errors:0 dropped:0 overruns:0 frame:0
          TX packets:433 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:21948616 (20.9 Mb)  TX bytes:80039 (78.1 Kb)
          Interrupt:9 Base address:0x4000

eth1      Link encap:Ethernet  HWaddr 00:02:2D:88:19:C1
          inet addr:140.116.246.198  Bcast:140.116.246.255
Mask:255.255.255.0
          inet6 addr: fe80::202:2dff:fe88:19c1/10 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2779 errors:0 dropped:0 overruns:0 frame:0
          TX packets:181 errors:3 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:1864533 (1.7 Mb)  TX bytes:27548 (26.9 Kb)
          Interrupt:3 Base address:0x100


show my iwconfig:
Code:

eth1      IEEE 802.11-DS  ESSID:"simata"  Nickname:"localhost.localdomain"
          Mode:Master  Frequency:2.412GHz  Access Point: 00:00:00:00:00:00
          Bit Rate=5.5Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
          Retry limit:4   RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality:0/0  Signal level:-34 dBm  Noise level:-40 dBm
          Rx invalid nwid:0  Rx invalid crypt:18  Rx invalid frag:2
          Tx excessive retries:28  Invalid misc:0   Missed beacon:0





From james.harper  Sun Aug 17 03:24:47 2003
From: james.harper (James Harper)
Date: Sun, 17 Aug 2003 20:24:47 +1000
Subject: SMP report
Message-ID: <3F3F57EF.7020002@bigpond.com>

I'm running 2.6.0-test3 with the latest cvs version of hostap on an SMP 
system and it appears much more stable than previous versions. I just 
tried a flood ping for a few minutes and the only error I got was:

Aug 17 20:19:17 portal kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
busy for 1 usec
Aug 17 20:20:53 portal kernel: wlan0: detected fid change (try=0, 
reg=0044): 0166 a5a4 0166
Aug 17 20:20:59 portal kernel: wlan0: detected fid change (try=0, 
reg=0040): 0000 03d6 03d6

which probably isn't good but previously I would be getting card resets 
and/or crashes etc all over the place.

hope that information is of some use to someone...

James





From proski  Sun Aug 17 19:59:33 2003
From: proski (Pavel Roskin)
Date: Sun, 17 Aug 2003 22:59:33 -0400 (EDT)
Subject: how to make my AP work?
In-Reply-To: <000b01c364dd$c0e4dc80$c8fdfea9@gigabyteli>
Message-ID: <Pine.LNX.4.44.0308172254440.13006-100000@portland.hansa.lan>

On Mon, 18 Aug 2003, ??? wrote:

> hello,i got some problem. i have made a linux kernel supported with
> devfs. and i load T1085800.hfw firmware ok!

HostAP doesn't work with tertiary firmware.  It makes secondary
firmware act as an access point.  If you want to use tertiary firmware,
use linux-wlan-ng.

Next time please report version of the software that gives you the
problem.  Also, a step-by-step explanation of what you are doing would be
helpful.  Relevant parts of the kernel log (as reported by dmesg) may be
useful as well.

-- 
Regards,
Pavel Roskin




From maty10  Mon Aug 18 01:22:01 2003
From: maty10 (Mathew Burns)
Date: Mon, 18 Aug 2003 18:22:01 +1000
Subject: Hard lockup with XI-636
Message-ID: <3F408CA9.4060503@iprimus.com.au>

I have a zcom (rebadged as skymaster here in australia) xi-626 pci card 
working fine in ad-hoc mode with the oricono_pci module but would like 
to use one of two identical boxes as a AP.

Whenever I issue "modprobe hostap_pci" the machine hard locks, with 
nothing written to syslog or dmesg.
The last line written by modprobe is "registered net device: wlan0"

Kernel 2.4.21 compiled myself with the wireless extention patches 
applied as suggested.

Can anyone help me start looking for a cause to this?






From DANIEL.ARLETH  Mon Aug 18 04:34:23 2003
From: DANIEL.ARLETH (ARLETH, DANIEL)
Date: Mon, 18 Aug 2003 13:34:23 +0200
Subject: Symbol/Nortel 4123 PCI Adapter - Port orinoco module to hostap
Message-ID: <252E5192A5C2D311B24B00508B5D5CCCBD821F@slpms0.sel.de>

Hello List,

after occasionally reading success messages from people using the (really
great) hostap driver in managed mode for the Symbol/Nortel pcmcia cards, I
hope I could get some help for my PCI Card here.

I want to run the Nortel PCI Card (4123) as a member of a bridge(, but the
symbol support in the Orinoco driver seems not to be ready for this).
I tried with the module available at
http://www.traum404.de/download/index.html
<http://www.traum404.de/download/index.html> .

As far as I can see (with my very basic C knowledge) this module consists of
only a few lines of code to initial the pcmcia card, and then let the
Orinoco driver do its work.
The only thing which has to be changed in the Orinoco driver are two lines
of code in Orinoco.c and Orinoco.h.

void hermes_struct_init(hermes_t *hw, ulong address,
			int io_space, int reg_spacing)
{
	hw->iobase = address;
>	hw->iobase1 = 0;
>	hw->iobase2 = 0;
       	hw->io_space = io_space;
	hw->reg_spacing = reg_spacing;
	hw->inten = 0x0;

So my hope is, this could be as easy for the hostap driver.

Please don't understand me wrong! I don't ask you for writing a driver for
me! But I can't do it and I hope to hear from you either 
"Forget it! The hostap has got nothing in common with the Orinoco driver, so
the Nortel_pci module is useless for the hostap driver" 
or
"No problem! Just ask a friend with C knowledge to have a look at it and
change ..........."

Or just gave me any hint how to get my Card running in a bridge.

Thanks,

Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030818/d022544b/attachment.htm 


From gallir  Mon Aug 18 05:05:05 2003
From: gallir (Ricardo Galli)
Date: Mon, 18 Aug 2003 14:05:05 +0200
Subject: Symbol/Nortel 4123 PCI Adapter - Port orinoco module to hostap
In-Reply-To: <252E5192A5C2D311B24B00508B5D5CCCBD821F@slpms0.sel.de>
References: <252E5192A5C2D311B24B00508B5D5CCCBD821F@slpms0.sel.de>
Message-ID: <200308181405.05451.gallir@uib.es>

On Monday 18 August 2003 13:34, ARLETH, DANIEL shaped the electrons to shout:
> Hello List,
>
> after occasionally reading success messages from people using the (really
> great) hostap driver in managed mode for the Symbol/Nortel pcmcia cards, I
> hope I could get some help for my PCI Card here.
>
> I want to run the Nortel PCI Card (4123) as a member of a bridge(, but the
> symbol support in the Orinoco driver seems not to be ready for this).

You are very confused. 

What do you want to achieve by putting a managed wireless card in a bridge? I 
guess you want to do level 2 bridging. To do it you should have the original 
source MAC (SA) and the final destination MAC (DA), which is _impossible_ in 
a "managed" card, which only deal with "receiving address" (RA) and 
"transmitter address" (TA).

To make it work you need:

a) An AP that is able to bridge between its associated stations and the 
ethernet. The master interface knows the MAC of every associated station and 
the ethernet has the original source and destination MAC, so bridging between 
the ethernet and (only) associated stations is possible.

b) Or, if you want to connect two different LANs, the card/SO needs two extra 
headers (SA and RA), and that the goal of WDS and the four headers (RA, TA, 
SA and DA).

So, put your "bridging" wireless card in master mode and add it to a bridging 
group. Or for managed one you can only do IP routing.


-- 
  ricardo galli       GPG id C8114D34
  http://mnm.uib.es/~gallir/




From zhengjr  Mon Aug 18 05:42:11 2003
From: zhengjr (???)
Date: Mon, 18 Aug 2003 20:42:11 +0800
Subject: how to make my AP work? 
References: <20030818120553.38EFFEA99@mail.iocaine.com>
Message-ID: <000901c36586$25b1faf0$7bf7748c@gigabyteli>

> HostAP doesn't work with tertiary firmware.  It makes secondary
> firmware act as an access point.  If you want to use tertiary firmware,
> use linux-wlan-ng.
> Next time please report version of the software that gives you the
> problem.  Also, a step-by-step explanation of what you are doing would be
> helpful.  Relevant parts of the kernel log (as reported by dmesg) may be
> useful as well.
> -Regards,
> -Pavel Roskin
It's very sorry. I dont say clearly. I use Avaya's wireless PCMCIA card.
so I use HermesAP-0.2. Now, I have installed heremesAP and made it work.
Other PC's wireless device can connect to my wireless interface.
My problem is how to make my AP like bridge, so that others connected to my
AP can
connected to Internet.
Someone tells me to setup NAT or makes my wire card to be shared with all
devices.
However I am newbie on wireless and network. So I need more detail to do
that.
Hope people can teach me how to do that or where have information about
that.

-thx ur reply,very appreciate.
-simata(zhengjr at locust.csie.ncku.edu.tw)





From DANIEL.ARLETH  Mon Aug 18 06:30:51 2003
From: DANIEL.ARLETH (ARLETH, DANIEL)
Date: Mon, 18 Aug 2003 15:30:51 +0200
Subject: Symbol/Nortel 4123 PCI Adapter - Port orinoco module to hosta p
Message-ID: <252E5192A5C2D311B24B00508B5D5CCCBD8220@slpms0.sel.de>

Ok, you are right. (Now) I'm very confused...........

My configuration:

Internet
   |     
 Router  (managed by my ISP)
   |
   |     (wired)
   |
 My AP1  (Prism2 in PLX / hostap in master mode
   |              Bridge between eth0/wlan0/wlan0wds0)
   |     (wds)
   |
 My AP2  (Prism2 in PLX / hostap in master mode
   |              Bridge between eth0/wlan0/wlan0wds0)
   |
   |-- wired clients
   |
wireless clients

The ISP Router and AP1 are placed at the attic, accessible for everybody, so
I bought a small cabinet to secure them. That's the reason why I bought the
Nortel Card, because of its external antenna.

And now I want to associate the AP1 as a normal client to the AP2 (because
there is no master mode driver for the Nortel card), but bridge the ISP
router and the wlan anyway together. 

The ISP Router masquerades all connections, because the internal net is
192.168.0.0 and I can't add static routes so I would have to masquerade on
AP1, too. That may work, but hmm, I think there must be a better way. 

Any idea?? Maybe something like proxy arp? Remember, I don't want to connect
a whole network behind AP1, only one client(the ISP router).

And there is really no chance to get the bridge up with a wlan Card in
managed mode?

Btw, is there any difference between "managed mode" and "station mode", or
does both mean the same?

Daniel
 

> Hello List,
>
> after occasionally reading success messages from people using the (really
> great) hostap driver in managed mode for the Symbol/Nortel pcmcia cards, I
> hope I could get some help for my PCI Card here.
>
> I want to run the Nortel PCI Card (4123) as a member of a bridge(, but the
> symbol support in the Orinoco driver seems not to be ready for this).

You are very confused. 

What do you want to achieve by putting a managed wireless card in a bridge?
I 
guess you want to do level 2 bridging. To do it you should have the original

source MAC (SA) and the final destination MAC (DA), which is _impossible_ in

a "managed" card, which only deal with "receiving address" (RA) and 
"transmitter address" (TA).

To make it work you need:

a) An AP that is able to bridge between its associated stations and the 
ethernet. The master interface knows the MAC of every associated station and

the ethernet has the original source and destination MAC, so bridging
between 
the ethernet and (only) associated stations is possible.

b) Or, if you want to connect two different LANs, the card/SO needs two
extra 
headers (SA and RA), and that the goal of WDS and the four headers (RA, TA, 
SA and DA).

So, put your "bridging" wireless card in master mode and add it to a
bridging 
group. Or for managed one you can only do IP routing.


-- 
  ricardo galli       GPG id C8114D34
  http://mnm.uib.es/~gallir/






From hdxia1  Mon Aug 18 06:57:40 2003
From: hdxia1 (Haidong Xia)
Date: Mon, 18 Aug 2003 13:57:40 +0000
Subject: HostAP Digest, Vol 4, Issue 33
Message-ID: <BAY1-F19Y1qClo8XoPN00028c13@hotmail.com>

Dear all,

Can anyone explain to me how HostAP set up a default wep key ? Since I don't 
have a hardware manual of prism2 card, I am a little confused, when I read 
the code of WEP key setting under HostAP.

The basic question is: When HostAP sets up a default wep key, a WinXP client 
automatically detects this access point has a default wep key. How a WinXP 
client know an Access Point has a WEP key, right after association?

I am doing an experiment to allow both of clients using Wep key, or not 
using wep key to get access to an Access point. But WinXP client keeps 
saying there is a wep key, and just wants to use a Wep key, even I didn't 
set up a key for it.

Is there a way to set up a default wep key in HostAP, but WinXP client will 
not detect it?  So that a user can configure the client freely with or with 
WEP key?   Of course, at hostAP side, it can detect a
frame is encrypted or not, and deal with it correspondingly.

Thanks for any point.
Haidong

_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE* 
http://join.msn.com/?page=features/virus




From askatti  Mon Aug 18 11:21:36 2003
From: askatti (Anand S. Katti)
Date: Mon, 18 Aug 2003 23:51:36 +0530 (IST)
Subject: how to make my AP work?
In-Reply-To: <20030818180003.7B350EAEC@mail.iocaine.com>
Message-ID: <Pine.LNX.4.44.0308182345370.20297-100000@ece.iisc.ernet.in>


> Someone tells me to setup NAT or makes my wire card to be shared with all
> devices.

If you are newbie and want some easy tool to setup NAT, I suggest you 
install SHOREWALL (an iptable based firewall http://shorewall.net/). And 
to configure the firewall you have to install WEBMIN(a system 
administration tool http://webmin.com/)

webmin has shorewall module in it, that helps u in configuring the 
firewall easily. In shorewall you can setup NAT and make other nodes 
browse the internet vai NAT.

If any problems in this let me know.
-------
With Regards,
Anand S. Katti






From proski  Mon Aug 18 12:10:26 2003
From: proski (Pavel Roskin)
Date: Mon, 18 Aug 2003 15:10:26 -0400 (EDT)
Subject: 2.6.0-test3 (and -test2)
In-Reply-To: <3F3EF801.4030101@bigpond.com>
References: <000001c363e5$a6ac34b0$c7fda8c0@int.sbss.com.au>
	<20030816160435.GA3251@jm.kir.nu> <3F3EF801.4030101@bigpond.com>
Message-ID: <Pine.LNX.4.56.0308181507140.20845@marabou.research.att.com>

On Sun, 17 Aug 2003, James Harper wrote:

> sorry, all i was asking for was a 'does it work?'... if there was a
> known problem then it's a bit of a waste of time me discovering it all
> over again.

Just in case, 2.6.0-test3 seems to have an interrupt problem with PCI
bridges by Texas Insriments.  2.6.0-test2 is OK.

> I tracked it down earlier this morning though, once I excluded
> hostap_crypt.c from the Makefile it all worked fine. I'm running with
> 2.6.0-test3 as I type this. I've always copied the files into the kernel
> tree and compiled from there with a 'make -j5 modules'. I believe the
> kernel patch for 2.6.0-test2 (and therefore also -test3) should have
> hostap_crypt.c removed from the makefile. It certainly works fine
> without it being there and doesn't work with it.

Yes, it's time to clean up references to hostap_crypt module and
hostap_crypt.c as the source for that module.  The patch is attached.

-- 
Regards,
Pavel Roskin
-------------- next part --------------
--- Makefile
+++ Makefile
@@ -105,22 +105,19 @@
 
 ifdef CONFIG_MODVERSIONS
 
-VERFILES=$(MSRC)/hostap.ver ## $(MSRC)/hostap_crypt.ver
+VERFILES=$(MSRC)/hostap.ver
 $(MSRC)/hostap_crypt_wep.o: $(VERFILES)
 $(MSRC)/hostap.o: $(VERFILES)
 $(MSRC)/hostap_cs.o: $(VERFILES)
 $(MSRC)/hostap_plx.o: $(VERFILES)
 $(MSRC)/hostap_pci.o: $(VERFILES)
-INCLUDES_MODVER=-include $(MSRC)/hostap.ver ##-include $(MSRC)/hostap_crypt.ver
+INCLUDES_MODVER=-include $(MSRC)/hostap.ver
 
 GENKSYMS=/sbin/genksyms
 ifdef CONFIG_SMP
         GENKSYMS += -p smp_
 endif
 
-##$(MSRC)/hostap_crypt.ver: $(MSRC)/hostap_crypt.c
-##	$(CC) $(INCLUDES) $(CFLAGS) -E -D__GENKSYMS__ $^ | \
-##		$(GENKSYMS) -k $(KERNELVER) > $@
 $(MSRC)/hostap.ver: $(MSRC)/hostap.c
 	$(CC) $(INCLUDES) $(CFLAGS) -E -D__GENKSYMS__ $^ | \
 		$(GENKSYMS) -k $(KERNELVER) > $@
@@ -155,7 +152,7 @@
 pccard:	$(MSRC)/$(MODULE_CS) hostap crypt install_info
 plx:	$(MSRC)/$(MODULE_PLX) hostap crypt install_info
 pci:	$(MSRC)/$(MODULE_PCI) hostap crypt install_info
-crypt:  $(MSRC)/hostap_crypt_wep.o ## $(MSRC)/hostap_crypt.o
+crypt:  $(MSRC)/hostap_crypt_wep.o
 hostap: $(MSRC)/hostap.o
 
 SRC=$(MSRC)/hostap_hw.c $(MSRC)/hostap_wlan.h $(MSRC)/hostap_config.h \
@@ -163,8 +160,6 @@
 	$(MSRC)/hostap_ap.h \
 	$(MSRC)/hostap_crypt.h $(MSRC)/hostap.h $(MSRC)/hostap_compat.h
 
-## $(MSRC)/hostap_crypt.o: $(MSRC)/hostap_crypt.c $(MSRC)/hostap_crypt.h
-
 $(MSRC)/hostap_crypt_wep.o: $(MSRC)/hostap_crypt_wep.c $(MSRC)/hostap_crypt.h
 
 $(MSRC)/hostap.o: $(MSRC)/hostap.c $(MSRC)/hostap.h \
@@ -229,7 +224,7 @@
 	mkdir -p $(MODPATH_PCI)
 	cp -f $(MSRC)/hostap.o $(MODPATH_PCI)
 
-install_crypt: $(MSRC)/hostap_crypt_wep.o ## $(MSRC)/hostap_crypt.o
+install_crypt: $(MSRC)/hostap_crypt_wep.o
 	@echo "Installing hostap_crypt_*.o to $(MODPATH_PCI)"
 	mkdir -p $(MODPATH_PCI)
 	cp -f $(MSRC)/hostap_crypt_*.o $(MODPATH_PCI)
--- driver/hostap.mk
+++ driver/hostap.mk
@@ -1,11 +1,9 @@
 all:
 	$(MAKE) -C modules MODULES=hostap_cs.o
 	$(MAKE) -C modules MODULES=hostap.o
-	$(MAKE) -C modules MODULES=hostap_crypt.o
 	$(MAKE) -C modules MODULES=hostap_crypt_wep.o
 
 install:
 	$(MAKE) -C modules install-modules MODULES=hostap_cs.o
 	$(MAKE) -C modules install-modules MODULES=hostap.o
-	$(MAKE) -C modules install-modules MODULES=hostap_crypt.o
 	$(MAKE) -C modules install-modules MODULES=hostap_crypt_wep.o
--- driver/modules/Makefile
+++ driver/modules/Makefile
@@ -1,10 +1,9 @@
 # Makefile for Linux 2.6 kbuild / Linux 2.4
 
 # export-objs was removed in Linux 2.5.60
-# export-objs := hostap.o ## hostap_crypt.o
+# export-objs := hostap.o
 
 obj-m += hostap.o hostap_crypt_wep.o
-## obj-m += hostap_crypt.o
 obj-m += hostap_cs.o
 obj-m += hostap_plx.o
 obj-m += hostap_pci.o
@@ -15,22 +14,19 @@
 
 ifdef CONFIG_MODVERSIONS
 
-VERFILES=hostap.ver ## hostap_crypt.ver
+VERFILES=hostap.ver
 hostap_crypt_wep.o: $(VERFILES)
 hostap.o: $(VERFILES)
 hostap_cs.o: $(VERFILES)
 hostap_plx.o: $(VERFILES)
 hostap_pci.o: $(VERFILES)
-INCLUDES_MODVER=-include hostap.ver ## -include hostap_crypt.ver
+INCLUDES_MODVER=-include hostap.ver
 
 GENKSYMS=/sbin/genksyms
 ifdef CONFIG_SMP
         GENKSYMS += -p smp_
 endif
 
-## hostap_crypt.ver: hostap_crypt.c
-##	$(CC) $(INCLUDES) $(CFLAGS) -E -D__GENKSYMS__ $^ | \
-##		$(GENKSYMS) -k $(VERSION).$(PATCHLEVEL).$(SUBLEVEL) > $@
 hostap.ver: hostap.c
 	$(CC) $(INCLUDES) $(CFLAGS) -E -D__GENKSYMS__ $^ | \
 		$(GENKSYMS) -k $(VERSION).$(PATCHLEVEL).$(SUBLEVEL) > $@
--- driver_source.txt
+++ driver_source.txt
@@ -40,13 +40,13 @@
 hostap_plx.c
 	Hardware specific routines for PLX-based PC Card adapter version
 
-
-crypto modules:
-
 hostap_crypt.[ch]
 	Registration/unregistration code for modularized encryption
 	implementation
 
+
+crypto modules:
+
 hostap_crypt_wep.c
 	Host-based WEP (Wired Equivalent Privacy) implementation
 
--- kernel-patches/hostap-linux-2.4.20.patch
+++ kernel-patches/hostap-linux-2.4.20.patch
@@ -19,7 +19,7 @@
 +  PLX/PCI/CS version of the driver to actually use the driver.
 +
 +  The driver can be compiled as modules and they will be called
-+  "hostap.o", "hostap_crypt.o", and "hostap_crypt_wep.o".
++  "hostap.o" and "hostap_crypt_wep.o".
 +
 +Host AP driver for Prism2/2.5/3 in PLX9052 based PCI adaptors
 +CONFIG_HOSTAP_PLX
@@ -108,7 +108,7 @@
  
  # Things that need to export symbols
 -export-objs	:= airo.o orinoco.o hermes.o
-+export-objs	:= airo.o orinoco.o hermes.o hostap.o hostap_crypt.o
++export-objs	:= airo.o orinoco.o hermes.o hostap.o
  
  obj-$(CONFIG_HERMES)		+= orinoco.o hermes.o
  obj-$(CONFIG_PCMCIA_HERMES)	+= orinoco_cs.o
@@ -116,7 +116,7 @@
  obj-$(CONFIG_AIRO)		+= airo.o
  obj-$(CONFIG_AIRO_CS)		+= airo_cs.o airo.o
  
-+obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt.o hostap_crypt_wep.o
++obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt_wep.o
 +obj-$(CONFIG_HOSTAP_CS)		+= hostap_cs.o
 +obj-$(CONFIG_HOSTAP_PLX)	+= hostap_plx.o
 +obj-$(CONFIG_HOSTAP_PCI)	+= hostap_pci.o
--- kernel-patches/hostap-linux-2.5.60.patch
+++ kernel-patches/hostap-linux-2.5.60.patch
@@ -38,7 +38,7 @@
 +	PLX/PCI/CS version of the driver to actually use the driver.
 +
 +	The driver can be compiled as modules and they will be called
-+	"hostap.o", "hostap_crypt.o", and "hostap_crypt_wep.o".
++	"hostap.o" and "hostap_crypt_wep.o".
 +
 +config HOSTAP_HOSTAPD
 +	bool "Use user space daemon (hostapd) with Host AP driver"
@@ -114,7 +114,7 @@
  obj-$(CONFIG_AIRO)		+= airo.o
  obj-$(CONFIG_AIRO_CS)		+= airo_cs.o airo.o
 +
-+obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt.o hostap_crypt_wep.o
++obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt_wep.o
 +obj-$(CONFIG_HOSTAP_CS)		+= hostap_cs.o
 +obj-$(CONFIG_HOSTAP_PLX)	+= hostap_plx.o
 +obj-$(CONFIG_HOSTAP_PCI)	+= hostap_pci.o
--- kernel-patches/hostap-linux-2.5.69.patch
+++ kernel-patches/hostap-linux-2.5.69.patch
@@ -36,7 +36,7 @@
 +	PLX/PCI/CS version of the driver to actually use the driver.
 +
 +	The driver can be compiled as modules and they will be called
-+	"hostap.o", "hostap_crypt.o", and "hostap_crypt_wep.o".
++	"hostap.o" and "hostap_crypt_wep.o".
 +
 +config HOSTAP_FIRMWARE
 +	bool "Support downloading firmware images with Host AP driver"
@@ -97,7 +97,7 @@
  obj-$(CONFIG_AIRO)		+= airo.o
  obj-$(CONFIG_AIRO_CS)		+= airo_cs.o airo.o
  
-+obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt.o hostap_crypt_wep.o
++obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt_wep.o
 +obj-$(CONFIG_HOSTAP_CS)		+= hostap_cs.o
 +obj-$(CONFIG_HOSTAP_PLX)	+= hostap_plx.o
 +obj-$(CONFIG_HOSTAP_PCI)	+= hostap_pci.o
--- kernel-patches/hostap-linux-2.6.0-test2.patch
+++ kernel-patches/hostap-linux-2.6.0-test2.patch
@@ -38,7 +38,7 @@
 +	PLX/PCI/CS version of the driver to actually use the driver.
 +
 +	The driver can be compiled as modules and they will be called
-+	"hostap.o", "hostap_crypt.o", and "hostap_crypt_wep.o".
++	"hostap.o" and "hostap_crypt_wep.o".
 +
 +config HOSTAP_FIRMWARE
 +	bool "Support downloading firmware images with Host AP driver"
@@ -100,7 +100,7 @@
  obj-$(CONFIG_AIRO)		+= airo.o
  obj-$(CONFIG_AIRO_CS)		+= airo_cs.o airo.o
  
-+obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt.o hostap_crypt_wep.o
++obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt_wep.o
 +obj-$(CONFIG_HOSTAP_CS)		+= hostap_cs.o
 +obj-$(CONFIG_HOSTAP_PLX)	+= hostap_plx.o
 +obj-$(CONFIG_HOSTAP_PCI)	+= hostap_pci.o
--- pcmcia-cs-patches/hostap-pcmcia-cs-3.1.34.patch
+++ pcmcia-cs-patches/hostap-pcmcia-cs-3.1.34.patch
@@ -6,13 +6,13 @@
  endif
  
 +# Host AP driver
-+MODULES	+= hostap.o hostap_crypt.o hostap_crypt_wep.o hostap_cs.o
-+SRCS	+= hostap.c hostap_crypt.c hostap_crypt_wep.c hostap_cs.c
++MODULES	+= hostap.o hostap_crypt_wep.o hostap_cs.o
++SRCS	+= hostap.c hostap_crypt_wep.c hostap_cs.c
 +
  all:	$(MODULES)
  
 -wvlan_hcf.o wvlan_hcfio.o hermes.o orinoco.o: %.o: %.c
-+wvlan_hcf.o wvlan_hcfio.o hermes.o orinoco.o hostap.o hostap_crypt.o: %.o: %.c
++wvlan_hcf.o wvlan_hcfio.o hermes.o orinoco.o hostap.o: %.o: %.c
  	$(CC) -MD -c $(XFLAGS) $<
  	@mkdir -p .depfiles ; mv $*.d .depfiles
  
--- todo.lst
+++ todo.lst
@@ -50,8 +50,6 @@
 - make sure that hostscan setting is re-set after card reset
 - reuse prism2_tx code with prism2_tx_80211
 - new module code should use try_module_get() for crypto modules
-- could actually integrate hostap_crypt.o module into hostap.o.. I don't think
-  it is that likely that only encryption stuff would be used in other drivers
 - ioctl's can be interrupted (EINTR, e.g., by killing iwconfig) which can
   result in leaving entries to pending CmdCompl list or command completion
   events to empty pending list; this should be cleaned up


From williamt  Mon Aug 18 16:23:37 2003
From: williamt (William Tai)
Date: Mon, 18 Aug 2003 16:23:37 -0700
Subject: What's the difference between prism2.5 and prism3 and what version
	of hostap support prism3
Message-ID: <04d901c365df$c097c4b0$e6f0c53f@williamt>

Hi All:


         When does hostsp start to support prism3 and
what's the difference between prism2.5 and prism3?

Thanx



From proski  Mon Aug 18 16:43:12 2003
From: proski (Pavel Roskin)
Date: Mon, 18 Aug 2003 19:43:12 -0400 (EDT)
Subject: What's the difference between prism2.5 and prism3 and what
 version of hostap support prism3
In-Reply-To: <04d901c365df$c097c4b0$e6f0c53f@williamt>
References: <04d901c365df$c097c4b0$e6f0c53f@williamt>
Message-ID: <Pine.LNX.4.56.0308181934170.26451@marabou.research.att.com>

On Mon, 18 Aug 2003, William Tai wrote:

>          When does hostsp start to support prism3 and
> what's the difference between prism2.5 and prism3?

Why do you think that Prism 3 is not supported?  Can you give the source
that led you to this conclusion?  I don't have a Prism 3 card, but I
believe it should work with the existing code.  I remember a report that
linux-wlan-ng worked with a Prism 3 card without any changes.

As for the differences, look for your self at
http://www.intersil.com/cda/application/0,1239,2,00.html

Unfortunately, I don't see any side-by-side comparison.  You may want to
compare specifications of the integrates Baseband/MAC chips - they
interact with the driver software.

-- 
Regards,
Pavel Roskin



From williamt  Mon Aug 18 17:03:05 2003
From: williamt (William Tai)
Date: Mon, 18 Aug 2003 17:03:05 -0700
Subject: What's the difference between prism2.5 and prism3 and what
	version of hostap support prism3
References: <04d901c365df$c097c4b0$e6f0c53f@williamt>
	<Pine.LNX.4.56.0308181934170.26451@marabou.research.att.com>
Message-ID: <04ee01c365e5$43ab6cd0$e6f0c53f@williamt>


----- Original Message ----- 
From: "Pavel Roskin" <proski at gnu.org>
To: "William Tai" <williamt at arescom.com>
Cc: <hostap at shmoo.com>
Sent: Monday, August 18, 2003 4:43 PM
Subject: Re: What's the difference between prism2.5 and prism3 and what
version of hostap support prism3


> On Mon, 18 Aug 2003, William Tai wrote:
>
> >          When does hostsp start to support prism3 and
> > what's the difference between prism2.5 and prism3?
>
> Why do you think that Prism 3 is not supported?  Can you give the source
> that led you to this conclusion?  I don't have a Prism 3 card, but I
> believe it should work with the existing code.  I remember a report that
> linux-wlan-ng worked with a Prism 3 card without any changes.
>

>From readme document
Introduction
============

This is a Linux driver for wireless LAN cards based on Intersil's
Prism2/2.5 chipset.
So I am confused.
My hostap driver was download at April.
I do not know whether my driver support prism3 or not.






> As for the differences, look for your self at
> http://www.intersil.com/cda/application/0,1239,2,00.html
>
> Unfortunately, I don't see any side-by-side comparison.  You may want to
> compare specifications of the integrates Baseband/MAC chips - they
> interact with the driver software.
>
> -- 
> Regards,
> Pavel Roskin
>




From proski  Mon Aug 18 17:02:26 2003
From: proski (Pavel Roskin)
Date: Mon, 18 Aug 2003 20:02:26 -0400 (EDT)
Subject: What's the difference between prism2.5 and prism3 and what
 version of hostap support prism3
In-Reply-To: <04ee01c365e5$43ab6cd0$e6f0c53f@williamt>
References: <04d901c365df$c097c4b0$e6f0c53f@williamt>
	<Pine.LNX.4.56.0308181934170.26451@marabou.research.att.com>
	<04ee01c365e5$43ab6cd0$e6f0c53f@williamt>
Message-ID: <Pine.LNX.4.56.0308181959090.26744@marabou.research.att.com>

On Mon, 18 Aug 2003, William Tai wrote:

> This is a Linux driver for wireless LAN cards based on Intersil's
> Prism2/2.5 chipset.
> So I am confused.
> My hostap driver was download at April.
> I do not know whether my driver support prism3 or not.

Indeed, it still says so.  Perhaps there haven't been many Prism 3 devices
around to add it to the documentation.

If you have any problems with Prism 3 device, please report them.  If it's
a PCI card, you may want to test the CVS version, which has the PCI ID
for Prism 3 cards.

If you have no problems and everything works, please report it as well
(with HostAP version and the card name, please), and the documentation
will be fixed.

-- 
Regards,
Pavel Roskin



From williamt  Mon Aug 18 17:33:20 2003
From: williamt (William Tai)
Date: Mon, 18 Aug 2003 17:33:20 -0700
Subject: What's the difference between prism2.5 and prism3 and what
	version of hostap support prism3
References: <04d901c365df$c097c4b0$e6f0c53f@williamt>
	<Pine.LNX.4.56.0308181934170.26451@marabou.research.att.com>
	<04ee01c365e5$43ab6cd0$e6f0c53f@williamt>
	<Pine.LNX.4.56.0308181959090.26744@marabou.research.att.com>
Message-ID: <050001c365e9$7d6481b0$e6f0c53f@williamt>


----- Original Message ----- 
From: "Pavel Roskin" <proski at gnu.org>
To: "William Tai" <williamt at arescom.com>
Cc: <hostap at shmoo.com>
Sent: Monday, August 18, 2003 5:02 PM
Subject: Re: What's the difference between prism2.5 and prism3 and what
version of hostap support prism3


> On Mon, 18 Aug 2003, William Tai wrote:
>
> > This is a Linux driver for wireless LAN cards based on Intersil's
> > Prism2/2.5 chipset.
> > So I am confused.
> > My hostap driver was download at April.
> > I do not know whether my driver support prism3 or not.
>
> Indeed, it still says so.  Perhaps there haven't been many Prism 3 devices
> around to add it to the documentation.
>
> If you have any problems with Prism 3 device, please report them.  If it's
> a PCI card, you may want to test the CVS version, which has the PCI ID
> for Prism 3 cards.
>

My driver is downloaded around April.
I insert the Prism3 card.
It seems not working well.
Client can not associated with my AP.
BTW, could you tell me when hostap start to support prism3?


Very Thanx

> If you have no problems and everything works, please report it as well
> (with HostAP version and the card name, please), and the documentation
> will be fixed.
>
> -- 
> Regards,
> Pavel Roskin
>




From jkmaline  Mon Aug 18 19:12:56 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Aug 2003 19:12:56 -0700
Subject: What's the difference between prism2.5 and prism3 and what
	version of hostap support prism3
In-Reply-To: <050001c365e9$7d6481b0$e6f0c53f@williamt>
References: <04d901c365df$c097c4b0$e6f0c53f@williamt>
	<Pine.LNX.4.56.0308181934170.26451@marabou.research.att.com>
	<04ee01c365e5$43ab6cd0$e6f0c53f@williamt>
	<Pine.LNX.4.56.0308181959090.26744@marabou.research.att.com>
	<050001c365e9$7d6481b0$e6f0c53f@williamt>
Message-ID: <20030819021256.GB3359@jm.kir.nu>

On Mon, Aug 18, 2003 at 05:33:20PM -0700, William Tai wrote:

> > On Mon, 18 Aug 2003, William Tai wrote:
> > > This is a Linux driver for wireless LAN cards based on Intersil's
> > > Prism2/2.5 chipset.

Yes, that was written when Prism3 did not yet exist and has not been
updated since ;-).

> > > I do not know whether my driver support prism3 or not.

Host AP driver has always supported Prism3. There are no major
differences between Prism2, Prism2.5, and Prism3 as far as the driver is
concerned.

> My driver is downloaded around April.
> I insert the Prism3 card.
> It seems not working well.
> Client can not associated with my AP.

Which firmware version are you using? If it happens to be STA f/w
v1.4.2, you should note that it has a known issue of not working in Host
AP mode. If it is another version, please do give more details: test
latest CVS version, send 'dmesg' output of a client trying to associate
with it. In addition, include full description of the card you are using
(vendor, model, firmware versions, pci/plx/cs).

> BTW, could you tell me when hostap start to support prism3?

It already supports Prism3. I use Prism2, Prism2.5, and Prism3 cards
in my tests and they all work fine. I am not aware of any Prism3-related
issue in the driver. You need to give more details about the issues you
have seen in order to make it possible to figure out what is wrong.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug 18 19:21:30 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Aug 2003 19:21:30 -0700
Subject: Symbol/Nortel 4123 PCI Adapter - Port orinoco module to hosta p
In-Reply-To: <252E5192A5C2D311B24B00508B5D5CCCBD8220@slpms0.sel.de>
References: <252E5192A5C2D311B24B00508B5D5CCCBD8220@slpms0.sel.de>
Message-ID: <20030819022130.GC3359@jm.kir.nu>

On Mon, Aug 18, 2003 at 03:30:51PM +0200, ARLETH, DANIEL wrote:

> The ISP Router and AP1 are placed at the attic, accessible for everybody, so
> I bought a small cabinet to secure them. That's the reason why I bought the
> Nortel Card, because of its external antenna.
> 
> And now I want to associate the AP1 as a normal client to the AP2 (because
> there is no master mode driver for the Nortel card), but bridge the ISP
> router and the wlan anyway together. 

You cannot use a IEEE 802.11 device that operates as a client that is
associated to an AP ("Managed"/"Infra" mode) to implement layer2 bridge.
IEEE 802.11 standard frames do not allow the source MAC address be
changed in the frames sent by that device.

However, you do not need to use "Master" (AP) mode for bridging; you
could also use WDS links without normal AP functionality. This may even
work with Lucent/Orinoco-based cards. At least, I have been able to use
Host AP driver with Lucent WaveLAN card to send and receive standard WDS
frames ('iwconfig wlan0 mode Repeater' and then add WDS links with
iwpriv wds_add command). This does not require Host AP mode.

> The ISP Router masquerades all connections, because the internal net is
> 192.168.0.0 and I can't add static routes so I would have to masquerade on
> AP1, too. That may work, but hmm, I think there must be a better way. 

Why do you think that masquerading on AP1 would not be OK?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug 18 19:33:38 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Aug 2003 19:33:38 -0700
Subject: Hard lockup with XI-636
In-Reply-To: <3F408CA9.4060503@iprimus.com.au>
References: <3F408CA9.4060503@iprimus.com.au>
Message-ID: <20030819023338.GD3359@jm.kir.nu>

On Mon, Aug 18, 2003 at 06:22:01PM +1000, Mathew Burns wrote:

> I have a zcom (rebadged as skymaster here in australia) xi-626 pci card 
> working fine in ad-hoc mode with the oricono_pci module but would like 
> to use one of two identical boxes as a AP.
> 
> Whenever I issue "modprobe hostap_pci" the machine hard locks, with 
> nothing written to syslog or dmesg.
> The last line written by modprobe is "registered net device: wlan0"

Do you get any messages on text console if you first set logging level
to maximum (dmesg -n 8)? What kind of host system are you using (CPU? is
it SMP?)?

> Kernel 2.4.21 compiled myself with the wireless extention patches 
> applied as suggested.

Which compiler version did you use to compile the kernel? Did you
compile Host AP driver with the exact same compiler? Did you run 'make
clean' after applying any patches to the kernel (i.e., recompiled
everything)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug 18 19:40:18 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Aug 2003 19:40:18 -0700
Subject: HostAP Digest, Vol 4, Issue 33
In-Reply-To: <BAY1-F19Y1qClo8XoPN00028c13@hotmail.com>
References: <BAY1-F19Y1qClo8XoPN00028c13@hotmail.com>
Message-ID: <20030819024018.GE3359@jm.kir.nu>

On Mon, Aug 18, 2003 at 01:57:40PM +0000, Haidong Xia wrote:

> Can anyone explain to me how HostAP set up a default wep key ? Since I 
> don't have a hardware manual of prism2 card, I am a little confused, when I 
> read the code of WEP key setting under HostAP.

You don't need a hardware manual for this.. IEEE 802.11 standard might
be more useful ;-).

> The basic question is: When HostAP sets up a default wep key, a WinXP 
> client automatically detects this access point has a default wep key. How a 
> WinXP client know an Access Point has a WEP key, right after association?

Actually, it already knows it before association. The AP includes a
Privacy bit in the capability info field of the beacons.

> I am doing an experiment to allow both of clients using Wep key, or not 
> using wep key to get access to an Access point. But WinXP client keeps 
> saying there is a wep key, and just wants to use a Wep key, even I didn't 
> set up a key for it.

Yes, many WinXP clients do not really like the Privacy bit in the
beacons (or probe responses) if you are trying to use unencrypted
connection.

> Is there a way to set up a default wep key in HostAP, but WinXP client will 
> not detect it?  So that a user can configure the client freely with or with 
> WEP key?   Of course, at hostAP side, it can detect a
> frame is encrypted or not, and deal with it correspondingly.

This depends a bit on the client implementation. In other words, you
might get it working with some drivers, but not with all.. I don't
remember whether Prism2 changes the capability information contents
based on "exclude unencrypted" configuration. If it does, you try
setting up the WEP keys with 'open' option of the iwconfig (iwconfig
wlan0 key s:abcde open).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug 18 19:47:33 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Aug 2003 19:47:33 -0700
Subject: 2.6.0-test3 (and -test2)
In-Reply-To: <Pine.LNX.4.56.0308181507140.20845@marabou.research.att.com>
References: <000001c363e5$a6ac34b0$c7fda8c0@int.sbss.com.au>
	<20030816160435.GA3251@jm.kir.nu> <3F3EF801.4030101@bigpond.com>
	<Pine.LNX.4.56.0308181507140.20845@marabou.research.att.com>
Message-ID: <20030819024733.GF3359@jm.kir.nu>

On Mon, Aug 18, 2003 at 03:10:26PM -0400, Pavel Roskin wrote:

> Yes, it's time to clean up references to hostap_crypt module and
> hostap_crypt.c as the source for that module.  The patch is attached.

Thanks! I did not apply the Makefile changes of removing already
commented out parts (I might still want to test them), but everything
else is now in CVS.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug 18 19:56:00 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Aug 2003 19:56:00 -0700
Subject: SMP report
In-Reply-To: <3F3F57EF.7020002@bigpond.com>
References: <3F3F57EF.7020002@bigpond.com>
Message-ID: <20030819025600.GG3359@jm.kir.nu>

On Sun, Aug 17, 2003 at 08:24:47PM +1000, James Harper wrote:

> I'm running 2.6.0-test3 with the latest cvs version of hostap on an SMP 
> system and it appears much more stable than previous versions. I just 
> tried a flood ping for a few minutes and the only error I got was:
> 
> Aug 17 20:19:17 portal kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
> busy for 1 usec

I'm not fully sure about what caused this, but with busy waiting for the
command reg, this should be fine.

> Aug 17 20:20:53 portal kernel: wlan0: detected fid change (try=0, 
> reg=0044): 0166 a5a4 0166
> Aug 17 20:20:59 portal kernel: wlan0: detected fid change (try=0, 
> reg=0040): 0000 03d6 03d6
> 
> which probably isn't good but previously I would be getting card resets 
> and/or crashes etc all over the place.

That's good, well, at least useful, to know. So, there are at least two
different SMP hosts that report changing fid registers and I haven't
heard of a single one without this "feature".. This looks like a
hardware bug to me since those registers should not really change its
value even if something is being read from the card (or written to it)
at the same time; as long as the RX/TX/Info event has not been ACKed
(and it will be ACKed only after reading those fid registers).

In other words, I apparently do need to leave that workaround code in
the driver, although probably with ifdefs for including it only to
hostap_pci and only when kernel is compiled with SMP support..

Getting those fid reads returning proper values will certainly remove
quite a few hw_resets and will thus help with the stability. The other
issue, i.e., system lockup on hw_reset, may however still exist. I
actually have couple of patches that could be tested on top of 0.0.4
release so that we could try to find a way to avoid the crash. If
someone with an SMP system using hostap_pci is willing to test these,
please let me know and I'll send the patches. Please note that testing
these will most probably end up crashing your system number of times..

-- 
Jouni Malinen                                            PGP id EFC895FA



From DANIEL.ARLETH  Tue Aug 19 02:13:23 2003
From: DANIEL.ARLETH (ARLETH, DANIEL)
Date: Tue, 19 Aug 2003 11:13:23 +0200
Subject: Symbol/Nortel 4123 PCI Adapter - Port orinoco module to hosta p
Message-ID: <252E5192A5C2D311B24B00508B5D5CCCBD8228@slpms0.sel.de>

> -----Urspr?ngliche Nachricht-----
> Von: Jouni Malinen [mailto:jkmaline at cc.hut.fi] 
> Gesendet: Dienstag, 19. August 2003 04:22
> An: hostap at shmoo.com
> Betreff: Re: Symbol/Nortel 4123 PCI Adapter - Port orinoco 
> module to hosta p

> You cannot use a IEEE 802.11 device that operates as a client that is
> associated to an AP ("Managed"/"Infra" mode) to implement 
> layer2 bridge.
> IEEE 802.11 standard frames do not allow the source MAC address be
> changed in the frames sent by that device.

Ok, I didn't know that.
 
> However, you do not need to use "Master" (AP) mode for bridging; you
> could also use WDS links without normal AP functionality. 
> This may even
> work with Lucent/Orinoco-based cards. At least, I have been 
> able to use
> Host AP driver with Lucent WaveLAN card to send and receive 
> standard WDS
> frames ('iwconfig wlan0 mode Repeater' and then add WDS links with
> iwpriv wds_add command). This does not require Host AP mode.

That sounds like the best solution, but

1. I've got a Nortel/Symbol Card. I read about reports people use this card
succesful in managed mode, but nothing about repeater mode. Do you think
this will work.

2. This leads me to the problem, why I actually posted to this list. My Card
is in a PCI adapter which is NOT with a PLX chip. 

Here again the belonging part of my first post:

>> I want to run the Nortel PCI Card (4123) as a member of a bridge(, but
the
>> symbol support in the Orinoco driver seems not to be ready for this).
>> I tried with the module available at
>> http://www.traum404.de/download/index.html
>> <http://www.traum404.de/download/index.html> .

>> As far as I can see (with my very basic C knowledge) this module consists
of
>> only a few lines of code to initial the pcmcia card, and then let the
>> Orinoco driver do its work.
>> The only thing which has to be changed in the Orinoco driver are two
lines
>> of code in Orinoco.c and Orinoco.h.

>> void hermes_struct_init(hermes_t *hw, ulong address,
>> 			int io_space, int reg_spacing)
>> {
>> 	hw->iobase = address;
>> >	hw->iobase1 = 0;
>> >	hw->iobase2 = 0;
>>        	hw->io_space = io_space;
>> 	hw->reg_spacing = reg_spacing;
>> 	hw->inten = 0x0;

>> So my hope is, this could be as easy for the hostap driver.

>> Please don't understand me wrong! I don't ask you for writing a driver
for
>> me! But I can't do it and I hope to hear from you either 
>> "Forget it! The hostap has got nothing in common with the Orinoco driver,
so
>> the Nortel_pci module is useless for the hostap driver" 
>> or
>> "No problem! Just ask a friend with C knowledge to have a look at it and
>> change ..........."

(End of quote)

It would be very nice, if anybody could give me an assessment for this.

> Why do you think that masquerading on AP1 would not be OK?
> 

Masquerading ervery connection 2 times is just needless and I worry it will
fail with some  protocols like ftp or messengers. Ok, I know no concretely
reason, ist just a fear.

Daniel


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



From roniuch  Tue Aug 19 02:24:02 2003
From: roniuch (=?ISO-8859-2?Q?Damian_Gaw=EAda?=)
Date: Tue, 19 Aug 2003 11:24:02 +0200
Subject: Hostap and Realtek 8180L
Message-ID: <3F41ECB2.2090200@stevenet.eu.org>

Hi!

Is there a plan to support Realtek 8180 chipset in the nearest future? 
Cards using this chip are inexpensive and their transmitting power is, 
reportedly, higher than of any prism based hardware.

--
Damian Gaweda




From imp  Tue Aug 19 04:04:40 2003
From: imp (imp)
Date: Tue, 19 Aug 2003 20:04:40 +0900
Subject: wlan0: hfa384x_cmd: entry still in list? 
Message-ID: <004101c36641$b063e530$d200a8c0@Snoopy>

Dear all

I have some problem using hostap, Please give your advice for me..

I run lastest CVS hostap and daemon, and I make some my own shell script which called automatically after hostapd start
and setting some wireless paramenter for myself.

the script is 

+ACMAIQ-/bin/sh
iwconfig wlan0 mode Master
iwconfig wlan0 nick +ACI-My Access Point+ACI-
iwconfig wlan0 channel 6
iwconfig wlan0 key off
iwconfig wlan0 rts 2347
iwconfig wlan0 frag 2346
iwconfig wlan0 rate auto
iwpriv wlan0 prism2+AF8-param 3 100
iwpriv wlan0 prism2+AF8-param 11 3
iwpriv wlan0 prism2+AF8-param 2 0
iwpriv wlan0 prism2+AF8-param 10 1
iwpriv wlan0 prism2+AF8-param 30 0
iwconfig wlan0 txpower 40
iwconfig wlan0 essid +ACI-imptest+ACI-

when I restart system include hostap wlan.. It was alway success, if there are no client STA which previous associated with my hostap AP.
(I mean remove STA wireless card from notebook. I try several wlan card from different vendor) 

But, after association from STA to AP then remain wireless card in notebook, and turn off the hostap(then the sta wireless card app scan the previous hostap), then, turn on my hostap. then I always meet flowing error while my system run above script...
 
+AH4- +ACM- wlan0: hfa384x+AF8-cmd: entry still in list? (entry+AD0-c016b820, type+AD0-0, res+AD0-0)
wlan0: hfa384x+AF8-cmd: command was not completed (res+AD0-0, entry+AD0-c016b820, type+AD0-0, cmd+AD0-0x0121, param0+AD0-0xfc33, EVSTAT+AD0-0000 INTEN+AD0-e1a0a09f)
wlan0: hfa384x+AF8-set+AF8-rid: CMDCODE+AF8-ACCESS+AF8-WRITE failed (res+AD0--110, rid+AD0-fc33, len+AD0-2)
wlan0: hfa384x+AF8-cmd: entry still in list? (entry+AD0-c016b820, type+AD0-0, res+AD0-0)
wlan0: hfa384x+AF8-cmd: command was not completed (res+AD0-0, entry+AD0-c016b820, type+AD0-0, cmd+AD0-0x0121, param0+AD0-0xfc10, EVSTAT+AD0-0000 INTEN+AD0-e1a0a09f)
wlan0: hfa384x+AF8-set+AF8-rid: CMDCODE+AF8-ACCESS+AF8-WRITE failed (res+AD0--110, rid+AD0-fc10, len+AD0-2)
wlan0: hfa384x+AF8-cmd: entry still in list? (entry+AD0-c016b820, type+AD0-0, res+AD0-0)
wlan0: hfa384x+AF8-cmd: command was not completed (res+AD0-0, entry+AD0-c016b820, type+AD0-0, cmd+AD0-0x0121, param0+AD0-0xfc43, EVSTAT+AD0-0000 INTEN+AD0-e1a0a09f)
wlan0: hfa384x+AF8-set+AF8-rid: CMDCODE+AF8-ACCESS+AF8-WRITE failed (res+AD0--110, rid+AD0-fc43, len+AD0-2)
wlan0: cnfEnhSecurity requires STA f/w 1.6.3 or newer
wlan0: cnfEnhSecurity set as 0
wlan0: hfa384x+AF8-cmd: entry still in list? (entry+AD0-c016b820, type+AD0-0, res+AD0-0)
wlan0: hfa384x+AF8-cmd: command was not completed (res+AD0-0, entry+AD0-c016b820, type+AD0-0, cmd+AD0-0x0021, param0+AD0-0xfdc6, EVSTAT+AD0-0000 INTEN+AD0-e1a0a09f)
wlan0: hfa384x+AF8-get+AF8-rid: CMDCODE+AF8-ACCESS failed (res+AD0--110, rid+AD0-fdc6, len+AD0-12)
wlan0: hfa384x+AF8-cmd: cmd+AF8-queue full
wlan0: hfa384x+AF8-cmd: cmd+AF8-queue full
wlan0: hfa384x+AF8-cmd: cmd+AF8-queue full
wlan0: hfa384x+AF8-set+AF8-rid: CMDCODE+AF8-ACCESS+AF8-WRITE failed (res+AD0--1, rid+AD0-fc02, len+AD0-34)




From a.boegl  Tue Aug 19 04:23:57 2003
From: a.boegl (=?GB2312?B?QWxleGFuZGVyIEJvImds?=)
Date: Tue, 19 Aug 2003 13:23:57 +0200
Subject: Error message> wlan0: SW TICK stuck?
In-Reply-To: <20030710171719.GA31992@jm.kir.nu>
References: <004e01c34147$b69d6e40$0965a8c0@msramek>
	<20030710171719.GA31992@jm.kir.nu>
Message-ID: <3F4208CD.3070900@amnet.at>

Jouni Malinen schrieb:

>On Thu, Jul 03, 2003 at 11:44:33AM +0200, Milos Sramek wrote:
>
>  
>
>>What does this error message mean ??  and why it's egressing ??
>>
>>wlan0: SW TICK stuck? bits=0x0 EvStat=8001 IntEn=e018
>>
>>Linux repeatly this message to console and is total "dead".
>>    
>>
>
>Host AP driver uses a software watchdog to detect busy looping IRQ
>events. That message should be displayed every two seconds if most of
>the kernel gets stuck (deadlock etc.) but hw interrupts are still
>working. Did you happen to catch any messages just before the first 'SW
>TICK stuck' message?
>
>  
>
Hi!

I have a simular problem, but it happends as soon I access the network.


The messages are folloing a "Unable to handle NULL pointer deference"
Kernel panic.

It seems that my problem is not hostap related cause I have the kernel
panic without the
hostap too, only without the SW TICK stuck messages every 2 secs.

I hope this can even help.










From askatti  Tue Aug 19 04:34:55 2003
From: askatti (Anand S. Katti)
Date: Tue, 19 Aug 2003 17:04:55 +0530 (IST)
Subject: 802.11 mathematical model
In-Reply-To: <20030819110447.C1760EB9A@mail.iocaine.com>
Message-ID: <Pine.LNX.4.44.0308191701070.14753-100000@ece.iisc.ernet.in>

Dear sir,

Im sorry if this post is not relevant to the current list. But I need the 
information on 802.11 in mathematical way.

Like I want to know the mathematical relation between RECEIVER 
SENSITIVITY, RANGE, MTBF, RATE, S/N RATIO, Txpower, Rxpower, etc..

Could anyone suggest me any link or books to get through this?
Well i know the definition of these above terms but if want to do 
programing, then i shudbe knowing the mathematical relation between them.

I hope you have the answer.

-- 
--------------.				
With Regards,   
Anand S. Katti




From Shripad_N  Tue Aug 19 07:23:55 2003
From: Shripad_N (Shripad N)
Date: Tue, 19 Aug 2003 19:53:55 +0530
Subject: Shutdown wlan interface
Message-ID: <E125980C421DFD4DA0B80D55DB1EDA5801421E5B@mtv01ex01.mindtree.com>

hi,

Is there any way to shutdown the wlan interface, ie stop consuming power, by
issuing a command.

iwconfig does not have a "down" option.

I dont want to plug in and plug out the card for that purpose. I tried
ifconfig wlan0 down

But the activity indicator of the card still is blinking.

please help,
regards
Shripad


DISCLAIMER:
This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Private Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return  e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited.  Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.



From gregfjohnson  Tue Aug 19 08:10:36 2003
From: gregfjohnson (Greg Johnson)
Date: Tue, 19 Aug 2003 08:10:36 -0700 (PDT)
Subject: prism cards
Message-ID: <20030819151036.37487.qmail@web14204.mail.yahoo.com>

Hello Vicente,

  I have also had a terrible time obtaining prism-based wireless cards.
The best I could come up with was to troll ebay.com looking for them.

  I use D-Link DWL-520 cards, which work great.  But, the Prism-based
versions are no longer available.  Note:  the DWL-520+ are NOT Prism-based
and will not work with hostap as far as I know.  Also, there are something
like three variants of the DWL-520 card, and the last one is not Prism-based
either.  The only way to tell on ebay is to closely examine the picture of
the card.

  Here is a URL for a Prism-based DWL-520 on ebay:

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3041951026&category=45001

  Here is a URL for a non-Prism-based DWL-520 on ebay that will not work
with hostap:

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3041508175&category=20321

  (I know from experience:  I am now the proud owner of one of the latter :-(.)

  If the picture of the card has a large blue and white component on it, then
it is a Prism-based hostap-compatible card.  If the picture has only small
black components, then it is not Prism-based and is not hostap-compatible.

  It seems to me that the disappearance of Prism-based cards represents a
threat to the whole hostap project.  The hostap project is one of the most
wonderful things I've found on the net for a while (THANKS JOUNI especially
and all contributors!!).

  What (if anything) can be done to encourage the continued viability of this
great project by protecting the availability of the hardware required for it?

Thanks,

Greg Johnson

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com



From david.goodenough  Tue Aug 19 08:21:11 2003
From: david.goodenough (David Goodenough)
Date: Tue, 19 Aug 2003 16:21:11 +0100
Subject: prism cards
In-Reply-To: <20030819151036.37487.qmail@web14204.mail.yahoo.com>
References: <20030819151036.37487.qmail@web14204.mail.yahoo.com>
Message-ID: <200308191621.12433.david.goodenough@btconnect.com>

On Tuesday 19 August 2003 16:10, Greg Johnson wrote:
> Hello Vicente,
>
>   I have also had a terrible time obtaining prism-based wireless cards.
> The best I could come up with was to troll ebay.com looking for them.
>
>   I use D-Link DWL-520 cards, which work great.  But, the Prism-based
> versions are no longer available.  Note:  the DWL-520+ are NOT Prism-based
> and will not work with hostap as far as I know.  Also, there are something
> like three variants of the DWL-520 card, and the last one is not
> Prism-based either.  The only way to tell on ebay is to closely examine the
> picture of the card.
>
>   Here is a URL for a Prism-based DWL-520 on ebay:
>
> http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3041951026&category=4500
>1
>
>   Here is a URL for a non-Prism-based DWL-520 on ebay that will not work
> with hostap:
>
> http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3041508175&category=2032
>1
>
>   (I know from experience:  I am now the proud owner of one of the latter
> :-(.)
>
>   If the picture of the card has a large blue and white component on it,
> then it is a Prism-based hostap-compatible card.  If the picture has only
> small black components, then it is not Prism-based and is not
> hostap-compatible.
>
>   It seems to me that the disappearance of Prism-based cards represents a
> threat to the whole hostap project.  The hostap project is one of the most
> wonderful things I've found on the net for a while (THANKS JOUNI especially
> and all contributors!!).
>
>   What (if anything) can be done to encourage the continued viability of
> this great project by protecting the availability of the hardware required
> for it?
>
> Thanks,
>
> Greg Johnson
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

You could try the Senao cards.  They seem to produce nothing but Prism
based cards (at least for 11b, their 11g cards are Aries based it would 
seem, but as far as I understand they are not in production yet).

David




From f6hqz  Tue Aug 19 10:25:44 2003
From: f6hqz (Francois BERGERET)
Date: Tue, 19 Aug 2003 19:25:44 +0200
Subject: prism cards
In-Reply-To: <20030819151036.37487.qmail@web14204.mail.yahoo.com>
Message-ID: <LEEMLOMCOLGDFKOEHKDPCENIDNAA.f6hqz@easyconnect.fr>

Hi friends,

I am using Micronet cards from Taiwan in a Soekris embeded PC running Bering with hostap, for HAM radio hobby. I have two different
cards : SP905V2 and SP905BDV2.

They are Prism 2.5 based.

All twice are from Z-com manufacturer instead :
- SP905V2 = XI-300B
- SP905BDV2 = XI-325H

They have two MMCX connectors for external antennas but are provided with a small slim antenna for laptop PC.

The best one is the SP905BDV2/XI-325H regarding ouput power and (mainly) its great RX sensitivity against competitors.

I leave in France, and it is possible to buy them here, from the Micronet importer at @ 78 EURO for the SP905BDV2. They have a lot
of wireless equipments...

I know but not have a SP906BA with Intersil chipset too but in PCI format.

GES (Generale Electronique Service)
Phone +33 1 64.41.78.88
Fax   +33 1 60.63.24.85
VoIP phoneH.323 callto:80.13.8.11
wireless at ges.fr (but seems to be out of service this days, may be on vacation).

Best Regards,
Francois BERGERET,
France.

> -----Message d'origine-----
> De : hostap-bounces at shmoo.com [mailto:hostap-bounces at shmoo.com]De la
> part de Greg Johnson
> Envoye : mardi 19 aout 2003 17:11
> A : hostap at shmoo.com; vicente.paredes at gruein.com
> Objet : prism cards
>
>
> Hello Vicente,
>
>   I have also had a terrible time obtaining prism-based wireless cards.
> The best I could come up with was to troll ebay.com looking for them.
>
>   I use D-Link DWL-520 cards, which work great.  But, the Prism-based
> versions are no longer available.  Note:  the DWL-520+ are NOT Prism-based
> and will not work with hostap as far as I know.  Also, there are something
> like three variants of the DWL-520 card, and the last one is not Prism-based
> either.  The only way to tell on ebay is to closely examine the picture of
> the card.
>
>   Here is a URL for a Prism-based DWL-520 on ebay:
>
> http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3041951026&category=45001
>
>   Here is a URL for a non-Prism-based DWL-520 on ebay that will not work
> with hostap:
>
> http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3041508175&category=20321
>
>   (I know from experience:  I am now the proud owner of one of the latter :-(.)
>
>   If the picture of the card has a large blue and white component on it, then
> it is a Prism-based hostap-compatible card.  If the picture has only small
> black components, then it is not Prism-based and is not hostap-compatible.
>
>   It seems to me that the disappearance of Prism-based cards represents a
> threat to the whole hostap project.  The hostap project is one of the most
> wonderful things I've found on the net for a while (THANKS JOUNI especially
> and all contributors!!).
>
>   What (if anything) can be done to encourage the continued viability of this
> great project by protecting the availability of the hardware required for it?
>
> Thanks,
>
> Greg Johnson
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From chhabra  Tue Aug 19 11:37:58 2003
From: chhabra (Madhusudan Singh)
Date: Tue, 19 Aug 2003 14:37:58 -0400
Subject: prism cards
In-Reply-To: <20030819174503.87344.qmail@web14203.mail.yahoo.com>
References: <20030819174503.87344.qmail@web14203.mail.yahoo.com>
Message-ID: <3F426E86.2030607@eecs.umich.edu>

I use Netgear MA401 (PCMCIA) and MA311(PCI) for my home wireless LAN. 
Both are hostap compatible. I do not know which stores have it. I bought 
mine online at buy.com

On how to do it, I wrote down instrucions at :

http://www.eecs.umich.edu/~chhabra/netgearwireless.html

I have not yet added the instructions for the Access Point, but they 
will soon be up.


Greg Johnson wrote:

>--- Madhusudan Singh <chhabra at eecs.umich.edu> wrote:
>  
>
>>Have you looked at Netgear cards ?
>>
>>
>>    
>>
>
>Hello Madhusudan,
>
>  I have not looked at Netgear cards.  Is there a hostap-compatible
>Netgear PCI card and a Netgear PCMCIA card that is currently available
>from Fry's, Best Buy, Circuit City etc.?
>
>Thanks,
>
>Greg Johnson
>  
>




From sachin  Tue Aug 19 07:40:41 2003
From: sachin (Sachin Ganu)
Date: Tue, 19 Aug 2003 10:40:41 -0400 (EDT)
Subject: Shutdown wlan interface
In-Reply-To: <E125980C421DFD4DA0B80D55DB1EDA5801421E5B@mtv01ex01.mindtree.com>
Message-ID: <Pine.GSO.4.05.10308191039260.14424-100000@liman1a>

If you dont want to use the card, you could use "cardctl eject 0" to
"eject" it (without actually pulling it out)

to restart the card, you use "cardctl insert 0"

Hope that helps,
Sachin

-----------------------------------------------------------
Sachin Ganu
Graduate Research Assistant
WINLAB, Rutgers University
73 Brett Rd, Piscataway NJ 08854

On Tue, 19 Aug 2003, Shripad N wrote:

> hi,
> 
> Is there any way to shutdown the wlan interface, ie stop consuming power, by
> issuing a command.
> 
> iwconfig does not have a "down" option.
> 
> I dont want to plug in and plug out the card for that purpose. I tried
> ifconfig wlan0 down
> 
> But the activity indicator of the card still is blinking.
> 
> please help,
> regards
> Shripad
> 
> 
> DISCLAIMER:
> This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Private Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return  e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited.  Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 
> 




From sleibt  Tue Aug 19 12:57:03 2003
From: sleibt (SLeiBt)
Date: Tue, 19 Aug 2003 21:57:03 +0200
Subject: prism cards
In-Reply-To: <LEEMLOMCOLGDFKOEHKDPCENIDNAA.f6hqz@easyconnect.fr>
References: <LEEMLOMCOLGDFKOEHKDPCENIDNAA.f6hqz@easyconnect.fr>
Message-ID: <1061323022.649.10.camel@act.irishseb.dyndns.org>

Hi!

Just a bit of warning... Quite a few makes have "fairly silently"
switched from prism to TI chipset in their 11 products... In some cases,
the product number changed a bit, say xxxV2, but some made no change
whatsoever to the product name.

I can't recall which it was I was interested in (ended up buying
netgear) and looking at the windows driver I found that it was made of 2
completely different sets of files, with different PCI ids & such, but
the exact same displayed name.

But maybe even netgear moved to something else than prism since last
spring.

Regards,

Sebastien





From lsantos  Tue Aug 19 13:04:42 2003
From: lsantos (Leonardo Pereira Santos)
Date: Tue, 19 Aug 2003 17:04:42 -0300
Subject: prism cards
In-Reply-To: <3F426E86.2030607@eecs.umich.edu>
References: <20030819174503.87344.qmail@web14203.mail.yahoo.com>
	<3F426E86.2030607@eecs.umich.edu>
Message-ID: <200308191704.42958.lsantos@pd3.com.br>

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

I'm using a SWL-2100N, which is a Prism2-based card, and it works fine. IMHO 
Samsung won't de discontinuing this card as they did an AP based on it... 
Cheers!

On Tuesday 19 August 2003 15:37, Madhusudan Singh wrote:
> I use Netgear MA401 (PCMCIA) and MA311(PCI) for my home wireless LAN.
> Both are hostap compatible. I do not know which stores have it. I bought
> mine online at buy.com
>
> On how to do it, I wrote down instrucions at :
>
> http://www.eecs.umich.edu/~chhabra/netgearwireless.html
>
> I have not yet added the instructions for the Access Point, but they
> will soon be up.
>
> Greg Johnson wrote:
> >--- Madhusudan Singh <chhabra at eecs.umich.edu> wrote:
> >>Have you looked at Netgear cards ?
> >
> >Hello Madhusudan,
> >
> >  I have not looked at Netgear cards.  Is there a hostap-compatible
> >Netgear PCI card and a Netgear PCMCIA card that is currently available
> >from Fry's, Best Buy, Circuit City etc.?
> >
> >Thanks,
> >
> >Greg Johnson
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

- -- 
This is Linux country.
On a quiet night, you can hear Windows reboot.

Leonardo Pereira Santos
Engenheiro de Projetos
PD3 Tecnologia
av. Par? 330/202
(51) 3337 1237

Today Fortune tells us:
The 'A' is for content, the 'minus' is for not typing it.  Don't ever do
this to my eyes again.
		-- Professor Ronald Brady, Philosophy, Ramapo State College
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/QoLa8uAMCTjfaxIRAtBXAJ480lwdQhKi6iQfoIsNkg95uofHxgCgj4lf
srWUrB0/Wp9CoJu+u9/cZh8=
=a9f2
-----END PGP SIGNATURE-----




From aca  Tue Aug 19 15:24:25 2003
From: aca (Aleksandar Nikolic)
Date: Wed, 20 Aug 2003 00:24:25 +0200
Subject: Prism cards (Greg Johnson)
Message-ID: <002201c366a0$a743ba20$020a010a@alfa>

Well We have a very big problems to find prism based wlan cards and there I can send to you look of three revision of DWL 520 
      Revision A is prism based
      Revision B is prism based too
but Revision C1 is not prism based  http://www.dlink.com/products/support.asp?pid=42

And one more thing  100%same card is Sparklan WL360F as DWL520 revision A and it is prism based so go to http://www.sparklan.com/wl360f.htm

So We all hope that prism will live, but selling of intersil corp on 17.07.2003. well  all we have is hope

Best regards 
Aleksandar Nikolic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030820/e3668ad4/attachment.htm 


From jkmaline  Tue Aug 19 17:44:32 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 19 Aug 2003 17:44:32 -0700
Subject: Symbol/Nortel 4123 PCI Adapter - Port orinoco module to hosta p
In-Reply-To: <252E5192A5C2D311B24B00508B5D5CCCBD8228@slpms0.sel.de>
References: <252E5192A5C2D311B24B00508B5D5CCCBD8228@slpms0.sel.de>
Message-ID: <20030820004432.GA7117@jm.kir.nu>

On Tue, Aug 19, 2003 at 11:13:23AM +0200, ARLETH, DANIEL wrote:

> 1. I've got a Nortel/Symbol Card. I read about reports people use this card
> succesful in managed mode, but nothing about repeater mode. Do you think
> this will work.

I have never used or even seen that card and I do not know details about
what chipset and which version it uses. In other words, I do not have
enough information to guess whether it would work in repeater mode or
not. I have tested Repeater mode successfully with at least one
non-Prism2 card (Lucent) and I might have even tested it with
a PrismI/Symbol-based card (but I do not remember this for sure).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Aug 19 17:44:38 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 19 Aug 2003 17:44:38 -0700
Subject: Hostap and Realtek 8180L
In-Reply-To: <3F41ECB2.2090200@stevenet.eu.org>
References: <3F41ECB2.2090200@stevenet.eu.org>
Message-ID: <20030820004438.GB7117@jm.kir.nu>

On Tue, Aug 19, 2003 at 11:24:02AM +0200, Damian Gaw?da wrote:

> Is there a plan to support Realtek 8180 chipset in the nearest future? 
> Cards using this chip are inexpensive and their transmitting power is, 
> reportedly, higher than of any prism based hardware.

Do you know whether it has support for something like Host AP mode on
Prism2 (i.e., sending and receiving IEEE 802.11 management frames)? Is
technical documentation available for it to develop open source drivers?
If answer to these is "yes, it does support something like Host AP mode
and yes, documentation is available", it could well be worthwhile to add
support for it. If either of this is not the case, it will probably not
be supported in the near (or even distant) future.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Aug 19 17:44:42 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 19 Aug 2003 17:44:42 -0700
Subject: Shutdown wlan interface
In-Reply-To: <E125980C421DFD4DA0B80D55DB1EDA5801421E5B@mtv01ex01.mindtree.com>
References: <E125980C421DFD4DA0B80D55DB1EDA5801421E5B@mtv01ex01.mindtree.com>
Message-ID: <20030820004442.GC7117@jm.kir.nu>

On Tue, Aug 19, 2003 at 07:53:55PM +0530, Shripad N wrote:

> Is there any way to shutdown the wlan interface, ie stop consuming power, by
> issuing a command.

What kind of level of power saving would you need? Using cardctl to
eject the card is probably pretty close to removing the card (I would
assume it disconnects operating voltage from the card). Another option
would be to just disable most of the Prism2 operations with "iwpriv
wlan0 reset 3". This is supposed to drop power consumption a lot, but
not as much as cardctl eject. One benefit of just disabling the card is
in not having to reconfigure Linux netdev when the card is needed next
time ("iwpriv wlan0 reset 4"). However, if you anyway do all the setup
from pcmcia-cs scripts, cardctl eject & insert should work fine.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Aug 19 17:51:10 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 19 Aug 2003 17:51:10 -0700
Subject: prism cards
In-Reply-To: <20030819151036.37487.qmail@web14204.mail.yahoo.com>
References: <20030819151036.37487.qmail@web14204.mail.yahoo.com>
Message-ID: <20030820005110.GD7117@jm.kir.nu>

On Tue, Aug 19, 2003 at 08:10:36AM -0700, Greg Johnson wrote:

>   It seems to me that the disappearance of Prism-based cards represents a
> threat to the whole hostap project.

>   What (if anything) can be done to encourage the continued viability of this
> great project by protecting the availability of the hardware required for it?

I do not see disappearance of Prism2/2.5/3-based cards as a major threat
for something like Host AP project; it's more like a fact of life.. Old
hardware will be replaced at some point when newer, cheaper or
technically superior, products become available. Prism2/2.5/3 does not
have a superior (far from it) interface to the host system, there are
other cards with much better design. I would find it much more
productive to add support for other wlan chipsets than to artificially
keep alive aging technology.

-- 
Jouni Malinen                                            PGP id EFC895FA



From tanyh  Tue Aug 19 18:17:36 2003
From: tanyh (Yang-Hwee TAN)
Date: Wed, 20 Aug 2003 09:17:36 +0800
Subject: 802.11 mathematical model
In-Reply-To: <Pine.LNX.4.44.0308191701070.14753-100000@ece.iisc.ernet.in>
References: <20030819110447.C1760EB9A@mail.iocaine.com>
	<Pine.LNX.4.44.0308191701070.14753-100000@ece.iisc.ernet.in>
Message-ID: <20030820011735.GA2352@mail.bii.a-star.edu.sg>

hi,

u may wana try to get more of this info from IEEE standards,  
   http://ieee.org (zone: wireless)

to look for the standard spec for IEEE802.11 you may find the 
stuffs you mention below.

if u need actual specs of a product or brand that supports 802.11, 
you'll need to get it from the vendors.


cheers,
yanghwee

On 2003-08-19 17:04:55, Anand S. Katti <askatti at ece.iisc.ernet.in> wrote:

> Dear sir,
> 
> Im sorry if this post is not relevant to the current list. But I need the 
> information on 802.11 in mathematical way.
> 
> Like I want to know the mathematical relation between RECEIVER 
> SENSITIVITY, RANGE, MTBF, RATE, S/N RATIO, Txpower, Rxpower, etc..
> 
> Could anyone suggest me any link or books to get through this?
> Well i know the definition of these above terms but if want to do 
> programing, then i shudbe knowing the mathematical relation between them.
> 
> I hope you have the answer.
> 
> -- 
> --------------.				
> With Regards,   
> Anand S. Katti
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap



From vda  Wed Aug 20 07:03:32 2003
From: vda (Denis Vlasenko)
Date: Wed, 20 Aug 2003 17:03:32 +0300
Subject: SMP report
References: <3F3F57EF.7020002@bigpond.com> 
Message-ID: <200308201403.h7KE3XL20929@Port.imtp.ilyichevsk.odessa.ua>

On 18 August 2003 08:26, Denis Vlasenko wrote:
> On 17 August 2003 13:24, James Harper wrote:
> > I'm running 2.6.0-test3 with the latest cvs version of hostap on an SMP 
> > system and it appears much more stable than previous versions. I just 
> > tried a flood ping for a few minutes and the only error I got was:
> > 
> > Aug 17 20:19:17 portal kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
> > busy for 1 usec
> > Aug 17 20:20:53 portal kernel: wlan0: detected fid change (try=0, 
> > reg=0044): 0166 a5a4 0166
> > Aug 17 20:20:59 portal kernel: wlan0: detected fid change (try=0, 
> > reg=0040): 0000 03d6 03d6
> > 
> > which probably isn't good but previously I would be getting card resets 
> > and/or crashes etc all over the place.
> 
> Hmm I will hack together a patch because I believe
> those 'fid change' messages indicate a locking bug.
> Hopefully today.

This is it. Will try to catch SMP race condition.

The interface is rather simple: printk_trace()
prints events recorded in a circular buffer,
mark_in_trace("Some text") records event.
Event is (jiffies,cpu,text) triple.

Only compile tested.
--
vda

--- hostap_hw.c.orig	Wed Aug  6 05:50:00 2003
+++ hostap_hw.c	Wed Aug 20 16:59:46 2003
@@ -2199,6 +2199,43 @@
  * and will try to get the correct fid eventually. */
 #define EXTRA_FID_READ_TESTS
 
+#ifdef EXTRA_FID_READ_TESTS
+struct trace {
+        int cpu;
+        int jiffy;
+        const char *event;
+};
+static struct trace tracebuf[16];
+static int tracepos=0;
+spinlock_t tracelock = SPIN_LOCK_UNLOCKED;
+#define TRACESZ (sizeof(tracebuf)/sizeof(tracebuf[0]))
+
+static void printk_trace(void) {
+        int i,flags;
+        spin_lock_irqsave(&tracelock,flags);
+        i = tracepos;
+        do {
+                struct trace *p = tracebuf+i;
+                printk("time:%d cpu:%d event:%s\n", p->jiffy, p->cpu, p->event);
+                i = (i+1)%TRACESZ;
+        } while(i!=tracepos);
+        spin_unlock_irqrestore(&tracelock,flags);
+}
+
+static void mark_in_trace(const char* event) {
+        int flags;
+        struct trace *p;
+
+        spin_lock_irqsave(&tracelock,flags);
+        p = tracebuf+tracepos;
+        tracepos = (tracepos+1)%TRACESZ;
+        p->jiffy = jiffies;
+        p->cpu = smp_processor_id();
+        p->event = event;
+        spin_unlock_irqrestore(&tracelock,flags);
+}
+#endif
+
 static inline u16 prism2_read_fid_reg(struct net_device *dev, u16 reg)
 {
 #ifdef EXTRA_FID_READ_TESTS
@@ -2216,6 +2253,8 @@
 		printk(KERN_DEBUG "%s: detected fid change (try=%d, reg=%04x):"
 		       " %04x %04x %04x\n",
 		       dev->name, i, reg, val, val2, val3);
+		printk_trace();
+
 		if ((val == val2 || val == val3) && val != 0)
 			return val;
 		if (val2 == val3 && val2 != 0)
@@ -2957,6 +2996,10 @@
 	local_info_t *local = (local_info_t *) dev->priv;
 	int events = 0;
 	u16 ev;
+
+#ifdef EXTRA_FID_READ_TESTS
+        mark_in_trace("prism2_interrupt");
+#endif
 
 	prism2_io_debug_add(dev, PRISM2_IO_DEBUG_CMD_INTERRUPT, 0, 0);
 



From tanyh  Wed Aug 20 17:55:41 2003
From: tanyh (Yang-Hwee TAN)
Date: Thu, 21 Aug 2003 08:55:41 +0800
Subject: [lsantos@pd3.com.br: Re: 802.11 mathematical model]
Message-ID: <20030821005541.GA12068@mail.bii.a-star.edu.sg>

u've got the mail sent to the wrong person, leonardo.
anyway, here's the forwarded message for Anand S. Katti 
read on...


-Yanghwee

----- Forwarded message from Leonardo Pereira Santos <lsantos at pd3.com.br> -----

From: Leonardo Pereira Santos <lsantos at pd3.com.br>
To: Yang-Hwee TAN <tanyh at bii.a-star.edu.sg>
Subject: Re: 802.11 mathematical model
Date: Wed, 20 Aug 2003 18:49:46 -0300

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

	I think there's a propagation model for 802.11, like the reflective model 
used to place cell phone radio bases, but I have no idea where to get it. I 
assume you are talking about the phisics of it.
	And about what I learned in college about radio propagation, there's no easy 
relation between the TX power and rcv power, as this depends on the 
propagation model of radio of this frequencies and modulation schemes, like 
DSSS. Try Electrical Engineering books on radio propagation. ARRL might have 
something more practical on 802.11, so taking a look at the ARRL site for 
bibliography does not hurt.
	What you need these for? If you say exactly what you need, perhaps some is 
able to help you further. Cheers!

On Tuesday 19 August 2003 22:17, Yang-Hwee TAN wrote:
> hi,
>
> u may wana try to get more of this info from IEEE standards,
>    http://ieee.org (zone: wireless)
>
> to look for the standard spec for IEEE802.11 you may find the
> stuffs you mention below.
>
> if u need actual specs of a product or brand that supports 802.11,
> you'll need to get it from the vendors.
>
>
> cheers,
> yanghwee
>
> On 2003-08-19 17:04:55, Anand S. Katti <askatti at ece.iisc.ernet.in> wrote:
> > Dear sir,
> >
> > Im sorry if this post is not relevant to the current list. But I need the
> > information on 802.11 in mathematical way.
> >
> > Like I want to know the mathematical relation between RECEIVER
> > SENSITIVITY, RANGE, MTBF, RATE, S/N RATIO, Txpower, Rxpower, etc..
> >
> > Could anyone suggest me any link or books to get through this?
> > Well i know the definition of these above terms but if want to do
> > programing, then i shudbe knowing the mathematical relation between them.
> >
> > I hope you have the answer.
> >
> > --
> > --------------.
> > With Regards,
> > Anand S. Katti
> >
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

- -- 
This is Linux country.
On a quiet night, you can hear Windows reboot.

Leonardo Pereira Santos
Engenheiro de Projetos
PD3 Tecnologia
av. Par? 330/202
(51) 3337 1237

Today Fortune tells us:
You too can wear a nose mitten.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/Q+z68uAMCTjfaxIRAlNmAJ0T5zpSOw+dLtGaMZJs0Ym9nbSYKACaA27j
YIKBnaVS0kEDS9AxrV5pRFo=
=TFKR
-----END PGP SIGNATURE-----


----- End forwarded message -----



From imp  Wed Aug 20 20:04:17 2003
From: imp (imp)
Date: Thu, 21 Aug 2003 12:04:17 +0900
Subject: firmware problem.
Message-ID: <005e01c36790$ec439730$d200a8c0@Snoopy>

Dear all

I already issue the "commnd still in list" error..
and I found the situation why it occur !!

with PRISM 2.5 or 3.0 card up to 1.5.6 firmware work very well.  
I mean, If STA link hostap then hostap has been reset (turn off and the turn on), the STA still can re-association with that hostap.

but, using above 1.5.6, 1.6.3, 1.7.2, 1.7.4 for example, 
above same test always failed.. I thinks It's must be prism firmware bug.. isn't it ? 

Thanks for your attention, and welcome to any comment.

Bernard... 




From askatti  Thu Aug 21 02:26:49 2003
From: askatti (Anand S. Katti)
Date: Thu, 21 Aug 2003 14:56:49 +0530 (IST)
Subject: hostAP vs Dedicated AP
Message-ID: <Pine.LNX.4.44.0308211449370.19687-100000@ece.iisc.ernet.in>

Dear All,

With help generous suggestions of you all, i was able to successfully 
install the hostAP drivers on my RHL8.0	box.

Now I want to do a feature comparison of hostAP and any dedicated ACCESS 
POINT.

like, i have DLINK DWL-900AP+, I would be doing a comparison of the 
featuers  supported by this and (Desktop machine acting as access 
point with ) hostAP.

considered features are 
1. WEP or equivalent protocols supported.
2. capability to host multiple BSS names.
3. packet forwarding latencies.
4. range.
5. No. of hosts supported.
6. any other added advantages.

I wud be greatfukl to you all if any body tell me if you have already dont 
these conmparison or if there is any comparison table alredy in existence ?

Waiting for your respones.

Thankin you,


-- 
--------------.				
With Regards,   
Anand S. Katti




From andreaf  Thu Aug 21 08:18:40 2003
From: andreaf (Andrea G. Forte)
Date: Thu, 21 Aug 2003 11:18:40 -0400 (EDT)
Subject: HostAP source code?
Message-ID: <200308211518.h7LFIeDs003788@marta.cs.columbia.edu>

Any of you guys know where I can find the hostAP main source code and in what 
kind of modules the driver is divided?
Thank you to everyone.
Andrea




From andreaf  Thu Aug 21 11:25:27 2003
From: andreaf (Andrea G. Forte)
Date: Thu, 21 Aug 2003 14:25:27 -0400 (EDT)
Subject: HostAP source?
Message-ID: <200308211825.h7LIPRRe009392@cisalpino.cs.columbia.edu>

Any of you guys can tell me how to find the hostAP main Source code? Could you 
also tell me in what modules the HostAp is divided into?
Thanks,
Andrea




From lcaeiro  Thu Aug 21 17:03:25 2003
From: lcaeiro (caeiro)
Date: Fri, 22 Aug 2003 01:03:25 +0100
Subject: resource temporarily unavailable
Message-ID: <002401c36840$cf7f2dc0$6401a8c0@home>


Hi,

I'm trying to test some modifications I made in hostap driver to control de card tx buffer. I'm using a counter that is increased when prism2_transmit is called and decreased when prism2_tx_ev or prism2_tx_exc is called to know how many messages is in tx buffer card. To test this mechanism I'm using Mgen to generate some UDP traffic, but when I increase the flow tx rate I receive the following message:

            Udp socket:: SendTo( ) : send to ( ) error: resource temporarily unavailable              
 
What could be the cause of this messages? On driver (dmesg) I haven't any error or information message.

Thanks in advance

LC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030822/3524281f/attachment.htm 


From lcaeiro  Thu Aug 21 14:48:39 2003
From: lcaeiro (caeiro)
Date: Thu, 21 Aug 2003 22:48:39 +0100
Subject: resource temporarily unavailable
Message-ID: <003801c3682d$fbeebcd0$6401a8c0@home>

Hi,

I'm trying to test some modifications I made in hostap driver to control de card tx buffer. I'm using a counter that is increased when prism2_transmit is called and decreased when prism2_tx_ev or prism2_tx_exc is called to know how many messages is in tx buffer card. To test this mechanism I'm using Mgen to generate some UDP traffic, but when I increase the flow tx rate I receive the following message:

            Udp socket:: SendTo( ) : send to ( ) error: resource temporarily unavailable              

What could be the cause of this messages? On driver (dmesg) I haven't any error or information message.

Thanks in advance

LC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030821/a79e656e/attachment.htm 


From erich  Wed Aug 20 09:06:02 2003
From: erich (Erich Schubert)
Date: Wed, 20 Aug 2003 18:06:02 +0200
Subject: A couple of Problems with hostap and 802.1x
Message-ID: <20030820160602.GA7888@legolas.drinsama.de>

Hello,
i'm playing around with hostap and 802.1x, but i'm running into a few
problems.

What is working for me:
EAP-MD5 and EAP-TSL work with hostapd, freeradius and win2k client
AND with WEP disabled (i think i got fixed WEP working, too). I can't
get dynamic rekeying to work.

Well, that leads to my questions already. ;)
- xsupplicant: using the same certificates i can't get it to work. It
sends out the user name; on the machine running hostapd i do see the EAP
Challenge being sent out, on the client i don't see it coming in with
ethereal. I guess that is why xsupplicant doesn't reply. Any ideas?

- dynamic wep rekeying with EAP-TSL and win2k. Does this work? when i
enable rekeying in hostapd authentication fails:
wlan0: encryption configured, but RX frame not encrypted (SA=...)
i guess that is the reply frame.

Another question: When 802.11i is finished; are there people working on
implementing these for linux already? I think it's too difficult for me
(i have way too little knowledge at this layer) but i might need it.

Thanks.

Greetings,
Erich Schubert
-- 
    erich@(vitavonni.de|debian.org)    --    GPG Key ID: 4B3A135C    (o_
        The best things in life are free: Friendship and Love.       //\
  Es gibt wenig aufrichtige Freunde. Die Nachfrage ist auch gering.  V_/_
                    --- Marie von Ebner-Eschenbach



From Kashif.Bhatti  Tue Aug 19 23:16:24 2003
From: Kashif.Bhatti (Kashif Bhatti)
Date: Wed, 20 Aug 2003 16:16:24 +1000
Subject: HOST AP - A Question from a beginner
References: <Pine.LNX.4.44.0308191701070.14753-100000@ece.iisc.ernet.in>
Message-ID: <000b01c366e2$a0de9690$4262ea84@Hakidu>

Dear All,

I will be happy to get feed back from you all on my problem.

Currently I am doing research on wireless location. I use a simple setup
where I have an Orinoco Gold wireless LAN card and I use a sniffer
program like Orinico Client Manager to extract signal strength data
from a wireless access point (real access point). I use a laptop running
windows 2000. I only have access to one wireless access point and I was
 thinking if it will be possible to use HOST AP to create a number of mobile
acess points (thats what HOST AP does - right ?).

Question:
Suppose I install Linux as the operating system on another laptop
and use a prism chipset based card and install HOST AP, will it
be POSSIBLE for me to treat this mobile access point similar to
the wireless access point that I am already experimenting on.

PART A:
If I get HOST AP working on the laptop runing Linux, and I
use my laptop that has a Orinoco Gold wireless card. Can I extract
signal strength data using the Orinoco client manager from the mobile
access point created with HOST AP, as I do with the real wireless
access point ?

PART B:
Or will I have to use Wireless Tools to extract signal strength data
from the cleint laptop installed with Orinoco Gold wireless card, via
the laptop installed with HOST AP ?

As a summary, I want to use my windows 2000 laptop as a client machine
that extracts signal strength data using ORINOCO Client manager
from the  mobile access point using  installed with HOST AP.

All help will be apreciated,

Kind regrads,

Kashif






From Kashif.Bhatti  Wed Aug 20 00:00:09 2003
From: Kashif.Bhatti (Kashif Bhatti)
Date: Wed, 20 Aug 2003 17:00:09 +1000
Subject: Urgent Help Needed, please
Message-ID: <001301c366e8$b3bf2440$4262ea84@Hakidu>

Dear All,

My experimental setup consists of the following:

1 - Client laptop, Windows 2000, Orinoco Gold Wireless Card, Orinoco CLient
Manager (for extracting signal strength data from a wireless access point).

2 - A REAL wireless access point.

3 - Host AP laptop, Redhat 7.0, Prism based wireless card.

In my experiments I extract signal strenth with my client laptop from a real
wireless
access point, using Orinoco client manager software. The signal strength is
stored as
follows in a log file:

,,Start time      ,End time        ,BSSID       ,  Ch,  Sl,  Nl,  Snr, AP
Name
,,2003/07/26-21:06,2003/07/26-21:06,00022D22F930,   3, -51, -94,  43,  Mall

QUESTION:
I am thinking of using additional wireless access points and read about
mobile Host AP. If I get Host AP running on Linux (I hope), will it be
possible for me to extract signal strenth with my client laptop (windows
2000) from the beacons transmitted by the Host AP laptop ?

Regards,

Kashif




From askatti  Thu Aug 21 21:47:14 2003
From: askatti (Anand S. Katti)
Date: Fri, 22 Aug 2003 10:17:14 +0530 (IST)
Subject: power levels/ tx power levels
Message-ID: <Pine.LNX.4.44.0308221015110.14283-100000@ece.iisc.ernet.in>


Dear All,

Please answer the follwoing questions.

1. Does the hostAP support multiple essid?
2. Can we set the different tx power levels?
3. Is there any way i can set the above two mentioned pooints? i mean in 
the source code or so?

Eagerly waiting.

-- 
--------------.				
With Regards,   
Anand S. Katti




From vda  Thu Aug 21 22:55:52 2003
From: vda (Denis Vlasenko)
Date: Fri, 22 Aug 2003 08:55:52 +0300
Subject: how to make my AP work?
In-Reply-To: <000901c36586$25b1faf0$7bf7748c@gigabyteli>
References: <20030818120553.38EFFEA99@mail.iocaine.com>
	<000901c36586$25b1faf0$7bf7748c@gigabyteli>
Message-ID: <200308220556.h7M5tsL12004@Port.imtp.ilyichevsk.odessa.ua>

On 18 August 2003 15:42, ??? wrote:
> > HostAP doesn't work with tertiary firmware.  It makes secondary
> > firmware act as an access point.  If you want to use tertiary firmware,
> > use linux-wlan-ng.
> > Next time please report version of the software that gives you the
> > problem.  Also, a step-by-step explanation of what you are doing would be
> > helpful.  Relevant parts of the kernel log (as reported by dmesg) may be
> > useful as well.
> > -Regards,
> > -Pavel Roskin
> It's very sorry. I dont say clearly. I use Avaya's wireless PCMCIA card.
> so I use HermesAP-0.2. Now, I have installed heremesAP and made it work.
> Other PC's wireless device can connect to my wireless interface.
> My problem is how to make my AP like bridge, so that others connected to my
> AP can
> connected to Internet.
> Someone tells me to setup NAT or makes my wire card to be shared with all
> devices.
> However I am newbie on wireless and network. So I need more detail to do
> that.
> Hope people can teach me how to do that or where have information about
> that.

http://www.lartc.org/
--
vda



From vda  Thu Aug 21 23:08:29 2003
From: vda (Denis Vlasenko)
Date: Fri, 22 Aug 2003 09:08:29 +0300
Subject: SMP report
In-Reply-To: <20030819025600.GG3359@jm.kir.nu>
References: <3F3F57EF.7020002@bigpond.com> <20030819025600.GG3359@jm.kir.nu>
Message-ID: <200308220608.h7M68UL12118@Port.imtp.ilyichevsk.odessa.ua>

On 19 August 2003 05:56, Jouni Malinen wrote:
> Getting those fid reads returning proper values will certainly remove
> quite a few hw_resets and will thus help with the stability. The other
> issue, i.e., system lockup on hw_reset, may however still exist. I
> actually have couple of patches that could be tested on top of 0.0.4
> release so that we could try to find a way to avoid the crash. If
> someone with an SMP system using hostap_pci is willing to test these,
> please let me know and I'll send the patches. Please note that testing
> these will most probably end up crashing your system number of times..

Maybe it will be faster and more visible to just post the pathes
to the list with appropriate big fat warning. Saves email RTT.
--
vda



From andreaf  Fri Aug 22 14:00:40 2003
From: andreaf (Andrea G. Forte)
Date: Fri, 22 Aug 2003 17:00:40 -0400 (EDT)
Subject: Monitoring Management frames with HostAP???
Message-ID: <200308222100.h7ML0eDY006535@cisalpino.cs.columbia.edu>

Hi guys,
I am trying to monitor management frames with HostAP in monitoring mode 2 or 3.
I am also using ethereal.
Unfortunately I get a lot of LLC, ARP and UNKNOWN frames and no management 
frames. I am using the latest version of ethereal and hostAP....anybody can 
help?
Thanks a lot,
Andrea




From proski  Fri Aug 22 15:01:08 2003
From: proski (Pavel Roskin)
Date: Fri, 22 Aug 2003 18:01:08 -0400 (EDT)
Subject: Primary Firmware Download
In-Reply-To: <EF5625F9F795C94BA28B150706A21548A053F8@MAIL>
References: <EF5625F9F795C94BA28B150706A21548A053F8@MAIL>
Message-ID: <Pine.LNX.4.56.0308221744350.25879@marabou.research.att.com>

On Fri, 22 Aug 2003, Foy, Patrick wrote:

> We have an embedded application that requires all the download work to
> be done in the driver because if the card goes through a reset, the
> application might not know about the reset and therefore won't reload
> the firmware into RAM.

There is nothing wrong with having the complete firmware in the kernel
memory.  The alternative would be to generate a hotplug even and call
prism2_srec from hotplug.

If you load complete firmware images to the kernel, there is one more
issue.  If your changes to be integrated and maintained as part of HostAP,
please use the firmware download API.  You can keep firmware in memory if
you want, but it should be loaded rather than compiled into the driver for
legal reasons.

> I changed the download code to read the pda before the download begins and
> then restore the pda after the download completes.  This fixes the mac
> address problem, but the reported version is the previous version
> information.
>
> Any ideas how I can update the PDA to fix the version information?

I have no idea how you "restore the PDA" and what it means.  If you are
plugging the image in the driver, it's better that you read the PDA from
NVRAM (non-volatile RAM), as it's done in linux-wlan-ng.  You shouldn't
write to PDA.

I'm afraid you misunderstand the plugging procedure.  If you rely on
prism2_srec to plug the image, you are doing it wrong.  If you put
firmware to the kernel space, you should plug the image with the PDA from
the card.  This also means that the driver should be aware of PDRs.

You can look at a similar implementation for Symbol cards, but I didn't
implement firmware API yet: http://www.red-bean.com/~proski/symbol/

By the way please don't top-post.  It makes it inconvenient to quote your
messages.

-- 
Regards,
Pavel Roskin



From hajo  Fri Aug 22 15:46:54 2003
From: hajo (Hans-Joachim Klingshirn)
Date: Sat, 23 Aug 2003 00:46:54 +0200
Subject: hostap 0.0.4/NICID 8002 wep trouble
Message-ID: <20030823004654.4e85c0ce.hajo@hajo.org>

Hi,

I am trying to enable wep on a wireless lan connection between two
computers running hostap 0.0.4, with no success so far.

The hardware in the ap (pcmcia card in plx adapter, hostap_plx):

hostap_diag wlan0 output:
NICID: id=0x8002 v1.0.0 (HWB3163-01,02,03,04 Rev A)
PRIID: id=0x0015 v0.3.0
STAID: id=0x001f v0.7.6 (station firmware)

lspci output:
00:0c.0 Network controller: Standard Microsystems Corp [SMC] SMC2602W
EZConnect / Addtron AWA-100 (rev 02)

The hardware in the client (minipci-card, hostap_pci):

hostap_diag wlan0 output
NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.1.0
STAID: id=0x001f v1.4.9 (station firmware)

lspci output
01:02.0 Network controller: Harris Semiconductor Prism 2.5 Wavelan chipset
(rev 01)

Kernel is 2.4.21, wireless tools are v26, interfaces are v14(client) and v15(ap)

Problem: When loading hostap on the ap, it disables card-based wep, so I
run hostapd on the ap box. Without activating wep, everything works fine.
When activating wep with a 40bit key, no data can be transmitted.
hostap(d) on the ap box does not give any log messages concerning wep (log
level set to maximum). The hostap.conf on the ap box is the standard
config file as in the 0.0.4 distribution, only log levels and ssid have
been changed.

The client box already tested ok with hostap and wep when used in another setup,
so the problem is with the ap.

Concerning the wep problem: do I make any obvious mistakes? How can I debug the 
problem properly?

Concerning the prism card in the access point: NICID is 8002, the firmware is very old. I read
a bit about flashing the firmware, but the NICID 8002 does not show up in the compatibility 
charts for firmwares, as linked to from the firmware flashing mini-howto. What strange card do 
I have here? 

TIA,

HaJo Klingshirn

-- 
Will work for bandwidth.



From pfoy  Fri Aug 22 08:23:39 2003
From: pfoy (Foy, Patrick)
Date: Fri, 22 Aug 2003 11:23:39 -0400
Subject: Primary Firmware Download
Message-ID: <EF5625F9F795C94BA28B150706A21548A053F8@MAIL>

Pavel,

Thanks for all your help on the RAM download!

I gotten the primary and secondary RAM download to work pretty reliably, but
I am having issues with the PDA.  

I've changed a few things with the download procedure, so that it is
performed in a two step process.  

1. In an offline procedure, the prism2_srec utility generates a compilable
header file (primary_fw.h or secondary_fw.h) that is compiled into prism2
driver

2. At run time, the hostap_download reads the firmware from global memory
and then downloads the content into the WLAN card.

We have an embedded application that requires all the download work to be
done in the driver because if the card goes through a reset, the application
might not know about the reset and therefore won't reload the firmware into
RAM.

The prism2_srec utility can be run on any machine to auto generate the
primary_fw.h and secondary_fw.h files.  However, the PDA information is
obtained from the WLAN card that is used to create the files and this PDA is
added to the secondary_fw.h.  Part of the PDA is the mac address.  After
loading the firmware on multiple AP devices, we discovered that all units
had the same MAC address (ooops!).

I changed the download code to read the pda before the download begins and
then restore the pda after the download completes.  This fixes the mac
address problem, but the reported version is the previous version
information.

Any ideas how I can update the PDA to fix the version information?

Thanks.

Patrick

      

-----Original Message-----
From: Foy, Patrick 
Sent: Thursday, July 31, 2003 4:29 PM
To: 'Pavel Roskin'
Subject: RE: Primary Firmware Download


Pavel,

We are shipping APs with Senao cards (2511CD-Plus), some with primary
firmware 1.0.5 and others with 1.1.0.  We need secondary 1.7.4 for WDS,
Enhanced security, scanning, etc which requires primary of 1.1.0 or newer.  

The reason that I need to upgrade the primary with hostap (either into RAM
or flash) is because we have shipped 100s of units and they need upgraded
"in the field" (and we don't want to open the cases to re-flash the cards
using winupdate).  I've read that updating the primary into flash isn't
reliable, so I wanted to take the least risky route, which is uploading to
RAM.

Upgrading the secondary into RAM seems very reliably, but loading only the
secondary firmware is only a solution for cards with primary 1.1.0.  I need
to find a solution that allows me to upgrade the older cards (primary 1.0.5)
with a primary version that supports a secondary version of 1.7.4

Thanks for your help.

Patrick
   


-----Original Message-----
From: Pavel Roskin [mailto:proski at gnu.org]
Sent: Thursday, July 31, 2003 4:03 PM
To: Foy, Patrick
Cc: hostap at shmoo.com
Subject: RE: Primary Firmware Download


On Thu, 31 Jul 2003, Foy, Patrick wrote:

> We've been avoiding the primary firmware download issue for our project,
but
> have finally decided to re-visit the issue.  Since this last email, have
you
> been able to download the primary firmware into RAM successfully (and
> reliably) using the hostap driver and the prism2_srec utility?

No.  It doesn't work.  But I don't think you need it.  If you think you
need it, please give more details.  What kind of hardware are you talking
about?  What primary and secondary firmware do you have?  Why do you want
to upgrade primary firmware in the RAM?  What's wrong with flashing the
latest primary and secondary firmware?  Cannot you just load secondary
firmware into the RAM?

-- 
Regards,
Pavel Roskin



From proski  Fri Aug 22 17:17:00 2003
From: proski (Pavel Roskin)
Date: Fri, 22 Aug 2003 20:17:00 -0400 (EDT)
Subject: HostAP source?
In-Reply-To: <200308211825.h7LIPRRe009392@cisalpino.cs.columbia.edu>
References: <200308211825.h7LIPRRe009392@cisalpino.cs.columbia.edu>
Message-ID: <Pine.LNX.4.56.0308222014020.26205@marabou.research.att.com>

On Thu, 21 Aug 2003, Andrea G. Forte wrote:

> Any of you guys can tell me how to find the hostAP main Source code?

Go to google.com and search for "hostap source code" (without quotes).
The URL you are looking for is within first 10 hits.

> Could you also tell me in what modules the HostAp is divided into?

Once you find the source code, unpack it.  There is a file called
driver_source.txt.  It answers your question.

-- 
Regards,
Pavel Roskin



From williamt  Fri Aug 22 17:40:15 2003
From: williamt (William Tai)
Date: Fri, 22 Aug 2003 17:40:15 -0700
Subject: hostcan problem
Message-ID: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>

Hi All:

I try to scan all neighboring APs.
However the number of APs I scanned is less than the number scanned by
another clients.
Does ant body have the same experience?

Thanx
William




From proski  Fri Aug 22 17:35:57 2003
From: proski (Pavel Roskin)
Date: Fri, 22 Aug 2003 20:35:57 -0400 (EDT)
Subject: hostap 0.0.4/NICID 8002 wep trouble
In-Reply-To: <20030823004654.4e85c0ce.hajo@hajo.org>
References: <20030823004654.4e85c0ce.hajo@hajo.org>
Message-ID: <Pine.LNX.4.56.0308222022160.26305@marabou.research.att.com>

On Sat, 23 Aug 2003, Hans-Joachim Klingshirn wrote:

> Concerning the prism card in the access point: NICID is 8002, the
> firmware is very old. I read a bit about flashing the firmware, but the
> NICID 8002 does not show up in the compatibility charts for firmwares,
> as linked to from the firmware flashing mini-howto. What strange card do
> I have here?

I don't think your problems with be discussed seriously until you upgrade.

Please give links when referring to documentation.  See Mini-howto on
Flashing Intersil Prism Chipsets: http://linux.junsun.net/intersil-prism/

There is no word "chart" in that howto.  Instead of compatibility charts,
use prism2_srec without "-r" or "-f" and it will tell you if the firmware
is compatible.

-- 
Regards,
Pavel Roskin



From jkmaline  Fri Aug 22 17:51:43 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 17:51:43 -0700
Subject: Primary Firmware Download
In-Reply-To: <EF5625F9F795C94BA28B150706A21548A053F8@MAIL>
References: <EF5625F9F795C94BA28B150706A21548A053F8@MAIL>
Message-ID: <20030823005143.GA3435@jm.kir.nu>

On Fri, Aug 22, 2003 at 11:23:39AM -0400, Foy, Patrick wrote:

> 2. At run time, the hostap_download reads the firmware from global memory
> and then downloads the content into the WLAN card.
> 
> We have an embedded application that requires all the download work to be
> done in the driver because if the card goes through a reset, the application
> might not know about the reset and therefore won't reload the firmware into
> RAM.

You might want to take a look at the CVS version of the Host AP driver
and persistent mode for volatile download.. Adding '-p' flag for the
prism2_srec will request the driver to keep a copy of the image in
kernel memory and automatically downlod it in case of hw_reset.

> The prism2_srec utility can be run on any machine to auto generate the
> primary_fw.h and secondary_fw.h files.

Please note that there are some issues with linking in non-GPL code to
the kernel modules and I would never accept this kind of change to be
added to the Host AP distribution.

> Any ideas how I can update the PDA to fix the version information?

By plugging the firmware properly using the PDA information of the card
that is going to use the image and not by using the same PDA for all
downloads.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Aug 22 17:55:53 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 17:55:53 -0700
Subject: hostcan problem
In-Reply-To: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>
References: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>
Message-ID: <20030823005553.GB3435@jm.kir.nu>

On Fri, Aug 22, 2003 at 05:40:15PM -0700, William Tai wrote:

> I try to scan all neighboring APs.
> However the number of APs I scanned is less than the number scanned by
> another clients.

Please include more information.. Which Host AP version did you use?
What commands did you use to request a scan and how did you read the
results? Are you using Master (Host AP) or Managed (station) mode? What
is your station firmware version?

-- 
Jouni Malinen                                            PGP id EFC895FA



From proski  Fri Aug 22 17:56:48 2003
From: proski (Pavel Roskin)
Date: Fri, 22 Aug 2003 20:56:48 -0400 (EDT)
Subject: Urgent Help Needed, please
In-Reply-To: <001301c366e8$b3bf2440$4262ea84@Hakidu>
References: <001301c366e8$b3bf2440$4262ea84@Hakidu>
Message-ID: <Pine.LNX.4.56.0308222051220.26487@marabou.research.att.com>

On Wed, 20 Aug 2003, Kashif Bhatti wrote:

> Dear All,

You are seriously risking to have your message incorrectly classified by
your choice of subject and greeting :-)

> In my experiments I extract signal strenth with my client laptop from a
> real wireless access point, using Orinoco client manager software.
[snip]
> QUESTION:
> I am thinking of using additional wireless access points and read about
> mobile Host AP. If I get Host AP running on Linux (I hope), will it be
> possible for me to extract signal strenth with my client laptop (windows
> 2000) from the beacons transmitted by the Host AP laptop ?

The format of beacons is mandated by 802.11 standard and it's the same,
whether it's emitted by HostAP of some other AP.  The signal strength is
measured on the client.  So I'm quite sure that you can measure signal
strength of all beacons, regardless of their provenance.

-- 
Regards,
Pavel Roskin



From proski  Fri Aug 22 17:59:42 2003
From: proski (Pavel Roskin)
Date: Fri, 22 Aug 2003 20:59:42 -0400 (EDT)
Subject: hostcan problem
In-Reply-To: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>
References: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>
Message-ID: <Pine.LNX.4.56.0308222057120.26500@marabou.research.att.com>

On Fri, 22 Aug 2003, William Tai wrote:

> Hi All:
>
> I try to scan all neighboring APs.
> However the number of APs I scanned is less than the number scanned by
> another clients.
> Does ant body have the same experience?

Yes.  Firmware 1.3.4 has this bug.  Firmware versions 1.5.6 and 1.7.4 are
known to be OK.

Also, make sure that you have no ESSID specified, or you will get only APs
with that ESSID.  Use "iwconfig wlan0 essid any".

-- 
Regards,
Pavel Roskin



From jkmaline  Fri Aug 22 18:01:27 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 18:01:27 -0700
Subject: hostap 0.0.4/NICID 8002 wep trouble
In-Reply-To: <20030823004654.4e85c0ce.hajo@hajo.org>
References: <20030823004654.4e85c0ce.hajo@hajo.org>
Message-ID: <20030823010127.GC3435@jm.kir.nu>

On Sat, Aug 23, 2003 at 12:46:54AM +0200, Hans-Joachim Klingshirn wrote:

> Problem: When loading hostap on the ap, it disables card-based wep, so I
> run hostapd on the ap box.

I don't understand this logic here.. Running hostapd (vs. kernel side
802.11 management) does not have anything to do with whether WEP is
being done in the hardware of software. Host AP driver is using
host-based software implementation of WEP if the firmware version is
known to have issues with hardware "accelerated" WEP. This happens
whether you use hostapd or not.

> When activating wep with a 40bit key, no data can be transmitted.
> hostap(d) on the ap box does not give any log messages concerning wep (log
> level set to maximum). The hostap.conf on the ap box is the standard
> config file as in the 0.0.4 distribution, only log levels and ssid have
> been changed.

Running hostapd with static WEP keys is something that I have never
really tested properly. I would recommend first testing WEP without
hostapd to keep the setup as simple as possible.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Aug 22 18:03:57 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 18:03:57 -0700
Subject: Monitoring Management frames with HostAP???
In-Reply-To: <200308222100.h7ML0eDY006535@cisalpino.cs.columbia.edu>
References: <200308222100.h7ML0eDY006535@cisalpino.cs.columbia.edu>
Message-ID: <20030823010357.GD3435@jm.kir.nu>

On Fri, Aug 22, 2003 at 05:00:40PM -0400, Andrea G. Forte wrote:

> I am trying to monitor management frames with HostAP in monitoring mode 2 or 3.
> I am also using ethereal.
> Unfortunately I get a lot of LLC, ARP and UNKNOWN frames and no management 
> frames. I am using the latest version of ethereal and hostAP....anybody can 
> help?

What version of libpcap are you using? Which commands did you use to
enable monitoring mode?

-- 
Jouni Malinen                                            PGP id EFC895FA



From williamt  Fri Aug 22 18:28:11 2003
From: williamt (William Tai)
Date: Fri, 22 Aug 2003 18:28:11 -0700
Subject: hostcan problem
References: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>
	<20030823005553.GB3435@jm.kir.nu>
Message-ID: <004c01c36915$d0fac170$e6f0c53f@williamt>


----- Original Message ----- 
From: "Jouni Malinen" <jkmaline at cc.hut.fi>
To: <hostap at shmoo.com>
Sent: Friday, August 22, 2003 5:55 PM
Subject: Re: hostcan problem


> On Fri, Aug 22, 2003 at 05:40:15PM -0700, William Tai wrote:
> 
> > I try to scan all neighboring APs.
> > However the number of APs I scanned is less than the number scanned by
> > another clients.
> 
> Please include more information.. 
Which Host AP version did you use?

Sorry I do not know.

> What commands did you use to request a scan and how did you read the
> results?

request a scan
int hostap_read_ap_info(struct device *dev)
{
 struct hfa384x_hostscan_request scan_req;
 u16 rate;
 int ret = 0;
 INT oldLevel;
 local_info_t *local = (local_info_t *) dev->priv;

 memset(&scan_req, 0, sizeof(scan_req));
 scan_req.channel_list = __constant_cpu_to_le16(0x000f/*0x3fff*/);
 rate = 2;//HFA384X_RATES_1MBPS;

 scan_req.txrate = cpu_to_le16(rate);
 /* leave SSID empty to accept all SSIDs */
oldLevel = NU_Control_Interrupts(NU_DISABLE_INTERRUPTS);
 if (local->iw_mode == IW_MODE_MASTER) {
  if (hostap_set_word(dev, HFA384X_RID_CNFPORTTYPE,
        HFA384X_PORTTYPE_BSS) ||
      local->func->reset_port(dev))
   printf("Leaving Host AP mode for HostScan failed\n\r");
 }
 if (local->func->set_rid(dev, HFA384X_RID_HOSTSCAN, &scan_req,
     sizeof(scan_req))) {
  printf("HOSTSCAN failed\n\r");
  ret = -EINVAL;
 }
NU_Control_Interrupts(oldLevel);
 NU_Sleep(400);
oldLevel = NU_Control_Interrupts(NU_DISABLE_INTERRUPTS);
 if (local->iw_mode == IW_MODE_MASTER) {
  if (hostap_set_word(dev, HFA384X_RID_CNFPORTTYPE,
        HFA384X_PORTTYPE_HOSTAP) ||
      local->func->reset_port(dev))
   printf("Returning to Host AP mode after HostScan failed\n\r");
 }
NU_Control_Interrupts(oldLevel);

 return ret;
}

read the result
#ifndef PRISM2_NO_DEBUG
 case HFA384X_INFO_HOSTSCANRESULTS:
  prism2_info_hostscanresults(local, buf, left);
  break;
#endif /* PRISM2_NO_DEBUG */


>Are you using Master (Host AP) or Managed (station) mode? What
> is your station firmware version?
>

HOSTAP mode


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



From jkmaline  Fri Aug 22 18:44:29 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 18:44:29 -0700
Subject: hostcan problem
In-Reply-To: <004c01c36915$d0fac170$e6f0c53f@williamt>
References: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>
	<20030823005553.GB3435@jm.kir.nu>
	<004c01c36915$d0fac170$e6f0c53f@williamt>
Message-ID: <20030823014429.GD3226@jm.kir.nu>

On Fri, Aug 22, 2003 at 06:28:11PM -0700, William Tai wrote:

> > Which Host AP version did you use?
> 
> Sorry I do not know.

Hmm.. Well, I would suggest finding out which version it is, if you want
to get more support from me ;-). Based on the code you listed below, it
is a modified version of something. I have never seen the listed
function before. It looks like somethign that was based on code I have
written, but someone has decided that it should be indented in some
horrible way.. In addition, it seems to be ported to non-Linux
platform (Nucleus).

I would like to remind you that my code in Host AP driver has been
released under GPL and there are certain requirements in distributing
modified versions of it. If you happen to link it into something like
Nucleus and distribute the combined program, you would be required to
make the source code of all the components of this combined program
available under the same license..

>  scan_req.channel_list = __constant_cpu_to_le16(0x000f/*0x3fff*/);

You are only scanning channels 1..4 so if you have APs on other
channels, they are not shown..

> >Are you using Master (Host AP) or Managed (station) mode? What
> > is your station firmware version?
> 
> HOSTAP mode

You should note that the scanning functions in the firmware do not work
in Host AP and jumping to client mode for a short period of time is
horrible hack and is certainly not very reliable..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Aug 22 18:55:02 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 18:55:02 -0700
Subject: Urgent Help Needed, please
In-Reply-To: <Pine.LNX.4.56.0308222051220.26487@marabou.research.att.com>
References: <001301c366e8$b3bf2440$4262ea84@Hakidu>
	<Pine.LNX.4.56.0308222051220.26487@marabou.research.att.com>
Message-ID: <20030823015502.GE3226@jm.kir.nu>

On Fri, Aug 22, 2003 at 08:56:48PM -0400, Pavel Roskin wrote:
> On Wed, 20 Aug 2003, Kashif Bhatti wrote:
> 
> > Dear All,
> 
> You are seriously risking to have your message incorrectly classified by
> your choice of subject and greeting :-)

Hey, that got only 2.3 of required 5.0 points.. Maybe promising $30M to
anyone who helps with the questions would have been needed ;-).

> > In my experiments I extract signal strenth with my client laptop from a
> > real wireless access point, using Orinoco client manager software.

Is "real wireless access point" defined to be something like Orinoco AP
that can use proprietary Lucent protocol for some link statistics
reporting?

> The format of beacons is mandated by 802.11 standard and it's the same,
> whether it's emitted by HostAP of some other AP.  The signal strength is
> measured on the client.  So I'm quite sure that you can measure signal
> strength of all beacons, regardless of their provenance.

Yes, beacon strength should certainly be available. However, the Lucent
link test frames (WMP LinkTest) will not be handled in interoperable
way. Station firmware wants to eat these without letting host system
handle them. The latest STA firmware version might allow this to be
changed, but I don't know whether it would really be worth anyones time
to implement support for this.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Aug 22 19:05:22 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 19:05:22 -0700
Subject: A couple of Problems with hostap and 802.1x
In-Reply-To: <20030820160602.GA7888@legolas.drinsama.de>
References: <20030820160602.GA7888@legolas.drinsama.de>
Message-ID: <20030823020522.GF3226@jm.kir.nu>

On Wed, Aug 20, 2003 at 06:06:02PM +0200, Erich Schubert wrote:

> Well, that leads to my questions already. ;)
> - xsupplicant: using the same certificates i can't get it to work. It
> sends out the user name; on the machine running hostapd i do see the EAP
> Challenge being sent out, on the client i don't see it coming in with
> ethereal. I guess that is why xsupplicant doesn't reply. Any ideas?

Seeing hostapd debug log with at least debug=2 (or -dd in command line)
level could be helpful to find out what did not work.

> - dynamic wep rekeying with EAP-TSL and win2k. Does this work? when i
> enable rekeying in hostapd authentication fails:
> wlan0: encryption configured, but RX frame not encrypted (SA=...)
> i guess that is the reply frame.

It should work. How did you configure hostapd for this? With both
broadcast and unicast keys? Does EAP-TLS succeed in this setup or do you
get that frame drop messages already for an EAPOL packet?

> Another question: When 802.11i is finished; are there people working on
> implementing these for linux already?

Yes.

-- 
Jouni Malinen                                            PGP id EFC895FA



From imp  Fri Aug 22 20:45:43 2003
From: imp (imp)
Date: Sat, 23 Aug 2003 12:45:43 +0900
Subject: hostap with 1.7.4 ???
Message-ID: <009201c36929$08007850$d200a8c0@Snoopy>

Dear all

I already issue the "commnd still in list" error..
and I found the situation why it occur !!

with PRISM 2.5 or 3.0 card up to 1.5.6 firmware work very well.  
I mean, If STA link hostap then hostap has been reset (turn off and the turn on), the STA still can re-association with that hostap.

but, using above 1.5.6, 1.6.3, 1.7.2, 1.7.4 for example, 
above same test always failed.. I thinks It's must be prism firmware bug.. isn't it ? 

Thanks for your attention, and welcome to any comment.

Bernard... 




From james.harper  Sat Aug 16 20:35:29 2003
From: james.harper (James Harper)
Date: Sun, 17 Aug 2003 13:35:29 +1000
Subject: 2.6.0-test3 (and -test2)
References: <000001c363e5$a6ac34b0$c7fda8c0@int.sbss.com.au>
	<20030816160435.GA3251@jm.kir.nu>
Message-ID: <3F3EF801.4030101@bigpond.com>

Jouni Malinen wrote:

>On Sat, Aug 16, 2003 at 09:00:48PM +1000, James Harper wrote:
>
>  
>
>>I can't get hostap to compile against 2.6.0-test3 (I didn't have any
>>luck with -test2 either but only tried that once). My kernel tree is
>>pretty much virgin. I'm using the cvs tree. I'm also compiling it all as
>>modules.
>>    
>>
>
>Please always include the exact commands you used and error messages you
>saw when reporting compilation problems. If you used any other command,
>please also note that plain 'make' is the best (and probably only) way
>to compile the driver for Linux 2.5/2.6.
>
>  
>
>>Does anyone have it going against this kernel? I get errors in
>>hostap_crypt, it appears that if HOSTAP_CRYPT_MODULE was defined I might
>>have more luck, or maybe my kernel tree is broken and I need a new one.
>>    
>>
>
>Yes, works fine with 2.6.0-test3 (and worked with -test2, too).
>HOSTAP_CRYPT_MODULE should not be defined. hostap_crypt module is now
>compined into hostap.o.
>
>  
>
sorry, all i was asking for was a 'does it work?'... if there was a 
known problem then it's a bit of a waste of time me discovering it all 
over again.
I tracked it down earlier this morning though, once I excluded 
hostap_crypt.c from the Makefile it all worked fine. I'm running with 
2.6.0-test3 as I type this. I've always copied the files into the kernel 
tree and compiled from there with a 'make -j5 modules'. I believe the 
kernel patch for 2.6.0-test2 (and therefore also -test3) should have 
hostap_crypt.c removed from the makefile. It certainly works fine 
without it being there and doesn't work with it.

thanks

James





From proski  Sun Aug 17 19:59:33 2003
From: proski (Pavel Roskin)
Date: Sun, 17 Aug 2003 22:59:33 -0400 (EDT)
Subject: how to make my AP work?
In-Reply-To: <000b01c364dd$c0e4dc80$c8fdfea9@gigabyteli>
Message-ID: <Pine.LNX.4.44.0308172254440.13006-100000@portland.hansa.lan>

On Mon, 18 Aug 2003, ??? wrote:

> hello,i got some problem. i have made a linux kernel supported with
> devfs. and i load T1085800.hfw firmware ok!

HostAP doesn't work with tertiary firmware.  It makes secondary
firmware act as an access point.  If you want to use tertiary firmware,
use linux-wlan-ng.

Next time please report version of the software that gives you the
problem.  Also, a step-by-step explanation of what you are doing would be
helpful.  Relevant parts of the kernel log (as reported by dmesg) may be
useful as well.

-- 
Regards,
Pavel Roskin




From maty10  Mon Aug 18 01:22:01 2003
From: maty10 (Mathew Burns)
Date: Mon, 18 Aug 2003 18:22:01 +1000
Subject: Hard lockup with XI-636
Message-ID: <3F408CA9.4060503@iprimus.com.au>

I have a zcom (rebadged as skymaster here in australia) xi-626 pci card 
working fine in ad-hoc mode with the oricono_pci module but would like 
to use one of two identical boxes as a AP.

Whenever I issue "modprobe hostap_pci" the machine hard locks, with 
nothing written to syslog or dmesg.
The last line written by modprobe is "registered net device: wlan0"

Kernel 2.4.21 compiled myself with the wireless extention patches 
applied as suggested.

Can anyone help me start looking for a cause to this?






From DANIEL.ARLETH  Mon Aug 18 04:34:23 2003
From: DANIEL.ARLETH (ARLETH, DANIEL)
Date: Mon, 18 Aug 2003 13:34:23 +0200
Subject: Symbol/Nortel 4123 PCI Adapter - Port orinoco module to hostap
Message-ID: <252E5192A5C2D311B24B00508B5D5CCCBD821F@slpms0.sel.de>

Hello List,

after occasionally reading success messages from people using the (really
great) hostap driver in managed mode for the Symbol/Nortel pcmcia cards, I
hope I could get some help for my PCI Card here.

I want to run the Nortel PCI Card (4123) as a member of a bridge(, but the
symbol support in the Orinoco driver seems not to be ready for this).
I tried with the module available at
http://www.traum404.de/download/index.html
<http://www.traum404.de/download/index.html> .

As far as I can see (with my very basic C knowledge) this module consists of
only a few lines of code to initial the pcmcia card, and then let the
Orinoco driver do its work.
The only thing which has to be changed in the Orinoco driver are two lines
of code in Orinoco.c and Orinoco.h.

void hermes_struct_init(hermes_t *hw, ulong address,
			int io_space, int reg_spacing)
{
	hw->iobase = address;
>	hw->iobase1 = 0;
>	hw->iobase2 = 0;
       	hw->io_space = io_space;
	hw->reg_spacing = reg_spacing;
	hw->inten = 0x0;

So my hope is, this could be as easy for the hostap driver.

Please don't understand me wrong! I don't ask you for writing a driver for
me! But I can't do it and I hope to hear from you either 
"Forget it! The hostap has got nothing in common with the Orinoco driver, so
the Nortel_pci module is useless for the hostap driver" 
or
"No problem! Just ask a friend with C knowledge to have a look at it and
change ..........."

Or just gave me any hint how to get my Card running in a bridge.

Thanks,

Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030818/d022544b/attachment-0001.htm 


From gallir  Mon Aug 18 05:05:05 2003
From: gallir (Ricardo Galli)
Date: Mon, 18 Aug 2003 14:05:05 +0200
Subject: Symbol/Nortel 4123 PCI Adapter - Port orinoco module to hostap
In-Reply-To: <252E5192A5C2D311B24B00508B5D5CCCBD821F@slpms0.sel.de>
References: <252E5192A5C2D311B24B00508B5D5CCCBD821F@slpms0.sel.de>
Message-ID: <200308181405.05451.gallir@uib.es>

On Monday 18 August 2003 13:34, ARLETH, DANIEL shaped the electrons to shout:
> Hello List,
>
> after occasionally reading success messages from people using the (really
> great) hostap driver in managed mode for the Symbol/Nortel pcmcia cards, I
> hope I could get some help for my PCI Card here.
>
> I want to run the Nortel PCI Card (4123) as a member of a bridge(, but the
> symbol support in the Orinoco driver seems not to be ready for this).

You are very confused. 

What do you want to achieve by putting a managed wireless card in a bridge? I 
guess you want to do level 2 bridging. To do it you should have the original 
source MAC (SA) and the final destination MAC (DA), which is _impossible_ in 
a "managed" card, which only deal with "receiving address" (RA) and 
"transmitter address" (TA).

To make it work you need:

a) An AP that is able to bridge between its associated stations and the 
ethernet. The master interface knows the MAC of every associated station and 
the ethernet has the original source and destination MAC, so bridging between 
the ethernet and (only) associated stations is possible.

b) Or, if you want to connect two different LANs, the card/SO needs two extra 
headers (SA and RA), and that the goal of WDS and the four headers (RA, TA, 
SA and DA).

So, put your "bridging" wireless card in master mode and add it to a bridging 
group. Or for managed one you can only do IP routing.


-- 
  ricardo galli       GPG id C8114D34
  http://mnm.uib.es/~gallir/




From zhengjr  Mon Aug 18 05:42:11 2003
From: zhengjr (???)
Date: Mon, 18 Aug 2003 20:42:11 +0800
Subject: how to make my AP work? 
References: <20030818120553.38EFFEA99@mail.iocaine.com>
Message-ID: <000901c36586$25b1faf0$7bf7748c@gigabyteli>

> HostAP doesn't work with tertiary firmware.  It makes secondary
> firmware act as an access point.  If you want to use tertiary firmware,
> use linux-wlan-ng.
> Next time please report version of the software that gives you the
> problem.  Also, a step-by-step explanation of what you are doing would be
> helpful.  Relevant parts of the kernel log (as reported by dmesg) may be
> useful as well.
> -Regards,
> -Pavel Roskin
It's very sorry. I dont say clearly. I use Avaya's wireless PCMCIA card.
so I use HermesAP-0.2. Now, I have installed heremesAP and made it work.
Other PC's wireless device can connect to my wireless interface.
My problem is how to make my AP like bridge, so that others connected to my
AP can
connected to Internet.
Someone tells me to setup NAT or makes my wire card to be shared with all
devices.
However I am newbie on wireless and network. So I need more detail to do
that.
Hope people can teach me how to do that or where have information about
that.

-thx ur reply,very appreciate.
-simata(zhengjr at locust.csie.ncku.edu.tw)





From DANIEL.ARLETH  Mon Aug 18 06:30:51 2003
From: DANIEL.ARLETH (ARLETH, DANIEL)
Date: Mon, 18 Aug 2003 15:30:51 +0200
Subject: Symbol/Nortel 4123 PCI Adapter - Port orinoco module to hosta p
Message-ID: <252E5192A5C2D311B24B00508B5D5CCCBD8220@slpms0.sel.de>

Ok, you are right. (Now) I'm very confused...........

My configuration:

Internet
   |     
 Router  (managed by my ISP)
   |
   |     (wired)
   |
 My AP1  (Prism2 in PLX / hostap in master mode
   |              Bridge between eth0/wlan0/wlan0wds0)
   |     (wds)
   |
 My AP2  (Prism2 in PLX / hostap in master mode
   |              Bridge between eth0/wlan0/wlan0wds0)
   |
   |-- wired clients
   |
wireless clients

The ISP Router and AP1 are placed at the attic, accessible for everybody, so
I bought a small cabinet to secure them. That's the reason why I bought the
Nortel Card, because of its external antenna.

And now I want to associate the AP1 as a normal client to the AP2 (because
there is no master mode driver for the Nortel card), but bridge the ISP
router and the wlan anyway together. 

The ISP Router masquerades all connections, because the internal net is
192.168.0.0 and I can't add static routes so I would have to masquerade on
AP1, too. That may work, but hmm, I think there must be a better way. 

Any idea?? Maybe something like proxy arp? Remember, I don't want to connect
a whole network behind AP1, only one client(the ISP router).

And there is really no chance to get the bridge up with a wlan Card in
managed mode?

Btw, is there any difference between "managed mode" and "station mode", or
does both mean the same?

Daniel
 

> Hello List,
>
> after occasionally reading success messages from people using the (really
> great) hostap driver in managed mode for the Symbol/Nortel pcmcia cards, I
> hope I could get some help for my PCI Card here.
>
> I want to run the Nortel PCI Card (4123) as a member of a bridge(, but the
> symbol support in the Orinoco driver seems not to be ready for this).

You are very confused. 

What do you want to achieve by putting a managed wireless card in a bridge?
I 
guess you want to do level 2 bridging. To do it you should have the original

source MAC (SA) and the final destination MAC (DA), which is _impossible_ in

a "managed" card, which only deal with "receiving address" (RA) and 
"transmitter address" (TA).

To make it work you need:

a) An AP that is able to bridge between its associated stations and the 
ethernet. The master interface knows the MAC of every associated station and

the ethernet has the original source and destination MAC, so bridging
between 
the ethernet and (only) associated stations is possible.

b) Or, if you want to connect two different LANs, the card/SO needs two
extra 
headers (SA and RA), and that the goal of WDS and the four headers (RA, TA, 
SA and DA).

So, put your "bridging" wireless card in master mode and add it to a
bridging 
group. Or for managed one you can only do IP routing.


-- 
  ricardo galli       GPG id C8114D34
  http://mnm.uib.es/~gallir/






From hdxia1  Mon Aug 18 06:57:40 2003
From: hdxia1 (Haidong Xia)
Date: Mon, 18 Aug 2003 13:57:40 +0000
Subject: HostAP Digest, Vol 4, Issue 33
Message-ID: <BAY1-F19Y1qClo8XoPN00028c13@hotmail.com>

Dear all,

Can anyone explain to me how HostAP set up a default wep key ? Since I don't 
have a hardware manual of prism2 card, I am a little confused, when I read 
the code of WEP key setting under HostAP.

The basic question is: When HostAP sets up a default wep key, a WinXP client 
automatically detects this access point has a default wep key. How a WinXP 
client know an Access Point has a WEP key, right after association?

I am doing an experiment to allow both of clients using Wep key, or not 
using wep key to get access to an Access point. But WinXP client keeps 
saying there is a wep key, and just wants to use a Wep key, even I didn't 
set up a key for it.

Is there a way to set up a default wep key in HostAP, but WinXP client will 
not detect it?  So that a user can configure the client freely with or with 
WEP key?   Of course, at hostAP side, it can detect a
frame is encrypted or not, and deal with it correspondingly.

Thanks for any point.
Haidong

_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE* 
http://join.msn.com/?page=features/virus




From askatti  Mon Aug 18 11:21:36 2003
From: askatti (Anand S. Katti)
Date: Mon, 18 Aug 2003 23:51:36 +0530 (IST)
Subject: how to make my AP work?
In-Reply-To: <20030818180003.7B350EAEC@mail.iocaine.com>
Message-ID: <Pine.LNX.4.44.0308182345370.20297-100000@ece.iisc.ernet.in>


> Someone tells me to setup NAT or makes my wire card to be shared with all
> devices.

If you are newbie and want some easy tool to setup NAT, I suggest you 
install SHOREWALL (an iptable based firewall http://shorewall.net/). And 
to configure the firewall you have to install WEBMIN(a system 
administration tool http://webmin.com/)

webmin has shorewall module in it, that helps u in configuring the 
firewall easily. In shorewall you can setup NAT and make other nodes 
browse the internet vai NAT.

If any problems in this let me know.
-------
With Regards,
Anand S. Katti






From proski  Mon Aug 18 12:10:26 2003
From: proski (Pavel Roskin)
Date: Mon, 18 Aug 2003 15:10:26 -0400 (EDT)
Subject: 2.6.0-test3 (and -test2)
In-Reply-To: <3F3EF801.4030101@bigpond.com>
References: <000001c363e5$a6ac34b0$c7fda8c0@int.sbss.com.au>
	<20030816160435.GA3251@jm.kir.nu> <3F3EF801.4030101@bigpond.com>
Message-ID: <Pine.LNX.4.56.0308181507140.20845@marabou.research.att.com>

On Sun, 17 Aug 2003, James Harper wrote:

> sorry, all i was asking for was a 'does it work?'... if there was a
> known problem then it's a bit of a waste of time me discovering it all
> over again.

Just in case, 2.6.0-test3 seems to have an interrupt problem with PCI
bridges by Texas Insriments.  2.6.0-test2 is OK.

> I tracked it down earlier this morning though, once I excluded
> hostap_crypt.c from the Makefile it all worked fine. I'm running with
> 2.6.0-test3 as I type this. I've always copied the files into the kernel
> tree and compiled from there with a 'make -j5 modules'. I believe the
> kernel patch for 2.6.0-test2 (and therefore also -test3) should have
> hostap_crypt.c removed from the makefile. It certainly works fine
> without it being there and doesn't work with it.

Yes, it's time to clean up references to hostap_crypt module and
hostap_crypt.c as the source for that module.  The patch is attached.

-- 
Regards,
Pavel Roskin
-------------- next part --------------
--- Makefile
+++ Makefile
@@ -105,22 +105,19 @@
 
 ifdef CONFIG_MODVERSIONS
 
-VERFILES=$(MSRC)/hostap.ver ## $(MSRC)/hostap_crypt.ver
+VERFILES=$(MSRC)/hostap.ver
 $(MSRC)/hostap_crypt_wep.o: $(VERFILES)
 $(MSRC)/hostap.o: $(VERFILES)
 $(MSRC)/hostap_cs.o: $(VERFILES)
 $(MSRC)/hostap_plx.o: $(VERFILES)
 $(MSRC)/hostap_pci.o: $(VERFILES)
-INCLUDES_MODVER=-include $(MSRC)/hostap.ver ##-include $(MSRC)/hostap_crypt.ver
+INCLUDES_MODVER=-include $(MSRC)/hostap.ver
 
 GENKSYMS=/sbin/genksyms
 ifdef CONFIG_SMP
         GENKSYMS += -p smp_
 endif
 
-##$(MSRC)/hostap_crypt.ver: $(MSRC)/hostap_crypt.c
-##	$(CC) $(INCLUDES) $(CFLAGS) -E -D__GENKSYMS__ $^ | \
-##		$(GENKSYMS) -k $(KERNELVER) > $@
 $(MSRC)/hostap.ver: $(MSRC)/hostap.c
 	$(CC) $(INCLUDES) $(CFLAGS) -E -D__GENKSYMS__ $^ | \
 		$(GENKSYMS) -k $(KERNELVER) > $@
@@ -155,7 +152,7 @@
 pccard:	$(MSRC)/$(MODULE_CS) hostap crypt install_info
 plx:	$(MSRC)/$(MODULE_PLX) hostap crypt install_info
 pci:	$(MSRC)/$(MODULE_PCI) hostap crypt install_info
-crypt:  $(MSRC)/hostap_crypt_wep.o ## $(MSRC)/hostap_crypt.o
+crypt:  $(MSRC)/hostap_crypt_wep.o
 hostap: $(MSRC)/hostap.o
 
 SRC=$(MSRC)/hostap_hw.c $(MSRC)/hostap_wlan.h $(MSRC)/hostap_config.h \
@@ -163,8 +160,6 @@
 	$(MSRC)/hostap_ap.h \
 	$(MSRC)/hostap_crypt.h $(MSRC)/hostap.h $(MSRC)/hostap_compat.h
 
-## $(MSRC)/hostap_crypt.o: $(MSRC)/hostap_crypt.c $(MSRC)/hostap_crypt.h
-
 $(MSRC)/hostap_crypt_wep.o: $(MSRC)/hostap_crypt_wep.c $(MSRC)/hostap_crypt.h
 
 $(MSRC)/hostap.o: $(MSRC)/hostap.c $(MSRC)/hostap.h \
@@ -229,7 +224,7 @@
 	mkdir -p $(MODPATH_PCI)
 	cp -f $(MSRC)/hostap.o $(MODPATH_PCI)
 
-install_crypt: $(MSRC)/hostap_crypt_wep.o ## $(MSRC)/hostap_crypt.o
+install_crypt: $(MSRC)/hostap_crypt_wep.o
 	@echo "Installing hostap_crypt_*.o to $(MODPATH_PCI)"
 	mkdir -p $(MODPATH_PCI)
 	cp -f $(MSRC)/hostap_crypt_*.o $(MODPATH_PCI)
--- driver/hostap.mk
+++ driver/hostap.mk
@@ -1,11 +1,9 @@
 all:
 	$(MAKE) -C modules MODULES=hostap_cs.o
 	$(MAKE) -C modules MODULES=hostap.o
-	$(MAKE) -C modules MODULES=hostap_crypt.o
 	$(MAKE) -C modules MODULES=hostap_crypt_wep.o
 
 install:
 	$(MAKE) -C modules install-modules MODULES=hostap_cs.o
 	$(MAKE) -C modules install-modules MODULES=hostap.o
-	$(MAKE) -C modules install-modules MODULES=hostap_crypt.o
 	$(MAKE) -C modules install-modules MODULES=hostap_crypt_wep.o
--- driver/modules/Makefile
+++ driver/modules/Makefile
@@ -1,10 +1,9 @@
 # Makefile for Linux 2.6 kbuild / Linux 2.4
 
 # export-objs was removed in Linux 2.5.60
-# export-objs := hostap.o ## hostap_crypt.o
+# export-objs := hostap.o
 
 obj-m += hostap.o hostap_crypt_wep.o
-## obj-m += hostap_crypt.o
 obj-m += hostap_cs.o
 obj-m += hostap_plx.o
 obj-m += hostap_pci.o
@@ -15,22 +14,19 @@
 
 ifdef CONFIG_MODVERSIONS
 
-VERFILES=hostap.ver ## hostap_crypt.ver
+VERFILES=hostap.ver
 hostap_crypt_wep.o: $(VERFILES)
 hostap.o: $(VERFILES)
 hostap_cs.o: $(VERFILES)
 hostap_plx.o: $(VERFILES)
 hostap_pci.o: $(VERFILES)
-INCLUDES_MODVER=-include hostap.ver ## -include hostap_crypt.ver
+INCLUDES_MODVER=-include hostap.ver
 
 GENKSYMS=/sbin/genksyms
 ifdef CONFIG_SMP
         GENKSYMS += -p smp_
 endif
 
-## hostap_crypt.ver: hostap_crypt.c
-##	$(CC) $(INCLUDES) $(CFLAGS) -E -D__GENKSYMS__ $^ | \
-##		$(GENKSYMS) -k $(VERSION).$(PATCHLEVEL).$(SUBLEVEL) > $@
 hostap.ver: hostap.c
 	$(CC) $(INCLUDES) $(CFLAGS) -E -D__GENKSYMS__ $^ | \
 		$(GENKSYMS) -k $(VERSION).$(PATCHLEVEL).$(SUBLEVEL) > $@
--- driver_source.txt
+++ driver_source.txt
@@ -40,13 +40,13 @@
 hostap_plx.c
 	Hardware specific routines for PLX-based PC Card adapter version
 
-
-crypto modules:
-
 hostap_crypt.[ch]
 	Registration/unregistration code for modularized encryption
 	implementation
 
+
+crypto modules:
+
 hostap_crypt_wep.c
 	Host-based WEP (Wired Equivalent Privacy) implementation
 
--- kernel-patches/hostap-linux-2.4.20.patch
+++ kernel-patches/hostap-linux-2.4.20.patch
@@ -19,7 +19,7 @@
 +  PLX/PCI/CS version of the driver to actually use the driver.
 +
 +  The driver can be compiled as modules and they will be called
-+  "hostap.o", "hostap_crypt.o", and "hostap_crypt_wep.o".
++  "hostap.o" and "hostap_crypt_wep.o".
 +
 +Host AP driver for Prism2/2.5/3 in PLX9052 based PCI adaptors
 +CONFIG_HOSTAP_PLX
@@ -108,7 +108,7 @@
  
  # Things that need to export symbols
 -export-objs	:= airo.o orinoco.o hermes.o
-+export-objs	:= airo.o orinoco.o hermes.o hostap.o hostap_crypt.o
++export-objs	:= airo.o orinoco.o hermes.o hostap.o
  
  obj-$(CONFIG_HERMES)		+= orinoco.o hermes.o
  obj-$(CONFIG_PCMCIA_HERMES)	+= orinoco_cs.o
@@ -116,7 +116,7 @@
  obj-$(CONFIG_AIRO)		+= airo.o
  obj-$(CONFIG_AIRO_CS)		+= airo_cs.o airo.o
  
-+obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt.o hostap_crypt_wep.o
++obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt_wep.o
 +obj-$(CONFIG_HOSTAP_CS)		+= hostap_cs.o
 +obj-$(CONFIG_HOSTAP_PLX)	+= hostap_plx.o
 +obj-$(CONFIG_HOSTAP_PCI)	+= hostap_pci.o
--- kernel-patches/hostap-linux-2.5.60.patch
+++ kernel-patches/hostap-linux-2.5.60.patch
@@ -38,7 +38,7 @@
 +	PLX/PCI/CS version of the driver to actually use the driver.
 +
 +	The driver can be compiled as modules and they will be called
-+	"hostap.o", "hostap_crypt.o", and "hostap_crypt_wep.o".
++	"hostap.o" and "hostap_crypt_wep.o".
 +
 +config HOSTAP_HOSTAPD
 +	bool "Use user space daemon (hostapd) with Host AP driver"
@@ -114,7 +114,7 @@
  obj-$(CONFIG_AIRO)		+= airo.o
  obj-$(CONFIG_AIRO_CS)		+= airo_cs.o airo.o
 +
-+obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt.o hostap_crypt_wep.o
++obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt_wep.o
 +obj-$(CONFIG_HOSTAP_CS)		+= hostap_cs.o
 +obj-$(CONFIG_HOSTAP_PLX)	+= hostap_plx.o
 +obj-$(CONFIG_HOSTAP_PCI)	+= hostap_pci.o
--- kernel-patches/hostap-linux-2.5.69.patch
+++ kernel-patches/hostap-linux-2.5.69.patch
@@ -36,7 +36,7 @@
 +	PLX/PCI/CS version of the driver to actually use the driver.
 +
 +	The driver can be compiled as modules and they will be called
-+	"hostap.o", "hostap_crypt.o", and "hostap_crypt_wep.o".
++	"hostap.o" and "hostap_crypt_wep.o".
 +
 +config HOSTAP_FIRMWARE
 +	bool "Support downloading firmware images with Host AP driver"
@@ -97,7 +97,7 @@
  obj-$(CONFIG_AIRO)		+= airo.o
  obj-$(CONFIG_AIRO_CS)		+= airo_cs.o airo.o
  
-+obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt.o hostap_crypt_wep.o
++obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt_wep.o
 +obj-$(CONFIG_HOSTAP_CS)		+= hostap_cs.o
 +obj-$(CONFIG_HOSTAP_PLX)	+= hostap_plx.o
 +obj-$(CONFIG_HOSTAP_PCI)	+= hostap_pci.o
--- kernel-patches/hostap-linux-2.6.0-test2.patch
+++ kernel-patches/hostap-linux-2.6.0-test2.patch
@@ -38,7 +38,7 @@
 +	PLX/PCI/CS version of the driver to actually use the driver.
 +
 +	The driver can be compiled as modules and they will be called
-+	"hostap.o", "hostap_crypt.o", and "hostap_crypt_wep.o".
++	"hostap.o" and "hostap_crypt_wep.o".
 +
 +config HOSTAP_FIRMWARE
 +	bool "Support downloading firmware images with Host AP driver"
@@ -100,7 +100,7 @@
  obj-$(CONFIG_AIRO)		+= airo.o
  obj-$(CONFIG_AIRO_CS)		+= airo_cs.o airo.o
  
-+obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt.o hostap_crypt_wep.o
++obj-$(CONFIG_HOSTAP)		+= hostap.o hostap_crypt_wep.o
 +obj-$(CONFIG_HOSTAP_CS)		+= hostap_cs.o
 +obj-$(CONFIG_HOSTAP_PLX)	+= hostap_plx.o
 +obj-$(CONFIG_HOSTAP_PCI)	+= hostap_pci.o
--- pcmcia-cs-patches/hostap-pcmcia-cs-3.1.34.patch
+++ pcmcia-cs-patches/hostap-pcmcia-cs-3.1.34.patch
@@ -6,13 +6,13 @@
  endif
  
 +# Host AP driver
-+MODULES	+= hostap.o hostap_crypt.o hostap_crypt_wep.o hostap_cs.o
-+SRCS	+= hostap.c hostap_crypt.c hostap_crypt_wep.c hostap_cs.c
++MODULES	+= hostap.o hostap_crypt_wep.o hostap_cs.o
++SRCS	+= hostap.c hostap_crypt_wep.c hostap_cs.c
 +
  all:	$(MODULES)
  
 -wvlan_hcf.o wvlan_hcfio.o hermes.o orinoco.o: %.o: %.c
-+wvlan_hcf.o wvlan_hcfio.o hermes.o orinoco.o hostap.o hostap_crypt.o: %.o: %.c
++wvlan_hcf.o wvlan_hcfio.o hermes.o orinoco.o hostap.o: %.o: %.c
  	$(CC) -MD -c $(XFLAGS) $<
  	@mkdir -p .depfiles ; mv $*.d .depfiles
  
--- todo.lst
+++ todo.lst
@@ -50,8 +50,6 @@
 - make sure that hostscan setting is re-set after card reset
 - reuse prism2_tx code with prism2_tx_80211
 - new module code should use try_module_get() for crypto modules
-- could actually integrate hostap_crypt.o module into hostap.o.. I don't think
-  it is that likely that only encryption stuff would be used in other drivers
 - ioctl's can be interrupted (EINTR, e.g., by killing iwconfig) which can
   result in leaving entries to pending CmdCompl list or command completion
   events to empty pending list; this should be cleaned up


From williamt  Mon Aug 18 16:23:37 2003
From: williamt (William Tai)
Date: Mon, 18 Aug 2003 16:23:37 -0700
Subject: What's the difference between prism2.5 and prism3 and what version
	of hostap support prism3
Message-ID: <04d901c365df$c097c4b0$e6f0c53f@williamt>

Hi All:


         When does hostsp start to support prism3 and
what's the difference between prism2.5 and prism3?

Thanx



From proski  Mon Aug 18 16:43:12 2003
From: proski (Pavel Roskin)
Date: Mon, 18 Aug 2003 19:43:12 -0400 (EDT)
Subject: What's the difference between prism2.5 and prism3 and what
 version of hostap support prism3
In-Reply-To: <04d901c365df$c097c4b0$e6f0c53f@williamt>
References: <04d901c365df$c097c4b0$e6f0c53f@williamt>
Message-ID: <Pine.LNX.4.56.0308181934170.26451@marabou.research.att.com>

On Mon, 18 Aug 2003, William Tai wrote:

>          When does hostsp start to support prism3 and
> what's the difference between prism2.5 and prism3?

Why do you think that Prism 3 is not supported?  Can you give the source
that led you to this conclusion?  I don't have a Prism 3 card, but I
believe it should work with the existing code.  I remember a report that
linux-wlan-ng worked with a Prism 3 card without any changes.

As for the differences, look for your self at
http://www.intersil.com/cda/application/0,1239,2,00.html

Unfortunately, I don't see any side-by-side comparison.  You may want to
compare specifications of the integrates Baseband/MAC chips - they
interact with the driver software.

-- 
Regards,
Pavel Roskin



From williamt  Mon Aug 18 17:03:05 2003
From: williamt (William Tai)
Date: Mon, 18 Aug 2003 17:03:05 -0700
Subject: What's the difference between prism2.5 and prism3 and what
	version of hostap support prism3
References: <04d901c365df$c097c4b0$e6f0c53f@williamt>
	<Pine.LNX.4.56.0308181934170.26451@marabou.research.att.com>
Message-ID: <04ee01c365e5$43ab6cd0$e6f0c53f@williamt>


----- Original Message ----- 
From: "Pavel Roskin" <proski at gnu.org>
To: "William Tai" <williamt at arescom.com>
Cc: <hostap at shmoo.com>
Sent: Monday, August 18, 2003 4:43 PM
Subject: Re: What's the difference between prism2.5 and prism3 and what
version of hostap support prism3


> On Mon, 18 Aug 2003, William Tai wrote:
>
> >          When does hostsp start to support prism3 and
> > what's the difference between prism2.5 and prism3?
>
> Why do you think that Prism 3 is not supported?  Can you give the source
> that led you to this conclusion?  I don't have a Prism 3 card, but I
> believe it should work with the existing code.  I remember a report that
> linux-wlan-ng worked with a Prism 3 card without any changes.
>

>From readme document
Introduction
============

This is a Linux driver for wireless LAN cards based on Intersil's
Prism2/2.5 chipset.
So I am confused.
My hostap driver was download at April.
I do not know whether my driver support prism3 or not.






> As for the differences, look for your self at
> http://www.intersil.com/cda/application/0,1239,2,00.html
>
> Unfortunately, I don't see any side-by-side comparison.  You may want to
> compare specifications of the integrates Baseband/MAC chips - they
> interact with the driver software.
>
> -- 
> Regards,
> Pavel Roskin
>




From proski  Mon Aug 18 17:02:26 2003
From: proski (Pavel Roskin)
Date: Mon, 18 Aug 2003 20:02:26 -0400 (EDT)
Subject: What's the difference between prism2.5 and prism3 and what
 version of hostap support prism3
In-Reply-To: <04ee01c365e5$43ab6cd0$e6f0c53f@williamt>
References: <04d901c365df$c097c4b0$e6f0c53f@williamt>
	<Pine.LNX.4.56.0308181934170.26451@marabou.research.att.com>
	<04ee01c365e5$43ab6cd0$e6f0c53f@williamt>
Message-ID: <Pine.LNX.4.56.0308181959090.26744@marabou.research.att.com>

On Mon, 18 Aug 2003, William Tai wrote:

> This is a Linux driver for wireless LAN cards based on Intersil's
> Prism2/2.5 chipset.
> So I am confused.
> My hostap driver was download at April.
> I do not know whether my driver support prism3 or not.

Indeed, it still says so.  Perhaps there haven't been many Prism 3 devices
around to add it to the documentation.

If you have any problems with Prism 3 device, please report them.  If it's
a PCI card, you may want to test the CVS version, which has the PCI ID
for Prism 3 cards.

If you have no problems and everything works, please report it as well
(with HostAP version and the card name, please), and the documentation
will be fixed.

-- 
Regards,
Pavel Roskin



From williamt  Mon Aug 18 17:33:20 2003
From: williamt (William Tai)
Date: Mon, 18 Aug 2003 17:33:20 -0700
Subject: What's the difference between prism2.5 and prism3 and what
	version of hostap support prism3
References: <04d901c365df$c097c4b0$e6f0c53f@williamt>
	<Pine.LNX.4.56.0308181934170.26451@marabou.research.att.com>
	<04ee01c365e5$43ab6cd0$e6f0c53f@williamt>
	<Pine.LNX.4.56.0308181959090.26744@marabou.research.att.com>
Message-ID: <050001c365e9$7d6481b0$e6f0c53f@williamt>


----- Original Message ----- 
From: "Pavel Roskin" <proski at gnu.org>
To: "William Tai" <williamt at arescom.com>
Cc: <hostap at shmoo.com>
Sent: Monday, August 18, 2003 5:02 PM
Subject: Re: What's the difference between prism2.5 and prism3 and what
version of hostap support prism3


> On Mon, 18 Aug 2003, William Tai wrote:
>
> > This is a Linux driver for wireless LAN cards based on Intersil's
> > Prism2/2.5 chipset.
> > So I am confused.
> > My hostap driver was download at April.
> > I do not know whether my driver support prism3 or not.
>
> Indeed, it still says so.  Perhaps there haven't been many Prism 3 devices
> around to add it to the documentation.
>
> If you have any problems with Prism 3 device, please report them.  If it's
> a PCI card, you may want to test the CVS version, which has the PCI ID
> for Prism 3 cards.
>

My driver is downloaded around April.
I insert the Prism3 card.
It seems not working well.
Client can not associated with my AP.
BTW, could you tell me when hostap start to support prism3?


Very Thanx

> If you have no problems and everything works, please report it as well
> (with HostAP version and the card name, please), and the documentation
> will be fixed.
>
> -- 
> Regards,
> Pavel Roskin
>




From jkmaline  Mon Aug 18 19:12:56 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Aug 2003 19:12:56 -0700
Subject: What's the difference between prism2.5 and prism3 and what
	version of hostap support prism3
In-Reply-To: <050001c365e9$7d6481b0$e6f0c53f@williamt>
References: <04d901c365df$c097c4b0$e6f0c53f@williamt>
	<Pine.LNX.4.56.0308181934170.26451@marabou.research.att.com>
	<04ee01c365e5$43ab6cd0$e6f0c53f@williamt>
	<Pine.LNX.4.56.0308181959090.26744@marabou.research.att.com>
	<050001c365e9$7d6481b0$e6f0c53f@williamt>
Message-ID: <20030819021256.GB3359@jm.kir.nu>

On Mon, Aug 18, 2003 at 05:33:20PM -0700, William Tai wrote:

> > On Mon, 18 Aug 2003, William Tai wrote:
> > > This is a Linux driver for wireless LAN cards based on Intersil's
> > > Prism2/2.5 chipset.

Yes, that was written when Prism3 did not yet exist and has not been
updated since ;-).

> > > I do not know whether my driver support prism3 or not.

Host AP driver has always supported Prism3. There are no major
differences between Prism2, Prism2.5, and Prism3 as far as the driver is
concerned.

> My driver is downloaded around April.
> I insert the Prism3 card.
> It seems not working well.
> Client can not associated with my AP.

Which firmware version are you using? If it happens to be STA f/w
v1.4.2, you should note that it has a known issue of not working in Host
AP mode. If it is another version, please do give more details: test
latest CVS version, send 'dmesg' output of a client trying to associate
with it. In addition, include full description of the card you are using
(vendor, model, firmware versions, pci/plx/cs).

> BTW, could you tell me when hostap start to support prism3?

It already supports Prism3. I use Prism2, Prism2.5, and Prism3 cards
in my tests and they all work fine. I am not aware of any Prism3-related
issue in the driver. You need to give more details about the issues you
have seen in order to make it possible to figure out what is wrong.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug 18 19:21:30 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Aug 2003 19:21:30 -0700
Subject: Symbol/Nortel 4123 PCI Adapter - Port orinoco module to hosta p
In-Reply-To: <252E5192A5C2D311B24B00508B5D5CCCBD8220@slpms0.sel.de>
References: <252E5192A5C2D311B24B00508B5D5CCCBD8220@slpms0.sel.de>
Message-ID: <20030819022130.GC3359@jm.kir.nu>

On Mon, Aug 18, 2003 at 03:30:51PM +0200, ARLETH, DANIEL wrote:

> The ISP Router and AP1 are placed at the attic, accessible for everybody, so
> I bought a small cabinet to secure them. That's the reason why I bought the
> Nortel Card, because of its external antenna.
> 
> And now I want to associate the AP1 as a normal client to the AP2 (because
> there is no master mode driver for the Nortel card), but bridge the ISP
> router and the wlan anyway together. 

You cannot use a IEEE 802.11 device that operates as a client that is
associated to an AP ("Managed"/"Infra" mode) to implement layer2 bridge.
IEEE 802.11 standard frames do not allow the source MAC address be
changed in the frames sent by that device.

However, you do not need to use "Master" (AP) mode for bridging; you
could also use WDS links without normal AP functionality. This may even
work with Lucent/Orinoco-based cards. At least, I have been able to use
Host AP driver with Lucent WaveLAN card to send and receive standard WDS
frames ('iwconfig wlan0 mode Repeater' and then add WDS links with
iwpriv wds_add command). This does not require Host AP mode.

> The ISP Router masquerades all connections, because the internal net is
> 192.168.0.0 and I can't add static routes so I would have to masquerade on
> AP1, too. That may work, but hmm, I think there must be a better way. 

Why do you think that masquerading on AP1 would not be OK?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug 18 19:33:38 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Aug 2003 19:33:38 -0700
Subject: Hard lockup with XI-636
In-Reply-To: <3F408CA9.4060503@iprimus.com.au>
References: <3F408CA9.4060503@iprimus.com.au>
Message-ID: <20030819023338.GD3359@jm.kir.nu>

On Mon, Aug 18, 2003 at 06:22:01PM +1000, Mathew Burns wrote:

> I have a zcom (rebadged as skymaster here in australia) xi-626 pci card 
> working fine in ad-hoc mode with the oricono_pci module but would like 
> to use one of two identical boxes as a AP.
> 
> Whenever I issue "modprobe hostap_pci" the machine hard locks, with 
> nothing written to syslog or dmesg.
> The last line written by modprobe is "registered net device: wlan0"

Do you get any messages on text console if you first set logging level
to maximum (dmesg -n 8)? What kind of host system are you using (CPU? is
it SMP?)?

> Kernel 2.4.21 compiled myself with the wireless extention patches 
> applied as suggested.

Which compiler version did you use to compile the kernel? Did you
compile Host AP driver with the exact same compiler? Did you run 'make
clean' after applying any patches to the kernel (i.e., recompiled
everything)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug 18 19:40:18 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Aug 2003 19:40:18 -0700
Subject: HostAP Digest, Vol 4, Issue 33
In-Reply-To: <BAY1-F19Y1qClo8XoPN00028c13@hotmail.com>
References: <BAY1-F19Y1qClo8XoPN00028c13@hotmail.com>
Message-ID: <20030819024018.GE3359@jm.kir.nu>

On Mon, Aug 18, 2003 at 01:57:40PM +0000, Haidong Xia wrote:

> Can anyone explain to me how HostAP set up a default wep key ? Since I 
> don't have a hardware manual of prism2 card, I am a little confused, when I 
> read the code of WEP key setting under HostAP.

You don't need a hardware manual for this.. IEEE 802.11 standard might
be more useful ;-).

> The basic question is: When HostAP sets up a default wep key, a WinXP 
> client automatically detects this access point has a default wep key. How a 
> WinXP client know an Access Point has a WEP key, right after association?

Actually, it already knows it before association. The AP includes a
Privacy bit in the capability info field of the beacons.

> I am doing an experiment to allow both of clients using Wep key, or not 
> using wep key to get access to an Access point. But WinXP client keeps 
> saying there is a wep key, and just wants to use a Wep key, even I didn't 
> set up a key for it.

Yes, many WinXP clients do not really like the Privacy bit in the
beacons (or probe responses) if you are trying to use unencrypted
connection.

> Is there a way to set up a default wep key in HostAP, but WinXP client will 
> not detect it?  So that a user can configure the client freely with or with 
> WEP key?   Of course, at hostAP side, it can detect a
> frame is encrypted or not, and deal with it correspondingly.

This depends a bit on the client implementation. In other words, you
might get it working with some drivers, but not with all.. I don't
remember whether Prism2 changes the capability information contents
based on "exclude unencrypted" configuration. If it does, you try
setting up the WEP keys with 'open' option of the iwconfig (iwconfig
wlan0 key s:abcde open).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug 18 19:47:33 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Aug 2003 19:47:33 -0700
Subject: 2.6.0-test3 (and -test2)
In-Reply-To: <Pine.LNX.4.56.0308181507140.20845@marabou.research.att.com>
References: <000001c363e5$a6ac34b0$c7fda8c0@int.sbss.com.au>
	<20030816160435.GA3251@jm.kir.nu> <3F3EF801.4030101@bigpond.com>
	<Pine.LNX.4.56.0308181507140.20845@marabou.research.att.com>
Message-ID: <20030819024733.GF3359@jm.kir.nu>

On Mon, Aug 18, 2003 at 03:10:26PM -0400, Pavel Roskin wrote:

> Yes, it's time to clean up references to hostap_crypt module and
> hostap_crypt.c as the source for that module.  The patch is attached.

Thanks! I did not apply the Makefile changes of removing already
commented out parts (I might still want to test them), but everything
else is now in CVS.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Aug 18 19:56:00 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Aug 2003 19:56:00 -0700
Subject: SMP report
In-Reply-To: <3F3F57EF.7020002@bigpond.com>
References: <3F3F57EF.7020002@bigpond.com>
Message-ID: <20030819025600.GG3359@jm.kir.nu>

On Sun, Aug 17, 2003 at 08:24:47PM +1000, James Harper wrote:

> I'm running 2.6.0-test3 with the latest cvs version of hostap on an SMP 
> system and it appears much more stable than previous versions. I just 
> tried a flood ping for a few minutes and the only error I got was:
> 
> Aug 17 20:19:17 portal kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
> busy for 1 usec

I'm not fully sure about what caused this, but with busy waiting for the
command reg, this should be fine.

> Aug 17 20:20:53 portal kernel: wlan0: detected fid change (try=0, 
> reg=0044): 0166 a5a4 0166
> Aug 17 20:20:59 portal kernel: wlan0: detected fid change (try=0, 
> reg=0040): 0000 03d6 03d6
> 
> which probably isn't good but previously I would be getting card resets 
> and/or crashes etc all over the place.

That's good, well, at least useful, to know. So, there are at least two
different SMP hosts that report changing fid registers and I haven't
heard of a single one without this "feature".. This looks like a
hardware bug to me since those registers should not really change its
value even if something is being read from the card (or written to it)
at the same time; as long as the RX/TX/Info event has not been ACKed
(and it will be ACKed only after reading those fid registers).

In other words, I apparently do need to leave that workaround code in
the driver, although probably with ifdefs for including it only to
hostap_pci and only when kernel is compiled with SMP support..

Getting those fid reads returning proper values will certainly remove
quite a few hw_resets and will thus help with the stability. The other
issue, i.e., system lockup on hw_reset, may however still exist. I
actually have couple of patches that could be tested on top of 0.0.4
release so that we could try to find a way to avoid the crash. If
someone with an SMP system using hostap_pci is willing to test these,
please let me know and I'll send the patches. Please note that testing
these will most probably end up crashing your system number of times..

-- 
Jouni Malinen                                            PGP id EFC895FA



From DANIEL.ARLETH  Tue Aug 19 02:13:23 2003
From: DANIEL.ARLETH (ARLETH, DANIEL)
Date: Tue, 19 Aug 2003 11:13:23 +0200
Subject: Symbol/Nortel 4123 PCI Adapter - Port orinoco module to hosta p
Message-ID: <252E5192A5C2D311B24B00508B5D5CCCBD8228@slpms0.sel.de>

> -----Urspr?ngliche Nachricht-----
> Von: Jouni Malinen [mailto:jkmaline at cc.hut.fi] 
> Gesendet: Dienstag, 19. August 2003 04:22
> An: hostap at shmoo.com
> Betreff: Re: Symbol/Nortel 4123 PCI Adapter - Port orinoco 
> module to hosta p

> You cannot use a IEEE 802.11 device that operates as a client that is
> associated to an AP ("Managed"/"Infra" mode) to implement 
> layer2 bridge.
> IEEE 802.11 standard frames do not allow the source MAC address be
> changed in the frames sent by that device.

Ok, I didn't know that.
 
> However, you do not need to use "Master" (AP) mode for bridging; you
> could also use WDS links without normal AP functionality. 
> This may even
> work with Lucent/Orinoco-based cards. At least, I have been 
> able to use
> Host AP driver with Lucent WaveLAN card to send and receive 
> standard WDS
> frames ('iwconfig wlan0 mode Repeater' and then add WDS links with
> iwpriv wds_add command). This does not require Host AP mode.

That sounds like the best solution, but

1. I've got a Nortel/Symbol Card. I read about reports people use this card
succesful in managed mode, but nothing about repeater mode. Do you think
this will work.

2. This leads me to the problem, why I actually posted to this list. My Card
is in a PCI adapter which is NOT with a PLX chip. 

Here again the belonging part of my first post:

>> I want to run the Nortel PCI Card (4123) as a member of a bridge(, but
the
>> symbol support in the Orinoco driver seems not to be ready for this).
>> I tried with the module available at
>> http://www.traum404.de/download/index.html
>> <http://www.traum404.de/download/index.html> .

>> As far as I can see (with my very basic C knowledge) this module consists
of
>> only a few lines of code to initial the pcmcia card, and then let the
>> Orinoco driver do its work.
>> The only thing which has to be changed in the Orinoco driver are two
lines
>> of code in Orinoco.c and Orinoco.h.

>> void hermes_struct_init(hermes_t *hw, ulong address,
>> 			int io_space, int reg_spacing)
>> {
>> 	hw->iobase = address;
>> >	hw->iobase1 = 0;
>> >	hw->iobase2 = 0;
>>        	hw->io_space = io_space;
>> 	hw->reg_spacing = reg_spacing;
>> 	hw->inten = 0x0;

>> So my hope is, this could be as easy for the hostap driver.

>> Please don't understand me wrong! I don't ask you for writing a driver
for
>> me! But I can't do it and I hope to hear from you either 
>> "Forget it! The hostap has got nothing in common with the Orinoco driver,
so
>> the Nortel_pci module is useless for the hostap driver" 
>> or
>> "No problem! Just ask a friend with C knowledge to have a look at it and
>> change ..........."

(End of quote)

It would be very nice, if anybody could give me an assessment for this.

> Why do you think that masquerading on AP1 would not be OK?
> 

Masquerading ervery connection 2 times is just needless and I worry it will
fail with some  protocols like ftp or messengers. Ok, I know no concretely
reason, ist just a fear.

Daniel


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



From roniuch  Tue Aug 19 02:24:02 2003
From: roniuch (=?ISO-8859-2?Q?Damian_Gaw=EAda?=)
Date: Tue, 19 Aug 2003 11:24:02 +0200
Subject: Hostap and Realtek 8180L
Message-ID: <3F41ECB2.2090200@stevenet.eu.org>

Hi!

Is there a plan to support Realtek 8180 chipset in the nearest future? 
Cards using this chip are inexpensive and their transmitting power is, 
reportedly, higher than of any prism based hardware.

--
Damian Gaweda




From imp  Tue Aug 19 04:04:40 2003
From: imp (imp)
Date: Tue, 19 Aug 2003 20:04:40 +0900
Subject: wlan0: hfa384x_cmd: entry still in list? 
Message-ID: <004101c36641$b063e530$d200a8c0@Snoopy>

Dear all

I have some problem using hostap, Please give your advice for me..

I run lastest CVS hostap and daemon, and I make some my own shell script which called automatically after hostapd start
and setting some wireless paramenter for myself.

the script is 

+ACMAIQ-/bin/sh
iwconfig wlan0 mode Master
iwconfig wlan0 nick +ACI-My Access Point+ACI-
iwconfig wlan0 channel 6
iwconfig wlan0 key off
iwconfig wlan0 rts 2347
iwconfig wlan0 frag 2346
iwconfig wlan0 rate auto
iwpriv wlan0 prism2+AF8-param 3 100
iwpriv wlan0 prism2+AF8-param 11 3
iwpriv wlan0 prism2+AF8-param 2 0
iwpriv wlan0 prism2+AF8-param 10 1
iwpriv wlan0 prism2+AF8-param 30 0
iwconfig wlan0 txpower 40
iwconfig wlan0 essid +ACI-imptest+ACI-

when I restart system include hostap wlan.. It was alway success, if there are no client STA which previous associated with my hostap AP.
(I mean remove STA wireless card from notebook. I try several wlan card from different vendor) 

But, after association from STA to AP then remain wireless card in notebook, and turn off the hostap(then the sta wireless card app scan the previous hostap), then, turn on my hostap. then I always meet flowing error while my system run above script...
 
+AH4- +ACM- wlan0: hfa384x+AF8-cmd: entry still in list? (entry+AD0-c016b820, type+AD0-0, res+AD0-0)
wlan0: hfa384x+AF8-cmd: command was not completed (res+AD0-0, entry+AD0-c016b820, type+AD0-0, cmd+AD0-0x0121, param0+AD0-0xfc33, EVSTAT+AD0-0000 INTEN+AD0-e1a0a09f)
wlan0: hfa384x+AF8-set+AF8-rid: CMDCODE+AF8-ACCESS+AF8-WRITE failed (res+AD0--110, rid+AD0-fc33, len+AD0-2)
wlan0: hfa384x+AF8-cmd: entry still in list? (entry+AD0-c016b820, type+AD0-0, res+AD0-0)
wlan0: hfa384x+AF8-cmd: command was not completed (res+AD0-0, entry+AD0-c016b820, type+AD0-0, cmd+AD0-0x0121, param0+AD0-0xfc10, EVSTAT+AD0-0000 INTEN+AD0-e1a0a09f)
wlan0: hfa384x+AF8-set+AF8-rid: CMDCODE+AF8-ACCESS+AF8-WRITE failed (res+AD0--110, rid+AD0-fc10, len+AD0-2)
wlan0: hfa384x+AF8-cmd: entry still in list? (entry+AD0-c016b820, type+AD0-0, res+AD0-0)
wlan0: hfa384x+AF8-cmd: command was not completed (res+AD0-0, entry+AD0-c016b820, type+AD0-0, cmd+AD0-0x0121, param0+AD0-0xfc43, EVSTAT+AD0-0000 INTEN+AD0-e1a0a09f)
wlan0: hfa384x+AF8-set+AF8-rid: CMDCODE+AF8-ACCESS+AF8-WRITE failed (res+AD0--110, rid+AD0-fc43, len+AD0-2)
wlan0: cnfEnhSecurity requires STA f/w 1.6.3 or newer
wlan0: cnfEnhSecurity set as 0
wlan0: hfa384x+AF8-cmd: entry still in list? (entry+AD0-c016b820, type+AD0-0, res+AD0-0)
wlan0: hfa384x+AF8-cmd: command was not completed (res+AD0-0, entry+AD0-c016b820, type+AD0-0, cmd+AD0-0x0021, param0+AD0-0xfdc6, EVSTAT+AD0-0000 INTEN+AD0-e1a0a09f)
wlan0: hfa384x+AF8-get+AF8-rid: CMDCODE+AF8-ACCESS failed (res+AD0--110, rid+AD0-fdc6, len+AD0-12)
wlan0: hfa384x+AF8-cmd: cmd+AF8-queue full
wlan0: hfa384x+AF8-cmd: cmd+AF8-queue full
wlan0: hfa384x+AF8-cmd: cmd+AF8-queue full
wlan0: hfa384x+AF8-set+AF8-rid: CMDCODE+AF8-ACCESS+AF8-WRITE failed (res+AD0--1, rid+AD0-fc02, len+AD0-34)




From a.boegl  Tue Aug 19 04:23:57 2003
From: a.boegl (=?GB2312?B?QWxleGFuZGVyIEJvImds?=)
Date: Tue, 19 Aug 2003 13:23:57 +0200
Subject: Error message> wlan0: SW TICK stuck?
In-Reply-To: <20030710171719.GA31992@jm.kir.nu>
References: <004e01c34147$b69d6e40$0965a8c0@msramek>
	<20030710171719.GA31992@jm.kir.nu>
Message-ID: <3F4208CD.3070900@amnet.at>

Jouni Malinen schrieb:

>On Thu, Jul 03, 2003 at 11:44:33AM +0200, Milos Sramek wrote:
>
>  
>
>>What does this error message mean ??  and why it's egressing ??
>>
>>wlan0: SW TICK stuck? bits=0x0 EvStat=8001 IntEn=e018
>>
>>Linux repeatly this message to console and is total "dead".
>>    
>>
>
>Host AP driver uses a software watchdog to detect busy looping IRQ
>events. That message should be displayed every two seconds if most of
>the kernel gets stuck (deadlock etc.) but hw interrupts are still
>working. Did you happen to catch any messages just before the first 'SW
>TICK stuck' message?
>
>  
>
Hi!

I have a simular problem, but it happends as soon I access the network.


The messages are folloing a "Unable to handle NULL pointer deference"
Kernel panic.

It seems that my problem is not hostap related cause I have the kernel
panic without the
hostap too, only without the SW TICK stuck messages every 2 secs.

I hope this can even help.










From askatti  Tue Aug 19 04:34:55 2003
From: askatti (Anand S. Katti)
Date: Tue, 19 Aug 2003 17:04:55 +0530 (IST)
Subject: 802.11 mathematical model
In-Reply-To: <20030819110447.C1760EB9A@mail.iocaine.com>
Message-ID: <Pine.LNX.4.44.0308191701070.14753-100000@ece.iisc.ernet.in>

Dear sir,

Im sorry if this post is not relevant to the current list. But I need the 
information on 802.11 in mathematical way.

Like I want to know the mathematical relation between RECEIVER 
SENSITIVITY, RANGE, MTBF, RATE, S/N RATIO, Txpower, Rxpower, etc..

Could anyone suggest me any link or books to get through this?
Well i know the definition of these above terms but if want to do 
programing, then i shudbe knowing the mathematical relation between them.

I hope you have the answer.

-- 
--------------.				
With Regards,   
Anand S. Katti




From Shripad_N  Tue Aug 19 07:23:55 2003
From: Shripad_N (Shripad N)
Date: Tue, 19 Aug 2003 19:53:55 +0530
Subject: Shutdown wlan interface
Message-ID: <E125980C421DFD4DA0B80D55DB1EDA5801421E5B@mtv01ex01.mindtree.com>

hi,

Is there any way to shutdown the wlan interface, ie stop consuming power, by
issuing a command.

iwconfig does not have a "down" option.

I dont want to plug in and plug out the card for that purpose. I tried
ifconfig wlan0 down

But the activity indicator of the card still is blinking.

please help,
regards
Shripad


DISCLAIMER:
This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Private Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return  e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited.  Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.



From sachin  Tue Aug 19 07:40:41 2003
From: sachin (Sachin Ganu)
Date: Tue, 19 Aug 2003 10:40:41 -0400 (EDT)
Subject: Shutdown wlan interface
In-Reply-To: <E125980C421DFD4DA0B80D55DB1EDA5801421E5B@mtv01ex01.mindtree.com>
Message-ID: <Pine.GSO.4.05.10308191039260.14424-100000@liman1a>

If you dont want to use the card, you could use "cardctl eject 0" to
"eject" it (without actually pulling it out)

to restart the card, you use "cardctl insert 0"

Hope that helps,
Sachin

-----------------------------------------------------------
Sachin Ganu
Graduate Research Assistant
WINLAB, Rutgers University
73 Brett Rd, Piscataway NJ 08854

On Tue, 19 Aug 2003, Shripad N wrote:

> hi,
> 
> Is there any way to shutdown the wlan interface, ie stop consuming power, by
> issuing a command.
> 
> iwconfig does not have a "down" option.
> 
> I dont want to plug in and plug out the card for that purpose. I tried
> ifconfig wlan0 down
> 
> But the activity indicator of the card still is blinking.
> 
> please help,
> regards
> Shripad
> 
> 
> DISCLAIMER:
> This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Private Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return  e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited.  Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 
> 




From gregfjohnson  Tue Aug 19 08:10:36 2003
From: gregfjohnson (Greg Johnson)
Date: Tue, 19 Aug 2003 08:10:36 -0700 (PDT)
Subject: prism cards
Message-ID: <20030819151036.37487.qmail@web14204.mail.yahoo.com>

Hello Vicente,

  I have also had a terrible time obtaining prism-based wireless cards.
The best I could come up with was to troll ebay.com looking for them.

  I use D-Link DWL-520 cards, which work great.  But, the Prism-based
versions are no longer available.  Note:  the DWL-520+ are NOT Prism-based
and will not work with hostap as far as I know.  Also, there are something
like three variants of the DWL-520 card, and the last one is not Prism-based
either.  The only way to tell on ebay is to closely examine the picture of
the card.

  Here is a URL for a Prism-based DWL-520 on ebay:

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3041951026&category=45001

  Here is a URL for a non-Prism-based DWL-520 on ebay that will not work
with hostap:

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3041508175&category=20321

  (I know from experience:  I am now the proud owner of one of the latter :-(.)

  If the picture of the card has a large blue and white component on it, then
it is a Prism-based hostap-compatible card.  If the picture has only small
black components, then it is not Prism-based and is not hostap-compatible.

  It seems to me that the disappearance of Prism-based cards represents a
threat to the whole hostap project.  The hostap project is one of the most
wonderful things I've found on the net for a while (THANKS JOUNI especially
and all contributors!!).

  What (if anything) can be done to encourage the continued viability of this
great project by protecting the availability of the hardware required for it?

Thanks,

Greg Johnson

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com



From david.goodenough  Tue Aug 19 08:21:11 2003
From: david.goodenough (David Goodenough)
Date: Tue, 19 Aug 2003 16:21:11 +0100
Subject: prism cards
In-Reply-To: <20030819151036.37487.qmail@web14204.mail.yahoo.com>
References: <20030819151036.37487.qmail@web14204.mail.yahoo.com>
Message-ID: <200308191621.12433.david.goodenough@btconnect.com>

On Tuesday 19 August 2003 16:10, Greg Johnson wrote:
> Hello Vicente,
>
>   I have also had a terrible time obtaining prism-based wireless cards.
> The best I could come up with was to troll ebay.com looking for them.
>
>   I use D-Link DWL-520 cards, which work great.  But, the Prism-based
> versions are no longer available.  Note:  the DWL-520+ are NOT Prism-based
> and will not work with hostap as far as I know.  Also, there are something
> like three variants of the DWL-520 card, and the last one is not
> Prism-based either.  The only way to tell on ebay is to closely examine the
> picture of the card.
>
>   Here is a URL for a Prism-based DWL-520 on ebay:
>
> http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3041951026&category=4500
>1
>
>   Here is a URL for a non-Prism-based DWL-520 on ebay that will not work
> with hostap:
>
> http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3041508175&category=2032
>1
>
>   (I know from experience:  I am now the proud owner of one of the latter
> :-(.)
>
>   If the picture of the card has a large blue and white component on it,
> then it is a Prism-based hostap-compatible card.  If the picture has only
> small black components, then it is not Prism-based and is not
> hostap-compatible.
>
>   It seems to me that the disappearance of Prism-based cards represents a
> threat to the whole hostap project.  The hostap project is one of the most
> wonderful things I've found on the net for a while (THANKS JOUNI especially
> and all contributors!!).
>
>   What (if anything) can be done to encourage the continued viability of
> this great project by protecting the availability of the hardware required
> for it?
>
> Thanks,
>
> Greg Johnson
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

You could try the Senao cards.  They seem to produce nothing but Prism
based cards (at least for 11b, their 11g cards are Aries based it would 
seem, but as far as I understand they are not in production yet).

David




From f6hqz  Tue Aug 19 10:25:44 2003
From: f6hqz (Francois BERGERET)
Date: Tue, 19 Aug 2003 19:25:44 +0200
Subject: prism cards
In-Reply-To: <20030819151036.37487.qmail@web14204.mail.yahoo.com>
Message-ID: <LEEMLOMCOLGDFKOEHKDPCENIDNAA.f6hqz@easyconnect.fr>

Hi friends,

I am using Micronet cards from Taiwan in a Soekris embeded PC running Bering with hostap, for HAM radio hobby. I have two different
cards : SP905V2 and SP905BDV2.

They are Prism 2.5 based.

All twice are from Z-com manufacturer instead :
- SP905V2 = XI-300B
- SP905BDV2 = XI-325H

They have two MMCX connectors for external antennas but are provided with a small slim antenna for laptop PC.

The best one is the SP905BDV2/XI-325H regarding ouput power and (mainly) its great RX sensitivity against competitors.

I leave in France, and it is possible to buy them here, from the Micronet importer at @ 78 EURO for the SP905BDV2. They have a lot
of wireless equipments...

I know but not have a SP906BA with Intersil chipset too but in PCI format.

GES (Generale Electronique Service)
Phone +33 1 64.41.78.88
Fax   +33 1 60.63.24.85
VoIP phoneH.323 callto:80.13.8.11
wireless at ges.fr (but seems to be out of service this days, may be on vacation).

Best Regards,
Francois BERGERET,
France.

> -----Message d'origine-----
> De : hostap-bounces at shmoo.com [mailto:hostap-bounces at shmoo.com]De la
> part de Greg Johnson
> Envoye : mardi 19 aout 2003 17:11
> A : hostap at shmoo.com; vicente.paredes at gruein.com
> Objet : prism cards
>
>
> Hello Vicente,
>
>   I have also had a terrible time obtaining prism-based wireless cards.
> The best I could come up with was to troll ebay.com looking for them.
>
>   I use D-Link DWL-520 cards, which work great.  But, the Prism-based
> versions are no longer available.  Note:  the DWL-520+ are NOT Prism-based
> and will not work with hostap as far as I know.  Also, there are something
> like three variants of the DWL-520 card, and the last one is not Prism-based
> either.  The only way to tell on ebay is to closely examine the picture of
> the card.
>
>   Here is a URL for a Prism-based DWL-520 on ebay:
>
> http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3041951026&category=45001
>
>   Here is a URL for a non-Prism-based DWL-520 on ebay that will not work
> with hostap:
>
> http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3041508175&category=20321
>
>   (I know from experience:  I am now the proud owner of one of the latter :-(.)
>
>   If the picture of the card has a large blue and white component on it, then
> it is a Prism-based hostap-compatible card.  If the picture has only small
> black components, then it is not Prism-based and is not hostap-compatible.
>
>   It seems to me that the disappearance of Prism-based cards represents a
> threat to the whole hostap project.  The hostap project is one of the most
> wonderful things I've found on the net for a while (THANKS JOUNI especially
> and all contributors!!).
>
>   What (if anything) can be done to encourage the continued viability of this
> great project by protecting the availability of the hardware required for it?
>
> Thanks,
>
> Greg Johnson
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From chhabra  Tue Aug 19 11:37:58 2003
From: chhabra (Madhusudan Singh)
Date: Tue, 19 Aug 2003 14:37:58 -0400
Subject: prism cards
In-Reply-To: <20030819174503.87344.qmail@web14203.mail.yahoo.com>
References: <20030819174503.87344.qmail@web14203.mail.yahoo.com>
Message-ID: <3F426E86.2030607@eecs.umich.edu>

I use Netgear MA401 (PCMCIA) and MA311(PCI) for my home wireless LAN. 
Both are hostap compatible. I do not know which stores have it. I bought 
mine online at buy.com

On how to do it, I wrote down instrucions at :

http://www.eecs.umich.edu/~chhabra/netgearwireless.html

I have not yet added the instructions for the Access Point, but they 
will soon be up.


Greg Johnson wrote:

>--- Madhusudan Singh <chhabra at eecs.umich.edu> wrote:
>  
>
>>Have you looked at Netgear cards ?
>>
>>
>>    
>>
>
>Hello Madhusudan,
>
>  I have not looked at Netgear cards.  Is there a hostap-compatible
>Netgear PCI card and a Netgear PCMCIA card that is currently available
>from Fry's, Best Buy, Circuit City etc.?
>
>Thanks,
>
>Greg Johnson
>  
>




From sleibt  Tue Aug 19 12:57:03 2003
From: sleibt (SLeiBt)
Date: Tue, 19 Aug 2003 21:57:03 +0200
Subject: prism cards
In-Reply-To: <LEEMLOMCOLGDFKOEHKDPCENIDNAA.f6hqz@easyconnect.fr>
References: <LEEMLOMCOLGDFKOEHKDPCENIDNAA.f6hqz@easyconnect.fr>
Message-ID: <1061323022.649.10.camel@act.irishseb.dyndns.org>

Hi!

Just a bit of warning... Quite a few makes have "fairly silently"
switched from prism to TI chipset in their 11 products... In some cases,
the product number changed a bit, say xxxV2, but some made no change
whatsoever to the product name.

I can't recall which it was I was interested in (ended up buying
netgear) and looking at the windows driver I found that it was made of 2
completely different sets of files, with different PCI ids & such, but
the exact same displayed name.

But maybe even netgear moved to something else than prism since last
spring.

Regards,

Sebastien





From lsantos  Tue Aug 19 13:04:42 2003
From: lsantos (Leonardo Pereira Santos)
Date: Tue, 19 Aug 2003 17:04:42 -0300
Subject: prism cards
In-Reply-To: <3F426E86.2030607@eecs.umich.edu>
References: <20030819174503.87344.qmail@web14203.mail.yahoo.com>
	<3F426E86.2030607@eecs.umich.edu>
Message-ID: <200308191704.42958.lsantos@pd3.com.br>

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

I'm using a SWL-2100N, which is a Prism2-based card, and it works fine. IMHO 
Samsung won't de discontinuing this card as they did an AP based on it... 
Cheers!

On Tuesday 19 August 2003 15:37, Madhusudan Singh wrote:
> I use Netgear MA401 (PCMCIA) and MA311(PCI) for my home wireless LAN.
> Both are hostap compatible. I do not know which stores have it. I bought
> mine online at buy.com
>
> On how to do it, I wrote down instrucions at :
>
> http://www.eecs.umich.edu/~chhabra/netgearwireless.html
>
> I have not yet added the instructions for the Access Point, but they
> will soon be up.
>
> Greg Johnson wrote:
> >--- Madhusudan Singh <chhabra at eecs.umich.edu> wrote:
> >>Have you looked at Netgear cards ?
> >
> >Hello Madhusudan,
> >
> >  I have not looked at Netgear cards.  Is there a hostap-compatible
> >Netgear PCI card and a Netgear PCMCIA card that is currently available
> >from Fry's, Best Buy, Circuit City etc.?
> >
> >Thanks,
> >
> >Greg Johnson
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

- -- 
This is Linux country.
On a quiet night, you can hear Windows reboot.

Leonardo Pereira Santos
Engenheiro de Projetos
PD3 Tecnologia
av. Par? 330/202
(51) 3337 1237

Today Fortune tells us:
The 'A' is for content, the 'minus' is for not typing it.  Don't ever do
this to my eyes again.
		-- Professor Ronald Brady, Philosophy, Ramapo State College
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/QoLa8uAMCTjfaxIRAtBXAJ480lwdQhKi6iQfoIsNkg95uofHxgCgj4lf
srWUrB0/Wp9CoJu+u9/cZh8=
=a9f2
-----END PGP SIGNATURE-----




From aca  Tue Aug 19 15:24:25 2003
From: aca (Aleksandar Nikolic)
Date: Wed, 20 Aug 2003 00:24:25 +0200
Subject: Prism cards (Greg Johnson)
Message-ID: <002201c366a0$a743ba20$020a010a@alfa>

Well We have a very big problems to find prism based wlan cards and there I can send to you look of three revision of DWL 520 
      Revision A is prism based
      Revision B is prism based too
but Revision C1 is not prism based  http://www.dlink.com/products/support.asp?pid=42

And one more thing  100%same card is Sparklan WL360F as DWL520 revision A and it is prism based so go to http://www.sparklan.com/wl360f.htm

So We all hope that prism will live, but selling of intersil corp on 17.07.2003. well  all we have is hope

Best regards 
Aleksandar Nikolic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030820/e3668ad4/attachment-0001.htm 


From jkmaline  Tue Aug 19 17:44:32 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 19 Aug 2003 17:44:32 -0700
Subject: Symbol/Nortel 4123 PCI Adapter - Port orinoco module to hosta p
In-Reply-To: <252E5192A5C2D311B24B00508B5D5CCCBD8228@slpms0.sel.de>
References: <252E5192A5C2D311B24B00508B5D5CCCBD8228@slpms0.sel.de>
Message-ID: <20030820004432.GA7117@jm.kir.nu>

On Tue, Aug 19, 2003 at 11:13:23AM +0200, ARLETH, DANIEL wrote:

> 1. I've got a Nortel/Symbol Card. I read about reports people use this card
> succesful in managed mode, but nothing about repeater mode. Do you think
> this will work.

I have never used or even seen that card and I do not know details about
what chipset and which version it uses. In other words, I do not have
enough information to guess whether it would work in repeater mode or
not. I have tested Repeater mode successfully with at least one
non-Prism2 card (Lucent) and I might have even tested it with
a PrismI/Symbol-based card (but I do not remember this for sure).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Aug 19 17:44:38 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 19 Aug 2003 17:44:38 -0700
Subject: Hostap and Realtek 8180L
In-Reply-To: <3F41ECB2.2090200@stevenet.eu.org>
References: <3F41ECB2.2090200@stevenet.eu.org>
Message-ID: <20030820004438.GB7117@jm.kir.nu>

On Tue, Aug 19, 2003 at 11:24:02AM +0200, Damian Gaw?da wrote:

> Is there a plan to support Realtek 8180 chipset in the nearest future? 
> Cards using this chip are inexpensive and their transmitting power is, 
> reportedly, higher than of any prism based hardware.

Do you know whether it has support for something like Host AP mode on
Prism2 (i.e., sending and receiving IEEE 802.11 management frames)? Is
technical documentation available for it to develop open source drivers?
If answer to these is "yes, it does support something like Host AP mode
and yes, documentation is available", it could well be worthwhile to add
support for it. If either of this is not the case, it will probably not
be supported in the near (or even distant) future.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Aug 19 17:44:42 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 19 Aug 2003 17:44:42 -0700
Subject: Shutdown wlan interface
In-Reply-To: <E125980C421DFD4DA0B80D55DB1EDA5801421E5B@mtv01ex01.mindtree.com>
References: <E125980C421DFD4DA0B80D55DB1EDA5801421E5B@mtv01ex01.mindtree.com>
Message-ID: <20030820004442.GC7117@jm.kir.nu>

On Tue, Aug 19, 2003 at 07:53:55PM +0530, Shripad N wrote:

> Is there any way to shutdown the wlan interface, ie stop consuming power, by
> issuing a command.

What kind of level of power saving would you need? Using cardctl to
eject the card is probably pretty close to removing the card (I would
assume it disconnects operating voltage from the card). Another option
would be to just disable most of the Prism2 operations with "iwpriv
wlan0 reset 3". This is supposed to drop power consumption a lot, but
not as much as cardctl eject. One benefit of just disabling the card is
in not having to reconfigure Linux netdev when the card is needed next
time ("iwpriv wlan0 reset 4"). However, if you anyway do all the setup
from pcmcia-cs scripts, cardctl eject & insert should work fine.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Aug 19 17:51:10 2003
From: jkmaline (Jouni Malinen)
Date: Tue, 19 Aug 2003 17:51:10 -0700
Subject: prism cards
In-Reply-To: <20030819151036.37487.qmail@web14204.mail.yahoo.com>
References: <20030819151036.37487.qmail@web14204.mail.yahoo.com>
Message-ID: <20030820005110.GD7117@jm.kir.nu>

On Tue, Aug 19, 2003 at 08:10:36AM -0700, Greg Johnson wrote:

>   It seems to me that the disappearance of Prism-based cards represents a
> threat to the whole hostap project.

>   What (if anything) can be done to encourage the continued viability of this
> great project by protecting the availability of the hardware required for it?

I do not see disappearance of Prism2/2.5/3-based cards as a major threat
for something like Host AP project; it's more like a fact of life.. Old
hardware will be replaced at some point when newer, cheaper or
technically superior, products become available. Prism2/2.5/3 does not
have a superior (far from it) interface to the host system, there are
other cards with much better design. I would find it much more
productive to add support for other wlan chipsets than to artificially
keep alive aging technology.

-- 
Jouni Malinen                                            PGP id EFC895FA



From tanyh  Tue Aug 19 18:17:36 2003
From: tanyh (Yang-Hwee TAN)
Date: Wed, 20 Aug 2003 09:17:36 +0800
Subject: 802.11 mathematical model
In-Reply-To: <Pine.LNX.4.44.0308191701070.14753-100000@ece.iisc.ernet.in>
References: <20030819110447.C1760EB9A@mail.iocaine.com>
	<Pine.LNX.4.44.0308191701070.14753-100000@ece.iisc.ernet.in>
Message-ID: <20030820011735.GA2352@mail.bii.a-star.edu.sg>

hi,

u may wana try to get more of this info from IEEE standards,  
   http://ieee.org (zone: wireless)

to look for the standard spec for IEEE802.11 you may find the 
stuffs you mention below.

if u need actual specs of a product or brand that supports 802.11, 
you'll need to get it from the vendors.


cheers,
yanghwee

On 2003-08-19 17:04:55, Anand S. Katti <askatti at ece.iisc.ernet.in> wrote:

> Dear sir,
> 
> Im sorry if this post is not relevant to the current list. But I need the 
> information on 802.11 in mathematical way.
> 
> Like I want to know the mathematical relation between RECEIVER 
> SENSITIVITY, RANGE, MTBF, RATE, S/N RATIO, Txpower, Rxpower, etc..
> 
> Could anyone suggest me any link or books to get through this?
> Well i know the definition of these above terms but if want to do 
> programing, then i shudbe knowing the mathematical relation between them.
> 
> I hope you have the answer.
> 
> -- 
> --------------.				
> With Regards,   
> Anand S. Katti
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap



From Kashif.Bhatti  Tue Aug 19 23:16:24 2003
From: Kashif.Bhatti (Kashif Bhatti)
Date: Wed, 20 Aug 2003 16:16:24 +1000
Subject: HOST AP - A Question from a beginner
References: <Pine.LNX.4.44.0308191701070.14753-100000@ece.iisc.ernet.in>
Message-ID: <000b01c366e2$a0de9690$4262ea84@Hakidu>

Dear All,

I will be happy to get feed back from you all on my problem.

Currently I am doing research on wireless location. I use a simple setup
where I have an Orinoco Gold wireless LAN card and I use a sniffer
program like Orinico Client Manager to extract signal strength data
from a wireless access point (real access point). I use a laptop running
windows 2000. I only have access to one wireless access point and I was
 thinking if it will be possible to use HOST AP to create a number of mobile
acess points (thats what HOST AP does - right ?).

Question:
Suppose I install Linux as the operating system on another laptop
and use a prism chipset based card and install HOST AP, will it
be POSSIBLE for me to treat this mobile access point similar to
the wireless access point that I am already experimenting on.

PART A:
If I get HOST AP working on the laptop runing Linux, and I
use my laptop that has a Orinoco Gold wireless card. Can I extract
signal strength data using the Orinoco client manager from the mobile
access point created with HOST AP, as I do with the real wireless
access point ?

PART B:
Or will I have to use Wireless Tools to extract signal strength data
from the cleint laptop installed with Orinoco Gold wireless card, via
the laptop installed with HOST AP ?

As a summary, I want to use my windows 2000 laptop as a client machine
that extracts signal strength data using ORINOCO Client manager
from the  mobile access point using  installed with HOST AP.

All help will be apreciated,

Kind regrads,

Kashif






From Kashif.Bhatti  Wed Aug 20 00:00:09 2003
From: Kashif.Bhatti (Kashif Bhatti)
Date: Wed, 20 Aug 2003 17:00:09 +1000
Subject: Urgent Help Needed, please
Message-ID: <001301c366e8$b3bf2440$4262ea84@Hakidu>

Dear All,

My experimental setup consists of the following:

1 - Client laptop, Windows 2000, Orinoco Gold Wireless Card, Orinoco CLient
Manager (for extracting signal strength data from a wireless access point).

2 - A REAL wireless access point.

3 - Host AP laptop, Redhat 7.0, Prism based wireless card.

In my experiments I extract signal strenth with my client laptop from a real
wireless
access point, using Orinoco client manager software. The signal strength is
stored as
follows in a log file:

,,Start time      ,End time        ,BSSID       ,  Ch,  Sl,  Nl,  Snr, AP
Name
,,2003/07/26-21:06,2003/07/26-21:06,00022D22F930,   3, -51, -94,  43,  Mall

QUESTION:
I am thinking of using additional wireless access points and read about
mobile Host AP. If I get Host AP running on Linux (I hope), will it be
possible for me to extract signal strenth with my client laptop (windows
2000) from the beacons transmitted by the Host AP laptop ?

Regards,

Kashif




From vda  Wed Aug 20 07:03:32 2003
From: vda (Denis Vlasenko)
Date: Wed, 20 Aug 2003 17:03:32 +0300
Subject: SMP report
References: <3F3F57EF.7020002@bigpond.com> 
Message-ID: <200308201403.h7KE3XL20929@Port.imtp.ilyichevsk.odessa.ua>

On 18 August 2003 08:26, Denis Vlasenko wrote:
> On 17 August 2003 13:24, James Harper wrote:
> > I'm running 2.6.0-test3 with the latest cvs version of hostap on an SMP 
> > system and it appears much more stable than previous versions. I just 
> > tried a flood ping for a few minutes and the only error I got was:
> > 
> > Aug 17 20:19:17 portal kernel: wlan0: hfa384x_cmd_issue: cmd reg was 
> > busy for 1 usec
> > Aug 17 20:20:53 portal kernel: wlan0: detected fid change (try=0, 
> > reg=0044): 0166 a5a4 0166
> > Aug 17 20:20:59 portal kernel: wlan0: detected fid change (try=0, 
> > reg=0040): 0000 03d6 03d6
> > 
> > which probably isn't good but previously I would be getting card resets 
> > and/or crashes etc all over the place.
> 
> Hmm I will hack together a patch because I believe
> those 'fid change' messages indicate a locking bug.
> Hopefully today.

This is it. Will try to catch SMP race condition.

The interface is rather simple: printk_trace()
prints events recorded in a circular buffer,
mark_in_trace("Some text") records event.
Event is (jiffies,cpu,text) triple.

Only compile tested.
--
vda

--- hostap_hw.c.orig	Wed Aug  6 05:50:00 2003
+++ hostap_hw.c	Wed Aug 20 16:59:46 2003
@@ -2199,6 +2199,43 @@
  * and will try to get the correct fid eventually. */
 #define EXTRA_FID_READ_TESTS
 
+#ifdef EXTRA_FID_READ_TESTS
+struct trace {
+        int cpu;
+        int jiffy;
+        const char *event;
+};
+static struct trace tracebuf[16];
+static int tracepos=0;
+spinlock_t tracelock = SPIN_LOCK_UNLOCKED;
+#define TRACESZ (sizeof(tracebuf)/sizeof(tracebuf[0]))
+
+static void printk_trace(void) {
+        int i,flags;
+        spin_lock_irqsave(&tracelock,flags);
+        i = tracepos;
+        do {
+                struct trace *p = tracebuf+i;
+                printk("time:%d cpu:%d event:%s\n", p->jiffy, p->cpu, p->event);
+                i = (i+1)%TRACESZ;
+        } while(i!=tracepos);
+        spin_unlock_irqrestore(&tracelock,flags);
+}
+
+static void mark_in_trace(const char* event) {
+        int flags;
+        struct trace *p;
+
+        spin_lock_irqsave(&tracelock,flags);
+        p = tracebuf+tracepos;
+        tracepos = (tracepos+1)%TRACESZ;
+        p->jiffy = jiffies;
+        p->cpu = smp_processor_id();
+        p->event = event;
+        spin_unlock_irqrestore(&tracelock,flags);
+}
+#endif
+
 static inline u16 prism2_read_fid_reg(struct net_device *dev, u16 reg)
 {
 #ifdef EXTRA_FID_READ_TESTS
@@ -2216,6 +2253,8 @@
 		printk(KERN_DEBUG "%s: detected fid change (try=%d, reg=%04x):"
 		       " %04x %04x %04x\n",
 		       dev->name, i, reg, val, val2, val3);
+		printk_trace();
+
 		if ((val == val2 || val == val3) && val != 0)
 			return val;
 		if (val2 == val3 && val2 != 0)
@@ -2957,6 +2996,10 @@
 	local_info_t *local = (local_info_t *) dev->priv;
 	int events = 0;
 	u16 ev;
+
+#ifdef EXTRA_FID_READ_TESTS
+        mark_in_trace("prism2_interrupt");
+#endif
 
 	prism2_io_debug_add(dev, PRISM2_IO_DEBUG_CMD_INTERRUPT, 0, 0);
 



From erich  Wed Aug 20 09:06:02 2003
From: erich (Erich Schubert)
Date: Wed, 20 Aug 2003 18:06:02 +0200
Subject: A couple of Problems with hostap and 802.1x
Message-ID: <20030820160602.GA7888@legolas.drinsama.de>

Hello,
i'm playing around with hostap and 802.1x, but i'm running into a few
problems.

What is working for me:
EAP-MD5 and EAP-TSL work with hostapd, freeradius and win2k client
AND with WEP disabled (i think i got fixed WEP working, too). I can't
get dynamic rekeying to work.

Well, that leads to my questions already. ;)
- xsupplicant: using the same certificates i can't get it to work. It
sends out the user name; on the machine running hostapd i do see the EAP
Challenge being sent out, on the client i don't see it coming in with
ethereal. I guess that is why xsupplicant doesn't reply. Any ideas?

- dynamic wep rekeying with EAP-TSL and win2k. Does this work? when i
enable rekeying in hostapd authentication fails:
wlan0: encryption configured, but RX frame not encrypted (SA=...)
i guess that is the reply frame.

Another question: When 802.11i is finished; are there people working on
implementing these for linux already? I think it's too difficult for me
(i have way too little knowledge at this layer) but i might need it.

Thanks.

Greetings,
Erich Schubert
-- 
    erich@(vitavonni.de|debian.org)    --    GPG Key ID: 4B3A135C    (o_
        The best things in life are free: Friendship and Love.       //\
  Es gibt wenig aufrichtige Freunde. Die Nachfrage ist auch gering.  V_/_
                    --- Marie von Ebner-Eschenbach



From tanyh  Wed Aug 20 17:55:41 2003
From: tanyh (Yang-Hwee TAN)
Date: Thu, 21 Aug 2003 08:55:41 +0800
Subject: [lsantos@pd3.com.br: Re: 802.11 mathematical model]
Message-ID: <20030821005541.GA12068@mail.bii.a-star.edu.sg>

u've got the mail sent to the wrong person, leonardo.
anyway, here's the forwarded message for Anand S. Katti 
read on...


-Yanghwee

----- Forwarded message from Leonardo Pereira Santos <lsantos at pd3.com.br> -----

From: Leonardo Pereira Santos <lsantos at pd3.com.br>
To: Yang-Hwee TAN <tanyh at bii.a-star.edu.sg>
Subject: Re: 802.11 mathematical model
Date: Wed, 20 Aug 2003 18:49:46 -0300

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

	I think there's a propagation model for 802.11, like the reflective model 
used to place cell phone radio bases, but I have no idea where to get it. I 
assume you are talking about the phisics of it.
	And about what I learned in college about radio propagation, there's no easy 
relation between the TX power and rcv power, as this depends on the 
propagation model of radio of this frequencies and modulation schemes, like 
DSSS. Try Electrical Engineering books on radio propagation. ARRL might have 
something more practical on 802.11, so taking a look at the ARRL site for 
bibliography does not hurt.
	What you need these for? If you say exactly what you need, perhaps some is 
able to help you further. Cheers!

On Tuesday 19 August 2003 22:17, Yang-Hwee TAN wrote:
> hi,
>
> u may wana try to get more of this info from IEEE standards,
>    http://ieee.org (zone: wireless)
>
> to look for the standard spec for IEEE802.11 you may find the
> stuffs you mention below.
>
> if u need actual specs of a product or brand that supports 802.11,
> you'll need to get it from the vendors.
>
>
> cheers,
> yanghwee
>
> On 2003-08-19 17:04:55, Anand S. Katti <askatti at ece.iisc.ernet.in> wrote:
> > Dear sir,
> >
> > Im sorry if this post is not relevant to the current list. But I need the
> > information on 802.11 in mathematical way.
> >
> > Like I want to know the mathematical relation between RECEIVER
> > SENSITIVITY, RANGE, MTBF, RATE, S/N RATIO, Txpower, Rxpower, etc..
> >
> > Could anyone suggest me any link or books to get through this?
> > Well i know the definition of these above terms but if want to do
> > programing, then i shudbe knowing the mathematical relation between them.
> >
> > I hope you have the answer.
> >
> > --
> > --------------.
> > With Regards,
> > Anand S. Katti
> >
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

- -- 
This is Linux country.
On a quiet night, you can hear Windows reboot.

Leonardo Pereira Santos
Engenheiro de Projetos
PD3 Tecnologia
av. Par? 330/202
(51) 3337 1237

Today Fortune tells us:
You too can wear a nose mitten.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/Q+z68uAMCTjfaxIRAlNmAJ0T5zpSOw+dLtGaMZJs0Ym9nbSYKACaA27j
YIKBnaVS0kEDS9AxrV5pRFo=
=TFKR
-----END PGP SIGNATURE-----


----- End forwarded message -----



From imp  Wed Aug 20 20:04:17 2003
From: imp (imp)
Date: Thu, 21 Aug 2003 12:04:17 +0900
Subject: firmware problem.
Message-ID: <005e01c36790$ec439730$d200a8c0@Snoopy>

Dear all

I already issue the "commnd still in list" error..
and I found the situation why it occur !!

with PRISM 2.5 or 3.0 card up to 1.5.6 firmware work very well.  
I mean, If STA link hostap then hostap has been reset (turn off and the turn on), the STA still can re-association with that hostap.

but, using above 1.5.6, 1.6.3, 1.7.2, 1.7.4 for example, 
above same test always failed.. I thinks It's must be prism firmware bug.. isn't it ? 

Thanks for your attention, and welcome to any comment.

Bernard... 




From askatti  Thu Aug 21 02:26:49 2003
From: askatti (Anand S. Katti)
Date: Thu, 21 Aug 2003 14:56:49 +0530 (IST)
Subject: hostAP vs Dedicated AP
Message-ID: <Pine.LNX.4.44.0308211449370.19687-100000@ece.iisc.ernet.in>

Dear All,

With help generous suggestions of you all, i was able to successfully 
install the hostAP drivers on my RHL8.0	box.

Now I want to do a feature comparison of hostAP and any dedicated ACCESS 
POINT.

like, i have DLINK DWL-900AP+, I would be doing a comparison of the 
featuers  supported by this and (Desktop machine acting as access 
point with ) hostAP.

considered features are 
1. WEP or equivalent protocols supported.
2. capability to host multiple BSS names.
3. packet forwarding latencies.
4. range.
5. No. of hosts supported.
6. any other added advantages.

I wud be greatfukl to you all if any body tell me if you have already dont 
these conmparison or if there is any comparison table alredy in existence ?

Waiting for your respones.

Thankin you,


-- 
--------------.				
With Regards,   
Anand S. Katti




From andreaf  Thu Aug 21 08:18:40 2003
From: andreaf (Andrea G. Forte)
Date: Thu, 21 Aug 2003 11:18:40 -0400 (EDT)
Subject: HostAP source code?
Message-ID: <200308211518.h7LFIeDs003788@marta.cs.columbia.edu>

Any of you guys know where I can find the hostAP main source code and in what 
kind of modules the driver is divided?
Thank you to everyone.
Andrea




From andreaf  Thu Aug 21 11:25:27 2003
From: andreaf (Andrea G. Forte)
Date: Thu, 21 Aug 2003 14:25:27 -0400 (EDT)
Subject: HostAP source?
Message-ID: <200308211825.h7LIPRRe009392@cisalpino.cs.columbia.edu>

Any of you guys can tell me how to find the hostAP main Source code? Could you 
also tell me in what modules the HostAp is divided into?
Thanks,
Andrea




From lcaeiro  Thu Aug 21 17:03:25 2003
From: lcaeiro (caeiro)
Date: Fri, 22 Aug 2003 01:03:25 +0100
Subject: resource temporarily unavailable
Message-ID: <002401c36840$cf7f2dc0$6401a8c0@home>


Hi,

I'm trying to test some modifications I made in hostap driver to control de card tx buffer. I'm using a counter that is increased when prism2_transmit is called and decreased when prism2_tx_ev or prism2_tx_exc is called to know how many messages is in tx buffer card. To test this mechanism I'm using Mgen to generate some UDP traffic, but when I increase the flow tx rate I receive the following message:

            Udp socket:: SendTo( ) : send to ( ) error: resource temporarily unavailable              
 
What could be the cause of this messages? On driver (dmesg) I haven't any error or information message.

Thanks in advance

LC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030822/3524281f/attachment-0001.htm 


From lcaeiro  Thu Aug 21 14:48:39 2003
From: lcaeiro (caeiro)
Date: Thu, 21 Aug 2003 22:48:39 +0100
Subject: resource temporarily unavailable
Message-ID: <003801c3682d$fbeebcd0$6401a8c0@home>

Hi,

I'm trying to test some modifications I made in hostap driver to control de card tx buffer. I'm using a counter that is increased when prism2_transmit is called and decreased when prism2_tx_ev or prism2_tx_exc is called to know how many messages is in tx buffer card. To test this mechanism I'm using Mgen to generate some UDP traffic, but when I increase the flow tx rate I receive the following message:

            Udp socket:: SendTo( ) : send to ( ) error: resource temporarily unavailable              

What could be the cause of this messages? On driver (dmesg) I haven't any error or information message.

Thanks in advance

LC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20030821/a79e656e/attachment-0001.htm 


From askatti  Thu Aug 21 21:47:14 2003
From: askatti (Anand S. Katti)
Date: Fri, 22 Aug 2003 10:17:14 +0530 (IST)
Subject: power levels/ tx power levels
Message-ID: <Pine.LNX.4.44.0308221015110.14283-100000@ece.iisc.ernet.in>


Dear All,

Please answer the follwoing questions.

1. Does the hostAP support multiple essid?
2. Can we set the different tx power levels?
3. Is there any way i can set the above two mentioned pooints? i mean in 
the source code or so?

Eagerly waiting.

-- 
--------------.				
With Regards,   
Anand S. Katti




From vda  Thu Aug 21 22:55:52 2003
From: vda (Denis Vlasenko)
Date: Fri, 22 Aug 2003 08:55:52 +0300
Subject: how to make my AP work?
In-Reply-To: <000901c36586$25b1faf0$7bf7748c@gigabyteli>
References: <20030818120553.38EFFEA99@mail.iocaine.com>
	<000901c36586$25b1faf0$7bf7748c@gigabyteli>
Message-ID: <200308220556.h7M5tsL12004@Port.imtp.ilyichevsk.odessa.ua>

On 18 August 2003 15:42, ??? wrote:
> > HostAP doesn't work with tertiary firmware.  It makes secondary
> > firmware act as an access point.  If you want to use tertiary firmware,
> > use linux-wlan-ng.
> > Next time please report version of the software that gives you the
> > problem.  Also, a step-by-step explanation of what you are doing would be
> > helpful.  Relevant parts of the kernel log (as reported by dmesg) may be
> > useful as well.
> > -Regards,
> > -Pavel Roskin
> It's very sorry. I dont say clearly. I use Avaya's wireless PCMCIA card.
> so I use HermesAP-0.2. Now, I have installed heremesAP and made it work.
> Other PC's wireless device can connect to my wireless interface.
> My problem is how to make my AP like bridge, so that others connected to my
> AP can
> connected to Internet.
> Someone tells me to setup NAT or makes my wire card to be shared with all
> devices.
> However I am newbie on wireless and network. So I need more detail to do
> that.
> Hope people can teach me how to do that or where have information about
> that.

http://www.lartc.org/
--
vda



From vda  Thu Aug 21 23:08:29 2003
From: vda (Denis Vlasenko)
Date: Fri, 22 Aug 2003 09:08:29 +0300
Subject: SMP report
In-Reply-To: <20030819025600.GG3359@jm.kir.nu>
References: <3F3F57EF.7020002@bigpond.com> <20030819025600.GG3359@jm.kir.nu>
Message-ID: <200308220608.h7M68UL12118@Port.imtp.ilyichevsk.odessa.ua>

On 19 August 2003 05:56, Jouni Malinen wrote:
> Getting those fid reads returning proper values will certainly remove
> quite a few hw_resets and will thus help with the stability. The other
> issue, i.e., system lockup on hw_reset, may however still exist. I
> actually have couple of patches that could be tested on top of 0.0.4
> release so that we could try to find a way to avoid the crash. If
> someone with an SMP system using hostap_pci is willing to test these,
> please let me know and I'll send the patches. Please note that testing
> these will most probably end up crashing your system number of times..

Maybe it will be faster and more visible to just post the pathes
to the list with appropriate big fat warning. Saves email RTT.
--
vda



From pfoy  Fri Aug 22 08:23:39 2003
From: pfoy (Foy, Patrick)
Date: Fri, 22 Aug 2003 11:23:39 -0400
Subject: Primary Firmware Download
Message-ID: <EF5625F9F795C94BA28B150706A21548A053F8@MAIL>

Pavel,

Thanks for all your help on the RAM download!

I gotten the primary and secondary RAM download to work pretty reliably, but
I am having issues with the PDA.  

I've changed a few things with the download procedure, so that it is
performed in a two step process.  

1. In an offline procedure, the prism2_srec utility generates a compilable
header file (primary_fw.h or secondary_fw.h) that is compiled into prism2
driver

2. At run time, the hostap_download reads the firmware from global memory
and then downloads the content into the WLAN card.

We have an embedded application that requires all the download work to be
done in the driver because if the card goes through a reset, the application
might not know about the reset and therefore won't reload the firmware into
RAM.

The prism2_srec utility can be run on any machine to auto generate the
primary_fw.h and secondary_fw.h files.  However, the PDA information is
obtained from the WLAN card that is used to create the files and this PDA is
added to the secondary_fw.h.  Part of the PDA is the mac address.  After
loading the firmware on multiple AP devices, we discovered that all units
had the same MAC address (ooops!).

I changed the download code to read the pda before the download begins and
then restore the pda after the download completes.  This fixes the mac
address problem, but the reported version is the previous version
information.

Any ideas how I can update the PDA to fix the version information?

Thanks.

Patrick

      

-----Original Message-----
From: Foy, Patrick 
Sent: Thursday, July 31, 2003 4:29 PM
To: 'Pavel Roskin'
Subject: RE: Primary Firmware Download


Pavel,

We are shipping APs with Senao cards (2511CD-Plus), some with primary
firmware 1.0.5 and others with 1.1.0.  We need secondary 1.7.4 for WDS,
Enhanced security, scanning, etc which requires primary of 1.1.0 or newer.  

The reason that I need to upgrade the primary with hostap (either into RAM
or flash) is because we have shipped 100s of units and they need upgraded
"in the field" (and we don't want to open the cases to re-flash the cards
using winupdate).  I've read that updating the primary into flash isn't
reliable, so I wanted to take the least risky route, which is uploading to
RAM.

Upgrading the secondary into RAM seems very reliably, but loading only the
secondary firmware is only a solution for cards with primary 1.1.0.  I need
to find a solution that allows me to upgrade the older cards (primary 1.0.5)
with a primary version that supports a secondary version of 1.7.4

Thanks for your help.

Patrick
   


-----Original Message-----
From: Pavel Roskin [mailto:proski at gnu.org]
Sent: Thursday, July 31, 2003 4:03 PM
To: Foy, Patrick
Cc: hostap at shmoo.com
Subject: RE: Primary Firmware Download


On Thu, 31 Jul 2003, Foy, Patrick wrote:

> We've been avoiding the primary firmware download issue for our project,
but
> have finally decided to re-visit the issue.  Since this last email, have
you
> been able to download the primary firmware into RAM successfully (and
> reliably) using the hostap driver and the prism2_srec utility?

No.  It doesn't work.  But I don't think you need it.  If you think you
need it, please give more details.  What kind of hardware are you talking
about?  What primary and secondary firmware do you have?  Why do you want
to upgrade primary firmware in the RAM?  What's wrong with flashing the
latest primary and secondary firmware?  Cannot you just load secondary
firmware into the RAM?

-- 
Regards,
Pavel Roskin



From andreaf  Fri Aug 22 14:00:40 2003
From: andreaf (Andrea G. Forte)
Date: Fri, 22 Aug 2003 17:00:40 -0400 (EDT)
Subject: Monitoring Management frames with HostAP???
Message-ID: <200308222100.h7ML0eDY006535@cisalpino.cs.columbia.edu>

Hi guys,
I am trying to monitor management frames with HostAP in monitoring mode 2 or 3.
I am also using ethereal.
Unfortunately I get a lot of LLC, ARP and UNKNOWN frames and no management 
frames. I am using the latest version of ethereal and hostAP....anybody can 
help?
Thanks a lot,
Andrea




From proski  Fri Aug 22 15:01:08 2003
From: proski (Pavel Roskin)
Date: Fri, 22 Aug 2003 18:01:08 -0400 (EDT)
Subject: Primary Firmware Download
In-Reply-To: <EF5625F9F795C94BA28B150706A21548A053F8@MAIL>
References: <EF5625F9F795C94BA28B150706A21548A053F8@MAIL>
Message-ID: <Pine.LNX.4.56.0308221744350.25879@marabou.research.att.com>

On Fri, 22 Aug 2003, Foy, Patrick wrote:

> We have an embedded application that requires all the download work to
> be done in the driver because if the card goes through a reset, the
> application might not know about the reset and therefore won't reload
> the firmware into RAM.

There is nothing wrong with having the complete firmware in the kernel
memory.  The alternative would be to generate a hotplug even and call
prism2_srec from hotplug.

If you load complete firmware images to the kernel, there is one more
issue.  If your changes to be integrated and maintained as part of HostAP,
please use the firmware download API.  You can keep firmware in memory if
you want, but it should be loaded rather than compiled into the driver for
legal reasons.

> I changed the download code to read the pda before the download begins and
> then restore the pda after the download completes.  This fixes the mac
> address problem, but the reported version is the previous version
> information.
>
> Any ideas how I can update the PDA to fix the version information?

I have no idea how you "restore the PDA" and what it means.  If you are
plugging the image in the driver, it's better that you read the PDA from
NVRAM (non-volatile RAM), as it's done in linux-wlan-ng.  You shouldn't
write to PDA.

I'm afraid you misunderstand the plugging procedure.  If you rely on
prism2_srec to plug the image, you are doing it wrong.  If you put
firmware to the kernel space, you should plug the image with the PDA from
the card.  This also means that the driver should be aware of PDRs.

You can look at a similar implementation for Symbol cards, but I didn't
implement firmware API yet: http://www.red-bean.com/~proski/symbol/

By the way please don't top-post.  It makes it inconvenient to quote your
messages.

-- 
Regards,
Pavel Roskin



From hajo  Fri Aug 22 15:46:54 2003
From: hajo (Hans-Joachim Klingshirn)
Date: Sat, 23 Aug 2003 00:46:54 +0200
Subject: hostap 0.0.4/NICID 8002 wep trouble
Message-ID: <20030823004654.4e85c0ce.hajo@hajo.org>

Hi,

I am trying to enable wep on a wireless lan connection between two
computers running hostap 0.0.4, with no success so far.

The hardware in the ap (pcmcia card in plx adapter, hostap_plx):

hostap_diag wlan0 output:
NICID: id=0x8002 v1.0.0 (HWB3163-01,02,03,04 Rev A)
PRIID: id=0x0015 v0.3.0
STAID: id=0x001f v0.7.6 (station firmware)

lspci output:
00:0c.0 Network controller: Standard Microsystems Corp [SMC] SMC2602W
EZConnect / Addtron AWA-100 (rev 02)

The hardware in the client (minipci-card, hostap_pci):

hostap_diag wlan0 output
NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.1.0
STAID: id=0x001f v1.4.9 (station firmware)

lspci output
01:02.0 Network controller: Harris Semiconductor Prism 2.5 Wavelan chipset
(rev 01)

Kernel is 2.4.21, wireless tools are v26, interfaces are v14(client) and v15(ap)

Problem: When loading hostap on the ap, it disables card-based wep, so I
run hostapd on the ap box. Without activating wep, everything works fine.
When activating wep with a 40bit key, no data can be transmitted.
hostap(d) on the ap box does not give any log messages concerning wep (log
level set to maximum). The hostap.conf on the ap box is the standard
config file as in the 0.0.4 distribution, only log levels and ssid have
been changed.

The client box already tested ok with hostap and wep when used in another setup,
so the problem is with the ap.

Concerning the wep problem: do I make any obvious mistakes? How can I debug the 
problem properly?

Concerning the prism card in the access point: NICID is 8002, the firmware is very old. I read
a bit about flashing the firmware, but the NICID 8002 does not show up in the compatibility 
charts for firmwares, as linked to from the firmware flashing mini-howto. What strange card do 
I have here? 

TIA,

HaJo Klingshirn

-- 
Will work for bandwidth.



From proski  Fri Aug 22 17:17:00 2003
From: proski (Pavel Roskin)
Date: Fri, 22 Aug 2003 20:17:00 -0400 (EDT)
Subject: HostAP source?
In-Reply-To: <200308211825.h7LIPRRe009392@cisalpino.cs.columbia.edu>
References: <200308211825.h7LIPRRe009392@cisalpino.cs.columbia.edu>
Message-ID: <Pine.LNX.4.56.0308222014020.26205@marabou.research.att.com>

On Thu, 21 Aug 2003, Andrea G. Forte wrote:

> Any of you guys can tell me how to find the hostAP main Source code?

Go to google.com and search for "hostap source code" (without quotes).
The URL you are looking for is within first 10 hits.

> Could you also tell me in what modules the HostAp is divided into?

Once you find the source code, unpack it.  There is a file called
driver_source.txt.  It answers your question.

-- 
Regards,
Pavel Roskin



From williamt  Fri Aug 22 17:40:15 2003
From: williamt (William Tai)
Date: Fri, 22 Aug 2003 17:40:15 -0700
Subject: hostcan problem
Message-ID: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>

Hi All:

I try to scan all neighboring APs.
However the number of APs I scanned is less than the number scanned by
another clients.
Does ant body have the same experience?

Thanx
William




From proski  Fri Aug 22 17:35:57 2003
From: proski (Pavel Roskin)
Date: Fri, 22 Aug 2003 20:35:57 -0400 (EDT)
Subject: hostap 0.0.4/NICID 8002 wep trouble
In-Reply-To: <20030823004654.4e85c0ce.hajo@hajo.org>
References: <20030823004654.4e85c0ce.hajo@hajo.org>
Message-ID: <Pine.LNX.4.56.0308222022160.26305@marabou.research.att.com>

On Sat, 23 Aug 2003, Hans-Joachim Klingshirn wrote:

> Concerning the prism card in the access point: NICID is 8002, the
> firmware is very old. I read a bit about flashing the firmware, but the
> NICID 8002 does not show up in the compatibility charts for firmwares,
> as linked to from the firmware flashing mini-howto. What strange card do
> I have here?

I don't think your problems with be discussed seriously until you upgrade.

Please give links when referring to documentation.  See Mini-howto on
Flashing Intersil Prism Chipsets: http://linux.junsun.net/intersil-prism/

There is no word "chart" in that howto.  Instead of compatibility charts,
use prism2_srec without "-r" or "-f" and it will tell you if the firmware
is compatible.

-- 
Regards,
Pavel Roskin



From jkmaline  Fri Aug 22 17:51:43 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 17:51:43 -0700
Subject: Primary Firmware Download
In-Reply-To: <EF5625F9F795C94BA28B150706A21548A053F8@MAIL>
References: <EF5625F9F795C94BA28B150706A21548A053F8@MAIL>
Message-ID: <20030823005143.GA3435@jm.kir.nu>

On Fri, Aug 22, 2003 at 11:23:39AM -0400, Foy, Patrick wrote:

> 2. At run time, the hostap_download reads the firmware from global memory
> and then downloads the content into the WLAN card.
> 
> We have an embedded application that requires all the download work to be
> done in the driver because if the card goes through a reset, the application
> might not know about the reset and therefore won't reload the firmware into
> RAM.

You might want to take a look at the CVS version of the Host AP driver
and persistent mode for volatile download.. Adding '-p' flag for the
prism2_srec will request the driver to keep a copy of the image in
kernel memory and automatically downlod it in case of hw_reset.

> The prism2_srec utility can be run on any machine to auto generate the
> primary_fw.h and secondary_fw.h files.

Please note that there are some issues with linking in non-GPL code to
the kernel modules and I would never accept this kind of change to be
added to the Host AP distribution.

> Any ideas how I can update the PDA to fix the version information?

By plugging the firmware properly using the PDA information of the card
that is going to use the image and not by using the same PDA for all
downloads.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Aug 22 17:55:53 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 17:55:53 -0700
Subject: hostcan problem
In-Reply-To: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>
References: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>
Message-ID: <20030823005553.GB3435@jm.kir.nu>

On Fri, Aug 22, 2003 at 05:40:15PM -0700, William Tai wrote:

> I try to scan all neighboring APs.
> However the number of APs I scanned is less than the number scanned by
> another clients.

Please include more information.. Which Host AP version did you use?
What commands did you use to request a scan and how did you read the
results? Are you using Master (Host AP) or Managed (station) mode? What
is your station firmware version?

-- 
Jouni Malinen                                            PGP id EFC895FA



From proski  Fri Aug 22 17:56:48 2003
From: proski (Pavel Roskin)
Date: Fri, 22 Aug 2003 20:56:48 -0400 (EDT)
Subject: Urgent Help Needed, please
In-Reply-To: <001301c366e8$b3bf2440$4262ea84@Hakidu>
References: <001301c366e8$b3bf2440$4262ea84@Hakidu>
Message-ID: <Pine.LNX.4.56.0308222051220.26487@marabou.research.att.com>

On Wed, 20 Aug 2003, Kashif Bhatti wrote:

> Dear All,

You are seriously risking to have your message incorrectly classified by
your choice of subject and greeting :-)

> In my experiments I extract signal strenth with my client laptop from a
> real wireless access point, using Orinoco client manager software.
[snip]
> QUESTION:
> I am thinking of using additional wireless access points and read about
> mobile Host AP. If I get Host AP running on Linux (I hope), will it be
> possible for me to extract signal strenth with my client laptop (windows
> 2000) from the beacons transmitted by the Host AP laptop ?

The format of beacons is mandated by 802.11 standard and it's the same,
whether it's emitted by HostAP of some other AP.  The signal strength is
measured on the client.  So I'm quite sure that you can measure signal
strength of all beacons, regardless of their provenance.

-- 
Regards,
Pavel Roskin



From proski  Fri Aug 22 17:59:42 2003
From: proski (Pavel Roskin)
Date: Fri, 22 Aug 2003 20:59:42 -0400 (EDT)
Subject: hostcan problem
In-Reply-To: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>
References: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>
Message-ID: <Pine.LNX.4.56.0308222057120.26500@marabou.research.att.com>

On Fri, 22 Aug 2003, William Tai wrote:

> Hi All:
>
> I try to scan all neighboring APs.
> However the number of APs I scanned is less than the number scanned by
> another clients.
> Does ant body have the same experience?

Yes.  Firmware 1.3.4 has this bug.  Firmware versions 1.5.6 and 1.7.4 are
known to be OK.

Also, make sure that you have no ESSID specified, or you will get only APs
with that ESSID.  Use "iwconfig wlan0 essid any".

-- 
Regards,
Pavel Roskin



From jkmaline  Fri Aug 22 18:01:27 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 18:01:27 -0700
Subject: hostap 0.0.4/NICID 8002 wep trouble
In-Reply-To: <20030823004654.4e85c0ce.hajo@hajo.org>
References: <20030823004654.4e85c0ce.hajo@hajo.org>
Message-ID: <20030823010127.GC3435@jm.kir.nu>

On Sat, Aug 23, 2003 at 12:46:54AM +0200, Hans-Joachim Klingshirn wrote:

> Problem: When loading hostap on the ap, it disables card-based wep, so I
> run hostapd on the ap box.

I don't understand this logic here.. Running hostapd (vs. kernel side
802.11 management) does not have anything to do with whether WEP is
being done in the hardware of software. Host AP driver is using
host-based software implementation of WEP if the firmware version is
known to have issues with hardware "accelerated" WEP. This happens
whether you use hostapd or not.

> When activating wep with a 40bit key, no data can be transmitted.
> hostap(d) on the ap box does not give any log messages concerning wep (log
> level set to maximum). The hostap.conf on the ap box is the standard
> config file as in the 0.0.4 distribution, only log levels and ssid have
> been changed.

Running hostapd with static WEP keys is something that I have never
really tested properly. I would recommend first testing WEP without
hostapd to keep the setup as simple as possible.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Aug 22 18:03:57 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 18:03:57 -0700
Subject: Monitoring Management frames with HostAP???
In-Reply-To: <200308222100.h7ML0eDY006535@cisalpino.cs.columbia.edu>
References: <200308222100.h7ML0eDY006535@cisalpino.cs.columbia.edu>
Message-ID: <20030823010357.GD3435@jm.kir.nu>

On Fri, Aug 22, 2003 at 05:00:40PM -0400, Andrea G. Forte wrote:

> I am trying to monitor management frames with HostAP in monitoring mode 2 or 3.
> I am also using ethereal.
> Unfortunately I get a lot of LLC, ARP and UNKNOWN frames and no management 
> frames. I am using the latest version of ethereal and hostAP....anybody can 
> help?

What version of libpcap are you using? Which commands did you use to
enable monitoring mode?

-- 
Jouni Malinen                                            PGP id EFC895FA



From williamt  Fri Aug 22 18:28:11 2003
From: williamt (William Tai)
Date: Fri, 22 Aug 2003 18:28:11 -0700
Subject: hostcan problem
References: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>
	<20030823005553.GB3435@jm.kir.nu>
Message-ID: <004c01c36915$d0fac170$e6f0c53f@williamt>


----- Original Message ----- 
From: "Jouni Malinen" <jkmaline at cc.hut.fi>
To: <hostap at shmoo.com>
Sent: Friday, August 22, 2003 5:55 PM
Subject: Re: hostcan problem


> On Fri, Aug 22, 2003 at 05:40:15PM -0700, William Tai wrote:
> 
> > I try to scan all neighboring APs.
> > However the number of APs I scanned is less than the number scanned by
> > another clients.
> 
> Please include more information.. 
Which Host AP version did you use?

Sorry I do not know.

> What commands did you use to request a scan and how did you read the
> results?

request a scan
int hostap_read_ap_info(struct device *dev)
{
 struct hfa384x_hostscan_request scan_req;
 u16 rate;
 int ret = 0;
 INT oldLevel;
 local_info_t *local = (local_info_t *) dev->priv;

 memset(&scan_req, 0, sizeof(scan_req));
 scan_req.channel_list = __constant_cpu_to_le16(0x000f/*0x3fff*/);
 rate = 2;//HFA384X_RATES_1MBPS;

 scan_req.txrate = cpu_to_le16(rate);
 /* leave SSID empty to accept all SSIDs */
oldLevel = NU_Control_Interrupts(NU_DISABLE_INTERRUPTS);
 if (local->iw_mode == IW_MODE_MASTER) {
  if (hostap_set_word(dev, HFA384X_RID_CNFPORTTYPE,
        HFA384X_PORTTYPE_BSS) ||
      local->func->reset_port(dev))
   printf("Leaving Host AP mode for HostScan failed\n\r");
 }
 if (local->func->set_rid(dev, HFA384X_RID_HOSTSCAN, &scan_req,
     sizeof(scan_req))) {
  printf("HOSTSCAN failed\n\r");
  ret = -EINVAL;
 }
NU_Control_Interrupts(oldLevel);
 NU_Sleep(400);
oldLevel = NU_Control_Interrupts(NU_DISABLE_INTERRUPTS);
 if (local->iw_mode == IW_MODE_MASTER) {
  if (hostap_set_word(dev, HFA384X_RID_CNFPORTTYPE,
        HFA384X_PORTTYPE_HOSTAP) ||
      local->func->reset_port(dev))
   printf("Returning to Host AP mode after HostScan failed\n\r");
 }
NU_Control_Interrupts(oldLevel);

 return ret;
}

read the result
#ifndef PRISM2_NO_DEBUG
 case HFA384X_INFO_HOSTSCANRESULTS:
  prism2_info_hostscanresults(local, buf, left);
  break;
#endif /* PRISM2_NO_DEBUG */


>Are you using Master (Host AP) or Managed (station) mode? What
> is your station firmware version?
>

HOSTAP mode


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



From jkmaline  Fri Aug 22 18:44:29 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 18:44:29 -0700
Subject: hostcan problem
In-Reply-To: <004c01c36915$d0fac170$e6f0c53f@williamt>
References: <002e01c3690f$1e6e31f0$e6f0c53f@williamt>
	<20030823005553.GB3435@jm.kir.nu>
	<004c01c36915$d0fac170$e6f0c53f@williamt>
Message-ID: <20030823014429.GD3226@jm.kir.nu>

On Fri, Aug 22, 2003 at 06:28:11PM -0700, William Tai wrote:

> > Which Host AP version did you use?
> 
> Sorry I do not know.

Hmm.. Well, I would suggest finding out which version it is, if you want
to get more support from me ;-). Based on the code you listed below, it
is a modified version of something. I have never seen the listed
function before. It looks like somethign that was based on code I have
written, but someone has decided that it should be indented in some
horrible way.. In addition, it seems to be ported to non-Linux
platform (Nucleus).

I would like to remind you that my code in Host AP driver has been
released under GPL and there are certain requirements in distributing
modified versions of it. If you happen to link it into something like
Nucleus and distribute the combined program, you would be required to
make the source code of all the components of this combined program
available under the same license..

>  scan_req.channel_list = __constant_cpu_to_le16(0x000f/*0x3fff*/);

You are only scanning channels 1..4 so if you have APs on other
channels, they are not shown..

> >Are you using Master (Host AP) or Managed (station) mode? What
> > is your station firmware version?
> 
> HOSTAP mode

You should note that the scanning functions in the firmware do not work
in Host AP and jumping to client mode for a short period of time is
horrible hack and is certainly not very reliable..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Aug 22 18:55:02 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 18:55:02 -0700
Subject: Urgent Help Needed, please
In-Reply-To: <Pine.LNX.4.56.0308222051220.26487@marabou.research.att.com>
References: <001301c366e8$b3bf2440$4262ea84@Hakidu>
	<Pine.LNX.4.56.0308222051220.26487@marabou.research.att.com>
Message-ID: <20030823015502.GE3226@jm.kir.nu>

On Fri, Aug 22, 2003 at 08:56:48PM -0400, Pavel Roskin wrote:
> On Wed, 20 Aug 2003, Kashif Bhatti wrote:
> 
> > Dear All,
> 
> You are seriously risking to have your message incorrectly classified by
> your choice of subject and greeting :-)

Hey, that got only 2.3 of required 5.0 points.. Maybe promising $30M to
anyone who helps with the questions would have been needed ;-).

> > In my experiments I extract signal strenth with my client laptop from a
> > real wireless access point, using Orinoco client manager software.

Is "real wireless access point" defined to be something like Orinoco AP
that can use proprietary Lucent protocol for some link statistics
reporting?

> The format of beacons is mandated by 802.11 standard and it's the same,
> whether it's emitted by HostAP of some other AP.  The signal strength is
> measured on the client.  So I'm quite sure that you can measure signal
> strength of all beacons, regardless of their provenance.

Yes, beacon strength should certainly be available. However, the Lucent
link test frames (WMP LinkTest) will not be handled in interoperable
way. Station firmware wants to eat these without letting host system
handle them. The latest STA firmware version might allow this to be
changed, but I don't know whether it would really be worth anyones time
to implement support for this.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Aug 22 19:05:22 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 19:05:22 -0700
Subject: A couple of Problems with hostap and 802.1x
In-Reply-To: <20030820160602.GA7888@legolas.drinsama.de>
References: <20030820160602.GA7888@legolas.drinsama.de>
Message-ID: <20030823020522.GF3226@jm.kir.nu>

On Wed, Aug 20, 2003 at 06:06:02PM +0200, Erich Schubert wrote:

> Well, that leads to my questions already. ;)
> - xsupplicant: using the same certificates i can't get it to work. It
> sends out the user name; on the machine running hostapd i do see the EAP
> Challenge being sent out, on the client i don't see it coming in with
> ethereal. I guess that is why xsupplicant doesn't reply. Any ideas?

Seeing hostapd debug log with at least debug=2 (or -dd in command line)
level could be helpful to find out what did not work.

> - dynamic wep rekeying with EAP-TSL and win2k. Does this work? when i
> enable rekeying in hostapd authentication fails:
> wlan0: encryption configured, but RX frame not encrypted (SA=...)
> i guess that is the reply frame.

It should work. How did you configure hostapd for this? With both
broadcast and unicast keys? Does EAP-TLS succeed in this setup or do you
get that frame drop messages already for an EAPOL packet?

> Another question: When 802.11i is finished; are there people working on
> implementing these for linux already?

Yes.

-- 
Jouni Malinen                                            PGP id EFC895FA



From imp  Fri Aug 22 20:45:43 2003
From: imp (imp)
Date: Sat, 23 Aug 2003 12:45:43 +0900
Subject: hostap with 1.7.4 ???
Message-ID: <009201c36929$08007850$d200a8c0@Snoopy>

Dear all

I already issue the "commnd still in list" error..
and I found the situation why it occur !!

with PRISM 2.5 or 3.0 card up to 1.5.6 firmware work very well.  
I mean, If STA link hostap then hostap has been reset (turn off and the turn on), the STA still can re-association with that hostap.

but, using above 1.5.6, 1.6.3, 1.7.2, 1.7.4 for example, 
above same test always failed.. I thinks It's must be prism firmware bug.. isn't it ? 

Thanks for your attention, and welcome to any comment.

Bernard... 




From jkmaline  Fri Aug 22 21:29:46 2003
From: jkmaline (Jouni Malinen)
Date: Fri, 22 Aug 2003 21:29:46 -0700
Subject: hostap with 1.7.4 ???
In-Reply-To: <009201c36929$08007850$d200a8c0@Snoopy>
References: <009201c36929$08007850$d200a8c0@Snoopy>
Message-ID: <20030823042946.GA3880@jm.kir.nu>

On Sat, Aug 23, 2003 at 12:45:43PM +0900, imp wrote:

> with PRISM 2.5 or 3.0 card up to 1.5.6 firmware work very well.  
> I mean, If STA link hostap then hostap has been reset (turn off and the turn on), the STA still can re-association with that hostap.
> 
> but, using above 1.5.6, 1.6.3, 1.7.2, 1.7.4 for example, 
> above same test always failed.. I thinks It's must be prism firmware bug.. isn't it ? 

I cannot reproduce this. I changed your setup script to first setup
wlan0 interface up and start hostapd and then run the iwconfig/iwpriv
commands. I associated a client station to the AP. Then I ejected the AP
card and reinserted it and ran the same setup script. Everything went
fine and STA associated successfully.

Can you try to make a bit simpler test case for this? Does the error
occur without hostapd?

-- 
Jouni Malinen                                            PGP id EFC895FA



From krose+hostap  Sat Aug 23 11:53:50 2003
From: krose+hostap (Kyle Rose)
Date: Sat, 23 Aug 2003 14:53:50 -0400
Subject: 802.1x automatic WEP key negotiation problems
Message-ID: <87u1886w8x.fsf@nausicaa.krose.org>

Last night, I successfully set up a HostAP/FreeRADIUS EAP/TLS
configuration on my firewall machine (PCMCIA->ISA bridge with a
Linksys WPC11 ver.3) and an xsupplicant configuration on my laptop
(Lucent Orinoco).

As far as I can tell, both cards have the latest firmware: 1.7.4 for
the Linksys, and whatever I managed to download from the Proxim
website the other day (maybe 8.10?).

At any rate, most everything works: the Linksys goes into AP mode,
shovels 802.1x frames from the laptop off to the hostapd, which then
contacts the FreeRADIUS server to initiate authentication, after which
the laptop is able to get DHCP request packets through to get an IP.
If the laptop doesn't have xsupplicant, or has an invalid certificate,
hostapd refuses to recognize its packets.  Sounds great.

However, nothing at all works when I try to turn on WEP key
negotiation.  Now, someone correct me if I'm wrong, but my impression
is that the xsupplicant and RADIUS server should together negotiate
some secure way for hostapd to send a WEP key to the laptop, initially
and perhaps at intervals, depending on whether one has re-keying
activated, no?  Well, when I activate the encryption in hostapd.conf
by setting:

wep_key_len_broadcast=5
wep_key_len_unicast=5

then nothing happens when I plug the Lucent card into the laptop and
start xsupplicant: I see *nothing* in the logs after hostapd
successfully starts up, even at hostapd's highest log level; and the
Lucent card's lights just blink periodically, but it doesn't even find
my LAN's ESSID.  The RADIUS server's configuration at this point is
moot, since hostapd never contacts it, presumably because it doesn't
see any of link negotiation frames from the laptop.

I've done the standard exhaustive-search things, like commenting out
one or the other of the above lines and restarting hostapd, to no
avail.  I have been searching for hours on the web, newsgroup, and
relevant mailing lists, also in vain.

Let me give you the output of some relevant commands while the laptop
is attempting (futilely) to get authenticated.  "yupa" is the firewall
machine containing the AP, and its LAN IP address is 192.168.16.1
(netmask 255.255.240.0).  Feel free to ask me for anything you think
would help debug this problem.

As an added bonus, if someone can help me solve this, I'll write a FAQ
Q&A for this problem so others won't bother you. :)

root at yupa:~# uname -a
Linux yupa 2.4.21 #1 Wed Aug 20 20:27:29 EDT 2003 i586 GNU/Linux

root at yupa:~# lsmod | grep host
hostap_cs              47964   2 
hostap                 69796   0  [hostap_cs]
hostap_crypt_wep        3244   1  (autoclean)
hostap_crypt            1520   0  [hostap hostap_crypt_wep]
ds                      6388   2  [hostap_cs]
pcmcia_core            43072   0  [hostap_cs ds i82365]

root at yupa:~# ifconfig
.
.
.
wlan0     Link encap:Ethernet  HWaddr 00:06:25:AB:9D:84  
          inet addr:192.168.16.1  Bcast:192.168.31.255  Mask:255.255.240.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:3 Base address:0x100 

wlan0ap   Link encap:UNSPEC  HWaddr 00-06-25-AB-9D-84-00-00-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:2290  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 b)  TX bytes:78 (78.0 b)
          Interrupt:3 Base address:0x100 

root at yupa:~# iwconfig
.
.
.
wlan0     IEEE 802.11b  ESSID:"valley-of-wind"  
          Mode:Master  Frequency:2.422GHz  Access Point: 00:06:25:AB:9D:84  
          Bit Rate:11Mb/s   Tx-Power:-15 dBm   Sensitivity=1/242700000  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:AFCC-CD41-B3 [2]   Security mode:open
          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

wlan0ap   IEEE 802.11b  ESSID:"valley-of-wind"  
          Mode:Master  Frequency:2.422GHz  Access Point: 00:06:25:AB:9D:84  
          Bit Rate:11Mb/s   Tx-Power:-15 dBm   Sensitivity=1/242700000  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:AFCC-CD41-B3 [2]   Security mode:open
          Power Management:off
          
wlan0sta  IEEE 802.11b  ESSID:"valley-of-wind"  
          Mode:Managed  Frequency:2.422GHz  Access Point: 00:00:00:00:00:00  
          Bit Rate:11Mb/s   Tx-Power:-15 dBm   Sensitivity=1/242700000  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:AFCC-CD41-B3 [2]   Security mode:open
          Power Management:off

root at yupa:~# hostap_crypt_conf -l wlan0
Default keys
  algorithm: WEP
  TX key idx: 2
  key 1:
  key 2: af cc cd 41 b3
  key 3:
  key 4:

root at yupa:~# for A in `prism2_param  | egrep '^[[:space:]]+[a-zA-z0-9]*:' | sed -e 's@^[[:space:]]*@@' -e 's@:.*@@'`; do echo -n "$A: "; prism2_param wlan0 $A | sed -e 's@^wlan0.*_param:@@'; done
txratectrl: 0  
beacon_int: 100  
dtim_period: 1  
pseudo_ibss: 0  
other_ap_policy: 0  
dump: 0  
ap_max_inactivity: 300  
ap_bridge_packets: 1  
ap_nullfunc_ack: 0  
max_wds: 16  
autom_ap_wds: 0  
ap_auth_algs: 3  
monitor_allow_fcserr: 0  
host_encrypt: 1  
host_decrypt: 1  
bus_master_threshold_rx: 0  
bus_master_threshold_tx: 0  
host_roaming: 0  
bcrx_sta_key: 0  
ieee_802_1x: 1  
antsel_tx: 0  
antsel_rx: 0  
monitor_type: 0  
wds_type: 4  
hostscan: Interface doesn't accept private ioctl...
getprism2_param (8BE1): Operation not supported
ap_scan: 0  
enh_sec: 0  
basic_rates: 3  
oper_rates: 15  
hostapd: 1  
ptype: 6  
alc: Interface doesn't accept private ioctl...
getprism2_param (8BE1): Operation not supported
txpower: 13  

root at yupa:~# cat /etc/hostapd/hostapd.conf 
##### hostapd configuration file ##############################################
# Empty lines and lines starting with # are ignored

# AP netdevice name (without 'ap' prefix, i.e., wlan0 uses wlan0ap for
# management frames)
interface=wlan0

# hostapd event logger configuration
#
# Two output method: syslog and stdout (only usable if not forking to
# background).
#
# Module bitfield (ORed bitfield of modules that will be logged; -1 = all
# modules):
# bit 0 (1) = IEEE 802.11
# bit 1 (2) = IEEE 802.1X
# bit 2 (4) = RADIUS
#
# Levels (minimum value for logged events):
#  0 = verbose debugging
#  1 = debugging
#  2 = informational messages
#  3 = notification
#  4 = warning
#
logger_syslog=-1
logger_syslog_level=0
logger_stdout=-1
logger_stdout_level=0

# Debugging: 0 = no, 1 = minimal, 2 = verbose, 3 = msg dumps
debug=2

# Dump file for state information (on SIGUSR1)
dump_file=/tmp/hostapd.dump

# Daemonize hostapd process (i.e., fork to background)
daemonize=1


##### IEEE 802.11 related configuration #######################################

# SSID to be used in IEEE 802.11 management frames
ssid=valley-of-wind

# Station MAC address -based authentication
# 0 = accept unless in deny list
# 1 = deny unless in accept list
# 2 = use external RADIUS server (accept/deny lists are searched first)
macaddr_acl=0

# Accept/deny lists are read from separate files (containing list of
# MAC addresses, one per line). Use absolute path name to make sure that the
# files can be read on SIGHUP configuration reloads.
#accept_mac_file=/etc/hostapd.accept
#deny_mac_file=/etc/hostapd.deny

# IEEE 802.11 specifies two authentication algorithms. hostapd can be
# configured to allow both of these or only one. Open system authentication
# should be used with IEEE 802.1X.
# Bit fields of allowed authentication algorithms:
# bit 0 = Open System Authentication
# bit 1 = Shared Key Authentication (requires WEP)
auth_algs=1

# Associate as a station to another AP while still acting as an AP on the same
# channel.
#assoc_ap_addr=00:12:34:56:78:9a


##### IEEE 802.1X (and IEEE 802.1aa/D4) related configuration #################

# Require IEEE 802.1X authorization
ieee8021x=1

# Use internal minimal EAP Authentication Server for testing IEEE 802.1X.
# This should only be used for testing since it authorizes all users that
# suppot IEEE 802.1X without any keys or certificates.
minimal_eap=0

# Optional displayable message sent with EAP Request-Identity
eap_message=Unauthorized use punishable by death

# WEP rekeying (disabled if key lengths are not set or are set to 0)
# Key lengths for default/broadcast and individual/unicast keys:
# 5 = 40-bit WEP (also known as 64-bit WEP with 40 secret bits)
# 13 = 104-bit WEP (also known as 128-bit WEP with 104 secret bits)
wep_key_len_broadcast=5
wep_key_len_unicast=5
# Rekeying period in seconds. 0 = do not rekey (i.e., set keys only once)
#wep_rekey_period=300

# EAPOL-Key index workaround (set bit7) for WinXP Supplicant (needed only if
# only broadcast keys are used)
eapol_key_index_workaround=0


##### IEEE 802.11f - Inter-Access Point Protocol (IAPP) #######################

# Interface to be used for IAPP broadcast packets
#iapp_interface=eth0


##### RADIUS configuration ####################################################
# for IEEE 802.1X with external Authentication Server, IEEE 802.11
# authentication with external ACL for MAC addresses, and accounting

# The own IP address of the access point (used as NAS-IP-Address)
own_ip_addr=192.168.16.1

# RADIUS authentication server
auth_server_addr=127.0.0.1
auth_server_port=1812
auth_server_shared_secret=foobar

# RADIUS accounting server
acct_server_addr=127.0.0.1
acct_server_port=1813
acct_server_shared_secret=foobar

# Secondary RADIUS servers; to be used if primary one does not reply to
# RADIUS packets. These are optional and there can be more than one secondary
# server listed.
#auth_server_addr=127.0.0.2
#auth_server_port=1812
#auth_server_shared_secret=secret2
#
#acct_server_addr=127.0.0.2
#acct_server_port=1813
#acct_server_shared_secret=secret2

# Retry interval for trying to return to the primary RADIUS server (in
# seconds). RADIUS client code will automatically try to use the next server
# when the current server is not replying to requests. If this interval is set,
# primary server will be retried after configured amount of time even if the
# currently used secondary server is still working.
#radius_retry_primary_interval=600


So, my final question is: given that I use only authenticated
protocols for my own communication (e.g., SFS, SSH, https, etc.), and
mainly want authentication to keep others from piggy-backing on my
limited egress capacity, do I *need* WEP?  To be more specific, is
EAP/TLS authentication worth anything without link-level encryption?
In my naive configuration, the AP seemed to reject any frames not from
an authenticated host, but just because I can't figure out how to get
them through doesn't mean it isn't possible.  Regardless of the
answer, I'd still like to have WEP...but I need to know if this is a
show-stopper or not.

By the way, great work, guys.  Despite the complexity of
configuration, most of it seems to work out of the box, and the rest
can probably be explained by the fact that I have only been using it
for about 24 hours now.

Cheers,
Kyle



From krose+hostap  Sat Aug 23 16:14:45 2003
From: krose+hostap (Kyle Rose)
Date: Sat, 23 Aug 2003 19:14:45 -0400
Subject: 802.1x automatic WEP key negotiation problems
Message-ID: <87k7946k62.fsf@nausicaa.krose.org>

Kyle Rose <krose+hostap at krose.org> writes:

> Last night, I successfully set up a HostAP/FreeRADIUS EAP/TLS
> configuration on my firewall machine (PCMCIA->ISA bridge with a
> Linksys WPC11 ver.3) and an xsupplicant configuration on my laptop
> (Lucent Orinoco).

I love responding to my own emails.

So, I've made a bit more progress.  First, I upgraded to 0.0.4 after
noticing that Debian only had 0.0.3.

Now, if I set:

#wep_key_len_broadcast=5
wep_key_len_unicast=5 # or 13, both work

then the laptop and the access point successfully negotiate a WEP key,
which appears on both systems:

AP
--
root at yupa:/usr/src/modules# hostap_crypt_conf  -l wlan0
Default keys
  algorithm: none

Keys for 00:60:1d:1c:bf:09
  algorithm: WEP
  TX key idx: 1
  key 1: e8 bb d0 d7 30 bc e8 e4 7c 84 be 20 34
  key 2:
  key 3:
  key 4:

laptop
------
the-book-of-life:~# iwconfig
.
.
.
        Encryption key:E8BB-D0D7-30BC-E8E4-7C84-BE20-34

But, when I try to ping the AP from the laptop, nothing gets through
to the IP stack, though I do see lots of lines in /var/log/messages
indicating that hostap is throwing away stuff:

Aug 23 19:09:51 yupa kernel: wlan0: encryption configured, but RX frame not encrypted (SA=00:60:1d:1c:bf:09)

I just downloaded the latest copy of the archives, and Erich Schubert
(<erich at debian.org>) complained of the same problem only a few days
ago.  So, I feel we are very close to the blocker here.

Incidentally, why does activating the broadcast WEP key cause the
behvaior I saw before (nothing getting through at all; no log messages
from hostap; etc.)?

Cheers,
Kyle



From ged  Sat Aug 23 04:27:40 2003
From: ged (Ged Haywood)
Date: Sat, 23 Aug 2003 12:27:40 +0100 (BST)
Subject: Prism cards
In-Reply-To: <20030822221229.69C43F0FA@mail.iocaine.com>
Message-ID: <Pine.LNX.4.21.0308231224140.30880-100000@www2.jubileegroup.co.uk>

> Date: Wed, 20 Aug 2003 00:24:25 +0200
> From: "Aleksandar Nikolic" <aca at loznica.com>
> Subject: Re:Prism cards (Greg Johnson)
> To: <hostap at shmoo.com>
> Message-ID: <002201c366a0$a743ba20$020a010a at alfa>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Well We have a very big problems to find prism based wlan cards and there I can send to you look of three revision of DWL 520 
>       Revision A is prism based
>       Revision B is prism based too
> but Revision C1 is not prism based  http://www.dlink.com/products/support.asp?pid=42

I'm still using (and selling:) Netgear MA311 and although supplies
have been difficult to find sometimes they are available.   They are
still Prism based.  I understand that the MA311+ variant is TI based.

73,
Ged.




From insecure  Sat Aug 23 04:40:39 2003
From: insecure (insecure)
Date: Sat, 23 Aug 2003 14:40:39 +0300
Subject: hostAP vs Dedicated AP
In-Reply-To: <Pine.LNX.4.44.0308211449370.19687-100000@ece.iisc.ernet.in>
References: <Pine.LNX.4.44.0308211449370.19687-100000@ece.iisc.ernet.in>
Message-ID: <200308231440.39982.insecure@mail.od.ua>

On Thursday 21 August 2003 12:26, Anand S. Katti wrote:
> 1. WEP or equivalent protocols supported.

hostap can do WEP in firmware or software,
can be modified to do anything you want in software.

> 2. capability to host multiple BSS names.

don't know

> 3. packet forwarding latencies.

Done in firmware, must be the same

> 4. range.

Don't know, this depends on hardware quality

> 5. No. of hosts supported.

This is limited by throughput degradation.
Theoretically you can have 2000+ hosts.

> 6. any other added advantages.

With hostap I turn off bridging and do routing.
This allows me to do firewalling (iptables),
traffic accounting etc etc etc.
If I will ever want it, I can do DHCP,
IPsec, traffic shaping, myriad of things.
--
vda



From lcaeiro  Sun Aug 24 02:37:30 2003
From: lcaeiro (Luisa Caeiro)
Date: Sun, 24 Aug 2003 10:37:30 +0100
Subject: Fw: Buffering messages (more information)
Message-ID: <000e01c36a23$5765e100$6501a8c0@netcabo>


----- Original Message -----
From: "Luisa Caeiro" <lcaeiro at est.ips.pt>
To: "Jouni Malinen" <jkmaline at cc.hut.fi>
Sent: Sunday, August 24, 2003 3:00 AM
Subject: Re: Buffering messages


>
> ----- Original Message -----
> From: "Jouni Malinen" <jkmaline at cc.hut.fi>
> To: "Lu?sa Caeiro" <lcaeiro at est.ips.pt>
> Sent: Saturday, August 23, 2003 2:19 AM
> Subject: Re: Buffering messages
>
>
> > On Fri, Aug 22, 2003 at 06:58:08PM +0100, Lu?sa Caeiro wrote:
> >
> > > I'm trying to control the tx_buffer of the card (in mode managed)
using
> a
> > > new skb_buf_queue (analogous to tx_buf in APs for stations in PS
mode).
> So,
> > > I count the messages when prism2_transmit is called and I decrease the
> count
> > > when a tx_ev or tx_exc is received. When the counter reaches a limit I
> > > bufferize the messages to send.
> >
> > I don't think I fully understood what you are trying to do with this
> > buffering.. If you just want to limit how many packets are pending in
> > the card buffer, you could either just use smaller TX fid value (which
> > does not give full control) or stop the Linux netif queue based on a
> > counter. This would not need any extra buffering in the driver.
> >
>
> I forgot the buffering in the driver and I follow your suggestion of stop
> the Linux netif queues when the msg counter in card buffer reach a limit.
> What happenned is that the card is resetting periodically because a
transmit
> timeout appears.
>
> I didn't say before that in addition to limit the packets in card buffer,
I
> split the beacon interval in several (3) periods (with a timer that is
> fetched with different values) and I just allow transmition in one of that
> periods. So in the periods where the transmission is not allowed I'm also
> stopping the Linux netif queues.
> Have you any idea of what could cause these resets?
>
> Thanks in advance
>
> Lu?sa Caeiro

To had some more information of the changes I made:
In prism2_transmit_cb - netif queues are not wake if the msg counter (that
has been incremented in prism2_transmit) reach the limit.
In prism2_tx_ev and prism2_txexc - the msg counter is decremented and netif
queues are wake if they are stopped and no transmission is pending.
In function associated with the timer that split the beacon interval - netif
queues are stopped if the new period started is a period not allowed to
transmit (and if netif queues are not already stopped) and are wake if the
new period started is the period allowed to transmit.

The timer in my test case runs with a timer.expires of 20ms, after 50ms and
after 30 ms and the cycle is repeated. The station just is allowed to
transmit in the last period of 30ms.

Another question I have is if we don't loose messages when we stop the netif
queues?

Thanks again.

> > --
> > Jouni Malinen                                            PGP id EFC895FA
>




From hostap  Sun Aug 24 09:42:39 2003
From: hostap (Jeff Gold)
Date: Sun, 24 Aug 2003 12:42:39 -0400
Subject: Partial MODVERSIONS?
Message-ID: <3F48EAFF.2090203@esclat.net>

I'm attempting to get hostap-0.0.4 working with RedHat 9 using the 
2.4.20-20.9 kernel (which at the moment is the latest offered through 
up2date).  This was working with 2.4.20-19.9 and hostap-0.0.3, but when 
I upgraded the kernel I had trouble compiling.  I immediatedly grabbed 
the latest hostap release to avoid struggling with old bugs.  And indeed 
the changelog says:

   * fixed number of compilation issues (RH9 kernel, *.mod files to local
     directory, 2.4.x compilation with CONFIG_MODVERSIONS, external
     pcmcia-cs)

Unfortunately while the hostap driver builds and installs with no 
trouble, modprobe reports unresolved symbols when attempting to load it. 
  As far as I can tell the problem is that only some kernel symbols used 
by the hostap driver are converted according to the modversions system. 
  For example, from "nm /lib/modules/2.4.20-20.9/net/hostap.o":

          U add_timer_Ra19eacf8
          U add_wait_queue

The first routine shows up in /proc/ksyms, but the second doesn't.  Or 
rather it does, but as add_wait_queue_R53621d0f.  Somehow add_timer was 
correctly adapted for CONFIG_MODVERSIONS=y, but add_wait_queue wasn't. 
All of the symbols modprobe claims are missing lack modversions tags in 
hostap.o, while those unresolved in nm output but not modprobe have 
them.  This seems quite strange to me.  I checked the output of "make 
-n" but each gcc line has -DMODVERSIONS and the associated -include 
option to pull in the modversions.h file.  I've not yet discovered any 
pattern that would make sense of this.  What could be going wrong?

The following symbols don't have modversions tags and are listed as 
unresolved by modprobe (the __this_module symbol is listed as unresolved 
in hostap.o but doesn't trouble modprobe):

     add_wait_queue
     alloc_skb
     create_proc_entry
     dev_queue_xmit
     ether_setup
     eth_type_trans
     irq_stat
     __kfree_skb
     __netdev_watchdog_up
     netif_rx
     proc_mkdir
     proc_net
     pskb_expand_head
     ___pskb_trim
     register_netdev
     register_netdevice
     remove_proc_entry
     remove_wait_queue
     request_module
     skb_clone
     skb_over_panic
     skb_under_panic
     softnet_data
     unregister_netdev
     unregister_netdevice
     __wake_up
     wireless_send_event

The following appear as unresolved in the hostap.o file, but with 
appropriate modversions tags (these are not reported as unresolved by 
modprobe):

     add_timer
     del_timer
     dev_get
     do_softirq
     flush_scheduled_tasks
     __const_udelay
     cpu_raise_softirq
     __generic_copy_from_user
     __generic_copy_to_user
     get_random_bytes
     jiffies
     kfree
     kmalloc
     __out_of_line_bug
     printk
     schedule_task
     schedule_timeout
     sprintf

Does this make sense to anyone?  What might I be doing wrong here?  Or 
is this a bug caused by the interation of hostap and the latest RedHat 
kernel source?

                                             Jeff




From gdead  Mon Aug 25 04:47:31 2003
From: gdead (Bruce Potter)
Date: Mon, 25 Aug 2003 05:47:31 -0600 (MDT)
Subject: Mail List Problems
Message-ID: <58014.64.80.176.20.1061812051.squirrel@mail.iocaine.com>

Howdy,
Many (most?  all?) don't know me.  I'm one of the silent moderators/admins
for the hostap list.  Hope you're all enjoying your flight.

The last week has been a rough one for the list.  About 2 days before the
worm nonsense, we migrated our list services to a new server.  That caused
a little burp.  Then the worms arrived on the scene and our mail servers
became a touch untable.

We've been working to resolve the issue.  Hopefully things are fixed now.
However, if you are still experiencing any odd problems, please let me
know.

later

bruce
the shmoo group





From f6hqz  Mon Aug 25 05:19:16 2003
From: f6hqz (Francois BERGERET)
Date: Mon, 25 Aug 2003 14:19:16 +0200
Subject: Mail List Problems
In-Reply-To: <58014.64.80.176.20.1061812051.squirrel@mail.iocaine.com>
Message-ID: <LEEMLOMCOLGDFKOEHKDPIEBPDOAA.f6hqz@easyconnect.fr>

Hi dear gentle moderator/admin ;-)

I have a very personal requirement to submit :
Is it possible to add some [hostap] or [shmoo] at subject beginning of each mail from your list ?
This could be very fine to sort/filter my hundred of daily received mails, as other mailing list as LEAF, FreeSWan, etc...

Many thanks in advance and Best Regards,
Francois BERGERET,
France.

> -----Message d'origine-----
> De : hostap-bounces+f6hqz=easyconnect.fr at shmoo.com
> [mailto:hostap-bounces+f6hqz=easyconnect.fr at shmoo.com]De la part de
> Bruce Potter
> Envoy? : lundi 25 ao?t 2003 13:48
> ? : hostap at shmoo.com
> Objet : Mail List Problems
>
>
> Howdy,
> Many (most?  all?) don't know me.  I'm one of the silent moderators/admins
> for the hostap list.  Hope you're all enjoying your flight.
>
>




From gdead  Mon Aug 25 05:46:56 2003
From: gdead (Bruce Potter)
Date: Mon, 25 Aug 2003 06:46:56 -0600 (MDT)
Subject: Mail List Problems
In-Reply-To: <LEEMLOMCOLGDFKOEHKDPIEBPDOAA.f6hqz@easyconnect.fr>
References: <58014.64.80.176.20.1061812051.squirrel@mail.iocaine.com>
	<LEEMLOMCOLGDFKOEHKDPIEBPDOAA.f6hqz@easyconnect.fr>
Message-ID: <59005.64.80.176.20.1061815616.squirrel@mail.iocaine.com>

This was discussed a while back (I believe when the list was first
migrated to a shmoo server).  The general feeling of the group (and
Jouni's request) was to leave the [hostap] off the subject.

All mail to the list should be to'd or cc'd to hostap at shmoo.com.  Most
existing mailers should allow you to filter your lists based on that
criteria.

Thanks

bruce

> Hi dear gentle moderator/admin ;-)
>
> I have a very personal requirement to submit :
> Is it possible to add some [hostap] or [shmoo] at subject beginning of
> each mail from your list ?
> This could be very fine to sort/filter my hundred of daily received mails,
> as other mailing list as LEAF, FreeSWan, etc...
>
> Many thanks in advance and Best Regards,
> Francois BERGERET,
> France.
>
>> -----Message d'origine-----
>> De : hostap-bounces+f6hqz=easyconnect.fr at shmoo.com
>> [mailto:hostap-bounces+f6hqz=easyconnect.fr at shmoo.com]De la part de
>> Bruce Potter
>> Envoy? : lundi 25 ao?t 2003 13:48
>> ? : hostap at shmoo.com
>> Objet : Mail List Problems
>>
>>
>> Howdy,
>> Many (most?  all?) don't know me.  I'm one of the silent
>> moderators/admins
>> for the hostap list.  Hope you're all enjoying your flight.
>>
>>
>
>




From fguidara  Mon Aug 25 05:16:35 2003
From: fguidara (Frank Guidara)
Date: Mon, 25 Aug 2003 12:16:35 -0000
Subject: NETDEV WATCHDOG: wlan0: transmit timed out
Message-ID: <1061813806.4332.22.camel@insane.gwelup.wafreenet>

Hey People,

I have setup HostAP 0.0.4 on a compaq laptop below is some information
that may be useful to people. The card works fine apart from the
timeout's I get on the card. I have orginally had this same wireless
card in another laptop using an older version of HostAP and not had a
problem.

This machine is now running kernel 2.4.21 

 If anyone could me sort out this little problem, It would be greatly
apperciated for this is my only form of internet connection.


 Bus  0, device  17, function  0:
    CardBus bridge: Texas Instruments PCI1131 (rev 1).
      IRQ 15.
      Master Capable.  Latency=168.  Min Gnt=192.Max Lat=5.
      Non-prefetchable 32 bit memory at 0x7fffe000 [0x7fffefff].
  Bus  0, device  17, function  1:
    CardBus bridge: Texas Instruments PCI1131 (#2) (rev 1).
      IRQ 11.
      Master Capable.  Latency=168.  Min Gnt=192.Max Lat=5.
      Non-prefetchable 32 bit memory at 0x7ffff000 [0x7fffffff].


Here are my errors logs:

Aug 17 20:58:03 wired kernel: NETDEV WATCHDOG: wlan0: transmit timed out
Aug 17 20:58:03 wired kernel: wlan0 Tx timed out! Resetting card
Aug 17 20:58:03 wired kernel: hostap_cs: wlan0: resetting card


-Regards

Frank




From f6hqz  Mon Aug 25 07:01:45 2003
From: f6hqz (Francois BERGERET)
Date: Mon, 25 Aug 2003 16:01:45 +0200
Subject: Mail List Problems
In-Reply-To: <59005.64.80.176.20.1061815616.squirrel@mail.iocaine.com>
Message-ID: <LEEMLOMCOLGDFKOEHKDPKECBDOAA.f6hqz@easyconnect.fr>

Ok, Bruce, I will do as this.

Thanks you.

Best Regards,
Francois BERGERET,
France.

> -----Message d'origine-----
> De : Bruce Potter [mailto:gdead at shmoo.com]
> Envoy? : lundi 25 ao?t 2003 14:47
> ? : f6hqz at easyconnect.fr
> Cc : Bruce Potter; hostap at shmoo.com
> Objet : RE: Mail List Problems
>
>
> This was discussed a while back (I believe when the list was first
> migrated to a shmoo server).  The general feeling of the group (and
> Jouni's request) was to leave the [hostap] off the subject.
>
> All mail to the list should be to'd or cc'd to hostap at shmoo.com.  Most
> existing mailers should allow you to filter your lists based on that
> criteria.
>
> Thanks
>
> bruce
>
> > Hi dear gentle moderator/admin ;-)
> >
> > I have a very personal requirement to submit :
> > Is it possible to add some [hostap] or [shmoo] at subject beginning of
> > each mail from your list ?
> > This could be very fine to sort/filter my hundred of daily received mails,
> > as other mailing list as LEAF, FreeSWan, etc...
> >
> > Many thanks in advance and Best Regards,
> > Francois BERGERET,
> > France.
> >
> >> -----Message d'origine-----
> >> De : hostap-bounces+f6hqz=easyconnect.fr at shmoo.com
> >> [mailto:hostap-bounces+f6hqz=easyconnect.fr at shmoo.com]De la part de
> >> Bruce Potter
> >> Envoy? : lundi 25 ao?t 2003 13:48
> >> ? : hostap at shmoo.com
> >> Objet : Mail List Problems
> >>
> >>
> >> Howdy,
> >> Many (most?  all?) don't know me.  I'm one of the silent
> >> moderators/admins
> >> for the hostap list.  Hope you're all enjoying your flight.
> >>
> >>
> >
> >
>
>




From sits  Mon Aug 25 07:35:00 2003
From: sits (Sitsofe Wheeler)
Date: Mon, 25 Aug 2003 14:35:00 -0000
Subject: NETDEV WATCHDOG: wlan0: transmit timed out
In-Reply-To: <1061813806.4332.22.camel@insane.gwelup.wafreenet>
References: <1061813806.4332.22.camel@insane.gwelup.wafreenet>
Message-ID: <1061822117.5782.59.camel@galvatron.localdomain>

On Mon, 2003-08-25 at 13:16, Frank Guidara wrote:
> Hey People,
> 
> I have setup HostAP 0.0.4 on a compaq laptop below is some information
> that may be useful to people. The card works fine apart from the
> timeout's I get on the card. I have orginally had this same wireless
> card in another laptop using an older version of HostAP and not had a
> problem.
I have found that both HostAP and the orinoco drivers seem to both have
this problem with the firmware I was using (0.3.0 primary, 1.4.9
secondary). The linux-wlan drivers do not do have this problem at all
but I am unclear as to when they made the change that caused this
problem to go away...

If your secondary firmware is old you could try a temporary ram upload
of newer firmware (I'm not sure where there are instructions to do this
though).

-- 
Sitsofe | http://sucs.org/~sits/




From niki.waibel  Mon Aug 25 07:46:32 2003
From: niki.waibel (Niki Waibel)
Date: Mon, 25 Aug 2003 16:46:32 +0200 (MEST)
Subject: best card for linux in hostap mode?
Message-ID: <200308251446.h7PEkWH3020332@enterprise2.newlogic.at>

which wireless card would you recommend for linux in ap mode?

what about this usb cards (long cable to card and short cable
to antenna would be nice ...)?

niki w. waibel



From andreaf  Mon Aug 25 09:10:01 2003
From: andreaf (Andrea G. Forte)
Date: Mon, 25 Aug 2003 12:10:01 -0400 (EDT)
Subject: Monitoring with orinoco turbo bronze???
Message-ID: <200308251610.h7PGA1DY023759@cisalpino.cs.columbia.edu>

Hi guys,
anybody knows of a monitoring program to use with PCMCIA Orinoco Turbo Bronze 
cards? I  am especially interested in the Management frames/Beacon frames.

Thank a lot to everybody and especially to Roskin.

Andrea




From fabian1  Mon Aug 25 09:25:38 2003
From: fabian1 (Fabian Gervan)
Date: Mon, 25 Aug 2003 17:25:38 +0100
Subject: cisco 340
Message-ID: <1488860340.20030825172538@diarioc.com.ar>

He guys, does hostap support a cisco340 pci card in Hostap Mode?

Regards
Fabian




From drdoom  Mon Aug 25 14:14:02 2003
From: drdoom (DrDoom)
Date: Mon, 25 Aug 2003 23:14:02 +0200
Subject: best card for linux in hostap mode?
In-Reply-To: <200308251446.h7PEkWH3020332@enterprise2.newlogic.at>
References: <200308251446.h7PEkWH3020332@enterprise2.newlogic.at>
Message-ID: <3F4A7C1A.6070401@drdoom.net>

I think SENAO 2511CD Plus ext2 is a very good choice, it has 2 MMCX 
connectors and prism2 chipset, also 200mW txpower.
http://www.seattlewireless.net/index.cgi/SenaoCard
About USB cards, hostap driver does not support USB.

-- 
-------------------------
David Martos (aka DrDoom)

http://www.sorgonet.com
-------------------------



Niki Waibel wrote:

>which wireless card would you recommend for linux in ap mode?
>
>what about this usb cards (long cable to card and short cable
>to antenna would be nice ...)?
>
>niki w. waibel
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>  
>





From wim  Mon Aug 25 14:16:21 2003
From: wim (Wim Osterholt)
Date: Mon, 25 Aug 2003 23:16:21 +0200 (MEST)
Subject: Subject: prism2_srec bugs
Message-ID: <20030825211621.4824.qmail@djo.tudelft.nl>


Hello Jouni,

> You might want to take a look at the CVS version of the Host AP driver
...
> > The prism2_srec utility ...

I'd like to mention some peculiarities.
I'll presumably be the only person in the world that likes to preserve the
cards contents before trying to upgrade it beyond repair. :-)
Anyway, I came to run prism2_srec and it still tells me:
Usage: prism2_srec [-vvrgfd] <interface> <srec file name> [srec file name]
  -d   dump SREC image into prism2_srec.dump

Confusion strikes when I read technospeak like 'downloading' where there's
clearly ment 'uploading', but how wrong can I get?

Running 'prism2_srec -d wlan0' does not give me the desired file
'prism2_srec.dump'.  Checking the source it never will.
It requires parameters that I cannot give. When I disable the check on the
number of command line parameters, it still demands filenames to check for
upload. Actually, it never comes to dump anything. I may disable several of
these items and in the end it produces the desired prism2_srec.dump, it
barfs about segmentation violation and the file remains empty (although
strace gave the impression that some 40K should have been written).

I just downloaded the CVS version, but these bugs are still there.

The cards is a 'BenQ AWL100' and is prism2.5 based. It works well with hostap,
but I can't get it to work with wlan-ng, so prism2dl is not an alternative.

Could you fix prism2_srec somehow, please.

Regards,
Wim Osterholt.





From sneeze  Mon Aug 25 15:45:48 2003
From: sneeze (Ryan Abbenhuys)
Date: Tue, 26 Aug 2003 08:45:48 +1000
Subject: cisco 340
Message-ID: <3f4a919c.1fac.0@alphalink.com.au>

You should be asking if the Cisco340 cards supports HostAP, not if HostAP
supports the card. :)

HostAP is a feature in Prism chipsets that the HostAP driver enables us to
use.

>He guys, does hostap support a cisco340 pci card in Hostap Mode?
>
>Regards
>Fabian
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>



From jkmaline  Mon Aug 25 19:04:42 2003
From: jkmaline (Jouni Malinen)
Date: Mon, 25 Aug 2003 19:04:42 -0700
Subject: Subject: prism2_srec bugs
In-Reply-To: <20030825211621.4824.qmail@djo.tudelft.nl>
References: <20030825211621.4824.qmail@djo.tudelft.nl>
Message-ID: <20030826020442.GA3273@jm.kir.nu>

On Mon, Aug 25, 2003 at 11:16:21PM +0200, Wim Osterholt wrote:

> I'll presumably be the only person in the world that likes to preserve the
> cards contents before trying to upgrade it beyond repair. :-)

Assuming you have a mechanism of returning the said backup, that might
be useful ;-).

> Usage: prism2_srec [-vvrgfd] <interface> <srec file name> [srec file name]
>   -d   dump SREC image into prism2_srec.dump

SREC = the upgrade file, not the flash contents..

> Confusion strikes when I read technospeak like 'downloading' where there's
> clearly ment 'uploading', but how wrong can I get?

Well, it is downloading from the Prism2 card point of view ;-).

> Running 'prism2_srec -d wlan0' does not give me the desired file
> 'prism2_srec.dump'.

..

> I just downloaded the CVS version, but these bugs are still there.

This is not a bug, it is a feature. '-d' option dumps the firmware
upgrade data to a file (instead of writing it to Prism2 RAM/flash). In
other words, you do need to give upgrade image name on the command line.

> Could you fix prism2_srec somehow, please.

If it ain't broken, there's nothing to fix ;-). Feel free to file a
feature request for adding a flash image dump to the program.

-- 
Jouni Malinen                                            PGP id EFC895FA



From sneeze  Mon Aug 25 22:59:45 2003
From: sneeze (Ryan Abbenhuys)
Date: Tue, 26 Aug 2003 15:59:45 +1000
Subject: No tx-power option
Message-ID: <3f4af751.131c.0@alphalink.com.au>

I've just noticed that the "Tx-Power" isn't displayed on my interfaces
running HostAP when I run an iwconfig, however other devices using other
drivers do. (i'll try some older hostap versions when I get home tonight)

I have two RH9 boxes running latest CVS of HostAP and both function
perfectly and have been for a year or more.

I used to run "iwconfig wlan0 txpower 200mW" at bootup as by default the
card didn't run at full power.  I've since noticed the txpower command no
longer works.

[root at wantirna-ap1 etc]# iwconfig wlan0 txpower 200mW
Error for wireless request "Set Tx Power" (8B26) :
    SET failed on device wlan0 ; Operation not supported.

Here's my iwconfig output  (notice wlan0 shows no Tx-Power while eth1
running the orinoco driver does)....


eth1      IEEE 802.11-DS  ESSID:"AAF_FKR_LINK"  Nickname:"wantirna-ap1"
          Mode:Ad-Hoc  Frequency:2.437GHz  Cell: 02:00:BD:7F:DC:2A
          Bit Rate:11Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
          Retry limit:4   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:12647
          Tx excessive retries:1022  Invalid misc:0   Missed beacon:0

wlan0     IEEE 802.11b  ESSID:"aaf.wireless.org.au" 
Nickname:"wantirna-ap1"
          Mode:Master  Frequency:2.462GHz  Access Point: 00:02:6F:04:0F:81
          Bit Rate:11Mb/s   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:964  Invalid misc:5138   Missed beacon:0



From lanev007  Tue Aug 26 01:52:24 2003
From: lanev007 (=?iso-8859-1?q?veronica=20lane?=)
Date: Tue, 26 Aug 2003 09:52:24 +0100 (BST)
Subject: hostap rpm source
Message-ID: <20030826085224.94584.qmail@web80702.mail.yahoo.com>

hi guys,

im trying to going to create a hostap driver into an
rpm form, instead of .tar. can somebody assist me with
this or direct me? thanks guys.

best regards,
vicky

________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://uk.messenger.yahoo.com/



From sgala  Tue Aug 26 04:23:54 2003
From: sgala (=?ISO-8859-1?Q?Santiago_Gala_P=E9rez?=)
Date: Tue, 26 Aug 2003 13:23:54 +0200
Subject: hostap rpm source
In-Reply-To: <20030826085224.94584.qmail@web80702.mail.yahoo.com>
Message-ID: <C68C2E0F-D7B7-11D7-B34E-000A958871C6@hisitech.com>


El martes, 26 agos, 2003, a las 10:52 Europe/Madrid, veronica lane 
escribi?:

> hi guys,
>
> im trying to going to create a hostap driver into an
> rpm form, instead of .tar. can somebody assist me with
> this or direct me? thanks guys.
>

It looks like a difficult task, as the binaries will depend on your 
kernel rpms.

For instance, Mandrake kernel RPMs are built for each  version + 
patches + config (like secure, smp, enterprise, ...) and a different 
set of binary hostap modules are needed for each combination.

The cleanest way would be to add the hostap.tgz as a source for the 
kernel SRPM and then generate from it also the 
hostap-modules-<version>+<config>+<architecture>... rpm (and possibly a 
hostapd rpm). The modules should depend completely on the respective 
kernel versions. hostapd possibly just on the hostap sources. It is a 
difficult task, however.

If you are building rpms for an organization where just a few kernels 
are deployed, you could try building just those few versions (again, 
being careful with the dependencies).

The current mandrake kernels, for instance, do include hostap drivers. 
But they are old, do not work without hostapd, and there is no hostapd 
package (a hostapd built from cvs sources is not compatible). So, your 
first task would be to get rid of those (in 
/lib/modules/xxx/3rdparty/...) in the generated kernels (I erase them 
by hand each time I upgrade kernels)

Starting from the mandrake kernel source spec (very complex, though) 
and fixing it to really work (if mandrake kernels are good for you) 
would possibly be simpler unless you are really familiar with the RPM 
tools.

Good luck ;-)
      Santiago

> best regards,
> vicky
>





From drdoom  Tue Aug 26 05:58:43 2003
From: drdoom (DrDoom)
Date: Tue, 26 Aug 2003 14:58:43 +0200
Subject: No tx-power option
In-Reply-To: <3f4af751.131c.0@alphalink.com.au>
References: <3f4af751.131c.0@alphalink.com.au>
Message-ID: <3F4B5983.2000703@drdoom.net>

I can confirm that, the same happens to me. I am also running RedHat 9.0 
with hostap 0.0.4

-- 
-------------------------
David Martos (aka DrDoom)

http://www.sorgonet.com
-------------------------



Ryan Abbenhuys wrote:

>I've just noticed that the "Tx-Power" isn't displayed on my interfaces
>running HostAP when I run an iwconfig, however other devices using other
>drivers do. (i'll try some older hostap versions when I get home tonight)
>
>I have two RH9 boxes running latest CVS of HostAP and both function
>perfectly and have been for a year or more.
>
>I used to run "iwconfig wlan0 txpower 200mW" at bootup as by default the
>card didn't run at full power.  I've since noticed the txpower command no
>longer works.
>
>[root at wantirna-ap1 etc]# iwconfig wlan0 txpower 200mW
>Error for wireless request "Set Tx Power" (8B26) :
>    SET failed on device wlan0 ; Operation not supported.
>
>Here's my iwconfig output  (notice wlan0 shows no Tx-Power while eth1
>running the orinoco driver does)....
>
>
>eth1      IEEE 802.11-DS  ESSID:"AAF_FKR_LINK"  Nickname:"wantirna-ap1"
>          Mode:Ad-Hoc  Frequency:2.437GHz  Cell: 02:00:BD:7F:DC:2A
>          Bit Rate:11Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
>          Retry limit:4   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:12647
>          Tx excessive retries:1022  Invalid misc:0   Missed beacon:0
>
>wlan0     IEEE 802.11b  ESSID:"aaf.wireless.org.au" 
>Nickname:"wantirna-ap1"
>          Mode:Master  Frequency:2.462GHz  Access Point: 00:02:6F:04:0F:81
>          Bit Rate:11Mb/s   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:964  Invalid misc:5138   Missed beacon:0
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>  
>





From krose+hostap  Tue Aug 26 07:29:06 2003
From: krose+hostap (Kyle Rose)
Date: Tue, 26 Aug 2003 10:29:06 -0400
Subject: 802.1x automatic WEP key negotiation problems
Message-ID: <873cfobih9.fsf@nausicaa.krose.org>

Sorry to spam the list if you guys got this already, but I got no
response and I wanted to make sure the list's mail problems didn't
blackhole the message.  (The following two emails don't appear in the
archives, for instance.)

Cheers,
Kyle


Message 1:
Date: Sat, 23 Aug 2003 14:53:50 -0400

Last night, I successfully set up a HostAP/FreeRADIUS EAP/TLS
configuration on my firewall machine (PCMCIA->ISA bridge with a
Linksys WPC11 ver.3) and an xsupplicant configuration on my laptop
(Lucent Orinoco).

As far as I can tell, both cards have the latest firmware: 1.7.4 for
the Linksys, and whatever I managed to download from the Proxim
website the other day (maybe 8.10?).

At any rate, most everything works: the Linksys goes into AP mode,
shovels 802.1x frames from the laptop off to the hostapd, which then
contacts the FreeRADIUS server to initiate authentication, after which
the laptop is able to get DHCP request packets through to get an IP.
If the laptop doesn't have xsupplicant, or has an invalid certificate,
hostapd refuses to recognize its packets.  Sounds great.

However, nothing at all works when I try to turn on WEP key
negotiation.  Now, someone correct me if I'm wrong, but my impression
is that the xsupplicant and RADIUS server should together negotiate
some secure way for hostapd to send a WEP key to the laptop, initially
and perhaps at intervals, depending on whether one has re-keying
activated, no?  Well, when I activate the encryption in hostapd.conf
by setting:

wep_key_len_broadcast=5
wep_key_len_unicast=5

then nothing happens when I plug the Lucent card into the laptop and
start xsupplicant: I see *nothing* in the logs after hostapd
successfully starts up, even at hostapd's highest log level; and the
Lucent card's lights just blink periodically, but it doesn't even find
my LAN's ESSID.  The RADIUS server's configuration at this point is
moot, since hostapd never contacts it, presumably because it doesn't
see any of link negotiation frames from the laptop.

I've done the standard exhaustive-search things, like commenting out
one or the other of the above lines and restarting hostapd, to no
avail.  I have been searching for hours on the web, newsgroup, and
relevant mailing lists, also in vain.

Let me give you the output of some relevant commands while the laptop
is attempting (futilely) to get authenticated.  "yupa" is the firewall
machine containing the AP, and its LAN IP address is 192.168.16.1
(netmask 255.255.240.0).  Feel free to ask me for anything you think
would help debug this problem.

As an added bonus, if someone can help me solve this, I'll write a FAQ
Q&A for this problem so others won't bother you. :)

root at yupa:~# uname -a
Linux yupa 2.4.21 #1 Wed Aug 20 20:27:29 EDT 2003 i586 GNU/Linux

root at yupa:~# lsmod | grep host
hostap_cs              47964   2 
hostap                 69796   0  [hostap_cs]
hostap_crypt_wep        3244   1  (autoclean)
hostap_crypt            1520   0  [hostap hostap_crypt_wep]
ds                      6388   2  [hostap_cs]
pcmcia_core            43072   0  [hostap_cs ds i82365]

root at yupa:~# ifconfig
.
.
.
wlan0     Link encap:Ethernet  HWaddr 00:06:25:AB:9D:84  
          inet addr:192.168.16.1  Bcast:192.168.31.255  Mask:255.255.240.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:3 Base address:0x100 

wlan0ap   Link encap:UNSPEC  HWaddr 00-06-25-AB-9D-84-00-00-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:2290  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 b)  TX bytes:78 (78.0 b)
          Interrupt:3 Base address:0x100 

root at yupa:~# iwconfig
.
.
.
wlan0     IEEE 802.11b  ESSID:"valley-of-wind"  
          Mode:Master  Frequency:2.422GHz  Access Point: 00:06:25:AB:9D:84  
          Bit Rate:11Mb/s   Tx-Power:-15 dBm   Sensitivity=1/242700000  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:AFCC-CD41-B3 [2]   Security mode:open
          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

wlan0ap   IEEE 802.11b  ESSID:"valley-of-wind"  
          Mode:Master  Frequency:2.422GHz  Access Point: 00:06:25:AB:9D:84  
          Bit Rate:11Mb/s   Tx-Power:-15 dBm   Sensitivity=1/242700000  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:AFCC-CD41-B3 [2]   Security mode:open
          Power Management:off
          
wlan0sta  IEEE 802.11b  ESSID:"valley-of-wind"  
          Mode:Managed  Frequency:2.422GHz  Access Point: 00:00:00:00:00:00  
          Bit Rate:11Mb/s   Tx-Power:-15 dBm   Sensitivity=1/242700000  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:AFCC-CD41-B3 [2]   Security mode:open
          Power Management:off

root at yupa:~# hostap_crypt_conf -l wlan0
Default keys
  algorithm: WEP
  TX key idx: 2
  key 1:
  key 2: af cc cd 41 b3
  key 3:
  key 4:

root at yupa:~# for A in `prism2_param  | egrep '^[[:space:]]+[a-zA-z0-9]*:' | sed -e 's@^[[:space:]]*@@' -e 's@:.*@@'`; do echo -n "$A: "; prism2_param wlan0 $A | sed -e 's@^wlan0.*_param:@@'; done
txratectrl: 0  
beacon_int: 100  
dtim_period: 1  
pseudo_ibss: 0  
other_ap_policy: 0  
dump: 0  
ap_max_inactivity: 300  
ap_bridge_packets: 1  
ap_nullfunc_ack: 0  
max_wds: 16  
autom_ap_wds: 0  
ap_auth_algs: 3  
monitor_allow_fcserr: 0  
host_encrypt: 1  
host_decrypt: 1  
bus_master_threshold_rx: 0  
bus_master_threshold_tx: 0  
host_roaming: 0  
bcrx_sta_key: 0  
ieee_802_1x: 1  
antsel_tx: 0  
antsel_rx: 0  
monitor_type: 0  
wds_type: 4  
hostscan: Interface doesn't accept private ioctl...
getprism2_param (8BE1): Operation not supported
ap_scan: 0  
enh_sec: 0  
basic_rates: 3  
oper_rates: 15  
hostapd: 1  
ptype: 6  
alc: Interface doesn't accept private ioctl...
getprism2_param (8BE1): Operation not supported
txpower: 13  

root at yupa:~# cat /etc/hostapd/hostapd.conf 
##### hostapd configuration file ##############################################
# Empty lines and lines starting with # are ignored

# AP netdevice name (without 'ap' prefix, i.e., wlan0 uses wlan0ap for
# management frames)
interface=wlan0

# hostapd event logger configuration
#
# Two output method: syslog and stdout (only usable if not forking to
# background).
#
# Module bitfield (ORed bitfield of modules that will be logged; -1 = all
# modules):
# bit 0 (1) = IEEE 802.11
# bit 1 (2) = IEEE 802.1X
# bit 2 (4) = RADIUS
#
# Levels (minimum value for logged events):
#  0 = verbose debugging
#  1 = debugging
#  2 = informational messages
#  3 = notification
#  4 = warning
#
logger_syslog=-1
logger_syslog_level=0
logger_stdout=-1
logger_stdout_level=0

# Debugging: 0 = no, 1 = minimal, 2 = verbose, 3 = msg dumps
debug=2

# Dump file for state information (on SIGUSR1)
dump_file=/tmp/hostapd.dump

# Daemonize hostapd process (i.e., fork to background)
daemonize=1


##### IEEE 802.11 related configuration #######################################

# SSID to be used in IEEE 802.11 management frames
ssid=valley-of-wind

# Station MAC address -based authentication
# 0 = accept unless in deny list
# 1 = deny unless in accept list
# 2 = use external RADIUS server (accept/deny lists are searched first)
macaddr_acl=0

# Accept/deny lists are read from separate files (containing list of
# MAC addresses, one per line). Use absolute path name to make sure that the
# files can be read on SIGHUP configuration reloads.
#accept_mac_file=/etc/hostapd.accept
#deny_mac_file=/etc/hostapd.deny

# IEEE 802.11 specifies two authentication algorithms. hostapd can be
# configured to allow both of these or only one. Open system authentication
# should be used with IEEE 802.1X.
# Bit fields of allowed authentication algorithms:
# bit 0 = Open System Authentication
# bit 1 = Shared Key Authentication (requires WEP)
auth_algs=1

# Associate as a station to another AP while still acting as an AP on the same
# channel.
#assoc_ap_addr=00:12:34:56:78:9a


##### IEEE 802.1X (and IEEE 802.1aa/D4) related configuration #################

# Require IEEE 802.1X authorization
ieee8021x=1

# Use internal minimal EAP Authentication Server for testing IEEE 802.1X.
# This should only be used for testing since it authorizes all users that
# suppot IEEE 802.1X without any keys or certificates.
minimal_eap=0

# Optional displayable message sent with EAP Request-Identity
eap_message=Unauthorized use punishable by death

# WEP rekeying (disabled if key lengths are not set or are set to 0)
# Key lengths for default/broadcast and individual/unicast keys:
# 5 = 40-bit WEP (also known as 64-bit WEP with 40 secret bits)
# 13 = 104-bit WEP (also known as 128-bit WEP with 104 secret bits)
wep_key_len_broadcast=5
wep_key_len_unicast=5
# Rekeying period in seconds. 0 = do not rekey (i.e., set keys only once)
#wep_rekey_period=300

# EAPOL-Key index workaround (set bit7) for WinXP Supplicant (needed only if
# only broadcast keys are used)
eapol_key_index_workaround=0


##### IEEE 802.11f - Inter-Access Point Protocol (IAPP) #######################

# Interface to be used for IAPP broadcast packets
#iapp_interface=eth0


##### RADIUS configuration ####################################################
# for IEEE 802.1X with external Authentication Server, IEEE 802.11
# authentication with external ACL for MAC addresses, and accounting

# The own IP address of the access point (used as NAS-IP-Address)
own_ip_addr=192.168.16.1

# RADIUS authentication server
auth_server_addr=127.0.0.1
auth_server_port=1812
auth_server_shared_secret=foobar

# RADIUS accounting server
acct_server_addr=127.0.0.1
acct_server_port=1813
acct_server_shared_secret=foobar

# Secondary RADIUS servers; to be used if primary one does not reply to
# RADIUS packets. These are optional and there can be more than one secondary
# server listed.
#auth_server_addr=127.0.0.2
#auth_server_port=1812
#auth_server_shared_secret=secret2
#
#acct_server_addr=127.0.0.2
#acct_server_port=1813
#acct_server_shared_secret=secret2

# Retry interval for trying to return to the primary RADIUS server (in
# seconds). RADIUS client code will automatically try to use the next server
# when the current server is not replying to requests. If this interval is set,
# primary server will be retried after configured amount of time even if the
# currently used secondary server is still working.
#radius_retry_primary_interval=600


So, my final question is: given that I use only authenticated
protocols for my own communication (e.g., SFS, SSH, https, etc.), and
mainly want authentication to keep others from piggy-backing on my
limited egress capacity, do I *need* WEP?  To be more specific, is
EAP/TLS authentication worth anything without link-level encryption?
In my naive configuration, the AP seemed to reject any frames not from
an authenticated host, but just because I can't figure out how to get
them through doesn't mean it isn't possible.  Regardless of the
answer, I'd still like to have WEP...but I need to know if this is a
show-stopper or not.

By the way, great work, guys.  Despite the complexity of
configuration, most of it seems to work out of the box, and the rest
can probably be explained by the fact that I have only been using it
for about 24 hours now.

Cheers,
Kyle


Message 2:
Date: Sat, 23 Aug 2003 19:14:45 -0400

Kyle Rose <krose+hostap at krose.org> writes:

> Last night, I successfully set up a HostAP/FreeRADIUS EAP/TLS
> configuration on my firewall machine (PCMCIA->ISA bridge with a
> Linksys WPC11 ver.3) and an xsupplicant configuration on my laptop
> (Lucent Orinoco).

I love responding to my own emails.

So, I've made a bit more progress.  First, I upgraded to 0.0.4 after
noticing that Debian only had 0.0.3.

Now, if I set:

#wep_key_len_broadcast=5
wep_key_len_unicast=5 # or 13, both work

then the laptop and the access point successfully negotiate a WEP key,
which appears on both systems:

AP
---
root at yupa:/usr/src/modules# hostap_crypt_conf -l wlan0
Default keys
  algorithm: none

Keys for 00:60:1d:1c:bf:09
  algorithm: WEP
  TX key idx: 1
  key 1: e8 bb d0 d7 30 bc e8 e4 7c 84 be 20 34
  key 2:
  key 3:
  key 4:

laptop
------
the-book-of-life:~# iwconfig
.
.
.
        Encryption key:E8BB-D0D7-30BC-E8E4-7C84-BE20-34

But, when I try to ping the AP from the laptop, nothing gets through
to the IP stack, though I do see lots of lines in /var/log/messages
indicating that hostap is throwing away stuff:

Aug 23 19:09:51 yupa kernel: wlan0: encryption configured, but RX frame not encrypted (SA=00:60:1d:1c:bf:09)

I just downloaded the latest copy of the archives, and Erich Schubert
(<erich at debian.org>) complained of the same problem only a few days
ago.  So, I feel we are very close to the blocker here.

Incidentally, why does activating the broadcast WEP key cause the
behvaior I saw before (nothing getting through at all; no log messages
from hostap; etc.)?

Cheers,
Kyle



From fabian1  Tue Aug 26 06:03:49 2003
From: fabian1 (Fabian Gervan)
Date: Tue, 26 Aug 2003 14:03:49 +0100
Subject: cisco 340
In-Reply-To: <3f4a919c.1fac.0@alphalink.com.au>
References: <3f4a919c.1fac.0@alphalink.com.au>
Message-ID: <7110401306.20030826140349@diarioc.com.ar>

Hello Ryan,

RA> HostAP is a feature in Prism chipsets that the HostAP driver enables us to
RA> use.

ok, I understand that cisco340 have prism2.5 chipset, but a propieraty
mac controller.

Regards
Fabian




From bapper  Tue Aug 26 12:43:35 2003
From: bapper (Brian Pomerantz)
Date: Tue, 26 Aug 2003 12:43:35 -0700
Subject: broadcast frames
Message-ID: <20030826194335.GA723@skull.piratehaven.org>

I didn't see anything on this in the list archives.  I'm seeing
broadcast/multi-cast frames sent out when there isn't a station
associated to the AP.  The attached patch appears to fix this problem,
though I'm not certain it is completely correct.  WDS still works and
I don't see broadcasts when there isn't a station associated.


BAPper
-------------- next part --------------
Index: hostap_hw.c
===================================================================
RCS file: /cvs/hostap-pollen8/driver/modules/hostap_hw.c,v
retrieving revision 1.1.1.2
retrieving revision 1.2
diff -r1.1.1.2 -r1.2
1659a1660,1665
> 		} else if (!local->ap->num_sta) {
> 			/*
> 			 * There are no stations, get the hell out!
> 			 */
> 			ret = 0; /* drop packet */
> 			goto fail;


From bapper  Tue Aug 26 12:55:53 2003
From: bapper (Brian Pomerantz)
Date: Tue, 26 Aug 2003 12:55:53 -0700
Subject: broadcast frames
In-Reply-To: <20030826194335.GA723@skull.piratehaven.org>
References: <20030826194335.GA723@skull.piratehaven.org>
Message-ID: <20030826195553.GA1438@skull.piratehaven.org>

On Tue, Aug 26, 2003 at 12:43:35PM -0700, Brian Pomerantz wrote:
> I didn't see anything on this in the list archives.  I'm seeing
> broadcast/multi-cast frames sent out when there isn't a station
> associated to the AP.  The attached patch appears to fix this problem,
> though I'm not certain it is completely correct.  WDS still works and
> I don't see broadcasts when there isn't a station associated.
> 

Sorry, forgot the context switch, here it is again.


BAPper
-------------- next part --------------
Index: hostap_hw.c
===================================================================
RCS file: /cvs/hostap-pollen8/driver/modules/hostap_hw.c,v
retrieving revision 1.1.1.2
diff -c -r1.1.1.2 hostap_hw.c
*** hostap_hw.c	30 Jul 2003 00:42:08 -0000	1.1.1.2
--- hostap_hw.c	26 Aug 2003 19:52:13 -0000
***************
*** 1657,1662 ****
--- 1657,1668 ----
  			/* AP client mode: send frames with foreign src addr
  			 * using 4-addr WDS frames */
  			use_wds = WDS_COMPLIANT_FRAME;
+ 		} else if (!local->ap->num_sta) {
+ 			/*
+ 			 * There are no stations, get the hell out!
+ 			 */
+ 			ret = 0; /* drop packet */
+ 			goto fail;
  		}
  	}
  


From wim  Tue Aug 26 13:10:40 2003
From: wim (Wim Osterholt)
Date: Tue, 26 Aug 2003 22:10:40 +0200 (MEST)
Subject: Subject: prism2_srec bugs
In-Reply-To: <20030826020442.GA3273@jm.kir.nu> from "Jouni Malinen" at Aug 25,
	2003 07:04:42 PM
Message-ID: <20030826201041.7010.qmail@djo.tudelft.nl>


> On Mon, Aug 25, 2003 at 11:16:21PM +0200, Wim Osterholt wrote:
>
> > I'll presumably be the only person in the world that likes to preserve the
> > cards contents before trying to upgrade it beyond repair. :-)
...
> 
> > Could you fix prism2_srec somehow, please.
> 
> If it ain't broken, there's nothing to fix ;-). Feel free to file a
> feature request for adding a flash image dump to the program.

Since you so skillfully deciphered my intentions from that message,
you could have noticed the request was already there.


Regards, Wim.






From jsun  Tue Aug 26 22:56:50 2003
From: jsun (Jun Sun)
Date: Tue, 26 Aug 2003 22:56:50 -0700
Subject: [PATCH] recognize Belkin F5D6020 card
Message-ID: <20030827055650.GA12030@gateway.junsun.net>

This patch is needed to bind hostap with belkin f5d6020 card.

Jun
-------------- next part --------------
diff -Nru hostap/driver/etc/hostap_cs.conf.orig hostap/driver/etc/hostap_cs.conf
--- hostap/driver/etc/hostap_cs.conf.orig	2003-08-26 14:32:05.000000000 -0700
+++ hostap/driver/etc/hostap_cs.conf	2003-08-26 22:48:27.000000000 -0700
@@ -105,6 +105,10 @@
    manfid 0x0156, 0x0002
    bind "hostap_cs"
 
+card "Belkin 802.11b WLAN PCMCIA"
+   manfid 0x0156, 0x0002
+   bind "hostap_cs"
+
 card "Senao SL-2011CD/SL-2011CDPLUS"
    version "INTERSIL", "HFA384x/IEEE", "Version 01.02"
    manfid 0x0156, 0x0002


From jsun  Tue Aug 26 23:03:11 2003
From: jsun (Jun Sun)
Date: Tue, 26 Aug 2003 23:03:11 -0700
Subject: modversion issue on redhat 9
Message-ID: <20030827060311.GB12030@gateway.junsun.net>

I am surprised that nobody has reported this problem before.

Basically if you compile hostap modules for a redhat 9 box, you
will end up many unresolved kernel symbols when you install the modules.

The problem is that hostap would include linux/modversions.h file ahead
of all other header files, but in reality this file needs to be included
after linux/rhconfig.h file because many #ifdef's used there.

I attached a quick hack here which makes thing work.  I suspect
the true fix is in linux/modversions.h, which should include
linux/rhconfig.h

Jun

-------------- next part --------------
diff -Nru hostap/Makefile.orig hostap/Makefile
--- hostap/Makefile.orig	2003-08-26 14:32:03.000000000 -0700
+++ hostap/Makefile	2003-08-26 17:49:55.000000000 -0700
@@ -86,7 +87,7 @@
 endif
 
 ifdef CONFIG_MODVERSIONS
-CFLAGS += -DMODVERSIONS -include $(KERNEL_PATH)/include/linux/modversions.h
+CFLAGS += -DMODVERSIONS -include $(KERNEL_PATH)/include/linux/rhconfig.h -include $(KERNEL_PATH)/include/linux/modversions.h
 endif
 
 ifdef CONFIG_SMP


From sneeze  Wed Aug 27 01:12:17 2003
From: sneeze (Ryan Abbenhuys)
Date: Wed, 27 Aug 2003 18:12:17 +1000
Subject: modversion issue on redhat 9
References: <20030827060311.GB12030@gateway.junsun.net>
Message-ID: <002801c36c72$ef6c4e70$0200a8c0@silver>

Hostap installs perfectly for me under Redhat9 using pcmcia-cs-3.2.4 and
kernel 2.4.21
No unresolved symbols or errors.  HostAP appears to function fine, it's just
that I have no Tx-Power settings or ability to alter it.


----- Original Message ----- 
From: "Jun Sun" <jsun at junsun.net>
To: <hostap at shmoo.com>
Sent: Wednesday, August 27, 2003 4:03 PM
Subject: modversion issue on redhat 9


> I am surprised that nobody has reported this problem before.
>
> Basically if you compile hostap modules for a redhat 9 box, you
> will end up many unresolved kernel symbols when you install the modules.
>
> The problem is that hostap would include linux/modversions.h file ahead
> of all other header files, but in reality this file needs to be included
> after linux/rhconfig.h file because many #ifdef's used there.
>
> I attached a quick hack here which makes thing work.  I suspect
> the true fix is in linux/modversions.h, which should include
> linux/rhconfig.h
>
> Jun
>
>


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


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




From bhlim  Wed Aug 27 04:26:45 2003
From: bhlim (Byunghwan Lim)
Date: Wed, 27 Aug 2003 20:26:45 +0900
Subject: modversion issue on redhat 9
In-Reply-To: <20030827060311.GB12030@gateway.junsun.net>
Message-ID: <001c01c36c8e$1e0cd860$bf60e8da@bhlim>

Hi,

After patch, I'm still having a unresolved symbol problem.
I'm using host-0.0.4 and redhat 9.0.
Is there anything wrong with the following ?

Host-0.0.4> patch -p1 < hostap-rh9-modversion-hack.patch
Host-0.0.4> make pccard
Host-0.0.4> make install_pccard

===============
depmod: *** Unresolved symbols in /lib/modules/2.4.20-8/net/hostap_pci.o
depmod:         hostap_set_encryption_R8aaee091
depmod:         hostap_setup_dev_R585c8fcf
depmod:         hostap_handle_sta_rx_R8a16aa2f
depmod:         hostap_info_init_R95534460
depmod:         hostap_init_proc_R7516ad70
depmod:         hostap_remove_proc_Rbff91d9d
depmod:         hostap_add_wds_link_Ra24606a9
depmod:         hostap_check_sta_fw_version_R1e0fcefb
depmod:         hostap_update_rx_stats_R13da1e24
depmod:         hostap_info_process_Re1f71c8d
depmod:         hostap_get_porttype_R431841a9
depmod:         hostap_free_data_R9f39cf07
depmod:         hostap_update_sta_ps_R799b9cbc
depmod:         hostap_handle_sta_crypto_R1d22880d
depmod:         hostap_handle_sta_tx_Rd71e2af9
depmod:         hostap_handle_sta_tx_exc_Ra3141dc7
depmod:         hostap_is_sta_assoc_Rd822bfb8
depmod:         hostap_set_hostapd_R0921b1a0
depmod:         hostap_init_data_R2788054f
depmod:         hostap_rx_R66d8552a
depmod:         hostap_set_antsel_R362084f8


Thank you
-Brian

-----Original Message-----
From: hostap-bounces+bhlim=icablesystem.com at shmoo.com
[mailto:hostap-bounces+bhlim=icablesystem.com at shmoo.com] On Behalf Of
Jun Sun
Sent: Wednesday, August 27, 2003 3:03 PM
To: hostap at shmoo.com
Subject: modversion issue on redhat 9

I am surprised that nobody has reported this problem before.

Basically if you compile hostap modules for a redhat 9 box, you
will end up many unresolved kernel symbols when you install the modules.

The problem is that hostap would include linux/modversions.h file ahead
of all other header files, but in reality this file needs to be included
after linux/rhconfig.h file because many #ifdef's used there.

I attached a quick hack here which makes thing work.  I suspect
the true fix is in linux/modversions.h, which should include
linux/rhconfig.h

Jun






From askatti  Wed Aug 27 05:31:14 2003
From: askatti (Anand S. Katti)
Date: Wed, 27 Aug 2003 18:01:14 +0530 (IST)
Subject: hostap IAPP
Message-ID: <Pine.LNX.4.44.0308271755050.10207-100000@ece.iisc.ernet.in>

Hi all,

Could any of you tell me whether hostAP can talk to other dedicated access 
points(like d-link AP).

Like I, have a hostap at one end and D-link AP at the other side, and I 
move a wireless node(Laptop) from BSS1  of hostAP to BSS2 of Dlink.
Then in can't ping any of the machines in the BSS1 governed by HostAP.

does this mean that, there is no proper communication between these two 
AP's?

Or the Dlink AP shud be set as repeater ?

Please shed light on this,


-- 
--------------.				
With Regards,   
Anand S. Katti




From erich  Mon Aug 25 06:30:58 2003
From: erich (Erich Schubert)
Date: Mon, 25 Aug 2003 15:30:58 +0200
Subject: A couple of Problems with hostap and 802.1x
In-Reply-To: <20030823020522.GF3226@jm.kir.nu>
References: <20030820160602.GA7888@legolas.drinsama.de>
	<20030823020522.GF3226@jm.kir.nu>
Message-ID: <20030825133058.GB16342@wintermute.xmldesign.de>

> > Well, that leads to my questions already. ;)
> > - xsupplicant: using the same certificates i can't get it to work. It
> > sends out the user name; on the machine running hostapd i do see the EAP
> > Challenge being sent out, on the client i don't see it coming in with
> > ethereal. I guess that is why xsupplicant doesn't reply. Any ideas?
> 
> Seeing hostapd debug log with at least debug=2 (or -dd in command line)
> level could be helpful to find out what did not work.

I have been running hostapd with -dd, freeradius with -XA and ethereal
in order to get it working. No success yet.

> > - dynamic wep rekeying with EAP-TSL and win2k. Does this work? when i
> > enable rekeying in hostapd authentication fails:
> > wlan0: encryption configured, but RX frame not encrypted (SA=...)
> > i guess that is the reply frame.
> 
> It should work. How did you configure hostapd for this? With both
> broadcast and unicast keys? Does EAP-TLS succeed in this setup or do you
> get that frame drop messages already for an EAPOL packet?

It seems the first EAPOL packet gets through, but nothing more. Maybe
the reply packet isn't arriving correctly. I have a third machine with
WLAN here, Knoppix-based (i'm using to try xsupplicant) but i couldn't
get useful dumps there either.

I tried EAP-TSL with a fixed WEP-Key, but i think i had problems with
that, too. Using WEP without 802.1x was fine though.
I tried at least both multicast and unicast keys enabled (default
values). Is it easier to just try one first?

> > Another question: When 802.11i is finished; are there people working on
> > implementing these for linux already?
> 
> Yes.

Great.

Gruss,
Erich Schubert
-- 
    erich@(mucl.de|debian.org)      --      GPG Key ID: 4B3A135C    (o_
   There was never a good war or a bad peace. - Benjamin Franklin   //\
    Die Freunde nennen sich aufrichtig. Die Feinde sind es: Daher   V_/_
      man ihren Tadel zur Selbsterkenntnis benutzen sollte, als
            eine bittere Arznei.  --- Arthur Schopenhauer



From erich  Mon Aug 25 06:49:39 2003
From: erich (Erich Schubert)
Date: Mon, 25 Aug 2003 15:49:39 +0200
Subject: Some more questions...
In-Reply-To: <20030823020522.GF3226@jm.kir.nu>
References: <20030820160602.GA7888@legolas.drinsama.de>
	<20030823020522.GF3226@jm.kir.nu>
Message-ID: <20030825134939.GC16342@wintermute.xmldesign.de>

One more questions:
Is it possible to use a prism 2.5 card in two modes at the same time?
Basically i want the following setup:
802.1x EAP/TSL authenticated frames (private ESSID) should be routed to
one destination, all other (ESSID any, no WEP) should be routed to a
hotspot server (people are expected to use ipsec if they want security
then)
I'd prefer these two connections to be kept apart, like two eth devices.
That would make it very easy to direct the packets to the proper
destination by iptables.
Ultimately two concurrent EAP/TSL sessions would be nice (separated by
ESSID), until 802.11i is finished. ;)

Does that work, or would you need two wlan cards?

Gruss,
Erich Schubert
-- 
    erich@(mucl.de|debian.org)      --      GPG Key ID: 4B3A135C    (o_
     Go away or i'll replace you with a very small shell script.    //\
   Wirklich gute Freunde machen sich erst aus dem Staub, wenn man   V_/_
           sie braucht. --- Charles Maurice de Tayllerand



From erich  Tue Aug 26 00:40:13 2003
From: erich (Erich Schubert)
Date: Tue, 26 Aug 2003 09:40:13 +0200
Subject: A couple of Problems with hostap and 802.1x
In-Reply-To: <20030823020522.GF3226@jm.kir.nu>
References: <20030820160602.GA7888@legolas.drinsama.de>
	<20030823020522.GF3226@jm.kir.nu>
Message-ID: <20030826074013.GA24751@wintermute.xmldesign.de>

> > - dynamic wep rekeying with EAP-TSL and win2k. Does this work? when i
> > enable rekeying in hostapd authentication fails:
> > wlan0: encryption configured, but RX frame not encrypted (SA=...)
> > i guess that is the reply frame.
> 
> It should work. How did you configure hostapd for this? With both
> broadcast and unicast keys? Does EAP-TLS succeed in this setup or do you
> get that frame drop messages already for an EAPOL packet?

Seems like using
wep_key_len_broadcast=0
wep_key_len_unicast=13
wep_rekey_period=60

my win2k test client was assigned a 13 byte key.
But it doesn't change after 60 seconds.
AND the win2k seems to transmit unencrypted:
kernel: wlan0: encryption configured, but RX frame not encrypted (SA=

when i run
  hostap_crypt_conf wlan0 <station MAC> NULL
transmission works.

Manually setting the broadcast TX key and station TX key on the server
as well as the (only?) TX key on the Win2K client to the same value on
resulted in a successful 802.1x re-authentication and successful
connection. Can this be card-depending on Win2K?
Since i'm a linux-only guy myself i don't know too much about Windows...
i have read in the howtos that WinXP seems to have the configuration
unified, whereas Win2k seems to have this done by the card driver.

Gruss,
Erich Schubert
-- 
      erich@(mucl.de|debian.org)      --      GPG Key ID: 4B3A135C     (o_
 A man doesn't know what he knows until he knows what he doesn't know. //\
 Mancher findet sein Herz nicht eher, als bis er seinen Kopf verliert. V_/_



From erich  Tue Aug 26 09:10:24 2003
From: erich (Erich Schubert)
Date: Tue, 26 Aug 2003 18:10:24 +0200
Subject: 802.1x automatic WEP key negotiation problems
In-Reply-To: <873cfobih9.fsf@nausicaa.krose.org>
References: <873cfobih9.fsf@nausicaa.krose.org>
Message-ID: <20030826161024.GA12719@wintermute.xmldesign.de>

> Sorry to spam the list if you guys got this already, but I got no
> response and I wanted to make sure the list's mail problems didn't
> blackhole the message.  (The following two emails don't appear in the
> archives, for instance.)

Your mail got through. But my mails aren't in the web interface either.

I got the same results, theres just one small thing i investigated
further: when i set the broadcast transmit key on the hostap and the
(only) key on the win2k box to the "host key" that was negotiated
then ping works fine (not too surprising though. ;)

Gruss,
Erich Schubert
-- 
    erich@(mucl.de|debian.org)      --      GPG Key ID: 4B3A135C    (o_
          There are only 10 types of people in the world:           //\
          Those who understand binary and those who don't           V_/_
   Mathematik: Das Alphabet, mit dessen Hilfe Gott das Universum
                beschrieben hat. --- Galileo Galilei



From sits  Wed Aug 27 08:25:27 2003
From: sits (Sitsofe Wheeler)
Date: Wed, 27 Aug 2003 15:25:27 -0000
Subject: [PATCH] recognize Belkin F5D6020 card
In-Reply-To: <20030827055650.GA12030@gateway.junsun.net>
References: <20030827055650.GA12030@gateway.junsun.net>
Message-ID: <1061997946.1454.4.camel@subsub.caederus.com>

On Wed, 2003-08-27 at 06:56, Jun Sun wrote:
> This patch is needed to bind hostap with belkin f5d6020 card.
Please don't apply this patch as is. There are lots of cards that match
the description within it so it would be better to brand these as
generic intersil prism chipsets than as the product of one particular
vendor.




From jsun  Wed Aug 27 10:02:15 2003
From: jsun (Jun Sun)
Date: Wed, 27 Aug 2003 10:02:15 -0700
Subject: modversion issue on redhat 9
In-Reply-To: <002801c36c72$ef6c4e70$0200a8c0@silver>
References: <20030827060311.GB12030@gateway.junsun.net>
	<002801c36c72$ef6c4e70$0200a8c0@silver>
Message-ID: <20030827170215.GA14228@gateway.junsun.net>

On Wed, Aug 27, 2003 at 06:12:17PM +1000, Ryan Abbenhuys wrote:
> Hostap installs perfectly for me under Redhat9 using pcmcia-cs-3.2.4 and
> kernel 2.4.21
> No unresolved symbols or errors.  HostAP appears to function fine, it's just
> that I have no Tx-Power settings or ability to alter it.
>

My report is only applicable to the original kernel that comes with
RedHat CD.

After you re-configure and re-compile the kernel, or even upgrade
the kernel through rpms, things can be quite different.  IIRC, earlier
RH kernels (such as 7.x) don't use MODVERSIONS.  That is probably why I
did not notice this problem.

Jun

> 
> ----- Original Message ----- 
> From: "Jun Sun" <jsun at junsun.net>
> To: <hostap at shmoo.com>
> Sent: Wednesday, August 27, 2003 4:03 PM
> Subject: modversion issue on redhat 9
> 
> 
> > I am surprised that nobody has reported this problem before.
> >
> > Basically if you compile hostap modules for a redhat 9 box, you
> > will end up many unresolved kernel symbols when you install the modules.
> >
> > The problem is that hostap would include linux/modversions.h file ahead
> > of all other header files, but in reality this file needs to be included
> > after linux/rhconfig.h file because many #ifdef's used there.
> >
> > I attached a quick hack here which makes thing work.  I suspect
> > the true fix is in linux/modversions.h, which should include
> > linux/rhconfig.h
> >
> > Jun
> >
> >
> 
> 
> ----------------------------------------------------------------------------
> ----
> 
> 
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
> >
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap



From jsun  Wed Aug 27 10:03:17 2003
From: jsun (Jun Sun)
Date: Wed, 27 Aug 2003 10:03:17 -0700
Subject: modversion issue on redhat 9
In-Reply-To: <001c01c36c8e$1e0cd860$bf60e8da@bhlim>
References: <20030827060311.GB12030@gateway.junsun.net>
	<001c01c36c8e$1e0cd860$bf60e8da@bhlim>
Message-ID: <20030827170317.GB14228@gateway.junsun.net>

On Wed, Aug 27, 2003 at 08:26:45PM +0900, Byunghwan Lim wrote:
> Hi,
> 
> After patch, I'm still having a unresolved symbol problem.
> I'm using host-0.0.4 and redhat 9.0.
> Is there anything wrong with the following ?
> 
> Host-0.0.4> patch -p1 < hostap-rh9-modversion-hack.patch
> Host-0.0.4> make pccard
> Host-0.0.4> make install_pccard
>

This is a different issue.  Try "make uninstall" and then "make install_pccard".

Jun
 
> ===============
> depmod: *** Unresolved symbols in /lib/modules/2.4.20-8/net/hostap_pci.o
> depmod:         hostap_set_encryption_R8aaee091
> depmod:         hostap_setup_dev_R585c8fcf
> depmod:         hostap_handle_sta_rx_R8a16aa2f
> depmod:         hostap_info_init_R95534460
> depmod:         hostap_init_proc_R7516ad70
> depmod:         hostap_remove_proc_Rbff91d9d
> depmod:         hostap_add_wds_link_Ra24606a9
> depmod:         hostap_check_sta_fw_version_R1e0fcefb
> depmod:         hostap_update_rx_stats_R13da1e24
> depmod:         hostap_info_process_Re1f71c8d
> depmod:         hostap_get_porttype_R431841a9
> depmod:         hostap_free_data_R9f39cf07
> depmod:         hostap_update_sta_ps_R799b9cbc
> depmod:         hostap_handle_sta_crypto_R1d22880d
> depmod:         hostap_handle_sta_tx_Rd71e2af9
> depmod:         hostap_handle_sta_tx_exc_Ra3141dc7
> depmod:         hostap_is_sta_assoc_Rd822bfb8
> depmod:         hostap_set_hostapd_R0921b1a0
> depmod:         hostap_init_data_R2788054f
> depmod:         hostap_rx_R66d8552a
> depmod:         hostap_set_antsel_R362084f8
> 
> 
> Thank you
> -Brian
> 
> -----Original Message-----
> From: hostap-bounces+bhlim=icablesystem.com at shmoo.com
> [mailto:hostap-bounces+bhlim=icablesystem.com at shmoo.com] On Behalf Of
> Jun Sun
> Sent: Wednesday, August 27, 2003 3:03 PM
> To: hostap at shmoo.com
> Subject: modversion issue on redhat 9
> 
> I am surprised that nobody has reported this problem before.
> 
> Basically if you compile hostap modules for a redhat 9 box, you
> will end up many unresolved kernel symbols when you install the modules.
> 
> The problem is that hostap would include linux/modversions.h file ahead
> of all other header files, but in reality this file needs to be included
> after linux/rhconfig.h file because many #ifdef's used there.
> 
> I attached a quick hack here which makes thing work.  I suspect
> the true fix is in linux/modversions.h, which should include
> linux/rhconfig.h
> 
> Jun
> 
> 



From jsun  Wed Aug 27 10:10:15 2003
From: jsun (Jun Sun)
Date: Wed, 27 Aug 2003 10:10:15 -0700
Subject: [PATCH] recognize Belkin F5D6020 card
In-Reply-To: <1061997946.1454.4.camel@subsub.caederus.com>
References: <20030827055650.GA12030@gateway.junsun.net>
	<1061997946.1454.4.camel@subsub.caederus.com>
Message-ID: <20030827171015.GC14228@gateway.junsun.net>

On Wed, Aug 27, 2003 at 04:25:46PM +0100, Sitsofe Wheeler wrote:
> On Wed, 2003-08-27 at 06:56, Jun Sun wrote:
> > This patch is needed to bind hostap with belkin f5d6020 card.
> Please don't apply this patch as is. There are lots of cards that match
> the description within it so it would be better to brand these as
> generic intersil prism chipsets than as the product of one particular
> vendor.

Good catch.  

After another look of the config file, I found about there about 4 or 5
of them have the same manfid.

However, I am not sure how to bind hostap_cs to devices only based on
manfid.  Any pcmcia expert here can shed some light?

Jun



From andreaf  Wed Aug 27 12:09:33 2003
From: andreaf (Andrea G. Forte)
Date: Wed, 27 Aug 2003 15:09:33 -0400 (EDT)
Subject: hostAP client source?
Message-ID: <200308271909.h7RJ9XDY009064@cisalpino.cs.columbia.edu>

Hello guys,
I am trying to look for the source code of the CLIENT part of hostAP. Anybody 
knows where I can find it?
Thanks a lot,
Andrea




From jsun  Wed Aug 27 15:45:58 2003
From: jsun (Jun Sun)
Date: Wed, 27 Aug 2003 15:45:58 -0700
Subject: prism2_srec flashing - Exact NICID was not found ...
Message-ID: <20030827224558.GA15548@gateway.junsun.net>


When I was trying to upgrade the station firmware on a 0x8008 v1.0.1 card,
I got a "Exact NICID was not found.." warning.  See the detail output
attached.

Can I proceed to flash with "-i" option?  In fact I seem to remember
Jouni saying "-i" option is ignored when doing flash firmware
upgrade.  Does this mean I can't upgrade station firmware on this card?

Has anybody tried 1.5.6 station firmware on this chip revision?  If
this version works, I wonder if I should just change the program
and flash it anyway.

Thanks.

Jun
-------------- next part --------------
[root at localhost 1.5.6]# ../../../build/hostap-030826.1433/hostap/utils/prism2_srec -v wlan1 s1010506.hex 
S3 CRC-16 generation record: start=0x003F1800 len=51140 prog=1
Start address 0x00000000
srec summary for s1010506.hex
Component: 0x001f 1.5.6 (station firmware)
Supported platforms:
  0x8002 1.0.0,  0x8002 1.0.1,  0x8003 1.0.0,  0x8003 1.0.1,  0x8004 1.0.0
  0x8008 1.0.0
Interface compatibility information:
  role=Supplier variant=6 range=1-10 iface=Station Firmware-Driver (4)
  role=Actor    variant=1 range=1-1 iface=Modem-Firmware (1)
  role=Actor    variant=1 range=1-1 iface=Controller-Firmware (2)
  role=Actor    variant=1 range=1-2 iface=Primary Firmware-Driver (3)
Separate S3 data areas:
S3 area count: 3
  addr=0x003EE000..0x003EE069 (len=106)
  addr=0x003F1800..0x003FDFC3 (len=51140)
  addr=0x003FF000..0x003FFCC7 (len=3272)
Total data length: 54518
Start address 0x00000000

Wireless LAN card information:
Components:
  NICID: 0x8008 v1.0.1
  PRIID: 0x0015 v0.3.0
  STAID: 0x001f v0.8.2
Interface compatibility information:
  PRI role=Supplier variant=1 range=1-1 iface=Modem-Firmware (1)
  PRI role=Supplier variant=1 range=1-1 iface=Controller-Firmware (2)
  PRI role=Supplier variant=1 range=1-2 iface=Primary Firmware-Driver (3)
  STA role=Supplier variant=1 range=1-6 iface=Station Firmware-Driver (4)
  PRI role=Actor    variant=1 range=1-1 iface=Controller-Firmware (2)
  STA role=Actor    variant=1 range=1-1 iface=Controller-Firmware (2)
  STA role=Actor    variant=1 range=1-1 iface=Modem-Firmware (1)

Verifying update compatibility and combining data:
Exact NICID was not found from the list of supported platforms, but an
alternative that has been reported to work was found.
Plugging PDR 0xffffffff at 0x003fcb7a (len=14)
Plugging PDR 0x0202 at 0x003fdb46 (len=100)
Plugging PDR 0x0203 at 0x003fdbaa (len=128)
Plugging PDR 0x0204 at 0x003fdc2a (len=80)
Plugging PDR 0x0405 at 0x003fdc7a (len=4)
PDR 0x0405 not found from wlan card PDA. Using default data.
  len=4: 00 00 00 30
Plugging PDR 0x0300 at 0x003fdc7e (len=28)
Plugging PDR 0x0301 at 0x003fdc9a (len=34)
Plugging PDR 0x0101 at 0x003fde78 (len=6)
Plugging PDR 0x0103 at 0x003fcb3c (len=12)
Plugging PDR 0x0104 at 0x003fcc74 (len=2)
Plugging PDR 0x0105 at 0x003fde84 (len=2)
Plugging PDR 0x0105 at 0x003fccaa (len=2)
Plugging PDR 0x0105 at 0x003fdf80 (len=2)
Plugging PDR 0x0107 at 0x003fcb4a (len=2)
Plugging PDR 0x0006 at 0x003fcb16 (len=10)
Plugging PDR 0x0406 at 0x003fdf18 (len=2)
PDR 0x0406 not found from wlan card PDA. Using default data.
  len=2: 64 00
Plugging PDR 0x0303 at 0x003fdcc0 (len=2)
PDR 0x0303 not found from wlan card PDA. Using default data.
  len=2: ff 1f
Generating CRC-16 (start=0x003f1800, len=51140) at 0x003f17fe
OK.



From jkmaline  Wed Aug 27 17:48:28 2003
From: jkmaline (Jouni Malinen)
Date: Wed, 27 Aug 2003 17:48:28 -0700
Subject: modversion issue on redhat 9
In-Reply-To: <20030827060311.GB12030@gateway.junsun.net>
References: <20030827060311.GB12030@gateway.junsun.net>
Message-ID: <20030828004828.GA3441@jm.kir.nu>

On Tue, Aug 26, 2003 at 11:03:11PM -0700, Jun Sun wrote:

> Basically if you compile hostap modules for a redhat 9 box, you
> will end up many unresolved kernel symbols when you install the modules.
> 
> The problem is that hostap would include linux/modversions.h file ahead
> of all other header files, but in reality this file needs to be included
> after linux/rhconfig.h file because many #ifdef's used there.

I use only the vanilla kernel tarballs from www.kernel.org. If vendors
make incompatible changes to these, I will not notice it and someone
else will have to make a workaround for it. I can then consider
including the patch if it is clean, necessary, and does not break any
existing functionality.

> I attached a quick hack here which makes thing work.  I suspect
> the true fix is in linux/modversions.h, which should include
> linux/rhconfig.h

I think that the real solution is to use kernel Makefiles when building
the Host AP modules. Just run plain 'make' in Host AP top directory. I
have not tested it with Red Hat kernels, though. If it does not work,
we can consider what else could be done to resolve the issue.

> diff -Nru hostap/Makefile.orig hostap/Makefile
> --- hostap/Makefile.orig	2003-08-26 14:32:03.000000000 -0700
> +++ hostap/Makefile	2003-08-26 17:49:55.000000000 -0700
> @@ -86,7 +87,7 @@
>  endif
>  
>  ifdef CONFIG_MODVERSIONS
> -CFLAGS += -DMODVERSIONS -include $(KERNEL_PATH)/include/linux/modversions.h
> +CFLAGS += -DMODVERSIONS -include $(KERNEL_PATH)/include/linux/rhconfig.h -include $(KERNEL_PATH)/include/linux/modversions.h
>  endif

Doesn't this break compilation for all non-RH kernels? In general, my
policy is not to add distro-specific changes to the Host AP tarball. The
best place for these would be in a separate patch file that could be
used, e.g., in an RPM.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Aug 27 17:49:09 2003
From: jkmaline (Jouni Malinen)
Date: Wed, 27 Aug 2003 17:49:09 -0700
Subject: [PATCH] recognize Belkin F5D6020 card
In-Reply-To: <20030827055650.GA12030@gateway.junsun.net>
References: <20030827055650.GA12030@gateway.junsun.net>
Message-ID: <20030828004909.GB3441@jm.kir.nu>

On Tue, Aug 26, 2003 at 10:56:50PM -0700, Jun Sun wrote:

> This patch is needed to bind hostap with belkin f5d6020 card.

> +card "Belkin 802.11b WLAN PCMCIA"
> +   manfid 0x0156, 0x0002
> +   bind "hostap_cs"

I will not add manfid 0x0156, 0x0002 because it used by many non-Prism2
cards. Please either send an entry that is using version line or send
full output of 'cardctl ident' when the card is inserted, so that I can
make a proper entry for this card.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Aug 27 17:52:19 2003
From: jkmaline (Jouni Malinen)
Date: Wed, 27 Aug 2003 17:52:19 -0700
Subject: prism2_srec flashing - Exact NICID was not found ...
In-Reply-To: <20030827224558.GA15548@gateway.junsun.net>
References: <20030827224558.GA15548@gateway.junsun.net>
Message-ID: <20030828005219.GC3441@jm.kir.nu>

On Wed, Aug 27, 2003 at 03:45:58PM -0700, Jun Sun wrote:

> When I was trying to upgrade the station firmware on a 0x8008 v1.0.1 card,
> I got a "Exact NICID was not found.." warning.  See the detail output
> attached.
> 
> Can I proceed to flash with "-i" option?  In fact I seem to remember
> Jouni saying "-i" option is ignored when doing flash firmware
> upgrade.  Does this mean I can't upgrade station firmware on this card?

Yes, "-i" would be ignored in this case and prism2_srec refuses to
download that flash image to the card. If you want to risk killing the
card, you can of course comment this verification out from prism2_srec.
However, I would strongly recommend first testing a RAM-downloadable
version of the exact same image to verify that it works with your card.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jsun  Wed Aug 27 19:14:35 2003
From: jsun (Jun Sun)
Date: Wed, 27 Aug 2003 19:14:35 -0700
Subject: [PATCH] recognize Belkin F5D6020 card
In-Reply-To: <20030828004909.GB3441@jm.kir.nu>
References: <20030827055650.GA12030@gateway.junsun.net>
	<20030828004909.GB3441@jm.kir.nu>
Message-ID: <20030828021435.GA20519@gateway.junsun.net>

On Wed, Aug 27, 2003 at 05:49:09PM -0700, Jouni Malinen wrote:
> On Tue, Aug 26, 2003 at 10:56:50PM -0700, Jun Sun wrote:
> 
> > This patch is needed to bind hostap with belkin f5d6020 card.
> 
> > +card "Belkin 802.11b WLAN PCMCIA"
> > +   manfid 0x0156, 0x0002
> > +   bind "hostap_cs"
> 
> I will not add manfid 0x0156, 0x0002 because it used by many non-Prism2
> cards. Please either send an entry that is using version line or send
> full output of 'cardctl ident' when the card is inserted, so that I can
> make a proper entry for this card.
>

Ahh, I understood it wrong with Sitsofe's email.  Here is
the patch which should be acceptable.

Jun
-------------- next part --------------
diff -Nru ./driver/etc/hostap_cs.conf.orig ./driver/etc/hostap_cs.conf
--- ./driver/etc/hostap_cs.conf.orig    2003-08-26 14:32:05.000000000 -0700
+++ ./driver/etc/hostap_cs.conf 2003-08-27 19:06:04.000000000 -0700
@@ -105,6 +105,11 @@
    manfid 0x0156, 0x0002
    bind "hostap_cs"
 
+card "Belkin 802.11b WLAN PCMCIA"
+   version "Belkin", "11Mbps Wireless Notebook Network Adapter", "Version 01.02"
+   manfid 0x0156, 0x0002
+   bind "hostap_cs"
+
 card "Senao SL-2011CD/SL-2011CDPLUS"
    version "INTERSIL", "HFA384x/IEEE", "Version 01.02"
    manfid 0x0156, 0x0002


From jsun  Wed Aug 27 19:23:33 2003
From: jsun (Jun Sun)
Date: Wed, 27 Aug 2003 19:23:33 -0700
Subject: updated min-HOWTO on flashing firmware
Message-ID: <20030828022333.GA20547@gateway.junsun.net>


I have updated the page to include linux-based prism2_srec flashing.  
It is awesome.  Big "thank-you" to Jouni.

Raffaele Raf also beautified his success story on DOS-based flashing
tools.  Plus a couple of other misc updates.

http://linux.junsun.net/intersil-prism/

Enjoy.

Jun



From lanev007  Wed Aug 27 19:52:30 2003
From: lanev007 (=?iso-8859-1?q?Veronica=20Lane?=)
Date: Thu, 28 Aug 2003 03:52:30 +0100 (BST)
Subject: Hostap driver problem
Message-ID: <20030828025230.64687.qmail@web80707.mail.yahoo.com>

hi guys, 

i just wanted to ask if there is an available driver
for hostap that is in the rpm version? i really would
like to know and your help would be greatly
appreciated.

thanks!!
veronica

________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://uk.messenger.yahoo.com/



From jkmaline  Wed Aug 27 20:17:41 2003
From: jkmaline (Jouni Malinen)
Date: Wed, 27 Aug 2003 20:17:41 -0700
Subject: [PATCH] recognize Belkin F5D6020 card
In-Reply-To: <20030828021435.GA20519@gateway.junsun.net>
References: <20030827055650.GA12030@gateway.junsun.net>
	<20030828004909.GB3441@jm.kir.nu>
	<20030828021435.GA20519@gateway.junsun.net>
Message-ID: <20030828031741.GA4195@jm.kir.nu>

On Wed, Aug 27, 2003 at 07:14:35PM -0700, Jun Sun wrote:

> Ahh, I understood it wrong with Sitsofe's email.  Here is
> the patch which should be acceptable.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From eaglecz  Thu Aug 28 00:10:38 2003
From: eaglecz (Tomas Charvat)
Date: Thu, 28 Aug 2003 09:10:38 +0200
Subject: card resset, clients not back
Message-ID: <003d01c36d33$7bdebb20$050314ac@rip>

gereting it happen to me few times with Cvs 14 days old, that this msg
apeared in syslog

Aug 28 00:37:15 nest kernel: NETDEV WATCHDOG: wlan3: transmit timed out
Aug 28 00:37:15 nest kernel: wlan3 Tx timed out! Resetting card
Aug 28 00:37:15 nest kernel: wlan3: CMD=010b EVSTAT=0000 OFFSET0=0000
OFFSET1=0000 SWSUPPORT0=8a32
Aug 28 00:37:15 nest kernel: wlan3: scheduled card reset
Aug 28 00:37:15 nest kernel: hostap_pci: wlan3: resetting card

and client wasnt able to connect back to ap.... usualy manual card reset
solve the problem,
but may be he is able to connect back in few mins.
anyway there is not msg about auth or any other action in syslog after that
error
and afetr 8 hours client was back online

my Fw is 1.7.4/1.1.1

and i must say it happen only on one if 5 Aps i have

regards
tomas





From Shripad_N  Thu Aug 28 00:36:35 2003
From: Shripad_N (Shripad N)
Date: Thu, 28 Aug 2003 13:06:35 +0530
Subject: CF card...
Message-ID: <E125980C421DFD4DA0B80D55DB1EDA5801D1D9D1@mtv01ex01.mindtree.com>

Hi,
Has any one tried to install HostAp driver on a WLAN CF card...
If yes, how was the performance.

I am asking this because, i found a few entries in the hostap_cs.conf 
for CF cards.

TIA
regards
Shripad


DISCLAIMER:
This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Private Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return  e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited.  Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.



From sits  Thu Aug 28 01:35:40 2003
From: sits (Sitsofe Wheeler)
Date: Thu, 28 Aug 2003 08:35:40 -0000
Subject: Hostap RPMs (was Hostap driver problem)
In-Reply-To: <20030828025230.64687.qmail@web80707.mail.yahoo.com>
References: <20030828025230.64687.qmail@web80707.mail.yahoo.com>
Message-ID: <1062059760.1455.11.camel@subsub.caederus.com>

On Thu, 2003-08-28 at 03:52, Veronica Lane wrote:
> i just wanted to ask if there is an available driver
> for hostap that is in the rpm version? i really would
> like to know and your help would be greatly
> appreciated.
Unfortunately it is not simple to provide RPMs of kernel modules. If I
were to build an RPM for say RedHat 8.0 then the RPM in question will
only work on the *exact same version* of the kernel it was compiled
against. So an RPM compiled to work on RedHat will not work on Mandrake
or SuSE etc. This also means that if RedHat release an updated kernel
with security fixes and I upgrade to it (as one should) then the
existing Hostap RPM will no longer work and will have to be rebuilt
again. At any rate, you didn't say which distro and kernel you were
running so the odds of my building an RPM that would work for you are
small (and if they differ then I couldn't help you anyway).

For RedHat, there are some kernel modules that are maintained outside
the distribution though. If you look at
http://shrike.freshrpms.net/rpm.html?id=856 you will find that the alsa
modules have been packaged up and each time RedHat release an updated
kernel some poor sap goes and rebuilds the entire bunch of RPMs again.
If you want Hostap RPMs I would suggest asking the people who package
that up to help you.




From ged  Wed Aug 27 07:49:15 2003
From: ged (Ged Haywood)
Date: Wed, 27 Aug 2003 15:49:15 +0100 (BST)
Subject: modversion issue on redhat 9 (Jun Sun)
In-Reply-To: <20030827142035.9D43BFE87@mail.iocaine.com>
Message-ID: <Pine.LNX.4.21.0308271540170.7371-100000@www2.jubileegroup.co.uk>

Hello there,

On Wed, 27 Aug 2003 Jun Sun wrote:

> Basically if you compile hostap modules for a redhat 9 box, you
> will end up many unresolved kernel symbols when you install the modules.
> 
> The problem is that hostap would include linux/modversions.h file ahead
> of all other header files, but in reality this file needs to be included
> after linux/rhconfig.h file because many #ifdef's used there.

I'm not sure that's the problem.

I think you might find that the kernel and modules that ship with RH9
were not compiled with the .config that you used.  If you recompile a
kernel or any modules with the .config that came with RH9 you may need
to reinstall all the modules as well as the kernel.

You can always just compile everything with CONFIG_MOD_VERSIONS not
set in the .config but that's asking for trouble later on if you have
more than one build on your system.

73,
Ged.







From patrickp  Thu Aug 28 13:07:06 2003
From: patrickp (Patrick Poncet)
Date: Thu, 28 Aug 2003 16:07:06 -0400
Subject: best card for linux in hostap mode?
In-Reply-To: <3F4A7C1A.6070401@drdoom.net>
Message-ID: <005001c36d9f$f4f39e60$b205010a@PATRICKP>

I agree

We're using it here and it's great especially with 200mW tx power!!!  

They seem to get harder and harder to get which scares me as we rely so
much on hostap with 802.1x here...  

What is the future of hostap if most manufacturers drop the prism
chipset and those who had it get discontinued???  Any contingency plan
in the works???

Cheers!

Patrick

-----Original Message-----
From: hostap-bounces+patrick=poncet.ca at shmoo.com
[mailto:hostap-bounces+patrick=poncet.ca at shmoo.com] On Behalf Of DrDoom
Sent: August 25, 2003 4:14 PM
To: Niki Waibel; HostAP
Subject: Re: best card for linux in hostap mode?


I think SENAO 2511CD Plus ext2 is a very good choice, it has 2 MMCX 
connectors and prism2 chipset, also 200mW txpower.
http://www.seattlewireless.net/index.cgi/SenaoCard
About USB cards, hostap driver does not support USB.

-- 
-------------------------
David Martos (aka DrDoom)

http://www.sorgonet.com
-------------------------



Niki Waibel wrote:

>which wireless card would you recommend for linux in ap mode?
>
>what about this usb cards (long cable to card and short cable to 
>antenna would be nice ...)?
>
>niki w. waibel
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com http://lists.shmoo.com/mailman/listinfo/hostap
>
>  
>


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




From jsun  Thu Aug 28 13:45:10 2003
From: jsun (Jun Sun)
Date: Thu, 28 Aug 2003 13:45:10 -0700
Subject: modversion issue on redhat 9 (Jun Sun)
In-Reply-To: <Pine.LNX.4.21.0308271540170.7371-100000@www2.jubileegroup.co.uk>
References: <20030827142035.9D43BFE87@mail.iocaine.com>
	<Pine.LNX.4.21.0308271540170.7371-100000@www2.jubileegroup.co.uk>
Message-ID: <20030828204510.GA23924@gateway.junsun.net>

On Wed, Aug 27, 2003 at 03:49:15PM +0100, Ged Haywood wrote:
> Hello there,
> 
> On Wed, 27 Aug 2003 Jun Sun wrote:
> 
> > Basically if you compile hostap modules for a redhat 9 box, you
> > will end up many unresolved kernel symbols when you install the modules.
> > 
> > The problem is that hostap would include linux/modversions.h file ahead
> > of all other header files, but in reality this file needs to be included
> > after linux/rhconfig.h file because many #ifdef's used there.
> 
> I'm not sure that's the problem.
> 
> I think you might find that the kernel and modules that ship with RH9
> were not compiled with the .config that you used.  

You _have to_ make sure .config is for the kernel that you are compiling
hostap for.  Otherwise you may have bigger troubles (such as pcmcia
not enabled, etc..)

> If you recompile a
> kernel or any modules with the .config that came with RH9 you may need
> to reinstall all the modules as well as the kernel.
>

Sure.  That is DIYS kernel 101.

> You can always just compile everything with CONFIG_MOD_VERSIONS not
> set in the .config but that's asking for trouble later on if you have
> more than one build on your system.
>

See previous answer.

Jun



From drdoom  Thu Aug 28 14:17:18 2003
From: drdoom (DrDoom)
Date: Thu, 28 Aug 2003 23:17:18 +0200
Subject: No tx-power option
In-Reply-To: <3f4af751.131c.0@alphalink.com.au>
References: <3f4af751.131c.0@alphalink.com.au>
Message-ID: <3F4E715E.5020700@drdoom.net>

I saw on the Changelog
http://hostap.epitest.fi/cgi-bin/viewcvs.cgi/*checkout*/hostap/ChangeLog?rev=HEAD&content-type=text/plain
for version 0.0.4 this:

* removed TX power controlling (iwconfig txpower) since the
	  experimental algorithm in the driver did not include any feedback
	  from the measured TX power and could allow TX power values that cause
	  interference or signal quality issues; now only txpower 'off' and
	  'auto' are allowed. TX power controlling will be returned after
	  proper algorithm using feedback loop has been implemented.

That explains why it doesn't work on 0.0.4 version.


Ryan Abbenhuys wrote:

>I've just noticed that the "Tx-Power" isn't displayed on my interfaces
>running HostAP when I run an iwconfig, however other devices using other
>drivers do. (i'll try some older hostap versions when I get home tonight)
>
>I have two RH9 boxes running latest CVS of HostAP and both function
>perfectly and have been for a year or more.
>
>I used to run "iwconfig wlan0 txpower 200mW" at bootup as by default the
>card didn't run at full power.  I've since noticed the txpower command no
>longer works.
>
>[root at wantirna-ap1 etc]# iwconfig wlan0 txpower 200mW
>Error for wireless request "Set Tx Power" (8B26) :
>    SET failed on device wlan0 ; Operation not supported.
>
>Here's my iwconfig output  (notice wlan0 shows no Tx-Power while eth1
>running the orinoco driver does)....
>
>
>eth1      IEEE 802.11-DS  ESSID:"AAF_FKR_LINK"  Nickname:"wantirna-ap1"
>          Mode:Ad-Hoc  Frequency:2.437GHz  Cell: 02:00:BD:7F:DC:2A
>          Bit Rate:11Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
>          Retry limit:4   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:12647
>          Tx excessive retries:1022  Invalid misc:0   Missed beacon:0
>
>wlan0     IEEE 802.11b  ESSID:"aaf.wireless.org.au" 
>Nickname:"wantirna-ap1"
>          Mode:Master  Frequency:2.462GHz  Access Point: 00:02:6F:04:0F:81
>          Bit Rate:11Mb/s   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:964  Invalid misc:5138   Missed beacon:0
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>  
>

-- 
-------------------------
David Martos (aka DrDoom)

http://www.sorgonet.com
-------------------------





From hostap  Thu Aug 28 16:14:45 2003
From: hostap (Jeff Gold)
Date: Thu, 28 Aug 2003 19:14:45 -0400
Subject: Partial MODVERSIONS?
In-Reply-To: <3F48EAFF.2090203@esclat.net>
References: <3F48EAFF.2090203@esclat.net>
Message-ID: <3F4E8CE5.5070804@esclat.net>

Jeff Gold wrote:
> I'm attempting to get hostap-0.0.4 working with RedHat 9 using the 
> 2.4.20-20.9 kernel (which at the moment is the latest offered through 
> up2date).  [...]
> 
> Unfortunately while the hostap driver builds and installs with no 
> trouble, modprobe reports unresolved symbols when attempting to load it. 

Removing the kernel source and reinstalling it using RPM corrected the 
problem.  Something sequence of events seems to corrupt the RedHat 
provided kernel source in some way, though I've not fully investigated 
the issue.

                                         Jeff




From harry  Thu Aug 28 16:15:35 2003
From: harry (Harry Moyes)
Date: Thu, 28 Aug 2003 23:15:35 -0000
Subject: modversion issue on redhat 9 (Jun Sun)
In-Reply-To: <Pine.LNX.4.21.0308271540170.7371-100000@www2.jubileegroup.co.uk>
References: <Pine.LNX.4.21.0308271540170.7371-100000@www2.jubileegroup.co.uk>
Message-ID: <1062112555.4230.62.camel@shoka>

On Wed, 2003-08-27 at 15:49, Ged Haywood wrote:
> Hello there,
> 
> On Wed, 27 Aug 2003 Jun Sun wrote:
> 
> > Basically if you compile hostap modules for a redhat 9 box, you
> > will end up many unresolved kernel symbols when you install the modules.
> > 
> > The problem is that hostap would include linux/modversions.h file ahead
> > of all other header files, but in reality this file needs to be included
> > after linux/rhconfig.h file because many #ifdef's used there.
> 
> I'm not sure that's the problem.
> 
> I think you might find that the kernel and modules that ship with RH9
> were not compiled with the .config that you used.  If you recompile a
> kernel or any modules with the .config that came with RH9 you may need
> to reinstall all the modules as well as the kernel.
> 
> You can always just compile everything with CONFIG_MOD_VERSIONS not
> set in the .config but that's asking for trouble later on if you have
> more than one build on your system.

You don't **have** to give up on module versioning

RedHat want to keep the pristine tested kernel that they ship with the
system, and its set of matching tested modules. 

The kernel source tree as installed by the source RPMs does not contain
a .config file. If you generate a .config file to match the existing
kernel with (say) make oldconfig, or generate a new one with make config
and friends, RedHat arrange that "custom" is appended to the end of the
version string.

If you build and install this kernel and its modules, its added as an
option to the boot loader (not the default option either). You can thus
build and test it without risking having an unbootable system 

This is all fairly sensible, since if you screw up you continue to have
your original RH supplied kernel and modules to fall back on.

As an unfortunate side effect, if you simply create a new .config file
but do nothing else,when you build hostap against this .config file and
the supplied source tree, hostap will be built with module versioning to
match a mythical 2.4.xx.xxcustom kernel, and the resulting Hostap
modules will not load against the default kernel

By repute the required .config file to match the default kernel as
shipped is defconfig deeper in the source tree under say
/arch/i386/defconfig. I can't confirm that copying this to .config in
the usual location and recompiling hostap will yield hostap modules with
versioning to match the default kernel as I've never tried it myself,
but at least one source I've seen contends that it does.

Alternatively (as I've done) go the whole hog, and build your custom
kernel and modules, boot from it and your shiny new hostap modules
**will** match the running kernel, and load correctly.

So IMHO its a very sensible RedHat built safety net, that unfortunately
fails to take into account building an "external"  module within the
source tree, without rebuilding the kernel itself.

When RH 8.0 was new and shiny, there was a flurry of posts with versions
of this issue. I posted a cookbook suggestion then that got a few folks
out of trouble. Maybe adding something similar to the above to the FAQ
would help folks avoid this particular pitfall.

Harry
 





From jsun  Thu Aug 28 18:07:14 2003
From: jsun (Jun Sun)
Date: Thu, 28 Aug 2003 18:07:14 -0700
Subject: Partial MODVERSIONS?
In-Reply-To: <3F4E8CE5.5070804@esclat.net>
References: <3F48EAFF.2090203@esclat.net> <3F4E8CE5.5070804@esclat.net>
Message-ID: <20030829010714.GA24727@gateway.junsun.net>

On Thu, Aug 28, 2003 at 07:14:45PM -0400, Jeff Gold wrote:
> Jeff Gold wrote:
> >I'm attempting to get hostap-0.0.4 working with RedHat 9 using the 
> >2.4.20-20.9 kernel (which at the moment is the latest offered through 
> >up2date).  [...]
> >
> >Unfortunately while the hostap driver builds and installs with no 
> >trouble, modprobe reports unresolved symbols when attempting to load it. 
> 
> Removing the kernel source and reinstalling it using RPM corrected the 
> problem.  Something sequence of events seems to corrupt the RedHat 
> provided kernel source in some way, though I've not fully investigated 
> the issue.
>

This is exactly the same problem as I decribed the other day,
under subject of "modversion issue on redhat 9".

There is a hackish workaround proposed there.  

(Can't believe I missed this email.  I knew I shouldn't be the
first person to encounter this issue.)

Jun



From hostap  Thu Aug 28 18:42:14 2003
From: hostap (Jeff Gold)
Date: Thu, 28 Aug 2003 21:42:14 -0400
Subject: modversion issue on redhat 9 (Jun Sun)
In-Reply-To: <1062112555.4230.62.camel@shoka>
References: <Pine.LNX.4.21.0308271540170.7371-100000@www2.jubileegroup.co.uk>
	<1062112555.4230.62.camel@shoka>
Message-ID: <3F4EAF76.2050802@esclat.net>

Harry Moyes wrote:
> By repute the required .config file to match the default kernel as
> shipped is defconfig deeper in the source tree under say
> /arch/i386/defconfig. I can't confirm that copying this to .config in
> the usual location and recompiling hostap will yield hostap modules with
> versioning to match the default kernel [...]

I can.  Except that the /usr/src/linux-2.4/configs directory is where
the default configuration files are found.  Also note that copying
kernel-2.4.20-i386.config from there into the top level of the RedHat
kernel-source tree into .configs allows the external hostap driver to
build with no problems, but copying kernel-2.4.20-i686.config instead
(as I originally did) results in some but not all kernel symbols being
defined in hostap.o and friends without modversions tags.  Note the 686
instead of 386.  Possibly this is related to the rhconfig.h file issue
that Jun Sun noticed.

Once I selected the proper configuration file everything fell into place
quite nicely.  :-)

                                          Jeff





From Jan.Rovner  Fri Aug 29 00:26:54 2003
From: Jan.Rovner (Jan Rovner)
Date: Fri, 29 Aug 2003 09:26:54 +0200
Subject: associated clients are dropped and can't associate anymore
Message-ID: <1048280C59E02941820A498C13F70CD41612@server.diademasw.inkubator.cz>

Hello,

I'm using hostap-0.0.4 in Master mode and sometimes
associated clients are silently dropped and can't 
associate with AP anymore.

The only thing that helps is to drop and reload
the driver:

ifconfig wlan0 down
rmmmod hostap_pci
modprobe hostap_pci
iwconfig wlan0 ...
ifconfig wlan0 ...

Does anyone has the same experience?

Maybe a SOFTWARE WATCHDOG could be the workaround
(to periodically monitor whether such situation 
occurred and in the positive case to execute "repair" 
script).

Any idea about this? Does such watchdog exist?

Thank you very much!
Jan




From martin.polak  Fri Aug 29 04:07:27 2003
From: martin.polak (Martin Polak)
Date: Fri, 29 Aug 2003 13:07:27 +0200
Subject: Are SMP issues already resolved?
Message-ID: <3F4F33EF.4050707@liwest.at>

Hi everyone!

I am planning to migrate my hostap-box to a dual pentium pro box.
There were several reports on smp-crashes with hostap on the list.

My question now is, if it is possible to run hostap flawlessly on SMPs now?
Any comments?

Martin




From info  Fri Aug 29 10:37:23 2003
From: info (WiNet - Biuro handlowe)
Date: Fri, 29 Aug 2003 19:37:23 +0200
Subject: bridge_packets in master mode
Message-ID: <49749345.20030829193723@wi-network.net>

Hi everyone,

I have trouble with bridge_packets between wireless STA on this same
WiFi interface wlan0.

- hostap-0.0.4 in Master mode
- wireless interface wlan0
- turn off bridge_packet in hostap 'iwpriv wlan0 bridge_packet 0'
- two WiFi STA 192.168.1.1 & 192.168.1.2
- wlan0 IP is 192.168.1.254/255.255.255.0

  I want control traffic between STA and remove bridge packets directly
between stations to kernel, but first STA not see second (ping)
If bridge_packet is 1 all is ok.

Please help me, where is error?

Sorry for my English.

Yours faithfully,
__
WiNet Communications
Website: www.wi-network.net
POLAND




From jhiller  Fri Aug 29 12:49:39 2003
From: jhiller (James B. Hiller)
Date: Fri, 29 Aug 2003 15:49:39 -0400 (EDT)
Subject: Are SMP issues already resolved?
In-Reply-To: <3F4F33EF.4050707@liwest.at> from "Martin Polak" at Aug 29,
	2003 01:07:27 PM
Message-ID: <200308291950.h7TJoORU000290@bassett.home.org>

> I am planning to migrate my hostap-box to a dual pentium pro box.
> There were several reports on smp-crashes with hostap on the list.
> 
> My question now is, if it is possible to run hostap flawlessly on SMPs now?
> Any comments?

Since I started with hostap about a month ago, I've had it only on
a dual PPro box (Tyan S1662D), and have had no issues.  I was running
hostap-0.0.4 at first, and then went to the CVS version on some date
in the last month because it (the CVS version) had a fix dealing
with volatile RAM downloads; nothing to do with SMP behavior; but
point is, in the two weeks I had straight 0.0.4, no issues, and no
issues since going to CVS.

Some more specifics - am running linux-2.4.21, and the card I'm using
is a DLink DWL-520, version A1, with firmware upgraded to 1.4.9/1.1.0.
I've also had a Netgear MA 311 in there, same firmware, no issues, and
a Zcomax XI-626, same and older firmware, no issues.

FWIW - I'm about 99.9% convinced that the DLink-DWL 520 V B1, which I
have now, the Netgear MA 311, and the Zcomax XI-626 are all the same
card, and that they're all the Zcomax card as the OEM.

jbh




From jhiller  Mon Aug 25 05:34:34 2003
From: jhiller (James B. Hiller)
Date: Mon, 25 Aug 2003 08:34:34 -0400 (EDT)
Subject: prism cards
Message-ID: <200308291955.h7TJt75B000444@bassett.home.org>

>   I have also had a terrible time obtaining prism-based wireless cards.
> The best I could come up with was to troll ebay.com looking for them.

If it matters - I have had luck over the last two months in getting
two DWL-520 cards, one Rev A1 and one Rev B1, from
www.networkingoutlet.com.  Believe they can get more of these
if you push.

>   I use D-Link DWL-520 cards, which work great.  But, the Prism-based
> versions are no longer available.  Note:  the DWL-520+ are NOT Prism-based
> and will not work with hostap as far as I know.  Also, there are something
> like three variants of the DWL-520 card, and the last one is not Prism-based
> either.  The only way to tell on ebay is to closely examine the picture of
> the card.

See above on the 520.  The way I ensured my purchase would yield the
correct device, as I have with other devices of particular hardware
I wanted, was to get with the tech support folks at the vendor and
get them to put hands on the one I would be sent, and check it out.
Never have gotten any resistance when I ask for that (other than
the occasional "does it really matter to you?").

>   It seems to me that the disappearance of Prism-based cards represents a
> threat to the whole hostap project.  The hostap project is one of the most
> wonderful things I've found on the net for a while (THANKS JOUNI especially
> and all contributors!!).

Note also that the Netgear MA 311, a PCI Prism card, is readily available
at a number of places, including Circuit City and BestBuy.

I agree that finding the cards in the configuration you want can be
something of a challenge, but I'd say they're far from scarce.  With
the number of variants shown on the Absolute Value Systems page,
there a quite a few to try finding before throwing in the towel.

jbh

--h7P6JBe8000090.1061792921/bassett.home.org--






From merlin  Sat Aug 30 06:12:50 2003
From: merlin (Christian Zoffoli)
Date: Sat, 30 Aug 2003 15:12:50 +0200
Subject: best card for linux in hostap mode?
In-Reply-To: <005001c36d9f$f4f39e60$b205010a@PATRICKP>
References: <005001c36d9f$f4f39e60$b205010a@PATRICKP>
Message-ID: <3F50A2D2.7000808@studiobz.it>

Patrick Poncet wrote:
> I agree
> 
> We're using it here and it's great especially with 200mW tx power!!!  
> 
> They seem to get harder and harder to get which scares me as we rely so
> much on hostap with 802.1x here...  
> 
> What is the future of hostap if most manufacturers drop the prism
> chipset and those who had it get discontinued???  Any contingency plan
> in the works???
> 

IMHO the only solution is to merge all the interesting features of 
hostap in a project like madwifi (for Atheros based cards).

Christian






From jkmaline  Sat Aug 30 08:21:41 2003
From: jkmaline (Jouni Malinen)
Date: Sat, 30 Aug 2003 08:21:41 -0700
Subject: bridge_packets in master mode
In-Reply-To: <49749345.20030829193723@wi-network.net>
References: <49749345.20030829193723@wi-network.net>
Message-ID: <20030830152141.GA3444@jm.kir.nu>

On Fri, Aug 29, 2003 at 07:37:23PM +0200, WiNet - Biuro handlowe wrote:

> - turn off bridge_packet in hostap 'iwpriv wlan0 bridge_packet 0'
> - two WiFi STA 192.168.1.1 & 192.168.1.2

>   I want control traffic between STA and remove bridge packets directly
> between stations to kernel, but first STA not see second (ping)
> If bridge_packet is 1 all is ok.

You seem to want to send frames between two STAs, but you disable the
mechanism used for doing it.. How are you planning to bridge those
packets, if you disable this functionality in the Host AP driver? Do you
have your own code (e.g., modified Linux bridge code) somewhere in the
kernel or are you planning to use IP routing (which would not work in
the setup you mentioned since broadcast packets are not routed)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From info  Sat Aug 30 08:39:28 2003
From: info (WiNet - Biuro handlowe)
Date: Sat, 30 Aug 2003 17:39:28 +0200
Subject: bridge_packets in master mode
In-Reply-To: <20030830152141.GA3444@jm.kir.nu>
References: <49749345.20030829193723@wi-network.net>
	<20030830152141.GA3444@jm.kir.nu>
Message-ID: <901319247.20030830173928@wi-network.net>

Hello,

many thanks for Your respond.

>>   I want control traffic between STA and remove bridge packets directly
>> between stations to kernel, but first STA not see second (ping)
>> If bridge_packet is 1 all is ok.

JM> You seem to want to send frames between two STAs, but you disable the
JM> mechanism used for doing it..
YI do it because I want control traffic between STA's in my LinuxBox,
by tc in the kernel. Bridge packet in hostap is out of soft control ;-(

>From hostap_ap.h:
        int bridge_packets; /* send packet to associated STAs directly to the
                             * wireless media instead of higher layers in the
                             * kernel */

JM> Do you have your own code (e.g., modified Linux bridge code)
No, it is standard kernel 2.4.22 without bridge soft.
wlan0 is Senao SL-2511CD+Ext2:
PRIID: id=0x0015 v1.1.1
STAID: id=0x001f v1.7.4 (station firmware)

JM> somewhere in the kernel or are you planning to use IP routing
I plan do it by routing table ;-)
My kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.254.252 0.0.0.0         255.255.255.252 U     0      0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0

Have You any idea?

Sorry for my English.

Yours faithfully,
__
WiNet Communications
Website: www.wi-network.net
POLAND




From a99-4427  Sat Aug 30 09:31:46 2003
From: a99-4427 (Elias Tsigoyannis)
Date: Sat, 30 Aug 2003 19:31:46 +0300
Subject: card initialization+firmware problems
Message-ID: <002301c36f14$34de0360$8551fea9@mage>

Hello to everybody!

Can somebody explain to me the initialization process of a prism2 card?
I use the winupdate programme to upgrade the firmware of my card and it
says:

Platform:    8003
Primary Firmware:    0.3.0
Station (Secondary) Firmware: 0.6.2

At first, I would like to ask if there is a primary firmware that is newer
than 0.3.0 for my card. I have seen
primary firmwares with number 1.1.0, but they are for different platforms
(800a,etc). Is there such a firmware
for my card? I have also found secondary firmware 1.5.6 that can be flashed
to my card. Does anyone have station firmware
1.7.x for platform 8003?

Anyway, I want to use this card in ad hoc mode. At first, I was using
firmware 0.6.2. I issued the "initialize command" without
any problems, however I noticed that when I put the value 0 to RID PortType
(0xFC00) as Intersil Prism
Driver's Manual says, even though I got a link status message that said
"Connected", immediately after I issued the "enable command" (for channel
0),
the RID PortStatus (0xFD40) had the value 6 (Connected to WDS). I read
Intersil's FAQs and found out
that the old manual said that old firmwares should use value 4 for RID
PortType. I tried that and the result was
that I didn't get a Link Status message, after the "enable command", but
PortStatus had the value 3 (Connected to IBSS). The problem either way
is that I can neither send any frames nor is my IBSS detected by any network
analyzers that I've used (I have 2 pcs. In one
of them I run the wireless network analyzer and at the second one I create
the IBSS. Both of them have Intersil Prism HWB3163-EVAL
wireless cards).

Anyway, I tried upgrading the firmware to 1.4.9 and 1.5.6 and now I face a
different problem. Although I can't put value 4 to
PortType (because PortStatus gets a value not specified by Intersil's
manual), if I put value 0 to PortType, then PortStatus gets
the value 2 (Searching for initial connection) and remains there. Since I
always put value 1 to RID createIBSS (FC81) that means
that the card should either search for an ESS/IBSS or create an IBSS, after
a while the RID PortStatus should change to 3
(Connected to IBSS). However it doesn't.

Does anyone know any firmware that operates according to Intersil's Driver
Programmer's manual?
I want the following events to occur:

1)I issue the initialize command
2)I set RID PortType to 0 (or 4...however please tell me which one I should
use)
3)I set RID createIBSS to 1 (join ESS or create/join IBSS)
4)I configure DesiredSSID,OwnSSID,OwnName,Channel
5)I issue the enable command for channel 0
6)I get a link status interrupt that says that I am connected and the
PortStatus RID has the value 3 (Connected to IBSS)

If I have understood something wrong and that's not the correct
initialization sequence please inform me..

Thanks in advance,
Elias Tsigoyannis





From DarlingTseng  Thu Aug 28 23:24:45 2003
From: DarlingTseng (Darling Tseng)
Date: Fri, 29 Aug 2003 14:24:45 +0800
Subject: associated station number under HOST AP
Message-ID: <884A96850E80D6119FFF0000E23860B5EDC46D@msg02>

Hello all:

	I want to know how to get the associated station number under HOST
AP.

	Or where I can find some programming guide with using HOST AP ?

	Thanks for your kindly reply at first.

regards,
DT



BenQ. "Bringing Enjoyment 'N Quality to Life". Enjoyment Matters.



From pail_lo  Fri Aug 29 04:02:42 2003
From: pail_lo (=?big5?B?w7kgpOWnZw==?=)
Date: Fri, 29 Aug 2003 11:02:42 +0000
Subject: ROAMing ?
Message-ID: <BAY2-F1652MYkjhib6U00053324@hotmail.com>

Does hostap support ROAMing ?

if yes, how can I enable it ?

_________________________________________________________________
???? MSN Mobile ??????? MSN Messenger ??????  
http://msn.com.tw/msnmobile 




From krose+hostap  Sat Aug 30 10:41:36 2003
From: krose+hostap (Kyle Rose)
Date: Sat, 30 Aug 2003 13:41:36 -0400
Subject: hostap WEP rekeying difficulties, cont'd
Message-ID: <87y8xbcab3.fsf@nausicaa.krose.org>

I got another laptop up and running for the purposes of monitoring the
802.11 frames.  Here's what I found out from ethereal:

(1) With wep_key_len_unicast and wep_key_len_broadcast both commented
out, everything of course works fine, except that no WEP results. :)

(2) With wep_key_len_unicast=13 and wep_key_len_broadcast commented
out, the client negotiates a unicast key properly but never uses it:
even after manually placing an entry in the client's ARP cache for the
AP's MAC, pings to the AP's IP address are not WEP-encrypted, meaning
the hostap driver is not lying that the Orinoco client isn't
encrypting the packets.  (Note: since ARP requests fail for the same
reason, it seems HostAP doesn't accept *any* packets from
authenticated ports that aren't WEP-encrypted, broadcast or not.)

(3) With wep_key_len_unicast=13 and wep_key_len_broadcast=13, the
client and AP exchange probe request/response (request broadcast,
response unicast to the client), but this never ends: the Orinoco card
never associates with the AP.

I did some diffs of a request/response pair for each of the above.
Neglecting differences in frame and sequence numbers, times,
connection stats (e.g., signal strength), the only substantial
differences I found were:

Between (1) and (2): nothing.

Between (1) and (3): the capability bit for whether the AP supports
WEP or not.

It seems to follow from this that the WEP capability bit deals only
with broadcast WEP, AND I started to get the feeling that the Orinoco
card won't ever send an Association Request in response to a Probe
Response with the WEP/AP capability bit set when it doesn't also have
WEP active also.

So, this got me to thinking: what if I put a bogus key on the client,
and THEN start xsupplicant?  The EAP messages and 802.1x frames should
remain unencrypted anyway.

Well, it turns out that nets me *some* progress: the client negotiates
two keys ("EAPOL Key processed: broadcast" and "EAPOL Key processed:
unicast") which both appear in iwlist eth0 enc on the client and in
hostap_crypt_conf -l wlan0 on the AP.  E.g.,

ap$ hostap_crypt_conf -l wlan0
Default keys
  algorithm: WEP
  TX key idx: 2
  key 1:
  key 2: 20 56 42 97 e0 64 f6 17 3f 3f 50 a5 59
  key 3:
  key 4:

Keys for 00:02:2d:0c:83:95
  algorithm: WEP
  TX key idx: 1
  key 1: a7 e4 cd b9 67 2d 58 5e 35 8b dd 61 58
  key 2:
  key 3:
  key 4:

client$ iwlist eth0 enc
eth0      2 key sizes : 40, 104bits
          4 keys available :
                [1]: A7E4-CDB9-672D-585E-358B-DD61-58 (104 bits)
                [2]: 2056-4297-E064-F617-3F3F-50A5-59 (104 bits)
                [3]: off
                [4]: off
          Current Transmit Key: [2]
          Security mode:open

...AND, I could finally talk WEP between these two machines.

Sounds good, eh?  Well, unfortunately, when I switch my monitoring
station to managed mode and activate xsupplicant there, it all falls
apart: neither machine can communicate with the AP now, with the
hostap module claiming

Aug 30 13:24:04 yupa kernel: wlan0: encryption configured, but RX frame not encrypted (SA=00:60:1d:1c:bf:09)
Aug 30 13:24:15 yupa kernel: wlan0: encryption configured, but RX frame not encrypted (SA=00:02:2d:0c:83:95)

for both clients, and continues to fail until I eject/insert the first
client, even if I remove the second client right after starting
xsupplicant on it.  (Although I applied the rekey_patch_orinoco to
only the kernel on the first client, a badly-behaved client should not
be able to cause an entire network to fail; even so, I doubt that is
the problem here.)

So, I'm slowly making progress, but it's very frustrating to be having
these problems when (a) it seems there are lots of people who are
making use of RADIUS/HostAP setups with no problems to speak of, and
(b) no one seems willing to help.  I know some of you have answers;
out with them! :)

Cheers,
Kyle



From jkmaline  Sat Aug 30 18:24:59 2003
From: jkmaline (Jouni Malinen)
Date: Sat, 30 Aug 2003 18:24:59 -0700
Subject: bridge_packets in master mode
In-Reply-To: <901319247.20030830173928@wi-network.net>
References: <49749345.20030829193723@wi-network.net>
	<20030830152141.GA3444@jm.kir.nu>
	<901319247.20030830173928@wi-network.net>
Message-ID: <20030831012458.GA9357@jm.kir.nu>

On Sat, Aug 30, 2003 at 05:39:28PM +0200, WiNet - Biuro handlowe wrote:

> YI do it because I want control traffic between STA's in my LinuxBox,
> by tc in the kernel. Bridge packet in hostap is out of soft control ;-(

The best way of doing this might be to modify Linux bridging code to
understand a bit more about how IEEE 802.11 access points operate and
allow it to bridge broadcast packets back to the same interface in this
case.

> I plan do it by routing table ;-)

And that will not work. I think you can convinse Linux to route unicast
packets back to the same interface and even disable ICMP redirects that
are normally sent in this case. However, IP routing does not route
broadcast frames (like ARP request from STA1 to get STA2's MAC address).
In other words, you would need to modify Linux kernel code for this,
too.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jiri.fojtasek  Sun Aug 31 04:09:13 2003
From: jiri.fojtasek (Jiri Fojtasek)
Date: Sun, 31 Aug 2003 13:09:13 +0200
Subject: bridge_packets in master mode
In-Reply-To: <20030831012458.GA9357@jm.kir.nu>
References: <49749345.20030829193723@wi-network.net>	<20030830152141.GA3444@jm.kir.nu>	<901319247.20030830173928@wi-network.net>
	<20030831012458.GA9357@jm.kir.nu>
Message-ID: <3F51D759.1090600@hlohovec.net>

Jouni Malinen wrote:

>On Sat, Aug 30, 2003 at 05:39:28PM +0200, WiNet - Biuro handlowe wrote:
>
>  
>
>>YI do it because I want control traffic between STA's in my LinuxBox,
>>by tc in the kernel. Bridge packet in hostap is out of soft control ;-(
>>    
>>
>
>The best way of doing this might be to modify Linux bridging code to
>understand a bit more about how IEEE 802.11 access points operate and
>allow it to bridge broadcast packets back to the same interface in this
>case.
>
>  
>
>>I plan do it by routing table ;-)
>>    
>>
>
>And that will not work. I think you can convinse Linux to route unicast
>packets back to the same interface and even disable ICMP redirects that
>are normally sent in this case. However, IP routing does not route
>broadcast frames (like ARP request from STA1 to get STA2's MAC address).
>In other words, you would need to modify Linux kernel code for this,
>too.
>
>  
>
I have done it by this:

1. disabled ICMP redirects
        for f in /proc/sys/net/ipv4/conf/*/accept_redirects; do
        echo 0 > $f
        done
        for f in /proc/sys/net/ipv4/conf/*/send_redirects; do
        echo 0 > $f
        done

2. Every sta uses subnet mask 255.255.255.252

3. Bridge br0 have aliases for every sta gateway eg:
br0:1 192.168.1.1
br0:2 192.168.1.5
br0:3 192.168.1.9
etc ....

4./ sta uses IP's:
192.168.1.2
192.168.1.6
192.168.1.10
etc ...

So, the "brigding" have done the router :), and traffics betwen STA's 
can be classified by tc. For WDS devices i use the same subnet ...

Jiri




From brianc  Sun Aug 31 11:05:50 2003
From: brianc (Brian Capouch)
Date: Sun, 31 Aug 2003 13:05:50 -0500
Subject: Wireless Bridge
Message-ID: <3F5238FE.1000305@palaver.net>

I'm trying to bridge two wired Ethernet segments using HostAP, and I 
have run into a couple of stumbles that I hope someone in the community 
might know how to work around.

The network in question has been set up (by someone else) to use flat IP 
addressing, and traffic is a mixture of IP and IPX.

They are currently using a old, proprietary, slow wireless bridge from 
Speedlan.

There would be no managed stations on the link; the intent is a simple 
point-to-point link in order to bridge the two wired LANS.

Here are the issues:

1. I could not seem to use the WDS-based setup described in the hostap 
README unless I set up both wireless ends in Master mode.  Will the WDS 
technique not work in IBSS ("ad-hoc") mode?

2. Because of the mixture of IP and IPX I am not certain as to the best 
way to secure the link.  Especially after reading the convolutions in 
some of the recent mails about wireless bridging and traffic control, I 
wonder if there is any way to use IPSec to secure a link of this type, 
or whether WEP is going to be my only practical choice.

Thanks in advance for any help that might be out there.

B.




From dave  Sun Aug 31 20:30:54 2003
From: dave (Dave)
Date: Sun, 31 Aug 2003 20:30:54 -0700
Subject: Wireless Bridge
References: <3F5238FE.1000305@palaver.net>
Message-ID: <000501c37039$732a88c0$0307ee3f@ws5>

Hi Brian,

It is actually quite easy to bring up a P2P loop...the following is assuming
one radio per end of loop and one ethernet as well as brctl being present on
each box. Also FW 1.5.x or better is required for wds_type 4.

box #1:
iwconfig wlan0 mode repeater
iwconfig wlan0 channel 11
prism2_param wlan0 max_wds 1
prism2_param wlan0 wds_type 4
iwpriv wlan0 wds_add <mac of box #2 wlan0>
brctl addbr br0
brctl addif br0 wlan0wds0
brctl addif br0 eth0
ifconfig wlan0wds0 up
ifconfig eth0 up
ifconfig br0 up


box #2:
iwconfig wlan0 mode repeater
iwconfig wlan0 channel 11
prism2_param wlan0 max_wds 1
prism2_param wlan0 wds_type 4
iwpriv wlan0 wds_add <mac of box #1 wlan0>
brctl addbr br0
brctl addif br0 wlan0wds0
brctl addif br0 eth0
ifconfig wlan0wds0 up
ifconfig eth0 up
ifconfig br0 up

I may have forgotton a command but that is the majority of it.


-Dave






----- Original Message -----
From: "Brian Capouch" <brianc at palaver.net>
To: <hostap at shmoo.com>
Sent: Sunday, August 31, 2003 11:05 AM
Subject: Wireless Bridge


> I'm trying to bridge two wired Ethernet segments using HostAP, and I
> have run into a couple of stumbles that I hope someone in the community
> might know how to work around.
>
> The network in question has been set up (by someone else) to use flat IP
> addressing, and traffic is a mixture of IP and IPX.
>
> They are currently using a old, proprietary, slow wireless bridge from
> Speedlan.
>
> There would be no managed stations on the link; the intent is a simple
> point-to-point link in order to bridge the two wired LANS.
>
> Here are the issues:
>
> 1. I could not seem to use the WDS-based setup described in the hostap
> README unless I set up both wireless ends in Master mode.  Will the WDS
> technique not work in IBSS ("ad-hoc") mode?
>
> 2. Because of the mixture of IP and IPX I am not certain as to the best
> way to secure the link.  Especially after reading the convolutions in
> some of the recent mails about wireless bridging and traffic control, I
> wonder if there is any way to use IPSec to secure a link of this type,
> or whether WEP is going to be my only practical choice.
>
> Thanks in advance for any help that might be out there.
>
> B.
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From a99-4427  Sat Aug 30 12:16:26 2003
From: a99-4427 (Elias Tsigoyannis)
Date: Sat, 30 Aug 2003 22:16:26 +0300
Subject: card initialization+firmware problems
References: <002301c36f14$34de0360$8551fea9@mage>
Message-ID: <001201c36f2b$35c314c0$8551fea9@mage>

After reading Jun Sun's mini-HOWTO on flashing Intersil Prism chipsets (
http://linux.junsun.net/intersil-prism/ ) I
found out that the latest Primary Firmware for platform 8003 is 0.3.0 and
the latest secondary firmware is 1.5.6.
I was wondering whether somebody could get the latest intersil drivers from

http://intersil.accent-graphics.net/design/prism/ss/crack-n-peel/prod-drvr/I
SL3PRDSUIT-EXE_WIN_(1-7-29).exe
and extract the flash version for the secondary firmware 1.7.1 for platform
8003.  I have seen some instructions
at http://mail.iocaine.com/pipermail/hostap/2002-November/000295.html but I
think that they just extract the ram
version of the firmware ( I want the flashable version). I don't have linux
installed so I am unable to follow these
instructions.

I have found somewhere in the web the file r1010701.hex which I attach in my
e-mail. Can somebody tell me
what this is? I think that this is the ram version of secondary firmware
1.7.1 but can someone test it? (I don't
know to download ram firmwares using windows).

I also found at http://www.netgate.com/support/prism_firmware/1.4.9.zip a
file that describes the differences
between every secondary firmware version for PCI cards from 1.0.0 to 1.4.9.
Does anyone know if the same ones
apply for PCMCIA cards,too? Does anyone have the corresponding files until
secondary version 1.7.4? What are
the differences between the primary and the tertiary versions?

Finally, I would like to say something that has to do with my problem, which
is stated below as well as in another
message in the same thread. I read in the web that setting RID createIBSS
(FC81) to 1 works only on firmwares
after 1.3.6 (I think). I have tried it setting to 0, too (since I am
interested only in ad hoc mode) however I had no
success. The same problems continued appearing. Is there a possibility that
the problem doesn't have to do with the
secondary firmware but with something else? (eg. primary firmware, tertiary
firmware, etc) Can someone help me?

Thanks again,
Elias Tsigoyannis

----- Original Message -----
From: "Elias Tsigoyannis" <a99-4427 at students.ee.upatras.gr>
To: <hostap at shmoo.com>
Sent: Saturday, August 30, 2003 7:31 PM
Subject: card initialization+firmware problems


> Hello to everybody!
>
> Can somebody explain to me the initialization process of a prism2 card?
> I use the winupdate programme to upgrade the firmware of my card and it
> says:
>
> Platform:    8003
> Primary Firmware:    0.3.0
> Station (Secondary) Firmware: 0.6.2
>
> At first, I would like to ask if there is a primary firmware that is newer
> than 0.3.0 for my card. I have seen
> primary firmwares with number 1.1.0, but they are for different platforms
> (800a,etc). Is there such a firmware
> for my card? I have also found secondary firmware 1.5.6 that can be
flashed
> to my card. Does anyone have station firmware
> 1.7.x for platform 8003?
>
> Anyway, I want to use this card in ad hoc mode. At first, I was using
> firmware 0.6.2. I issued the "initialize command" without
> any problems, however I noticed that when I put the value 0 to RID
PortType
> (0xFC00) as Intersil Prism
> Driver's Manual says, even though I got a link status message that said
> "Connected", immediately after I issued the "enable command" (for channel
> 0),
> the RID PortStatus (0xFD40) had the value 6 (Connected to WDS). I read
> Intersil's FAQs and found out
> that the old manual said that old firmwares should use value 4 for RID
> PortType. I tried that and the result was
> that I didn't get a Link Status message, after the "enable command", but
> PortStatus had the value 3 (Connected to IBSS). The problem either way
> is that I can neither send any frames nor is my IBSS detected by any
network
> analyzers that I've used (I have 2 pcs. In one
> of them I run the wireless network analyzer and at the second one I create
> the IBSS. Both of them have Intersil Prism HWB3163-EVAL
> wireless cards).
>
> Anyway, I tried upgrading the firmware to 1.4.9 and 1.5.6 and now I face a
> different problem. Although I can't put value 4 to
> PortType (because PortStatus gets a value not specified by Intersil's
> manual), if I put value 0 to PortType, then PortStatus gets
> the value 2 (Searching for initial connection) and remains there. Since I
> always put value 1 to RID createIBSS (FC81) that means
> that the card should either search for an ESS/IBSS or create an IBSS,
after
> a while the RID PortStatus should change to 3
> (Connected to IBSS). However it doesn't.
>
> Does anyone know any firmware that operates according to Intersil's Driver
> Programmer's manual?
> I want the following events to occur:
>
> 1)I issue the initialize command
> 2)I set RID PortType to 0 (or 4...however please tell me which one I
should
> use)
> 3)I set RID createIBSS to 1 (join ESS or create/join IBSS)
> 4)I configure DesiredSSID,OwnSSID,OwnName,Channel
> 5)I issue the enable command for channel 0
> 6)I get a link status interrupt that says that I am connected and the
> PortStatus RID has the value 3 (Connected to IBSS)
>
> If I have understood something wrong and that's not the correct
> initialization sequence please inform me..
>
> Thanks in advance,
> Elias Tsigoyannis
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: r1010701.hex
Type: application/octet-stream
Size: 163277 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20030830/1156b312/attachment.obj 


