Thanks you for the report. It is difficult to convey ipv4 vs ipv6 vs both in list form and currently ufw lists any ipv6 rules with '(v6)' as part of the To and From (as seen in your paste). It isn't clear to me how adding an 'IPv6' break would improve this... I'm going to mark this as wishlist while I think about it.
Regarding the side note, the person who posted the question was unaware of https://bugs.launchpad.net/ufw/+bug/1880453 which speaks to future support (it isn't needed as ufw will use the nft backend if the system is configured to do so). ** Changed in: ufw (Ubuntu) Importance: Undecided => Wishlist ** Changed in: ufw (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1898696 Title: add some deliminiter between ipv4 and ipv6 in ufw status Status in ufw package in Ubuntu: Confirmed Bug description: "ufw status numbered" shows all the rules in one block, numbered from top to bottom. First are the ipv4 rules, then the ipv6. This has led to some irritation. A user asked how to add a IPv4 rule to the end of the list. https://answers.launchpad.net/ubuntu/+source/ufw/+question/692096 Inserting ipv6 rules to the correct position is not easy to understand https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1368411 My suggestion is to at least add some separator between the ipv4 and ipv6 rules in the output of "ufw status". A blank line, or a comment line (# IPv6 rules:) would be fine. This would indicate that not both rule lists, but only one of them, is applied to a connection. ## output suggestion: Status: active To Action From -- ------ ---- [ 1] 22/tcp ALLOW IN Anywhere [ 2] 8080:8090/tcp ALLOW IN Anywhere # mywww [ 3] WWW Full ALLOW IN Anywhere # IPv6 rules: [ 4] 22/tcp (v6) ALLOW IN Anywhere (v6) [ 5] 8080:8090/tcp (v6) ALLOW IN Anywhere (v6) # mywww [ 6] WWW Full (v6) ALLOW IN Anywhere (v6) ## system info ufw --version: ufw 0.35 #### side note But maybe this is irrelevant as long as the future plans of ufw are unclear. (https://answers.launchpad.net/ubuntu/+source/ufw/+question/692803) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1898696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
