Messages in this thread |  | | Date | Wed, 26 Sep 2001 12:09:59 -0700 | From | J Sloan <> |
| |
Steve Pirk wrote:
> This much I have found so far... > In /usr/src/linux-2.2.16/.config : > CONFIG_IP_MASQUERADE=y > CONFIG_IP_MASQUERADE_ICMP=y > CONFIG_IP_MASQUERADE_MOD=y > CONFIG_IP_MASQUERADE_IPAUTOFW=m > CONFIG_IP_MASQUERADE_IPPORTFW=m > CONFIG_IP_MASQUERADE_MFW=m > > In /usr/src/linux-2.2.19/.config > no CONFIG_IP_MASQUERADE lines at all.... > > Would it be save to add them to a 2.2.19 or 2.4.10 .config file?
bad idea -
> > Is aliasing/masquerading enabled by default in kernel versions > above 2.2.19?
I think it's a default feature in 2.4.x since I don't see a config file option for it and it works fine on all my boxen -
Let's check the docs:
Ah, here it is - and it matches my experience -
/usr/src/linux/Documentation/networking/alias.txt: ----------------------------------------------------------------------------- IP-Aliasing: ============
IP-aliases are additional IP-adresses/masks hooked up to a base interface by adding a colon and a string when running ifconfig. This string is usually numeric, but this is not a must.
IP-Aliases are avail if CONFIG_INET (`standard' IPv4 networking) is configured in the kernel.
o Alias creation. Alias creation is done by 'magic' interface naming: eg. to create a 200.1.1.1 alias for eth0 ...
# ifconfig eth0:0 200.1.1.1 etc,etc.... ~~ -> request alias #0 creation (if not yet exists) for eth0
The corresponding route is also set up by this command. Please note: The route always points to the base interface.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |