Ben, On Thu, Jan 7, 2016 at 9:33 AM, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: > Could be > a power-save issue perhaps. That was our thought, too. Particularly, since if there is steady traffic (at least a ping every 8 seconds), the problem does not appear to occur. However, the rtl8192cu doesn't support power-saving mode and in any case, we made sure it's off: # iw wlan0 get power_save Power save: off > I assume you have sniffed to see if any frames are going out on the air during the time of trouble? No, I'm not actually sure how I'd do that. The site we see this most frequently with is remote and we don't have any special WiFi packet sniffer. > If correct packets go out on the air and AP doesn't answer, then likely AP > problem. Not likely an AP problem, since we're seeing this with multiple APs of different brands etc. > If pkts don't get on the air, then check to see if they at least get to > the driver. Yeah, that should be easy to do, I suppose. We had rtl8192cu debugging turned on before but at that time it didn't help. > If they don't get to the driver, then probably it is a kernel/stack issue. > > If they get to the driver but not on the air, then NIC and/or it's firmware > and/or the driver is likely the culprit. Thanks for your thoughts! --david -- eGauge Systems LLC, http://egauge.net/, 1.877-EGAUGE1, fax 720.545.9768 -- 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
