Difference between pfSense and OpenWrt

Where did you take that image capture?

1 Like

Could OpenWrt ever become a suitable platform for x86?

It depends on your tasks.
Yes, you can already use OpenWrt to manage networking, firewalling and the like.
But, general-purpose Linux distros are more suitable in other ways.
It's unlikely to change in the near future.

1 Like

not main target but works quite good, personaly moved to pfsense for main utm , openwrt on ap, i'm happy
with this setup

2 Likes

I mean if OpenWrt can at some point be adapted as pfSense and take advantage of all the resources of the PC as they say in this forum about that OS.

1 Like

OpenWrt can use as much resources as required by the running services.
There's no need to use more if your tasks do not require it.

3 Likes

i use custom firewall rules, opendns, vlan and suricata ids - the last one saw somene try to run on openwrt but can't find it now, on pfsense/opnsense this can be configured by 15minutes by gui and works like a charm , and for me pfsense have pretty webgui with dark mode

2 Likes

PFSense is not as good as OpenSense. OpenSense seems to have more up to date packages.

3 Likes
3 Likes

maybe opensense have more packages like working wireguard and often came updates but in my case i like this pfsense webgui :slight_smile: but there is also difference in performance between *sense and openwrt like with openwrt is more than twice time faster on the same hw. there is one more world worth of try - sophos xg utm with free home license have lots of worth features and can recomend for try it .

OpenWRT will probably never be as popular as pfsense or OPNsense on x86 because pfsense/OPNSense has considerably greater capabilities than OpenWRT.

One thing OpenWRT on x86 has going for it is that being linux based, it has far greater hardware support than pfsense/OPNSense's FreeBSD. So if you have obscure NICs or wifi hardware that aren't supported in FreeBSD, OpenWRT would be option.

Another area where OpenWRT beats pfsense/OPNSense is LTE modems. FreeBSD doesn't have MBIM or QMI, so the only option for LTE connectivity in pfsense/OPNSense is PPP which limits performance pretty severely (something like 30mb/sec, IIRC).

BTW, OPNSense is a fork of pfsense. OPENSense was forked when pfsense switched to a different framework for the management web interface. Also, OPNSense targets very frequent updates with the idea that frequent updates mean better security. Pfsense updates very infrequently with the idea that less frequent updates and more testing means better stability.

I'll try not to start an ideology war here, but the pfsense developers started engaging in some decidedly unseemly and un-open-source behavior after OPNSense forked. Many people won't touch pfsense with a ten foot pole because of the behavior of the maintainers.

3 Likes

totally different animals...

one is total gw... the other embedded multitool ( yes x64/86 gw is a key one of those tools ) ... pro's and con's in each...

out of interest... what are the two top Linux based competitors to pfSense these days... used to be smoothwall and... maybe monowall for limited... smb-something or other for more 'corporate' use...???

2 Likes

There's no real linux based competitor to pfsense. Monowall was what became pfsense. Smoothwall is commercial. There's still a (well hidden) GPL version called Smoothwall Express, but it has not been updated since 2014.

Sophos has not one, but two full-featured linux based next-generation firewalls. They both are free for home use.

Untangle is linux based, but is commercial. I think they still have a free crippled home version.

Really, OpenWRT is the only linux based fully open-source alternative to pfsense/OPNsense.

3 Likes

wow... hard to believe... yup... that's when I moved away from most of those distro's ... circa 2010ish when they all seemed to start forking 'full commercial' editions...

smoothwall was very cool... my first home router used a 433-ish pentium over dialup running on smoothwall, dansguardian, transparentproxy... those were the days! :cowboy_hat_face:

3 Likes

I'm not sure that is entirely correct. What about ipfire?
https://www.ipfire.org/

2 Likes

Did not know ipfire existed.

1 Like

Screenshot from https://www.privacytools.io/operating-systems/#firmware

1 Like

I'm using NCM just fine on FreeBSD however :slight_smile:

Great answer!

I just wanted to add or maybe clear a few things:

  1. FreeBSD (as well as OpenBSD and NetBSD) are just as opensource (if not more) than Linux.
  2. The BSD license, though it might have a few restrictions not found in GPL, is in general a less strict license than GPL. One of the main differences is that the BSD license does NOT require you to public your changes or improvements, meaning you can use it anyway you like in a commercial product.

The last thing is quite important and is the reason BSD Unix'es has been used in a number of commercial products like:
Nintendo Switch
Citrix Netscaler
Playstation 3-4
... to name a few.

Even certain part of Windows uses (or used) BSD components.

The more lax license for BSD also means they can incorporate code from more projects. For instance did FreeBSD have the great ZFS filesystem (developed by Sun) long before Linux, which is probably the reason FreeNAS decided to build on FreeBSD.

But the somewhat stricter GPL license is probably the reason we have OpenWRT: the Linksys developers was required to publish there code since is was based on Linux (GPL).
Had they build it on *BSD could they have decided to keep it closed.

Only requirement for the BSD license is to keep a copyright notice (which you actually can find someplaces in Microsoft Windows).

5 Likes

Great additions @MortenVinding! Thanks :slight_smile: