Astronutty
Limp Gawd
- Joined
- Aug 10, 2004
- Messages
- 166
Dear CipaFilter,
I love working with every technology software and hardware item that I have ever come across, from command line to Apple-like friendly... except the CIPAFilter.
To put things into perspective, the CIPAFilter is a very powerful device, and is a rock solid product as it performs the advertized functions. Yet after two months struggling to use the CIPAFilter, thinking that me, the user was slow to learn or comprehend, it was not until today that I really examined why I struggle with it.
The reasons why have nothing to do with the power and performance, but everything to do with how the GUI interfaces with the user and certain easy to repair issues.
1) You cannot set a specific rule to expire after a set amount of time. A selector for the rule to disable itself or delete itself is needed upon expiration.
2) I have 77 Statefull Firewall rules, and they are not sortable so you can compare by title, protocol, or port. You should be able to have a priority level set that is then by default, sorted that way, yet otherwise sortable, even if it is in a reports menu.
3) Each rule is 7 lines of text tall, making my 77 rules over 7 pages of scrolling, which are non sortable.
4) When 7 pages down, the column category names are 7 pages up, so if you are trying to be super careful, you scroll up and down a lot to double check that you are inserting the proper variable into the proper field.
5) To make a rule non-editable, you must click another rule, refresh the page, or save the page to make that first clicked-on rule un-editable. It is so easy to make mistakes this way as you are tempted to close the rule with the red X. (See #8 below)
6) When you click on a rule intentionally or accidentally, the GUI changes drastically... then allows modification. I want all fields modifiable on the entire page, maybe changed items highlighted in light red so they can be tripple checked, then I can save.
7) If you make a change to a rule, then scroll down, make another change to another rule, there is no visual confirmation of which change was made on which rule made elsewhere before you save at the bottom. One rule at a time then save folks.
8) The red X that appears after clicking a rule, deletes the rule with absolutely no confirmation... (the red X in Windows, MacOS, and Linux CLOSES, not deletes)
9) No IP-MAC association comparison (that I have seen). I want to know who is attempting to connect.
10) I want rules with date stamps on their creation so I can see if a rule can be tied to an issue. (Naming the rule with creation date and time has become my standard operating procedure, albeit a chore.)
I believe the CIPAFilter is actually very dangerous as I am unable to sort and compare my new rules with the previous administrator's rules, to check for conflicting, possibly dangerous, or mistakenly made rules. I want all rules sorted together, so I see similar sorted rules together on one page to compare and analyze for dangers.
In CIPAFilter's attempt to be "Web 2.0", they have broken the user interface, and this they do in a "Web 3.0" world. (I do not like the terms "Web 2.0/3.0", but I do not know how else to explain my point clearly.)
I do not believe we should have to struggle to use our devices these days, this is a highly modifiable WebGUI we are talking about, and web GUI design experts are coming out of colleges like rain falling in the Amazon. One person could remedy all these issues in under a month of programming. My staff programmer is only in his second year of college, and I am confidant he and I could fix CIPAFilter in under two weeks.
CIPAFilter, please fix your GUI.
In honest, hopeful, and humble sincerity,
Steve Qualls
Technology Director
Chadwick School District
I love working with every technology software and hardware item that I have ever come across, from command line to Apple-like friendly... except the CIPAFilter.
To put things into perspective, the CIPAFilter is a very powerful device, and is a rock solid product as it performs the advertized functions. Yet after two months struggling to use the CIPAFilter, thinking that me, the user was slow to learn or comprehend, it was not until today that I really examined why I struggle with it.
The reasons why have nothing to do with the power and performance, but everything to do with how the GUI interfaces with the user and certain easy to repair issues.
1) You cannot set a specific rule to expire after a set amount of time. A selector for the rule to disable itself or delete itself is needed upon expiration.
2) I have 77 Statefull Firewall rules, and they are not sortable so you can compare by title, protocol, or port. You should be able to have a priority level set that is then by default, sorted that way, yet otherwise sortable, even if it is in a reports menu.
3) Each rule is 7 lines of text tall, making my 77 rules over 7 pages of scrolling, which are non sortable.
4) When 7 pages down, the column category names are 7 pages up, so if you are trying to be super careful, you scroll up and down a lot to double check that you are inserting the proper variable into the proper field.
5) To make a rule non-editable, you must click another rule, refresh the page, or save the page to make that first clicked-on rule un-editable. It is so easy to make mistakes this way as you are tempted to close the rule with the red X. (See #8 below)
6) When you click on a rule intentionally or accidentally, the GUI changes drastically... then allows modification. I want all fields modifiable on the entire page, maybe changed items highlighted in light red so they can be tripple checked, then I can save.
7) If you make a change to a rule, then scroll down, make another change to another rule, there is no visual confirmation of which change was made on which rule made elsewhere before you save at the bottom. One rule at a time then save folks.
8) The red X that appears after clicking a rule, deletes the rule with absolutely no confirmation... (the red X in Windows, MacOS, and Linux CLOSES, not deletes)
9) No IP-MAC association comparison (that I have seen). I want to know who is attempting to connect.
10) I want rules with date stamps on their creation so I can see if a rule can be tied to an issue. (Naming the rule with creation date and time has become my standard operating procedure, albeit a chore.)
I believe the CIPAFilter is actually very dangerous as I am unable to sort and compare my new rules with the previous administrator's rules, to check for conflicting, possibly dangerous, or mistakenly made rules. I want all rules sorted together, so I see similar sorted rules together on one page to compare and analyze for dangers.
In CIPAFilter's attempt to be "Web 2.0", they have broken the user interface, and this they do in a "Web 3.0" world. (I do not like the terms "Web 2.0/3.0", but I do not know how else to explain my point clearly.)
I do not believe we should have to struggle to use our devices these days, this is a highly modifiable WebGUI we are talking about, and web GUI design experts are coming out of colleges like rain falling in the Amazon. One person could remedy all these issues in under a month of programming. My staff programmer is only in his second year of college, and I am confidant he and I could fix CIPAFilter in under two weeks.
CIPAFilter, please fix your GUI.
In honest, hopeful, and humble sincerity,
Steve Qualls
Technology Director
Chadwick School District