Bug 11306 - Changing name of hostgroups is reflected in firewall rules only partially
Summary: Changing name of hostgroups is reflected in firewall rules only partially
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: all All
: Will affect an average number of users Minor Usability
Assignee: Stefan Schantl
QA Contact:
URL:
Keywords:
Depends on:
Blocks: FWBUGS
  Show dependency tree / graph
 
Reported: 2017-03-23 18:29 UTC by ipf-tom
Modified: 2021-07-26 13:45 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ipf-tom 2017-03-23 18:29:24 UTC 
How to reproduce:
(1) Create a host group.
(2) Create two firewall rules:
   (a) one with the host group as source 
   (b) one with the host group as destination
(3) change the name of the host group
(4) go back to the firewall rules

You will see, that the rule (2b) with the host group as destination does reflect the changed name of the group.
But the other rule (2a) still shows up the original name of the host group, which is not valid any more.
Comment 1 ipf-tom 2017-03-23 18:29:58 UTC 
observed in IPFire 2.19 (x86_64) - Core Update 109
Comment 2 Peter Müller 2018-02-06 20:24:58 UTC 
Is this bug still valid?
Comment 3 ipf-tom 2018-02-07 10:44:53 UTC 
(In reply to Peter Müller from comment #2)
> Is this bug still valid?
Yes, I can reproduce the problem in IPFire 2.19 (x86_64) - Core Update 117.
Comment 4 Peter Müller 2019-10-13 10:34:54 UTC 
Since Alexander used to work on the firewall CGIs, I am assigning this to him.
Comment 5 Stefan Schantl 2021-07-16 13:59:10 UTC 
I tested this on a Core 157 system and followed the guide to reproduce this issue.

Unfortunately I was not able to reproduce the error, the changed group name showed up correctly on both rules.

It seems this bug report is not valid anymore - I'm going to close this bug, please feel free to re-open if this issue still exists.
Comment 6 ipf-tom 2021-07-26 13:45:14 UTC 
Yes, the problem must have been solved meanwhile!
I did try to reproduce, but everything works fine now!