Re: [RFC PATCH nf-next 0/1] payload mangling support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09.11, Jan Engelhardt wrote:
> 
> On Monday 2015-11-09 15:10, Patrick McHardy wrote:
> 
> >The following patch adds support for payload mangling. It supports updating
> >all fields except those included in pseudo headers since it only supports a
> >single checksum update operation. So it can not be used for stateless NAT.
> >
> >Checksum updates currently only support internet checksums and assume the
> >mangled data is actually covered by the checksum. Userspace only allows use
> >for these protocols.
> >
> >So the main questions is basically, do we want to support stateless NAT?
> 
> Some people ask for that sort of thing every now and then, so it
> depends on whether you want to please them. On the upside, they only
> seem to request L3 address editing and L3addrs-inside-ICMP(v6), so
> the amount of protocol handlers needed is small.

Yeah, but the l3 addresses are embedded in the protocol specific pseudo
header: There are basically two possibilities:

* add a paremeterized pseudo header update function to the payload expression.
  Requires one rule per protocol so we can set the required parameters.

* add automatic magic header updates, requires to add protocol knowledge of
  all protocols which are using this.

I'm not against supporting this per se, but I tend to go in the direction of
waiting for people that need this and describe their use cases. I don't see
any problem in adding either way later on.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Netfitler Users]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux