|
Hello,
On Fri, 29 Dec 2000, Florin Andrei wrote:
> --- Michael E Brown <michael_e_brown@xxxxxxxx> wrote:
> >
> > The other obvious tuning recommendation: Pick a stable 2.4 kernel and use
> > that. Any (untuned) 2.4 kernel will blow away 2.2 in a multiprocessor
> > configuration. If I remember correctly 2.4.0test 10-11 are pretty stable.
>
> Yes, but LVS for 2.4 is really stable for production?
It looks good. The only problem: you can't use the LVS box as
gateway for non-LVS connections in NAT mode. I.e. a working setup can be:
LVS box:
external addresses:
DIP=10.0.0.1
VIP=10.0.0.100
internal addresses:
192.168.0.1
ipvsadm -a -t 10.0.0.100:80 -r 192.168.0.2:80 -m
real server:
192.168.1.2 - network for non-LVS traffic
192.168.0.2 - network for LVS traffic
ip rule add prio 100 from 192.168.0.0/24 table 100
ip route add table 100 via 192.168.0.1 dev eth0 src 192.168.0.2
route add default gw 192.168.1.3
LVS box default gateway (192.168.1.3, masq box)
192.168.0.1 \ /
RS1 192.168.1.2
192.168.0.2
You have to use source routing and to split the traffic to
a LVS and non-LVS related. One day if/when LVS can coexist with
ip_conntrack/iptable_nat such tricks will not be needed.
> =====
> Florin Andrei
Regards
--
Julian Anastasov <ja@xxxxxx>
|
