netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Florian Westphal <fw@strlen.de>
Cc: pablo@netfilter.org, netfilter-devel@vger.kernel.org
Subject: Re: [RFC PATCH nf-next 0/1] payload mangling support
Date: Mon, 9 Nov 2015 16:00:07 +0000	[thread overview]
Message-ID: <20151109160007.GL8098@macbook.localdomain> (raw)
In-Reply-To: <20151109155014.GB7759@breakpoint.cc>

On 09.11, Florian Westphal wrote:
> Patrick McHardy <kaber@trash.net> wrote:
> > On 09.11, Florian Westphal wrote:
> > > Patrick McHardy <kaber@trash.net> wrote:
> > > > So the main questions is basically, do we want to support stateless NAT?
> > > > The downside is that we have to add protocol specific checksumming functions.
> > > 
> > > For now i'm only be interested in mangling MAC addresses for nft bridge
> > > to provide ebtables snat/dnat/redirect equivalents.
> > 
> > I have not tested that, it probably needs some minor adjustments to skip
> > checksum updates for NFT_PAYLOAD_LL_HEADER, but other than that, this will
> > obviously work.
> 
> For redirect we also need to alter skb->pkttype to PACKET_HOST.
> 
> I can take care of this later if needed, I'd just need advice on
> how to add this (meta statement?).

Good point. I guess that would be the proper solution, I don't think we want to
try to figure out whether an address is local in the payload module.


      reply	other threads:[~2015-11-09 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 14:10 [RFC PATCH nf-next 0/1] payload mangling support Patrick McHardy
2015-11-09 14:10 ` [RFC PATCH nf-next 1/1] netfilter: nft_payload: add packet " Patrick McHardy
2015-11-23 12:31   ` Pablo Neira Ayuso
2015-11-23 12:45     ` Patrick McHardy
2015-11-09 15:22 ` [RFC PATCH nf-next 0/1] payload " Jan Engelhardt
2015-11-09 15:37   ` Patrick McHardy
2015-11-09 15:30 ` Florian Westphal
2015-11-09 15:41   ` Patrick McHardy
2015-11-09 15:50     ` Florian Westphal
2015-11-09 16:00       ` Patrick McHardy [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=20151109160007.GL8098@macbook.localdomain \
    --to=kaber@trash.net \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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).