libnetfilter_conntrack and port of router

libnetfilter_conntrack and port of router

[Tomasz Próchniak]

Hi

First sorry about my English.

I have a important (to me) question.

I have 2.6.14-5 kernel and libnetfilter_conntrack-0.0.28/ and 
libnfnetlink-0.0.13/

i do not know how to get info about nat (port and ip, witch it will be seen in 
net)

example:  
10.0.0.10:8888 ---------->10.0.0.1||88.88.88.88:3333--------->1111:22.22.22.22
my comp after nat            my router                         comp in net   


im intrasted about 88.88.88.88 and port 3333

i have struct 
struct nfct_conntrack {
        struct nfct_tuple tuple[NFCT_DIR_MAX];

        u_int32_t       timeout;
        u_int32_t       mark;
        u_int32_t       status;
        u_int32_t       use;
        u_int32_t       id;

        union nfct_protoinfo protoinfo;
        struct nfct_counters counters[NFCT_DIR_MAX];
        struct nfct_nat nat;       //does this info should be in this struct??
};

but this struct 
struct nfct_nat {
        u_int32_t min_ip, max_ip;
        union nfct_l4 l4min, l4max;
};

if filled with 0 :(

pleas help me 

thanks Kornik




-- 
Mylić się jest rzeczą ludzką,
ale żeby naprawdę coś spaprać
 potrzeba komputera.

Edward Morgan Forster

Re: libnetfilter_conntrack and port of router

[Harald Welte]

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

On Mon, Jan 09, 2006 at 12:30:55PM +0100, Tomasz Próchniak wrote:
> Hi
> 
> First sorry about my English.
> 
> I have a important (to me) question.
> 
> I have 2.6.14-5 kernel and libnetfilter_conntrack-0.0.28/ and 
> libnfnetlink-0.0.13/
> 
> i do not know how to get info about nat (port and ip, witch it will be seen in 
> net)

you have to look at the original and the reply tupl.

> struct nfct_conntrack {
>         struct nfct_tuple tuple[NFCT_DIR_MAX];

everything is in those two struct nfct_tuple.

-- 
- Harald Welte <laforge@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

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