On Sat, Aug 12, 2017 at 11:32:57PM +0800, JingPiao Chen wrote:
> On Sat, Aug 12, 2017 at 03:22:24AM +0300, Dmitry V. Levin wrote:
> > On Thu, Aug 10, 2017 at 09:03:22AM +0800, JingPiao Chen wrote:
> > > Note:
> > > 
> > > rule:
> > > Before v2.6.18-284-g14c0b97, rule carry struct rtmsg,
> > > now carry struct fib_rule_hdr.
> > > 
> > > $ man 7 rtnetlink # or read the old kernel
> > > RTM_NEWRULE, RTM_DELRULE, RTM_GETRULE
> > >   Add, delete or retrieve a routing rule.  Carries a struct rtmsg
> > > 
> > > Read linux kernel source code
> > > linux/net/core/fib_rules.c: fib_nl_delrule(), fib_nl_delrule();
> > > know rule carry struct fib_rule_hdr.
> > 
> > struct rtmsg and struct fib_rule_hdr are essentially the same structure,
> > iproute2 uses the former.
> 
> You mean that rule header message is struct rtmsg,
> and rule netlink attribute are FRA_*?

Like iproute2, you can use struct rtmsg but treat it as
struct fib_rule_hdr: ignore rtm_protocol and rtm_scope fields,
treat rtmsg.rtm_type as fib_rule_hdr.action, and parse FRA_* attributes.


-- 
ldv

Attachment: signature.asc
Description: PGP signature

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Strace-devel mailing list
Strace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/strace-devel

Reply via email to