Comment 6 for bug 448503
Revision history for this message
| Kevin Stenerson (stenersonkevin) wrote | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I'd like to make an additional comment on how useful this feature would be. There are certain servers I work with that must use a lot of non-common ports, a for some applications, and also restrict connections based on IP/etc. It would be very convenient if rules could be labeled or even tagged so that it is quicker to know whether the firewall is a problem with a service or not.
Additionaly, IPv6 support has greatly increased the number of rules that must be managed, and it can sometimes be easy to forget exactly what each one is for.