Raspberry Pi wireless Access Point: This repo automates the config of hostapd, dnsmasq, dhcpcd & wpa_supplicant to transform a Pi into an AP. Requires: a Pi, Ethernet cable & DHCP-enabled port on a broadband router or a switch connected to this router. For other interesting & practical Pi solutions, my Stack page is: https://raspberrypi.stackexchange.com/users/97613/f1linux
Describe bug
After running install.sh ufw is deactivated, and previously added custom rules have been cleared.
Did AP EVER work correctly before fault?
no
Bug CONSISTENTLY reproducible?
yes
If "yes", provide detailed steps to reproduce bug:
sudo ufw enable
sudo ./install.sh
Additional context
The very first TROUBLESHOOTING item is to check ufw, so it wasn't hard to fix, but it seems odd that enabling ufw should not be part of the install script.
And yes, ufw was active before running the script, and I had added some custom rules that got deleted. It seems like it reset ufw to an initial inactive state.
Otherwise the process was seamless.
Proposed Fixes
The install script should enable ufw, and preserve existing rules.
Describe bug After running install.sh ufw is deactivated, and previously added custom rules have been cleared.
Did AP EVER work correctly before fault?
Bug CONSISTENTLY reproducible?
If "yes", provide detailed steps to reproduce bug:
Additional context
The very first TROUBLESHOOTING item is to check ufw, so it wasn't hard to fix, but it seems odd that enabling ufw should not be part of the install script.
And yes, ufw was active before running the script, and I had added some custom rules that got deleted. It seems like it reset ufw to an initial inactive state.
Otherwise the process was seamless.
Proposed Fixes
The install script should enable ufw, and preserve existing rules.