Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running out of IPs #26

Open
2 tasks done
clonm opened this issue Mar 18, 2020 · 1 comment
Open
2 tasks done

Running out of IPs #26

clonm opened this issue Mar 18, 2020 · 1 comment

Comments

@clonm
Copy link
Contributor

clonm commented Mar 18, 2020

@CazNm changed their DHCP range to 10.20.16.1/18 because they were running out of IPs with /22. This overlaps with the Cloyne range. It also raises the question of whether Cloyne has been having this issue too and we just haven't noticed/diagnosed it correctly.

  • CZ has changed their range to /20 at my request. TBD if this causes problems, because people have left due to COVID-19.
  • I'm going to try expanding the Cloyne DHCP range to 10.20.32.1/21 and see if it fixes or breaks anything. This will involve moving the Cloyne and Kingman antennas from 10.20.35.XX to 10.20.39.XX.
@clonm
Copy link
Contributor Author

clonm commented Mar 18, 2020

  1. For each antenna, under network, changed .35. to .39. in the static IP, and changed netmask to 255.255.248.0.
  2. On Cloyne router, under IP -> DHCP server, changed Home Range to 10.20.32.0/21 and netmask to 21
  3. Also on Cloyne router, under IP -> Pool, changed dhcp_pool1 from 10.20.32.100-10.20.35.190 to 10.20.32.100-10.20.39.190

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant