Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
Theres a lot of exploits usable on rcon protocol, its better to just block it all, or only allow to certain ip..
iptables -A INPUT -p tcp --destination-port {PORT-NUMBER-HERE} -j DROP
You will need further research to allow some ip.
so if I have 3 instances of srcds_linux open with thier own ports specifically for them this is how I'd block rcon completly correct?
(btw a slight bit of background is important here) I've done some stuff with iptables already just getting things exactly right isn't always my strong suit. I'm currently running 3 servers on gmod aswell as a teamspeak3 server. These are all running on the same machine btw with their resources devided out as they need them so they don't interfere with each other. will I run into any sort of issues with this sort of setup in the iptables? I want to ensure all 4 are fully up and running while also being secure aswell. as for rcon I won't need to worry about whitelisting an ip or anything. I have a seperate admin module currently in testing which removes the need for a rcon. and even if I need rcon I can easily log into my vps and do things to the server console from there. makes things pretty secure and easy aswell.
a side follow up question that I hadn't thought about. is there a way to target specifically which processes have access and such for ports/connections?
like for example srcds_A can have connections for players only thought port 27125, and srcds_B is using 27225? so if anybody tries to for example send data in through a port which normally accepts connections to srcds but is non-player info it drops that (I noticed that there is also 27005 for some reason but not sure what that port is used for)
if anybody has any other security tips btw for ports/iptables its greatly appreciated. alot of new things keep getting brought to my attention with network stuff and its alot for 1 guy to figure out all of it and ensure the best possible enviornment for players.
- Allow ssh to the server (only for a limited amount of networks my provider is using)
- Allow udp to the ports the srcds servers are running on (from any ip)
- Allow udp 9987 to the teamspeak3 server (from any ip)
- Drop any other traffic
An anonymized example:
what are these 2 lines however? I'm not familiar with what they do. the others are pretty straight forward.
iptables -I INPUT -i lo -j ACCEPT
iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
No ideia what the second one is..
Since we are talking about, its good ideia to put some protection on it..
my iptables rules:
I took it from the srcds forums or alliedmodders forums, modified by my needs.
My gameport is 25994.
The first one was already explained by Blaquicat.
The second one is to allow answer packets for sessions which your server has initiated (for example OS updates, srcds updates, etc.)