Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Sascha Reissner" <sascha.reissner@toxicnet.de>
To: "George J. Jahchan, Eng." <NetFilter-Users@Compucenter.org>,
	Netfilter <netfilter@lists.netfilter.org>
Cc: "Gokarn, Pavan" <PavanG@TechKnowledge.ws>
Subject: Re: Unassigned Networks List
Date: Sat, 8 Mar 2003 07:39:18 +0100	[thread overview]
Message-ID: <000701c2e53d$72cc42b0$026410ac@honor> (raw)
In-Reply-To: NGBBIFPIJNDPMFBPKBPGOEJIDKAA.NetFilter-Users@Compucenter.org

From: "George J. Jahchan, Eng." <NetFilter-Users@Compucenter.org>

[...]

> 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.

[...]

so you plan on checking currently unassigned ip blocks on a daily base just
in case some ISP suddenly gets such a block assigned?

well, there are for sure some efford/reward relations that are not worth
doing.. this is one of them ;)

if you want security, unplug the network cable ;-)




  reply	other threads:[~2003-03-08  6:39 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 ` Unassigned Networks List George J. Jahchan, Eng.
2003-03-08  6:39   ` Sascha Reissner [this message]
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='000701c2e53d$72cc42b0$026410ac@honor' \
    --to=sascha.reissner@toxicnet.de \
    --cc=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