Bug #13364
closed
Using the copy (not clone) function on firewall rules unintentionally converts interface ``address`` to interface ``net``
Added by Marcos M almost 2 years ago.
Updated over 1 year ago.
Plus Target Version:
23.01
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.
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.
- Plus Target Version changed from 22.11 to 23.01
- Assignee set to Jim Pingle
- Status changed from New to In Progress
I can reproduce this on the latest dev snaps exactly as described. Working on a fix now.
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
- 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.
- Status changed from Feedback to Resolved
Working correctly on current snap
Also available in: Atom
PDF
Updated by 
Updated by