116 reputation
3
bio website
location
age
visits member for 3 years, 7 months
seen Sep 17 at 10:09

Jun
21
comment Limit incoming connections using iptables per IP
Hm, never seen hashlimit while googling. But I don't understand how it works: iptables -I INPUT -p tcp --dport 22 -m state --state NEW -m hashlimit --hashlimit-name SSH --hashlimit-mode srcip --hashlimit-above 5/min -j REJECT this call does not trap any command, while iptables -I INPUT -p tcp --dport 22 -m state --state NEW -m hashlimit --hashlimit-name SSH --hashlimit-mode srcip --hashlimit 5/min -j REJECT traps all new connections...
Jun
21
comment Limit incoming connections using iptables per IP
yes, incoming IP are unknown
Jun
20
asked Limit incoming connections using iptables per IP
Apr
23
comment bind (hardlink) one directory to many places
Note, that I've 2000 chrooted folders and I don't want to have 2000 mount records in /etc/fstab. While 2000 hardlinks are not a problem. Or may be 2000 mounts are not a problem for Linux kernel?
Apr
23
comment bind (hardlink) one directory to many places
I know this, but I asked for "filesystem way". Is there some?
Apr
23
asked bind (hardlink) one directory to many places
Mar
8
comment Redirect with iptables if destination port is not listened
Thanks! That is exactly what I wanted!
Mar
8
awarded  Scholar
Mar
8
accepted Redirect with iptables if destination port is not listened
Mar
8
comment Redirect with iptables if destination port is not listened
Good idea, I thought about some ngnix or other proxy. Before accepting this solution I would like to see if any other ideas would come. May be iptables nf queue would be more simple?
Mar
8
awarded  Supporter
Mar
8
awarded  Student
Mar
7
asked Redirect with iptables if destination port is not listened