FYI - WAN interface wrong after upgrade from 2.4.5 to 2.5
I upgraded our hosted VM pfSense from 2.4.5 to 2.5 and lost IPSec connection.
Just wanted to find out if anyone else had this issue where WAN interface in IPSec changed for some reason.
After pulling lots of hair, found that my WAN interface was showing different in IPSec Status. It picked up one of my virtual IPs although WAN was assigned static IP.
I just went into WAN interface->assigned a different address->saved->confirmed this address in status->changed WAN back to original-> confirmed in status and it resolved.
@jakelind My update from 2.4.5p1 to 2.5.0 caused automatic IPv4 default gateway selection logic to fail. "Automatic" now incorrectly selects an OpenVPN site-to-site link as the IPv4 default. Manual selection of the right default gateway if makes everything work again. This isn't exactly what you describe, but it's close enough to seem like it could share an underlying cause.
@msswift Thank you that fixed it for me too!