netdev - Re: Ping Is Broken

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4AD3BC12.6020409@hp.com>
Date:	Mon, 12 Oct 2009 19:30:26 -0400
From:	Brian Haley <brian.haley@...com>
To:	Jarek Poplawski <jarkao2@...il.com>
CC:	Rob.Townley@...il.com, netdev@...r.kernel.org,
	Omaha Linux User Group <olug@...g.org>,
	CentOS mailing list <centos@...tos.org>
Subject: Re: Ping Is Broken



Jarek Poplawski wrote:
> Brian Haley wrote, On 10/12/2009 10:36 PM:
> 
>> In this case ping is doing an SO_BINDTODEVICE to eth0, so the kernel is going
>> to force the packets out of it, even if it isn't the "correct" interface.  If
>> you ran tcpdump you'd probably see an ARP resolution failure, or an ICMP from
>> a gateway.
> 
> BTW, SO_BINDTODEVICE is used only to acquire a source address, not the real
> connection (unless I miss something).

No, SO_BINDTODEVICE affects routing, as well as incoming packets - it's in macros
like INET_MATCH(), from what I've seen it restricts a socket to only use the device
specified, irregardless of the source address you're using.  For example, you can
bind to 127.0.0.1 and send packets out eth0 if sk_bound_dev_if is set to it if I
remember correctly.

-Brian
--
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