Thread: RE: [Madwifi-devel] bmiss problem
Status: Beta
Brought to you by:
otaku
From: Henry Q. <he...@am...> - 2003-11-20 16:28:05
|
Gerald, A few days ago I modified the ath_bmiss_tasklet, so when bmiss int = happens, instead of going to scan immediately, it goes to assoc state = and sends out an assoc req, it times out in 5 seconds if there's no = response from AP and then goes to scan state. If you still have bmiss problem try the latest CVS (main branch), see if = it works. Henry > -----Original Message----- > From: Gerald Britton [mailto:gbr...@do...]=20 > Sent: Thursday, November 20, 2003 10:38 AM > To: Mathieu Lacage > Cc: madwifi > Subject: Re: [Madwifi-devel] bmiss problem >=20 >=20 > On Thu, Nov 20, 2003 at 03:35:27PM +0100, Mathieu Lacage wrote: > > 1) I never get a bmiss interrupt. >=20 > In times of high rate data reception I endup seeing bmiss interrupts. >=20 > > 2) I get data from the rx_tasklet and I forward it to the=20 > networking=20 > > stack. >=20 > In times of high rate data reception, I stop seeing the=20 > rx_tasklet being called, a few moments later I see a bmiss interrupt. >=20 > > 3) my dhclient does not seem to be receiving any DHCPACK packet >=20 > If it's scanning and not associated this makes sense, also if=20 > it's gone to the bad place as mine does (rx stops happening)=20 > this makes sense. >=20 > > 4) ethereal seems to be receiving all DHCPREQUEST and DHCPACK=20 > > packets >=20 > ethereal on the same machine? or ethereal on an independant machine? >=20 > > 5) the algorithm my dhclient follows when deciding=20 > whether or not to=20 > > shut down the interface because its lease has expired seems to be=20 > > pretty > > weird: it seems to be trying really hard to survive in case the DHCP > > server is down so it takes a lot of time and a lot of=20 > randomness to shut > > down the network interface. > > 6) all transmission ceases when the dhclient shuts down=20 > the network > > interface. (as expected) > > 7) sometimes, it looks like the network interface comes=20 > back to life > > more or less randomly when it is down. >=20 > I've determined that I really hate dhclient. Are you using=20 > Red Hat 9 or Fedora Core 1? I seem to endup with a pile of=20 > dhclient processes which all have a habit of conflicting and=20 > bouncing the interface a lot. At one point I did up my own=20 > network-scripts which are a lot nicer for debugging purposes.=20 > Hopefully I'll revive those soon. >=20 > You say that you're looking for your "revert to SCAN mode=20 > problem" Where in here are you seeing it go into scan mode? >=20 > -- Gerald >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program.=20 > Does SourceForge.net help you be more productive? Does it=20 > help you create better code? SHARE THE LOVE, and help us=20 > help YOU! Click Here: http://sourceforge.net/donate/=20 > _______________________________________________ > Madwifi-devel mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-devel >=20 |
From: Gerald B. <gbr...@do...> - 2003-11-20 17:16:16
|
On Thu, Nov 20, 2003 at 11:28:00AM -0500, Henry Qian wrote: > Gerald, > > A few days ago I modified the ath_bmiss_tasklet, so when bmiss int happens, > instead of going to scan immediately, it goes to assoc state and sends out an > assoc req, it times out in 5 seconds if there's no response from AP and then > goes to scan state. It ends up falling through into the scan state. I think there's something more going on here where the hardware gets into a bad state and stops receiving anything. The process of scanning seems to knock it free. -- Gerald |
From: Mathieu L. <Mat...@so...> - 2003-11-21 07:59:55
|
On Thu, 2003-11-20 at 17:28, Henry Qian wrote: > Gerald, > > A few days ago I modified the ath_bmiss_tasklet, so when bmiss int happens, instead of going to scan immediately, it goes to assoc state and sends out an assoc req, it times out in 5 seconds if there's no response from AP and then goes to scan state. > > If you still have bmiss problem try the latest CVS (main branch), see if it works. I have done something similar in my local copy but this did not change anything. Arguably, I have difficulty seeing how my problem relates to gerald's. Mathieu -- Mathieu Lacage <mat...@so...> |