To be honest two people said the same thing, and 3 others are just
completely wrong. Invalid protocol posted the fix had anyone bothered to
investigate the link.
block outbound TCP to 27017, 27018, and 27019.
With multiple IP allocations the server falls back to TCP, if you block
them, it reverts to UDP. It has nothing to do with his +ip vs -ip
configuration.
----- Original Message -----
From: "Mart-Jan Reeuwijk" <[email protected]>
To: "Half-Life dedicated Linux server mailing list"
<[email protected]>
Sent: Sunday, July 22, 2012 6:43 PM
Subject: Re: [hlds_linux] IP address mumbo jumbo
You can launch the program with a special group ID and then configure
IPTables to filter on the group.
________________________________
From: "[email protected]" <[email protected]>
To: Half-Life dedicated Linux server mailing list
<[email protected]>
Sent: Monday, 23 July 2012, 0:20
Subject: Re: [hlds_linux] IP address mumbo jumbo
Unless things have changed, this doesn't help. Your listening port is
bound to the IP you specify, but the master server lists you on the IP
your traffic to it comes in on, and since the servers on Linux do NOT bind
outgoing connections to your chosen interface, that means it always uses
the default route and your primary IP.
The master server doesn't take your word for good reasons; you could be
behind NAT, for instance. the server not binding outgoing connections to
your chosen IP is a bug.
Jesse Molina <[email protected]> wrote:
What that guy below said. You need to use -ip on the command line, NOT
+ip.
Didrole wrote:
Try to use -ip instead of +ip
2012/7/22 Saul Rennison <[email protected]>
I'm pretty sure the reported public IP is the one that Steam sees your
packets coming from, and the other address it the one the game server
is
bound to.
Can you connect to your server via the eth0 address; 85.x.x.57:27015?
If
not then there's nothing to worry about. Also I don't know why you've
hidden your IP, when it's publically available on the master servers ;)
Kind regards,
*Saul Rennison*
On 22 July 2012 16:19, Ronny Schedel <[email protected]> wrote:
Hello,
I have discovered a strange thing with our DOD:S and TF2 servers
today.
Take a look at the line of the status output:
udp/ip : 85.x.x.95:27015 (public ip: 85.x.x.57)
We are binding our server to 85.x.x.95 with +ip as start parameters.
The
public IP shows our IP address from the first network card eth0. Wtf?
How
can I prevent this behaviour?
Best regards
Ronny
_____________________________________________
**_________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.**com/cgi-bin/mailman/listinfo/**hlds_linux<
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux>;
_____________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
_____________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
--
# Jesse Molina
# Mail = [email protected]
# Cell = 1-602-323-7608
_____________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
