Wireguard Bug in pfsense plus

[lawrencesystems]

I think we found a wireguard bug that we can only replicate in pfsense plus and not on CE.

We have a site to site setup between two systems, one plus running 22.01-RELEASE (amd64) the other CE 2.6.0-RELEASE (amd64). It's been working well for the last few months and it was setup using the guide in the documentation with static routes. (and referencing Christian McDonald site to site video)
https://docs.netgate.com/pfsense/en/latest/recipes/wireguard-s2s.html

The issue is that on pfsense plus when you start/stop or restart wireguard the static routes disappear and do not come back unless you either edit and save the interface (no changed need to be made) or by going into any one of the static routes and to an edit/save/apply. This does not occur on pfsense CE edition.

We did test on another pfsense plus 22.01 system to make sure it was not just that firewall by adding wireguard as an interface, adding a static route, restarting wireguard and the result was the same, the routes did not show up.

[lawrencesystems]

I probably should have looked at GitHub first, I am not a programmer but this looks like it might be a solution:
https://github.com/pfsense/FreeBSD-ports/commit/21c83fc18c324b248bb75cf51019dc7a1af332ac

[luckman212]

@lawrencesystems Yep, that was the solution. See redmine #13153.

Thought I was the only soul on the internet who'd encountered that problem. Figures if anyone else would have bumped up against it, it would be you guys