From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Tushar Shinde <mtk.tushar@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: IPv6 Policy based routing not working.
Date: Wed, 27 Aug 2014 08:05:46 +0200 [thread overview]
Message-ID: <1409119546.11976.11.camel@localhost> (raw)
In-Reply-To: <CABQpAL4zbeqX4X1Kuzw-+FOppmYx7VzTzJn9OMLyYVBdS0Bz9w@mail.gmail.com>
On Mi, 2014-08-27 at 11:32 +0530, Tushar Shinde wrote:
> So do we need to always use ipv6 address to bind unlike ipv4?
No, I think SO_BINDTODEVICE should work. But ping6 does not use it, so
one could add support for this to ping with a new option.
ping6 uses cmsg with undefined ipv6 source address but set ifindex and
that's not at all like SO_BINDTODEVICE.
Bye,
Hannes
next prev parent reply other threads:[~2014-08-27 6:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 16:02 IPv6 Policy based routing not working Tushar Shinde
2014-08-26 22:01 ` Hannes Frederic Sowa
2014-08-27 4:54 ` Tushar Shinde
2014-08-27 5:55 ` Hannes Frederic Sowa
2014-08-27 6:02 ` Tushar Shinde
2014-08-27 6:05 ` Hannes Frederic Sowa [this message]
2014-08-27 13:41 ` Tushar Shinde
2014-08-27 14:19 ` Hannes Frederic Sowa
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=1409119546.11976.11.camel@localhost \
--to=hannes@stressinduktion.org \
--cc=mtk.tushar@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).