Bug #11459
closed
pfBlockerNG doesn't include WireGuard interface in outbound floating rules
Added by Viktor Gurov almost 5 years ago.
Updated over 4 years ago.
Description
pfBlockerNG needs an option on the General tab for "WireGuard" similar to the "IPsec", "OpenVPN" and "L2TP VPN" options.
Without the option the auto outbound floating rules do not have the WireGuard interface group selected.
same as #8332
- Status changed from New to Pull Request Review
- Status changed from Pull Request Review to Feedback
- Assignee set to Viktor Gurov
PR has been merged. Thanks!
Tested on the latest RC release.
pfBlockerNG-devel 3.0.0_16
After enabling a Wireguard tunnel the interface still doesn't show up under pfBlockerNG IP and DNSBL tabs. Please check.
You will need to assign the WireGuard tunnel to a pfSense interface. pfBlocker can't 'see' unassigned WireGuard tunnels.
- Status changed from Feedback to Resolved
After enabling the Wireguard service, the system automatically creates an interface group with the name WireGuard (Firewall/Rules). I expected it to show up in pfBlockerNG.
After manually assigning WireGuard tunnel to a pfSense interface, it shows up in pfBlockerNG.
Ticket resolved.
Also available in: Atom
PDF