netdev - Re: Trying to ping from a subinterface.

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: <538DF7F9.4020306@us.thalesgroup.com>
Date:	Tue, 3 Jun 2014 09:29:45 -0700
From:	CLOSE Dave <Dave.Close@...thalesgroup.com>
To:	Ben Greear <greearb@...delatech.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Trying to ping from a subinterface.

I wrote:

> I apologize to the group. I had been led to believe this was working on
> earlier Fedora releases. In fact, it was complaining but then falling
> back to the main interface and performing the ping anyway. What is new
> is the refusal to fall back.

Ben Greear answered:

> SO_BINDTODEVICE could never work on sub-interfaces as far as I know,
> but maybe older versions of ping just didn't bother doing SO_BINDTODEVICE.

It appears that the older version tried the call, got a failure,
complained about it, and then continued by using the main interface
instead. The exit code was not affected.

The current version tries the call, fails, complains, and exits with
code 2.

> Do you actually need sub-interfaces for some reason, or can you just use
> multiple IPs on one interface (or maybe mac-vlans)?

I can live without them. But they do provide a nice way to reference
an address by name.
-- 
Dave Close