netdev - Clarification on rtnetlink requests

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALj-AT+z+Mv5ZUZWDDxquaZKu3o5qstuarz-qLcx80CH_n7LGQ@mail.gmail.com>
Date:	Wed, 19 Aug 2015 11:05:03 -0400
From:	David Chappelle <chappedm@...il.com>
To:	netdev@...r.kernel.org
Subject: Clarification on rtnetlink requests

I am a bit confused with respect to the structure of rtnetlink requests.
It seems that in some circumstances a request can look like:

    struct request
    {
        struct nlmsghdr header;
        struct rtgenmsg body;
    };

and in other cases it can look like:

    struct request
    {
        struct nlmsghdr header;
        struct ifinfomsg body;
    };

How do I know which one to use when sending RTM_GETLINK and
RTM_GETADDR requests? Furthermore, it also seems that 'struct rtattr'
can be specified at the end of the request as well. Is there any
documentation that describes this.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html