Quote:
Originally Posted by Nopanic
There isn't really one, looking at it from a support point of view, if one piece of equipment is failing, then its that, that's at fault.. (i.e the failing wireless device) but as its the Superhub your not going to get much more from this forum  |
The iPad was just an example and the impression given was that the affected client device varies.
So let's look at it from the support perspective rather than a defending the Superhub perspective.
What is the common link in the faults? The Superhub.
What remedial action resolves it? Power cycling the Superhub.
So let's look from a technical support perspective at what a reload of the Superhub will do.
Will it reset the wireless adapter on the affected client device? No.
Will it reset the IP stack of the affected device and make it perform DHCP transactions differently if it is getting wireless association with the Superhub? No.
Indeed will it have any effect at all on the affected client device? No.
Will it reset the wireless adapter on the access point? Yep.
Will it reset the IP stack and DHCP server on the access point? Yep
Will it clear the RAM of the access point clearing any software bug causing problems with either wireless or higher protocol stack functionality? Yep.
---------- Post added at 18:01 ---------- Previous post was at 17:59 ----------
Quote:
Originally Posted by fixerman
Well! That's not a very encouraging response. I was hoping for a more technical explanation why I was having this experience.  |
You'd need to ask the tools who write the Superhub firmware for a more technical explanation. It seems to be getting more software updates than Windows so shouldn't be too long before you see R27 rushed out.