Another PFSense+FreeNAS argument
-
Perhaps it would be beneficial to explain my setup a little. I have 4 pfsensei, all virtual. Two of them provide redundant, failover, QOS'd internet gateway/firewall/multi-lan router. These two do exactly what a security device should, and that's NOTHING except the single security intensive task for which it was purposed.
Separately, I have two other pfsensei that run networking services. DHCP, DNS, radius, and a few incidentals for the multiple LANs that the other two route and firewall for. These two systems are behind a secure firewall, and also have their own internal firewall. I would consider these secondary system as a candidate for hosting additional file services as well. web server, WINS server, and a couple others which belong in each LAN, but do not belong on the edge device.
Furthermore, virtualizing a full fledged NAS service (Providing large scale data storage to the network) is a VERY BAD idea, especially for home users as it requires expensive special hardware to do it properly.
-
As for ZFS, can't that be put into pfSense independent of FreeNAS? ZFS is just a file system no?
As I pointed out for the general case, this is another instance of replication of code and labour. FreeNAS already has this fully fleshed out and working. It would be better for everyone to use the existing single working codebase (Fewer bugs, less chance for security related bugs to creep in).
Replication of Code/Functionality and diverging developer bases are one of the few problems still plaguing free software today. It's exactly that attitude that's contributing to the problem.
-
A security device (firewall/router) should not also be a file storage/server device.
However, a file storage/server device should most definitely be a security device.
I would stop using pfsense if this was built in, talk about a security nightmare.
Obviously you didn't read the entirety of my post. I clearly thing that by default, none of the NAS stuff should be installed on a router, and none of the router stuff on a NAS device, but available through the package system and developed atop a strong common base
-
A security device (firewall/router) should not also be a file storage/server device.
However, a file storage/server device should most definitely be a security device.
Absolutely not.
A security device should not be accessible by end users. Your NAS is a file server, and is protected by a firewall to ensure that only the traffic you want to reach it is allowed through to that zone. You may also have user level access on the NAS itself tied in with an LDAP server, this is to prevent users from attempting to authenticate directly to the NAS.
Of course I'm coming at this from a commercial POV and not home user, but the basis for that is still the same.
I would stop using pfsense if this was built in, talk about a security nightmare.
Obviously you didn't read the entirety of my post. I clearly thing that by default, none of the NAS stuff should be installed on a router, and none of the router stuff on a NAS device, but available through the package system and developed atop a strong common base
If you want it as a package… Go for it! Start coding... :)
-
developed atop a strong common base
If you want it as a package… Go for it! Start coding... :)
It's not just that I believe everything should just be a package. There needs to be a single unified base upon which all packages are built. Common to the two largest projects that share a large set of features and requirements. The greatest benefit is to be seen by merging of developer base and reduced lines of total code. Simply adding features to one or the other as packages almost completely mitigates the greatest strengths of the concept of a merger.
-
Why FreeNAS? Why not NAS4Free?
-
Why FreeNAS? Why not NAS4Free?
I'm most familiar with FreeNAS, and I know it to be generally accepted to be the "best" freebsd/pf NAS solution.
If NAS4Free developers want to get in on the whole PFSense+FreeNAS Integration to make it into a PF4NAS mega-conglomerate, there's no reason even more experienced developers wouldn't improve the overall end user experience and contribute to feature maturity, security, and polish
-
There's some general concepts that all suggest this is a bad (dangerous) idea:
-
Security vs. Convenience. They're inversely related. If people want more convenience, usually security is then sacrificed, and vice versa. By incorporating more roles onto a security appliance, it's increasing the convenience; as a result, security is decreased.
-
Attack Surface. By adding more roles, you only dramatically increase the attack service of the device, server, or appliance. Something that is a specialist then becomes a generalist. We're adding more windows and doors to the house, making it easier for just one of them to be compromised and an attacker to gain entry and own the entire box.
-
Security by Isolation concept.
NAS is a storage device, usually for personal, private, or sensitive information. Even for a home user, the data includes personal documents, finances, family photos and videos. Putting those on a a perimeter/edge device such as a router or firewall is putting all that precious data closer to the Internet, when it should be the opposite: protected and as internal as possible from the WAN.
Heck, one could argue that even pfSense with a ton of packages installed is "too much" of an all-in-one solution, for convenience. Traditional firewall, proxy, content filter, IDS/IPS, DNS, DHCP, VPN endpoint, RADIUS. Some have these roles all on separate devices.
It seems OK to me to harden each server however, including NAS. Host-based firewall like FreeBSD's pf running on FreeNAS or Suricata running on a server. I mean, all our Windows devices have a basic host-based firewall enabled, Linux has iptables, etc. So it's fine to have host-based firewalls running on a NAS appliance and other servers, but something with a role of firewall/router should really be as isolated and simple as possible to reduce attack surface.
-
-
"Furthermore, virtualizing a full fledged NAS service (Providing large scale data storage to the network) is a VERY BAD idea, especially for home users as it requires expensive special hardware to do it properly."
What? I run my pfsense virtual - seems so do you, so you think it ok to turn it into a NAS - so then what it shouldn't be a vm then?
A NAS is network attached storage - what would be full fledged vs say not full fledged? What OS you use to provide access to your storage seems irreverent , be it freenas, nas4free, unraid, openfiler, windows anything, etc..
As to special expensive hardware? Again pure poppycock.. My very reasonable priced N40L provides me both my router via vm, and my nas - currently just windows 7 running drivepool from stablebit to make it easier to share out multiple drives as one share vs having to raid them in anyway, etc. This currently provides my network with 6+ TB which can easily expand to 16 in the same box by just plugging in the drives if so desired, more if I used the esata or usb connections, etc.
Anyone with the desire can bring up a very cheap a NAS be it the os is virtual, or they just buy a premade one - there are plenty of OS'es out there that are designed to be NASes - I don't see a reason to try and combine a nas OS with my edge router/firewall..
-
Furthermore, virtualizing a full fledged NAS service (Providing large scale data storage to the network) is a VERY BAD idea, especially for home users as it requires expensive special hardware to do it properly.
Perhaps you could elaborate on that. What sort of performance do you require that can't be achieved by a virtalised solution? It seems there are plenty of pfSense users doing exactly that, running it as a VM together with a NAS VM, and seeing good results.
Steve
-
A "very bad" idea solution of using a VM is still more secure than the "atrocious horrendous ghastly abhorrent lurid terrible horrible no good very bad" idea of putting a storage server on your firewall.
If you want to shoot your own foot, we won't be handing you the gun.
-
A "very bad" idea solution of using a VM is still more secure than the "atrocious horrendous ghastly abhorrent lurid terrible horrible no good very bad" idea of putting a storage server on your firewall.
If you want to shoot your own foot, we won't be handing you the gun.
LOL.
Well said.
-
A "very bad" idea solution of using a VM is still more secure than the "atrocious horrendous ghastly abhorrent lurid terrible horrible no good very bad" idea of putting a storage server on your firewall.
If you want to shoot your own foot, we won't be handing you the gun.
I apparently haven't said loudly enough that I don't actually want any of my edge routers to also be NAS devices, and some people apparently can't read.
-
Furthermore, virtualizing a full fledged NAS service (Providing large scale data storage to the network) is a VERY BAD idea, especially for home users as it requires expensive special hardware to do it properly.
Perhaps you could elaborate on that. What sort of performance do you require that can't be achieved by a virtalised solution? It seems there are plenty of pfSense users doing exactly that, running it as a VM together with a NAS VM, and seeing good results.
Steve
Any sufficiently competent NAS needs access to RAW disks, not encapsulated disks, or disks behind a translation layer, but for optimal error recovery the NAS needs access to raw disks. This usually means direct access to the associated controller, such that either the NAS OS is on bare metal, or the Controller is passed through to the Virtual Machine. Passing the Controller through to a virtual machine requires expensive controllers, expensive motherboards, and either Limits the user to an AMD processor, or requires a Xeon processor.
As for performance, passing your NAS RAW DISKS is not about performance, it's about reliability. Certainly any data you don't care about can be on a virtualized disk NAS. Make sure you take good backups.
As for defining "Fully Fledged", a fully fledged NAS is one that's providing the primary storage for a network. The system with the massive storage that hosts the backups and large scale multimedia. The system that hosts VM images and exports them to VM hosts. It's the Fully Fledged NAS, as opposed to the lightweight NAS that someone might virtualize to provide a limited amount of space to something that needs to be available more easily. I'm picturing, well, Pictures, or a website, or a UPNP media server…
-
There is an issue here that I've talked about before (as have others) but probably worth going into again.
pfSense has become sufficiently popular and is sufficiently flexible that it's install base encompasses a very wide range deployment scenarios. For example it was originally conceived as a direct replacement for Cisco ASA boxes but it's now installed in maybe greater numbers as a SOHO router where a WRT54 would once have been. Think about the difference between those two pieces of equipment and how wildly your expectations would vary between them. Users are coming to pfSense expecting everything both of those can provide.
Now think about adding NAS capability. In the world of the SOHO router this already exists. There are numerous NAS type add-on packages for OpenWRT for instance and you don't see people complaining about it. However if you went to Cisco complaining about not having file sharing capability on your new firewall you'd get short shrift.
Now you could argue that having it as a package allows both requirements to be satisfied but the fact is that if it were possible to do it someone would install a full NAS package on a perimeter firewall. That may then get hacked and that would be very bad for the project.I might suggest that if you are setting up a fairly serious NAS as you describe then why not just run a separate machine?
I hadn't considered that direct disk access was such an issue though. Do you have a link to any discussion on that?
Steve
-
Some of us can read fine and still don't buy the arguments.
If you cared at all about speed/resilience/security then you would not be combining a firewall with a NAS. You're talking about making a compromise to have them both on the same unit, and compromises mean sacrifices. You'll sacrifice a bit of everything to shoehorn them into the same device.
But that's the problem with Bikeshed arguments, everyone wants them to be different colors.
-
"Any sufficiently competent NAS needs access to RAW disks"
And who said my NAS didn't have raw access to the disks?
Raw Device Mapping is simple enough in esxi that anyone can do it. You don't need exp controllers either.
http://www.vm-help.com/esx40i/SATA_RDMs.phpSo yes my nas creates the file system on these disks, they are not vmdks that are given too the vm.. But even so - that could also be done as well. Sorry but you DONT need raw access to provide access to storage.
My nas also has access to the smart info on the disks, etc. etc.
Your trying to overcomplicate a simple thing like access to storage over a network.
-
jimp,
Any chance you can port pfsense to be a Windows based appliance? I want to play Solitaire.
-
Ha! ;D
https://github.com/qpleple/solitaire/tree/master/src/Cli
Steve
-
Ha! ;D
https://github.com/qpleple/solitaire/tree/master/src/Cli
Steve
I guess this might not be appropriate to build into the base system :-\ but maybe somebody will make it package ;)