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] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.01.1209231433560.9625@nerf07.vanv.qr>
Date:	Sun, 23 Sep 2012 14:37:39 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...i.de>
To:	ratheesh kannoth <ratheesh.ksz@...il.com>
cc:	netdev@...r.kernel.org
Subject: Re: loop back address question

On Tuesday 2012-09-18 15:42, ratheesh kannoth wrote:

>Hi ,
>
>i have two  linux machines(2.6.29 ) A & B, both  connected  to same lan network
>
>1)  if  i assign 127.0.2.1 and 127.0.2.2 to interfaces , can we ping
>each other ?  is there any way to  send packets out of interface ?

1. The route "local 127.0.0.0/8 dev lo" in the local table has a higher 
priority than the main table, so you would need to reorder that first.

2. There are a handful of places in linux where ipv4_is_loopback() is 
used on addresses to take a different path, so the chances to 
successfully get 127.0.2.0/24 packets out an interface may not be 100%.

Just in case you tried selling blocks out of your 127 block to someone..
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ