5 ms·

I find some of the limits weird https://www.digitalocean.com/docs/networking/vpc/ https://www.digitalocean.com/docs/networking/vpc/ - VPC network ranges cannot

I find some of the limits weird https://www.digitalocean.com/docs/networking/vpc/ https://www.digitalocean.com/docs/networking/vpc/ - VPC network ranges cannot overlap with the ranges of other networks in the same account. (Edit: Does this mean each VPC in the account has to have a non overlapping subnet?) -Resources do not currently support multiple private network interfaces and cannot be placed in multiple VPC networks. - Not being able to change the VPC connected to stuff without taking a snapshot

t3rabytes 6y ago
Pretty standard? Taking AWS for example: - You can do this, but it's highly discouraged since it means no VPC peering if you ever need that. - Can't do this at all with network interfaces, it all is via VPC peering. - Can't change the VPC after an instance has been created, you have to take a snapshot and relaunch it.
- nerdbaggy 6y ago
  Interesting, didn’t know that about AWS. In more familiar with the Google cloud version of VPC. Seems the DO implementation is more like the AWS version
  - t3rabytes 6y ago
    Heh, no worries -- mostly the same deal there: - You can do it, but it's probably not a great idea if you need to do VPC peering (or attach multiple VPCs to one VM, see next). - Does actually work, but it does not work if the VPCs you're trying to attach to a single VM have overlapping CIDRs. - Same deal, almost. You cannot add or remove network interfaces from an existing VM.
  - troutwine 6y ago
    For what it's worth VPC ranges are allowed to overlap in GCP -- and do by default -- but then you aren't able to peer them. I kind of prefer the DO/AWS constraint.
    - cbetti 6y ago
      Agreed, having paid the cost of a few VPC moves to separate ranges on AWS in order to gain peering.
    - Legogris 6y ago
      No such constraint in AWS.
      - troutwine 6y ago
        I misremembered. Thanks for the clarification.
- rantwasp 6y ago
  you cannot peer 2 vpcs that have an overlap but you can have multiple vpcs that have overlaps. it only matters for the 2 vpcs you want to peer
  - vorpalhex 6y ago
    But AWS tells you to not overlap them, and likely keeps that behavior for legacy reasons.
    - moduspol 6y ago
      I could have missed it, but I've never seen a suggestion not to overlap network addresses unless you want to peer them. If you're launching ephemeral networks for testing VMs / virtual appliances in their own, isolated networks, it can be totally feasible to have lots of them using the same addresses. You can only create 5 VPCs (at all) by default per AWS account, but they'll raise that limit for you if you request it.
- KingOfCoders 6y ago
  I basically have no clue. I thought one would have a node two VPC, e.g. app and database, so it can speak to both, but the load balancers can't. With peering one would have an app VPC and a database VPC and peer them?
  - vorpalhex 6y ago
    In AWS you use a mix of private and public subnets within a single VPC. Not sure best practice for DO since I haven't tried their VPC setup but it doesn't appear to have a way to let two VPCs interact yet.
Legogris 6y ago
> - VPC network ranges cannot overlap with the ranges of other networks in the same account. (Edit: Does this mean each VPC in the account has to have a non overlapping subnet?) Overlapping subnets tend to be a mistake and will bite you in the behind whenever you want to peer them. What'd be your reason to want overlapping subnets in the first place?

t3rabytes 6y ago

Pretty standard? Taking AWS for example: - You can do this, but it's highly discouraged since it means no VPC peering if you ever need that. - Can't do this at all with network interfaces, it all is via VPC peering. - Can't change the VPC after an instance has been created, you have to take a snapshot and relaunch it.

nerdbaggy 6y ago
Interesting, didn’t know that about AWS. In more familiar with the Google cloud version of VPC. Seems the DO implementation is more like the AWS version
- t3rabytes 6y ago
  Heh, no worries -- mostly the same deal there: - You can do it, but it's probably not a great idea if you need to do VPC peering (or attach multiple VPCs to one VM, see next). - Does actually work, but it does not work if the VPCs you're trying to attach to a single VM have overlapping CIDRs. - Same deal, almost. You cannot add or remove network interfaces from an existing VM.
- troutwine 6y ago
  For what it's worth VPC ranges are allowed to overlap in GCP -- and do by default -- but then you aren't able to peer them. I kind of prefer the DO/AWS constraint.
  - cbetti 6y ago
    Agreed, having paid the cost of a few VPC moves to separate ranges on AWS in order to gain peering.
  - Legogris 6y ago
    No such constraint in AWS.
    - troutwine 6y ago
      I misremembered. Thanks for the clarification.
rantwasp 6y ago
you cannot peer 2 vpcs that have an overlap but you can have multiple vpcs that have overlaps. it only matters for the 2 vpcs you want to peer
- vorpalhex 6y ago
  But AWS tells you to not overlap them, and likely keeps that behavior for legacy reasons.
  - moduspol 6y ago
    I could have missed it, but I've never seen a suggestion not to overlap network addresses unless you want to peer them. If you're launching ephemeral networks for testing VMs / virtual appliances in their own, isolated networks, it can be totally feasible to have lots of them using the same addresses. You can only create 5 VPCs (at all) by default per AWS account, but they'll raise that limit for you if you request it.
KingOfCoders 6y ago
I basically have no clue. I thought one would have a node two VPC, e.g. app and database, so it can speak to both, but the load balancers can't. With peering one would have an app VPC and a database VPC and peer them?
- vorpalhex 6y ago
  In AWS you use a mix of private and public subnets within a single VPC. Not sure best practice for DO since I haven't tried their VPC setup but it doesn't appear to have a way to let two VPCs interact yet.

Legogris 6y ago

> - VPC network ranges cannot overlap with the ranges of other networks in the same account. (Edit: Does this mean each VPC in the account has to have a non overlapping subnet?) Overlapping subnets tend to be a mistake and will bite you in the behind whenever you want to peer them. What'd be your reason to want overlapping subnets in the first place?