Home Forums SecAst (Security for Asterisk) Configuration & Optimization IP’s not blocked despite SecAst saying they are

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • Avatar photoCustomer Inquiry
    Member
    Post count: 197

    SecAst says IP’s are being blocked but they’re not. They keep on attacking my system. I’m using iptables on the local machine to block attackers.

    Avatar photoTelium Support Group
    Member
    Post count: 258

    The most likely cause is that the banned IP’s are not being handled properly by the firewall. There is also a known issue with fail2ban – in case you are attempting to run fail2ban alongside SecAst.

    If you are using local IPtables to block attackers, ensure that the SECAST chain exists, and that the first rule on the INPUT chain jumps to target chain SECAST. For example, the command “iptables –L” should show something like:

    Chain INPUT (policy ACCEPT)
    target prot opt source destination
    SECAST all — anywhere anywhere
    Chain FORWARD (policy ACCEPT)
    target prot opt source destination
    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination
    Chain SECAST (1 references)
    target prot opt source destination
    RETURN all — anywhere anywhere

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.