Some Cox customers reported they were not able to reach one of our IPv6
prefixes, including more specifics announced by different ASNs. I
suspect the whole range is blackholed or something.
```
mtr -r -c1 -w 2a12:dd44::1
Start: 2022-08-25T18:09:50-0700
HOST: ronsor-lg-arch
I couldn't really figure out why things where behaving so weird today
until now when you mentioned this and I had a look and realized my
firewall also picked up an ipv6 address with broken routing.
This is in the NJ area.
/T
On 2022-08-25 15:31, Rob Foehl wrote:
Maintenance outage last night,
https://datatracker.ietf.org/doc/html/draft-ietf-grow-as-path-prepending
Cheers,
Jeff
> On Aug 25, 2022, at 11:00, Tom Beecher wrote:
>
>
>
>> Usually What shoud we do ? Should we filter it ?
>
>
> As with many things, the answer depends on your situation.
>
> If I was running an edge
Maintenance outage last night, PD woke up shortly afterward and collected
a /56, no joy after that -- egress traffic gets where it's going, ingress
is dropped not far into 701. Only visible covering route is the
2600:4000::/24 aggregate, both externally and via Verizon's looking glass.
It
> Usually What shoud we do ? Should we filter it ?
>
As with many things, the answer depends on your situation.
If I was running an edge device with a limited FIB, perhaps I might drop
it to save memory. If I had beefier devices, perhaps I would just depref
it. Maybe it's a prefix/source ASN I
I would imagine the "long as-path" one would handle excessive prepends
too, right?
50 prepends is silly but doesn't really hurt my feelings. But >100 is absurd.
--
Hunter Fuller (they)
Router Jockey
VBH M-1C
+1 256 824 5331
Office of Information Technology
The University of Alabama in
Hello Alistair,
Are you sure there is one about excess prepends?. I just took a look
and I did not find any.
I found one about filtering long as-paths but not specifically about
prepends.
Thanks,
Alejandro,
On 25/8/22 10:31 AM, Alistair Mackenzie wrote:
There are some generally
On Thu, 25 Aug 2022, 16:31 Alistair Mackenzie, wrote:
> There are some generally accepted and useful filters found at
> https://bgpfilterguide.nlnog.net/. There is one which covers excess
> prepends.
>
It's generally accepted to filter **very** long as paths.
As Alistair pointed to. The guide
BGPLay works pretty well.
https://stat.ripe.net/about/
From: NANOG On
Behalf Of Jacques Latour
Sent: Tuesday, August 23, 2022 2:17 PM
To: NANOG
Subject: BGP Visualization with Software Galaxies
I was looking for a functional version of a BGP visualisation tool like the one
at NTT
There are some generally accepted and useful filters found at
https://bgpfilterguide.nlnog.net/. There is one which covers excess
prepends.
On Thu, 25 Aug 2022 at 15:25, anonymous wrote:
> Hey everyone,
>
> Too many hops found as below.
> Usually What shoud we do ? Should we filter it ?
>
>
Hey everyone,
Too many hops found as below.
Usually What shoud we do ? Should we filter it ?
91.246.12.0/24
AS path: 4788 9002 41313 51196 51196 51196 51196
51196 51196 51196 51196 51196 51196 51196 51196 51196 51196 51196 51196
51196 51196 51196 51196 51196 51196 51196
11 matches
Mail list logo
