|
A few suggestions:
There is a front end to LVS configuration in RedHat called Piranha. You can
use that to create the necessary /etc/lvs.cf
configuration file. It also includes a set of utilities called pulse and nanny
which will automatically issue the
necessary ipvsadm commands. This way you don't have to do that manually each
time. If you go to the RedHat support site and
search for Piranha you will find a link to their Piranha HOWTO guide.
In RedHat, there is a script /etc/rc.d/init.d/pulse which needs to be run each
time to startup the pulse + nanny daemons. In
order to do this you have to create the necessary links in rc3.d, rc4.d, rc5.d
to startup/shutdown the pulse daemon.
In order to avoid having to do this command each time you boot:
echo "1" > /proc/sys/net/ipv4/ip_forward
You can change this parameter in /etc/sysconfig/network:
FORWARD_IPV$="yes"
The `ipchains` command can be placed at the end of /etc/rc.d/rc.local to be
automatically issued on each boot. While on the
topic of the ipchains command, the one thing that threw me off was that the
examples in the HOWTO's look something
like what you cite:
/sbin/ipchains -A forward -j MASQ -s 172.1.0.0/24 -d 0.0.0.0/0
What isn't explicitly stated anywhere is that if your public network is not
eth0 (corresponding to -d 0.0.0.0/0) then you need
to designate the public interface in the -d parameter. For example, on my
system I had to specify '-d 192.161.1.0'
in order to get things working. Another useful `ipchains` tip is to include the
-l flag in the command line. This causes
logging info to /var/log/messages which is useful for diagnosing problems. You
should disable that flag once you're
operational.
Finally, I also found it necessary to include the following kernel option under
network options:
IP: alias
--
Tim Burke Tel. 978-446-9166 x232
Mission Critical Linux, LLC burke@xxxxxxxxxxx
http://www.missioncriticallinux.com
|
