MegaGlest Forum
MegaGlest => Bug reports => Topic started by: treba on 15 January 2012, 00:38:01
-
hey
this always happens, when i start up a second server on the same mashine:
(http://dl.dropbox.com/u/56789020/images/Screenshot%20at%202012-01-15%2001%3A32%3A43.png)
-
I think its not possible to run a second server !
The server always runs with 61357. The port you can switch ingame is only the port which is distributed to the masterserver! This does not mean your server really works with 61358. Its meant for (home)setups with routers which use NAT. There you can forward the port 61358 to the right computer with and its port 61357.
Confusing, but thats the way it is :-/ .
UPDATE: To really run a server with another IP you must edit the glestuser.ini manually and set:
ServerPort=61358
( additional its still needed to set the publish port to 61358 too! )
Update2: Oh there is something better now!!!
look at the parameters:
--use-ports=x,y Force hosted games to listen internally on port
x, externally on port y.
Where x is the internal port # on the local
machine to listen for connects
y is the external port # on the
router/proxy to forward connection
from to the internal port #
*NOTE: If enabled the FTP Server port #'s will
-
hey titi,
thx for the reply, but that's exactly what i already use (as softcoder suggested me here (https://forum.megaglest.org/index.php?topic=7949.msg79747#msg79747))
both ports, internal and external, are set to 61358
still the but remains :(
-
The problem is one of the following:
- the masterserver code mixes up gameservers listening on different ports on the same IP address
- the gameserver, when listening on a different port than 61357, still claims it is listening on port 61357 when announcing its game to the masterserver
I suspect the first is the case. Unless someone else is faster than me, I'll try to sort this out sometime this (busy) week.
-
One important fact to note is that its a bad idea to use only 1 number higher than the normal default port of 61357 (you show above as 61358). Why? Because STARTING at this port we ALSO use port #'s for FTP file xfer, thats why in my example i show 100 # different between port #'s on same server. Please try staggering port #'s by more than 20 when running on same server and let us know how that works.
When you look at the options screen under network it shows which ports are used based on the starting port #.
Thanks
-
ah alright. that seems to fix the problem. thx alot and say hello to the first mashine running multiple servers of megaglest :)
-
I hope this machine has a lot of ram :D ( 1GB per masterserver ).
I think its a good idea to add this information to the server name as it makes a huge difference for bigger games ( swapping->disconnect ....)
-
There's an open feature request for a welcome message. There surely is a need for dedicated server admins to be able to pass along information for players which can't be covered by the server name field alone.
-
it has 2gig, but each server is limited to 850mb. engineer.old had only 512mb overall.
maybe the servers should share 1700mb instead, as mostly only one server is in use. have to see.