Hi Johannes, > > The connection monitor currently relies on probe requests paired > > with probe responses to ensure that a connection is alive. This is > > fragile in some environments where probe responses can get lost. > > When we receive beacons we can also consider the connection to be > > alive, so cancel connection poll instance when we receive a beacon. > > > > The debug message "cancelling probereq poll due to a received beacon" > > is removed as part of this change as this case is hit very often after > > the above change and debug log receives significant number of these messages. > > Not doing that was actually intentional -- we want to know whether or > not the connection is working both ways, not just whether we can receive > frames. This can certainly be improved, but I'm not sure this is the > best approach. this patch might be a band-aid and needs improvement or a total different solution, but it does help my disconnect problems. It makes my connection fully stable again. So it is not a wrong approach in general, because otherwise I have to be always close to me AP. And then using WiFi is bloody pointless since I could just put an Ethernet cable into the wall socket directly. Regards Marcel -- 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