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

dnsmasq.conf.j2 incomplete for IPv6 only setup #614

Open
florath opened this issue Jan 31, 2025 · 1 comment
Open

dnsmasq.conf.j2 incomplete for IPv6 only setup #614

florath opened this issue Jan 31, 2025 · 1 comment
Labels
needs-triage Indicates an issue lacks a `triage/foo` label and requires one.

Comments

@florath
Copy link

florath commented Jan 31, 2025

Running in an IPv6 only environment I run into a couple of problems and had a closer look at the dnsmasq.conf.j2 file:

  1. "option6:router" is not a valid option [1] - but it is generated in line 19
  2. Lines 65ff of the dnsmasq.conf.j2 which are mostly a (bad) copy of lines 14ff. The later one tries to be for IPv4 and IPv6 (which fails as described earlier) weather the first one is specific for IPv6, but does not even put the "option6" in place and also uses the wrong (IPv4) attributes.
  3. There is IMHO no hint in the documentation how IPv6 addresses should be specified in the dnsmasq.env file. With or without brackets?

Depending on the input I get errors like

dnsmasq: bad dhcp-option at line 14 of /etc/dnsmasq.conf

where the line number differs depending on the set of input variables.

[1] see https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blob_plain;f=src/dhcp-common.c;hb=refs/heads/master lines 638ff

@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Jan 31, 2025
@metal3-io-bot
Copy link
Contributor

This issue is currently awaiting triage.
If Metal3.io contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Indicates an issue lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants