Messages

/var/logs is the right place. Unfortunately to my knowledge freeBSD's dmesg doesn't have the ability like linux to include the timestamps. Those are helpful when diagnosing.
Perhaps you are also using a service that is not part of the OS, maybe also has logs?

It's been running well for close to a year. No custom services that I'm aware of.

What type of system? Some NICs are known to have problems when ASPM is enabled.

Custom

• AsRock Rack B550D4ID-2L2T
• Intel X520-DA2 10GTek

Been running well for close to a year. However, I did recently update to 24.7 (can't recall from what but it was a major update for sure).

I just had a strange outage. DHCP devices suddenly couldn't renew their leases, static assigned devices couldn't reach the Internet. LAN/WAN interfaces on the firewall were link up. The firewall itself could ping WAN addresses. Reloading services from the console didn't help, only a full reboot did. Didn't change anything about the network or firewall today. Running  24.7.11_2.

I've reviewed the logs from the UI, even poked around at logs in /var/logs. Is there anywhere else I can look to determine what happened? (I know the exact time my devices suddenly went down.)

[Virtual IPs]

Edit: I have tried changing the virtual IP to "Proxy ARP". No effect.

Recently migrated from PFSense to OPNSense, and am struggling with this. OPNSense is on latest, 23.7.11. My configuration is below, but curl to ifconfig.me doesn't change (from my default WAN address).

1.2.3.4 is my (fake) WAN address, and 192.168.1.100 is my (fake) internal address. I want 192.168.1.100's outbound traffic to use 1.2.3.4 (as opposed to, say, 1.2.3.5).

Virtual IPs

• Mode: IP Alias
• Interface: WAN
• Network/Address: 1.2.3.4/29

Firewall: NAT: Outbound

• Mode: Hybrid
• Interface: WAN
• TCP/IP Version: IPv4
• Protocol: any
• Source address: 192.168.1.100/32
• Source port: any
• Destination address: any
• Destination port: any
• Translation/target: 1.2.3.4