Thread: [Madwifi-devel] BSD port -- release 9
Status: Beta
Brought to you by:
otaku
From: Mathieu L. <Mat...@so...> - 2003-11-06 09:14:01
|
hi all, Here is a _tested_ release: ftp://ftp-sop.inria.fr/dream/Outgoing/madwifi-9.tar.gz ftp://ftp-sop.inria.fr/dream/Outgoing/port.notes-9 What has been tested: 1) connect to an internet-connected AP, download through ftp.lip6.fr linux-2.4.22.tar.bz2: 600KB/s. 2) connect 2 madwifi STAs to the same AP, exchange between the 2 STAs through the AP with UDP the same linux-2.4.22.tar.bz2: 285KB/s. 3) connect 1 madwifi STA to 1 madwifi AP, exchange the same linux-2.4.22.tar.bz2 between the STA and the AP: badly works. The STA seems to randomly revert to SCAN thus breaking the connection. I have not really investigated exactly what happens and why it happens. I hope this will work for as many people as possible. This is hopefully the last release before I start checking this into a CVS branch. regards, Mathieu -- Mathieu Lacage <mat...@so...> |
From: Jean L. <lo...@cl...> - 2003-11-06 09:25:42
|
hi ! thanks for reactivity =) could you just swap line 1399 and 1398 in if_ath.c ;-) ? bye Jean Mathieu Lacage wrote: > hi all, > > Here is a _tested_ release: > ftp://ftp-sop.inria.fr/dream/Outgoing/madwifi-9.tar.gz > ftp://ftp-sop.inria.fr/dream/Outgoing/port.notes-9 > What has been tested: > 1) connect to an internet-connected AP, download through ftp.lip6.fr > linux-2.4.22.tar.bz2: 600KB/s. > 2) connect 2 madwifi STAs to the same AP, exchange between the 2 STAs > through the AP with UDP the same linux-2.4.22.tar.bz2: 285KB/s. > 3) connect 1 madwifi STA to 1 madwifi AP, exchange the same > linux-2.4.22.tar.bz2 between the STA and the AP: badly works. The STA > seems to randomly revert to SCAN thus breaking the connection. I have > not really investigated exactly what happens and why it happens. > > I hope this will work for as many people as possible. This is hopefully > the last release before I start checking this into a CVS branch. > > regards, > Mathieu |
From: Mathieu L. <Mat...@so...> - 2003-11-06 09:46:05
|
On Thu, 2003-11-06 at 10:25, Jean Lorchat wrote: > hi ! > > thanks for reactivity =) > > could you just swap line 1399 and 1398 in if_ath.c ;-) ? gah, too much C++ recently :) Mathieu > > bye > Jean > > > Mathieu Lacage wrote: > > hi all, > > > > Here is a _tested_ release: > > ftp://ftp-sop.inria.fr/dream/Outgoing/madwifi-9.tar.gz > > ftp://ftp-sop.inria.fr/dream/Outgoing/port.notes-9 > > What has been tested: > > 1) connect to an internet-connected AP, download through ftp.lip6.fr > > linux-2.4.22.tar.bz2: 600KB/s. > > 2) connect 2 madwifi STAs to the same AP, exchange between the 2 STAs > > through the AP with UDP the same linux-2.4.22.tar.bz2: 285KB/s. > > 3) connect 1 madwifi STA to 1 madwifi AP, exchange the same > > linux-2.4.22.tar.bz2 between the STA and the AP: badly works. The STA > > seems to randomly revert to SCAN thus breaking the connection. I have > > not really investigated exactly what happens and why it happens. > > > > I hope this will work for as many people as possible. This is hopefully > > the last release before I start checking this into a CVS branch. > > > > regards, > > Mathieu -- Mathieu Lacage <mat...@so...> |
From: Gerald B. <gbr...@do...> - 2003-11-06 15:25:17
|
On Thu, Nov 06, 2003 at 10:13:53AM +0100, Mathieu Lacage wrote: > 3) connect 1 madwifi STA to 1 madwifi AP, exchange the same > linux-2.4.22.tar.bz2 between the STA and the AP: badly works. The STA > seems to randomly revert to SCAN thus breaking the connection. I have > not really investigated exactly what happens and why it happens. This is the behavior I described a few days ago. The hardware generates a BMISS interrupt which causes the driver to think that it lost the access point and it starts scanning for a new one. I have heard that some APs will fail to output beacons occasionally in high traffic situations. There is a hal call to set the threshhold of how many missed beacons occur before triggering the interrupt, but tweaking this didn't appear to do anything. One thought is that a counter of missed beacons isn't getting reset when a beacon is seen (the hal calls seem to imply that there is some sort of reset of a counter, but it's never called). -- Gerald |
From: Mathieu L. <Mat...@so...> - 2003-11-06 17:25:35
|
hi gerald, For the record, I have seen this same problem is straight CVS madwifi drivers. On Thu, 2003-11-06 at 16:25, Gerald Britton wrote: > On Thu, Nov 06, 2003 at 10:13:53AM +0100, Mathieu Lacage wrote: > > 3) connect 1 madwifi STA to 1 madwifi AP, exchange the same > > linux-2.4.22.tar.bz2 between the STA and the AP: badly works. The STA > > seems to randomly revert to SCAN thus breaking the connection. I have > > not really investigated exactly what happens and why it happens. > > This is the behavior I described a few days ago. The hardware generates a > BMISS interrupt which causes the driver to think that it lost the access Yes, it seems that this is what happens. printking does not help because it seems all the driver debugging is thrashed (don't ask me why) but I really think that the interupt is generated. Maybe I should try the IBM probe code to make this is the case... > point and it starts scanning for a new one. I have heard that some APs will > fail to output beacons occasionally in high traffic situations. There is a Here, I am running a madwifi AP so I'll look into trying to get information on beacon generation failures. > hal call to set the threshhold of how many missed beacons occur before > triggering the interrupt, but tweaking this didn't appear to do anything. > > One thought is that a counter of missed beacons isn't getting reset when > a beacon is seen (the hal calls seem to imply that there is some sort of > reset of a counter, but it's never called). yes. You seem to be right. Anyone know when we are supposed to call ah_resetStationBeaconTimers ? Mathieu -- Mathieu Lacage <mat...@so...> |
From: Tino K. <tin...@gm...> - 2003-11-26 22:05:30
|
On Thu, Nov 06, 2003 at 10:13:53 +0100, Mathieu Lacage wrote: > hi all, > > Here is a _tested_ release: > ftp://ftp-sop.inria.fr/dream/Outgoing/madwifi-9.tar.gz > ftp://ftp-sop.inria.fr/dream/Outgoing/port.notes-9 Where is the archive? It seems to be disappeared. Regards, Tino |
From: Sam L. <sa...@er...> - 2003-11-26 22:52:47
|
On Wednesday 26 November 2003 02:04 pm, Tino Keitel wrote: > On Thu, Nov 06, 2003 at 10:13:53 +0100, Mathieu Lacage wrote: > > hi all, > > > > Here is a _tested_ release: > > ftp://ftp-sop.inria.fr/dream/Outgoing/madwifi-9.tar.gz > > ftp://ftp-sop.inria.fr/dream/Outgoing/port.notes-9 > > Where is the archive? It seems to be disappeared. The code is in CVS now; checkout the WLAN2 branch. Sam |
From: Mathieu L. <Mat...@so...> - 2003-11-27 06:57:42
|
hi tino, I apologize for this inconvenience: it seems cron scripts run on this ftp server to delete all 'old' files (namely, files older than 10 days). The code is currently in CVS in the WLAN2 branch: cvs -d:ext:cvs.sf.net:/cvsroot/madwifi -z9 co -r WLAN2 madwifi regards, Mathieu On Wed, 2003-11-26 at 23:04, Tino Keitel wrote: > On Thu, Nov 06, 2003 at 10:13:53 +0100, Mathieu Lacage wrote: > > hi all, > > > > Here is a _tested_ release: > > ftp://ftp-sop.inria.fr/dream/Outgoing/madwifi-9.tar.gz > > ftp://ftp-sop.inria.fr/dream/Outgoing/port.notes-9 > > Where is the archive? It seems to be disappeared. > > Regards, > Tino > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Madwifi-devel mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-devel -- Mathieu Lacage <mat...@so...> |