NF_IP_PRE_ROUTING,... not defined

NF_IP_PRE_ROUTING,... not defined

[Giant Sand Fan's]

because the #ifndef __KERNEL__ tags goes beyond NT_IP_PRE_ROUTING,..
defines , this change appears in 2.6.25 (because I works in 2.6.22)
and I cannot compile my kernel module hook with that version.

There is a way to do a correct development-compilation with this headers?

I cannot find anything about this issue.Yes I can move the "#endif"
but i think that must not be right thing.

So sorry if I'm out of scope.
-- 
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

Re: NF_IP_PRE_ROUTING,... not defined

[Patrick McHardy]

Giant Sand Fan's wrote:
> because the #ifndef __KERNEL__ tags goes beyond NT_IP_PRE_ROUTING,..
> defines , this change appears in 2.6.25 (because I works in 2.6.22)
> and I cannot compile my kernel module hook with that version.
> 
> There is a way to do a correct development-compilation with this headers?
> 
> I cannot find anything about this issue.Yes I can move the "#endif"
> but i think that must not be right thing.
> 
> So sorry if I'm out of scope.

The kernel doesn't need these definitions anymore, so they're not
available to avoid people using them.

For external modules that need to compile with multiple version,
you can either add the necessary definitions yourself (the values
are part of the ABI and unchangable) or possibly use the compat
headers from xtables-addons.

Re: NF_IP_PRE_ROUTING,... not defined

[Giant Sand Fan's]

ok, thanks, added by hand.

In my aim to port my netfilt-routing soft from 2.6.22 to 2.6.25 i have
too a problem, my *skb pointers are null (skb seems ok) and i don't
know if there is more related to thoses changes to 2.6.25 as define
__KERNEL__ thing in netfilter_ipv4.h any clue,idea, doc about those
complete changes.

2008/11/10 Patrick McHardy <kaber@trash.net>:
> Giant Sand Fan's wrote:
>>
>> because the #ifndef __KERNEL__ tags goes beyond NT_IP_PRE_ROUTING,..
>> defines , this change appears in 2.6.25 (because I works in 2.6.22)
>> and I cannot compile my kernel module hook with that version.
>>
>> There is a way to do a correct development-compilation with this headers?
>>
>> I cannot find anything about this issue.Yes I can move the "#endif"
>> but i think that must not be right thing.
>>
>> So sorry if I'm out of scope.
>
> The kernel doesn't need these definitions anymore, so they're not
> available to avoid people using them.
>
> For external modules that need to compile with multiple version,
> you can either add the necessary definitions yourself (the values
> are part of the ABI and unchangable) or possibly use the compat
> headers from xtables-addons.
>



-- 
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

Re: NF_IP_PRE_ROUTING,... not defined

[Giant Sand Fan's]

Hi,

I'm answering to myself . The problem is that from , i think, 2.6.24
the interface of the hook function has a *skb_buff and not a
**skb_buff.


Thanks.

2008/11/11 Giant Sand Fan's <rampxxxx@gmail.com>:
> ok, thanks, added by hand.
>
> In my aim to port my netfilt-routing soft from 2.6.22 to 2.6.25 i have
> too a problem, my *skb pointers are null (skb seems ok) and i don't
> know if there is more related to thoses changes to 2.6.25 as define
> __KERNEL__ thing in netfilter_ipv4.h any clue,idea, doc about those
> complete changes.
>
> 2008/11/10 Patrick McHardy <kaber@trash.net>:
>> Giant Sand Fan's wrote:
>>>
>>> because the #ifndef __KERNEL__ tags goes beyond NT_IP_PRE_ROUTING,..
>>> defines , this change appears in 2.6.25 (because I works in 2.6.22)
>>> and I cannot compile my kernel module hook with that version.
>>>
>>> There is a way to do a correct development-compilation with this headers?
>>>
>>> I cannot find anything about this issue.Yes I can move the "#endif"
>>> but i think that must not be right thing.
>>>
>>> So sorry if I'm out of scope.
>>
>> The kernel doesn't need these definitions anymore, so they're not
>> available to avoid people using them.
>>
>> For external modules that need to compile with multiple version,
>> you can either add the necessary definitions yourself (the values
>> are part of the ABI and unchangable) or possibly use the compat
>> headers from xtables-addons.
>>
>
>
>
> --
> Please avoid sending me Word or PowerPoint attachments.
> See http://www.gnu.org/philosophy/no-word-attachments.html
>



-- 
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html