From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net: vrf: Handle ipv6 multicast and link-local addresses
Date: Wed, 15 Jun 2016 12:34:48 -0700 (PDT) [thread overview]
Message-ID: <20160615.123448.416476723750890023.davem@davemloft.net> (raw)
In-Reply-To: <1465850659-27830-1-git-send-email-dsa@cumulusnetworks.com>
From: David Ahern <dsa@cumulusnetworks.com>
Date: Mon, 13 Jun 2016 13:44:16 -0700
> IPv6 multicast and link-local addresses require special handling by the
> VRF driver. Rather than using the VRF device index and full FIB lookups,
> packets to/from these addresses should use direct FIB lookups based on
> the VRF device table.
>
> Multicast routes do not make sense for the L3 master device directly.
> Accordingly, do not add mcast routes for the device, and the VRF driver
> should fail attempts to send packets to ipv6 mcast addresses on the
> device (e.g, ping6 ff02::1%<vrf> should fail)
>
> With this change connections into and out of a VRF enslaved device work
> for multicast and link-local addresses (icmp, tcp, and udp). e.g.,
>
> 1. packets into VM with VRF config:
> ping6 -c3 fe80::e0:f9ff:fe1c:b974%br1
> ping6 -c3 ff02::1%br1
> ssh -6 fe80::e0:f9ff:fe1c:b974%br1
>
> 2. packets going out a VRF enslaved device:
> ping6 -c3 fe80::18f8:83ff:fe4b:7a2e%eth1
> ping6 -c3 ff02::1%eth1
> ssh -6 root@fe80::18f8:83ff:fe4b:7a2e%eth1
Series applied.
prev parent reply other threads:[~2016-06-15 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 20:44 [PATCH net-next 0/3] net: vrf: Handle ipv6 multicast and link-local addresses David Ahern
2016-06-13 20:44 ` [PATCH net-next 1/3] net: l3mdev: Remove const from flowi6 arg to get_rt6_dst David Ahern
2016-06-13 20:44 ` [PATCH net-next 2/3] net: ipv6: Do not add multicast route for l3 master devices David Ahern
2016-06-13 20:44 ` [PATCH net-next 3/3] net: vrf: Handle ipv6 multicast and link-local addresses David Ahern
2016-06-15 19:34 ` David Miller [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=20160615.123448.416476723750890023.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.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.