On Tue, Feb 24, 2015 at 12:27 PM, Owen DeLong <o...@delong.com> wrote:
>
>> On Feb 19, 2015, at 21:25 , Christopher Morrow <morrowc.li...@gmail.com> 
>> wrote:
>>
>> On Thu, Feb 19, 2015 at 10:16 PM, manning bill <bmann...@isi.edu> wrote:
>>> and then there are the loons who will locally push /64 or longer, some of 
>>> which may leak.
>>>
>>
>> 2001:2b8:46:bbbb::/64
>> ... a fairly extensive list actually....
>>
>>> show route table inet6.0 | grep ^2 | except /4[876543210] | except /3 | 
>>> except /2 | count
>> Count: 297 lines
>>
>> 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?)
>>
>> -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.

yup, not very many and I think not enough to matter over all, give
then actual point was I see many smaller (longer?) than /48 in the
table.

Reply via email to