Bug #11437: WireGuard group is not printed in the interface column of the NAT rule list - pfSense - pfSense bugtracker

Bug #11437

WireGuard group is not printed in the interface column of the NAT rule list

Added by Marcelo Gondim about 2 months ago. Updated 25 days ago.

Status:

Feedback

Priority:

Normal

Assignee:

Viktor Gurov

Category:

WireGuard

Target version:

Future

Start date:

02/17/2021

Due date:

% Done:

100%

Estimated time:

Affected Version:

2.5.0

Affected Architecture:

Release Notes:

Default

Description

Hi all,

When creating a "NAT Outbound" rule and selecting the WireGuard interface, it does not appear in the listed rule after it is applied. The interface does not appear in the rule, but the rule still works. Just an aesthetic problem.

img1.jpg (69.1 KB) img1.jpg		Marcelo Gondim, 02/18/2021 07:56 AM
img2.jpg (50.9 KB) img2.jpg		Marcelo Gondim, 02/18/2021 07:56 AM
img2.jpg (61 KB) img2.jpg		Marcelo Gondim, 02/18/2021 08:00 AM

Associated revisions

Revision 4fef1c10 (diff)
Added by Viktor Gurov about 2 months ago

WireGuard interface friendly description. Fixes #11437

Revision 36ef00b5 (diff)
Added by Viktor Gurov about 1 month ago

WireGuard interface friendly description. Fixes #11437

(cherry picked from commit 4fef1c109de562f9f97d7c04d4cf8f0f041811e0)

History

#1 Updated by Marcelo Gondim about 2 months ago

File img1.jpg img1.jpg added
File img2.jpg img2.jpg added

#2 Updated by Marcelo Gondim about 2 months ago

File img2.jpg img2.jpg added

#3 Updated by Jim Pingle about 2 months ago

Subject changed from WireGuard interface does not appear in the NAT rule to WireGuard group is not printed in the interface column of the NAT rule list
Target version set to CE-Next

Updating subject to make it a little more clear.

If you look at the generated ruleset in /tmp/rules.debug, does the rule look OK there?

#4 Updated by Viktor Gurov about 2 months ago

fix:
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/140

#5 Updated by Jim Pingle about 2 months ago

Status changed from New to Pull Request Review

#6 Updated by Jim Pingle about 2 months ago

Affected Version set to 2.5.0

#7 Updated by Marcelo Gondim about 2 months ago

Hi all,

Do you need me to do some test here by my side? If you need, just say.

#8 Updated by Jim Pingle about 2 months ago

The PR is still pending so there isn't anything to try yet. Once it's committed and this issue is in a Feedback state then you can try applying the commit ID via the System Patches package, but it's not to that point.