ipchains as kernel module

[shaggy1112]

Hi,

I am loading ipchains using modprobe as a module of the kernel.
What I want to know is what do I need to do so that this mod will be loaded on startup? I am not sure of the syntax of modules.conf, and haven't been able to find it.

Thanks

[ph34r]

You can put it at the start of the script you use to generate your chains... and then perhaps reference that script from rc.local...

[shaggy1112]

ok i'll just put it in local....i just didn't know if i *should* do it in modules.conf.

thanks

[serz]

What distro?

[shaggy1112]

rh 8.0

[serz]

Yep, that's the file where you to edit, /etc/modules.conf.

[shaggy1112]

yeah...but i'm not sure of the syntax. based on what is in the file, i can't derive what should be there from 'modprobe ipchains'

[tommyj27]

"modprobe ipchains" should be sufficient,

[bwkaz]

I don't know for sure, but I wouldn't try to put it in modules.conf. That file is used for getting dependency information -- when the kernel needs some service that it can't currently handle, it (...well, modprobe, actually) checks through that file to try to find a module that can give the kernel that service.

In this case, I don't know of any service that the kernel would be automatically looking for, that you would be able to alias to ipchains.

I do the same thing on my systems as some others have said -- I have a separate rc.firewall script that loads all the modules and sets up the firewall rules for me, and then I just call that script from rc.local (well, more or less...).

[shaggy1112]

thanks for the response.

i originally thought of loading it in the script that starts the chains, but if for some reason I had to start and stop the firewall (testing, adding rules etc.), I didn't want to have to have it loading and unloading the module. I have put it in rc.local so that it just loads with the os, and so that I don't have to worry about it in the script.

thanks.