netdev - Re: Question about reading the routing table with netlink

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

Message-ID: <20130910231312.GC4794@order.stressinduktion.org>
Date:	Wed, 11 Sep 2013 01:13:12 +0200
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Fernando Gont <fernando@...t.com.ar>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: Question about reading the routing table with netlink

On Tue, Sep 10, 2013 at 11:21:44AM -0300, Fernando Gont wrote:
> Folks,
> 
> Short version of the question:
> I'm trying to loop up a routing table entry with a
> socket(AF_NETLINK,SOCK_RAW,NETLINK_ROUTE).
> 
> Everything seems fine, except that I do not quite understand what's the
> effect of setting the RTA_SRC attribute type when doing that.

It sets the source address for the routing table lookup. This is important if
e.g. rules are specified or if ipv6 subtrees are in use.

> Empirically, it seems that if the RTA_SRC attribute is set and it
> contains an address that is assigned to the interface involved in the
> route, then such address is later returned in the reply as an RTA_SRC
> attribute.

Hm, I thought that RTA_SRC only has a semantic in the request and is moslty
just copied over to the response.

Greetings,

  Hannes

--
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