I assume this is what the op is referring although I don't know why. A nas should not need a firewall, it should be properly protected in a private LAN.
that is the URL
As I said I'm a win longtime user,no experience with freenas but there appears to be a builtin FW within freenas anjd I don't know how to configure it,the single user for whom the freenas is intended knows nothing about LAN's nevermind freenas,so I'm trying to cover all eventualities
brian
There is no built-in firewall for FreeNAS. The expectation is that the FreeNAS admin will fully understand what he/she is doing both on the server as well as the network topology for the FreeNAS server. Get that stuff wrong and you could find yourself without data one morning without warning. Just spent 2 days with someone that lost their pool suddenly because they didn't realize that FreeNAS really should be on 24x7, so they didn't run a scrub for 2 years, then lost a disk. Whoops!
So yeah, do LOTS of homework. If you haven't spent a week reading stickies and reading the manual you didn't do anywhere near enough homework. Some people might even say you need several weeks.
FYI, there is a firewall. The ipfwwe discussed in some other thread is a very powerful firewall. In FreeNAS it's compiled with the IPFIREWALL_DEFAULT_TO_ACCEPT option. However, you can also easily configure it to drop all packets (or anything in between :)) via ipfw(8).
FYI, there is a firewall. The ipfwwe discussed in some other thread is a very powerful firewall. In FreeNAS it's compiled with the IPFIREWALL_DEFAULT_TO_ACCEPT option. However, you can also easily configure it to drop all packets (or anything in between :)) via ipfw(8).
OK, I'll grant you that. But that is not expected to be used as a firewall for FreeNAS that is internet facing. There's no GUI options or anything associated with it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.