/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
Bruno Melloni <[EMAIL PROTECTED]> wrote:
>
> Why do we call modprobe for the ip_masq_... modules in the rc.local
> script?
Because otherwise they would never be loaded.
> Masquerading seems to work even without the modprobe statements (at
> least in RedHat 6.0).
Yes, straight masq causes most protocols to work properly, but some
(such as port-mode ftp) will fail because they embed IP/port information
in the data stream, and masq's necessary mangling of that information
causes failures.
The kernel will auto-load modules that correspond to devices and
filesystems and such, because the kernel has been programmed to
recognize these references. But there is no code in the kernel that
will auto-load a protocol module when certain packets are noticed on the
network. So you must pre-load the modules in order for them to have any
effect.
--
[EMAIL PROTECTED] (Fuzzy Fox) || "Nothing takes the taste out of peanut
sometimes known as David DeSimone || butter quite like unrequited love."
http://www.dallas.net/~fox/ || -- Charlie Brown
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
