Sophos Firewall: v21.0 GA: Feedback and experiences

The new alphabetical (but not alpha-numerical?) interface-name-order does not feel very natural?
I'd expect "P1 XXX" before "P3 XXX"? - like Excel would sort a table ;)

FFin ,

Request to provide support access id, so we can investigate further.

Support Access Id send via PM. You should be able to reproduce on every other appliance as well.

Thanks for providing access, will update investigation.

FFin ,

In v21, we have resolved the issue with lexicographical ordering of interfaces. Previously, for interfaces like Port1, Port2...Port10, Port10 would incorrectly appear next to Port1, resulting in an order like Port1, Port10, Port2, and so on. This has now been fixed.

Additionally, based on feedback from various users, we’ve adjusted the interface ordering to be alphabetical, with numeric values considered only when they appear at the end of the interface name. For example, PLANInter1, PLANInter2, and PWAN3 will now appear in both alphabetical and numerical order. If a number appears within the name, only the letters before the number are considered for ordering. For example, in "P2 LAN Inter," only the letter 'P' is considered for sorting, and the rest is ignored.

 Considering both numbers and letters that appear anywhere in the name would make the sorting more complex, and the lexicographical issue would persist. This was a design choice we had to make.

In the future, we aim to further improve this and provide users with the option to customize how interfaces are ordered.

Sorry Kavan Modi but that argument makes absolutely no sense in my optinion.

An interface named "WAN2 xyz" should always be sorted after an interface "WAN1 abc", regardless of the characters that are coming after that number.
How many of all deployed appliances have more than 10 ports so that the "1, 10, 2" is a real world problem? In my opinion THAT old "sorting problem" was maybe reasonable for 1-10% of all firewall users while 90-99% are now suffering from the new unlogical sort order.

Just make the interface list adjustable (drag & drop or a configurable "rank" ID number for each interface) and just don't show unconfigured interfaces (like the UTM handled that) at all. That would be an improvement, but not the change that was made in V21...

"Just make" is always something, which is not that easy in software development. 

As stated above, there are improvements considered for the future. By now, we changed the ordering now based on the Name and not the Interface numbering. 

I know, but unlogical changes are easy to implement.
Example:

What is the logic here? (Port#s are 4,2,6 top-down)

I know, but unlogical changes are easy to implement.
Example:

What is the logic here? (Port#s are 4,2,6 top-down)

I would consider to name Interfaces with Numbers as well - But that is me. 
As stated above, we consider right now only Numbers, if attached to the first number. 

On my installation(s) - I always map WAN with numbers, to quick reference, i have WAN1 Cable and WAN2 LTE - But that is me. 

Giving it a number would also sort it as you like. 

The question is: How many people have Interfaces without any number - So WAN X etc.

We will see, after getting the first customers towards the SFOSv21.0 GA, how the adaption is and how feedback is received. 

Yes, but ONLY if I name them WAN1, WAN2, WAN3.
As soon as something naming comes after the number the sort order is not comprehensible for me...

 LuCar Toni  like "WAN1 Cable" and "WAN2 LTE" would be useful. But unfortunately that's what's not working.
See my initial screenshot or @kerbora's above.
So new sorting should be some kind of alphabetical but does not support blanks, numbers between characters and more...

It only sorts correct without any numbers, blanks, etc. or only with a single number at the very end of interface name, without anything following to the number.

So "WANCable1" and "WANLTE2" would sort correctly - but impacting readability and i cannot include Port Number as well.

We will look into this in more detail, if we missed certain use cases.