Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix for https://redmine.pfsense.org/issues/13153 #152

Merged
merged 1 commit into from May 13, 2022

Conversation

luckman212
Copy link
Contributor

@luckman212 luckman212 commented May 13, 2022

After downing & upping WG site to site tunnels, or stopping / restarting the service, any static routes are lost and the tunnels break if you're not using FRR/BGP etc.

This adds a call to system_staticroutes_configure() in wg_service.inc so the routes get re-added. I tested this on 22.05.b.20220512.0600 with 2 S2S tunnels and a RemoteAccess tunnel.

see https://redmine.pfsense.org/issues/13153

@rcmcdonald91 rcmcdonald91 merged commit 2e88b3a into rcmcdonald91:main May 13, 2022
@rcmcdonald91
Copy link
Owner

Thanks for the catch. Merged and synced upstream. Patch will be in next build cycle tomorrow morning.

@UniverseXXX
Copy link

UniverseXXX commented Dec 23, 2022

Do you know if this has actually been resolved? I'm still having this issue. I've got WireGuard 0.1.6_2 installed, but I still need to go into Routing and manually click Save in WAN Gateway, actually, I need to do it two times, only after this Wireguard Gateway gets enabled and the WireGuard package starts up.
What's interesting is that patch introduced in 0.1.6_2 (as per https://redmine.pfsense.org/issues/12808?tab=history), doesn't seem to be applied to wg_service.inc. The line calling system_staticroutes_configure() function is missing from the file. Applying manually that patch not helping either.
I'm on pfSense 22.05.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants