Our great sponsors
-
Installation
The premier source of truth powering network automation. Open source under Apache 2. Public demo: https://demo.netbox.dev
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Good advice is often shared here that says assign a /16 per site and then assign prefixes from within. Obviously in your case using the 192.168.0.0/16 is only going to work for one site and then you'd need to use some other RFC 1918 prefix. This advice is though solid and absolutely for scalability reasons. Stability of routing tables is paramount when building out large networks. The way you have defined prefixes using 192.168.10.0/24 and then 192.168.20.0/24 is a sure sign of a lack of sub-netting experience. We all start somewhere though which is why I'm giving you the heads up! A great tool if you have never tried it is https://github.com/netbox-community/netbox