netdev - Re: RTA_SRC doesn't work?

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

Message-ID: <7ir4hp6qlb.wl%jch@pps.univ-paris-diderot.fr>
Date:	Thu, 02 May 2013 23:04:32 +0200
From:	Juliusz Chroboczek <jch@....univ-paris-diderot.fr>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org
Subject: Re: RTA_SRC doesn't work?

> > Perhaps I'm confused, then.  Isn't the lookup key the pair (dst, src)?
> > Or do I not understand the semantics of RTA_SRC?

> You're specifying on that command line the source address to use on
> outgoing frames generated by the host.

So it looks like I'm confused -- I was under the impression that's
what RTA_PREFSRC is for.  So is there a way to have a routing table
entry that matches on both the source and destination addresses of an
IP packet without setting up multiple routing tables and rules?

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