Netdev List
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Gilberto Bertin <gilberto.bertin@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [BUG] Any-IP IPv6 support broken
Date: Thu, 29 Oct 2015 20:09:42 +0100	[thread overview]
Message-ID: <1446145782.493380.423921913.1E80CAD4@webmail.messagingengine.com> (raw)
In-Reply-To: <E3F3A24A-F483-4026-97E5-B49F65AD2493@gmail.com>



On Thu, Oct 29, 2015, at 19:58, Gilberto Bertin wrote:
> 
> > On 29 Oct 2015, at 18:39, Hannes Frederic Sowa <hannes@stressinduktion.org> wrote:
> > 
> > Try the loopback interface:
> > 
> > ip -6 route add local abcd:abcd:abcd:abcd::/64 dev *lo*
> > 
> > Otherwise packets should end up in neighbor subsystem and you don't want
> > that, still. ;)
> > 
> 
> Thanks for the reply.
> 
> I know it’s working on the lo interface, but unluckily I need it on
> other interfaces (and aliasing lo is not an option).
> 
> Moreover:
> - the IPv6 patch explicitly refers to the possibility to do this with
>   eth0 interface (i.e. it's not a lo-only feature)
> - should it be consistent with the IPv4 behaviour? (or maybe it's not
>   supposed to work even with IPv4 addresses, and so this is a bug)

The routing commands won't automatically enable the ndisc layer to
answer neighbour discovery requests for that. The rule thing should work
but your clients somehow need to route all packets over the box with the
"anyip" route setup.

Bye,
Hannes

      reply	other threads:[~2015-10-29 19:09 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
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 [this message]

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=1446145782.493380.423921913.1E80CAD4@webmail.messagingengine.com \
    --to=hannes@stressinduktion.org \
    --cc=gilberto.bertin@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