Superhub Technical question!

fixerman · 08-05-2011, 08:13

My knowledge of modem technology is just about zero, so my question is, why on occasions can I not get a wireless device to gain Internet access, without rebooting the modem when other wireless devices have Internet with no problem. For example this morning I could not get Internet access on my iPad but no problem on my iPhone. A reboot of the modem and all was well again. This has happened on several occasions.

I am on 30mb Superhub!

Nopanic · 08-05-2011, 08:22

uh oh ..

Ignitionnet · 08-05-2011, 08:29

Quote:

Originally Posted by fixerman

I am on 30mb Superhub!

The bit I've put in bold is all you need to know. It's by a mile the worst piece of hardware I've used at home having been online at home on broadband connections for over 10 years across 6 addresses, 4 VM connections all with different modem and router and 5 ADSL providers, with different CPE for each.

fixerman · 09-05-2011, 07:31

Quote:

Originally Posted by Ignitionnet

The bit I've put in bold is all you need to know. It's by a mile the worst piece of hardware I've used at home having been online at home on broadband connections for over 10 years across 6 addresses, 4 VM connections all with different modem and router and 5 ADSL providers, with different CPE for each.

Well! That's not a very encouraging response. I was hoping for a more technical explanation why I was having this experience.

Nopanic · 09-05-2011, 07:33

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

Ignitionnet · 12-05-2011, 17:01

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.

pip08456 · 12-05-2011, 17:14

Quote:

Originally Posted by Ignitionnet

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.

I thought they were Monkeys!

R27 is supposed to be released beginning of June.

Watch out for R28, R29 and R30!

craigj2k12 · 12-05-2011, 17:50

Quote:

Originally Posted by pip08456

Watch out for R28, R29 and R30!

I cant see them getting R27 right, so queue R28, ........ , R45 etc.

all they need to do is disable the router so the device becomes a standalone modem, and I bet you they do something wrong in the firmware like once its in bridge mode you cant get it out, or cant even access the web interface

they may even go to a higher level of stupidity like make it so the superhub cant receive any further firmware updates lol that would be funny, having thousands of superhubs which need replacing

Stephen · 12-05-2011, 18:36

That is just a silly post and wouldn't happen at all.

craigj2k12 · 12-05-2011, 18:40

Quote:

Originally Posted by Stephen

That is just a silly post and wouldn't happen at all.

on the face of it, it sounds silly, but if we take a look at whats happened in the last couple of firmwares!

bridge mode should be an easier thing to do, compared with the stuff they tried (and failed) with the other firmwares. As we saw with SSH enabled, we managed to get a bridge mode working pretty simply, just disabling the router functions etc, all they have to do is put those commands behind a couple of radio buttons and the opposite commands for turning the router back on. I can see that they are taking their time with the bridge mode firmware and they are probably making sure that it is perfect before rolling it out, one would hope!

Ignitionnet · 13-05-2011, 19:17

Given that this thing was on, what, R20 in January and we're looking at R27 in, err, May, you can forgive the cynicism.

pip08456 · 13-05-2011, 19:32

I never consider you to be a cynic Igni, that would be silly!

Nopanic · 13-05-2011, 23:01

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

Quote:

Originally Posted by Ignitionnet

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 ----------

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.

See

Ignitionnet · 14-05-2011, 08:21

Quote:

Originally Posted by Nopanic

See

zekeisaszekedoes · 16-05-2011, 12:26

Most wireless problems are caused by the 300Mbps mode on the super hub (I'm going to stop title casing it from now on), which is unstable and can cause lockups requiring a reboot, especially when wirelessly transferring large files.

Put it on 145Mbps mode and it'll work more reliably, however if you have a 100Mb broadband service this now means any wireless devices won't be able to make the most of it, which is odd because of course part of the reason it exists is so all devices can make use of the flagship 100Mb tier whether they are wired or wireless.