Hi Luca -
Luca Olivetti wrote:
Since I was having problems with mandrake's standard kernel (since I
installed 9.0 I had a lot of lock ups -- maybe these are the cause of
the filesystem corruption I'm seeing now), I was compiling stock 2.4.19
kernel + xfs patches (all my filesystems are xfs).
The whole issue of portscanning is debatable, some people say it should
be illegal, and others saying it's not a crime to 'peek in the windows'
so to say. I won't really get into the debate, but there isn't much you
can do about people portscanning you. Only open the ports you
Just to add to this thread a bit, but blocking the IP where the portscan
may appear to come from isn't a guarantee you'll stop the portscans.
Popular port scanning software like nmap supports whats called 'Idle
Scanning' which bounce the scan's off 'zombie' hosts, tricking IDS's to
report the
Hi Hans -
What you're trying to do is actually a pretty common setup, which is
good, cus there are lots of examples. To save yourself some time, there
is a program that ships with mandrake called 'draknet' and could be
really helpfull for you. Its a nice utility that will walk you through
Hi Hans -
Try: insmod ip_tables
instead of iptables, that should work for ya.
Dan
http://five2one.org/
hans privat wrote:
hi,
in a sysadmin-book I've read, that with kernel 2.4 the iptables
should be used.
now I have done a lookup with lsmod and have seen, that there was NO
iptables but an
