- The Delete option under Zones and Policies for DMZ is grayed out. I created a DMZ because my Vonage adapter stopped working, but I don’t need it now and would like to delete it, but it doesn’t seem to work.
- Under DNS and DHCP > Static Leases, it displays1-10 on the first page by default. I have 22 total. Changing Show to 100 doesn’t do anything. I still need to select page 2.
1 Like
AFAIK is by design, to avoid mistakes from the users.
maybe @andre8244 knows better than me.
Issue confirmed: DHCP: static leases page size change doesn't work properly · Issue #740 · NethServer/nethsecurity · GitHub
AFAIK is by design, to avoid mistakes from the users.
maybe @andre8244 knows better than me.
I confirm that special zones such as ‘dmz’ cannot be deleted by design. Looks like creating one of them and then trying to delete it is a corner case.
Nice.
Well. I’d use this approach (create a new zone, test, write notes about the “correct config”, then delete the zone) in existing environment for a complete revamp of an existing one.
It’s a really niche case, because most of the time if you’re careful and take notes on what a rule does and how should be positioned… you don’t need to create form scratch the whole shebang about a zone…
Also, replacing an “host” (a special one) on a zone well… if it’s into DMZ it’s quite sanitized place for take experiments (if you don’t mess too much with interactions).
Question:
if a zone is deleted… what happens to all zone-related objects and rules?
Rules on non-existent zones are ignored
1 Like
So won’t be deleted.
Are marked in any way for saying “this actually don’t works”?
Currently they are not, but this might be a nice improvement
1 Like
So, currently, deleting a custom zone leave the rule panel in… a confusing state because the sysadmin have to determine by own means what rules are actually enforced and what not.
UX… let’s see might be improved for this scenario.
Agree
Specifically with respect to DMZ, why not create it as part of the default config? Most small routers already have it. I bet that’s the only zone the vast majority of users would ever want to use with Nethserver. That way, my obsessive-compulsive disorder (OCD) won’t be triggered when i find out the create operation isn’t transitive 
I agree.
@davide_marini can you check if is possible?
If so, I propose to create a card for the future developments.
I would like also to rethink this one: permit the users to delete the zone even if in use.
What do you think @Lucia_A ?
We prefer a clean initial configuration without unnecessary zones, it makes nft even more efficient.
I know that @davide_marini has some ideas for the UI to easily create most common zones, but for now is not on the road map.