mirror of https://github.com/tLDP/LDP
Editing of new "Linux-Networking" guide. This copy is not to be distributed. Its just a draft to give people an idea as to the format of the new document and a backup just in case my laptop dies.
Binh.
This commit is contained in:
binh
parent
bb17c58207
commit
5d58c8ff1a
|
|
@ -1,161 +1,165 @@
|
|||
<sect1 id="IP-Aliasing">
|
||||
|
||||
Setting up IP Aliasing on A Linux Machine Mini-HOWTO
|
||||
Harish Pillay
|
||||
h.pillay@ieee.org
|
||||
Joy Yokley - Converted document from HTML to DocBook v4.1 (SGML)
|
||||
2001-01-23
|
||||
Revision History
|
||||
Revision 1.2 2001-01-26 Revised by: JEY
|
||||
Revision 1.1 2001-01-24 Revised by: JEY
|
||||
Revision 1.0 1997-01-13 Revised by: HP
|
||||
|
||||
4. Acknowledgements
|
||||
|
||||
Thanks to all those who have done this great work on Linux and IP Aliasing.
|
||||
And especially to Juan Jose Ciarlante for clarifying my questions.
|
||||
|
||||
Kudos to the ace programmers!
|
||||
|
||||
If you find this document useful or have suggestions on improvements, email
|
||||
me at <[mailto:h.pillay@ieee.org] h.pillay@ieee.org>.
|
||||
|
||||
Enjoy.
|
||||
|
||||
For additional information on networking, you may want to consult the [http:/
|
||||
/www.linuxdoc.org/HOWTO/Networking-Overview-HOWTO.html] The Linux Networking
|
||||
Overview HOWTO.
|
||||
|
||||
8.5. IP aliasing
|
||||
|
||||
This feature of the Linux kernel provides the possibility of setting
|
||||
multiple network addresses on the same low-level network device driver
|
||||
(e.g two IP addresses in one Ethernet card). It is typically used for
|
||||
services that act differently based on the address they listen on
|
||||
(e.g. "multihosting" or "virtual domains" or "virtual hosting
|
||||
services".
|
||||
|
||||
Related HOWTO:
|
||||
|
||||
· IP Aliasing HOWTO <http://metalab.unc.edu/mdw/HOWTO/mini/IP-
|
||||
Alias.html>
|
||||
|
||||
6.5. IP Aliasing
|
||||
|
||||
There are some applications where being able to configure multiple IP
|
||||
addresses to a single network device is useful. Internet Service
|
||||
Providers often use this facility to provide a `customized' to their
|
||||
World Wide Web and ftp offerings for their customers. You can refer to
|
||||
the ``IP-Alias mini-HOWTO'' for more information than you find here.
|
||||
|
||||
Kernel Compile Options:
|
||||
|
||||
|
||||
Networking options --->
|
||||
....
|
||||
[*] Network aliasing
|
||||
....
|
||||
<*> IP: aliasing support
|
||||
|
||||
|
||||
|
||||
After compiling and installing your kernel with IP_Alias support
|
||||
configuration is very simple. The aliases are added to virtual network
|
||||
devices associated with the actual network device. A simple naming
|
||||
convention applies to these devices being <devname>:<virtual dev num>,
|
||||
e.g. eth0:0, ppp0:10 etc. Note that the the ifname:number device can
|
||||
only be configured after the main interface has been set up.
|
||||
|
||||
For example, assume you have an ethernet network that supports two
|
||||
different IP subnetworks simultaneously and you wish your machine to
|
||||
have direct access to both, you could use something like:
|
||||
|
||||
|
||||
|
||||
root# ifconfig eth0 192.168.1.1 netmask 255.255.255.0 up
|
||||
root# route add -net 192.168.1.0 netmask 255.255.255.0 eth0
|
||||
|
||||
root# ifconfig eth0:0 192.168.10.1 netmask 255.255.255.0 up
|
||||
root# route add -net 192.168.10.0 netmask 255.255.255.0 eth0:0
|
||||
|
||||
|
||||
|
||||
To delete an alias you simply add a `-' to the end of its name and
|
||||
refer to it and is as simple as:
|
||||
|
||||
|
||||
|
||||
root# ifconfig eth0:0- 0
|
||||
|
||||
|
||||
|
||||
All routes associated with that alias will also be deleted
|
||||
automatically.
|
||||
|
||||
<title>IP-Aliasing</title>
|
||||
|
||||
<para>
|
||||
This is a cookbook recipe on how to set up and run IP aliasing on a Linux box
|
||||
and how to set up the machine to receive e-mail on the aliased IP addresses.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This feature of the Linux kernel provides the possibility of setting
|
||||
multiple network addresses on the same low-level network device driver
|
||||
(e.g two IP addresses in one Ethernet card). It is typically used for
|
||||
services that act differently based on the address they listen on
|
||||
(e.g. "multihosting" or "virtual domains" or "virtual hosting
|
||||
services".
|
||||
</para>
|
||||
|
||||
<para>
|
||||
There are some applications where being able to configure multiple IP
|
||||
addresses to a single network device is useful. Internet Service
|
||||
Providers often use this facility to provide a `customized' to their
|
||||
World Wide Web and ftp offerings for their customers. You can refer to
|
||||
the ``IP-Alias mini-HOWTO'' for more information than you find here.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Quickstart:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
After compiling and installing your kernel with IP_Alias support
|
||||
configuration is very simple. The aliases are added to virtual network
|
||||
devices associated with the actual network device. A simple naming
|
||||
convention applies to these devices being <devname>:<virtual dev num>,
|
||||
e.g. eth0:0, ppp0:10 etc. Note that the the ifname:number device can
|
||||
only be configured after the main interface has been set up.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
For example, assume you have an ethernet network that supports two
|
||||
different IP subnetworks simultaneously and you wish your machine to
|
||||
have direct access to both, you could use something like:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
root# ifconfig eth0 192.168.1.1 netmask 255.255.255.0 up
|
||||
root# route add -net 192.168.1.0 netmask 255.255.255.0 eth0
|
||||
root# ifconfig eth0:0 192.168.10.1 netmask 255.255.255.0 up
|
||||
root# route add -net 192.168.10.0 netmask 255.255.255.0 eth0:0
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
-----------------------------------------------------------------------------
|
||||
<para>
|
||||
1. My Setup
|
||||
</para>
|
||||
|
||||
<para>
|
||||
* IP Alias is standard in kernels 2.0.x and 2.2.x, and available as a
|
||||
compile-time option in 2.4.x (IP Alias has been deprecated in 2.4.x and
|
||||
replaced by a more powerful firewalling mechanism.)
|
||||
|
||||
* IP Alias compiled as a loadable module. You would have indicated in the
|
||||
"make config" command to make your kernel, that you want the IP Masq to
|
||||
be compiled as a (M)odule. Check the Modules HOW-TO (if that exists) or
|
||||
check the info in /usr/src/linux/Documentation/modules.txt.
|
||||
|
||||
* I have to support 2 additional IPs over and above the IP already
|
||||
allocated to me.
|
||||
|
||||
* A D-Link DE620 pocket adapter (not important, works with any Linux
|
||||
supported network adapter).
|
||||
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
Kernel Compile Options:
|
||||
|
||||
Networking options --->
|
||||
....
|
||||
[*] Network aliasing
|
||||
....
|
||||
<*> IP: aliasing support
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
|
||||
-----------------------------------------------------------------------------
|
||||
2. Commands
|
||||
|
||||
1. Load the IP Alias module (you can skip this step if you compiled the
|
||||
module into the kernel):
|
||||
/sbin/insmod /lib/modules/`uname -r`/ipv4/ip_alias.o
|
||||
|
||||
2. Setup the loopback, eth0, and all the IP addresses beginning with the
|
||||
main IP address for the eth0 interface:
|
||||
<para>
|
||||
2. Commands
|
||||
</para>
|
||||
|
||||
<para>
|
||||
1. Load the IP Alias module (you can skip this step if you compiled the
|
||||
module into the kernel):
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
/sbin/insmod /lib/modules/`uname -r`/ipv4/ip_alias.o
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
2. Setup the loopback, eth0, and all the IP addresses beginning with the
|
||||
main IP address for the eth0 interface:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
/sbin/ifconfig lo 127.0.0.1
|
||||
/sbin/ifconfig eth0 up
|
||||
/sbin/ifconfig eth0 172.16.3.1
|
||||
/sbin/ifconfig eth0:0 172.16.3.10
|
||||
/sbin/ifconfig eth0:1 172.16.3.100
|
||||
|
||||
172.16.3.1 is the main IP address, while .10 and .100 are the aliases.
|
||||
The magic is the eth0:x where x=0,1,2,...n for the different IP
|
||||
addresses. The main IP address does not need to be aliased.
|
||||
|
||||
3. Setup the routes. First route the loopback, then the net, and finally,
|
||||
the various IP addresses starting with the default (originally allocated)
|
||||
one:
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
172.16.3.1 is the main IP address, while .10 and .100 are the aliases.
|
||||
The magic is the eth0:x where x=0,1,2,...n for the different IP
|
||||
addresses. The main IP address does not need to be aliased.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
3. Setup the routes. First route the loopback, then the net, and finally,
|
||||
the various IP addresses starting with the default (originally allocated)
|
||||
one:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
/sbin/route add -net 127.0.0.0
|
||||
/sbin/route add -net 172.16.3.0 dev eth0
|
||||
/sbin/route add -host 172.16.3.1 dev eth0
|
||||
/sbin/route add -host 172.16.3.10 dev eth0:0
|
||||
/sbin/route add -host 172.16.3.100 dev eth0:1
|
||||
/sbin/route add default gw 172.16.3.200
|
||||
|
||||
That's it.
|
||||
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
That's it.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In the example IP address above, I am using the Private IP addresses (RFC
|
||||
1918) for illustrative purposes. Substitute them with your own official or
|
||||
private IP addresses.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The example shows only 3 IP addresses. The max is defined to be 256 in /usr/
|
||||
include/linux/net_alias.h. 256 IP addresses on ONE card is a lot :-)!
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Here's what my /sbin/ifconfig looks like:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
lo Link encap:Local Loopback
|
||||
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
|
||||
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
|
||||
|
|
@ -180,29 +184,58 @@ eth0:1 Link encap:10Mbps Ethernet HWaddr 00:8E:B8:83:19:20
|
|||
UP BROADCAST RUNNING MTU:1500 Metric:1
|
||||
RX packets:1 errors:0 dropped:0 overruns:0
|
||||
TX packets:0 errors:0 dropped:0 overruns:0
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
And /proc/net/aliases:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
device family address
|
||||
eth0:0 2 172.16.3.10
|
||||
eth0:1 2 172.16.3.100
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
And /proc/net/alias_types:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
type name n_attach
|
||||
2 ip 2
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Of course, the stuff in /proc/net was created by the ifconfig command and not
|
||||
by hand!
|
||||
</para>
|
||||
-----------------------------------------------------------------------------
|
||||
|
||||
<para>
|
||||
3. Troubleshooting: Questions and Answers
|
||||
</para>
|
||||
|
||||
<para>
|
||||
3.1. Question: How can I keep the settings through a reboot?
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Answer: Whether you are using BSD-style or SysV-style (Redhat?? for example)
|
||||
init, you can always include it in /etc/rc.d/rc.local. Here's what I have on
|
||||
my SysV init system (Redhat?? 3.0.3 and 4.0):
|
||||
</para>
|
||||
|
||||
<para>
|
||||
My /etc/rc.d/rc.local: (edited to show the relevant portions)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
#setting up IP alias interfaces
|
||||
echo "Setting 172.16.3.1, 172.16.3.10, 172.16.3.100 IP Aliases ..."
|
||||
/sbin/ifconfig lo 127.0.0.1
|
||||
|
|
@ -219,37 +252,54 @@ echo "Setting IP routes ..."
|
|||
/sbin/route add -host 172.16.3.100 eth0:1
|
||||
/sbin/route add default gw 172.16.3.200
|
||||
#
|
||||
</screen>
|
||||
</para>
|
||||
-----------------------------------------------------------------------------
|
||||
|
||||
<para>
|
||||
3.2. Question: How do I set up the IP aliased machine to receive e-mail on
|
||||
the various aliased IP addresses (on a machine using sendmail)?
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Answer: Create (if it doesn't already exist) a file called, /etc/
|
||||
mynames.cw,for example. The file does not have to be this exact name nor in
|
||||
the /etc directory.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In that file, place the official domain names of the aliased IP addresses. If
|
||||
these aliased IP addresses do not have a domain name, then you can place the
|
||||
IP address itself.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The /etc/mynames.cw might look like this:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
# /etc/mynames.cw - include all aliases for your machine here; # is a comment
|
||||
domain.one.net
|
||||
domain.two.com
|
||||
domain.three.org
|
||||
4.5.6.7
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In your sendmail.cf file, where it defines a file class macro Fw, add the
|
||||
following:
|
||||
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
##################
|
||||
# local info #
|
||||
##################
|
||||
|
||||
|
||||
# file containing names of hosts for which we receive email
|
||||
Fw/etc/mynames.cw
|
||||
|
||||
|
||||
That should do it. Test out the new setting by invoking sendmail in test
|
||||
mode. The following is an example:
|
||||
|
|
@ -289,11 +339,39 @@ rewrite: ruleset 0 returns: $# smtp $@ 4 . 5 . 6 . 8 $: me < @ 4 . 5 . 6 . 8 >
|
|||
rewrite: ruleset 97 returns: $# smtp $@ 4 . 5 . 6 . 8 $: me < @ 4 . 5 . 6 . 8 >
|
||||
rewrite: ruleset 0 returns: $# smtp $@ 4 . 5 . 6 . 8 $: me < @ 4 . 5 . 6 . 8 >
|
||||
>
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Notice when I tested me@4.5.6.7, it delivered the mail to the local machine,
|
||||
while me@4.5.6.8 was handed off to the smtp mailer. That is the correct
|
||||
response.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
3.3. Question: How do I delete an alias?
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Answer: To delete an alias you simply add a `-' to the end of its name and
|
||||
refer to it and is as simple as:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
root# ifconfig eth0:0- 0
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
All routes associated with that alias will also be deleted
|
||||
automatically.
|
||||
</para>
|
||||
|
||||
|
||||
|
||||
<para>
|
||||
You are all set now.
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
|
|
|
|||
|
|
@ -941,5 +941,28 @@ Credits for fixes and hints are listed here, will grow sure in the future
|
|||
David S. Lawyer <mailto:dave@lafn.org>
|
||||
v1.36, August 2004
|
||||
|
||||
|
||||
Setting up IP Aliasing on A Linux Machine Mini-HOWTO
|
||||
Harish Pillay
|
||||
h.pillay@ieee.org
|
||||
Joy Yokley - Converted document from HTML to DocBook v4.1 (SGML)
|
||||
2001-01-23
|
||||
Revision History
|
||||
Revision 1.2 2001-01-26 Revised by: JEY
|
||||
Revision 1.1 2001-01-24 Revised by: JEY
|
||||
Revision 1.0 1997-01-13 Revised by: HP
|
||||
4. Acknowledgements
|
||||
Thanks to all those who have done this great work on Linux and IP Aliasing.
|
||||
And especially to Juan Jose Ciarlante for clarifying my questions.
|
||||
Kudos to the ace programmers!
|
||||
If you find this document useful or have suggestions on improvements, email
|
||||
me at <[mailto:h.pillay@ieee.org] h.pillay@ieee.org>.
|
||||
Enjoy.
|
||||
For additional information on networking, you may want to consult the [http:/
|
||||
/www.linuxdoc.org/HOWTO/Networking-Overview-HOWTO.html] The Linux Networking
|
||||
Overview HOWTO.
|
||||
Related HOWTO:
|
||||
· IP Aliasing HOWTO <http://metalab.unc.edu/mdw/HOWTO/mini/IP-
|
||||
Alias.html>
|
||||
|
||||
|
||||
</appendix>
|
||||
|
|
|
|||
Loading…
Reference in New Issue