Topics

Hi!

After upgraded to 22.1.10 none of the Zenarmor (ex Sensei) menu works.
Got this error:
Fatal error: Uncaught Error: Class 'Phalcon\Config' not found in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php:113 Stack trace: #0 /usr/local/opnsense/mvc/app/models/OPNsense/Base/BaseModel.php(364): OPNsense\Sensei\Sensei->init() #1 /usr/local/opnsense/mvc/app/controllers/OPNsense/Sensei/IndexController.php(21): OPNsense\Base\BaseModel->__construct() #2 [internal function]: OPNsense\Sensei\IndexController->indexAction() #3 [internal function]: Phalcon\Dispatcher\AbstractDispatcher->callActionMethod(Object(OPNsense\Sensei\IndexController), 'indexAction', Array) #4 [internal function]: Phalcon\Dispatcher\AbstractDispatcher->dispatch() #5 /usr/local/opnsense/www/index.php(72): Phalcon\Mvc\Application->handle('/ui/sensei/inde...') #6 {main} thrown in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 113

Since the 22.1.6 zerotier eats 99% of one cpu, it was perfect in 22.1.6 but went wrong in 22.1.7.

In the latest update (22.1.8) the sqlite3 is also updated to the 3.38.2.
This eats one cpu fully.

Hi!

After the upgrade i experienced a strange behaviour. The firewall randomly kills every tcp connection in every 15-20 minutes. It is a kill not connection reset, so if im on an ssh term its just frozen not got broken pipe.
Its a single gateway machine but if i disabled the state killing on gateway failure and enabled the sticky connection that help. The gateway is stable, i dint notice any gateway failure but still opnsense sometimes declared its down.
Even if i disable gateway monitoring! So this feature is pretty much garbage currently. No matter if you use or not, not reliable. Therefore every firewall with multiple gateway and load balancing is acting really weird now. I had to disable the load balancin completely.
There is a way to rollback the whole system without reinstalling? 20.7.6 was fine.

Thx!

Hi!

I have multiple opnsense virtual machine with vmxnet adapter's. All of them is 10Gbps connection.
The internet access is 1/1 Gbps. I can measure when im directly connected to with my laptop.
I use 802.1q vlan tagging on the virtual machines using simply static ip addressing.
Every opnsense vm produce the symptoms like the bandwidth reduced to around 600/600Mbps.
This issue only occured since upgrade to 20.7. It was fine with the 20.1.
My friends also experiencing this issue, it seems its some kind of overhead because we experienced this:
1000/1000 connection measured around 600/600
500/500 connection measured around 300/300
300/300 connection measured arounf 200/200

Non of them is pppoe so its not mtu issue. We use the standard 1500byte on everywhere.
If i put a soho mikrotik device instead of the opnsense it can be translate the full gigabit without an issue.
Anybody knows anything about this?

update: its the same result with e1000e adapter too using vmware.
update: using proxmox with virtio works fine.
update: the same setup working perfect with pfsense which is based on Freebsd 11 not HBSD.
It seems the HBSD is the source of all problems...

Thx!

After upgrade from the latest 20.1.x to the 20.7 the firewall crashed right after the suricata service loaded. Some sort of CPU error, i cant see its scrolling too fast, then immediately reboot the machine. This stuck into a loop.
Full clean 20.7 install then restore the config.xml also cause this issue.
So the problem is with the suricata related part in the config.xml. Or even the whole suricata module bugged.
Make sure you are disabled before the upgrade.

Hi!

My boxes all runing the recently lastest OPNsense 17.7.7_1-amd64 version.
Today i see there is a new update availabe 17.7.8.
In the firmware upgrade page i see the new version but the changelog popup not showing unless i check that by hand, and cannot offered the upgrade. Just say my version is the latest. It is the same on the console too.
Console upgrade said im in the latest version.
All my box do the same.
This is just me or somebody else experienced this issue too?