Yes and no.
This solution could generate more support cases than needed, if the admin enable, change o destroy a rule, so this and previous arrangement are/were quite useful to avoid that.
As seen in several support topics, sometimes more than admins there are wanna-be admins. Maybe i am the first of this list.
We are willing to improve the situation but still we do not have a clear design in mind for the UI.
This gonna take time, please be patient 
We will try to share a preview to gather feedback before the full implementation.
1 Like
Generally speaking, I’d think the firewall rules page should be similar to what I think the virtual hosts page should be (and also isn’t)–all the active rules should be listed there, and ideally should be able to be adjusted there. But for services managed by Neth, we shouldn’t require admins to know port numbers, tcp/udp, etc., nor to manually enter network addresses–the admin should be able to say that, e.g., ejabberd should be available on red/orange/blue/green, and Neth figure out the rest.
I’d think the ideal arrangement would be that this could be specified, in this way, from the firewall rules page (perhaps with an “advanced” option to make more detailed changes to the rules). But, as we’d previously discussed with respect to the virtual hosts issue, that means that one page needs to know about everything that might be installed, what ports it needs, on which protocols, etc. So if it isn’t practical to do it this way, it could link to the relevant settings for whatever modules are installed. But at a minimum, all the applicable rules should at least be visible there.
2 Likes
@giacomo Do you think it’s better to expand Services page or add a new Service Access page under Firewall section? And in this new page show ports and access rules.
If you want to expand actual Services page I can have an idea. If you want to create a new page I can think…
I do not have in mind a working solution, neither I can’t give some hints for a good direction for the implementation.
I just need to postpone this task and rethink the page with the design team.
1 Like
@giacomo I don’t mean to intrude, but… what do you think of something like this?
- description into tooltip on info icon
- ports on two lines (TCP and UDP)
- access showed and exchange button to change it (it opens a modal - not implemented for now - only where access is specified?)
We can also move this two column after running one if you think is better.
It’s only a purpose… I hope it can be helpful
Would you please tell us which difference is between enabled and running?
For sure it’s a good start! But we probably also need to improve the firewall part at the same time.
It has the same meaning as reported by systemctl status:
- enabled: it should be started
- running: it’s actually running
2 Likes
Do you want to have same rules into two pages as NethGUI?
I like this approach. It’s clear and all in one. 
Only thing to consider is, that it’s maybe only for lager displays suitable.
In NethGUI we have “Services” and “Network Services” page. To merge them simplifies the GUI at all IMO.
1 Like
The new implementation is read for testing thanks to @andre8244!
Check it out:
I hope we have meet all your expectations @flatspin @danb35 @pike @federico.ballarini @carsten !
3 Likes
Nice job!
2 Likes
Big thanks to @andre8244!! Really well done. 
Now there is a great overview over all services.
1 Like
Missing local rules…
# rpm -qa nethserver-fir*
nethserver-firewall-base-ui-3.8.1-1.ns7.noarch
nethserver-firewall-base-3.8.1-1.ns7.noarch
No further updates currently available (at time of post).
No testing repositories enabled…
Ok, i can thank this guy. But i still cannot see any difference. Therefore…
New updated package has to be deployed for update?
kudos to @andre8244 tnx! 
installation is ok also on armhfp and aarch64 
@pike packages are in testing, you should add “–enablerepo=nethserver-testing” to yum command
1 Like
Ok, i’m gonna wait the release.