|
Hi Todd,
there should be no problem to incremente NOARP_MAX_IP,
all memory is allocated statically.
The RIP in the 'add' command of noarpctl is
used to suppress the selection of the VIP as the sender
IP address in arp requests.
If not suppressed the back-end host request updates all arp
cache entries on the local net for the VIP with the mac of
the back-end host.
A way to generate a request of this type is, from a real server:
#> nc -s $VIP somehost 80
Ciao
Maurizio
On Thu, Feb 03, 2005 at 07:19:23PM -0800, Todd Lyons wrote:
> Todd Lyons wanted us to know:
>
> >#define NOARP_MAX_IP (16)
> >Is it going to create problems to pick this number up to 32 or 64? I
>
> Not that I'm impatient :-), but I tried it and it's working (actually,
> it's not crashing, which could be the same thing) :-)
>
> I have a question about the man page description though:
> NOARPCTL COMMANDS
> add Adds a new Virtual IP to the list. Requires two
> arguments: the VIP is the address to hide, the Real
> IP (RIP) is a real address of this host to use when
> ARP query are made that would use VIP.
>
> I must be misunderstanding something very basic. I thought you didn't
> want real servers to arp at all for VIPs, no matter what interface the
> arp comes in on and no matter what interface is defined with the
> matching address. The only acceptable arp answer is for the RIP
> (implying local traffic or traffic that is not desired to be load
> balanced). But the above man page contradicts my ideas. So I'm a bit
> confused as to how exactly noarp is working.
> --
> Regards... Todd
> They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety. --Benjamin Franklin
> Linux kernel 2.6.8.1-12mdkenterprise 4 users, load average: 0.01, 0.01,
> 0.00
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
|
