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 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
