Hi all,
Thank you for your replies, we ended up finding a left over ingress filter on
one of our upstreams.
Regards, Michel
> On 25 Mar 2023, at 15:41, Aaron Gould wrote:
> i traced to it, and it wasn't responding at first, then later it worked
>
yeah i see what you mean by, it doesn't work, then it starts working...
i traced to it, and it wasn't responding at first, then later it worked
C:\>tracert -w 1 86.104.228.1
Tracing route to 86.104.228.1 over a maximum of 30 hops
...
9 118 ms * 119 ms prs-bb1-link.ip.twelve99.n
On Sat, Mar 25, 2023 at 1:54 AM ic wrote:
> Do you all have any idea what I should check / try next?
A good tool for diagnosing BGP problems is:
https://www.routeviews.org/routeviews/
While the problem is occurring, pick some of the collector hosts from
https://www.routeviews.org/routeviews/ind
One more thing: it seems that no matter what, the prefix is always reachable
from AS3257 which makes the whole thing even weirder.
> On 25 Mar 2023, at 09:54, ic wrote:
>
> Hi there,
>
> I’m contacting you because after spending 2 days troubleshooting I can’t seem
> to find a solution to the
Hi there,
I’m contacting you because after spending 2 days troubleshooting I can’t seem
to find a solution to the following.
We (AS45021) bought/transffered the 86.104.228.0/24 prefix a few months back
because we couldn’t wait longer on the RIPE waiting list.
Before you ask, yes, AS45021 is cu
5 matches
Mail list logo
