From 1ce1f11f6b1029d21ee4b20babc77b7304fbfc00 Mon Sep 17 00:00:00 2001 From: Tyler Bird Date: Wed, 5 Sep 2018 15:00:44 -0600 Subject: [PATCH] Shift IP Ranges If we increment the IP ranges from `.7`, `.8`, `.9` to `.16`, `.17`, `.18`, it will play nicer with other canonical bosh-deployment cf-deployment repositories. This is because the cf-deployment sets up a cloud-config range of `10.244.0.0/20`. That only has a usable range to `.15`: ``` $ sipcalc 10.244.0.0/20 -[ipv4 : 10.244.0.0/20] - 0 [CIDR] Host address - 10.244.0.0 Host address (decimal) - 183762944 Host address (hex) - AF40000 Network address - 10.244.0.0 Network mask - 255.255.240.0 Network mask (bits) - 20 Network mask (hex) - FFFFF000 Broadcast address - 10.244.15.255 Cisco wildcard - 0.0.15.255 Addresses in network - 4096 Network range - 10.244.0.0 - 10.244.15.255 Usable range - 10.244.0.1 - 10.244.15.254 ``` And the [convention in bosh-lite](https://bosh.io/docs/bosh-lite/) has been to add a route for internal containers to be on a `10.244.0.0/16` range. So we can get to more networks than just the cf-deployment's `/20`. I've test the `.16`, `.17`, `.18`, and all three deployments (bosh-deployment, cf-deployment, cf-mysql-deployment) work better "out of the box" with these changes. --- bosh-lite/cloud-config.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/bosh-lite/cloud-config.yml b/bosh-lite/cloud-config.yml index 67adb47..e5f770d 100644 --- a/bosh-lite/cloud-config.yml +++ b/bosh-lite/cloud-config.yml @@ -18,18 +18,18 @@ networks: - name: default subnets: - az: z1 - range: 10.244.7.0/24 - gateway: 10.244.7.1 + range: 10.244.16.0/24 + gateway: 10.244.16.1 cloud_properties: name: random - az: z2 - range: 10.244.8.0/24 - gateway: 10.244.8.1 + range: 10.244.17.0/24 + gateway: 10.244.17.1 cloud_properties: name: random - az: z3 - range: 10.244.9.0/24 - gateway: 10.244.9.1 + range: 10.244.18.0/24 + gateway: 10.244.18.1 cloud_properties: name: random vm_extensions: