RE: Vrrp Implementation issue over LinuxIp

Hope the list doesn't mind this Linux specific conversation....

>    We are planning to run VRRP over a Logical Interface 
> created in Linux
> IP.(similar to eth0)

I'm not sure what this means. I run VRRP over an ethernet
interface. Is what you're doing significantly different?
 
>    How we can I prevent that Linux Interface from sending arp 
> reply when it is in Backup State?

Well, I think you're asking the wrong question. The real
question is how to you make the interface send an ARP reply
when it's supposed to. I always find it fascinating that
there's really no good reason for the non-owner system to
know the VR IP address at all except for ARP, so you're
best off if you can avoid attaching it to an interface
to begin with instead of attaching it and trying to
suppress the results.

I manipulate the ARP table directly, although in
the 2.4 kernel I had to extend to kernel's ARP code to
allow setting an ARP entry with a specific MAC address.
(I don't know if 2.6 supports that out of the box.)

>   Also,How can we to associate various virtual MacAddresses 
> to that Linux Interface?

You just add them as if they were multicast MAC addresses
you want your hardware to accept for delivery
Remember, the kernel should always use the natural MAC
address for all packets it sends. Only the VRRP packets
that your VRRP app generates should have the VR MAC
address as the source.

-don

_______________________________________________
vrrp mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/vrrp