On Wed, 2013-03-27 at 12:08 -0700, Alex Romosan wrote: > > Are you sure this only happens after suspend/resume? It seems like it > > would always happen? At least if there was a beacon in the scan results > > already, which should probably always be the case... > > no, it always happens, but i only noticed it after suspend/resume. when > i suspend i do an ifdown (because i haven't figured out a way to > convince my new access point not to drop idle connections) and then i do > an ifup to reconnect on resume. when i'm testing it now, i just take the > network down and then try to bring it back up. Ah, right, I guess I'm a little surprised it ever works at all ... We'll see in the log though. johannes -- 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
