[PATCH 1/4] Fix expectaction mask dumping, take #3

[Harald Welte]

On Thu, Feb 16, 2006 at 10:36:20AM +0100, Patrick McHardy wrote:

> I'm not sure I understand. The new attribute still contains the same
> value as the netlink header, doesn't it? So userspace should currently
> have at least two possibilities to get the correct value:
> 
> - use the value from the netlink header
> - use the value from the tuple that comes with the mask, as the first
>   part of your patch does. This seems most logically to me since the
>   mask and the tuple belong together.

I still dream about a connection with one end in ipv4 space and the
other in ipv6.  If we ever want to cover such a model, then the tuple
needs to include l3num.
-- 
- Harald Welte <laforge at netfilter.org>                 http://netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : /pipermail/netfilter-devel/attachments/20060216/934fb4c3/attachment.pgp