blank port thing.

hedgehog · Post by **hedgehog** » Sat Jul 31, 2004 12:49 am

okay, so i removed the port= setting on reine's serverconfig.

it connects to the gal fine.

now how the heck do i or anyone else land on it?

Post by **Magicfinger** » Sat Jul 31, 2004 1:25 am

well i managed to connect d/load textures but then promptly crashed my pc

hedgehog · Post by **hedgehog** » Sat Jul 31, 2004 2:44 am

that was after i re-added the port= argument tho

zaroba · Post by **zaroba** » Sat Jul 31, 2004 5:14 pm

with no port setting, doesen't the island just use the defualt port 4662?

Post by **Mit** » Sat Jul 31, 2004 5:23 pm

nope, it uses the same technique as the client (or just about any other bit of internet software that doesnt expect you to specify an outgoing port) and uses the next free port as specifed by the operating system.

If your world is a standard server, rather than a gateway, that should theoretically be it. When the client joins the galaxy, the galaxy server tells the client where the worlds currently are and ding. If it doesnt work, then you've probably got some firewally/nat thing interfering and only accepting messages from a connection you've established explicitly - (i..e it will let the galaxy server talk to the world coz the world initiated the connection to the galaxy) - in which case, for now, you'll probably need to adjust your firewall settings or revert to a fixed, specific port which you've forwarded manually.

hedgehog · Post by **hedgehog** » Sat Jul 31, 2004 7:14 pm

yeh i think this is the part in the thread where fooli asks what the point of a firewall is if it doesn't block ports

k. so we're back to explicitly forwarding and recieving. i've set the router to have outgoing ports forwarded to the appropriate machine, using the same port rather than a random number, so i guess we'll sit on that and see how we do