PDA

View Full Version : Ports 1332 and 1336


Link
Jan 23, 2007, 11:28 AM
I got an email message from someone who apparently had success from behind a router by forwarding ports 1332 and 1336. Does anyone else know anything about this? Would JJ2 use these ports at all?

Hi i have seens i got my router (almost a year) tried to get rid of the
anoying Time Out errors!
But all the port forwarding didn't work, but now i have finally fixed it!
You have to port forward port 1332 and 1336 to.
I thought it would be helpfull to others so i just wanted you to know...

Xplosive
Jan 23, 2007, 11:36 AM
Thats intresting but I don't think it could be true im sure people would of found this out a while back.

Violet CLM
Jan 23, 2007, 05:52 PM
Doesn't work for me.

Neobeo
Jan 23, 2007, 06:08 PM
I strongly doubt its plausability.

Monolith
Jan 23, 2007, 11:02 PM
Those could just be the ports JJ2 used in the temporary port range on that person's computer. I don't imagine those ports will be consistant, even for him.

Cpp
Jan 23, 2007, 11:45 PM
Hmm I've never seen that before in my 4 years of jj2 traffic logging (server-side). I think its totally plausable on clinet side however. Jj2 will reserve random ports to receive/send traffic when connected as a client to another server each time it starts up.

blurredd
Jan 24, 2007, 10:06 AM
From what I've seen, JJ2 from startup uses the same UDP port chosen from the ephemeral port range until the exe is closed. I'm guessing it wouldn't be too hard to force JJ2 to use a specific port, although I imagine that would have its own problems. Alternatively (and much easier to do) JJ2 could indicate to the user which UDP port is being used and thus which port should be forwarded, but that of course lacks practicality. I should really learn more about sockets.

Grytolle
Jan 24, 2007, 10:50 AM
Adding a setting to 1.23+ for forcing usage of certain ports would be a good idea.

Neobeo
Jan 24, 2007, 02:02 PM
It really isn't any difficult to force a UDP port on the client side. By default, JJ2 uses port 0, which lets winsock randomly choose an unused port. It really wouldn't be a bad idea to hardcode a fixed port number. Drawbacks would be if some other program happens to already be using that port, or similarly problems playing online on more than one JJ2.

blurredd
Jan 24, 2007, 07:13 PM
Hmm... I managed to force JJ2 to use a specific UDP port, and indeed it wasn't hard. Neobeo might've figured this all out already, but at least it was a learning experience of sorts. Ditto everything else he said.

Edit: I still don't know why some people are able to join a server through GIP or similar when they couldn't otherwise.

Grytolle
Jan 24, 2007, 10:37 PM
It really isn't any difficult to force a UDP port on the client side. By default, JJ2 uses port 0, which lets winsock randomly choose an unused port. It really wouldn't be a bad idea to hardcode a fixed port number. Drawbacks would be if some other program happens to already be using that port, or similarly problems playing online on more than one JJ2.So let's make a setting!:D