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-next>] [day] [month] [year] [list]
Message-ID: <51891E0D.7050907@msgid.tls.msk.ru>
Date:	Tue, 07 May 2013 19:30:21 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	netdev <netdev@...r.kernel.org>
Subject: source IP address for ARP requests

Hello.

With a somewhat unusual configuration:

 eth0  10.0.0.1/32
 eth1  192.168.1.1/24
 route add 10.0.0.2 dev eth1 src 10.0.0.1

namely, so that just one ip address is available
on an "unrelated" subnet, with "our" address taken
from another interface.

With this config, ARPs for 10.0.0.2 are sent to eth1
with source address of 192.168.1.1, even if "src"
is configured for the route in question:

 9:28:46.220680 ARP, Request who-has 10.0.0.2 tell 192.168.1.1, length 28

Is that right, or should the host send ARP requests
with src=10.0.0.1?

This is kernel 3.2(.40).

Thank you!

/mjt
--
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