Messages

I ran into this issue with Protectli devices using Coreboot and the 25.1 installer as well. I was able to get the installer working properly by doing the following:

• Spool up FreeBSD VM and attached the installer .img as a second hard drive
• Figure out which device was the .img using gpart list
• Create a directory and mount the device
• Edit the /mnt/directory/boot/device.hints and set hint.uart.0.at="isa" and hint.uart.1.at="isa"
• Un-mount the device, disconnect the .img from the VM and write it out to a USB

I don't know if this was a bad idea or not, but was able to wipe the device from the installer, install 25.1 and import the config backup from a second USB device, and the serial console worked in both the installer and the device itself once the upgrade completed.

My colleague figured it out: assigning the wg0 interface under Interfaces - Assignments and then enabling it immediately fixed the issue. Oddly enough, this was only required on one end of the tunnel; Wireguard on the other OpnSense device worked fine without this fix. 

Hi All
I'm having some trouble getting a wireguard site-to-site connection working; wireguard is enabled and configured on each side but neither shows any handshake or traffic. Both of the WAN addresses are static and public. Here are the diagnostic steps I have take so far:

• Tested networking between the WAN addresses on the two sites using both ICMP and TCP socket tests, both pass
• Rebuilt the tunnel using public keys without special characters
• Ran firmware Health audit
• Stoped and started Wireguard service using every means available as well as rebooting both firewalls
• Ran wg command in shell, both sides show appropriate configs
• Ran packet captures on both WAN ports filtered to UDP and Wireguard port, shows no traffic

Anyone have any ideas what I am missing here?