You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a working raspberry pi AP previously configured using isc-dhcp-server. I installed RaspAP which I think is an awesome webgui to easily controlling the AP. However, it looks like it cannot coexist with isc-dhcp-server and uses dnsmasq to handling the assignment of the IP addresses, DNS, etc to the connected clients. Is it possible to get RaspAP to use isc-dhcp-server instead of dnsmasq. The config file for isc-dhcp-server is located at /etc/dhcp/dhcpd.conf
Thank you.
The text was updated successfully, but these errors were encountered:
I think that to use an alternative to dnsmasq you would need to make some changes to the code, in particular includes/dhcp.php. The dnsmasq (and other) command line tools are called using the exec method so these are the things to look for.
If you do feel inclined to create a pull request for this then it would be helpful if it could be configurable via the raspap.php configuration file.
getveloce
added a commit
to getveloce/raspap-webgui
that referenced
this issue
Feb 25, 2017
The administration interface for isc-dhcp-server is different enough from dnsmasq that this would necessitate significant code changes. Given that dnsmasq does everything needed for the project, this is not likely to happen.
I would, however, encourage you to create a PR or fork the project.
I had a working raspberry pi AP previously configured using isc-dhcp-server. I installed RaspAP which I think is an awesome webgui to easily controlling the AP. However, it looks like it cannot coexist with isc-dhcp-server and uses dnsmasq to handling the assignment of the IP addresses, DNS, etc to the connected clients. Is it possible to get RaspAP to use isc-dhcp-server instead of dnsmasq. The config file for isc-dhcp-server is located at /etc/dhcp/dhcpd.conf
Thank you.
The text was updated successfully, but these errors were encountered: