Jump to content

Home

Some listen server help please.


Joruus

Recommended Posts

Is there any specific cvar or command that you can enter into the console to find out exactly what port your game server has started on?

 

This is the problem I've got.I run a server occasionally on a 1.1 megabit up and down SDSL. My IP Is static so its always 65.102.249.185. But for some reason, every time I start up my JKO server it just randomly assigns itself a port.

 

While I understand that 28070 is the default port for JKO, for some reason my server starts up on other ports. Making it very hard to instantly find after it starts up. Its been on port 10273, 27032, and 26719 that I can think of as of this time.

 

I run the server in listen mode because I only have the one box availible to me here at the house. And sometimes people find the server immediately, and sometimes it will run for half a day with no clients.

 

Pretty weird, overall.

Link to comment
Share on other sites

Originally posted by Joruus

Is there any specific cvar or command that you can enter into the console to find out exactly what port your game server has started on?

 

This is the problem I've got.I run a server occasionally on a 1.1 megabit up and down SDSL. My IP Is static so its always 65.102.249.185. But for some reason, every time I start up my JKO server it just randomly assigns itself a port.

 

While I understand that 28070 is the default port for JKO, for some reason my server starts up on other ports. Making it very hard to instantly find after it starts up. Its been on port 10273, 27032, and 26719 that I can think of as of this time.

 

I run the server in listen mode because I only have the one box availible to me here at the house. And sometimes people find the server immediately, and sometimes it will run for half a day with no clients.

 

Pretty weird, overall.

 

You might try using the +set net_port 28070 in the same line you use to call the server..

 

i.e.: jk2ded +set net_port 28070

 

I don't know of any way from inside the game to show what port it's listening on, except for when there are clients already connected.. If you type status at the server console,

you'll see the remote players IP:port the port is what port they connected to your server on.

 

But, you can always run netstat -a to show what ports are open and waiting for connections. You can always be sure that the server will be listening on a high number UDP port.

 

I think the newer versions of Linux, will allow you to do a netstat -anp (don't quote me on that).. This will show you which Program has that port open as well. There are also 3rd party programs, like 'lsof' that will give you indepth information as to which programs have what file handles, ports, and more open.

 

 

Hope this helps.

Link to comment
Share on other sites

This is my current server address

 

65.102.249.185:19400<====Whats with the port?

 

Yet in my dedicated server console reports this.

 

]net_port

"net_port" is:"28070" default:"28070"

 

Why would the console report the port as 28070 when its quite obviously running on port 19400?

 

And for some reason, it only shows up on ASE when I run it dedicated, showed up immediately almost. Whereas when I run it listen...it doesn't show up at all. But I've run it listen mode alot and its been open to the public and people have found it before.

 

This is very confusing. Some days listen servers advertise and some days they don't?

Link to comment
Share on other sites

Active Connections

 

Proto Local Address Foreign Address State

TCP v5t0i3:0 V5T0I3:0 LISTENING

TCP v5t0i3:59 V5T0I3:0 LISTENING

TCP v5t0i3:finger V5T0I3:0 LISTENING

TCP v5t0i3:27244 V5T0I3:0 LISTENING

TCP v5t0i3:1657 V5T0I3:0 LISTENING

TCP v5t0i3:28070 V5T0I3:0 LISTENING

TCP v5t0i3:1657 ky.enterthegame.com:6667 ESTABLISHED

TCP v5t0i3:137 V5T0I3:0 LISTENING

TCP v5t0i3:138 V5T0I3:0 LISTENING

TCP v5t0i3:nbsession V5T0I3:0 LISTENING

TCP v5t0i3:3413 V5T0I3:0 LISTENING

UDP v5t0i3:27244 *:*

UDP v5t0i3:28070 *:*

UDP v5t0i3:nbname *:*

UDP v5t0i3:nbdatagram *:*

UDP v5t0i3:3413 *:*

 

28070 is obviously shown in the UDP table, but theres no address and its not in any state.

 

But the server is still on 19400, at least publically. I work with networks all day long and this is right up there with some of the most confusing crap I've ever seen.

Link to comment
Share on other sites

Originally posted by Joruus

And for some reason, it only shows up on ASE when I run it dedicated, showed up immediately almost. Whereas when I run it listen...it doesn't show up at all. But I've run it listen mode alot and its been open to the public and people have found it before.

 

This is very confusing. Some days listen servers advertise and some days they don't?

 

Listen servers, by default, do not advertise. That's part of the definition of a listen server--they just listen for connections. It is possible to MAKE a listen server show up in the master list by manually sending a heartbeat. Now, if there's a bug in there somewhere, it'd be a good idea to try and isolate it so it can be reported and fixed. ;)

Link to comment
Share on other sites

I've run it listen before without sending heartbeats and people have found it with no problem via server browsers.

 

Today I've been running it listen and sending manual heartbeats every 10 minutes or so. And its not showing up on GSPY or ASE, and no one is connecting to it.

 

And its coming up on a different port every time. Its ridiculous.

Link to comment
Share on other sites

When I switch the server over to dedicated to get it to report to the master servers accurately, it consistently comes up on server ports other than 28070.

 

19400

27332

 

And on last boot

 

20337

 

If I do a search with my IP + the default port 28070, the request times out.

 

But in the console, when I check net_port it states that the port is 28070 and the default is 28070.

 

So thinking maybe it was just a silly bug, I tried getting around it. I typed this in the server console;

 

/seta net_port 28071

 

Then I rebooted the server, and ran net_port again, and it came up as 28070 again. But...once it showed up on ASE, it was under 20337.

Link to comment
Share on other sites

After shutting down again. I went into my jk2mpconfig file and added the net_port command with port 27081.

 

Then I restarted, and it reported that net_port was 27081. So its now changed in the start up configuration.

 

But when I insert the server on ASE using my ip 65.102.249.185:28071, it times out...because the server itself is NOT running on that port.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...