----- Original Message -----
From: "Mike Lander" <[EMAIL PROTECTED]>
To: "Shorewall" <[email protected]>
Sent: Monday, August 27, 2007 9:50 AM
Subject: [Shorewall-users] Error Parsing SSHKnock with Shorewall Per
: Hello to the list,
: I have an error driving me crazy. I noticed there are no
: comma's in the script. OR is there a fix for this?
:
: Compiling /etc/shorewall/rules...
: ERROR: Couldn't parse /etc/shorewall/SSHKnock: Bad name after SSHKnock'
: at (eval 6) line 15, <$currentfile> line 39.
: : /etc/shorewall/rules (line 39)
: ns5:/var/log/samba # uname -r
: 2.6.18.8-0.5-default
: ns5:/var/log/samba # shorewall version
: 4.0.2
: ns5:/var/log/samba #
: ------------------------------------------------I believe the error is in
: this script: Note I added commas
: has the same error?
: use Shorewall::Chains;
:
: if ( $level ) {
: log_rule_limit( $level,
: $chainref,
: 'SSHKnock',
: 'ACCEPT',
: '',
: $tag,
: 'add',
: '-p tcp --dport 22 -m recent --rcheck --name SSH );
:
: log_rule_limit( $level,
: $chainref,
: 'SSHKnock,
: 'DROP',
: '',
: $tag,
: 'add',
: '-p tcp --dport ! 22' );
: }
:
: add_rule( $chainref, '-p tcp --dport 22 -m recent --rcheck --seconds
: 60 --name SSH -j ACCEPT' );
: add_rule( $chainref, '-p tcp --dport 1599 -m
: --name SSH --remove -j DROP' );
: add_rule( $chainref, '-p tcp --dport 1600 -m
: --name SSH --set -j DROP' );
: add_rule( $chainref, '-p tcp --dport 1601 -m
: --name SSH --remove -j DROP' );
:
: 1;
: Thank you,
: Mike
Sorry for the double post
my flavor is Open Suse 10.2
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
