From: Ben Greear <greearb@candelatech.com>
To: Trev Larock <trev@larock.ca>, David Ahern <dsahern@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: VRF + ip xfrm, egress ESP packet looping when qdisc configured
Date: Tue, 7 Jan 2020 14:59:46 -0800 [thread overview]
Message-ID: <9777beb0-0c9c-ef8b-22f0-81373b635e50@candelatech.com> (raw)
In-Reply-To: <CAHgT=KdW3hNy4pE+prSA1WyKNu0Ni8qg0SSbxWQ_Dx0RjcPLdA@mail.gmail.com>
On 1/5/20 9:58 PM, Trev Larock wrote:
> On Sun, Jan 5, 2020 at 11:29 PM David Ahern <dsahern@gmail.com> wrote:
>> I was able to adapt your commands with the above and reproduced the
>> problem. I need to think about the proper solution.
>>
> Ok thanks for investigating.
>
>> Also, I looked at my commands from a few years ago (IPsec with VRF) and
>> noticed you are not adding a device context to the xfrm policy and
>> state. e.g.,
>>
> Yes was part of my original query, that makes sense in order to be able to have
> multiple vrf each with their own xfrm policies.
> I will investigate further on it. The oif passed to xfrm_lookup seemed to be
> enp0s8 oif rather than vrf0 oif, so I was observing just cleartext
> pings go out / policy wouldn't match.
> Perhaps I'm missing something to get vrf0 oif passed for the ping packet.
As luck would have it, I am investigating problems that sound very similar
today.
In my case, I'm not using network name spaces. For instance:
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.
David: I'll be happy to test patches, and if you think it will be a while
before you can write them, if you want to point me to the likely problem places,
I can make an attempt at fixing it.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2020-01-07 22:59 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 [this message]
2020-01-13 16:48 ` David Ahern
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=9777beb0-0c9c-ef8b-22f0-81373b635e50@candelatech.com \
--to=greearb@candelatech.com \
--cc=dsahern@gmail.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).