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.

Sign up for GitHub

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

Jump to bottom

Treat 100.64.0.0/10 as a private subnet #1031

Closed
eslesarchuk opened this issue Jun 14, 2015 · 2 comments
Closed

Treat 100.64.0.0/10 as a private subnet #1031

eslesarchuk opened this issue Jun 14, 2015 · 2 comments

Comments

@eslesarchuk
Copy link

According to RFC 6598 http://tools.ietf.org/html/rfc6598 there's also a 4th subnet 100.64.0.0/10, which may be used by Service Providers as a private network.

Technically, we're using that subnet within AWS EC2 (in purpose of not intersecting with RFC 1918's addresses), and at first I was quite surprised seeing the Consul's message like "Hey, this is not a private IP, I wont start with this".

I know, the RFC says it is intended to use for NAT purposes, but since it's definitely not a public subnet, we can treat it as a private one.
@highlyunavailable
Copy link
Contributor

We're running into this on Azure too.

highlyunavailable pushed a commit to highlyunavailable/consul that referenced this issue Jun 19, 2015
Add RFC 6598 private IP range
b48842c 
Fixes hashicorp#1031 by adding 100.64.0.0/10 as a private IP range.
@highlyunavailable highlyunavailable mentioned this issue Jun 19, 2015
Merged
@ryanuber
Copy link
Member

Thanks for reporting this, fixed in #1050!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@eslesarchuk @ryanuber @highlyunavailable