Allowing changing the pre-allocated IP within a VPC manually
While the documentation make it sound like you are able to change the private IP of your droplet (see https://www.digitalocean.com/docs/networking/vpc/how-to/enable/), in reality it doesn't work. I mean the OS gets the new IP, but it cannot reach any other instances in that VPC from that point on.
It would be great to have the ability to manually set the IP in a VPC.
For example I am trying to put all of my DB instances under the same sub-range, so I can firewall them by range, but I cannot do that now, as I cannot set the IP, but have to live with what has been allocated.
-
Anonymous
- Sep 20 2020
- Needs review
Related ideas
I want to be more clear: without this feature, the DigitalOcean VPC offering is completely useless to me.
There's no way to intentionally move pirvate IPs around if/when hosts fail? Are you kidding? this a very common practice in managing clustered services.
I'm forced to send all traffic over public ipv4 and rely on firewalls for security, and use a public floating IP managed by automated scripts. But none of this traffic is really appropriate for public internet - and I'd rather not pay for the bandwith - these are all backend database services. Its just a silly setup and makes me long for better hosting privders.
Attachments Open full size
We are really not asking for much here. I can do this on my home network or most any network and it works fine. Surely the DO virtualization environment could support it somehow.
Attachments Open full size
The absence of this feature made my company move from DO unfortunetly.
Attachments Open full size
This would be great. I want to move some office VM to DO, but retaining original LAN IP address
Attachments Open full size