From: David Ahern <dsahern@gmail.com>
To: Jeff Barnhill <0xeffeff@gmail.com>, netdev@vger.kernel.org
Subject: Re: v6/sit tunnels and VRFs
Date: Wed, 25 Oct 2017 15:31:35 -0600 [thread overview]
Message-ID: <fc420b5d-f179-a1fb-9cf5-ce1820870c83@gmail.com> (raw)
In-Reply-To: <CAL6e_pdXJFoVVCfAOc9D_kE73juGQzjoUueEBvEMS=cq5CDKkg@mail.gmail.com>
On 10/25/17 2:45 PM, Jeff Barnhill wrote:
> Are v6/sit tunnels working with VRFs?
>
> For instance, I have a very simple configuration with three VMs
> running 4.13.0-16 (Ubuntu Server 17.10) kernels. VM3 is setup as a
> router for separation. VM1 and VM2 have static routes to each other
> via VM3. All VMs have v4 interfaces configured. If I setup a sit
> tunnel with v6 addrs from V1 to V2, tunneled data flows as expected
> (verified with ping) and can be seen via tcpdump on VM3. However, if
> I create a VRF on VM2 and enslave the v4 interface and tunnel to that
> VRF, data does not leave VM2 and ping displays "Destination Host
> Unreachable". I did verify that basic v4 ping works between VM1 and
> VM2 with the v4 interface on VM2 enslaved to VRF device.
>
> If this should work, I can provide more details with configuration commands.
Please provide configuration details and I'll take a look
next prev parent reply other threads:[~2017-10-25 21:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 20:45 v6/sit tunnels and VRFs Jeff Barnhill
2017-10-25 21:31 ` David Ahern [this message]
2017-10-26 3:28 ` Jeff Barnhill
2017-10-26 17:24 ` David Ahern
2017-10-27 5:19 ` Jeff Barnhill
2017-10-27 16:25 ` David Ahern
2017-10-27 20:59 ` Jeff Barnhill
2017-10-27 22:53 ` David Ahern
2017-10-28 2:43 ` Jeff Barnhill
2017-10-29 15:48 ` David Ahern
2017-10-31 22:20 ` Jeff Barnhill
2017-10-31 22:36 ` David Ahern
2017-10-31 22:42 ` David Ahern
2018-04-12 16:54 ` Jeff Barnhill
2018-04-13 2:25 ` David Ahern
2018-04-13 20:23 ` Jeff Barnhill
2018-04-13 20:31 ` David Ahern
2018-04-14 22:07 ` Jeff Barnhill
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=fc420b5d-f179-a1fb-9cf5-ce1820870c83@gmail.com \
--to=dsahern@gmail.com \
--cc=0xeffeff@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).