ip_conntrack_ftp as a module or built-in?

ip_conntrack_ftp as a module or built-in?

[netfilter]

Hello,

sorry for this generic question, but I searched long, without any 
clue.

On my linux box I load the ip_conntrack_ftp module with some 
parameter (to let the HylaFAX daemon talk with the clients):

    insmod ip_conntrack_ftp ports=21,4559

Is there a way to pass that "ports" parameter to the kernel, if 
the feature is compiled into the kernel, instead of as a module?

May be this is a generic modprobe question...

Thank you anyway.

-- 
Niccolo Rigacci
Firenze - Italy

Re: ip_conntrack_ftp as a module or built-in?

[Rob Sterenborg]

On Tue, November 22, 2005 11:47, netfilter@rigacci.org wrote:
> Hello,
>
> sorry for this generic question, but I searched long, without any
> clue.
>
> On my linux box I load the ip_conntrack_ftp module with some
> parameter (to let the HylaFAX daemon talk with the clients):
>
>     insmod ip_conntrack_ftp ports=21,4559
>
> Is there a way to pass that "ports" parameter to the kernel, if
> the feature is compiled into the kernel, instead of as a module?

I'm not sure if passing that parameter to the kernel during boot time
will work (probably not).
Why would you do that anyway : why not use the module ?


Gr,
Rob

Re: ip_conntrack_ftp as a module or built-in?

[netfilter]

> I'm not sure if passing that parameter to the kernel during boot time
> will work (probably not).
> Why would you do that anyway : why not use the module ?

We are developing a network appliance and we are trying to keep a 
small static kernel, with only the required features, no KMOD, no 
discover, hotplug or whatever.

Infact this is a more generic question: a module that accepts 
some paramters can be built into the kernel and still receive all 
of them?

Thanks

-- 
Niccolo Rigacci
Firenze - Italy

Re: ip_conntrack_ftp as a module or built-in?

[/dev/rob0]

On Tuesday 2005-November-22 05:33, netfilter@rigacci.org wrote:
> > I'm not sure if passing that parameter to the kernel during boot
> > time will work (probably not).
> > Why would you do that anyway : why not use the module ?
>
> We are developing a network appliance and we are trying to keep a
> small static kernel, with only the required features, no KMOD, no
> discover, hotplug or whatever.

This is about the only scenario in which built-in netfilter drivers
make sense.

> Infact this is a more generic question: a module that accepts
> some paramters can be built into the kernel and still receive all

man 7 bootparam
[/usr/src/linux/]Documentation/kernel-parameters.txt
-- 
    mail to this address is discarded unless "/dev/rob0"
    or "not-spam" is in Subject: header