Re: Issue with Configuring madwifi/Atheros in AP mode on DWL-AG530
Vivek Ramamoorthy <[email protected]> Fri, 30 Sep 2011 00:00:13 -0700
| Newsgroups | gmane.linux.drivers.madwifi.user |
|---|---|
| Message-ID | <CAEC20oAmX5hTPOg_D+6Ai-tofLvKiaOMk7TH3tDvC9qHfroOww@mail.gmail.com> |
--===============3790640666312894575== Content-Type: multipart/alternative; boundary=00151747c09a3f904b04ae232d64 --00151747c09a3f904b04ae232d64 Content-Type: text/plain; charset=ISO-8859-1 Hi Pavel, Firewall was off. So that doesnt seem to be the issue.. Do you think, I should try an earlier version of madwifi in combination with an older kernel? Thanks Vivek On Tue, Sep 27, 2011 at 3:47 PM, Vivek Ramamoorthy <[email protected]>wrote: > Hi Pavel, > > thanks for the inputs let me try checking the firewall settings. > The madwifi version I am using is svn r4165 (branch madwifi-0.9.4) > > Attaching the dmesg, which I had missed out in earlier email. > > Thanks > Vivek > > > On Tue, Sep 27, 2011 at 1:11 PM, Pavel Roskin <[email protected]> wrote: > >> On Tue, 27 Sep 2011 11:34:53 -0700 >> Vivek Ramamoorthy <[email protected]> wrote: >> >> > Hi All, >> > >> > I have been trying to use a DLINK DWL-AG530 PCI card along with >> > Madwifi to configure the chip in AP mode. Although the client >> > associates fine, I am unable to ping ath0 interface. >> > I have statically assigned IP to client since I dont have a DHCP >> > server running. >> > >> > So here are the steps I have followed till now: >> > >> > 1) Downloaded source from http://madwifi-project.org/ and installed >> > the same on my linux machine. Here are details of my linux version: >> > >> > [root@localhost ~]# uname -a >> > Linux localhost.localdomain 2.6.27.25-78.2.56.fc9.i686 #1 SMP Thu Jun >> > 18 12:47:50 EDT 2009 i686 i686 i386 GNU/Linux >> >> You forgot the version of madwifi. It it's a snapshot, please specify >> whether it's the trunk of the 0.9.4 branch, and what is the date or the >> revision of the snapshot. >> >> > 3) In /etc/modprobe.d/madwifi >> > >> > alias wlan0 ath_pci >> > blacklist ath5k >> > options ath_pci autocreate=ap >> > >> > 4) Since I read in forums that DWL-AG530 comes with a broken country >> > code, I changed the regdomain to 0x0 (also tried with 0x16) >> > 5) modprobe ath_pci countrycode=840 >> > 6) wlanconfig ath0 destroy >> > 7) wlanconfig ath0 create wlandev wifi0 wlanmode ap >> >> You can use the "autocreate=ap" parameter to avoid the need to recreate >> ath0. >> >> > 8) iwpriv ath0 authmode 1 (open mode) >> >> I don't think you need to tweak private parameters for basic >> functionality. >> >> > 9) iwconfig ath0 essid "test_wlan" >> > 10) ifconfig ath0 10.1.1.10 netmask 255.255.255.0 >> > 11) ifconfig ath0 up >> > >> > *An issue I see, is that everytime I try to set the channel using >> > iwconfig ath0 channel 6 (or whatever) the kernel panics and the >> > system goes to hang state, so I leave it at default* >> >> I guess if might be the issue that prevents the release of the >> version 0.9.4.1: >> https://madwifi-project.org/ticket/1903 >> >> The workaround it to set the channel while the interface is down. >> >> > I have a windows 7 client, on which i configure a static IP of >> > 10.1.1.12 and connect to wlan "test_wlan". The client associates, and >> > also I was able to sniff the assoc rsp, and ack packets from the air >> > which had a "Success" status. >> > >> > However, when I ping 10.1.1.10 (ath0), no response. I get a Dest >> > Unreachable from 10.1.1.12. So I added arp entry for 10.1.1.10 >> > manually on my client. When I do that the ICMP request times out, and >> > I do see the ICMP requests in the air. >> > >> > I have been trying to figure out if the driver is dropping these >> > packets due to some configuration thats wrong? Do let me know if >> > anyone has faced similar issues. >> >> I suggest that you check firewall settings on Fedora (iptables). Try >> turning it off. >> >> > i have tried using bridges between ath0 and eth0 interface, Even that >> > hasnt worked. >> > >> > Attaching the outputs of ifconfig, iwconfig and dmesg (No errors i >> > saw in dmesg) along. >> > >> > Also, if anyone has used any of the currently available atheros >> > chipsets along with Madwifi successfully to set up an AP (Master >> > mode), would be great if you could provide me the Chipsets model >> > number, and Madwifi version.. I am fine with any Atheros based >> > Chipset that is available in the market, as long as I can use it with >> > madwifi to setup in AP mode. Just wondering if the DWL-AG530 may be >> > having issues in AP mode, since it works just fine as a wireless >> > client. >> >> As far as I know, the only chipsets that are supported by MadWifi but >> don't work in AP mode are AR5210 and possibly AR5211. Both are very >> old and don't even support 802.11g. >> >> -- >> Regards, >> Pavel Roskin >> > > --00151747c09a3f904b04ae232d64 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Pavel,<div><br></div><div>Firewall was off. So that doesnt seem to be th= e issue..</div><div>Do you think, I should try an earlier version of madwif= i in combination with an older kernel?=A0</div><div><br></div><div>Thanks</= div> <div>Vivek</div><div><br></div><div><br><div class=3D"gmail_quote">On Tue, = Sep 27, 2011 at 3:47 PM, Vivek Ramamoorthy <span dir=3D"ltr"><<a href=3D= "mailto:[email protected]">[email protected]</a>></span> wrote:<= br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex;">Hi Pavel,<div><br></div><div>thanks for the= inputs let me try checking the firewall settings.</div><div>The madwifi ve= rsion I am using is=A0svn r4165 (branch madwifi-0.9.4)</div> <div><br></div><div>Attaching the dmesg, which I had missed out in earlier = email.</div> <div><br></div><div>Thanks</div><div>Vivek</div><div><div></div><div class= =3D"h5"><div><br></div><div><br><div class=3D"gmail_quote">On Tue, Sep 27, = 2011 at 1:11 PM, Pavel Roskin <span dir=3D"ltr"><<a href=3D"mailto:prosk= [email protected]" target=3D"_blank">[email protected]</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><div>On Tue, 27 Sep 2011 11:34:53 -0700<br> Vivek Ramamoorthy <<a href=3D"mailto:[email protected]" target=3D"_b= lank">[email protected]</a>> wrote:<br> <br> > Hi All,<br> ><br> > I have been trying to use a DLINK DWL-AG530 PCI card along with<br> > Madwifi to configure the chip in AP mode. Although the client<br> > associates fine, I am unable to ping ath0 interface.<br> > I have statically assigned IP to client since I dont have a DHCP<br> > server running.<br> ><br> > So here are the steps I have followed till now:<br> ><br> > 1) Downloaded source from <a href=3D"http://madwifi-project.org/" targ= et=3D"_blank">http://madwifi-project.org/</a> and installed<br> > the same on my linux machine. Here are details of my linux version:<br= > ><br> > [root@localhost ~]# uname -a<br> > Linux localhost.localdomain 2.6.27.25-78.2.56.fc9.i686 #1 SMP Thu Jun<= br> > 18 12:47:50 EDT 2009 i686 i686 i386 GNU/Linux<br> <br> </div>You forgot the version of madwifi. =A0It it's a snapshot, please = specify<br> whether it's the trunk of the 0.9.4 branch, and what is the date or the= <br> revision of the snapshot.<br> <div><br> > 3) In /etc/modprobe.d/madwifi<br> ><br> > alias wlan0 ath_pci<br> > blacklist ath5k<br> > options ath_pci autocreate=3Dap<br> ><br> > 4) Since I read in forums that DWL-AG530 comes with a broken country<b= r> > code, I changed the regdomain to 0x0 (also tried with 0x16)<br> > 5) modprobe ath_pci countrycode=3D840<br> > 6) wlanconfig ath0 destroy<br> > 7) wlanconfig ath0 create wlandev wifi0 wlanmode ap<br> <br> </div>You can use the "autocreate=3Dap" parameter to avoid the ne= ed to recreate<br> ath0.<br> <div><br> > 8) iwpriv ath0 authmode 1 =A0 (open mode)<br> <br> </div>I don't think you need to tweak private parameters for basic<br> functionality.<br> <div><br> > 9) iwconfig ath0 essid "test_wlan"<br> > 10) ifconfig ath0 10.1.1.10 netmask 255.255.255.0<br> > 11) ifconfig ath0 up<br> ><br> > *An issue I see, is that everytime I try to set the channel using<br> > iwconfig ath0 channel 6 (or whatever) the kernel panics and the<br> > system goes to hang state, so I leave it at default*<br> <br> </div>I guess if might be the issue that prevents the release of the<br> version <a href=3D"http://0.9.4.1" target=3D"_blank">0.9.4.1</a>:<br> <a href=3D"https://madwifi-project.org/ticket/1903" target=3D"_blank">https= ://madwifi-project.org/ticket/1903</a><br> <br> The workaround it to set the channel while the interface is down.<br> <div><br> > I have a windows 7 client, on which i configure a static IP of<br> > 10.1.1.12 and connect to wlan "test_wlan". The client associ= ates, and<br> > also I was able to sniff the assoc rsp, and ack packets from the air<b= r> > which had a "Success" status.<br> ><br> > However, when I ping 10.1.1.10 (ath0), no response. I get a Dest<br> > Unreachable from 10.1.1.12. So I added arp entry for 10.1.1.10<br> > manually on my client. When I do that the ICMP request times out, and<= br> > I do see the ICMP requests in the air.<br> ><br> > I have been trying to figure out if the driver is dropping these<br> > packets due to some configuration thats wrong? Do let me know if<br> > anyone has faced similar issues.<br> <br> </div>I suggest that you check firewall settings on Fedora (iptables). =A0T= ry<br> turning it off.<br> <div><br> > i have tried using bridges between ath0 and eth0 interface, Even that<= br> > hasnt worked.<br> ><br> > Attaching the outputs of ifconfig, iwconfig and dmesg (No errors i<br> > saw in dmesg) along.<br> ><br> > Also, if anyone has used any of the currently available atheros<br> > chipsets along with Madwifi successfully to set up an AP (Master<br> > mode), would be great if you could provide me the Chipsets model<br> > number, and Madwifi version.. I am fine with any Atheros based<br> > Chipset that is available in the market, as long as I can use it with<= br> > madwifi to setup in AP mode. Just wondering if the DWL-AG530 may be<br= > > having issues in AP mode, since it works just fine as a wireless<br> > client.<br> <br> </div>As far as I know, the only chipsets that are supported by MadWifi but= <br> don't work in AP mode are AR5210 and possibly AR5211. =A0Both are very<= br> old and don't even support 802.11g.<br> <font color=3D"#888888"><br> --<br> Regards,<br> Pavel Roskin<br> </font></blockquote></div><br></div> </div></div></blockquote></div><br></div> --00151747c09a3f904b04ae232d64-- --===============3790640666312894575== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 --===============3790640666312894575== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Madwifi-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/madwifi-users --===============3790640666312894575==--