Recent posts

#1

25.7, 25.10 Series / Re: Unbound error

Last post by spraysn - Today at 09:17:21 PM

Thanks alot! Have a nice evening!

#2

25.7, 25.10 Series / Re: Unbound error

Last post by franco - Today at 09:15:46 PM

Thanks, that helps. I think this was introduced in 25.7.8.

We'll fix it, but nothing that needs immediate attention (which I'm trying to look out for on a release day such as today).


Cheers,
Franco

#3

Hardware and Performance / Re: N150 / N355 good fits?

Last post by OPNenthu - Today at 09:13:09 PM

I wonder, is it better to have fewer (2x) but higher frequency P-cores vs. 4x or 8x "normal" cores for OPNsense?

if zenarmor had decent multi-core processing, a N150 would maybe do 10g, a N305/N355 almost certainly.

i wish protectli had an N355 version

How do you feel about their i3/i5/i7 line (VP66xx)?  They are not fanless and of course cost more, but idle TDP is 12W (100W max) per the product sheets. Also dual channel, though not sure if that makes a big difference.

Would you still take the VP2440 over a VP6650 if cost were not a factor?

#4

High availability / Re: Packet loss on HA backup f...

Last post by Monviech (Cedrik) - Today at 08:59:27 PM

Check the CAM tables of your switches, most likely there is some MAC address learning issue at play.

Follow the troubleshooting guide:

https://docs.opnsense.org/manual/how-tos/carp.html#troubleshooting

#5

High availability / Packet loss on HA backup firew...

Last post by user1234 - Today at 08:50:04 PM

I have setup a pair of firewalls using three public IPs all within a /24 subnet. This is the same setup as shown in the docs just with different IPs. https://docs.opnsense.org/_images/900px-Carp_setup_example.png.

The problem is the backup firewall (doesn't matter which one) has severe packet loss (40-80%). The primary firewall always works fine when using the VIP.

For example in the diagram above if I ping 8.8.8.8 or any other site from the backup firewall using 172.18.0.102 I get packet loss. If I failover then I get packet loss when pinging from 172.18.0.101.

I haven't got any NAT rules other than for the VIP.

Any idea what could be causing this or what I can check to debug the issue? Thanks

#6

25.7, 25.10 Series / Re: OPNsense dies every 24th h...

Last post by TomasL - Today at 08:23:38 PM

Yes I did.
Before OPNsense i was running CENTOS7 with an IP-tables firewall (https://github.com/arno-iptables-firewall/aif/), without any problems.

#7

25.7, 25.10 Series / Re: OPNsense dies every 24th h...

Last post by Seimus - Today at 08:12:11 PM

So the device lives, but no traffic is going thru?

That realtek NIC looks suspicious, did you install the additional realtek plugin?

Regards,
S.

#8

General Discussion / Re: use traffic shaper in fire...

Last post by Seimus - Today at 07:50:15 PM

I did open as well a ticket for better tracking ;)

https://github.com/opnsense/src/issues/273

Thanks Franco!

Regards,
S.

#9

25.7, 25.10 Series / OPNsense dies every 24th hour ...

Last post by TomasL - Today at 07:48:46 PM

Every 24 hour OPNsense dies, and throughput goes down to zero.
This happens when I do large uploads, i.e full bandwidth 600 Mb/s for 24 hours continuously.
After re-boot bandwidth is restored for an additional 24 hours.
Sometimesm it goes down after half an hour
HW is Gigabyte N3150 based MB, with realtek super-io (2x 1Gb/s Lan-ports).
Intel Celeron N3150, 4 cores @ 1,6 GHz
4g MEMORY.
No overheating, memory usage around 16%, CPU maxes out at 40% on the peaks.
Any sugestions on where to look.

#10

25.7, 25.10 Series / Re: Unbound error

Last post by spraysn - Today at 07:45:04 PM

Ah ok that's normal apparently when you run check and I'm seeing the same. So I guess Unbound works? A bit more text would really help clear this up.


Cheers,
Franco

What information do you need? On 23 November 2025, I edited my 'network-views.conf' file in '/usr/local/etc/unbound.opnsense.d/' . After that, I checked the configuration. It told me there were no errors.
Today is the first time I have seen this error since then.
Before writing this post, I updated to the latest version of OPNsense and rebooted. The error is still there.