VM Router Help with Cisco Dual Wan Setup - Page 2

dfhage · 22-12-2015, 09:51

As it turns out VM had changed me from routed subnet to single static IP at my request(I certainly did not), so it was never going to work ! Funnily enough the date uncannily lined up with a frank exchange of views with customer service about the poor connection uptime !
Engineer sorted this morning, so at the moment all is well.

ccarmock · 22-12-2015, 10:16

Both are the in 'static' ranges for VM Business, so it depends which they have assigned to your account. Do you have a login ID you have to enter into he business section of the Superhub? I don't mean to access it's web interface - but when you get into that in the business settings?

This is the account that the SH uses to connect with VMB systems to form your PPP/L2TP tunnel to map the static IP addresses to the SH.

If this wasn't setup correctly to start with I suspect the SH IP isn't fixed at the moment.

If you connect a PC to one of the superhub Ethernet ports and ensure DHCP is enabled on the PC do you get a 192.168.x.x address?

If so visit http://whatsmyip.org to see what public address you have.

Also check the SH interface in the business section for a login & password - both should have been given to you when you setup your account. The engineer can get them for you, as can support.

dfhage · 22-12-2015, 10:30

I have a user name and password from VM that had been entered into the SH , along with a Static IP and subnet ending 240, these were done during install by the engineer a while ago.

The same engineer came today, made a call to get the original static subnet back, and 20 minutes later we were back in business.

I now have a working router (losing connections not withstanding)
I have no idea why VM took it upon themselves to "downgrade"to a single static IP (with presumably NAT), as this completely hobbled my new Dual Wan Router configuration.
Now just waiting till next Feb !

ccarmock · 22-12-2015, 10:49

Sounds good - ok you have the routed subnet option which as mentioned, is the same setup I have and found in this mode to be stable. I will be interested to know if you find it stable now.

If not, maybe invest £10 in a plug-in time-clock to do a once daily reboot of the Superhub. In some cases that seems to avoid the issue. Shouldn't be needed of course!

My guess is that there was some major issue or vulnerability with the previous firmware as they refuse to roll back to a version that was stable, and had been in service for well over a year. The new version was pushed out as 'bug fixes' and to add SIP ALG support.

Hopefully the new device will be a lot better.

One very disappointing thing here is the lack of communication from VMB on this issue.