Messages

Apparently, you need a business license or higher for multi core support. This is laughable. In this day and age, charging for multi core support, seriously? Modern CPU's have had multiple cores for years. What software company charges for multi core support? NONE, except for Zenarmor you need to revisit your strategy. Multi core support is nothing novel or innovative. All modern software applications support it.

what. the whole reason i want multi-core support is so i can downgrade my home hardware to lower TDP cpu... ugh

You can still do it, but you will end to purchase I believe a business or higher license. Multi core won't be supported on home versions. Again, there is NO software company out there that charges for multi core support. Most companies develop there programs to support multiple cores, free of charge.


Zenarmor on the other hand releases software that doesn't support multiple cores and then releases it as a feature that must be paid for. This my friend is comical and probably the reason why no Zenarmor employees have responded to this thread. Because they know it's ludicrous. Could you imagine if Microsoft or Google required a multi core license? Microsoft Word - multi core edition.


What about this. What if Opnsense put receive side scaling (RSS) behind a paywall. For example you need to purchase Opnsense business edition to enable RSS. LOL

Apparently, you need a business license or higher for multi core support. This is laughable. In this day and age, charging for multi core support, seriously? Modern CPU's have had multiple cores for years. What software company charges for multi core support? NONE, except for Zenarmor you need to revisit your strategy. Multi core support is nothing novel or innovative. All modern software applications support it.

I just canceled my Zenarmor subscription. I reviewed the Zenarmor documentation and multi core support is behind a paywall. Apparently, you need a a more comprehensive license for multi core support? CPU's have been multi core for several years. This support should be free.

Hello,

I just wanted to report that the experimental configurations are not effective in terms of FQ-CoDel. Bufferbloat is mitigated correctly if I use the existing traffic shaper configuration. The experimental configurations don't work properly. I'm not sure if the traffic is being shaped as the shaper statistics are not updated.

I understand that these configurations are experimental. I just wanted to report my experience.

Fixed now in RC2 (it's online).

Works great. Thanks Franco.

Many thanks Franco. I wasn't sure if adding the rule was appropriate. The RC is looking good.

I'm not sure if a GitHub  issue was raised. It was discussed in the main the Beta feedback thread (first 3 pages). I thought that issue would have been addressed with the RC. I'll provide an image of my LAN ruleset. The first rule is the one the new rule that I had to add to address the LAN Web-UI issue. Before I added the rule the the default deny rule was blocking access. I'm not sure if this was introduced to address a security issue. Nothing was added to release notes about this.

Nothing fancy here in terms of firewall rules. It took some time for the rule to take effect, although I didn't reset firewall states after I made the change. The OPNsense team should probably weigh in here.

The first rule is the new one that I needed to add to address the WebUI access issue.

LAN firewall ruleset

Thank you @Cljackhammer.

Your fix worked partially. Disabling the packet filter via the command line allowed me to get into the GUI. Unfortunately, I haven't figured out a firewall rule that works to keep it fixed. My configuration is non-standard because it is a test VM. OPNsense is listening on 10.7.1.26 and setting rules to allow 443 to either the IP address or "this firewall" doesn't keep it fixed. It's a test VM, so this is just for fun.

Do you have a link to the issue on GitHub? I searched but couldn't find it. I'd like to help test the fix.

I had the same problem. I was not able access the Web-GUI because a default deny firewall rule was altered with the update that blocks access. I had to disable the packet filter on the command line, then I was able to login and then I specifically had to add a firewall rule to my lan interface allowing ip's from my lan to access the lan address 192.168.1.1 on port 443.

I believe that others have reported this issue, but it hasn't been resolved.

I identified the issue. The Zenarmor periodicals script is doign a pkg info against opnsense. I'm running the opnsense RC, so the package name is is opnsense-devel, resulting in a failure, I addressed it on my end. I assume that this issue will be resolved when I apply the release version of opnsense. I just need to remember to revise the script.

I identified the issue. The Zenarmor periodicals script is doign a pkg info against opnsense. I'm running the opnsense RC, so the package name is is opnsense-devel, resulting in a failure, I addressed it on my end. I assume that this issue will be resolved when I apply the release version of opnsense. I just need to remember to revise the script.

Expriening a flood of these errors after updating Zenarmor today. The Zenarmor periodicals CRON job is the culprit.

   *   *   *   *   Zenarmor periodicals   Sensei periodicals

2025-01-23T18:59:01-05:00   Error   configd.py   [1d76c18e-5413-43eb-91d2-5f9375733079] Script action stderr returned "b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'"

Well, found the issue. This Zenarmor CRON job is the culprit. I will post a message on the Zenarmor forum.

*   *   *   *   *   Zenarmor periodicals   Sensei periodicals    

I just ran a health check and it came up clean. Not sure wha'ts going on here.

This error is being logged every minute. Not good.

Expriening a flood of these errors after updating to the RC. Also, you might want to mention that after this upgrade you might not be able access the Web-GUI because a default deny firewall rule blocks access. I had to disable the packet filter on the command line and specifically add a rule to my lan interface allowing ip's from my lan to access the lan address 192.168.1.1 on port 443.

2025-01-23T18:59:01-05:00   Error   configd.py   [1d76c18e-5413-43eb-91d2-5f9375733079] Script action stderr returned "b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'"