On Fri, 20 Jan 2017 15:15:21 +0100 Nikolay Aleksandrov <[email protected]> wrote:
> This patch adds a new field that is printed in the end of the line which > denotes the real entry state. Before this patch an entry's IIF could > disappear and it would look like an unresolved one (iif = unresolved): > (3.0.16.1, 225.11.16.1) Iif: unresolved > with no way to really distinguish it from an unresolved entry. > After the patch if the dumped entry has RTNH_F_UNRESOLVED set we get: > (3.0.16.1, 225.11.16.1) Iif: unresolved State: unresolved > for unresolved entries and: > (0.0.0.0, 225.11.11.11) Iif: eth4 Oifs: eth3 State: resolved > for resolved entries after the OIF list. Note that "State:" has ':' in > it so it cannot be mistaken for an interface name. > > And for the example above, we'd get: > (0.0.0.0, 225.11.11.11) Iif: unresolved State: resolved > > Also when dumping all routes via ip route show table all, it will show > up as: > multicast 225.11.16.1/32 from 3.0.16.1/32 table default proto 17 unresolved > > Signed-off-by: Nikolay Aleksandrov <[email protected]> Applied to net-next
