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

tunnel interface names cannot be longer than 15 characters #274

Merged
merged 1 commit into from
Jan 7, 2018

Conversation

andrewsykim
Copy link
Collaborator

Ran into some strange behaviour as reported here. Turns out it was because linux interface names cannot be more than 15 characters. Removing the - in the interface name ensures that we will always have at most 15 characters for IPv4. However, I do have concerns around backwards compatibility and some more work may have to be done here so that the transition is smoother. @murali-reddy would love your thoughts here.

@andrewsykim
Copy link
Collaborator Author

On second thought, if I had used a private IPs (10.X.X.X) I probably wouldn't have run into this issue. However, this is an edge case that other uses may run into.

@murali-reddy
Copy link
Member

@andrewsykim problem may arise with private ip range of 172.16..-172.31.. as well. So it must be fixed. But i know some production users who are using old convention. Modifing the logic to generate the tunnel interface name with your change only if length of IP address without . is 12?

@andrewsykim
Copy link
Collaborator Author

@murali-reddy that's a great idea, I'll update the PR soon!

@andrewsykim
Copy link
Collaborator Author

updated

@murali-reddy murali-reddy merged commit 78588fc into cloudnativelabs:master Jan 7, 2018
@murali-reddy
Copy link
Member

Thanks @andrewsykim

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

Successfully merging this pull request may close these issues.

2 participants