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>] [day] [month] [year] [list]
Date:	Mon, 11 Apr 2011 21:33:46 +0200
From:	Oskar Berggren <oskar.berggren@...il.com>
To:	netdev@...r.kernel.org
Subject: arp_solicit and source ip selection

Hi,

arp_solicit() tries to use the source IP-address of the IP-packet that
caused an ARP resolution to be necessary, when sending an ARP request.
If the IP-packet is not generated locally, that its source IP cannot
be reused in the ARP packet, and instead inet_select_addr() is called
for the relevant network interface.

Any reason why arp_solicit() could not, or should not, use the routing
subsystem to determine source IP address for the ARP request? That
would enable it to take account of any "src" directives specified in
the routing tables.

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