IPT_ENTRY_ITERATE

IPT_ENTRY_ITERATE

[Swapnil Nagle]

I am embarassed to ask this but : where is IPT_ENTRY_ITERATE defined ?

grep shows  only one match :

libiptc/libip4tc.c:#define ENTRY_ITERATE    IPT_ENTRY_ITERATE

Regards,
Swapnil.

Re: IPT_ENTRY_ITERATE

[Martin Josefsson]

On Thu, 23 Sep 2004, Swapnil Nagle wrote:

> I am embarassed to ask this but : where is IPT_ENTRY_ITERATE defined ?

Don't be.

> grep shows  only one match :
>
> libiptc/libip4tc.c:#define ENTRY_ITERATE    IPT_ENTRY_ITERATE

These defines are used backwards... the function in libiptc.c is called
ENTRY_ITERATE() which then gets expanded to IPT_ENTRY_ITERATE() when it's
compiled for ipv4. This is because most of the libiptc code is shared
between ipv4 and ipv6 and we don't want massive code duplication when
it's mostly just the names of the structures that change.
(look at ENTRY_ITERATE in libip6tc.c and you'll see it's similar)

You want to look at ENTRY_ITERATE() in libiptc.c

/Martin

Re: IPT_ENTRY_ITERATE

[Swapnil Nagle]

>>grep shows  only one match :
>>
>>libiptc/libip4tc.c:#define ENTRY_ITERATE    IPT_ENTRY_ITERATE
>>    
>>
>
>These defines are used backwards... the function in libiptc.c is called
>ENTRY_ITERATE() which then gets expanded to IPT_ENTRY_ITERATE() when it's
>compiled for ipv4. This is because most of the libiptc code is shared
>
>  
>
...

>You want to look at ENTRY_ITERATE() in libiptc.c
>
>  
>
I couldn't find the definition for either ENTRY_ITERATE() or 
IPT_ENTRY_ITERATE() in libiptc.c.
Basically I want to see the code that iterates through the entries and 
calls the function specified through ENTRY_ITERATE().

Regards,
Swapnil.

Re: IPT_ENTRY_ITERATE

[KOVACS Krisztian]

  Hi,

2004-09-23, cs keltezéssel 10:07-kor Swapnil Nagle ezt írta:
> I couldn't find the definition for either ENTRY_ITERATE() or 
> IPT_ENTRY_ITERATE() in libiptc.c.
> Basically I want to see the code that iterates through the entries and 
> calls the function specified through ENTRY_ITERATE().

  Use LXR!

  http://lxr.linux.no/ident?v=2.6.8.1&i=IPT_ENTRY_ITERATE

-- 
 Regards,
   Krisztian KOVACS

Re: IPT_ENTRY_ITERATE

[Martin Josefsson]

On Thu, 23 Sep 2004, KOVACS Krisztian wrote:

>
>   Hi,
>
> 2004-09-23, cs keltezéssel 10:07-kor Swapnil Nagle ezt írta:
> > I couldn't find the definition for either ENTRY_ITERATE() or
> > IPT_ENTRY_ITERATE() in libiptc.c.
> > Basically I want to see the code that iterates through the entries and
> > calls the function specified through ENTRY_ITERATE().
>
>   Use LXR!
>
>   http://lxr.linux.no/ident?v=2.6.8.1&i=IPT_ENTRY_ITERATE

Ah yes. Thats what you get for trying to answer questions before the first
cup of coffee.

/Martin

Re: IPT_ENTRY_ITERATE

[Swapnil Nagle]

>>I couldn't find the definition for either ENTRY_ITERATE() or 
>>IPT_ENTRY_ITERATE() in libiptc.c.
>>    
>>
...

>  Use LXR!
>
>  http://lxr.linux.no/ident?v=2.6.8.1&i=IPT_ENTRY_ITERATE
>
>  
>
Thanks :) I had no idea that it was in the iptables kernel headers & not 
in the userspace program !

-- Swapnil

Re: IPT_ENTRY_ITERATE

[Harald Welte]

[-- Attachment #1: Type: text/plain, Size: 768 bytes --]

On Thu, Sep 23, 2004 at 02:03:33PM +0530, Swapnil Nagle wrote:

> Thanks :) I had no idea that it was in the iptables kernel headers & not 
> in the userspace program !

Both have to iterate the ruleset, so it is logical to have them only in
one place.  An since you can compile the kernel without iptables
userspace (but not vice versa) it becomes completely obvious ;)

> -- Swapnil

-- 
- Harald Welte <laforge@netfilter.org>             http://www.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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]