Superhub Superhub Firmware Beta Test - Page 47

Neo-Tech · 03-08-2011, 15:43

Just got R29 pushed to my Hub. Wireless performance is still the same, and the only change I see is a Modem mode page.

Sirius · 03-08-2011, 15:50

Quote:

Originally Posted by Neo-Tech

Just got R29 pushed to my Hub. Wireless performance is still the same, and the only change I see is a Modem mode page.

Was that as part of the beta

Helix · 03-08-2011, 15:54

At last, typical VM though didn't think to tell us in advance - just waited until we discovered it.

Sirius · 03-08-2011, 15:55

Quote:

Originally Posted by Helix

At last, typical VM though didn't think to tell us in advance - just waited until we discovered it.

Is it part of the beta ?

jinxed · 03-08-2011, 15:55

Had it pushed to my hub to, but i did apply to be part of the beta test.

HD Boy · 03-08-2011, 15:56

i also just got R29 pushed to my Hub. yes that as part of the beta

Helix · 03-08-2011, 16:04

Quote:

Originally Posted by Sirius

Is it part of the beta ?

I am a Beta tester, not sure if they have rolled it out wider. They haven't updated the message in the now closed Beta forum. We were meant to be moved to a new forum as R29 was rolled out.

AndyCalling · 03-08-2011, 16:22

Can I ask, when you enable modem mode does it resync the modem connection? I ask because mine is very stable for most things but can take an hour or more to resync and the Superhub always reboots when I try to control my Dad's computer through Remote Assistance. I shall be wanting to drop to modem mode to do RA and then back to router mode when finished. There is no reason why the modem should reboot if we're just switching the router on and off but I thought I'd just check.

Can you confirm for me?

03-08-2011, 16:25

Yes it forces a restart and you get a fresh public IP.

kwikbreaks · 03-08-2011, 17:19

Quote:

Originally Posted by AndyCalling

There is no reason why the modem should reboot if we're just switching the router on and off

It has to at least get a new DHCP lease because the MAC the modem section sees has changed from the internal router to that of the PC in port 1. It may or may not resync.

AndyCalling · 03-08-2011, 18:08

I have two network ports and so can have the second one set up with the same MAC as the router provides to the modem and switch ports, so it shouldn't need to reboot. I had to do this when trying to connect to an old Talk Talk wired router via RA with my old VM 20meg modem and VM netgear router for the same reason, but that was because the TT router was carp. No modem reboot was necessary.

How do I work out the correct MAC to spoof on my second lan port with the Superhub? Where do I look up the MAC the router side exposes to the modem side?

BenMcr · 03-08-2011, 18:14

As by the sounds of it the modem mode option forces a reboot anyway is there really a need to do that?

03-08-2011, 18:19

Yes the GUI forces the reboot after you confirm Modem Mode enabled, no way to stop it and I don't see why it's such a biggie??

---------- Post added at 19:19 ---------- Previous post was at 19:16 ----------

Quote:

Originally Posted by AndyCalling

How do I work out the correct MAC to spoof on my second lan port with the Superhub? Where do I look up the MAC the router side exposes to the modem side?

A VM rep in 0151 land told me the MAC of the internal router is one digit higher than the MAC of the modem part, how true this is I'm unsure but worth a try. I guess if you pick up the same public IP with your own kit then it works!

AndyCalling · 03-08-2011, 18:27

Damn. Looks like I'm knackerd then. I was relying on modem mode to solve this problem.

Do you know why I might have the long connection time problem then? My power levels are fine as is SNR and speed. I'm not in a high usage area. The engineer who installed it tried several Superhubs and they all had trouble locking on. Should I call VM and get an engineer out?

BenMcr · 03-08-2011, 18:27

In Windows 7 at least, you can find out what the router MAC address is by looking it up on the Network browser (Right click on device > Properties > Network Device)