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

Cannot enable DHCP server: Cannot check if IP is static #3289

Closed
marceltc opened this issue Jun 28, 2021 · 8 comments
Closed

Cannot enable DHCP server: Cannot check if IP is static #3289

marceltc opened this issue Jun 28, 2021 · 8 comments

Comments

@marceltc
Copy link

Issue Details

  • Version of AdGuard Home server:
    • v0.106.3, FreeBSD amd64
  • How did you install AdGuard Home:
    • FreeBSD pkg
  • How did you setup DNS configuration:
    • Router
  • If it's a router or IoT, please write device model:
    • TP-Link Archer a9
  • CPU architecture:
    • AMD64
  • Operating system and version:
    • FreeBSD 12.2-RELEASE-p6

Expected Behavior

DHCP server option should successfully detect if existing DHCP server exists on network. Attempting to enable the DHCP server should be successful if none exists.

Actual Behavior

"Enable DHCP server" is grayed out. If I try to manually enable it via editing the .yaml, I get an error on the GUI: Error: control/dhcp/set_config | enabling dhcp: checking static ip: cannot check if IP is static: not supported on freebsd | 500 If I use the "Check for DHCP servers" button, I get Error: control/dhcp/find_active_dhcp | Network Error

Additional Information

In my case, I do have a static IP set up. Is setting up AdGuard as a DHCP server not supported in FreeBSD? If it is, then what am I doing wrong?

@ainar-g ainar-g self-assigned this Jun 28, 2021
@ainar-g
Copy link
Contributor

ainar-g commented Jun 28, 2021

Hi, and thank you for the report. There are definitely some features missing, but enabling through the config should work. We'll look into it.

@ainar-g ainar-g added this to the v0.107.0 milestone Jun 30, 2021
@ainar-g ainar-g assigned EugeneOne1 and unassigned ainar-g Jun 30, 2021
@one8three
Copy link

Having the same problem on ARM64 FreeBSD. I manually enabled it in the config and it seems to somewhat work but there are still issues. I've attached DHCP related logs.

adguard-dhcp.log

adguard pushed a commit that referenced this issue Jul 30, 2021
Merge in DNS/adguard-home from 3289-freebsd-dhcp to master

Updates #3289.

Squashed commit of the following:

commit 1365d8f
Author: Eugene Burkov <[email protected]>
Date:   Fri Jul 30 15:01:13 2021 +0300

    dhcpd: fix doc

commit 26724df
Author: Eugene Burkov <[email protected]>
Date:   Fri Jul 30 14:52:58 2021 +0300

    all: imp code & docs

commit 9a9574a
Author: Eugene Burkov <[email protected]>
Date:   Thu Jul 29 15:51:07 2021 +0300

    all: fix broadcasting, sup freebsd dhcp, fix http response
@EugeneOne1
Copy link
Member

@mkap20, we've just updated the edge channel with the build that should fix the issue for you. Could you please check it?

@TheRandMan, it seems, that in your case AdGuard Home can't bind on the port 68. Is it launched with root permissions?

@marceltc
Copy link
Author

Just installed and checked today. Issue still looks the same, except this time I also get receiving packet: invalid argument if I try to check for DHCP servers through the GUI.

@EugeneOne1
Copy link
Member

@mkap20, just to clarify:

  1. What exact version of AdGuard Home did you installed (it's printed in the right bottom corner of the AdGuard Home's dashboard)?
  2. How did you configured the static IP address on FreeBSD?

FYI, the receiving packet: invalid argument error shouldn't block the DHCP to be enabled.

@marceltc
Copy link
Author

marceltc commented Aug 3, 2021

@EugeneOne1 Seems that invalid argument error resolved. I just updated to the latest release (v0.107.0-a.119+c14bde28) and no longer get the Cannot check if IP is static error. The "Check for DHCP servers" button still does not seem to work though :/

@one8three
Copy link

On the latest beta release (v0.107.0-b.6) I was able to successfully enable DHCP using the web GUI. I had to click "Check for DHCP servers" twice (both times gave me errors) then the "Enable DHCP" worked.

I then successfully received an IP address on a device and was able to set a static address as well.

@EugeneOne1
Copy link
Member

@mkap20, we've filed the new issue about the error, that still persists. As far as I can tell, current issue is fixed (DHCP server is now could be turned on), so I'll close it for now. Please feel free to open new issues if you find any other bugs on FreeBSD.

@ainar-g ainar-g removed the needs investigation Needs to be reproduced reliably. label Sep 13, 2021
heyxkhoa pushed a commit to heyxkhoa/AdGuardHome that referenced this issue Mar 20, 2023
Merge in DNS/adguard-home from 3289-freebsd-dhcp to master

Updates AdguardTeam#3289.

Squashed commit of the following:

commit 1365d8f
Author: Eugene Burkov <[email protected]>
Date:   Fri Jul 30 15:01:13 2021 +0300

    dhcpd: fix doc

commit 26724df
Author: Eugene Burkov <[email protected]>
Date:   Fri Jul 30 14:52:58 2021 +0300

    all: imp code & docs

commit 9a9574a
Author: Eugene Burkov <[email protected]>
Date:   Thu Jul 29 15:51:07 2021 +0300

    all: fix broadcasting, sup freebsd dhcp, fix http response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants