Closed esackowitz closed 9 months ago
@esackowitz thanks for the very complete and accurate bug report. As a gesture of gratitude, I'd like to offer you Insiders access for your time.
@esackowitz thanks for the very complete and accurate bug report. As a gesture of gratitude, I'd like to offer you Insiders access for your time.
You're very welcome. Thank you for the quick turn. Happy to join the insiders.
I would be remiss to report that the fix worked in saving the DHCP values, however, DNSMasq wont start. . Uninstall and reinstall does not solve issue. Still need to confirm on other Pi's. Happy to fill out another issue if you prefer.
Please generate a debug log and perform a self-diagnosis before creating a new issue, thanks.
Code of Conduct
Issue reporting checklist
Operating System
Raspberry Pi OS (32-bit) Lite Bookworm
Quick install or Manual setup?
Quick install
Onboard wireless chipset or external adapter?
Onboard wireless chipset
Hardware
Raspberry Pi 4 Model B
RaspAP version
3.0 (Latest)
Other software or services running with RaspAP?
No other software
Contact details (optional)
eric@secureco.com
Bug description
After a clean install of the O/S using Raspberry Pi Imager
then performing all needed updates and following the automated install of RASPAP
Out of the box the default DHCP Server setup on Wlan0 is missing network start and end IP ranges along with lease time and interval. This is an invalid configuration.
Any attempt to save as is will fail with error as expected
Any attempt at manually entering in the default ranges starting with 10.3.141.50 to 10.3.141.254 and the 12hr lease interval will allow you to save the settings and will confirm as valid, however, those settings do not get applied and the screen will revert to the original invalid config.
Steps to reproduce
Screenshots
No response
Additional context
This raspberry Pi was previously running with RaspAP v2.6.5 on earlier build of O/S Linux 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux and was fully operational as hotspot.
This has been reproduced on 3 other identical raspberry Pi 4's with same issue.
We attempted to downgrade to Version 3.0.2 on same O/S and problem persists. It is specifically something to do with this version of Raspberian,
Relevant log output