WebAssembly is supported as well. It has become much faster a few months back when it supported WebAssembly. On my system and using forefox it was 340 knodes/s with asm.js. With WebAssembly it is 600+ knodes/s
I was suspecting so. I presume whoever did it followed the link, noticed the engine was using asm.js and not wasm, and thought I was mistaken. But truly what the engine uses depends on the browser and its configuration.
This may be a good time to try a new relative open source product. OPNSense is a fork of PFSense with some philosophical and practical differences. Here are some notes on what and why https://docs.opnsense.org/fork/thefork.html
I'd recommend people take a look at VyOS[1] as well. It's a great router distribution, which comes with a lot of batteries included to do many, many things.
I guess I might still use pfSense when I need a _firewall_. I'd immediately grab VyOS whenever I need a router. Both can do routing and firewalling, though.
Oh yes, OPNsense. Those sure are some philosophical and practical differences. Differences as in:
- code theft
- copyright abuse
- attempt to steal pfSense trademark in Europe
- toxic project members who publicly attack anyone who dares to point out issues (including assault on all major pfSense developers).
- hiding serious vulnerabilities
- downplaying serious vulnerabilities
I think it would be healthy for you to 1) read about what copyright actually is and 2) read about what various licenses permit. There seems to be a disconnect between what is actually occurring and your understanding (and subsequent nerd-rage).
I have read your comments, visited your linked website. I think you may have some points.. To be clear I am testing OPNSense now for the first time. I thought their license is Apache. I will consider your points during my testing. I will also continue reading your posts on reddit and compare it to testing and repository data. Thank you for your comment, though somewhat harsh.
