From: "Jeremy Jones" <jeremy@samnjack.com>
To: Netfilter <netfilter@lists.netfilter.org>
Subject: RE: Unassigned Networks List
Date: Wed, 5 Mar 2003 07:52:25 -0700 [thread overview]
Message-ID: <OCENLNBAGANFOEJAEAGOKEAFCAAA.jeremy@samnjack.com> (raw)
In-Reply-To: <NGBBIFPIJNDPMFBPKBPGGEBDDKAA.NetFilter-Users@Compucenter.org>
This should help:
http://www.iana.org/assignments/ipv4-address-space
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org]On Behalf Of George J.
Jahchan, Eng.
Sent: Tuesday, March 04, 2003 8:17 PM
To: Netfilter
Subject: Unassigned Networks List
I need to ingress/egress filter unassigned netblocks and I am having a very
hard time finding a comprehensive list of unassigned class B and C networks.
It is extremely time consuming to go through the different regional
registrars to come up with such a list, not to mention putting networks back
together to minimize the number of rules.
IANA has good class A and D lists, B and C classes are however listed "in
bulk" (next to useless). Searching through Google I came up empty handed.
Does anyone have a comprehensive list they are willing to share, or links to
sites that list these network blocks.
TIA
next prev parent reply other threads:[~2003-03-05 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 3:16 Unassigned Networks List George J. Jahchan, Eng.
2003-03-05 14:52 ` Jeremy Jones [this message]
[not found] <007201c2e2d7$4c6552f0$e11310ac@techknowledge.ws>
2003-03-08 5:51 ` George J. Jahchan, Eng.
2003-03-08 6:39 ` 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
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 21:25 Jason Opperisano
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=OCENLNBAGANFOEJAEAGOKEAFCAAA.jeremy@samnjack.com \
--to=jeremy@samnjack.com \
--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