Server IP:Port Binds


(ignitor) #1

In launch i have the following;

+set net_IP 216.246.108.73 +set net_serverPort 27015 +set net_serverPortMaster 27016

What i find interesting is how every IP my server has available now listens on the 27016 port. The only ones that don’t are IP’s that already have services running on them.

IE
216.246.108.75:27016 Reponds
216.246.108.74:27016 Reponds
216.246.108.73:27016 Reponds (as it should)

net_ip
"net_ip" is:"216.246.108.73" default:"localhost"
local IP address

Wth am I doing wrong (if anything)?


(ignitor) #2

In addition the serverport is supposed to be 27015 but responds to something like hlsw under port 27016. In doing further research you can issue a netstat on your server and you may see something similar to me;

UDP    0.0.0.0:27016          *:*

Basically it has bound UDP 27106 to every address available. .

It does appear to have properly bound the port for 27105

UDP 216.246.108.73:27015 :

Also server port auth appears to bind to everything as well under “8766” not sure if it’s supposed to or not.


(Johnny5_Hull) #3

We are also having this exact same issue.

The biggest problem is that when this happens, it prevents any other steam based game (that uses ports 27015) from starting correctly, throwing errors that the port is already in use.

This really does need sorting sooner rather than later, as this is causing major headaches for us and our customers.

Is there or has there been any news on whether a fix is in place for this?


(Deadwalking) #4

You could always just bump up the ports by 2 everytime you create a new instance of a server. I f am reading the OP correctly.

Running Source based games already using ports 27015 27016. So first Brink server would start above that 27017 27018 and so on. PortAuth can stay 8766 for all servers I believe that it is only used for Steam to recognie the server, but I could be wrong about that.

I have my 2 servers starting at ports 27019+27020 and 27021+27022

The +net_ip should be working as well since last server patch. But I am not sure if it will make it only listen on the ip set thru +net_ip.

As long as there are no conflicts with another application or service needing certain ports you can set them to whatever you want except the PortAuth. Keeping in mind that other programs default to certain ports.


(Johnny5_Hull) #5

we are doing this, however we also have other games which with port bumping get caught in the mix.

I’m not knocking it massively, its awkward at the minute, and causing a headache, but its not that difficult to balance them out.

I have every confidence it will get sorted… just hoping it’s sooner.