Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Adam D. Barratt" <netfilter.list@adam-barratt.org.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Spoofed ip's
Date: Wed, 12 Feb 2003 08:56:11 -0000	[thread overview]
Message-ID: <0e1701c2d274$972e04d0$eb00010a@andromeda> (raw)
In-Reply-To: 1044948351.23287.11.camel@filth.sadomain.co.za

deff wrote, Tuesday, February 11, 2003 7:25 AM:
[...]
> Then i took a look at Firestarter's iptables script and saw that
> it also filters out other addresses.

> Could anyone please check the rules below and tell me if the
> the source ip'ss are valid. I'm seeing an incredible amount of
> these ip's attempting to get through .

> To me it looks like i'm blocking out the whole internet, but that
> makes me wonder why firestarter does it .

If you're going to bother doing this, at least do it properly. Don't use
someone else's list, as some of them are outdated and therefore, as in this
case, *wrong*.

At a quick glance, 69/8, 81/8, 82/8, 219/8, 220/8 and 221/8 are *not*
reserved. Some of them haven't been for nearly two years now.

http://www.iana.org/assignments/ipv4-address-space is the official
reference, which is kept up-to-date, and should be checked every so often
(alternatively, one could subscribe to the bogon announcement list).

Adam



      parent reply	other threads:[~2003-02-12  8:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-11  7:25 Spoofed ip's deff
2003-02-11 15:56 ` uniplex
2003-02-12  1:28   ` Arnt Karlsen
2003-02-12  8:51     ` Adam D. Barratt
2003-02-11 17:09 ` Athan
2003-02-11 19:22 ` Gastón Franco
2003-02-12  8:56 ` Adam D. Barratt [this message]

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='0e1701c2d274$972e04d0$eb00010a@andromeda' \
    --to=netfilter.list@adam-barratt.org.uk \
    --cc=netfilter@lists.netfilter.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