Messages

Hi Franco,

This 'bug/issue' has likely been introduced sometime in 24.7.x, as I was running this setup for many months without any issue and the failover principle always worked.

I then switched dover to AGH at some point, so cannot pinpoint in which 24.7.x build this may have crept in.

It is definitely not working as expected in 25.1 beta.

Happy so send any logs or any other information required.

As a side question, is there any plan to build DHCP into dnsmasq itself?

I agree, I believe it came in with 24.7.12. All was fine until I updated then had a dnsmasq issue of some sort. I also noticed that my advanced settings conf file in the dnsmasq.conf.d folder was wiped out after the update. This would have just simplified my client reporting to pihole. Something else must have also happened since my DNS wasn't working at all.

Don't know what but the latest update isn't passing on requests to my defined pihole servers in /System/Settings/General.

Previous version works as expected.

I'm running 24.7.6 currently and am also having this issue. Ever since updating to 24.7.x I've been experiencing the GUI locking up. Almost every time I engage with it for longer than a handful of minutes it will lock up. Sometimes refreshing through the browser refresh button helps but sometimes I need to close and reopen the tab. No hardware changes or even setup changes were done, just the upgrade to 24.7.x

When it's not seized I can visually notice a jumpy traffic graph. Also if I try and change the position of a widget, it won't move with me and usually have to drop it somewhere in-between my chosen location.

How do I got about changing the timeout?

Another bump for this... issue.

Only occurs when LAN is selected, works fine on WAN alone.

error

Code Select Expand

<Error> -- opening devname netmap:igb1-0/R@conf:host-rings=4 failed: Device busy

I do have Zenarmor installed

All interface MTU's have been left blank.

I set netmap buff_size to 4096, error continues.

I've been learning Pen Testing and have been using Kali Linux. The other day I was attacking my alternate WIFI network sending multiple deauths etc when somehow I ended up crashing my OPNsense instance. Reboot fixed it, but couldn't see anything obvious in the logs unless I'm looking in the wrong spot.

Is it possible there's a correlation between my testing and the crash? If so where should I look to see what happened. I'm installed on baremetal with 8Gb of RAM and a decent CPU.

Hello all, strange question maybe... I have dedicated a rack server for OPNsense and would like to paint the handles orange to show off what it is running.

Does anyone know the actual Pantone color code for the orange and even the grey?