Bug #11613: Pushing WireGuard traffic out a specific GW using static routes requires a reboot to revert. - pfSense - pfSense bugtracker

Actions

Copy link

Bug #11613

closed

Pushing WireGuard traffic out a specific GW using static routes requires a reboot to revert.

Added by Christian McDonald almost 4 years ago. Updated almost 3 years ago.

Status:

Rejected

Priority:

Normal

Assignee:

Category:

WireGuard

Target version:

Start date:

03/03/2021

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Force Exclusion

Affected Version:

Affected Architecture:

Description

I initially had my WireGuard traffic going out a secondary WAN using a static route with the remote wireguard endpoint as a /32 route. This worked great. I'm now using a gateway group as the pfSense default gateway and so I no longer needed this static route. Simply removing the static route and clearing state table wasn't enough to get WireGuard honoring the change.