From: Hannes Frederic Sowa <hannes@stressinduktion•org>
To: Stas Sergeev <stsp@list•ru>
Cc: netdev <netdev@vger•kernel.org>,
Sowmini Varadhan <sowmini.varadhan@oracle•com>
Subject: Re: Q: bad routing table cache entries
Date: Tue, 12 Jan 2016 18:26:24 +0100 [thread overview]
Message-ID: <56953740.1090204@stressinduktion.org> (raw)
In-Reply-To: <56953560.9050906@list.ru>
On 12.01.2016 18:18, Stas Sergeev wrote:
> 12.01.2016 20:06, Hannes Frederic Sowa пишет:
>> On 12.01.2016 17:56, Stas Sergeev wrote:
>>> 12.01.2016 19:42, Stas Sergeev пишет:
>>> Also the rfc1620 you pointed, seems to be saying this:
>>>
>>> A Redirect message SHOULD be silently discarded if the
>>> new router address it specifies is not on the same
>>> connected (sub-) net through which the Redirect arrived,
>>> or if the source of the Redirect is not the current
>>> first-hop router for the specified destination.
>>>
>>> It seems, this is exactly the rule we were trying to find
>>> during the thread. And it seems violated, either. Unless I am
>>> mis-interpreting it, of course.
>>
>> If you read on you will read that with shared_media this exact clause (the first of those) is not in effect any more.
> OK. But how to get such a redirect to work, if (checked with
> tcpdump) the packets do not even go to eth0, but to "lo"?
I don't know, the router must be on the same shared medium. I guess
physical reconfiguration is required?
Aren't there arp request for the host on eth0?
> And how to deal with the above quote from rfc1812?
>
>> I don't know why shared_media=1 is the default in Linux, this decision was made long before I joined here. Anyway, with shared_media=1 this is absolutely the required behavior.
> Then it should work. How? :)
What should work? Sorry, I can't follow you. Everything looks fine to
me. The default is shared_media, so servers send such redirects and
client accept those. If it would be 0 the rfc1812 applies and should
stop servers to send such redirects and clients to accept those.
Bye,
Hannes
next prev parent reply other threads:[~2016-01-12 17:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 10:54 Q: bad routing table cache entries Stas Sergeev
2015-12-29 11:58 ` Sowmini Varadhan
2015-12-29 12:06 ` Stas Sergeev
2015-12-29 12:32 ` Sowmini Varadhan
2015-12-29 12:43 ` Stas Sergeev
2015-12-29 13:19 ` Stas Sergeev
2015-12-29 15:22 ` Sowmini Varadhan
2015-12-29 15:38 ` Stas Sergeev
2015-12-29 17:40 ` Stas Sergeev
2015-12-30 12:42 ` Stas Sergeev
2015-12-30 14:17 ` Eric Dumazet
2015-12-30 17:56 ` David Miller
2016-01-04 1:05 ` Sowmini Varadhan
2016-01-04 1:32 ` Stas Sergeev
2016-01-04 17:23 ` Stas Sergeev
2016-01-12 14:40 ` Stas Sergeev
2016-01-12 14:47 ` Sowmini Varadhan
2016-01-12 20:33 ` David Miller
2016-01-12 15:34 ` Hannes Frederic Sowa
2016-01-12 15:52 ` Hannes Frederic Sowa
2016-01-12 16:03 ` Stas Sergeev
2016-01-12 16:10 ` Hannes Frederic Sowa
2016-01-12 16:42 ` Stas Sergeev
2016-01-12 16:56 ` Stas Sergeev
2016-01-12 17:06 ` Hannes Frederic Sowa
2016-01-12 17:18 ` Stas Sergeev
2016-01-12 17:26 ` Hannes Frederic Sowa [this message]
2016-01-12 17:33 ` Stas Sergeev
2016-01-12 17:47 ` Hannes Frederic Sowa
2016-01-12 20:43 ` Stas Sergeev
2016-01-12 22:26 ` Hannes Frederic Sowa
2016-01-12 22:57 ` Stas Sergeev
2016-01-12 23:07 ` Hannes Frederic Sowa
2016-01-13 12:59 ` Stas Sergeev
2016-01-12 17:41 ` Stas Sergeev
2016-01-12 15:57 ` Stas Sergeev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56953740.1090204@stressinduktion.org \
--to=hannes@stressinduktion$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sowmini.varadhan@oracle$(echo .)com \
--cc=stsp@list$(echo .)ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox