V
voodoochile
Guest
Small request here. Can the firewall module be updated to allow port ranges?
The scenario I'm in right now is such. If I use the Firewall module, I can get pretty decent control over the firewall on my Plesk boxes, with one exception. Rolloff ports for Passive FTP. If I were to use your module to set this up, it would take approximatley 500 indiviual rules to allow my customers that have to use passive FTP to be able to roll off to the passive ports. (I hardset the passive ports the clients can use in the proftpd.conf file, and give them a range of 8500-9000.) Now, whenever PSA updates the firewall rules, it overwrites the rule that I have to add by hand and tech support lights up with people unable to FTP.
While the tool has a lot of potential, this one feature makes it somewhat worthless in a virtualhosting environment. It'd be a pretty simple table and code update, so I don't think this should be a big deal to add?
Thanks!
The scenario I'm in right now is such. If I use the Firewall module, I can get pretty decent control over the firewall on my Plesk boxes, with one exception. Rolloff ports for Passive FTP. If I were to use your module to set this up, it would take approximatley 500 indiviual rules to allow my customers that have to use passive FTP to be able to roll off to the passive ports. (I hardset the passive ports the clients can use in the proftpd.conf file, and give them a range of 8500-9000.) Now, whenever PSA updates the firewall rules, it overwrites the rule that I have to add by hand and tech support lights up with people unable to FTP.
While the tool has a lot of potential, this one feature makes it somewhat worthless in a virtualhosting environment. It'd be a pretty simple table and code update, so I don't think this should be a big deal to add?
Thanks!