News for hackers. Stuff that matters.

A comment on BGP super-blunder: How Verizon sparked a ‘cascading catastrophic failure’.

Re:BGP super-blunder: How Verizon sparked a ‘cascading catas... by neuronflux on Tuesday August 13, 2019 @01:08PM (#20687825)
BGP filters fix this. Only accept routes from customers for IP space that they control.

I imagine Verizon has some sort of webUI with bad defaults (no filter) so that their helpdesk can setup new customers - Hanlon's razor being what it is.

[ Parent | on HN ]
Re:BGP super-blunder: How Verizon sparked a ‘cascading catas... by icedchai on Tuesday August 13, 2019 @01:21PM (#20687994)
I remember setting up a T1 in the mid 90's. Our upstream was InternetMCI. There was no Web UI. There was no documentation of any sort. The guy (MCI tech) just had me read him routes over the phone and he announced them. Fun times!
[ Parent | on HN ]
Re:BGP super-blunder: How Verizon sparked a ‘cascading catas... by yusyusyus on Tuesday August 13, 2019 @04:09PM (#20689708)
easier explanation is that they were doing troubleshooting and had removed the filter to do that.
[ Parent | on HN ]
Re:BGP super-blunder: How Verizon sparked a ‘cascading catas... by icedchai on Tuesday August 13, 2019 @06:34PM (#20690945)
In the early days, some upstream ISPs did no filtering. You could announce anything.
[ Parent | on HN ]