netdev - Re: Q: bad routing table cache entries

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: <20160112.153335.213439668062764562.davem@davemloft.net>
Date:	Tue, 12 Jan 2016 15:33:35 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	sowmini.varadhan@...cle.com
Cc:	stsp@...t.ru, netdev@...r.kernel.org, alexander.duyck@...il.com
Subject: Re: Q: bad routing table cache entries

From: Sowmini Varadhan <sowmini.varadhan@...cle.com>
Date: Tue, 12 Jan 2016 09:47:25 -0500

> On (01/12/16 17:40), Stas Sergeev wrote:
>> Updated testing results:
>> After I disabled shared_media not only for "all", but
>> also for _all_ interfaces individually, the problem seem to
>> have stopped. So thanks for these hints.
>> Now, as the media is actually really shared (same NIC/cable),
>> I just wonder what's going on here.
> 
> I dont know the history of the shared_media tunable (or
> the rationale behind the default) - I was just reading out the
> code - perhaps someone on the list who has the history can share 
> the motivation behind this tunable.

Most of the choices for defaults for ipv4 routing and ARP behavior
are motivated by two things:

1) host based addressing model

2) increasing the chance of successful communication with peers