Menu

#2 new feature (blocking single port)

Next Release
open
5
2007-04-20
2007-04-05
No

Maybe it could be better to add an optional param when blocking ip's like the port number, usually it's ok to block all the server to the offender but sometimes you just want to block the offender (or client) to the specific port he's abusing/attacking . I've made that modification to my installations but I hope this could be a feature added in the next release :)

Discussion

  • Max Schubert

    Max Schubert - 2007-04-20

    Logged In: YES
    user_id=458935
    Originator: NO

    Nice idea! Do you do this through your triggered action script? If so and you are interested in contributing I would be happy to include your script in the distribution (you will get full credit in the script and the project for your contribution).

    If you are not interested in contributing, I will be happy to add this capability to the included iptables fw wrapper script.

     
  • Max Schubert

    Max Schubert - 2007-04-20
    • labels: --> action triggers
    • milestone: --> Next Release
    • assigned_to: nobody --> perldork
    • status: open --> pending
     
  • Mauricio Terrats

    • status: pending --> open
     
  • Mauricio Terrats

    fw modified to block specific ports

     
  • Mauricio Terrats

    Logged In: YES
    user_id=8655
    Originator: YES

    It needs some work since my bash scripting is not good enough :) but here it goes, Im uploading a modified version of /actions/fw called fw.sh which I call like fw drop|allow xxx.xxx.xxxx.xxx [port] , this file on "drop" only echo's what it needs to be done. If you remove the echos it will start blocking on particular ports if specified but I couldn't hack the "allow" in order to delete the rule of that specific port... but I do know you can do it ;)
    File Added: fw.sh

     

Log in to post a comment.

MongoDB Logo MongoDB