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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 9 Apr 2014 22:30:10 +0200 From: Hannes Frederic Sowa <hannes@...essinduktion.org> To: "Ilya V. Matveychikov" <i.matveychikov@...uritycode.ru> Cc: netdev@...r.kernel.org Subject: Re: question: update_pmtu doesn't update dst mtu 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. ;) Bye, Hannes -- 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
Powered by blists - more mailing lists