Re: Cymru Bogon AS path change

2013-09-16 Thread Rabbi Rob Thomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, NANOGers. > We're a bit past our change window, and my apologies for that. We're > almost at the finish line, however, so I'll beg your indulgences while > we wind it up. We've completed the change and all looks migrated and happy. The change w

Re: Cymru Bogon AS path change

2013-09-16 Thread Rabbi Rob Thomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi again, NANOGers. > My apologies! We had a configuration "oops" during a migration to a new > back-end infrastructure. We're working through that now, and I believe > we have it sorted. I'll send out a more gory detailed update in a bit. We're m

Re: Cymru Bogon AS path change

2013-09-16 Thread Rabbi Rob Thomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, NANOGers. > Did anyone else notice that the path changed from 65332 to 65332 65331 > earlier today? My apologies! We had a configuration "oops" during a migration to a new back-end infrastructure. We're working through that now, and I believe w

Cymru Bogon AS path change

2013-09-16 Thread Ben Bartsch
Did anyone else notice that the path changed from 65332 to 65332 65331 earlier today? We certainly did when we starting advertising all the bogons to our ISP peers. Probably should have had an inbound AS path filter on that cymru peering...

Re: Cymru Bogon AS path change

2013-09-16 Thread Nick Hilliard
On 16/09/2013 18:01, Ben Bartsch wrote: > We certainly did when we starting advertising all the bogons to our ISP > peers. Probably should have had an inbound AS path filter on that cymru > peering... better still, tag them all with a BGP community to make a note that they are bogons from Cymru (