All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Lim <vincent.lim@nestac.com>
To: bobo <boboaq@163.com>
Cc: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>,
	"bobowd@sohu.com" <bobowd@sohu.com>
Subject: Re: How to  load these modules?
Date: Fri, 20 Dec 2002 15:32:49 +0800	[thread overview]
Message-ID: <3E02C7A1.1446C5B5@nestac.com> (raw)
In-Reply-To: 20021220032315.3B1701D110BCC@sm181.163.com

bobo wrote:
> 
>      Hello  all:
> 
>            While I am studying iptables,I read such contents from a tutorial as bellow:
> 
>   "the rc.firewall.txt neede the following options to be compiled to kernel or as modules..
> 
>   .CONFIG_PACKET
>   .CONFIG_NETFILTER
>   .CONFIG_IP_NF_CONNTRACK
> ..........
> 
>    I find some moudles of REDHAT 7.2 in /lib/modules/2.4.7-10/kernel/net/ipv4/netfilter,
>  but the modules'name are not the same as the above.  There are about 20 modules in the directory.
> 
>   Why?
> 
>   How could I do?   How could I get these modules?

I did a check on /usr/src/linux/net/ipv4/netfilter/Makefile and found
the following line:
obj-$(CONFIG_IP_NF_CONNTRACK) += ip_conntrack.o

This (I think) means that if "CONFIG...." is selected, then the module
that corresponds to this selection is ip_conntrack.o

then in /usr/src/linux/net/Makefile

subdir-$(CONFIG_NETFILTER)  += ipv4/netfilter

I think this meant that all modules in ipv4/netfilter would be needed
for that selection.

-- 
Vincent Lim
Software Engineer
NESTAC Solution Sdn Bhd
vincent.lim@nestac.com | +(6012) 659-6609


  reply	other threads:[~2002-12-20  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20  3:27 How to load these modules? bobo
2002-12-20  7:32 ` Vincent Lim [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-20  3:27 bobo
2002-12-20  3:22 bobo
2002-12-20  3:10 bobo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E02C7A1.1446C5B5@nestac.com \
    --to=vincent.lim@nestac.com \
    --cc=boboaq@163.com \
    --cc=bobowd@sohu.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.