Superhub : Virgin Business Superhub now has Modem Mode

[qasdfdsaq]

Interesting.

That's quite possible, but largely because said issues may be more to do with the CPE having to handling the origination/termination of the PPP session (i.e. extra router functions) than just passing it through.

Encapsulating/de-encapsulating 150Mbps+ of traffic on a <1Ghz MIPS CPU can be an intensive task, especially if there's encryption involved.

[ccarmock]

It could be yes. So I think there are two issues to resolve - this performance issue and the need for firmware for the SH2AC to support the configuration needed for the Fixed IP services.

[rhyds]

Originally Posted by ccarmock

You know I have a feeling that the original firmware did show the IP address of the tunnel destination, I have looked to see if I kept a screen shot but can't find one.

I am referring to the original firmware not the .06 release prior to the bugged .13

I'm still on .06 if you want me to take a look

[ccarmock]

It was the release prior to .06 that I seem to remember a server address being displayed.

[johnnyboyleeds]

Just a quick thought on the L2TP tunnel endpoint. Does anyone who has had their business hub replaced still have the old one to possibly check for the tunnel endpoint?

[huwjr]

Hey all,

I have left our Superhub online since my last post, I have checked it every couple of weeks since then with the following methods:
Success - Ping public IP of superhub from www
Success - Log into superhub gui from www and LAN
Failed - Ping local IP of superhub from LAN
Superhub GUI - Ping connected device static IP
Superhub GUI - Shows no connected devices

However, on Sat Jan 31 our superhub rebooted of it's own accord and our downstream router was suddenly accessible again and hasn't dropped out since, it hosts an old and superseded PPTP VPN but this enables us to monitor the upstream and downstream routers separately and see the disparity between the Virgin Superhub being up and a usable internet connection.

My director has been chasing refunds that they promised (but haven't deilvered on, surprise surprise), he asked for an update on the 'faulty firmware' and they said that they had rolled out a fixed version to a few superhubs. Now, our firmware is still on the same .13 version but all of the problems we had before have vanished and it's all a bit too good to be true.. do you think they're also stupid enough to roll out a fix on the same version number?

I'm yet to test "Modem Only Mode" again, and I'm in no great rush to do so, but has anyone else suddenly found their Superhub is usable to some degree again?

[nickgoldman]

Ours SH is not locking up as much, however it is rebooting itself randomly every 1-2 days (does anyone else see this?). I wonder if as a temporary fix VMB have put in place a patch to reboot the SH if VM or the SH detect a condition that will cause the device will lock up.

[drsox]

Since about November the company I support has had almost daily incidents of the SuperHub going strange.

The symptom is the LAN side stops responding to ARP requests. So their machines can't ping or contact the SuperHub. The SuperHub is still responding to pings and it's web interface on the WAN (Cable) side.. I have to remote into it and reboot it or ask them to power cycle the SuperHub - then things return to normal.

It's really getting annoying... so I started searching for bridge / modem only mode instructions and stumbled across this thread. I'm still unsure what the procedure is.
Anyone have any simple instructions? They have a single static IP address and a SuperHub that offers Modem Only mode (and provides some PPP details on that same screen).
Do they need to use these PPPoE details or just set their ethernet router to DHCP?

Tom - www.mouselike.org

[huwjr]

No offense drsox but if you had bothered to read the thread you'd know it's broken.

Originally Posted by drsox

Since about November the company I support has had almost daily incidents of the SuperHub going strange.

The symptom is the LAN side stops responding to ARP requests. So their machines can't ping or contact the SuperHub. The SuperHub is still responding to pings and it's web interface on the WAN (Cable) side.. I have to remote into it and reboot it or ask them to power cycle the SuperHub - then things return to normal.

It's really getting annoying... so I started searching for bridge / modem only mode instructions and stumbled across this thread. I'm still unsure what the procedure is.
Anyone have any simple instructions? They have a single static IP address and a SuperHub that offers Modem Only mode (and provides some PPP details on that same screen).
Do they need to use these PPPoE details or just set their ethernet router to DHCP?

Tom - www.mouselike.org

[drsox]

Originally Posted by huwjr

No offense drsox but if you had bothered to read the thread you'd know it's broken.

I did and I don't really see that - I see some people saying that it works fine and many people use bridge mode, some people saying you need to use PPPoE and some saying you need to use PPTP / L2TP.

Personally I think that the PPPoE method is the most likely method but.. this, being a help forum?, I thought I would check if someone had some advice before I potentially wasted my time and annoyed those at the company while breaking the internet to attempt potentially futile changes.

Tom - www.mouselike.org

[qasdfdsaq]

Hey... mouselike.org, there's something I haven't heard of in a while... I used to use your SIP testing server all the time!

Anyway. Whether the Superhub works for you is rather hit-and-miss. There is no universally reliable way to make it work for someone if it is currently causing issues on the business service.

Bridge mode has recently appeared on the Superhub business firmware but is still officially unsupported. I'm not aware of anyone having actually used it successfully. It would, however, be a universally reliable way of resolving the Superhub's problems if it did work, like on the residential service.

VM don't use PPPoE on cable. The L2TP thing is relevant only if you have a routed, fixed-IP subnet from VM, as that is how the service works. Theoretically if you put the modem in bridge mode you would have to create the tunnel yourself to establish connectivity. To date however, I'm not aware of anyone actually using it successfully. It is merely theoretical, given that thus far VM have refused to give out the connection details we need to actually set up a tunnel.

[drsox]

Originally Posted by qasdfdsaq

Hey... mouselike.org, there's something I haven't heard of in a while... I used to use your SIP testing server all the time!

It is still going.. Good tool to test with. I regularly use it via the PSTN number when trying to fix phone issues.

Shame about bridge mode. The office with the issue is staffed 24/7 and their broadband is pretty critical.

Testing settings _would_ have been fine if someone had not cancelled the Fax line last week, taking out the backup ADSL they had so I can't easily test without making the workers angry until the Backup DSL has been reinstated.

Tom - www.mouselike.org

[rhyds]

As I've mentioned before, we're using the standard superhub with the .06 firmware to supply a routed 5 Static IP subnet and its stable.

[huwjr]

Still going strong since the suspicious restart... there may be hope for some of you yet!

Originally Posted by huwjr

Hey all,

I have left our Superhub online since my last post, I have checked it every couple of weeks since then with the following methods:
Success - Ping public IP of superhub from www
Success - Log into superhub gui from www and LAN
Failed - Ping local IP of superhub from LAN
Superhub GUI - Ping connected device static IP
Superhub GUI - Shows no connected devices

However, on Sat Jan 31 our superhub rebooted of it's own accord and our downstream router was suddenly accessible again and hasn't dropped out since, it hosts an old and superseded PPTP VPN but this enables us to monitor the upstream and downstream routers separately and see the disparity between the Virgin Superhub being up and a usable internet connection.

My director has been chasing refunds that they promised (but haven't deilvered on, surprise surprise), he asked for an update on the 'faulty firmware' and they said that they had rolled out a fixed version to a few superhubs. Now, our firmware is still on the same .13 version but all of the problems we had before have vanished and it's all a bit too good to be true.. do you think they're also stupid enough to roll out a fix on the same version number?

I'm yet to test "Modem Only Mode" again, and I'm in no great rush to do so, but has anyone else suddenly found their Superhub is usable to some degree again?

[ccarmock]

Called sales again - they are now saying first half of this year for 152 Mb/s with fixed IP address