Project

General

Profile

Actions

Bug #6910

closed

Pre-fill 'interface' field when creating firewall rule on interface -> efficiency

Added by Hollander Hollander over 7 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/10/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

Now it is possible to create a firewall rule on a vlan tab, and fill in the wrong interface in that rule. Aside from that, it isn't efficient.

It is a simple copy field to field. When in FW rules / VLAN100 tab, pre-fill field 'interface' with ; VLAN100', and disable any other choices to prevent errors. Better yet: make it read only. Better yet: don't show that field at all.

Only show it and make it R/W in floating FW-rules.

Actions #1

Updated by Jim Pingle over 7 years ago

  • Status changed from New to Rejected

Being able to edit the interface allows you to move a rule from one interface to another. (e.g. copy LAN rule, edit LAN rule, switch interface to DMZ)

It should not be locked down.

Actions #2

Updated by Hollander Hollander over 7 years ago

1. Button: 'copy'
2. Popup: which fields to change (interface);
3. Save = copied with altered values.

Actions #3

Updated by Jim Pingle over 7 years ago

You're assuming everyone uses it the same way you use it, which isn't the case. Removing functionality to prevent foot-shooting isn't a good idea.

Actions #4

Updated by Hollander Hollander over 7 years ago

I'm assuming people want to work efficient.

What is wrong with copying a field into a field to make sure people don't get RSI and don't waste their time on filling fields manually that a computer can do for you? Because that was my main proposal.

I'm used to a change mode versus a display mode, which is why I suggest read only or hide. But that was the detail, not the main suggestion. I can understand your point for this detail, so scrap that detail. It leaves the main suggestion.

Let's assume I need to do work on 600 VLANs. A (computer) system that automatically copies field A to field B avoids a lot of useless clicking.

Actions #5

Updated by Hollander Hollander over 7 years ago

I mean it constructively, btw, not to whine or something.

Actions #6

Updated by Jim Pingle over 7 years ago

But the details you mention are not solved by this suggestion. The interface is already filled/selected when you create or copy a rule. To lock that would reduce functionality (the ability to edit and move a rule).

Locking the field would take away the ability to edit a rule and move it to a new interface in one step. That would make moving a rule a much longer process because people would have to duplicate, change the interface, and then remove the old rule.

So in attempting to solve one problem you've made a much more common use several steps longer and more inefficient.

Actions

Also available in: Atom PDF