[182454] in North American Network Operators' Group
Re: AW: AW: Prefix-Hijack by AS7514
daemon@ATHENA.MIT.EDU (Colin Johnston)
Fri Jul 17 05:17:33 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <20150717.175553.1297824131323484151.maz@iij.ad.jp>
From: Colin Johnston <colinj@gt86car.org.uk>
Date: Fri, 17 Jul 2015 10:17:23 +0100
To: Matsuzaki Yoshinobu <maz@iij.ad.jp>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
even if customer router crash fault, should have been filtered via prefix li=
st blocking to only allow customer network prefixs to be anounced onwards ? a=
s per best practice
colin
Sent from my iPhone
> On 17 Jul 2015, at 09:55, Matsuzaki Yoshinobu <maz@iij.ad.jp> wrote:
>=20
> Colin Johnston <colinj@gt86car.org.uk> wrote
>> any idea why error happened ?
>> what config needs fixing to mitigate mistake?
>> it was easy to see problem via ripe atlas :)
>=20
> I just got brief explanation from a friend in AS7514.
>=20
> A router in their network suddenly went out of control, and it seems
> this somehow generated wrong routing information. They solved the
> issue by disconnecting the router and are now investigating it.
> -----
> Matsuzaki Yoshinobu <maz@iij.ad.jp>
> - IIJ/AS2497 INOC-DBA: 2497*629
