WDS link establishment

M Tamer Refaei mohamed.refaei at us.fujitsu.com
Sat Jun 4 20:11:25 EDT 2005


Should there be any?  I mean does the 802.11 standard specify any sequence
of packet exchange prior to establishing a WDS link?

> Send HostAP mailing list submissions to
> 	hostap at shmoo.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.shmoo.com/mailman/listinfo/hostap
> or, via email, send a message with subject or body 'help' to
> 	hostap-request at shmoo.com
>
> You can reach the person managing the list at
> 	hostap-owner at shmoo.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of HostAP digest..."
>
>
> Today's Topics:
>
>    1. WDS link establishment (Mohamed Tamer Refaei)
>    2. Re: hard to found a wireless card!!! (Jouni Malinen)
>    3. Re: authentication failure. what means EAP "packets were not
>       identical"? (Jouni Malinen)
>    4. Re: AR5112 card working with madwifi-bsd, hostapd-0.4.1,
>       wpa_supplicant-0.4.1(and openssl-0.9.7g) (Jouni Malinen)
>    5. Re: WDS link establishment (Jouni Malinen)
>    6. Re: Trying again.Please help ! wpa_supplicant problem with
>       eap-ttls (Jouni Malinen)
>    7. Re: Problems with hostap-driver, wpa_supplicant and WPA-PSK
>       (Jouni Malinen)
>    8. Re: Release candidate for the next stable release (0.3.9-rc1)
>       (Jouni Malinen)
>    9. Re: IPW2195 A/B/G (ipw2200 1.0.4 + wpa_supplicant 0.4.1)
>       Hidden essid	problem (Jouni Malinen)
>   10. Re: IPW2100 will not connect to Linksys router (Jouni Malinen)
>   11. Re: help! wpa_supplicant with WEP never associates, just
>       timeout-loops (Jouni Malinen)
>   12. crashing! (Andrew Duane)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 3 Jun 2005 17:02:41 -0400
> From: "Mohamed Tamer Refaei" <mohamed.refaei at us.fujitsu.com>
> Subject: WDS link establishment
> To: <hostap at shmoo.com>
> Message-ID: <018501c5687f$9583b820$2e04a8c0 at flacp>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi all
>
> are there any packets exchanged between two ends of a WDS link before the
> link is established?
>
> thanks
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.shmoo.com/pipermail/hostap/attachments/20050603/4d429cd9/attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Fri, 3 Jun 2005 18:09:18 -0700
> From: Jouni Malinen <jkmaline at cc.hut.fi>
> Subject: Re: hard to found a wireless card!!!
> To: hostap at shmoo.com
> Message-ID: <20050604010918.GT15669 at jm.kir.nu>
> Content-Type: text/plain; charset=us-ascii
>
> On Sat, Jun 04, 2005 at 01:26:14AM +0800, GoldWater wrote:
>
>> Many days ago, I want to find a wired and EAP/TLS solution with
>> HostAP, I failed! because wpa_supplicant_winddows does not support
>> wired network adapters.
>
> But like I mentioned, it would be possible to build a version with
> driver_wired included..
>
>> Few days ago, I change to focus on wireless card first, I bought a
>> pair of 3Com 3CRWE777A, my god! under my misunderstand, I fail again,
>> 3CRWE777A does not support WPA, which mean that I still can not using
>> wpa_supplicant_winddows.
>>
>> Today, I want to buy a set of new "suitable" wireless card again, I go
>> through many pages, in
>> http://www.linux-wlan.org/docs/wlan_adapters.html.gz, I found a list
>> of many cards and include chipset, but I think it is outdate. on the
>> other hand, I visited many brand's web site, I can not found any
>> information about the chipset of the card.
>
> If you are looking for a wireless card for Windows, I don't see much
> point in trying to find a Prism2/2.5/3 card unless you are going to use
> that card on Linux, too. As far as wpa_supplicant for Windows is
> concerned, it does not matter which card you are using as long as you
> have a working driver for it with WPA support.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 3 Jun 2005 18:15:21 -0700
> From: Jouni Malinen <jkmaline at cc.hut.fi>
> Subject: Re: authentication failure. what means EAP "packets were not
> 	identical"?
> To: hostap at shmoo.com
> Message-ID: <20050604011521.GU15669 at jm.kir.nu>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Jun 03, 2005 at 08:46:07PM +0200, Tilman Schoop wrote:
>
>> I have the problem that a client (wpa_supplicant 0.3.8, ndiswrapper)
>> does not authenticate with an Cisco AP (secured with LEAP+TKIP).
>> It tries ever and ever again with no result.
>
> Please send full wpa_supplicant debug log if you want me to take a
> closer look at this.
>
>> I tried to analyse the wpa_supplicant's logs and have found the
>> following sequence after the username/password for LEAP are sent and
>> the answer is expected:
>>
>> EAP: EAP entering state RECEIVED
>> EAP: Received EAP-Failure
>
> Authentication server denied authentication for some reason. This debug
> log excerpt does not include enough information to say why that
> happened.
>
>> EAP: AS used the same Id again, but EAP packets were not identical
>> EAP: workaround - assume this is not a duplicate packet
>
> These are from a EAP workaround that some authentication servers
> require. In this case, this can safely be ignored.
>
>> EAP: EAP entering state FAILURE
>> EAPOL: SUPP_PAE entering state HELD
>
> This is from processing of the failed EAP authenticationa.
>
>> or is this just a warning that can be ignored and the real cause is a
>> negative authentication response?
>
> Yes.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 3 Jun 2005 18:21:33 -0700
> From: Jouni Malinen <jkmaline at cc.hut.fi>
> Subject: Re: AR5112 card working with madwifi-bsd, hostapd-0.4.1,
> 	wpa_supplicant-0.4.1(and openssl-0.9.7g)
> To: hostap at shmoo.com
> Message-ID: <20050604012133.GW15669 at jm.kir.nu>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Jun 03, 2005 at 01:28:14PM +0800, Victor Yeo wrote:
>
>> Now when i run hostapd, i get "l2_packet_receive -
>> recv: Network is down" error
>
> I haven't went through the code to find what is generating this, but I
> believe this can be safely ignored.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 3 Jun 2005 18:27:26 -0700
> From: Jouni Malinen <jkmaline at cc.hut.fi>
> Subject: Re: WDS link establishment
> To: hostap at shmoo.com
> Message-ID: <20050604012726.GX15669 at jm.kir.nu>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Jun 03, 2005 at 05:02:41PM -0400, Mohamed Tamer Refaei wrote:
>
>> are there any packets exchanged between two ends of a WDS link before
>> the link is established?
>
> No, at least with the current Host AP driver.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 3 Jun 2005 18:41:15 -0700
> From: Jouni Malinen <jkmaline at cc.hut.fi>
> Subject: Re: Trying again.Please help ! wpa_supplicant problem with
> 	eap-ttls
> To: hostap at shmoo.com
> Message-ID: <20050604014115.GY15669 at jm.kir.nu>
> Content-Type: text/plain; charset=us-ascii
>
> On Thu, Jun 02, 2005 at 05:36:46PM +0200, helas Akropolis wrote:
>
>> wpa-psk work fine, but when i try to use eap-ttls there ist no
>> connection between the wpa_supplicant(wxp sp2) and the
>> hostap. can anyone please tell me what i am doing wrong?
>
> Unfortunately, you did not include enough debug output from the RADIUS
> server to find out what was happening. wpa_supplicant debug log seems to
> indicate that the RADIUS server is doing something odd, i.e., it is
> trying to change from EAP-TTLS to EAP-TLS within the same authentication
> session.
>
>> The wpa_supplicant say everytime i get connected: SSL: SSL_connect:error
>> in SSLv3 read server hello A
>
> That is expected in the beginning of the TLS handshake when server hello
> has not yet been received.
>
>> EAP: Received EAP-Request method=1 id=0
>> EAP: Received EAP-Request method=1 id=1
>
> First, RADIUS server is sending EAP-Request/Identity. This is correct.
>
>> EAP: Received EAP-Request method=21 id=2
>
> And the server starts EAP-TTLS.
>
>> TX EAPOL - hexdump(len=124): 00 09 5b 12 0f a5 00 09 5b 98 e2 7e 88 8e
>> 01 00 00
>> 6a 02 02 00 6a 15 00 16 03 01 00 5f 01 00 00 5b 03 01 42 9d b7 1a 5b 92
>> ad 3b 7b
>> 6c 93 95 b9 65 c5 e4 06 af 62 c8 c2 7f 32 6d 24 8f 99 2d 1a 00 59 bf 00
>> 00 34 0
>> 0 39 00 38 00 35 00 16 00 13 00 0a 00 33 00 32 00 2f 00 66 00 05 00 04
>> 00 63 00
>> 62 00 61 00 15 00 12 00 09 00 65 00 64 00 60 00 14 00 11 00 08 00 06 00
>> 03 01 00
>
> wpa_supplicant replies with EAP-TTLS..
>
>> WPA: EAPOL frame too short, len 10, expecting at least 99
>> RX EAPOL from 00:09:5b:12:0f:a5
>> RX EAPOL - hexdump(len=10): 02 00 00 06 01 03 00 06 0d 20
>> EAP: Received EAP-Request method=13 id=3
>> EAP: EAP entering state DISCARD
>
> But the authentication server is sending EAP-TLS/Start?! This is
> incorrect behavior.
>
> Please send a more complete debug log from the RADIUS server. In
> addition, getting a packet capture from the RADIUS server (i.e.,
> something showing the RADIUS packets between the server and AP) could be
> helpful.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 3 Jun 2005 18:43:14 -0700
> From: Jouni Malinen <jkmaline at cc.hut.fi>
> Subject: Re: Problems with hostap-driver, wpa_supplicant and WPA-PSK
> To: hostap at shmoo.com
> Message-ID: <20050604014314.GZ15669 at jm.kir.nu>
> Content-Type: text/plain; charset=us-ascii
>
> On Thu, Jun 02, 2005 at 07:39:07AM +0200, Urs Thuermann wrote:
>
>> So, my next question is:  Is there a way to update the firmware under
>> linux?  The system is an embedded PC104 board and I'd rather not
>> disassemble it completely to pull the Prism2 card and insert it into
>> some Windows box.
>
> Yes, Host AP driver support firmware upgrade (both to RAM and flash)
> with prism2_srec tool.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>
>
> ------------------------------
>
> Message: 8
> Date: Fri, 3 Jun 2005 18:49:19 -0700
> From: Jouni Malinen <jkmaline at cc.hut.fi>
> Subject: Re: Release candidate for the next stable release (0.3.9-rc1)
> To: hostap at shmoo.com
> Cc: romano at dea.icai.upco.es
> Message-ID: <20050604014919.GA15669 at jm.kir.nu>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Jun 03, 2005 at 02:48:30PM +0200, Romano Giannetti wrote:
>
>> I tested here wpa_supplicant 0.3.9-rc2 (801.1x with cisco servers,
>> PEAP/MSCHAP2, ndiswrapper driver) without any noticeable regression.
>
> Thanks for testing this! I would have release 0.3.9 already had it not
> been for the Intel driver ioctl mess.. I hoped to see a new version of
> ipw2100 driver released, but that has not happened yet, so maybe it is
> just time to ignore this and release wpa_supplicant anyway.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>
>
> ------------------------------
>
> Message: 9
> Date: Fri, 3 Jun 2005 18:54:15 -0700
> From: Jouni Malinen <jkmaline at cc.hut.fi>
> Subject: Re: IPW2195 A/B/G (ipw2200 1.0.4 + wpa_supplicant 0.4.1)
> 	Hidden essid	problem
> To: hostap at shmoo.com
> Message-ID: <20050604015415.GB15669 at jm.kir.nu>
> Content-Type: text/plain; charset=iso-8859-1
>
> On Thu, Jun 02, 2005 at 12:44:25PM +0200, Samuel D?az Garc?a wrote:
>
>> Ipw2200: 1.0.4 + geography patch
>> wpa_supplicant: 0.4.1
>> madwifi: current cvs snapshot
>
>> The problem now is that i can't associate to a WPA-PSK (TKIP+AES) hidden
>> essid AP.
>>
>> The same wpa_supplicant config file works fine with madwifi driver.
>>
>> Is another bug or patch that we need to know?
>
> No, it is a feature, or well, a missing feature. ipw2200 driver/firmware
> does not support per-SSID scanning. So if you want to associate with an
> AP that is using a hidden SSID, you will need to use ap_scan=2 mode.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>
>
> ------------------------------
>
> Message: 10
> Date: Fri, 3 Jun 2005 19:00:30 -0700
> From: Jouni Malinen <jkmaline at cc.hut.fi>
> Subject: Re: IPW2100 will not connect to Linksys router
> To: hostap at shmoo.com
> Message-ID: <20050604020030.GC15669 at jm.kir.nu>
> Content-Type: text/plain; charset=us-ascii
>
> On Tue, May 31, 2005 at 09:09:48PM -0800, Joshua J. Kugler wrote:
>
>> NIC: Intel PRO/Wireless LAN 2100 (And latest firmware from
>> ipw2100.sf.net)
>> AP: Linksys BEFW11S4 (802.11b)
>
>> I have set up WPA on the AP, and it will connect fine from a Windows XP
>> box. When I try to connect from this Linux laptop, I get this:
>>
>> [root at cdesysadminlaptop joshua]# wpa_supplicant -ieth1
>> -c/etc/wpa_supplicant.conf -Dipw
>> Trying to associate with 00:12:17:3c:9c:73 (SSID='hillwireless' freq=0
>> MHz)
>> Associated with 00:12:17:3c:9c:73
>> WPA: Key negotiation completed with 00:12:17:3c:9c:73 [PTK=TKIP
>> GTK=TKIP]
>> WPA: Group rekeying completed with 00:12:17:3c:9c:73 [GTK=TKIP]
>> Disconnect event - remove keys
>
> Based on the debug log, it looks like the WPA 4-Way handshake is
> completed successfully and the client is able to receive message 1/2 of
> the Group Key handshake. However, for some reason the AP does not either
> receive or accept message 2/2. If you can get any event/debug
> information from the AP, it could be helpful in finding out what is
> happening.
>
>> So, there you go...if you need more logs, let me know.  What I don't
>> understand is why my AP get's "blacklisted."  What is it doing wrong?
>
> The AP disconnected the client and wpa_supplicant uses a blacklist to
> go through all available APs (if there's more than one) before trying
> again with the one that rejected the authentication.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>
>
> ------------------------------
>
> Message: 11
> Date: Fri, 3 Jun 2005 20:36:33 -0700
> From: Jouni Malinen <jkmaline at cc.hut.fi>
> Subject: Re: help! wpa_supplicant with WEP never associates, just
> 	timeout-loops
> To: hostap at shmoo.com
> Message-ID: <20050604033633.GD15669 at jm.kir.nu>
> Content-Type: text/plain; charset=us-ascii
>
> On Mon, May 30, 2005 at 05:08:35PM -0400, David P. Reed wrote:
>
>> I have a fairly vanilla system: FC3, madwifi running pretty standard on
>> a Compaq Evo N610c.   ath0 associates just fine without wpa_supplicant
>> with an access point using WEP shared keys and ifup, specifying the
>> proper key.
>>
>> I cannot get wpa_supplicant to associate, however.    It finds the
>> access point and tries to associate, but times out and loops retrying.
>
> I'm not completely sure what madwifi driver expects here, but it looked
> like the the driver did not configure something correctly when WEP key
> was set with the private ioctl.. I think this worked before, but at
> least it did not work now with my madwifi-bsd build.
>
> I changed wpa_supplicant to use standard Linux wireless extensions when
> driver_madwifi is configuring WEP keys. This seemed to allow me to
> associate with an AP both with open system and shared key authentication
> algorithms and WEP. Could you please test the current CVS snapshot
> (development branch) from http://hostap.epitest.fi/ and let me know
> whether it fixes the association in your test case?
>
>> wpa_supplicant, and this is just frustrating.  I really want to shift my
>> setup to wpa rather than WEP, but this doesn't give me much confidence
>> that wpa_supplicant will work for me.
>
> Please keep in mind that WPA gets much more attention among developers
> and is actually more likely to work than WEP or plaintext..
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>
>
> ------------------------------
>
> Message: 12
> Date: Sat, 4 Jun 2005 11:34:26 +0100
> From: "Andrew Duane" <andrew at duaneville.com>
> Subject: crashing!
> To: <hostap at shmoo.com>
> Message-ID: <000101c568f0$fb6028b0$0b01a8c0 at terminus>
> Content-Type: text/plain; charset="windows-1250"
>
> Hi,
>
>
>
> I have used ndiswrapper and wpa_supplicant for months on FC3 with
> success, but recently I had a HDD failure and had to reinstall. Now im
> getting lockups when I try to get wpa_supplicant running.
>
>
>
> I have a linksys wmp54g wireless card and have installed ndiswrapper
> v1.1 with the latest linksys drivers. This part of the process seemed to
> go okay.
>
>
>
> Now I have tried installing both wpa_supplicant 0.4.1 and 0.3.8 tna.
> Here is the config I use:
>
>
>
> .config file:
>
>
>
> CONFIG_WIRELESS_EXTENSION=y
>
> CONFIG_DRIVER_NDISWRAPPER=y
>
>
>
> Wpa_supplicant.conf:
>
>
>
> # allow frontend (e.g., wpa_cli) to be used by all users in 'wheel'
> group
>
> #ctrl_interface=/var/run/wpa_supplicant
>
> #ctrl_interface_group=users
>
> #
>
> # home network; allow all valid ciphers
>
> network={
>
>         ssid="myssid"
>
>         key_mgmt=WPA-PSK
>
>         psk="mypass"
>
> }
>
>
>
> Had to comment out the ctrl_interface stuff cause I got an error about
> reading the file?? Think I need to add another entry in .config to get
> this working. It used to work though??
>
>
>
> Anyway if I run wpa_supplicant with wlan0 interface up or down ? it
> crashes my pc (I?m using Fedora Core 4 Test 3)
>
>
>
> Here is the output any help would be great!
>
>
>
> [root at trantor wpa_supplicant-0.4.1]# wpa_supplicant -iwlan0
> -c/etc/wpa_supplicant.conf -d
>
> Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver
> 'default'
>
> Configuration file '/etc/wpa_supplicant.conf' ->
> '/etc/wpa_supplicant.conf'
>
> Reading configuration file '/etc/wpa_supplicant.conf'
>
> Priority group 0
>
>    id=0 ssid='Foundation'
>
> Initializing interface (2) 'wlan0'
>
> ioctl[SIOCSIWPMKSA]: No such device
>
> Own MAC address: 00:0c:41:61:d6:4f
>
> Setting scan request: 0 sec 100000 usec
>
> Wireless event: cmd=0x8b06 len=8
>
> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
>
> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
>
> State: DISCONNECTED -> SCANNING
>
> Starting AP scan (broadcast SSID)
>
> Scan timeout - try to get results
>
> Received 310 bytes of scan results (1 BSSes)
>
> Scan results: 1
>
> Selecting BSS from priority group 0
>
> 0: 00:0c:41:9d:f4:4a ssid='Foundation' wpa_ie_len=24 rsn_ie_len=0
> caps=0x11
>
>    selected
>
> Trying to associate with 00:0c:41:9d:f4:4a (SSID='Foundation' freq=2452
> MHz)
>
> Cancelling scan request
>
> Automatic auth_alg selection: 0x1
>
> WPA: using IEEE 802.11i/D3.0
>
> WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
>
> WPA: using GTK TKIP
>
> WPA: using PTK TKIP
>
> WPA: using KEY_MGMT WPA-PSK
>
> WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
> 01 00 00 50 f2 02 01 00 00 50 f2 02
>
> No keys have been configured - skip key clearing
>
> State: SCANNING -> ASSOCIATING
>
> Setting authentication timeout: 5 sec 0 usec
>
> Wireless event: cmd=0x8c02 len=205
>
> Custom wireless event:
> 'ASSOCINFO(ReqIEs=000a466f756e646174696f6e010882848b9624b0486c32048c1298
> 60dd050010180100dd160050f20101000050f20201000050f20201000050f202
> RespIEs=010882848b9624b0486c32048c129860dd06001018010100)'
>
> Association info event
>
> req_ies - hexdump(len=59): 00 0a 46 6f 75 6e 64 61 74 69 6f 6e 01 08 82
> 84 8b 96 24 b0 48 6c 32 04 8c 12 98 60 dd 05 00 10 18 01 00 dd 16 00 50
> f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
>
> resp_ies - hexdump(len=24): 01 08 82 84 8b 96 24 b0 48 6c 32 04 8c 12 98
> 60 dd 06 00 10 18 01 01 00
>
> assoc_wpa_ie - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01
> 00 00 50 f2 02 01 00 00 50 f2 02
>
> Wireless event: cmd=0x8b15 len=20
>
> Wireless event: new AP: 00:0c:41:9d:f4:4a
>
> State: ASSOCIATING -> ASSOCIATED
>
> Association event - clear replay counter
>
> Associated to a new BSS: BSSID=00:0c:41:9d:f4:4a
>
> No keys have been configured - skip key clearing
>
> Associated with 00:0c:41:9d:f4:4a
>
> Setting authentication timeout: 10 sec 0 usec
>
> RX EAPOL from 00:0c:41:9d:f4:4a
>
> Setting authentication timeout: 10 sec 0 usec
>
> IEEE 802.1X RX: version=1 type=3 length=95
>
>   EAPOL-Key type=254
>
> State: ASSOCIATED -> 4WAY_HANDSHAKE
>
> WPA: RX message 1 of 4-Way Handshake from 00:0c:41:9d:f4:4a (ver=1)
>
> WPA: Renewed SNonce - hexdump(len=32): 04 5f e4 6c 16 93 a4 1f b8 a6 65
> 2a 94 33 e8 1a 6c b8 fe d4 de c3 ac bd 6b 31 35 33 30 80 2d a0
>
> WPA: PMK - hexdump(len=32): [REMOVED]
>
> WPA: PTK - hexdump(len=64): [REMOVED]
>
> WPA: Sending EAPOL-Key 2/4
>
>
>
>
>
>
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.6.1 - Release Date: 03/06/2005
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.shmoo.com/pipermail/hostap/attachments/20050604/a5387721/attachment.htm
>
> ------------------------------
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
>
> End of HostAP Digest, Vol 26, Issue 9
> *************************************
>




-------------------------
Mohamed Tamer Refaei



More information about the HostAP mailing list