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

Azure vWAN Bootstrapping suggests /16 hub address range #440

Closed
paulgrimley opened this issue Feb 23, 2021 · 3 comments · Fixed by #608
Closed

Azure vWAN Bootstrapping suggests /16 hub address range #440

paulgrimley opened this issue Feb 23, 2021 · 3 comments · Fixed by #608
Assignees
Labels
enhancement New feature or request

Comments

@paulgrimley
Copy link
Contributor

image

The vWAN connectivity subscription bootstrapping config leads with a /16 address range which is misleading, the recommendation is to use a /23 range - could we update the deployment ARM to reflect this.

@paulgrimley paulgrimley added bug Something isn't working triage labels Feb 23, 2021
@daltondhcp daltondhcp added enhancement New feature or request and removed bug Something isn't working triage labels Mar 24, 2021
@daltondhcp
Copy link
Contributor

Thank you for reporting Paul, we'll take a look at it!

@zebak007
Copy link

Confirmed. I just did a fresh deployment and the CIDR proposed in the Azure landing zone accelerator deployment UI is still referring to 10.100.0.0/16.

@jtracey93
Copy link
Collaborator

jtracey93 commented Jul 29, 2021

@zebak007 please see #714 where this has recently been re-logged.

Also I have just submitted a PR which is being reviewed by my colleagues which will fix this #718

@ghost ghost locked as resolved and limited conversation to collaborators Jan 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants