Skip to contentSkip to conversation

ip_conntrack_ftp as a module or built-in?

DISCUSSION [email protected] 3 participants 4 messages Nov 22, 2005

lore
Share & tools
lore
#0 lore raw

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.

Signature · 2 lines
Niccolo Rigacci
Firenze - Italy
#1 lore raw
Quoted 5 lines · On Tue, November 22, 2005 11:47, [email protected] wrote:

Hello,

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

Quoted 7 lines

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

#2 lore raw
Quoted 3 lines

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

Signature · 2 lines
Niccolo Rigacci
Firenze - Italy
#3 lore raw
Quoted 7 lines · On Tuesday 2005-November-22 05:33, [email protected] wrote:
Quoted 3 lines

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.

Quoted 2 lines

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

Signature · 2 lines
    mail to this address is discarded unless "/dev/rob0"
    or "not-spam" is in Subject: header