byUsers Forums

If the username/password on the label don't work then maybe the installer changed the password

Did they ask you for any passwords at the time?

Update:

I was using the wrong IP to login to the superhub's router. I'm now trying to working out how to open ports in the 12000+ range...

Not really Taz. After logging into the router yesterday I was able to use port forwarding to open one port (TCP 443) but the other ports that need to be open are in the 12000 to 13050 range. There aren't any listed in the Services drop-down list. Twice I tried to use the add Custom Rules option but each attempt returned me to the router login page.

I then tried Port Triggering as that permitted me to use the higher numbered ports but I don't understand what is required for the Target Range.

If I understand the difference between Port Forwarding and Port Triggering then you would use Port Forwarding to open certain ports that are needed on a particular computer which is specified by that computers IP address. If you are unable to do it through Port Forwarding then you use Port Triggering then connect/login to whatever you want the ports open for and when the router detects which ports are needed, the router opens them for you. But as I've said, I don't understand the Target Range.

The ports that need opening are: TCP 443, TCP 12043, UDP 12035 or 12036, UDP 13000 to 13050. Port Forwarding enabled me to open TCP 443 but none of the others so I tried Port Triggering which let me set the others but I'm confused as to what is required for the Target Range.  As i understand it (I may have this the wrong way around): Port Forwarding is used to open outgoing ports for a particular purpose and the Target Range is for opening incoming ports. Last night I again tried using voice chat in second life but no-one seemed to be using it so I was unable to test if I'd got the required ports open.

In case it makes a difference, our old setup was:
Webstar Atlantic modem - ethernet cable - netgear router - ethernet cable to whichever computer. Second Life Voice Chat worked then.
The new setup is:
SuperHub - ethernet cable - (old) netgear router - ethernet cable to whichever computer. Everything works except Second Life Voice Chat. The old router never needed port forwarding setting up. I had wondered about removing the old router but it 'works' so why remove something thats doing its job.

Someone suggested I use Skype instead of Second Life's Voice Chat as an alternative but I read somewhere that skype won't work for someone with a VM cable connection and the link to pertforwarding.com in that link you gave me suggests if I wanted to use skype, I'd still need to enable it via port forwarding...

Last edited by oldgit (17-07-2012 12:19:38)

I've just managed to add the TCP 12043 to Port Forwarding by selecting the same HTTPS 'service' as I did for the TCP 443 port. Then clicking the Apply button took me to the routers login page but after logging into it again then going to the Port Forwarding, 12043 was listed.

I haven't been able to find out which of the 'services' to select then change the ports for the UDP port ranges. I'm wary trying each in turn in case I end up opening a port to something nasty. I still don't understand what the Target Range is in Port Triggering.

boringgit wrote:

Skype should work fine - it is a pretty clever bit of software and will use somebody elses bandwith if it can't use yours , but yeah - the Netgear is certainly an additional complication - have you set it to bridge mode, or not made any changes since it was your main router? If its not in bridge mode you are doing double NAT which is very rarely a good idea.

I've only used a superhub once and I didnt need to forward any ports on that occasion, but most routers allow you to add custom services, then forward to them - that would be where you define your 1200+ ports and forward them...

Thanks for the info boringgit but I'll only try Skype if I can't get voice chat in Second Life working.
I don't know what bridge mode is or if it's set so I just Googled it. The VM engineer set the Super Hub so after I'd done the other part on my wife's laptop, she'll be able to connect to it wirelessly (as she can now via the old router) so I suppose the answer is yes, its set to bridge mode.

Thanks for the explanation. My wife's laptop uses a wireless connection to the old router until I change it to use the superhub.

boringgit wrote:

It was the netgear I meant.

Your calling it the netgear may have added to my confusion because both routers are netgear routers

I'll be busy for a few hours but later today I'll connect this computer directly to the superhub's router and see if it makes a difference then post the result(s).

I understand that you dont want to use Skype and I wouldnt want to press you into doing so - but trust me - Skype works with no ports forwarded! I spent a long time at work trying to block the and then had to accept that it just was gonna work

I'm afraid to say I know nothing about second life. You can try to enable upnp on the superhub (when used without your old router). It has the potential to be a hideous security hole, but as with so many things... Its not actually a hole, its just a potential exploit....