[178279] in North American Network Operators' Group
Re: v6 deagg
daemon@ATHENA.MIT.EDU (Owen DeLong)
Tue Feb 24 12:30:10 2015
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CAL9jLabkt40PqY27Nmty8w1OzoXb6vGjmpbnOYtfXoaL936cFw@mail.gmail.com>
Date: Tue, 24 Feb 2015 09:27:59 -0800
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: North American Network Operators' Group <nanog@nanog.org>,
manning bill <bmanning@isi.edu>
Errors-To: nanog-bounces@nanog.org
> On Feb 19, 2015, at 21:25 , Christopher Morrow =
<morrowc.lists@gmail.com> wrote:
>=20
> On Thu, Feb 19, 2015 at 10:16 PM, manning bill <bmanning@isi.edu> =
wrote:
>> and then there are the loons who will locally push /64 or longer, =
some of which may leak.
>>=20
>=20
> 2001:2b8:46:bbbb::/64
> ... a fairly extensive list actually....
>=20
>> show route table inet6.0 | grep ^2 | except /4[876543210] | except /3 =
| except /2 | count
> Count: 297 lines
>=20
> Some are likely my local network's interfaces (so skip ~50 or so? to
> be generous) and some might be my provider's customers? (but they
> shouldn't send me shorter than a /48, right?)
>=20
> -chris
> (note on another observation point I don't see this sort of thing so
> perhaps it's just one upstream in a collection... I'll ask them
> seperately)
Your regular expression will not only count /49 and longer, it will also =
count /19 and shorter.
In my routing table, there are at least some examples of such routes.
Owen
