From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Greear Subject: Re: source interface ping bug ? Date: Mon, 30 Jul 2007 09:06:10 -0700 Message-ID: <46AE0C72.3020201@candelatech.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: nano bug Return-path: Received: from ns2.lanforge.com ([66.165.47.211]:53446 "EHLO ns2.lanforge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752359AbXG3QGL (ORCPT ); Mon, 30 Jul 2007 12:06:11 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org nano bug wrote: > Can someone have a look a this and tell if it's kernel related or if I > posted this in the wrong place ? Thanks. > Last I checked, ping did not do an SO_BINDTODEVICE even if you did -i ethX. I think it just looked up the IP for that port and treated it as -i a.b.c.d. That said, I'm not sure why the behaviour changes for you between kernel releases. Maybe an 'strace' of your ping command on the different kernels would help figure out what the problem is? Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com