1. If this code also includes a check box to automatically create the firewall rules to enable or disable https access to the pfsense web gui from the WAN interface, then I'll add $100.00 USD to the fee that I pay. Note, for this bonus to be paid, this additional function needs to actually work, not just be the gui front end for this item.
Unless Bill complains I am willing to create such a feature. A few questions about the bonus feature.
If you want to be able to remotely administer the box you are currently aware that you can do this with a firewall rule, no?
I was thinking something along the following lines.
1 "Allow remote administration checkbox on the webgui port and protocol, with a field next to it to specify either a IP or a alias which is allowed to connect".
2 "Allow remote administration checkbox, force the webgui to https, user port selection from general settings, with a field next to it to specify either a IP or a alias which is allowed to connect".
I am aware that there are quite a number of users that require access to the webgui on port 80 because of artificial reasons they can not control. So I wanted to make it possible to allow remote administration over port 80 http.
Although I consider it good practice to switch to https.
Would the following suggestion work for you, only allow setting the remote administration checkbox when the protocol is https on whatever the webgui port is? This would leave the choice of external port free, you can always set this on the general setup page.