Results 11 to 13 of 13
Oh, if he didn't overwrite the sysconfig file, right, I see what you mean. A reboot might fix it!...
- 12-01-2011 #11Linux Guru
- Join Date
- May 2011
- Posts
- 1,843
Oh, if he didn't overwrite the sysconfig file, right, I see what you mean. A reboot might fix it!
- 12-01-2011 #12Just Joined!
- Join Date
- Nov 2011
- Posts
- 65
Code:iptables -p input drop
Code:iptables -a input i eth0 -p tcp --dport 80 -j accept
Code:iptables -a input i eth0 -p tcp --dport 8080 -j accept
Later i restarted iptablesCode:iptables -A INPUT -p tcp --dport 22 -m recent --set --name ssh --rsource iptables -A INPUT -p tcp --dport 22 -m recent ! --rcheck --seconds 60 --hitcount 4 --name ssh --rsource -j ACCEPT
I thought i lost all the rules. So again i tried to addCode:iptables -Lnv iptables: No chain/target/match by that name.
So I am locked from SSH access?Code:iptables -p input drop
- 12-01-2011 #13Just Joined!
- Join Date
- Nov 2011
- Posts
- 65
After restarting, I got access.
iptables -LnvCode:service iptables start
No chain/target/match by that name.
iptables v1.4.7: Couldn't load target `accept':/lib64/xtables/libipt_accept.so: cannot open shared object file: No such file or directoryCode:iptables -D input -i eth0 -p tcp --dport 80 -j accept
Does it make any sense?
I don't know whether my rules are there.


Reply With Quote