|
2.4.26pre and 2.6.4pre will come with 2 new device flags for tuning the ARP
stack: arp_announce and arp_ignore. All IPVS like setups can use
arp_announce=2 and arp_ignore=1/2/3 to solve the "ARP problem" with DR/TUN
setups. These flags are going to replace the "hidden" functionality which
does not work well for directors when they are changing their role between
master/slave for a particular VIP. The risk is that other hosts can probe
for VIP using unicast packets which the hidden flag always replies. I'll
continue to support the hidden flag for 2.4 and 2.6 to help existing setups
but switching to the new device flags (or other solutions) is recommended.
-----Original Message-----
From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Peter Johnson
Sent: Thursday, 18 November 2004 2:24 PM
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: IPVS on 2.6 Kernel
Hi All,
I am very new to LVS but not foreign to it's concepts or goals. I am trying
to implement LVS across two real servers with each also being a director
(active / passive). Most of the documentation and HOWTOs that I have found
are relating to 2.0.x, 2.2.x and 2.4.x kernels, I haven't been able to find
much about 2.6.x kernels.
The difference? e.g. I have no "hidden" interface attribute in sysctl
The setup:-
OS: Debian running 2.6.9
Addresses: VIP and RIP on same LAN segment.
Real 1 - x.x.x.1
Real 2 - x.x.x.2
Virtual - x.x.x.3
Method: Ideally DR
Could someone possibly point me in the direction of this information or
provide me with some guidance?
Could someone also possibly explain the processing order of packets through
the kernel? e.g. does it follow network -> interface -> kernel -> iptables
-> routing -> application (e.g. ipvs)
Thanks,
PJ
|
