On October 18, 2018 10:44:36 AM GMT+02:00, Daniel Suchy <[email protected]>
wrote:
>Hello,
>I think sorting should not be limited only to "show routes" output.
Beware. The sorted output may be significantly slower than the unsorted. The
unsorted route list will remain the default.
>Also
>other show commands needs to be sorted in human-readable order (like
>show protocols, show bfd sessions etc). In large-scale deployments
>(like
>IXP route-servers, where you're also have limited commands available
>within looking-glasses), current outputs are quite messy.
They shall be sorted in the same order as in config. This allows for having any
custom order to e.g. have bgp protocol and the appropriate pipe together at the
same place (in multitable mode) or anything else the operator thinks out of the
thin air.
If it doesn't work in this way, please report a bug with a reproducer. We
should also mention that in documentation, it is probably missing there.
>Is there any plan / road-map to change current behavior?
Not really. There is no good reason to change one arbitrary ordering to another
one, especially when the current ordering is user defined.
Anyway, it may be helpful to allow sorting wildcard includes in config. Would
that help?
Maria
>On 10/18/18 10:04 AM, Maria Jan Matějka wrote:
>> I suspect you want sorting the whole table by the prefices. This is
>> currently not supported. After we implement the sorting by prefix, it
>> won't need any special keyword in config, you will be able to request
>> sorted output in show route command.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
