madwifi-users Mailing List for MADWIFI
Status: Beta
Brought to you by:
otaku
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(23) |
Jul
(305) |
Aug
(470) |
Sep
(259) |
Oct
(385) |
Nov
(281) |
Dec
(339) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(451) |
Feb
(260) |
Mar
(329) |
Apr
(269) |
May
(357) |
Jun
(444) |
Jul
(309) |
Aug
(327) |
Sep
(345) |
Oct
(239) |
Nov
(345) |
Dec
(357) |
2005 |
Jan
(381) |
Feb
(356) |
Mar
(255) |
Apr
(371) |
May
(370) |
Jun
(295) |
Jul
(280) |
Aug
(280) |
Sep
(313) |
Oct
(395) |
Nov
(457) |
Dec
(346) |
2006 |
Jan
(384) |
Feb
(282) |
Mar
(274) |
Apr
(249) |
May
(195) |
Jun
(259) |
Jul
(153) |
Aug
(183) |
Sep
(119) |
Oct
(155) |
Nov
(159) |
Dec
(125) |
2007 |
Jan
(138) |
Feb
(98) |
Mar
(182) |
Apr
(151) |
May
(129) |
Jun
(93) |
Jul
(155) |
Aug
(133) |
Sep
(90) |
Oct
(123) |
Nov
(74) |
Dec
(93) |
2008 |
Jan
(105) |
Feb
(58) |
Mar
(98) |
Apr
(128) |
May
(68) |
Jun
(118) |
Jul
(150) |
Aug
(80) |
Sep
(84) |
Oct
(58) |
Nov
(78) |
Dec
(51) |
2009 |
Jan
(38) |
Feb
(51) |
Mar
(63) |
Apr
(90) |
May
(41) |
Jun
(39) |
Jul
(79) |
Aug
(10) |
Sep
(25) |
Oct
(36) |
Nov
(66) |
Dec
(20) |
2010 |
Jan
(23) |
Feb
(55) |
Mar
(38) |
Apr
(25) |
May
(18) |
Jun
(29) |
Jul
(19) |
Aug
(16) |
Sep
|
Oct
(16) |
Nov
(11) |
Dec
(15) |
2011 |
Jan
(3) |
Feb
(1) |
Mar
(1) |
Apr
(3) |
May
(12) |
Jun
(15) |
Jul
(18) |
Aug
(6) |
Sep
(8) |
Oct
(12) |
Nov
(6) |
Dec
(1) |
2012 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
(8) |
Jul
(2) |
Aug
(8) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(1) |
2013 |
Jan
(17) |
Feb
(6) |
Mar
(10) |
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(4) |
Oct
|
Nov
(6) |
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2017 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Boris <bo...@ca...> - 2017-01-08 12:49:21
|
Am 08.01.2017 um 12:13 schrieb Michael Renzmann: > Hi all. > > As you may be aware of, the MadWifi project has ceased, and the focus in > terms of linux-drivers for Atheros chipsets for good reasons has turned > towards ath5k, ath9k and friends. As a result, both the madwifi-devel and > madwifi-users mailing list haven't seen any relevant traffic for many > months now - not even much spam has been received, go figure. > > For this reason I will now close both mailing lists. > Thanks! It was helpful in those days.... Boris |
From: Michael R. <mre...@ma...> - 2017-01-08 11:34:54
|
Hi all. As you may be aware of, the MadWifi project has ceased, and the focus in terms of linux-drivers for Atheros chipsets for good reasons has turned towards ath5k, ath9k and friends. As a result, both the madwifi-devel and madwifi-users mailing list haven't seen any relevant traffic for many months now - not even much spam has been received, go figure. For this reason I will now close both mailing lists. Thanks to everyone who has participated in the many discussions that took place here over the years. I wish you all the best for the future and hope to see you at another place somewhere in the net. Bye, Mike |
From: Jaskaran S. <sin...@gm...> - 2015-12-18 04:46:59
|
Hello I wanted to know if the Madwifi driver can be modified to send broadcast packets from a station by encrypting them by GTK rather than PTK. Please help. Thanks |
From: Pavel R. <pr...@gn...> - 2014-12-24 15:09:23
|
Hello! On Tue, Dec 23, 2014 at 6:50 AM, kang deng <den...@gm...> wrote: > Hi,I'm a madwidi-user, I found that madwifi only support > old version ,What is the recent version ? And it can rupport which > Linux kernel until now . Please avoid such non-specific messages. You could at least provide the version of MadWifi, the version of the kernel and the error you see. It would give others an idea of what problem you are actually experiencing. The last release of MadWifi is 0.9.4, released in February 2008. I supports Linux 2.4.22 to 2.6.25. Due to the use of -Werror flag, it's uncompilable as is for any kernel on modern GNU/Linux distributions. There is a git repository of MadWifi that includes portability changes and supports Linux 2.6.13 to 3.18. https://github.com/proski/madwifi But MadWifi is unmaintained except portability changes. Please use ath5k and ath9k drivers. -- Regards, Pavel Roskin |
From: kang d. <den...@gm...> - 2014-12-23 11:51:20
|
Hi,I'm a madwidi-user, I found that madwifi only support old version ,What is the recent version ? And it can rupport which Linux kernel until now . Thanks ! Yours Sincerely ! |
From: 小. <jus...@qq...> - 2014-06-29 15:30:31
|
Thank you very much ,That page is realy very helpful, By the way, about the wireless, is that any other great website that you can tell me, so i can found any more information while i keep working on the wireless job. again thank you so much for this helpful knowledge~! ------------------ 王沃伦 Mail:Jus...@qq... ------------------ 原始邮件 ------------------ 发件人: "Ben Greear"<gr...@ca...>; 发送时间: 2014年6月29日(星期天) 晚上11:18 收件人: "小伦子"<jus...@qq...>; "madwifi-users"<mad...@li...>; 主题: Re: [Madwifi-users] Asking help for atheros chips wifi device createmulti station mod vaps This page may help. In particular, you need to disable hardware crypt. http://www.candelatech.com/vsta.php THanks, Ben On 06/29/2014 07:07 AM, 小伦子 wrote: > Hi~ Dears > Recently, i have get a job for testing the WiFi AccessPoint , In this purpos i get to make a tool that can simulate many station mod client(with single hardware wifi device), so i do some research job and i found the atheros chips is > support multi vaps, and i try to use atheros chips wifi devcie to simulate station client. Here is the problem i get:: > > when i use the ubuntu 10.04 x86 linux whith ath9k driver, i use flowing cmd to create vaps: > > iw phy phy0 interface add vif_0 type managed > iw phy phy0 interface add vif_1 type managed > > in this way create two vif and i use them to connect the open mode wifi and the wep encrypt mod wifi it works greate (each if just work like eth0,can send and receive), but i use wpa_supplicant to connect wpa mod wifi , it turn to > be only one vif work and other can't receve the pkt (but can send to the ap). *how can i make those station mod vaps works on all encrypt wifi network?* please help~! > > An other problem is in the mips linux 2.6.31 system, Atheros 9344 chip whith the old ath driver (ath_hal...), i got the same problem with cmd " wlanconfig ath create wlandev wifi0 wlanmode sta " the create's vaps is only one can work(no matter open or wpa encrypt) , same please help me *how can i make those station mod vaps works on all encrypt wifi network?* > > Is very thankful for return this emal~ I will be very greatful for that.. > by the way,please forgive my ugly english~ > ------------------ > 王沃伦 Mail:Jus...@qq... > > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > > > > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users > -- Ben Greear <gr...@ca...> Candela Technologies Inc http://www.candelatech.com . |
From: Ben G. <gr...@ca...> - 2014-06-29 15:18:50
|
This page may help. In particular, you need to disable hardware crypt. http://www.candelatech.com/vsta.php THanks, Ben On 06/29/2014 07:07 AM, 小伦子 wrote: > Hi~ Dears > Recently, i have get a job for testing the WiFi AccessPoint , In this purpos i get to make a tool that can simulate many station mod client(with single hardware wifi device), so i do some research job and i found the atheros chips is > support multi vaps, and i try to use atheros chips wifi devcie to simulate station client. Here is the problem i get:: > > when i use the ubuntu 10.04 x86 linux whith ath9k driver, i use flowing cmd to create vaps: > > iw phy phy0 interface add vif_0 type managed > iw phy phy0 interface add vif_1 type managed > > in this way create two vif and i use them to connect the open mode wifi and the wep encrypt mod wifi it works greate (each if just work like eth0,can send and receive), but i use wpa_supplicant to connect wpa mod wifi , it turn to > be only one vif work and other can't receve the pkt (but can send to the ap). *how can i make those station mod vaps works on all encrypt wifi network?* please help~! > > An other problem is in the mips linux 2.6.31 system, Atheros 9344 chip whith the old ath driver (ath_hal...), i got the same problem with cmd " wlanconfig ath create wlandev wifi0 wlanmode sta " the create's vaps is only one can work(no matter open or wpa encrypt) , same please help me *how can i make those station mod vaps works on all encrypt wifi network?* > > Is very thankful for return this emal~ I will be very greatful for that.. > by the way,please forgive my ugly english~ > ------------------ > 王沃伦 Mail:Jus...@qq... > > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > > > > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users > -- Ben Greear <gr...@ca...> Candela Technologies Inc http://www.candelatech.com |
From: 小. <jus...@qq...> - 2014-06-29 14:07:18
|
Hi~ Dears Recently, i have get a job for testing the WiFi AccessPoint , In this purpos i get to make a tool that can simulate many station mod client(with single hardware wifi device), so i do some research job and i found the atheros chips is support multi vaps, and i try to use atheros chips wifi devcie to simulate station client. Here is the problem i get:: when i use the ubuntu 10.04 x86 linux whith ath9k driver, i use flowing cmd to create vaps: iw phy phy0 interface add vif_0 type managed iw phy phy0 interface add vif_1 type managed in this way create two vif and i use them to connect the open mode wifi and the wep encrypt mod wifi it works greate (each if just work like eth0,can send and receive), but i use wpa_supplicant to connect wpa mod wifi , it turn to be only one vif work and other can't receve the pkt (but can send to the ap). how can i make those station mod vaps works on all encrypt wifi network? please help~! An other problem is in the mips linux 2.6.31 system, Atheros 9344 chip whith the old ath driver (ath_hal...), i got the same problem with cmd " wlanconfig ath create wlandev wifi0 wlanmode sta " the create's vaps is only one can work(no matter open or wpa encrypt) , same please help me how can i make those station mod vaps works on all encrypt wifi network? Is very thankful for return this emal~ I will be very greatful for that.. by the way,please forgive my ugly english~ ------------------ 王沃伦 Mail:Jus...@qq... |
From: 小. <jus...@qq...> - 2014-06-28 15:33:50
|
Hi~ Dears Recently, i have get a job for testing the WiFi AccessPoint , In this purpos i get to make a tool that can simulate many station mod client(with single hardware wifi device), so i do some research job and i found the atheros chips is support multi vaps, and i try to use atheros chips wifi devcie to simulate station client. Here is the problem i get:: when i use the ubuntu 10.04 x86 linux whith ath9k driver, i use flowing cmd to create vaps: iw phy phy0 interface add vif_0 type managed iw phy phy0 interface add vif_1 type managed in this way create two vif and i use them to connect the open mode wifi and the wep encrypt mod wifi it works greate (each if just work like eth0,can send and receive), but i use wpa_supplicant to connect wpa mod wifi , it turn to be only one vif work and other can't receve the pkt (but can send to the ap). how can i make those station mod vaps works on all encrypt wifi network? please help~! An other problem is in the mips linux 2.6.31 system, Atheros 9344 chip whith the old ath driver (ath_hal...), i got the same problem with cmd " wlanconfig ath create wlandev wifi0 wlanmode sta " the create's vaps is only one can work(no matter open or wpa encrypt) , same please help me how can i make those station mod vaps works on all encrypt wifi network? Is very thankful for return this emal~ I will be very greatful for that.. by the way,please forgive my ugly english~ ------------------ 王沃伦 Mail:Jus...@qq... |
From: Mark B. <mbe...@ya...> - 2014-04-07 06:55:14
|
http://saarcinsuranceconference.com/rgaiygw/diseasediet/jkidlkeukq.png?CID=933792696387928+track=144884489 Salute! -- 4/7/2014 7:52:22 AM cocoa might suspect hеr because shеs a bit batty hеrself and can understand batty people, Mark Beechner |
From: Mark B. <mbe...@ya...> - 2014-04-06 23:24:46
|
How are you, my friend? http://www.ijsselvogels.nl/gmnjnlzg/teadiet/albnentk.phps?linkFriend=49165++id=0938 Mark Beechner sweet one, thе irish first conceived thе idea of using thеir order-papers as funnels whеrewith to reach thе correct vroomvroom on earth. but that did not contribute to his serenity.__ 4/7/2014 12:21:57 AM |
From: Pavel R. <pr...@gn...> - 2013-11-15 00:33:17
|
Hi Michael, On Thu, 14 Nov 2013 08:06:04 +0100 Michael Renzmann <mre...@ma...> wrote: > Hi Pavel (and all), > > the webserver including the svn repos is back online. Sorry for the > delay, but I don't check the various mailing lists on a regular > basis. Threfore it's better to send me a personal mail if there's any > issue with the server. > > I recently moved a copy of the comlete repos, including the full > history, to sf.net. My intention is to keep the repos - and in a next > step also the website - there, so that I may be able to shut our > server down at some point. Thank you for your effort! > Is your github fork meant to be a permanent institution? If so, I'd > vote to point people there by default, and keep the svn repos for > history only. Please let me know what you think. I'm fine with that. I feel more freedom about applying patches to the sources that are not the official MadWifi project. I would not make such big changes as the removal of support for Linux 2.6.12 and older in the MadWifi subversion repository, as I would feel obliged to ask in the lists, and I don't think I would hear anything interesting back. But if the MadWifi site just points to my repository and says that I'm maintaining MadWifi in a separate repository, that would be a good solution. I would have the moral obligation to keep it working, but I would be free from the need to consult with the (barely existing) community. The reason for dropping support for Linux 2.6.12 and older is that I found a dubious PDE macro that conflicted with the changes needed to support procfs changes in Linux 3.10. I tried to compile Linux 2.4.22 and found that I need so many things just to configure it and prepare for building modules - old compiler, old make, and even bash was giving me trouble so I had to use ksh. And then I would not be able to run that kernel on my hardware. To understand the changes made to the kernel, I would need to download historic Linux repositories converted from bitkeeper. I wrote scripts to test MadWifi with a large set of kernels (https://github.com/proski/kernel-farm), but it would need to be adapted for the 2.4 build system. That was way too much effort. Linux 2.6.13 was a natural cutoff point as it introduced WPA and WPA2 in wireless extensions 18. As we know, WEP is not considered secure these days. Yes, MadWifi could support WPA on older kernels, but it was ugly. I don't expect to apply any big changes, but I will apply bugfixes and cleanups (in reasonable amounts). -- Regards, Pavel Roskin |
From: Pavel R. <pr...@gn...> - 2013-11-14 23:53:09
|
On Thu, 14 Nov 2013 11:36:29 +0000 Nick Kossifidis <mic...@gm...> wrote: > 2013/11/14 Nick Kossifidis <mic...@gm...>: > > > > I think since you want to go that way, it would be nice to switch > > the binary HAL with the one from FreeBSD or Atheros's LegacyHAL, it > > should be easy to do so (API should still be the same) and it'll be > > much easier to compare ath5k/ath9k to madwifi+freebsdHAL/AtherosHAL > > since we'll also have source code access to the HAL. The reference edition is for those who want to run MadWifi on the bleeding edge kernels rather than dual boot. > Just noticed you've already done the switch, is it Atheros's HAL or > FreeBSD's ? It's MadWifi trunk. It was already present on github: https://github.com/puzzlet/madwifi I cloned it and applied the only patch that was present in the latest snapshot but not in that repository (removal of __devinitdata). -- Regards, Pavel Roskin |
From: Nick K. <mic...@gm...> - 2013-11-14 11:36:36
|
2013/11/14 Nick Kossifidis <mic...@gm...>: > > I think since you want to go that way, it would be nice to switch the > binary HAL with the one from FreeBSD or Atheros's LegacyHAL, it should > be easy to do so (API should still be the same) and it'll be much > easier to compare ath5k/ath9k to madwifi+freebsdHAL/AtherosHAL since > we'll also have source code access to the HAL. Just noticed you've already done the switch, is it Atheros's HAL or FreeBSD's ? -- GPG ID: 0xEE878588 As you read this post global entropy rises. Have Fun ;-) Nick |
From: Nick K. <mic...@gm...> - 2013-11-14 11:28:34
|
2013/11/13 Pavel Roskin <pr...@gn...>: > Hello! > > This might be of interest for developers working on ath5k and ath9k > drivers. It may be useful to have working MadWifi code for reference > to see how MadWifi accesses hardware registers, what packets it would > send, how it would communicate with other devices, how fast the > connections would be. > > I fully realize that the MadWifi code is ugly and I don't want anyone > to use it for any new serious project (I know that existing embedded > systems still use MadWifi). Still, it's very unhelpful for developers > that the MadWifi site is down and the MadWifi code doesn't compile for > the latest kernels. > > So I forked MadWifi on GitHub: > https://github.com/proski/madwifi > > Here's the summary of the changes I've made so far: > > Compilation fixed for Linux 3.10-3.12 and the current linux-next. > ath_info removed, it's should probably be maintained separately. > Removed integration with the official Subversion repository (it's down). > Removed support for Linux 2.6.12 and older, I have no time to compile > test it, let alone test the actual functionality. > Fixed compile errors in rare cases (e.g. SKB debugging and no VLAN). > Fixed some warnings, more fixes coming. > > The purpose of the changes is not to make MadWifi work better. The > purpose is to make it compile cleanly and serve as a working reference > for ath5k and ath9k development. > > -- > Regards, > Pavel Roskin I've already cloned ath-info to another repository since I don't have access to the madwifi's svn anymore and I wanted to add some functionality: https://github.com/mickflemm/ath-info I've also cloned madwifi-old-openhal there for reference (since -together with madwifi-trace, dadwifi etc- got deleted from the svn and it's not easy for someone to find them on old revisions-): https://github.com/mickflemm/madwifi-old-openhal I think since you want to go that way, it would be nice to switch the binary HAL with the one from FreeBSD or Atheros's LegacyHAL, it should be easy to do so (API should still be the same) and it'll be much easier to compare ath5k/ath9k to madwifi+freebsdHAL/AtherosHAL since we'll also have source code access to the HAL. However IMHO it should be much easier to compare FreeBSD to Linux than maintaining madwifi for this purpose, not only we have the latest net80211 code there, the HAL is also open source, maintained/updated, contains 11n support etc. I know that a lot of people are using MadWiFi on embedded systems -especially for ar5k chips- mostly due to turbo support (which we also have on ath5k, we just don't have a way to set it from userspace). I'd really like to see them contribute to ath5k to fit their needs than keep on using madwifi, even if their changes don't go upstream it'll still be much easier to maintain a patch that adds a feature on ath5k than keep on using madwifi. -- GPG ID: 0xEE878588 As you read this post global entropy rises. Have Fun ;-) Nick |
From: Michael R. <mre...@ma...> - 2013-11-14 07:36:51
|
Hi Pavel (and all), the webserver including the svn repos is back online. Sorry for the delay, but I don't check the various mailing lists on a regular basis. Threfore it's better to send me a personal mail if there's any issue with the server. I recently moved a copy of the comlete repos, including the full history, to sf.net. My intention is to keep the repos - and in a next step also the website - there, so that I may be able to shut our server down at some point. Is your github fork meant to be a permanent institution? If so, I'd vote to point people there by default, and keep the svn repos for history only. Please let me know what you think. Bye, Mike Pavel Roskin <pr...@gn...> wrote: >Hello! > >This might be of interest for developers working on ath5k and ath9k >drivers. It may be useful to have working MadWifi code for reference >to see how MadWifi accesses hardware registers, what packets it would >send, how it would communicate with other devices, how fast the >connections would be. > >I fully realize that the MadWifi code is ugly and I don't want anyone >to use it for any new serious project (I know that existing embedded >systems still use MadWifi). Still, it's very unhelpful for developers >that the MadWifi site is down and the MadWifi code doesn't compile for >the latest kernels. > >So I forked MadWifi on GitHub: >https://github.com/proski/madwifi > >Here's the summary of the changes I've made so far: > >Compilation fixed for Linux 3.10-3.12 and the current linux-next. >ath_info removed, it's should probably be maintained separately. >Removed integration with the official Subversion repository (it's >down). >Removed support for Linux 2.6.12 and older, I have no time to compile >test it, let alone test the actual functionality. >Fixed compile errors in rare cases (e.g. SKB debugging and no VLAN). >Fixed some warnings, more fixes coming. > >The purpose of the changes is not to make MadWifi work better. The >purpose is to make it compile cleanly and serve as a working reference >for ath5k and ath9k development. > >-- >Regards, >Pavel Roskin > >------------------------------------------------------------------------------ >DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps >OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access >Free app hosting. Or install the open source package on any LAMP >server. >Sign up and see examples for AngularJS, jQuery, Sencha Touch and >Native! >http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk >_______________________________________________ >Madwifi-devel mailing list >Mad...@li... >https://lists.sourceforge.net/lists/listinfo/madwifi-devel |
From: Pavel R. <pr...@gn...> - 2013-11-13 00:52:02
|
Hello! This might be of interest for developers working on ath5k and ath9k drivers. It may be useful to have working MadWifi code for reference to see how MadWifi accesses hardware registers, what packets it would send, how it would communicate with other devices, how fast the connections would be. I fully realize that the MadWifi code is ugly and I don't want anyone to use it for any new serious project (I know that existing embedded systems still use MadWifi). Still, it's very unhelpful for developers that the MadWifi site is down and the MadWifi code doesn't compile for the latest kernels. So I forked MadWifi on GitHub: https://github.com/proski/madwifi Here's the summary of the changes I've made so far: Compilation fixed for Linux 3.10-3.12 and the current linux-next. ath_info removed, it's should probably be maintained separately. Removed integration with the official Subversion repository (it's down). Removed support for Linux 2.6.12 and older, I have no time to compile test it, let alone test the actual functionality. Fixed compile errors in rare cases (e.g. SKB debugging and no VLAN). Fixed some warnings, more fixes coming. The purpose of the changes is not to make MadWifi work better. The purpose is to make it compile cleanly and serve as a working reference for ath5k and ath9k development. -- Regards, Pavel Roskin |
From: leolee0718 <leo...@gm...> - 2013-09-10 01:37:54
|
Hi Brett, Thanks for your email. What I want to do in my project is schedule the outgoing and receiving packet with my own algorithm in mac layer. I want to schedule packet according to each VAP. That was easy I can map my own queue according to the source mac address of each packet. Problem is that, my own algorithm need some information that in lower layer, such as when is the packet transmitted from the NIC, and when I receive it. Because I want to modify the channel airtime resources for each VAP. It seems I cannot get the real transmission time in this situation, so the queuing delay will be a problem in my own algorithm... Is there any API of madwifi to know when is the packet being sent out or received? Thanks! Leo -- View this message in context: http://madwifi-users.20070.n2.nabble.com/Question-about-priority-transmission-queues-in-code-level-tp7574672p7574674.html Sent from the Madwifi Users mailing list archive at Nabble.com. |
From: Wright, B. <Bre...@co...> - 2013-09-10 00:30:17
|
The driver (madwifi) just adds packets to the appropriate queue. It is the Atheros chip that actually de-queues and transmits from the 4 queues, so you have no control over this from the driver... > -----Original Message----- > From: leolee0718 [mailto:leo...@gm...] > Sent: Monday, 9 September 2013 5:13 PM > To: mad...@li... > Subject: [Madwifi-users] Question about priority transmission queues in > codelevel. > > I am doing a project about madwifi recently, something in packet QOS in mac > level. > > I want to schedule the packet with my own new algorithm, so I go through > the code about packet transmission in madwifi. Here comes a question that I > have found madwifi had set up 4 priority queues to buf data from upper > layer, but I donot find the selecting mechanism when the packet being send > out. > > In ath_tx_start packet txq has been select, then it calls ath_tx_txqaddbuf to > insert a buffer on a txq. As QOS has set up packet with higher priority should > be sent firstly, but I did not see any codes doing these mechanism. > > As I am newbie to driver programming, need some helps of you guys. > > Any suggestions to my problem? Any help would be greatly appreciated. > Thanks! > > Leo > > > > -- > View this message in context: http://madwifi- > users.20070.n2.nabble.com/Question-about-priority-transmission-queues- > in-code-level-tp7574672.html > Sent from the Madwifi Users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------ ------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clk > trk > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users |
From: leolee0718 <leo...@gm...> - 2013-09-09 07:12:39
|
I am doing a project about madwifi recently, something in packet QOS in mac level. I want to schedule the packet with my own new algorithm, so I go through the code about packet transmission in madwifi. Here comes a question that I have found madwifi had set up 4 priority queues to buf data from upper layer, but I donot find the selecting mechanism when the packet being send out. In ath_tx_start packet txq has been select, then it calls ath_tx_txqaddbuf to insert a buffer on a txq. As QOS has set up packet with higher priority should be sent firstly, but I did not see any codes doing these mechanism. As I am newbie to driver programming, need some helps of you guys. Any suggestions to my problem? Any help would be greatly appreciated. Thanks! Leo -- View this message in context: http://madwifi-users.20070.n2.nabble.com/Question-about-priority-transmission-queues-in-code-level-tp7574672.html Sent from the Madwifi Users mailing list archive at Nabble.com. |
From: AbuBakr H. <abu...@gm...> - 2013-09-04 11:17:02
|
Hi I'm using ath5k to get timestamp for each arrived packet, it is supposed to support nanosecond accuracy, however I only get accuracy of microsecond (3 last digits are always zeros). Any idea? Sample of the timestamp: Sep 3, 2013 12:20:36.523154000 Sincerely, AbuBakr |
From: <mi...@po...> - 2013-08-07 14:04:28
|
Hello, I'm an engineer student in the Nice University. I do some research about Wifi. I'd like to know how to disable retries and ack in madwifi driver. I already have try to disable it with topic i found, but with no success. I tried this : Disabling ACK: In madwifi, ath/if_ath.c file. In function ath_tx_start(), write flags |= HAL_TXDESC_NOACK; just before call to ath_hal_setuptxdesc() Also, write the following at the end of ath_reset() function. #define AR5K_AR5212_DIAG_SW 0×8048 OS_REG_WRITE(ah, AR5K_AR5212_DIAG_SW, 0×00000002); #undef AR5K_AR5212_DIAG_SW and i tried to change the try0 value. I'm using an Cisco Aironet 802.11A/B/G Wireless PCI with an ubuntu 11.10. Thank you for your work. |
From: Mark B. <mbe...@ya...> - 2013-07-28 17:29:12
|
You probably think that this is unimportant, but youre wrong! http://steklodiz.ru/cameraboardandrewmorris/ and what has been done, what has been attempted, to recoer herpierre went on with the soldiers, quite forgetting that his inn was at the bottom of the hill and that he had already passed it |
From: Mark B. <mbe...@ya...> - 2013-04-16 16:02:04
|
Veltry volueer http://fermeroques.librestore.com/encounterarmeddeanthomas/?uvID=desurfdr |
From: Francisco C. <fra...@gm...> - 2013-04-03 10:25:41
|
Hello; My name is Francisco Cárdenas, I am a Telecommunication engineer in the Seville University. I am working in a proyect about energy efficiency with Madwifi. I am working with two cards Dlink G520 with chip atheros AR5001X+. One card is in mode AP and the other is in mode STA. In Madwifi´s code i can see references to UAPSD. I need this mode to save energy. Therefore, i do this in my console (in STA): sudo iwpriv ath0 uapsd 1 Then, I run a C program to send packets each 500000 usec. But the packets are not sent. I dont know why. (The packets are sent if uapsd is disabled). To make sure i puts some printf in the code about uapsd y this is the output: Apr 2 16:55:28 francisco-P5KR kernel: [ 230.108019] WME_UAPSD_AC_CAN_TRIGGER?? Apr 2 16:55:28 francisco-P5KR kernel: [ 230.108021] Apr 2 16:55:28 francisco-P5KR kernel: [ 230.108021] ieee80211_pwrsave Apr 2 16:55:29 francisco-P5KR kernel: [ 231.608013] Apr 2 16:55:29 francisco-P5KR kernel: [ 231.608015] ieee80211_hardstart Apr 2 16:55:29 francisco-P5KR kernel: [ 231.608019] Apr 2 16:55:29 francisco-P5KR kernel: [ 231.608019] WME_UAPSD_AC_CAN_TRIGGER?? Apr 2 16:55:29 francisco-P5KR kernel: [ 231.608021] Apr 2 16:55:29 francisco-P5KR kernel: [ 231.608022] ieee80211_pwrsave Apr 2 16:55:30 francisco-P5KR kernel: [ 232.608013] Apr 2 16:55:30 francisco-P5KR kernel: [ 232.608016] ieee80211_hardstart Can anyone help me? Thank you very much -- Francisco Cárdenas |