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 refuses to start with duplicate IPs #1373

Closed
marek-guran opened this issue Aug 2, 2023 · 3 comments · Fixed by #1497
Closed

dnsmasq refuses to start with duplicate IPs #1373

marek-guran opened this issue Aug 2, 2023 · 3 comments · Fixed by #1497

Comments

@marek-guran
Copy link
Contributor

Checklist

  • [x ] This is a bug report
  • [ x] I observed this bug on a clean install of the OS
  • [ x] I have followed the project prerequisites
  • [ x] I have searched this repository for existing issues
  • [ x] I checked the FAQ and official documentation before creating this issue
  • [ x] I have read and understand the issue reporting guidelines

Bug description

When you give static lease with duplicate IP to 2 or more devices, dnsmasq will not like it and refuse to start.

Your environment

  1. Operating System: Ubuntu Server 23.04
  2. Hardware and version: Raspberry Pi 4B
  3. RaspAP version: v2.9.3
  4. Clean install of a compatible operating system? No
  5. RaspAP Quick Install or Manual setup? Quick Install
  6. Using default configuration? Yes
  7. Simultaneous AP and managed mode? No
  8. Onboard wireless chipset or external adapter? Onboard
  9. Other software or services running with RaspAP? Yes, but it does not make nothing to do with bug

Steps to reproduce

When you open on web gui section: DHCP Server/Static Leases and you put there 2 devices or more with same LAN IP like for example: 10.0.1.3 (both with this), the dnsmasq will refuse to start on boot or when you restart the service. It can be fixed very easily by removing or changing duplicate IP. I would suggest giving there check if the IP is not already used before saving it.

Screenshots

Additional context

Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Nov 28, 2023
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2023
@billz billz added confirmed bug and removed stale labels Dec 12, 2023
@billz billz reopened this Dec 12, 2023
Copy link

This issue is stale because it has been open for 30 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants