Actions
Bug #13364
closed
Using the copy (not clone) function on firewall rules unintentionally converts interface ``address`` to interface ``net``
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
23.01
Release Notes:
Default
Affected Version:
2.7.0
Affected Architecture:
Description
Tested on 22.05 and latest dev.
Steps:- Start with three interfaces, WAN, LAN, OP1
- Create a rule on OPT1: ipv4 src any, dst OPT1 addr
- Select the rule, click Copy, set it to LAN interface, and check the conversion box.
- The new LAN rule has a destination of LAN net instead of LAN address.
Updated by Kris Phillips over 2 years ago
Tested this and confirmed an issue on 22.05. Tested just using the copy button in the actual rule and this does not occur there, so it's something with the conversion process.
Updated by Jim Pingle about 2 years ago
- Plus Target Version changed from 22.11 to 23.01
Updated by Jim Pingle about 2 years ago
I can reproduce this on the latest dev snaps exactly as described. Working on a fix now.
Updated by Jim Pingle about 2 years ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Applied in changeset 749af017d77897079e759cb934461f1f4e810592.
Updated by Jim Pingle about 2 years ago
- Subject changed from Firewall rule copying converts interface ``address`` to interface ``net`` to Using the copy (not clone) function on firewall rules unintentionally converts interface ``address`` to interface ``net``
- Category changed from Web Interface to Rules / NAT
Updating subject for release notes.
Updated by Jim Pingle about 2 years ago
- Status changed from Feedback to Resolved
Working correctly on current snap
Actions