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 - add DHCP config field for default gateway #7208

Open
nrauso opened this issue Dec 11, 2024 · 2 comments · Fixed by NethServer/ns8-dnsmasq#23
Open

Dnsmasq - add DHCP config field for default gateway #7208

nrauso opened this issue Dec 11, 2024 · 2 comments · Fixed by NethServer/ns8-dnsmasq#23
Assignees
Labels
verified All test cases were verified successfully

Comments

@nrauso
Copy link

nrauso commented Dec 11, 2024

In simple scenarios, you can use dnsmasq on NS8 to set up a basic DHCP server.
The current implementation assigns the NS8 IP as the default gateway for clients that obtain an address through DHCP.

Proposed solution
To prevent routing issues, it would be beneficial to add an extra field in the DHCP configuration interface, allowing the sysadmin to specify the correct default gateway to distribute to DHCP clients.

@Tbaile Tbaile self-assigned this Dec 13, 2024
@Tbaile Tbaile moved this from ToDo to In Progress in NethServer Dec 13, 2024
@Tbaile Tbaile added this to the NethServer 8.4 milestone Dec 13, 2024
@Tbaile
Copy link
Contributor

Tbaile commented Dec 20, 2024

QA module: ghcr.io/nethserver/dnsmasq:dhcp-gateway-field

  • Fresh install
    • Install a fresh instance of the module using the image above
    • Init the module, check that in DHCP section Gateway option is present
    • Try to break the save (leave it empty, incomplete or out of the defined network)
    • Set a correct value, check with a client in the same network that the gateway is set correctly (use nmap --script broadcast-dhcp-discover)
  • Update
    • Update an existing module with the DHCP section enabled.
    • Check with nmap --script broadcast-dhcp-discover that the client still gets correctly the DHCP info
    • Open the DHCP section in the module, check that the gateway field is empty (correct, defaults to DNSMasq)
    • Check that the field is now required

@Tbaile Tbaile added the testing Packages are available from testing repositories label Dec 20, 2024
@nethbot nethbot moved this from In Progress to Testing in NethServer Dec 20, 2024
@nrauso nrauso self-assigned this Dec 20, 2024
@Tbaile Tbaile removed their assignment Dec 20, 2024
@nrauso
Copy link
Author

nrauso commented Dec 20, 2024

test case 1: VERIFIED
test case 2: VERIFIED

@nrauso nrauso added the verified All test cases were verified successfully label Dec 20, 2024
@github-actions github-actions bot removed the testing Packages are available from testing repositories label Dec 20, 2024
@nethbot nethbot moved this from Testing to Verified in NethServer Dec 20, 2024
@github-project-automation github-project-automation bot moved this from Verified to Done in NethServer Dec 20, 2024
@Tbaile Tbaile reopened this Dec 20, 2024
@github-project-automation github-project-automation bot moved this from Done to In Progress in NethServer Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
verified All test cases were verified successfully
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants