Project

General

Profile

Actions

Bug #11459

closed

pfBlockerNG doesn't include WireGuard interface in outbound floating rules

Added by Viktor Gurov 5 months ago. Updated 28 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
pfBlockerNG
Target version:
-
Start date:
02/19/2021
Due date:
% Done:

0%

Estimated time:
Affected Version:
Affected Architecture:

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

Actions #2

Updated by Jim Pingle 5 months ago

  • Status changed from New to Pull Request Review
Actions #3

Updated by Renato Botelho 5 months ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Viktor Gurov

PR has been merged. Thanks!

Actions #4

Updated by Danilo Zrenjanin about 1 month ago

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.

Actions #5

Updated by Christian McDonald about 1 month ago

You will need to assign the WireGuard tunnel to a pfSense interface. pfBlocker can't 'see' unassigned WireGuard tunnels.

Actions #6

Updated by Danilo Zrenjanin 28 days ago

  • 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.

Actions

Also available in: Atom PDF