<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
<BR>Thanks Bruce,<BR>
Can you tell me which version of madwifi, hostap, and wpa_supplicant you are using?<BR>
<BR>
Thanks,<BR>
Joe<BR><BR>
<BLOCKQUOTE>
<HR>
Subject: RE: hostAP and wds with madwifi<BR>Date: Mon, 24 Sep 2007 10:03:25 -0700<BR>From: bsmith@road-inc.com<BR>To: microcool@hotmail.com; hostap@shmoo.com<BR><BR>
<META content="Microsoft SafeHTML" name=Generator>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass EC_body.hmmessage
{font-size:10pt;font-family:Tahoma;}
</STYLE>
<DIV id=EC_idOWAReplyText50167 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>I've used it in this mode although I am having an issue with moving data.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial>I first run wpa_supplicant on the sta intf and wait for association, then run hostapd on the other interface. I then can see it from a second wifi card and can associate. There was an issue with it not sending beacons but I don't remember the exact configuration but anytime I use this sequence it works fine. </FONT></DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial>So the order of my bringup:</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>wlanconfig ath create wlandev wifi0 wlanmode ap</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>creates ath0</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>wlanconfig ath create wlandev wifi0 wlanmode sta nosbeacon</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>creates ath1</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>iwpriv ath0 wds 1</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>iwpriv ath1 wds 1</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>ifconfig ath0 up</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>ifconfig ath1 up</FONT></DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial>brctl addbr br0</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>brctl addif br0 ath0</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>brctl addif br0 ath1</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>brctl setfd br0 1</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>ifconfig br0 192.168.3.20</FONT></DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial>wpa_supplicant -Dmadwifi -iath1 -c /etc/wpa.conf</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>wait for association</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>hostapd /etc/hostapd.conf</FONT></DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>I used a 2 wifi card at eth0 and ran wpa_supplicant on it to attach to the new AP defined in /etc/hostapd.conf. You might try leaving ath0 down until wpa_supplicant is done then bring up ath0 and hostapd. </DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial>I've also found the madwifi driver to be unstable, causing my machines to freeze. Only in wds mode, otherwise the driver seems sound.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial>Cheers,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>Bruce</FONT></DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV></DIV>
<DIV dir=ltr><FONT face=Arial></FONT><BR>
<HR>
<FONT face=Tahoma size=2><B>From:</B> hostap-bounces+bsmith=road-inc.com@shmoo.com on behalf of Micro Cool<BR><B>Sent:</B> Mon 9/24/2007 7:21 AM<BR><B>To:</B> hostap@shmoo.com<BR><B>Subject:</B> hostAP and wds with madwifi<BR></FONT><BR></DIV>
<DIV>I am trying to get wpa_supplicant and hostapd to work for wds with the madwifi driver but I have not been having much luck. I am aware that generally wds is not supported for 11i key managment method but since madwifi sets their wds links up as a station and a AP I thought it might be possible if you run hostAP on the AP interface and wpa_supplicant on the station interface. However when I tried this for some reason whenever I bring the AP interface up with hostAP it never beacons. Thought this was odd so I tried bringing the AP interface up first and then bring the station interface up and indeed the AP did beacon but as soon as the station linked it stopped.<BR> <BR>Does anyone have any thoughts why this is happening?<BR> <BR> <BR>Thanks,<BR>Joe<BR><BR>
<HR>
Can you find the hidden words? Take a break and play Seekadoo! <A href="http://club.live.com/seekadoo.aspx?icid=seek_wlmailtextlink" target=_blank>Play now!</A></DIV></BLOCKQUOTE><br /><hr />Can you find the hidden words? Take a break and play Seekadoo! <a href='http://club.live.com/seekadoo.aspx?icid=seek_wlmailtextlink' target='_new'>Play now!</a></body>
</html>