Thread: [Madwifi-users] Corrupted Packets
Status: Beta
Brought to you by:
otaku
From: Clifton W. <cli...@gm...> - 2006-12-22 21:18:35
|
Hi guys, I modified madwifi-0.9.2.1 to allow me to look at the corrupted 802.11 frames recevied by the driver. I noticed that every field was subject to corruption except the destination mac address in the 802.11 mac header. Is HAL discarding frames that don't have the same mac address in the destination mac address field as the intended receiver before passing them to the driver? Thanks. |
From: Jose I. C. T. <ild...@gm...> - 2006-12-22 22:46:42
|
Hi! On 12/22/06, Clifton Watson <cli...@gm...> wrote: > Hi guys, > > I modified madwifi-0.9.2.1 to allow me to look at the corrupted 802.11 > frames recevied by the driver. I noticed that every field was > subject to corruption except the destination mac address in the 802.11 > mac header. Is HAL discarding frames that don't have the same mac > address in the destination mac address field as the intended receiver > before passing them to the driver? I don't think it's the hal. Try with a "monitor" interface. The thing is: you could receive packages that were not directed to you. I may be wrong: I'm not an expert in this area. Hope this helps, Ildefonso Camargo |
From: Jose I. C. T. <ild...@gm...> - 2006-12-27 02:17:01
|
Hi!. On 12/23/06, Clifton Watson <cli...@gm...> wrote: > Hi Jose, > > You are right. However, the catch is to not be in "monitor" mode. I > am trying to receive all packets in a "normal" operating mode, > regardless of whether they are corrupted or aren't necessarily > destined for a particular receiver. I'm not sure if this "actually" works, but I had created "monitor mode" and "sta" interfaces at the same time. In this moment I'm using the wireless link a lot (important stuff), and I can't risk the downtime if I create and use the monitor interface and it makes my sta interface go down :-S ... so, I can't test right now. But I think that if you create both, the monitor and the sta, you should get packages with a destination mac *different* from the local mac. I don't know if one get corrupted (ie, bad crc) packages in monitor mode.... but the fact is: you can have both: monitor and sta interface (I even had an AP, STA, and then added a "monitor" just to "see" if it was possible). > > I am getting corrupted packets but none of them seem to have a > corrupted destination mac address. The source and transmitter mac > addresses are corrupted sometimes, but not the destination mac. I > expected that if a packet was corrupt or had a bad CRC, I would see a > corrupted destination mac address sometimes. Sounds like the interface is filtering the packages that have a wrong MAC (and thus is not directed to "this" sta). > > Maybe there is a way the driver can be modified to allow this. If > anybody has an idea of how or where this can be done, please let me > know. If you happend to need to play around with the hal, you should try OpenBSD: they have the "openhal". I saw somewhere a port to the "madwifi-old" of the openhal. > > Thanks for your feedback Jose. NP. c-ya! Ildefonso Camargo > > On 12/22/06, Jose Ildefonso Camargo Tolosa <ild...@gm...> wrote: > > Hi! > > > > On 12/22/06, Clifton Watson <cli...@gm...> wrote: > > > Hi guys, > > > > > > I modified madwifi-0.9.2.1 to allow me to look at the corrupted 802.11 > > > frames recevied by the driver. I noticed that every field was > > > subject to corruption except the destination mac address in the 802.11 > > > mac header. Is HAL discarding frames that don't have the same mac > > > address in the destination mac address field as the intended receiver > > > before passing them to the driver? > > > > I don't think it's the hal. Try with a "monitor" interface. The > > thing is: you could receive packages that were not directed to you. > > > > I may be wrong: I'm not an expert in this area. > > > > Hope this helps, > > > > Ildefonso Camargo > > > > > -- > --C. L. Watson > ************************************************************** > Clifton L. Watson, M.S. Student > Michigan State University > Department of Electrical and Computer Engineering > Wireless And Video communicationS Laboratory > 2322 Engineering Building > East Lansing, MI 48824-1226 > <http://www.egr.msu.edu/waves/people/watson.htm> > ************************************************************** > |
From: Leszek O. <le...@os...> - 2006-12-27 08:58:30
|
The holy war never ends, does it: http://www.thejemreport.com/mambo/content/view/293/ Leszek |
From: Michael R. <ma...@no...> - 2006-12-29 17:30:02
|
Hi. > http://www.thejemreport.com/mambo/content/view/293/ Thanks for the information. Here's my response to that article. If anyone knows the e-mail address of the author, feel free to forward it to that guy. === cut === > Mysteriously, it has virtually no support from the Madwifi > Project, which is the development team responsible for > creating Atheros drivers for Linux-based operating systems. Wrong. We have madwifi-old-openhal as well as dadwifi-openhal branches in our repository, and the person who actively ports OpenHAL to Linux - Nick Kossifidis - works directly in that repository. Of course, there is still a lot of work to do, but Rome wasn't built in one day. Switching from one HAL to another is complicated and can not be expected to happen instantly. > Madwifi continues to primarily support the proprietary > Atheros HAL, Of course, what else should we do? Cut the support for the binary-only HAL and leave the users in the rain while the integration of OpenHAL into MadWifi is worked on? This is not the way we want to deal with the users of our driver. > though there is an old and uninformative page in the > Madwifi Wiki about it. Old? Looking at the history, the page has been created "10/18/06", telling the interested reader that it's just a little more than two months old. Uninformative? Well, we are far from perfect and we can't fight on all fronts at the same time. And after all: it's a wiki. Users are welcome to contribute text that makes the page better understandable. Questions on that topic will be answered as our time and knowledge allows when they are sent to one of the known mailing lists. > The email addresses listed for the Madwifi developers > either bounce Which of the given addresses bounced? At least the one from me does definitely not bounce (unless the IP of the sending mail server is listed either in list.dsbl.org, safe.dnsbl.sorbs.net or sbl-xbl.spamhaus.org). Even then there's always the mailing lists as a possibility to get in contact with the team, if other ways fail. > or elicit no response to requests I can not speak for the others on the team, but I'm quite sure I didn't get a request from the person who wrote the article on my published mail addresses. Obviously, I can not respond to something I didn't get. > for comments on why there is no apparent effort > to use the open source HAL in Madwifi. This part of the sentence shows that the article, at least partially, has been badly researched. There were some extensive discussions in madwifi-devel as well as netdev about integrating OpenHAL into MadWifi during the last weeks. > It may very well be pressure from Atheros that keeps > ar5k out of Madwifi, Bullshit. Atheros didn't put any pressure on us, neither in terms of development decisions nor in other terms. > but no one at Madwifi or Atheros would talk to me about it. Again: it's hard to respond if one is not asked. === cut === Bye, Mike |
From: Pavel R. <pr...@gn...> - 2006-12-29 22:42:40
|
On Fri, 2006-12-29 at 18:29 +0100, Michael Renzmann wrote: > Wrong. We have madwifi-old-openhal as well as dadwifi-openhal branches in > our repository, and the person who actively ports OpenHAL to Linux - Nick > Kossifidis - works directly in that repository. And if this effort succeeds, Atheros chipsets with be supported by Linux without any binary blobs under any license, which is not the case for Atmel or even Prism 3. -- Regards, Pavel Roskin |
From: p0g0 <p0...@ma...> - 2006-12-29 23:16:13
|
Regarding all the JemReport BS. It might have a bit of a silver lining: Mr Jem panned both MadWifi and Atheros on /. and I'd guess that Atheros's PR person is right pissed off about it. Given our recently invigorated ambition to improve ties with Atheros, I'd suggest that we might contact Atheros PR & offer to improve our mutual FOSS reputations, and try to have a happy conversation with them about how they have already supported FOSS (code drops, past employee support, Sam, their stuff on the Atheros website), and what things we might be able to say about the future-it's a good chance to sell the product. My 2cents. Will Herrick Michael Renzmann wrote: > Hi. > > >> http://www.thejemreport.com/mambo/content/view/293/ >> > > Thanks for the information. Here's my response to that article. If anyone > knows the e-mail address of the author, feel free to forward it to that > guy. > > === cut === > >> Mysteriously, it has virtually no support from the Madwifi >> Project, which is the development team responsible for >> creating Atheros drivers for Linux-based operating systems. >> > > Wrong. We have madwifi-old-openhal as well as dadwifi-openhal branches in > our repository, and the person who actively ports OpenHAL to Linux - Nick > Kossifidis - works directly in that repository. > > Of course, there is still a lot of work to do, but Rome wasn't built in > one day. Switching from one HAL to another is complicated and can not be > expected to happen instantly. > > >> Madwifi continues to primarily support the proprietary >> Atheros HAL, >> > > Of course, what else should we do? Cut the support for the binary-only HAL > and leave the users in the rain while the integration of OpenHAL into > MadWifi is worked on? This is not the way we want to deal with the users > of our driver. > > >> though there is an old and uninformative page in the >> Madwifi Wiki about it. >> > > Old? Looking at the history, the page has been created "10/18/06", telling > the interested reader that it's just a little more than two months old. > > Uninformative? Well, we are far from perfect and we can't fight on all > fronts at the same time. And after all: it's a wiki. Users are welcome to > contribute text that makes the page better understandable. Questions on > that topic will be answered as our time and knowledge allows when they are > sent to one of the known mailing lists. > > >> The email addresses listed for the Madwifi developers >> either bounce >> > > Which of the given addresses bounced? At least the one from me does > definitely not bounce (unless the IP of the sending mail server is listed > either in list.dsbl.org, safe.dnsbl.sorbs.net or sbl-xbl.spamhaus.org). > Even then there's always the mailing lists as a possibility to get in > contact with the team, if other ways fail. > > >> or elicit no response to requests >> > > I can not speak for the others on the team, but I'm quite sure I didn't > get a request from the person who wrote the article on my published mail > addresses. Obviously, I can not respond to something I didn't get. > > >> for comments on why there is no apparent effort >> to use the open source HAL in Madwifi. >> > > This part of the sentence shows that the article, at least partially, has > been badly researched. There were some extensive discussions in > madwifi-devel as well as netdev about integrating OpenHAL into MadWifi > during the last weeks. > > >> It may very well be pressure from Atheros that keeps >> ar5k out of Madwifi, >> > > Bullshit. Atheros didn't put any pressure on us, neither in terms of > development decisions nor in other terms. > > >> but no one at Madwifi or Atheros would talk to me about it. >> > > Again: it's hard to respond if one is not asked. > === cut === > > Bye, Mike > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users > > |
From: Jose I. C. T. <ild...@gm...> - 2006-12-29 02:16:15
|
Hi! On 12/27/06, Leszek Olszewski <le...@os...> wrote: > The holy war never ends, does it: No, it doesn't. But it turns to be very funny from time to time. Nice article, I really liked to read it: I'll try to buy more from Ralink and Atmel :P . I have had LOTS of problems with the Atheros card I have. I'm about to install openbsd just to see if it behaves better. I'll let you know when I do it. c-ya! Ildefonso Camargo > > http://www.thejemreport.com/mambo/content/view/293/ > > Leszek > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users > |
From: synfin <sy...@gm...> - 2006-12-29 14:53:32
|
> I have had LOTS of problems with the Atheros card I have. I'm about > to install openbsd just to see if it behaves better. OpenBSD 4.0 won't recognize my D-Link G520s (AR 5212) properly. Previously, I have been able to get hostap working, but only in 11b mode. OpenBSD's OpenHAL is definitely the future, but we'll all have to give it more time and help it mature. My only problem with madwifi has been with bridging. I'm currently using FreeBSD 6.1 in a wireless bridge without issue and madwifi on all the clients. >> No, it doesn't. But it turns to be very funny from time to time. >the article is way beyond funny. Its full of untruths and half-truths. Some of the questions posed about Madwifi could have been answered with just a little research across this list. http://undeadly.org/cgi?action=article&sid=20061221105518&pid=21 Kind regards, Josh |
From: Jim T. <ji...@ne...> - 2006-12-29 03:31:17
|
On Dec 28, 2006, at 4:16 PM, Jose Ildefonso Camargo Tolosa wrote: > Hi! > > On 12/27/06, Leszek Olszewski <le...@os...> wrote: >> The holy war never ends, does it: > > No, it doesn't. But it turns to be very funny from time to time. the article is way beyond funny. Its full of untruths and half-truths. > Nice article, I really liked to read it: I'll try to buy more from > Ralink and Atmel :P . this is a (mostly) Atheros list. Why are you here? > I have had LOTS of problems with the Atheros card I have. I'm about > to install openbsd just to see if it behaves better. I'll let you > know when I do it. If it magically works better under OpenBSD I'll be surprised. > c-ya! > > Ildefonso Camargo > >> >> http://www.thejemreport.com/mambo/content/view/293/ >> >> Leszek >> >> >> --------------------------------------------------------------------- >> ---- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to >> share your >> opinions on IT & business topics through brief surveys - and earn >> cash >> http://www.techsay.com/default.php? >> page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Madwifi-users mailing list >> Mad...@li... >> https://lists.sourceforge.net/lists/listinfo/madwifi-users >> > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users |
From: Jose I. C. T. <ild...@gm...> - 2006-12-30 00:21:18
|
On 12/28/06, Jim Thompson <ji...@ne...> wrote: > > On Dec 28, 2006, at 4:16 PM, Jose Ildefonso Camargo Tolosa wrote: > > > Hi! > > > > On 12/27/06, Leszek Olszewski <le...@os...> wrote: > >> The holy war never ends, does it: > > > > No, it doesn't. But it turns to be very funny from time to time. > > the article is way beyond funny. Its full of untruths and half-truths. Yep. > > > Nice article, I really liked to read it: I'll try to buy more from > > Ralink and Atmel :P . > > this is a (mostly) Atheros list. Why are you here? Because I happen to have two Atheros cards.... well.... I...basically.... only have Atheros cards.... mmmm.... except my laptop which came with an IPW3945 (intel), and it is Mini PCI Express, and I have no other MiniPCI Express card to change it :( . > > > I have had LOTS of problems with the Atheros card I have. I'm about > > to install openbsd just to see if it behaves better. I'll let you > > know when I do it. > > If it magically works better under OpenBSD I'll be surprised. me too... but it doesn't work very well now, so I just want to try it! ... and I need to learn OpenBSD anyway.... and FreeBSD. See: the problem that have me "pissed" now is that it just "magically" disassociate from the AP, and it do not associate again, it just keep scanning, and scanning, and scanning... and If I run a "iwlist ath2 scan", I see the AP!!!!!!. Anyway, I make the interfaces down, and then remove the ath_pci module, reload it, and then configure the interfaces again, and it associate again with no problem. This use to happen randomly in intervals that varies from 20 minutes to several hours... but It happen everyday. Anyway.... I still hasn't had the time to setup my openbsd box... but I'll do it this weekend. After that, I'll try FreeBSD, and give feedback on it. If I have the time, I'll download and try the "madwifi-old", and the dadwifi project... "just to see". Thanks for creating this great piece of code: I really appreciate the good and hard work you have put in this. c-ya! Ildefonso Camargo |
From: Jim T. <ji...@ne...> - 2006-12-31 07:28:53
|
On Dec 29, 2006, at 2:21 PM, Jose Ildefonso Camargo Tolosa wrote: > On 12/28/06, Jim Thompson <ji...@ne...> wrote: >> this is a (mostly) Atheros list. Why are you here? > > Because I happen to have two Atheros cards.... well.... > I...basically.... only have Atheros cards.... mmmm.... except my > laptop which came with an IPW3945 (intel), and it is Mini PCI Express, > and I have no other MiniPCI Express card to change it :( . If you really have a PCI (mini) Express Atheros card, I'll be shocked if OpenBSD detects it at all. but perhaps your Atheros cards are CardBus or (non-express) miniPCI, and likely therefore are based on ar5002 (or earlier) chipsets. >> If it magically works better under OpenBSD I'll be surprised. > > me too... but it doesn't work very well now, so I just want to try it! > ... and I need to learn OpenBSD anyway.... and FreeBSD. If it magically works better under FreeBSD (esp 6.x), I won't be surprised. If it magically works better under OpenBSD (any version), I will. > See: the problem that have me "pissed" now is that it just "magically" > disassociate from the AP, and it do not associate again, it just keep > scanning, and scanning, and scanning... and If I run a "iwlist ath2 > scan", I see the AP!!!!!!. So the AP is still sending beacons, and the card is still receiving. Do you know (via a frame capture, or similar) if your laptop is continuing to attempt to (re-)associate to the AP? If so, does the AP respond? > Anyway, I make the interfaces down, and > then remove the ath_pci module, reload it, and then configure the > interfaces again, and it associate again with no problem. This use to > happen randomly in intervals that varies from 20 minutes to several > hours... but It happen everyday. Could be something completely external to your setup as well. Jim |