From SOURCES to PACKAGES
-
Running as a web server is what's really not recommended. As a reverse proxy less so. However adding any packages yourself carries an inherent risk especially if they are services exposed to WAN. You would responsible for maintaining it against any new vulnerability.
There are several reverse proxy packages already. Does nginx offer something the others don't that you really need?
Steve
-
Too many people seem to think pfsense is a swiss army knife.
-
An nginx package doesn't seem like a terrible idea though, as long as it's limited to reverse proxy duties. People will inevitably use it as a web server I imagine. ::)
Steve
-
Too many people seem to think pfsense is a swiss army knife.
Actually, it is. And that's no problem. It's great.
The only thing is, that you have to use it cleverly. Like 5 posts before: he has two pfSense installs, one for main firewalling, and one for playing around. What's wrong with that? -
My personal opinion is that if you install too many services on your pfsense firewall, you no longer have a firewall - you have something that needs a firewall in front of it.
-
But he said he already has a firewall in front, which is a separate pfSense box.
-
http://www.youtube.com/watch?v=aXQ2lO3ieBA
-
I have no problem using pfSense as a base for an appliance. You just have to understand the security implications. pfSense had at one time a dedicated DNS version and it makes a nice VPN concentrator. No reason why it couldn't be a dedicated reverse proxy.
Steve
-
-
But… Can it blend?
-
???
-
