Hopefully you would be sending those flows out a different circuit than the one that’s going to get swamped with a DDoS otherwise... it might just take a while to mitigate that ;-) depending on the type obviously.
-- J. Hellenthal The fact that there's a highway to Hell but only a stairway to Heaven says a lot about anticipated traffic volume. > On Feb 3, 2020, at 11:01, Javier Juan <javier.j...@gmail.com> wrote: > > > Hi ! > > I was looking around (a couple years ago) for mitigation appliances (Riorey, > Arbor, F5 and so on).... but the best and almost affordable solution I found > was Incapsula/Imperva. > https://docs.imperva.com/bundle/cloud-application-security/page/introducing/network-ddos-monitoring.htm > > > Basically, You send your flows to Imperva on cloud for analysis. As soon as > they find DDoS attack , they activate mitigation. It´s some kind of > elegant-hybrid solution without on-premise appliances . Just check it out :) > > Regards, > > JJ > > > >> On Sun, Nov 17, 2019 at 11:20 PM Rabbi Rob Thomas <r...@cymru.com> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> >> Hello, NANOG! >> >> I'm in the midst of rebuilding/upgrading our backbone and peering - >> sessions cheerfully accepted :) - and am curious what folks recommend >> in the DDoS mitigation appliance realm? Ideally it would be capable >> of 10Gbps and circa 14Mpps rate of mitigation. If you have a >> recommendation, I'd love to hear it and the reasons for it. If you >> have an alternative to an appliance that has worked well for you >> (we're a mix of Cisco and Juniper), I'm all ears. >> >> Private responses are fine, and I'm happy to summarize back to the >> list if there is interest. >> >> Thank you! >> Rob. >> - -- >> Rabbi Rob Thomas Team Cymru >> "It is easy to believe in freedom of speech for those with whom we >> agree." - Leo McKern >> -----BEGIN PGP SIGNATURE----- >> >> iQIzBAEBCAAdFiEEDcVjavXj08cL/QwdQ+hhYvqF8o0FAl3Rx08ACgkQQ+hhYvqF >> 8o0snw/8CxTOujcodNh/huMXZaUNlMNoNRz3IoPqBiAP9BZomMz9xqlpDW/qvWBF >> xhoJ07C0O0mo5ilNjnPR308uifIBu6ylw02PshOCU06dV0afgtndxGg5AoG9npUV >> 7uCi2afWaf22dq5TwKLut8QPNNQJTRzndX88xJw9MzzoBTemxRtM7ft4H3UhJ0hv >> oKo83FCNZQt36I+GZA9GBJeXM+o0f5h0w6fhRqARzttf6brJZdXgROyIQ7jptGuZ >> N3Yrjk/8RM4XKMnYbtIwl8NS3c0nEGN3ndn+Bz7p2FE7QJrZKonk/o03dvr2kU0Y >> 7gUQliOOzV9EsptVGyLCVyDJSElvXTBaps0giEVZhdmEIDJPWvBc+93j1g7xbmti >> 27lT6+5qBmEN0oKJWxXgtw9/n1yX9vsc7tXlgYDoXGhIlszdB3baRao1tYEp8BBQ >> hTGAULRfHe94tRzvOOQUQIuhzNcK1Q4E2jU6kzBB1wJsBD4zuHk+QIJLSHBmmnka >> VNKlQ+5zP8dmSMBp6k4feqAtt3hy0Bj+34FbdQZYPutIe3VXHEjpWI3jI9vKjhtC >> g7U/9CQIjVUl2APn1IllArpUpETBlNq7dSeJNUN/4Xh+eHglUnEn/m2kFG5mizmP >> d0YvLEVe0/+WzDUz+y3KxDVP5tdJT1VM46FHIgeiB4KrWNGRPUo= >> =uuel >> -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME cryptographic signature
