Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Daniel Dvořák" <dandee@hellteam.net>
To: netfilter@vger.kernel.org
Subject: logdrop rule does not work any more
Date: Fri, 16 May 2008 17:40:25 +0200	[thread overview]
Message-ID: <482DAAE9.80708@hellteam.net> (raw)

Hi all,
 
I haven´t found any hint about my problem so I would like to ask about 
logdrop rule.
 
I had iptables 1.3.6 from Debian Etch distro and I use logdrop rule like 
these rules:
 
ipt="/sbin/iptables"
 
modprobe ip_conntrack
modprobe ip_conntrack_ftp
modprobe ipt_MASQUERADE
modprobe ipt_state
 
$ipt -P INPUT ACCEPT
$ipt -P OUTPUT ACCEPT
$ipt -P FORWARD ACCEPT
$ipt -P logdrop ACCEPT
 
$ipt -F INPUT
$ipt -F OUTPUT
$ipt -F -t nat
$ipt -F -t mangle
$ipt -F logdrop
 
$ipt -X logdrop
$ipt -N logdrop
$ipt -A logdrop -j LOG --log-prefix "logdrop"
$ipt -A logdrop -j DROP
...
$ipt -t mangle -A POSTROUTING -p tcp --dport 25 -j logdrop ... for example
 
It worked fain until I had to compile new iptables version 1.4.0 and my 
problem has appeared every time when I start my firewall script.
 
The error message is here:
 
iptables: Bad built-in chain name
iptables v1.4.0: Couldn't load target 
`logdrop':/usr/local/lib/iptables/libipt_logdrop.so: cannot open shared 
object file: No such file or directory
 
Try `iptables -h' or 'iptables --help' for more information.
I do not know why during the compilation of new iptables, there is not 
libipt_logdrop.so module while in version 1.3.6 there had to be in 
directory, because no errors ever appeared.
 
In changelog from 1.3.6 to 1.4.0, there is no information about 
cancelling logdrop support.
 
So where is the problem ?
What do I do in wrong way ?
 
Thank you.
 
Dan
 
P.S.: I am not subscribed in mailling list, mail me directly please.

             reply	other threads:[~2008-05-16 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 15:40 Daniel Dvořák [this message]
2008-05-16 16:00 ` logdrop rule does not work any more Gáspár Lajos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=482DAAE9.80708@hellteam.net \
    --to=dandee@hellteam.net \
    --cc=netfilter@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox