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

[Feature Request] Allow setting "option dhcp-option-overload" in DHCP web gui #8174

Open
2 tasks done
matthawkins90 opened this issue Jan 1, 2025 · 1 comment
Open
2 tasks done
Labels
support Community support

Comments

@matthawkins90
Copy link

matthawkins90 commented Jan 1, 2025

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Is your feature request related to a problem? Please describe.

In order to allow unifi flex mini switches (which cannot be ssh-ed into) to be adopted by a unifi controller on a different subnet, I need to set DHCP Option 43 to point to the IP address of the unifi controller. Following this guide, I tried various ways of inputting the value 01:04:<hex-encoded-ip-address>. Finally, the method that "looked correct" after packed inspection was to use Type: String and 01:04:<hex-encoded-ip-address> without being surrounded by quotation marks. However, even though it looked correct in the packet inspection, it still won't work, and my unifi switches continue to remain undiscovered. This opnsense forum post suggests that I set the option dhcp-option-overload. However, I really have no idea how to do that, even after ssh-ing into opnsense.

Describe the solution you like

I would like to be able to modify the option dhcp-option-overload value from within the web gui.

Describe alternatives you considered

I tried ssh-ing into the router to modify /var/dhcpd/etc/dhcpd.conf, but it didn't work and my changes got reset after I restarted dhcpd.

@AdSchellevis
Copy link
Member

rfc suggests code 53 (https://datatracker.ietf.org/doc/html/rfc2132#section-9.3)

@AdSchellevis AdSchellevis added the support Community support label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Community support
Development

No branches or pull requests

2 participants