Superhub : SuperHub as an Access Point

[AndyCalling]

I recommend you only use words acceptable before the watershed. This isn't so bad as 'feck' was judged OK for such when Father Ted was on telly, so that has state approval as suitable for children, as has the word 'arse' which was also used in Father Ted and authorised. Also, the standard middle-class approach of adjusted phrases such as 'darn', 'flip', 'ruddy hell' and 'stupid beggars' should be OK.

There should be enough to get the message across within such socially acceptable strictures.

[idi banashapan]

and 'Frack' as well as any conjugation thereof, as used in BSG!

[AndyCalling]

Also, I expect you could get away with calling someone a complete member, since we are all forum members here. Shouldn't corrupt any children with that. Dropping the word but keeping the rest should also be OK such as in the phrase 'that Superhub really is a complete steaming pile'.

You may so want to adopt a commonly understood forum substitute, ie. 'my ping has really dropped through the floor recently, last weekend it was a complete pile Superhub' or 'my last VM bill was a right mess, the phone bill was simply a steaming lump of Superhub if you ask me'.

Loads of child-safe options there, I'm sure you can come up with your own acceptable alternatives to using horrible offensive language like some mother-flipping Superhub-head might try.

BongMong - Cleaning up cable-talk for a brighter tomorrow.

[AndyCalling]

Originally Posted by Paul M

Dont get involved in something that doesnt concern you.

Hmm, rather strong, that. Particularly when you're supposedly trying to stop people from causing offence to others. Not the best example to set. If it wasn't the concern of forum members then might I suggest you PM the fellow and that you don't post your comment on a public forum? Just an idea, to help you with constructive input.

[idi banashapan]

Originally Posted by AndyCalling

Hmm, rather strong, that. Particularly when you're supposedly trying to stop people from causing offence to others. Not the best example to set. If it wasn't the concern of forum members then might I suggest you PM the fellow and that you don't post your comment on a public forum? Just an idea, to help you with constructive input.

Thank you. I thought I was the only one who noticed that comment. 'thread closed' coming soon.... Lol

[caph]

Originally Posted by Skie

I've been able to get O2 adsl routers to act as bridges by pointing to the other one as a gateway, but I dont think you can define a gateway on the superhub. You can't break anything by trying, but I doubt it would work.

This is a common misconception. A wireless access point (or a device acting as one) does not have a default gateway. It can't have one because it is not capable of routing. It merely extends a LAN.

To the OP. Just turn on the spare superhub, disable DHCP, enable wireless and plug the cable from your main Superhub in to the LAN port of your spare superhub (NOT the WAN port). Job done and no settings required.

[AndyCalling]

Hmm, I have a spare Superhub (legal, don't ask the story as it is long and boring) so I might do this as I'll be able to get a little more wireless speed out of one device by setting it up this way. Two superhubs = dual channel? Might be a good idea. Would there be any way to upgrade the software on the second hub if it improves wireless at all though? Could I just temporarily connect it to the cable socket to get the update, even if it's never been activated by VM before, then switch back to my normal wan-connected hub for use?

[m74uk]

I'm going to try it at the weekend Andy.

If you get it going before that, let me know.

PS....Didn't know you could get them illegal.

I've only got a second one cause I got one when I updated to 20mb then when I upgraded to 50mb 3 weeks later I got another one.

[AndyCalling]

Yes, unfortunately some dodgy types like to get ebay boxes and try to hack into the cable for free. VM seem to be getting on top of this practice though.

Mine came to me due to VM cock-up and they aren't interested in getting it back.

I have done it. One Superhub on 2.4Ghz as a wireless access point and one on 5Ghz as the main router and modem.

My second hub, when connected to VM cable, will connect to the walled garden type of thing where you can activate it, but I don't want to do that. It gets notified of an update to the firmware but upon downloading it finds it to be incompatible according to the log. Shame, because it is firmware R19 instead of R20 like my main router. Seems like it'll be stuck this way for ever so no chance of it getting wireless improvements or fixes.

Still, it has to do little. Set it up like this:

1) Plug the second router (Superhub) in to a wired PC like your laptop or netbook with ethernet cable, leaving your main PC attached to your main router (Superhub). Disable any wireless networks on your netbook first to stop any DHCP hassles.
2) Go into the settings and turn off the firewall and flood protection, these affect the lan side (oddly) so you'll need to do this.
3) Set up the wireless SSID and set it to 2.4Ghz. You should also set it to 145Mbps unless you live in an isolated spot or it'll take up two 2.4Ghz channels and peeve your neighbours. Don't be a wireless thug! Save 300Mbps for the 5Ghz router. Remember to set up your wireless encryption, you can use the same passphrase as you do in your primary router to save confusion. After all, which ever one they get through they have got through, so you may as well only give them one right answer instead of two. Common sense.
4) Turn off UPNP just in case.
5) Now, last thing you do, set the lan IP address to 192.168.0.254, set the ending IP address to 192.168.0.253 and set DHCP Server to No. You need to set the ending IP address as well or it will complain, even though DHCP is switched off.
6) When you apply the lan IP changes you will lose connection to the second router. Switch it off and disconnect it. Go into your main routers settings (the one connected to VM) and adjust the ending IP address to 192.168.0.253 as you did with the second router. You can tweak any other settings like SSID and 300Mbps 5Ghz mode now if you like.
7) Connect a lan port on the second router to a lan port on the primary router.
8) Switch it on and you're done. Just remember the settings for the second router can be accessed through ip 192.168.0.254 leaving your primary router on 192.168.0.1.

Please note, I have no idea what would happen if both guest networks were switched on at once. Something to play with, I guess.

So, now you have a dual band Superhub. Impress your friends! Ahem... or something.

[caph]

Originally Posted by caph

Job done and no settings required.

Oops, as Andy correctly points out you do have to change the LAN address of your intermediate superhub otherwise it will clash with your main superhub.

Oh well, almost right.

[AndyCalling]

I've been testing, and truely it appears that instead of just giving me a Superhub, VM have effectively given me an Uberhub! It is a 6 gigabit port, true dual band, 3 wireless network monster (potentially, still haven't tested two guest networks at once).

Now theoretically, since VM supplied all this equipment, and it is set up in a legitimate way, they will have to support it. I suggest though that if you call one of their overseas support agents and tell them what you have set up then ask for support, they may just resign their job on the spot rather than deal with it. It looks like us Uberhubbers will have to support each other.

No major problems for me except Remote Assistance, so I still need that bridge mode firmware as a work around for RA crashing the router.

Still, I'm interested in seeing how any one else with an Uberhub setup gets on. Uberhubbers, please post your results!

We are likely to be a small 'elite' as few will get sent an Uberhub from VM like ours. Even fewer will want to look as nerdy as us by sticking two Superhubs by their PC like it's some kind of Hal rebuild... ~

[m74uk]

Got my Uberhub up & running now

Done what you said with the settings Andy & have got the Cable connected to my Main Superhub & set to 5Ghz which only my laptop connects to via my NETGEAR WNDA3100v2 & the 2nd Superhub situated in a central location, hardwired back to the main hub, servicing all other wireless devices on 2.4Ghz

All running smoothly just now & very happy with it.

Thanks

[Chrysalis]

yeah thats one thing I forgot, the ip address itself would need to be changed.

[zekeisaszekedoes]

Not difficult to do this - switch off DHCP on 2nd router, give it an IP ideally out of main router DHCP range (i.e. 1st/gateway is 192.168.1.1, SH is 192.168.1.2) and away you go. I was using my Super Hub this way before I got better wireless N routers that don't bugger up all the time. But I'd steer clear of the thing entirely and get decent kit.

[AndyCalling]

I have got rid of the Uberhub setup. The reason? Well, the Superhub with the version R19 firmware seems to cut off wireless devices after a while, all of them. They remain linked with a good signal, just can't communicate with the internet or with other devices. It may just go increadibly slowly, almost not working at all. Changing channels seems to wake it up, but it goes back to not working a while later. The version R20 firmware in the main Superhub seems not to have these problems.

I have no such issues when I use my little VM supplied Netgear WGR614v9 router as a wireless access point (with the latest Netgear firmware on it rather than the old VM firmware). I can't get 150N on it of course though, only G.

If anyone knows a way to update a Superhub's firmware without 'activating' it so it becomes the main Superhub on one's account, do let me know. Otherwise it is just a brick as firmware R19 was obviously updated to R20 for a good reason. R19 has something very broken in it.