Re: AW: AW: Prefix-Hijack by AS7514

2015-07-17 Thread Mark Tinka
On 17/Jul/15 11:46, Matsuzaki Yoshinobu wrote: > Yes, I agree, and we have done that. How about peering partners - > which is our case this time. Is it feasible to maintain strict > inbound prefix filters for all peering relationships? To be honest, not really. Some countries I know do this f

Re: AW: AW: Prefix-Hijack by AS7514

2015-07-17 Thread Matsuzaki Yoshinobu
Colin Johnston wrote > even if customer router crash fault, should have been filtered via > prefix list blocking to only allow customer network prefixs to be > anounced onwards ? as per best practice Yes, I agree, and we have done that. How about peering partners - which is our case this time.

Re: AW: AW: Prefix-Hijack by AS7514

2015-07-17 Thread Colin Johnston
even if customer router crash fault, should have been filtered via prefix list blocking to only allow customer network prefixs to be anounced onwards ? as per best practice colin Sent from my iPhone > On 17 Jul 2015, at 09:55, Matsuzaki Yoshinobu wrote: > > Colin Johnston wrote >> any idea w

Re: AW: AW: Prefix-Hijack by AS7514

2015-07-17 Thread Matsuzaki Yoshinobu
Colin Johnston wrote > any idea why error happened ? > what config needs fixing to mitigate mistake? > it was easy to see problem via ripe atlas :) I just got brief explanation from a friend in AS7514. A router in their network suddenly went out of control, and it seems this somehow generated wr

Re: AW: AW: Prefix-Hijack by AS7514

2015-07-17 Thread Colin Johnston
any idea why error happened ? what config needs fixing to mitigate mistake? it was easy to see problem via ripe atlas :) colin Sent from my iPhone > On 17 Jul 2015, at 09:32, Matsuzaki Yoshinobu wrote: > > Date: Fri, 17 Jul 2015 15:38:13 +0900 > "Paul S." wrote >> I let IIJ know too, hopefull

Re: AW: AW: Prefix-Hijack by AS7514

2015-07-17 Thread Matsuzaki Yoshinobu
Date: Fri, 17 Jul 2015 15:38:13 +0900 "Paul S." wrote > I let IIJ know too, hopefully they'll filter it soon. It seems AS7514 stopped the announcements around 06:54UTC. I am not sure how BGPmon guesses AS relationships, but it needs improvements as it shows IIJ as an upstream of AS7514 wrongly.

Re: AW: AW: Prefix-Hijack by AS7514

2015-07-16 Thread Paul S.
I let IIJ know too, hopefully they'll filter it soon. On 7/17/2015 午後 03:30, Jürgen Jaritsch wrote: Hi, we also sent them an mail, but their MX is not reachable for us :( best regards Jürgen Jaritsch Head of Network & Infrastructure ANEXIA Internetdienstleistungs GmbH Telefon: +43-5-0556-3