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
| ||
|
Date: Tue, 7 Jun 2016 16:16:02 +0530 From: Krishna Mohan <krishnamohany3k@...il.com> To: netdev@...r.kernel.org Subject: Fwd: Loopback properties in routing on linux kernel HI All, I have a question to determine the uses of multiple loopbacks interfaces(int loopback) in routing(quagga) on linux kernel. Please apologise if it is a dumb question. This is what I understand, please clarify if my understanding is correct. 1. we need them to represent a /32 ip, normally used for router-id. 2. we can measure traffic destined to that ip, via its independent statistics per loopback interface. 3. ip unnumbered uses loopbacks to represent that ip. my question is, is it necessary to have ifindex per loopback interface we create? if I create kernel loopback as lo:1 (as subinterface on default loopback in kernel) with ip assigned to it will do 1. for getting 2 and 3 done, loopback needs to be a separate netdev. is that correct? Will I be having any advantage if I configure the interface as lo:1 vs a separate netdev per loopback interface (i mean dummy netdev) to terminate the /32 destined traffic? Thanks in advance. Krishna Mohan.
Powered by blists - more mailing lists