netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gilberto Bertin <gilberto.bertin@gmail.com>
To: "Maciej Żenczykowski" <zenczykowski@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	Linux NetDev <netdev@vger.kernel.org>
Subject: Re: [BUG] Any-IP IPv6 support broken
Date: Mon, 2 Nov 2015 10:45:39 -0800	[thread overview]
Message-ID: <C98935CD-7723-4903-A4E2-DEB98DCC5912@gmail.com> (raw)
In-Reply-To: <CAHo-OowqDLe1d+bJEo9B_1AC41n+RM+5Kkq7NknA-CouWoeYAQ@mail.gmail.com>


> On 29 Oct 2015, at 17:44, Maciej Żenczykowski <zenczykowski@gmail.com> wrote:
> 
> What are you trying to do?

I would like to have a "bind-to-subnet" semantic with IPv6.

This is currently working with IPv4, and the setup is the follow:

- setup a dummy network device configured with any-IP
- add an any-IP route
- bind() on the dummy device

in this way we can effectively bind a process to a particular subnet
(by binding it to a dummy device which is receiving all the packets
from a particular subnet).

The point of using dummy devices is that we can configure multiple ones
(and so we can bind multiple processes to multiple subnets).

> 
> Does what you're trying to do work on an older kernel?  Which kernel
> version does it break at?
> 
> btw. afaik any-ip doesn't work with IPv4 on any un-patched kernel (the
> IPv4 support patch was reverted).


This is actually working with IPv4 (as I said I'm using a recent kernel,
4.1), and the fact that you say it's not supposed to work leads me to
think that maybe we are not talking about the same feature.

Cheers,
	gilberto

  reply	other threads:[~2015-11-02 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 15:00 [BUG] Any-IP IPv6 support broken Gilberto Bertin
2015-10-29 15:34 ` Eric Dumazet
2015-10-30  0:44   ` Maciej Żenczykowski
2015-11-02 18:45     ` Gilberto Bertin [this message]
2015-11-02 21:30       ` Maciej Żenczykowski
2015-10-29 18:39 ` Hannes Frederic Sowa
2015-10-29 18:58   ` Gilberto Bertin
2015-10-29 19:09     ` 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=C98935CD-7723-4903-A4E2-DEB98DCC5912@gmail.com \
    --to=gilberto.bertin@gmail.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=zenczykowski@gmail.com \
    /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).