Author Topic: From LAN to public server  (Read 5001 times)

Exterminans

  • Posts: 14
  • Turrets: +0/-0
From LAN to public server
« on: July 03, 2008, 09:46:24 pm »
I've tried to join a public server from a little lanparty but it seemed as only one person could join a server, as soon as th second person tries both got kicked.
Someone suggest me to use a different net_port for every client, but this seems a bit to complicated for a lager group of people to change this settings manually. So my suggestion is to add a option in the settings-menu to use a random port instead or check if the port is not allready in use (what shouldnt be that hard).

David

  • Spam Killer
  • *
  • Posts: 3543
  • Turrets: +249/-273
Re: From LAN to public server
« Reply #1 on: July 03, 2008, 10:19:06 pm »
How would you check its not in use?
Get a working router or manually change the port if your router is too dumb to do it for you.
Any maps not in the MG repo?  Email me or come to irc.freenode.net/#mg.
--
My words are mine and mine alone.  I can't speak for anyone else, and there is no one who can speak for me.  If I ever make a post that gives the opinions or positions of other users or groups, then they will be clearly labeled as such.
I'm disappointed that people's past actions have forced me to state what should be obvious.
I am not a dev.  Nothing I say counts for anything.

Bissig

  • Posts: 1309
  • Turrets: +103/-131
Re: From LAN to public server
« Reply #2 on: July 04, 2008, 12:14:00 am »
The solutions is already here and it is called NAT - network adress translation. ANY router should be able to do it. (Seriously, is there any ISP not using routers to connect "dial-up" customers to their net these days?)

kevlarman

  • Posts: 2737
  • Turrets: +291/-295
Re: From LAN to public server
« Reply #3 on: July 04, 2008, 03:49:39 am »
The solutions is already here and it is called NAT - network adress translation. ANY router should be able to do it. (Seriously, is there any ISP not using routers to connect "dial-up" customers to their net these days?)
not all NAT implementations are perfect, many common routers don't do the right thing when multiple clients start udp "connections" to the same ip:port with the same source port.
Quote from: Asvarox link=topic=8622.msg169333#msg169333
Ok let's plan it out. Asva, you are nub, go sit on rets, I will build, you two go feed like hell, you go pwn their asses, and everyone else camp in the hallway, roger?
the dretch bites.
-----
|..d| #
|.@.-##
-----

Bissig

  • Posts: 1309
  • Turrets: +103/-131
Re: From LAN to public server
« Reply #4 on: July 04, 2008, 07:52:43 pm »
The solutions is already here and it is called NAT - network adress translation. ANY router should be able to do it. (Seriously, is there any ISP not using routers to connect "dial-up" customers to their net these days?)
not all NAT implementations are perfect, many common routers don't do the right thing when multiple clients start udp "connections" to the same ip:port with the same source port.

Same for TCP?

David

  • Spam Killer
  • *
  • Posts: 3543
  • Turrets: +249/-273
Re: From LAN to public server
« Reply #5 on: July 04, 2008, 09:37:57 pm »
TCP has connections so is a lot easier to track, but its entirely possible for shitty router's to fuck that up too.  But I would assume that most are better at tcp.
Any maps not in the MG repo?  Email me or come to irc.freenode.net/#mg.
--
My words are mine and mine alone.  I can't speak for anyone else, and there is no one who can speak for me.  If I ever make a post that gives the opinions or positions of other users or groups, then they will be clearly labeled as such.
I'm disappointed that people's past actions have forced me to state what should be obvious.
I am not a dev.  Nothing I say counts for anything.