Skip to content

libnm: when stringifying policy routing rule place "not" specifier after "priority"

Thomas Haller requested to merge th/policy-route-to-string-not-attribute into master

Otherwise, it just looks odd:

  "not priority 31265 from 0.0.0.0/0 fwmark 0xcb87 table 52103"

better would be

  "priority 31265 not from 0.0.0.0/0 fwmark 0xcb87 table 52103"

The "not" specifier should come after the priority. It makes more sense to read it that way. As far as parsing the string is concerned, the order does not matter. So this change in behavior is no problem.

Merge request reports