From: "Ilya V. Matveychikov" <i.matveychikov@securitycode.ru>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: <netdev@vger.kernel.org>
Subject: Re: question: update_pmtu doesn't update dst mtu
Date: Thu, 10 Apr 2014 12:28:49 +0400 [thread overview]
Message-ID: <53465641.4070407@securitycode.ru> (raw)
In-Reply-To: <20140409203010.GE27255@order.stressinduktion.org>
On 10.04.2014 00:30, Hannes Frederic Sowa wrote:
> On Wed, Apr 09, 2014 at 12:17:33PM +0400, Ilya V. Matveychikov wrote:
>> Works fine, thanks! By the way, could you briefly explain why routes are
>> separated to input and output? What are the benefits?
>
> Core routing table is not split by input and output, merely the dst
> construction and surrounding lookup and policy checks are seperated for input
> and output.
>
> Output does not have to deal with source address validation e.g. but has to do
> source address selection.
>
> Quite hard to answer, I guess the design emerged quite naturally. ;)
OK, I've got it. Thanks again.
next prev parent reply other threads:[~2014-04-10 8:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 11:37 question: update_pmtu doesn't update dst mtu Ilya V. Matveychikov
2014-04-03 11:58 ` Hannes Frederic Sowa
2014-04-03 12:07 ` Ilya V. Matveychikov
2014-04-03 12:14 ` Hannes Frederic Sowa
2014-04-03 12:27 ` Ilya V. Matveychikov
2014-04-08 9:03 ` Ilya V. Matveychikov
2014-04-08 14:57 ` Hannes Frederic Sowa
2014-04-09 8:17 ` Ilya V. Matveychikov
2014-04-09 20:30 ` Hannes Frederic Sowa
2014-04-10 8:28 ` Ilya V. Matveychikov [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-03 11:57 Ilya V. Matveychikov
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=53465641.4070407@securitycode.ru \
--to=i.matveychikov@securitycode.ru \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.