An update from Linode about the recent DDoS attacks

Re:An update from Linode about the recent DDoS attacks by scurvy on Saturday January 02, 2016 @12:44PM (#10826919)

Judging by the downvotes I got, there are people on HN that must think you should expose your router's control plane to the Internet. That or they expect transit providers to not protect their network.

There's no intelligent discussion left here. It's devolved into a sympathy vote. "You said something mean about Linode. I love Linode. Downvotes for you."

If Linode had posted the update to NANOG, it would have been more productive. I don't often say that.

[ Parent | on HN ]

Re:An update from Linode about the recent DDoS attacks by alexforster on Saturday January 02, 2016 @02:45PM (#10827571)

You may want to go pinging around some of your own tier 1 crossconnects. I bet you'll be surprised.

[ Parent | on HN ]

Re:An update from Linode about the recent DDoS attacks by scurvy on Saturday January 02, 2016 @04:34PM (#10828065)

They all respond because I asked them for it. About half didn't upon turn up. It's super trivial for them to null route them or readdress in rfc 1918/4193 space.

Or are you referring to xconnects inside their network? That's up to them to work out and I've never seen a provider just abandon their network while under attack.

[ Parent | on HN ]

Re:An update from Linode about the recent DDoS attacks by alexforster on Saturday January 02, 2016 @06:35PM (#10828586)

You may want to reconsider. CoPP only goes so far, as we've learned the hard way.

[ Parent | on HN ]

Re:An update from Linode about the recent DDoS attacks by scurvy on Saturday January 02, 2016 @09:27PM (#10829218)

I don't run Cisco, but thanks for worrying about that. Also, stateless ACL's should protect against overrunning the control plane.

[ Parent | on HN ]