-
Notifications
You must be signed in to change notification settings - Fork 109
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: hardcode fallback for wireserver endpoint #145
Conversation
Prep for #130. |
I've also verified that this fallback is compatible with our metadata version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just two minor comments, looks ok otherwise. Thanks!
If we can't fetch the wireserver address from the DHCP lease option, do what WALinuxAgent does and use the fallback wireserver endpoint at 168.63.129.16.
@jlebon can you self-merge this here? |
Doesn't look like it. |
@@ -46,6 +46,10 @@ Content-Transfer-Encoding: base64 | |||
|
|||
"; | |||
|
|||
/// This is a known working wireserver endpoint within Azure. | |||
/// See: https://blogs.msdn.microsoft.com/mast/2015/05/18/what-is-the-ip-address-168-63-129-16/ | |||
const FALLBACK_WIRESERVER_ADDR: [u8; 4] = [168, 63, 129, 16]; // for grep: 168.63.129.16 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for grep: 168.63.129.16
💯
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Four years later, I did indeed end up finding this line with grep. 🎉
If we can't fetch the wireserver address from the DHCP lease option, do
what WALinuxAgent does and use the fallback wireserver endpoint at
168.63.129.16.