How to limit 1 connection per 5 seconds? (IPTABLES)
up vote
0
down vote
favorite
I want to limit 1 connect per 5 seconds using IPTABLES for people, which are connecting to port "12871/12881". I was trying to find rule for it, but ineffectively.
It must be like a "queue" of connects - for example 1 connect per 5 seconds.
I had here discussion:
How to limit 1 connect per 5 seconds? (IPTABLES) but Im not able to reply on this account, previous was unregistered and logged me out.
iptables firewall
asked Nov 23 at 17:53
onStyle
6
New contributor
onStyle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
I want to limit 1 connect per 5 seconds using IPTABLES for people, which are connecting to port "12871/12881". I was trying to find rule for it, but ineffectively.
It must be like a "queue" of connects - for example 1 connect per 5 seconds.
I had here discussion:
How to limit 1 connect per 5 seconds? (IPTABLES) but Im not able to reply on this account, previous was unregistered and logged me out.
iptables firewall
asked Nov 23 at 17:53
onStyle
6
New contributor
onStyle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I want to limit 1 connect per 5 seconds using IPTABLES for people, which are connecting to port "12871/12881". I was trying to find rule for it, but ineffectively.
It must be like a "queue" of connects - for example 1 connect per 5 seconds.
I had here discussion:
How to limit 1 connect per 5 seconds? (IPTABLES) but Im not able to reply on this account, previous was unregistered and logged me out.
iptables firewall
asked Nov 23 at 17:53
onStyle
6
New contributor
onStyle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I want to limit 1 connect per 5 seconds using IPTABLES for people, which are connecting to port "12871/12881". I was trying to find rule for it, but ineffectively.
It must be like a "queue" of connects - for example 1 connect per 5 seconds.
I had here discussion:
How to limit 1 connect per 5 seconds? (IPTABLES) but Im not able to reply on this account, previous was unregistered and logged me out.
iptables firewall
iptables firewall
asked Nov 23 at 17:53
onStyle
6
New contributor
onStyle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 23 at 17:53
onStyle
6
New contributor
onStyle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 23 at 17:53
onStyle
6
New contributor
onStyle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 23 at 17:53
onStyle
6
asked Nov 23 at 17:53
onStyle
6
6
New contributor
onStyle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
onStyle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
onStyle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
Example: Limit Connections Per Second
The following example will drop incoming connections if IP make more than 3 connection attempts to port 12871:12881 within 5 seconds.
iptables -A INPUT -p tcp --dport 12871:12881 -i eth0 -m state --state NEW -m recent --set
iptables -A INPUT -p tcp --dport 12871:12881 -i eth0 -m state --state NEW -m recent --update --seconds 5 --hitcount 3 -j DROP
Just change eth0 to your interface id...
The hitcount and seconds can be tailored to your needs.
I don't know, but it seems like your hardware is just not up to running a HurtWorld server.
Try running it with these options:
- batchmode
- nographics
- exec "host 12871;queryport 12881"
- servername whateveryouwant
- addadmin "<My Steam ID>"
- logfile "gamelog.txt"
Ref:
https://hurtworld.gamepedia.com/Hosting_A_Server
https://linuxgsm.com/lgsm/hwserver/
https://docs.linuxgsm.com/configuration/linuxgsm-config
answered Nov 23 at 17:56
Michael Prokopec
52415
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
@Michale Prokopec If there will be at specific time more than 3 connects all the time no one will connect - they will try to connect until they won't do it.
– onStyle
Nov 23 at 17:58
After 3 connection attempts in 5 seconds by the same IP that IP is ignored. You can change it so after 2 connection attempts within 2 seconds that IP is ignored.
– Michael Prokopec
Nov 23 at 18:15
"wll drop incoming connections if IP make more than 3 connection". Server have 100 slots for players. In one time connects 100+ different IPs, so these connections are not making one user, but 100 different users. I must do something like: 1 player -> 5 seconds -> 2 player -> 5 seconds
– onStyle
Nov 23 at 18:20
If the above will not work, the're are resource or other config issues if you're still having issues.
– Michael Prokopec
Nov 23 at 18:28
Yeah it don't work. If one connect, it must stop other connects for 5 seconds.
– onStyle
Nov 23 at 18:58
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Example: Limit Connections Per Second
The following example will drop incoming connections if IP make more than 3 connection attempts to port 12871:12881 within 5 seconds.
iptables -A INPUT -p tcp --dport 12871:12881 -i eth0 -m state --state NEW -m recent --set
iptables -A INPUT -p tcp --dport 12871:12881 -i eth0 -m state --state NEW -m recent --update --seconds 5 --hitcount 3 -j DROP
Just change eth0 to your interface id...
The hitcount and seconds can be tailored to your needs.
I don't know, but it seems like your hardware is just not up to running a HurtWorld server.
Try running it with these options:
- batchmode
- nographics
- exec "host 12871;queryport 12881"
- servername whateveryouwant
- addadmin "<My Steam ID>"
- logfile "gamelog.txt"
Ref:
https://hurtworld.gamepedia.com/Hosting_A_Server
https://linuxgsm.com/lgsm/hwserver/
https://docs.linuxgsm.com/configuration/linuxgsm-config
answered Nov 23 at 17:56
Michael Prokopec
52415
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
@Michale Prokopec If there will be at specific time more than 3 connects all the time no one will connect - they will try to connect until they won't do it.
– onStyle
Nov 23 at 17:58
After 3 connection attempts in 5 seconds by the same IP that IP is ignored. You can change it so after 2 connection attempts within 2 seconds that IP is ignored.
– Michael Prokopec
Nov 23 at 18:15
"wll drop incoming connections if IP make more than 3 connection". Server have 100 slots for players. In one time connects 100+ different IPs, so these connections are not making one user, but 100 different users. I must do something like: 1 player -> 5 seconds -> 2 player -> 5 seconds
– onStyle
Nov 23 at 18:20
If the above will not work, the're are resource or other config issues if you're still having issues.
– Michael Prokopec
Nov 23 at 18:28
Yeah it don't work. If one connect, it must stop other connects for 5 seconds.
– onStyle
Nov 23 at 18:58
add a comment |
up vote
1
down vote
Example: Limit Connections Per Second
The following example will drop incoming connections if IP make more than 3 connection attempts to port 12871:12881 within 5 seconds.
iptables -A INPUT -p tcp --dport 12871:12881 -i eth0 -m state --state NEW -m recent --set
iptables -A INPUT -p tcp --dport 12871:12881 -i eth0 -m state --state NEW -m recent --update --seconds 5 --hitcount 3 -j DROP
Just change eth0 to your interface id...
The hitcount and seconds can be tailored to your needs.
I don't know, but it seems like your hardware is just not up to running a HurtWorld server.
Try running it with these options:
- batchmode
- nographics
- exec "host 12871;queryport 12881"
- servername whateveryouwant
- addadmin "<My Steam ID>"
- logfile "gamelog.txt"
Ref:
https://hurtworld.gamepedia.com/Hosting_A_Server
https://linuxgsm.com/lgsm/hwserver/
https://docs.linuxgsm.com/configuration/linuxgsm-config
answered Nov 23 at 17:56
Michael Prokopec
52415
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
@Michale Prokopec If there will be at specific time more than 3 connects all the time no one will connect - they will try to connect until they won't do it.
– onStyle
Nov 23 at 17:58
After 3 connection attempts in 5 seconds by the same IP that IP is ignored. You can change it so after 2 connection attempts within 2 seconds that IP is ignored.
– Michael Prokopec
Nov 23 at 18:15
"wll drop incoming connections if IP make more than 3 connection". Server have 100 slots for players. In one time connects 100+ different IPs, so these connections are not making one user, but 100 different users. I must do something like: 1 player -> 5 seconds -> 2 player -> 5 seconds
– onStyle
Nov 23 at 18:20
If the above will not work, the're are resource or other config issues if you're still having issues.
– Michael Prokopec
Nov 23 at 18:28
Yeah it don't work. If one connect, it must stop other connects for 5 seconds.
– onStyle
Nov 23 at 18:58
add a comment |
up vote
1
down vote
up vote
1
down vote
Example: Limit Connections Per Second
The following example will drop incoming connections if IP make more than 3 connection attempts to port 12871:12881 within 5 seconds.
iptables -A INPUT -p tcp --dport 12871:12881 -i eth0 -m state --state NEW -m recent --set
iptables -A INPUT -p tcp --dport 12871:12881 -i eth0 -m state --state NEW -m recent --update --seconds 5 --hitcount 3 -j DROP
Just change eth0 to your interface id...
The hitcount and seconds can be tailored to your needs.
I don't know, but it seems like your hardware is just not up to running a HurtWorld server.
Try running it with these options:
- batchmode
- nographics
- exec "host 12871;queryport 12881"
- servername whateveryouwant
- addadmin "<My Steam ID>"
- logfile "gamelog.txt"
Ref:
https://hurtworld.gamepedia.com/Hosting_A_Server
https://linuxgsm.com/lgsm/hwserver/
https://docs.linuxgsm.com/configuration/linuxgsm-config
answered Nov 23 at 17:56
Michael Prokopec
52415
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Example: Limit Connections Per Second
The following example will drop incoming connections if IP make more than 3 connection attempts to port 12871:12881 within 5 seconds.
iptables -A INPUT -p tcp --dport 12871:12881 -i eth0 -m state --state NEW -m recent --set
iptables -A INPUT -p tcp --dport 12871:12881 -i eth0 -m state --state NEW -m recent --update --seconds 5 --hitcount 3 -j DROP
Just change eth0 to your interface id...
The hitcount and seconds can be tailored to your needs.
I don't know, but it seems like your hardware is just not up to running a HurtWorld server.
Try running it with these options:
- batchmode
- nographics
- exec "host 12871;queryport 12881"
- servername whateveryouwant
- addadmin "<My Steam ID>"
- logfile "gamelog.txt"
Ref:
https://hurtworld.gamepedia.com/Hosting_A_Server
https://linuxgsm.com/lgsm/hwserver/
https://docs.linuxgsm.com/configuration/linuxgsm-config
answered Nov 23 at 17:56
Michael Prokopec
52415
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 24 at 4:06
answered Nov 23 at 17:56
Michael Prokopec
52415
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 23 at 17:56
Michael Prokopec
52415
answered Nov 23 at 17:56
Michael Prokopec
52415
52415
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
@Michale Prokopec If there will be at specific time more than 3 connects all the time no one will connect - they will try to connect until they won't do it.
– onStyle
Nov 23 at 17:58
After 3 connection attempts in 5 seconds by the same IP that IP is ignored. You can change it so after 2 connection attempts within 2 seconds that IP is ignored.
– Michael Prokopec
Nov 23 at 18:15
"wll drop incoming connections if IP make more than 3 connection". Server have 100 slots for players. In one time connects 100+ different IPs, so these connections are not making one user, but 100 different users. I must do something like: 1 player -> 5 seconds -> 2 player -> 5 seconds
– onStyle
Nov 23 at 18:20
If the above will not work, the're are resource or other config issues if you're still having issues.
– Michael Prokopec
Nov 23 at 18:28
Yeah it don't work. If one connect, it must stop other connects for 5 seconds.
– onStyle
Nov 23 at 18:58
add a comment |
@Michale Prokopec If there will be at specific time more than 3 connects all the time no one will connect - they will try to connect until they won't do it.
– onStyle
Nov 23 at 17:58
After 3 connection attempts in 5 seconds by the same IP that IP is ignored. You can change it so after 2 connection attempts within 2 seconds that IP is ignored.
– Michael Prokopec
Nov 23 at 18:15
"wll drop incoming connections if IP make more than 3 connection". Server have 100 slots for players. In one time connects 100+ different IPs, so these connections are not making one user, but 100 different users. I must do something like: 1 player -> 5 seconds -> 2 player -> 5 seconds
– onStyle
Nov 23 at 18:20
If the above will not work, the're are resource or other config issues if you're still having issues.
– Michael Prokopec
Nov 23 at 18:28
Yeah it don't work. If one connect, it must stop other connects for 5 seconds.
– onStyle
Nov 23 at 18:58
@Michale Prokopec If there will be at specific time more than 3 connects all the time no one will connect - they will try to connect until they won't do it.
– onStyle
Nov 23 at 17:58
@Michale Prokopec If there will be at specific time more than 3 connects all the time no one will connect - they will try to connect until they won't do it.
– onStyle
Nov 23 at 17:58
After 3 connection attempts in 5 seconds by the same IP that IP is ignored. You can change it so after 2 connection attempts within 2 seconds that IP is ignored.
– Michael Prokopec
Nov 23 at 18:15
After 3 connection attempts in 5 seconds by the same IP that IP is ignored. You can change it so after 2 connection attempts within 2 seconds that IP is ignored.
– Michael Prokopec
Nov 23 at 18:15
"wll drop incoming connections if IP make more than 3 connection". Server have 100 slots for players. In one time connects 100+ different IPs, so these connections are not making one user, but 100 different users. I must do something like: 1 player -> 5 seconds -> 2 player -> 5 seconds
– onStyle
Nov 23 at 18:20
"wll drop incoming connections if IP make more than 3 connection". Server have 100 slots for players. In one time connects 100+ different IPs, so these connections are not making one user, but 100 different users. I must do something like: 1 player -> 5 seconds -> 2 player -> 5 seconds
– onStyle
Nov 23 at 18:20
If the above will not work, the're are resource or other config issues if you're still having issues.
– Michael Prokopec
Nov 23 at 18:28
If the above will not work, the're are resource or other config issues if you're still having issues.
– Michael Prokopec
Nov 23 at 18:28
Yeah it don't work. If one connect, it must stop other connects for 5 seconds.
– onStyle
Nov 23 at 18:58
Yeah it don't work. If one connect, it must stop other connects for 5 seconds.
– onStyle
Nov 23 at 18:58
add a comment |
onStyle is a new contributor. Be nice, and check out our Code of Conduct.
onStyle is a new contributor. Be nice, and check out our Code of Conduct.
onStyle is a new contributor. Be nice, and check out our Code of Conduct.
onStyle is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f483737%2fhow-to-limit-1-connection-per-5-seconds-iptables%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
