From: "Timo Teräs" <timo.teras@iki.fi>
To: netdev@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>
Subject: NBMA GRE over IPsec behind NAT
Date: Wed, 21 Jan 2009 11:14:04 +0200 [thread overview]
Message-ID: <4976E75C.8070804@iki.fi> (raw)
Hi,
I sent a mail earlier about this subject, see:
http://marc.info/?l=linux-netdev&m=122232910618099&w=4
I've been thinking more about this and reading the code
trying to figure out how to fix this.
One idea for the fix would be:
1. Include the NAT Original Address in NDA_LLADDR (this way
we don't have to modify struct neighbour)
2. Add new Neighbor Cache Entry Flag (NTF_NATOA?) to specify
if the NAT-OA is present
3. Modify neighbor cache to cope with the new flag and address
4. Add NAT-OA field for ipv4 in struct flowi
5. ipv4/xfrm4_policy.c: __xfrm4_find_bundle() to compare NAT-OA
if it is specified in struct flowi.
6. Possibly ipv4/xfrm4_policy.c: _decode_session4() would
extract the NAT-OA to struct flowi from skb->dst->neighbour.
Does this sound something that might work? Would it be an
acceptable approach?
- Timo
next reply other threads:[~2009-01-21 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 9:14 Timo Teräs [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-25 7:51 NBMA GRE over IPsec behind NAT Timo Teräs
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=4976E75C.8070804@iki.fi \
--to=timo.teras@iki.fi \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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).