Skip to content

Don't use dhcp4 for none mode #6001

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

Merged

Conversation

gthvn1
Copy link
Contributor

@gthvn1 gthvn1 commented Sep 18, 2024

For the context, we had an strange behavior where an host installed with IPv6 stack only got an Ipv4 address only during the first boot due to the start of a systemd service called chrony-wait. This is because during the first boot the xcp-networkd looks for a configuration from /etc/firstboot.d/data/management.conf and if the MODE=none it uses DHCP4. And as chrony-wait is started it got a source in IPv4 before XAPI had time to reconfigure it using IPv6 stack. So we think that if the MODE is none we shouldn't use DHCP4.

Regards,
Guillaume

Signed-off-by: Guillaume <guillaume.thouvenin@vates.tech>
@gthvn1 gthvn1 force-pushed the gtn-dont-use-dhcp4-for-none-mode branch from 8c4fc2e to d0215ed Compare September 18, 2024 13:32
@psafont psafont added this pull request to the merge queue Sep 18, 2024
Merged via the queue into xapi-project:master with commit ba3b3ac Sep 18, 2024
15 checks passed
@gthvn1 gthvn1 deleted the gtn-dont-use-dhcp4-for-none-mode branch September 19, 2024 08:33
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.

3 participants