Do you remember what version kernel this was fixed in? I can update the nodes to at least this version and see if it helps...
On my setup, I am not seeing ANY probes from the ath5k nodes at all. If I start a MadWifi node and the ath5k nodes join it, then bring down the MadWifi node, the ath5k nodes ALL start beaconing... Cheers, -- Jonathan Guerin On Wed, Jul 21, 2010 at 9:16 AM, Bob Copeland <m...@bobcopeland.com> wrote: > On Wed, Jul 21, 2010 at 10:11:14AM +1200, Derek Smithies wrote: >>> Then on the other machine (Vista) I just located 'myibss' (so beacons >>> are working) and selected it, then successfully pinged 192.168.10.1. >> Wrong. >> If the other machine located your node, then one of the four statements >> is true: > > Ok, fine, I just set up a monitor interface and I see beacons > (and probe responses) for my setup on that channel. > >> A scan should not be necessary - if both ends are put on channel 2462- a >> scan should not be required - there is no channel changing. Yet - my >> colleague noted a scan helped nodes to associate. > > There was a bug in older kernels that wouldn't fully configure the > beacons until after a reset, which scanning happens to do. It's > possible something similar is going on. > > Also, scanning might open a previously passive channel because we might > get lucky and receive a beacon from another node on it. The 'iw phy > phy0 info' can show this kind of thing. > > -- > Bob Copeland %% www.bobcopeland.com > > _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
