Quote from: tonys on Today at 09:28:48 PM<27>1 2026-10-13T14:15:46-05:00 OPNsense.home.lan lighttpd 15457 - [meta sequenceId="1"] (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.85/src/gw_backend.c.384) child signalled: 9
Quote from: Greg_E on Today at 07:40:18 PMThat is something to consider, I hadn't thought about the storage being any part of the slowness. There are other reason to buy the product, the policies flexibility is one of them. And when you find a product that you like, it's nice when you can support it and keep it moving forward.For me what gave me the hint is these errors :
[52805] 196.658358 [1089] netmap_obj_free ouch, double free on buffer 18426
[52805] 196.658370 [1089] netmap_obj_free ouch, double free on buffer 18428
[52805] 196.658381 [1089] netmap_obj_free ouch, double free on buffer 18432
[52807] igb1: link state changed to UP
[52854] swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2101141, size: 65536
[52866] swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2108016, size: 16384
[52874] swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2101141, size: 65536
[52886] swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2108016, size: 16384 Quote from: jarb638 on Today at 01:50:26 PM2. What would happen if I configured a separate WAN IP address on each OPNsense node but kept CARP only on the internal interfaces?So WAN IP of node A would only be available if A has the master role and the WAN IP of B would only be available if B is master. I think, that's not what you want at all.
Quote from: jarb638 on Today at 01:50:26 PMCould the secondary node take over the internal VIPs and continue operating through its own WAN connection?Yes, but your WAN IP changes then. This might not be desired.