netdev - Re: on-link assumption in ipv4 routing cache

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: <20081020.221312.211946478.davem@davemloft.net>
Date:	Mon, 20 Oct 2008 22:13:12 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	vladislav.yasevich@...com
Cc:	netdev@...r.kernel.org
Subject: Re: on-link assumption in ipv4 routing cache

From: Vlad Yasevich <vladislav.yasevich@...com>
Date: Mon, 20 Oct 2008 21:02:44 -0400

> This was somewhat of a surprise since I expected a EHOSTUNRACH error since
> there were no routes to the destination and SO_DONTROUTE was not set.
> 
> I am really curious as to reason for this behavior?

In general the Linux ipv4 stack tries to do things that make it more
likely for successful communication between two nodes.

This is one such example, another is the choice of using the host
based addressing model rather than the interface based addressing
model.

Alexey Kuznetsov is responsible for most of these decisions, he is
a genius.
--
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