Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
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!...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353

    Oh, if he didn't overwrite the sysconfig file, right, I see what you mean. A reboot might fix it!

  2. #12
    Just Joined!
    Join Date
    Nov 2011
    Posts
    66
    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
    Code:
    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
    Later i restarted iptables

    Code:
    iptables -Lnv
    iptables: No chain/target/match by that name.
    I thought i lost all the rules. So again i tried to add

    Code:
    iptables -p input drop
    So I am locked from SSH access?

  3. #13
    Just Joined!
    Join Date
    Nov 2011
    Posts
    66
    After restarting, I got access.

    Code:
    service iptables start
    iptables -Lnv
    No chain/target/match by that name.

    Code:
    iptables -D input -i eth0 -p tcp --dport 80 -j accept
    iptables v1.4.7: Couldn't load target `accept':/lib64/xtables/libipt_accept.so: cannot open shared object file: No such file or directory

    Does it make any sense?
    I don't know whether my rules are there.

  4. $spacer_open
    $spacer_close
Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •