linux-kernel - routing rule with additional attributes (RTA

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAMQ79Xm2gwURrctVZOChs8CqeTxxkvsCmELH9oh5KaXq3QsxqA@mail.gmail.com>
Date:	Wed, 30 Oct 2013 13:15:04 +0400
From:	Василий Максимов <vasilii.maksimov@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: routing rule with additional attributes (RTA_DST)

Hi All,

while cretaing rules via NETLINK, I observed not (well) documented in
rtnetlink(7) behaviour.

If I created rule using RTM_NEWRULE message, I'm able to provide
RTA_DST attribute with destination IP (setting up rtmsg.dst_len to the
appropriate value).
Such message to NETLINK provides to creating following rules:
#ip ru sh
...
19999: from 10.0.0.1 to 10.10.0.11 lookup 19
...

So, could you please tell:
-can I count on this behaviour in future linux kernels?
-which additional attributes can be also passed? I tried
RTA_IIF/RTA_OIF and it looks like it works too.
-is there any way to debug how kernel choose rules?

Thanks in advance,
Vasily.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/