Mon, 9 Aug 2004 17:58:59 +0100
On Monday 09 August 2004 5:40 pm, 'Me' wrote:
> I=92m having problems logging packets (IPTables: 1.2.8 Kernel: 2.4.8) w=
> the following rule (from the FAQ):
> iptables -N logdrop
> iptables -A logdrop -j LOG
> iptables -A logdrop -j DROP
> On the log line I get:
> iptables: No chain/target/match by that name
> I=92m a little lost =96 any pointers?
It seems unlikely, but has your kernel been compiled without support for =
LOG target (and by the way, why are you using a three year old kernel=20
Test one thing at a time:
1. Can you use the LOG target?
iptables -A INPUT -j LOG
2. Can you put a rule into a user-defined chain?
iptables -N logdrop
iptables -A logdrop -j DROP
If both the above tests work, then there is no reason you shouldn't be ab=
put a LOG target into your user-defined chain (so check very carefully th=
syntac of what you are typing when you get the error, etc).
If one of the above tests fails, you know where the problem is.
Just one last thing to check - you haven't compiled the userspace iptable=
tool without also recompiling the kernelspace netfilter part, have you?
If you do one of these, you should also do the other to match.
Microsoft may sell more software than any other company, but McDonald's s=
more burgers than any other company, and I think the other similarities a=
Please reply to the =
please don't C=