From: "George J. Jahchan, Eng." <NetFilter-Users@Compucenter.org>
To: Netfilter <netfilter@lists.netfilter.org>
Cc: "Gokarn, Pavan" <PavanG@TechKnowledge.ws>
Subject: RE: Unassigned Networks List
Date: Sat, 8 Mar 2003 07:51:44 +0200 [thread overview]
Message-ID: <NGBBIFPIJNDPMFBPKBPGOEJIDKAA.NetFilter-Users@Compucenter.org> (raw)
In-Reply-To: <007201c2e2d7$4c6552f0$e11310ac@techknowledge.ws>
Pavan,
I am trying to block RFC1918 networks, in addition to unassigned ones (IANA
reserved or not assigned) from getting in or out on the public interface.
Any traffic coming in (or leaving) from such networks on the public
interface undoubtedly has a spoofed source IP and should be dropped.
As mentioned before, classes A & D networks are fairly well documented on
IANA's site <http://www.iana.org/assignments/ipv4-address-space>, but B and
C are listed as "various registries" and in bulk, which is of no help.
I need a list of 128~191 and 192~223 netblocks which are either reserved or
not assigned.
Site filtering based on content classification is an entirely different
matter that is best handled at the http proxy level, and is of no relevance
here.
Thank you for any help,
Regards,
George.
-----Original Message-----
From: Pavan Gokarn [mailto:pavang@techknowledge.ws]
Sent: Wednesday, March 05, 2003 7:23 AM
To: George J. Jahchan, Eng.
Subject: Re: Unassigned Networks List
what do you want to do george. do u want to block some sites which are
bad(porn) or block a range of specific ip addresses. in the former case I
might me able to help you.
regards
next parent reply other threads:[~2003-03-08 5:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <007201c2e2d7$4c6552f0$e11310ac@techknowledge.ws>
2003-03-08 5:51 ` George J. Jahchan, Eng. [this message]
2003-03-08 6:39 ` Unassigned Networks List Sascha Reissner
2003-03-08 6:48 ` Daniel Wittenberg
2003-03-08 12:03 ` Arnt Karlsen
2003-03-08 14:07 ` Kelly Setzer
2003-03-11 22:33 ` Arnt Karlsen
2003-03-16 17:37 ` nbastin
2003-03-12 21:25 Jason Opperisano
-- strict thread matches above, loose matches on Subject: below --
2003-03-05 3:16 George J. Jahchan, Eng.
2003-03-05 14:52 ` Jeremy Jones
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=NGBBIFPIJNDPMFBPKBPGOEJIDKAA.NetFilter-Users@Compucenter.org \
--to=netfilter-users@compucenter.org \
--cc=PavanG@TechKnowledge.ws \
--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