Cable Forum - View Single Post

kwikbreaks · 19-06-2011, 09:20

Having changed all my hardcoded devices to use the 192.168.0 range when I got the Superhub I've just had to change its base range as I've finally given up on using one as a hub and connected a separate router in the DMZ. I only went to the 192.168.20 range but don't recall any problem doing it. All the hub has in its config now is an IP reservation and DMZ specified for the router.

I got WoL working using LogMeIn for a single device (my laptop) by having it on a fixed IP and forwarding port 9 UDP to it specifically. You can't forward to the port 255 on the Superhub which I think is what is needed to be able to WoL more than one specific device. I'm pretty sure the router I'm currently using, the VM freebie WNR2000, was working for WoL OK when I was on 20Mbps with a separate modem but it doesn't seem to want to work now - I'll see if forwarding 9 UDP on it works.

It didn't. Now for something really silly - what if I forward UDP 9 to the router evn though it is already in the DMZ?

That didn't work either. On reflection I think I only used the WNR2000 for a short time and switched to a Buffalo running Tomato firmware. Maybe low-end Netgear kit has an aversion to passing on magic packets. If I get the VMNG300 I requested from the CEO office I'll get a better router. If not I'll probably wait and see what the R27 firmware brings as the WNR2000 is only a small step up on the Superhub and using the two in tandem has significantly increased latency which may mess with my VOIP.

19-06-2011, 09:20	#8
kwikbreaks Inactive Join Date: May 2010 Services: Plusnet FTTC, FoxSat HDR for TV, Vonage VOIP. Posts: 2,082	Re: Superhub Configuration Question Having changed all my hardcoded devices to use the 192.168.0 range when I got the Superhub I've just had to change its base range as I've finally given up on using one as a hub and connected a separate router in the DMZ. I only went to the 192.168.20 range but don't recall any problem doing it. All the hub has in its config now is an IP reservation and DMZ specified for the router. I got WoL working using LogMeIn for a single device (my laptop) by having it on a fixed IP and forwarding port 9 UDP to it specifically. You can't forward to the port 255 on the Superhub which I think is what is needed to be able to WoL more than one specific device. I'm pretty sure the router I'm currently using, the VM freebie WNR2000, was working for WoL OK when I was on 20Mbps with a separate modem but it doesn't seem to want to work now - I'll see if forwarding 9 UDP on it works. It didn't. Now for something really silly - what if I forward UDP 9 to the router evn though it is already in the DMZ? That didn't work either. On reflection I think I only used the WNR2000 for a short time and switched to a Buffalo running Tomato firmware. Maybe low-end Netgear kit has an aversion to passing on magic packets. If I get the VMNG300 I requested from the CEO office I'll get a better router. If not I'll probably wait and see what the R27 firmware brings as the WNR2000 is only a small step up on the Superhub and using the two in tandem has significantly increased latency which may mess with my VOIP.