
Originally Posted by
azazel1024
No, it is not a router issue, or at least not directly. Rebooting the router/access point when I have "limited connectivity" does nothing. Only disconnecting and reconnecting manually on the T100 does it, or a reboot if the netstack has locked up. It of course might be an issue between my router/access point and the Broadcom SDIO adapter in the T100, but this isn't simply that it is failing to connect, or invalid IP or something like that, either something my router/access point are doing is causing the broadcom drivers on my T100 to lock up, or else it is something that the broadcom drivers are doing completely on their own.
Since it has happened on several different networks, I suspect a bit of the later more than the former. However, I have seen lots and lots of problems with different broadcom adapters and a variety of routers. In general, broadcom based routers and broadcom adapters almost always seem to work fine. Broadcom adapters and OTHER chipset routers sometimes have problems (but not always). A good example is the TP-Link C7 Archer, it seems to work fine with everything, except some Broadcom 802.11ac clients, especially the ones in the Apple macbook pro seems to have a horrible time with it. Now, it might be that the router is doing something "wrong" not standards complaint, but since all OTHER chipset based clients seem to have no problem with it...
It sounds like a two way street at least. Broadcom seems to have an issue with its hardware/drivers in a lot of recent clients, but it also is possible that it is a lot of router manufactuers also have an issue in their firmware/hardware that is triggering the issue. So the question is...who is at fault?
At anyrate, it seems to be going okay now. I still get limited connectivity, but its easy to just disconnect and reconnect right now and that fixes it 9 out of 10 times. I can deal with having to reboot once a week because it won't reconnect.
On a seperate issue, something I've noticed with my T100 is that it does NOT like 40MHz mode if you are using an "edge" channel. I discovered this because a new access point I added in to my network for outdoor coverage, for some random reason, will NOT work on Channel 1. Both my T100, my laptop and my phone can connect to that AP on channel 1 (at least in 20MHz mode), but if I try to transfer a file, do a speed test, that sort of thing, it'll go at 1-2MB/sec for 500-2,000KBs and then stop...10-15s later, another 500-2000KBs, then stop and so on. Channel 2, same result. channel 11, worked great! No stuttering/locking and smooth, fast sailing.
So I switched my living room access point from Channel 6+10 40MHz to Channel 1+5 (and also my basement router to Channel 11, so no channel overlap anywhere for where routers have overlapping coverage). That was a couple of weeks ago. The laptop ran great on everything, but I just actually tested the T100, since I haven't had a reason to transfer any files to/from in a couple of weeks, just general internet/email/gaming kind of stuff. Well, on Channel 1+5, it was going pretty slow. Hitting 6.5MB/sec peak. This is over several tests, that is a lot slower than before. So I tried switching to 7+11 to see if maybe I could switch my other APs to channel 2 (to see if the outdoor one would function properly on that channel) for no overlap. Worse, it would transfer at 2-3MBsec and stutter like crazy. No issues on my iPhone or laptop. Smooth sailing on all of these channels with no noticable speed difference between then.
I finally tested on channel 2+6 and it worked great again. Back to the 8-9.5MB/sec I had been getting before. So, cool beans, its all working properly now with no overlap, but just...odd.
I mean very, very, VERY bizzare.