Quote:
Originally Posted by naysan19
Hi all,
This may have already been discussed in another thread but I thought I would share anyway.
To give some background: We have a 50M connection with 5 static IPs (routed subnet) and a SuperHub 1 which has caused nothing but problems since day one (literally)! As learnt from others in this forum, modem mode is a no go - no settings would work so I set up the SH in router mode and used the second static IP on our Draytek router. Even in this set up the connection would go down at least once every 1-3 days, either the unit would need to be restarted manually or I was able to connect to the WAN IP of the unit and restart it, for some reason it was usually that the unit didn't know anything was connected to the LAN port which was the problem - hence no connection on site but the GUI was reachable off-site using the WAN IP (if it was still responsive).
I have been watching the forum on news of the SH3 and called Virgin Media last week to complain again and request for a SH3 which I was previously told would be given for free to suffering businesses with a SH1. The adviser explained that this offer is no longer valid as they have a new firmware version for the SH1 - BUS_V2.37.17 which was applied remotely a few days later.
Our SH1 has been running for over 8 days now without any problems! No connection drops, no random restarting and the GUI has been responsive every day. Hopefully this firmware makes the SH1 stable.
I'm pretty sure I've never seen the system up time above 4 days until now.
One interesting note is that there is no longer an option to put the unit into Modem mode and the GUI is slightly different.
So, if you are still having problems with the SH1 in router mode - give Virgin Media a call to apply the new firmware.
We'll have to wait until the SH3 supports multiple static IPs (routed subnet) before we can upgrade to the new speeds.
|
I just called VMB and the guy I spoke with didn't know anything about it. I think I am best calling up on Monday and asking.
If they have finally fixed this I will be very pleased as this has been ongoing for over a year.
is there any chance of a screenshot of the 2.37.17 release?