Re: [PATCH 19/27] xt_policy: use the new unoin nf_inet_addr

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

 



On Jan 8 2008 16:54, Patrick McHardy wrote:
>> > >
>> > > +#ifdef __KERNEL__
>> > > +		struct {
>> > > +			union nf_inet_addr saddr;
>> > > +			union nf_inet_addr smask;
>> > > +			union nf_inet_addr daddr;
>> > > +			union nf_inet_addr dmask;
>> > > +		};
>> > > +#else
>> > > +		struct {
>> > > +			union xt_policy_addr saddr;
>> > > +			union xt_policy_addr smask;
>> > > +			union xt_policy_addr daddr;
>> > > +			union xt_policy_addr dmask;
>> > > +		};
>> > > +#endif
>> >
>> > I really dislike this uglyness, but I've applied it since
>> > there it also doesn't make much sense to leave single files
>> > using their own address definition.
>> >
>> 
>> <CES>It will all go away in a few years time</CES>
>> 
>> Ehrm, how will userspace actually deal with it?
>
>
> I don't understand what you mean with this question.
>
>
When will iptables start using the union nf_inet_addr saddr; variant?

I already figured it out myself, so don't bother. :-)
-
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