Hello,
Just to clear up a few things. We are not running any route optimization
software (ever). The reason we "refused" to help is because we were not
going to contact our transit providers NOC regarding other parties
routes, even if we did they wouldn't be of assistance.
We are purely pass
2018 14:50
To: nanog@nanog.org
Subject: Re: BGP Hijack/Sickness with AS4637
Hi,
Well bad news on the ColoAU front, they refused to cooperate.
We'll pushback thru our GTT accounts... But I'm running out of ideas.
If anyone has any good ideas how to proceed at this
ind.
Chris Conn
AS16532
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Tom Paseka via NANOG
Sent: Friday, May 25, 2018 6:01 PM
To: Nikolas Geyer
Cc: NANOG list
Subject: Re: BGP Hijack/Sickness with AS4637
This looks like a route that has been cached
ind.
Chris Conn
AS16532
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Tom Paseka via NANOG
Sent: Friday, May 25, 2018 6:01 PM
To: Nikolas Geyer
Cc: NANOG list
Subject: Re: BGP Hijack/Sickness with AS4637
This looks like a route that has been cached
Of Nikolas Geyer
Sent: Friday, May 25, 2018 11:59 AM
To: aheb...@pubnix.net
Cc: NANOG list
Subject: Re: BGP Hijack/Sickness with AS4637
Greetings!
Actually, what you have provided below shows the exact opposite. It shows
ColoAU have received the route from 4637 who have received it from 3257 who
Hi,
Looks like it was a RIB<->FIB bug in part.
How: BGP Optimizator maybe a culprit, but without insights from
ColoAU it is hard to say.
Thank to Job, Mark, Tracey for their time.
-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Cha
On Thu, May 31, 2018 at 02:40:06PM +, Job Snijders wrote:
> Upon further inspection, it seems more likely that the bgp optimiser is
> in ColoAU's network. Given the scale of AS 4637, if it were deployed
> inside Telstra I'd expect more problem reports. AS 4637 may actually
> just be an innocent
On 31/May/18 16:31, Alain Hebert wrote:
>
> PS: Still curious how, beside some RIB/FIB failure, how our AS
> ended up there.
We've suffered this many times as well, particularly when records show
up on HE's BGP tool.
It's a b**ch to get fixed, because too many fingers get pointed, and
fol
On Thu, May 31, 2018 at 10:31:26AM -0400, Alain Hebert wrote:
> Thanks for the ideas and the hint. Good read.
>
> Will do.
Upon further inspection, it seems more likely that the bgp optimiser is
in ColoAU's network. Given the scale of AS 4637, if it were deployed
inside Telstra I'd expect more p
On 31/May/18 16:15, Job Snijders wrote:
> I recommend you reach out to AUSNOG and APOPS and hope someone there
> knows someone at Telstra Hong Kong.
I have a friend at Telstra HKG. He's not in the IP team, but he can
summon a warm body if needed.
Mark.
Thanks for the ideas and the hint. Good read.
Will do.
PS: Still curious how, beside some RIB/FIB failure, how our AS
ended up there.
-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H
On Thu, May 31, 2018 at 09:49:47AM -0400, Alain Hebert wrote:
> Well bad news on the ColoAU front, they refused to cooperate.
>
> We'll pushback thru our GTT accounts... But I'm running out of ideas.
>
> If anyone has any good ideas how to proceed at this point feel free to
> share =D.
This fee
an IX? If so, did you learn the route from
route servers or do you peer directly with them?
Phil
-Original Message-
From: NANOG On Behalf Of Alain Hebert
Sent: 31 May 2018 14:50
To: nanog@nanog.org
Subject: Re: BGP Hijack/Sickness with AS4637
Hi,
Well bad news on the Co
.org] On Behalf Of Tom Paseka via NANOG
Sent: Friday, May 25, 2018 6:01 PM
To: Nikolas Geyer
Cc: NANOG list
Subject: Re: BGP Hijack/Sickness with AS4637
This looks like a route that has been cached by some ISPs/routers even though a
withdrawal has actually happened.
If you actually forward p
This looks like a route that has been cached by some ISPs/routers even
though a withdrawal has actually happened.
If you actually forward packets a long the path, you'll see its not
following the AS Path suggested, instead the real route that it should be.
Bouncing your session with 4637 would lik
Greetings!
Actually, what you have provided below shows the exact opposite. It shows
ColoAU have received the route from 4637 who have received it from 3257 who
have received it from 29909 who have received it from 16532 who originated it.
It infers nothing about who 16532 found the route to co
Hi,
We're looking for a contact, *that works*, to get in touch with
AS4637 (Telstra/HK) about some hijacking or router sickness.
BGPmon has been reporting an hijack of AS3's subnet 18.29.238.0/23.
After being contacted by AS3, we went over the advertisement with
AS29909 and
17 matches
Mail list logo
