-
Notifications
You must be signed in to change notification settings - Fork 450
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
network plugin is broken on v6 only hosts #685
Comments
This horribleness makes it sorta work for me... but I"m very unclear on 1. How network.rb and linux/network.rb are working together (and somehow both touch the same attr which is crazy to me) or 2. How this routewalking is supposed to work... but maybe this can get someone started:
|
Here's Ohai output for reference: Hybrid setup: IPv6 only: |
@jaymzh Any chance you help me understand the exact network setup you're using? I haven't run IPv6 on Linux before so what someone's setup would look like is a bit unknown to me. Our current tests check for a system running IPv6 only, as in even lo has no IPv4 address. That seems to work as expected. What we're not testing for, and not handling apparently, is IPv4/IPv6 on lo, but only IPv6 on the actual interfaces. I assume that's the more likely scenario for most people and what you're running? |
What do you mean it works as expected - your gist above shows the problem precisely: https://gist.github.com/tas50/dbb18c4644f8281b29a4#file-gistfile1-txt-L44 And yes, I can send you a private gist with route tables and interface configs if you'd like. |
@jaymzh When I referred to working as expected I meant on an absolutely pure IPv6 only host, which I suspect is not what most IPv6 setups look like. Things are absolutely not working as expected for a simple IPv6 setup. If you want to shoot me a gist at tsmith at chef.io that would really help. |
Done. |
tldr; Generally speaking, 127.0.0.1 is always going to work - you don't need external v4 for that and too many things hard-code it. We have no v4 addr on eth0. |
@jaymzh @tas50 can one of you forward me those route tables? [email protected]. |
Sent.
|
macaddress
largely because the code doesn't try:Talk about epic clowntown. But even when you ammend that to pick up macaddress there, it won't work and this is because above that it does some route selection magic:
Which doesn't work because there is no
src
on your average v6 routes:So that code doesn't even come close to working. Therefore there's no route to look at so that mac-address selection code can't possibly work.
The text was updated successfully, but these errors were encountered: