Question

any "real" private networking solution ?

Well, I want to mention first about the current private networking on DO, that’s not what we want. Why?

1 - Because, we want our DB cluster “completely” isolated from public access. While well as firewall or ifdown eth0 can do that, they do not provide any guarantees to mitigate DDOS attacks. So, when DDOS start to hit the server at big volume, the server will waste resource to mitigate the attack instead of working for its cluster. So, they should just be at BACK-END only, not mixed FRONT-END~BACK-END.

2- Let’s assume, the first problem has resolved and we are happy with that. What will happen if the attacker does DDOS inside DO datacenter? So, it’s useful to mention once again here; there should be a private networking option which we can completely isolate our VPS from any other 3rd networks. I guess, it should not be too hard for you guys like writing a script that adds filters to internal switches the on DO datacenter.

To the back to the reason of the question, this mistakes on DO really seem that DO business area targets only small businesses and million dollar businesses.

But, to be honest, I love you DO :)

Thanks.


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi there,

I just came across this question and decided to post a small update here in case that anyone else comes across this in 2020.

I would recommend considering the new DigitalOcean VPC networks.

VPC networks are completely isolated from both other customers and other VPCs on your own account. See here for more details:

https://www.digitalocean.com/docs/networking/vpc/

It’s also worth pointing out that DigitalOcean private networks provided account level isolation since July 18, 2018. The big changes with the release of VPCs are:

  • You can create multiple VPCs that are isolated from each other
  • You can define the IP range for your VPCs yourself

Source

@Kamal, may you didn’t understand me as well. Since DigitalOcean offers Virtualization (KVM Virtualization), all operations are software level. What I need is hardware isolated. Even it does not try to respond to DDOS, you have nothing to do with virtualization when 300gbps hits your network. That was the point. <br> <br>For VLAN, I’m glad it’s in on the roadmap. I just voted.

Disabling the network interface will stop all traffic from reaching your droplet, so it wouldn’t try to respond to the queries that are generated by the DDoS attack. <br> <br>We currently do not support assigning a whole separate VLAN to one account however it is on the roadmap – you can vote for the feature and follow the progress on it here: <a href=“https://digitalocean.uservoice.com/forums/136585-digitalocean/suggestions/3574245-vlan”>https://digitalocean.uservoice.com/forums/136585-digitalocean/suggestions/3574245-vlan</a>.