From: Ben Greear <greearb@candelatech.com>
To: CLOSE Dave <Dave.Close@us.thalesgroup.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Trying to ping from a subinterface.
Date: Mon, 02 Jun 2014 21:13:51 -0700 [thread overview]
Message-ID: <538D4B7F.4080302@candelatech.com> (raw)
In-Reply-To: <538D19C9.3090801@us.thalesgroup.com>
On 06/02/2014 05:41 PM, CLOSE Dave wrote:
> Stephen Hemminger wrote (in response to my complaint):
>
>>>> # ping -I eth3:sub1 172.17.30.1
>>>> ping: SO_BINDTODEVICE: Invalid argument
>
>> Interface aliases (sub interfaces) aren't real interfaces in Linux.
>> They are a deprecated way of doing multiple addresses on the same
>> device. Aliases aren't real devices, they don't behave like devices,
>> and they only are useful with ancient tools like ifconfig.
>>
>> Don't use them unless you have to deal with systems older than 10
>> years.
>
> 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.
>
> Starting fresh, I'd agree with your suggestion. But there is a lot of
> legacy code in the world...
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.
Do you actually need sub-interfaces for some reason, or can you just use
multiple IPs on one interface (or maybe mac-vlans)?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-06-03 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 20:47 Trying to ping from a subinterface CLOSE Dave
2014-06-03 0:35 ` Stephen Hemminger
2014-06-03 0:41 ` CLOSE Dave
2014-06-03 4:13 ` Ben Greear [this message]
2014-06-03 16:29 ` CLOSE Dave
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=538D4B7F.4080302@candelatech.com \
--to=greearb@candelatech.com \
--cc=Dave.Close@us.thalesgroup.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.