The dev.netmap.ring_num = 1024 recommendation also did not work for me. Setting the value to 2048 addressed my issue. I'm no longer seeing this error: Critical eastpect stack overflow detected; terminated.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: RutgerDiehard on June 12, 2025, 11:43:37 AMIt seems the eastpect service started to have issues way before the last event at 02:44 this morning where it filled the logs every 30 seconds with:2025-06-12T02:44:11 Critical eastpect stack overflow detected; terminated
Now, attempting to start the packet service results in nothing in logs at all.
Quote from: furfix on June 10, 2025, 03:33:21 PMHello, I have a genuine question regarding Zenarmor's development. I've noticed there haven't been any updates since February, and the roadmap seems to be on hold. Additionally, the UI hasn't yet been updated to align with the new OPNsense interface. Like many others, I'm really hoping the promised multicore support will be released in July and made accessible beyond just premium users. I sincerely hope the team is doing well and continuing their great work. Thank you for all your efforts!
Quote from: dirtyfreebooter on April 16, 2025, 03:39:24 PMQuote from: Cljackhammer on April 16, 2025, 12:59:25 PMApparently, 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
Quote from: franco on January 24, 2025, 12:51:55 PMFixed now in RC2 (it's online).
Quote from: julsssark on January 24, 2025, 04:48:11 AMThank 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.