From: Arnt Karlsen <arnt@c2i.net>
To: netfilter@lists.netfilter.org
Subject: Re: Unassigned Networks List
Date: Tue, 11 Mar 2003 23:33:05 +0100 [thread overview]
Message-ID: <20030311233305.6c118b6d.arnt@c2i.net> (raw)
In-Reply-To: <20030308140703.GB2652@placemark.com>
On Sat, 8 Mar 2003 08:07:03 -0600,
Kelly Setzer <Kelly.Setzer@placemark.com> wrote in message
<20030308140703.GB2652@placemark.com>:
> On Sat, Mar 08, 2003 at 01:03:50PM +0100, Arnt Karlsen wrote:
> > On 08 Mar 2003 00:48:47 -0600,
> > Daniel Wittenberg <daniel-wittenberg@starken.com> wrote in message
> > <1047106127.2050.56.camel@runabout.noc.starken.com>:
> >
> > > firewall, so we couldn't ping the provider. I subsequently got in
> > > an"discussion" with their CTO about RFC 1918 on how it's probably
> > > not good to be using private IP's to route public traffic, at
> > > least IMHO.
> >
> > ..such discussions are better taken in public, so the hotshot can
> > show off his alledged competence... ;-)
>
> When @home was just getting off the ground, they used to expose 10/8
> addresses. I was talking to a first or second level network engineer,
> and he *INSISTED* that 10/8 has been assigned to @home.
>
> ha
..but he is _right_, even I use it here at _my_ home,
and, I even have 192.168/16 and 172.16/12. ;-)
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
next prev parent reply other threads:[~2003-03-11 22:33 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
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 [this message]
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=20030311233305.6c118b6d.arnt@c2i.net \
--to=arnt@c2i.net \
--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