Thank you for the reply. I see now that my request was wildly unrealistic.
Not "wildly", just unrealistic unless you have a massive budget.

Basically I'm trying to write a business plan and am trying to plan for the worst case scenario so I don't fall over if traffic somehow spikes to such levels. My expected level of traffic is probably in the 300 megabits a second range but the incoming links from my upstream provider are 10GbE so I need to have some plan just in case I get a spike of 10 gigabits (as unlikely as that may be I still need to plan for it).
I would suggest simply limiting your incoming traffic... and paying for less bandwidth. Most providers are quite happy to sell you, e.g. 4Gbps capacity on a 10Gbps physical line. That moves the problem back a layer to the "someone else's problem" domain.

I haven't ruled out the possibility of using Cisco / Juniper for some of my requirements but obviously would like to use OpenBSD if possible because I've used it in the past and it includes everything that I need and best of all the documentation is excellent.
I think you might be able to do 10Gbps of L2TP traffic on Linux or FreeBSD (on commodity hardware) if you use one of the highly-optimized networking stacks that are available (e.g. DPDK). But even they won't handle it gracefully. I'm not even certain that Cisco or Juniper gear will decapsulate L2tP traffic at that rate.

I can drop the logging requirement pretty easily. That isn't really important at all.

I wonder what other people do when they are disaster planning for their new services? At the same time I wonder how the internet backbone is handled. As far as I am aware they handle speeds of about 100 gigabits a second so the hardware / software must be available for handling such speeds. I just guess they are ridiculously expensive to buy and maintain (well outside my budget anyway).
You build-to-budget.
The 100Gbps backbones/routers you hear about are a) few and far between, b) insanely expensive (multi-millions of dollars), and c) only shuttling packets as-is from one port to another. Everyone else just buys what they can afford, and then they take steps (like throttling) to ensure their servers don't fall over. Of course, a lot of people just let their servers fall over, too...

Also: load-balancers.

-Adam

Reply via email to