FVS336Gv3 with Virgin SuperHub 2?

Have you tried running "Auto Detect" on the Broadband ISP setting? Does it tell you it detected DHCP?

Nhellie26 wrote:
Have you tried running "Auto Detect" on the Broadband ISP setting? Does it tell you it detected DHCP?

Hi Nhellie26,

Thanks for the quick response. Yes, I tried Auto Detect but it said "No service detected". I also tried setting WAN2 to be the Primary WAN and using that instead, with the same result.

Regards,

Jolyon

Well, that seemed to be the issue. It is not detecting that you have a connection at all. Have you also tried swapping cables, does the WAN port lit up when you are connected to it?

Hi jolyoncox,

Try this: Power off both the FVS336Gv3 and the Virgin Media SuperHub 2. After 5 seconds, power on first the Virgin Media SuperHub 2 and wait for it to initialize. Then, power on the FVS336Gv3 and wait until it initializes . Then, check if you can now go online through the FVS336Gv3.

Do you have a static WAN IP Address from your ISP?

Nhellie26 wrote:
Well, that seemed to be the issue. It is not detecting that you have a connection at all. Have you also tried swapping cables, does the WAN port lit up when you are connected to it?

Yes, that's what I thought, but I was using the same cable as for the FVS318 and simply moving it between routers - and yes, the port was lighting up. I tried using a different cable, but it made no difference.

However, the problem is now solved - see below.

Thanks for your help.

Regards,

Jolyon

Sasword wrote:
Hi jolyoncox, Try this: Power off both the FVS336Gv3 and the Virgin Media SuperHub 2. After 5 seconds, power on first the Virgin Media SuperHub 2 and wait for it to initialize. Then, power on the FVS336Gv3 and wait until it initializes . Then, check if you can now go online through the FVS336Gv3. Do you have a static WAN IP Address from your ISP?

Hi Sasword,

That's what I've been doing all along, per the instructions which came with the SuperHub - and the same when switching back to the FVS318. However, after one of many changeovers it suddenly started working!

I had a response in another forum which I think explains it. Apparently the modem locks itself to the MAC address of the router, and you either have to spoof the MAC address or unlock it by waiting much longer before rebooting. I think I must have accidentally done that, so it worked and all is fine now.

The old modem didn't lock itself to the MAC address, so it never occurred to me that the SuperHub would - there is precious little documentation and in modem-only mode there are no settings to see.

BTW, the WAN IP address is in principle dynamic, though in practice it never changes. However, I don't rely on that and use DynDNS for incoming stuff - the FVS336Gv3 knows how to update that.

Thanks for your help.

Regards,

Jolyon

jolyoncox wrote:

Apparently the modem locks itself to the MAC address of the router, and you either have to spoof the MAC address or unlock it by waiting much longer before rebooting. I think I must have accidentally done that, so it worked and all is fine now. The old modem didn't lock itself to the MAC address, so it never occurred to me that the SuperHub would - there is precious little documentation and in modem-only mode there are no settings to see.

After reading your problem, this was going to be my guess. Typically, I will clone the MAC address from the old router when swapping routers--even when it is not MAC bound. This allows you to keep your old dynamic IP address even when swapping routers. ;)

this is a pretty common thing, I haven't though of it at first though. Good thing jolyoncox got it working :)

Nhellie26 wrote:
this is a pretty common thing, I haven't though of it at first though. Good thing jolyoncox got it working :)

I've bashed my head against a brick wall for 6hrs once when I first ran into this issue. That experience helped me remember. :D

Hmmm...I spoke too soon!

It all worked fine until we had a power cut - since the power came back, the 336G has been completely unable to obtain a lease from the SuperHub, even after power-cycling both in the right order (several times) and then spoofing the MAC address to the same as the FVS318 and trying again.

I've just tried again with an FVS336Gv2 (also on the latest firmware, and also with a spoofed MAC address) with the same result. Meanwhile the FVS318 behaves perfectly (if slowly), so I guess it must be a router setting somewhere. Scratching my head for ideas...any suggestions appreciated.

What I really want is a proper modem instead of all this SuperHub rubbish, so I can actually see what the modem is doing!