[33102] in North American Network Operators' Group
Re: RFC1918 addresses to permit in for VPN?
daemon@ATHENA.MIT.EDU (John Fraizer)
Fri Dec 29 13:03:29 2000
Date: Fri, 29 Dec 2000 12:57:10 -0500 (EST)
From: John Fraizer <nanog@EnterZone.Net>
To: Andrew Brown <atatat@atatdot.net>
Cc: nanog@merit.edu
In-Reply-To: <20001229125342.A29733@noc.untraceable.net>
Message-ID: <Pine.LNX.4.21.0012291255210.22358-100000@Overkill.EnterZone.Net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
Oh, you're quite right. So, the moral of this story is:
If you want your network to look right and act right, don't use 1918 space
on your routers.
---
John Fraizer
EnterZone, Inc
On Fri, 29 Dec 2000, Andrew Brown wrote:
> imho, that just makes bt look even worse. now, instead of using
> things they shouldn't, they've got a large "broken" network.
>
> On Fri, Dec 29, 2000 at 12:50:43PM -0500, John Fraizer wrote:
> >
> >
> >Block traffic sourced from 1918 space at the borders like all good
> >providers should do and it looks more like this:
> >
> >11 transit1-pos10-3.ilford.ukcore.bt.net (194.74.16.245) 105.436 ms 104.467 ms 110.371 ms
> >12 core2-gig3-0.ilford.ukcore.bt.net (194.74.16.111) 109.295 ms 105.359 ms 107.466 ms
> >13 core2-pos10-0.bletchley.ukcore.bt.net (62.6.196.221) 107.255 ms 107.344 ms 109.345 ms
> >14 vhsaccess1-pos8-0.bletchley.fixed.bt.net (62.6.197.138) 107.308 ms 105.954 ms 111.282 ms
> >15 213.120.207.222 (213.120.207.222) 107.333 ms 106.454 ms 105.460 ms
> >16 * * *
> >17 * * *
> >18 213.120.62.61 (213.120.62.61) 106.933 ms 109.007 ms 111.363 ms
> >19 * * *
> >20 * * *
> >21 * * *
> >22 * * *
> >23 * * *
> >24 * * *
> >25 * * *
> >26 * * *
> >27 * * *
> >28 * * *
> >29 * * *
> >30 * * *
> >
> >
> >
> >---
> >John Fraizer
> >EnterZone, Inc
