James B. Byrne wrote:
>
> On Fri, January 8, 2010 15:32, James B. Byrne wrote:
>> I went to reload (iptables-restore) my iptables configuration and
>> obtained an error at the COMMIT statement. No further details were
>> provided even when I ran restore with the -v option.
>>
>
>
> I ran lsmod a
> Check out this TUTORIAL
> http://www.zoominternet.net/~lazydog/iptables-
> tutorial.html#RECENTMATCH
I do not seem to be making myself clear. I do not need a tutorial
on how to use the recent module of iptables. The recent module
itself seems not to be available on this particular host anymore
On Fri, January 8, 2010 15:32, James B. Byrne wrote:
> I went to reload (iptables-restore) my iptables configuration and
> obtained an error at the COMMIT statement. No further details were
> provided even when I ran restore with the -v option.
>
I ran lsmod and I do not find that ipt_recent is
On Friday 08 January 2010 15:32, James B. Byrne wrote:
> :BRUTE_FORCE - [0:0]
>
> . . .
> -A BRUTE_FORCE -p tcp -m tcp -m state -m recent --set -i eth0
> --dport 22 --state NEW
> -A BRUTE_FORCE -m comment -j RETURN --comment "Return to calling chain"
> COMMIT
Check out this TUTORIAL
http:
Quoting "James B. Byrne" :
> I went to reload (iptables-restore) my iptables configuration and
> obtained an error at the COMMIT statement. No further details were
> provided even when I ran restore with the -v option.
>
> I determined that none of my backed up configuration files going
> back to
I went to reload (iptables-restore) my iptables configuration and
obtained an error at the COMMIT statement. No further details were
provided even when I ran restore with the -v option.
I determined that none of my backed up configuration files going
back to October will load either. This is mor
6 matches
Mail list logo
