current kernel - 2.4.29
i compiled new kernel - 2.6.7 and installed modules ...-> booted PC using new image...
after that i returned to old one...
are that modules which 2.6.7 kernel has installed loaded by 2.4.29 ??
and did that install changed previous config??
i noticed that running "lsmod" prints different modules loaded by iptables...
here is printout:
Module Size Used by Not tainted
ipt_REJECT 3128 4 (autoclean)
ipt_LOG 3448 10 (autoclean)
ipt_state 536 11 (autoclean)
ipt_pkttype 504 4 (autoclean)
ipt_owner 1368 0 (autoclean)
ipt_recent 7908 0 (autoclean)
ipt_multiport 696 4 (autoclean)
ipt_conntrack 1048 3 (autoclean)
iptable_mangle 2104 1 (autoclean)
ip_nat_irc 2064 0 (unused)
ip_nat_tftp 1712 0 (unused)
ip_nat_ftp 2544 0 (unused)
iptable_nat 16974 3 [ip_nat_irc ip_nat_tftp ip_nat_ftp]
ip_conntrack_irc 2768 1
ip_conntrack_tftp 1616 1
ip_conntrack_ftp 3632 1
ip_conntrack 18440 3 [ipt_state ipt_conntrack ip_nat_irc ip_nat_tft p ip_nat_ftp iptable_nat ip_conntrack_irc ip_conntrack_tftp ip_conntrack_ftp]
iptable_filter 1676 1
ip_tables 12000 13 [ipt_REJECT ipt_LOG ipt_state ipt_pkttype ipt_ owner ipt_recent ipt_multiport ipt_conntrack iptable_mangle iptable_nat iptable_ filter]

tnx

To my knowledge, each kernel has its own set of compiled modules. A module compiled for 2.4.29 cannot be loaded by a 2.6.7 kernel and vice versa. For this reason, you will need each kernel with the appropriate modules compiled.

On my machine, for example, the kernel modules are stored under "/lib/modules/2.6.14.6". When I initially installed Debian, it set me up with a 2.6.8.11 kernel, for which the modules exist in "/lib/modules/2.6.8-11-amd64-k8". When I made my own 2.6.14.6 kernel, I had to compile all of the modules I wanted again, because the ones in 2.6.8-11-amd64-k8 are useless to the 2.6.14.6 kernel.

Does that answer your question? I'm not entirely sure I have.

yes i get it, tnx