From: David Ahern <dsahern@gmail.com>
To: Ben Greear <greearb@candelatech.com>, Trev Larock <trev@larock.ca>
Cc: netdev@vger.kernel.org
Subject: Re: VRF + ip xfrm, egress ESP packet looping when qdisc configured
Date: Mon, 13 Jan 2020 09:48:48 -0700 [thread overview]
Message-ID: <fe7ec5d0-73ed-aa8b-3246-39894252fec7@gmail.com> (raw)
In-Reply-To: <9777beb0-0c9c-ef8b-22f0-81373b635e50@candelatech.com>
On 1/7/20 3:59 PM, Ben Greear wrote:
>
> As luck would have it, I am investigating problems that sound very similar
> today.
Trev's problem is looping due to the presence of the qdisc. The vrf
driver needs to detect that it has seen the packet and not redirect it
again.
>
> In my case, I'm not using network name spaces. For instance:
use of the namespaces is solely for a standalone (single node) test. It
has no bearing on the problem.
>
> eth1 is the un-encrypted interface
> x_eth1 is the xfrm network device on top of eth1
> both belong to _vrf1
>
> What I see is that packets coming in eth1 from the VPN are encrypted and
> received
> on x_eth1.
>
> But, UDP frames that I am trying very hard to send on x_eth1
> (SO_BINDTODEVICE is called)
> are not actually sent from there but instead go out of eth1 un-encrypted.
have you added debugs to the udp code to check that device binding? What
about the fib_table_lookup tracepoint?
next prev parent reply other threads:[~2020-01-13 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 23:11 VRF + ip xfrm, egress ESP packet looping when qdisc configured Trev Larock
2020-01-03 4:44 ` David Ahern
2020-01-04 5:56 ` Trev Larock
2020-01-06 4:27 ` David Ahern
2020-01-06 5:58 ` Trev Larock
2020-01-07 22:59 ` Ben Greear
2020-01-13 16:48 ` David Ahern [this message]
2020-02-03 3:13 ` Trev Larock
2020-02-03 4:04 ` David Ahern
2020-02-21 4:52 ` Trev Larock
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=fe7ec5d0-73ed-aa8b-3246-39894252fec7@gmail.com \
--to=dsahern@gmail.com \
--cc=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
--cc=trev@larock.ca \
/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).