| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20170120094214.4d01938e@xeon-e3> Date: Fri, 20 Jan 2017 09:42:14 -0800 From: Stephen Hemminger <stephen@...workplumber.org> To: Nikolay Aleksandrov <nikolay@...ulusnetworks.com> Cc: netdev@...r.kernel.org, roopa@...ulusnetworks.com Subject: Re: [PATCH iproute2 net-next v2] ipmroute: add support for RTNH_F_UNRESOLVED On Fri, 20 Jan 2017 15:15:21 +0100 Nikolay Aleksandrov <nikolay@...ulusnetworks.com> 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 <nikolay@...ulusnetworks.com> Applied to net-next
Powered by blists - more mailing lists