On 03/20/2010 06:13 AM, Eric S. Johnson wrote: >> Seems to me that if we put a second IP on the interface, then we >> can let the OS deal with arp and kill the arpd logic entirely. > > Yeah, I thought the same thing. In fact it looks like the pseudo arp > deamon wont "start up" for IP's assigned to the interface, due to > the Vrrp::check_ownership > >>> Would a correct solution be to have xorp set the virtual IP >>> as a secondary IP on that VIF? If so, what would be the correct >>> way to do this.. IfTreeVif::add_addr method? >> >> Sounds good to me. I fixed the bug in xorp.ct that caused vrrp >> to crash early...now I'm seeing similar activity w/regard to >> the MAC addr being set but no IP visible. >> >> I'll poke at the add_addr logic and see what I can get >> to happen... > > Ive been on vacation this last week, but started this before > I left. Below are the diff I have. Basicly I copied the logic > for adding the mac, and got as far as vrrp_target where I think > a XRL needs to be sent, but I hadn't figured out how/what yet,
I think I know how to make XRL & FEA do it's thing...will have a patch this evening if all goes well. The work I did yesterday looks very close to your patch, so hopefully we're on the right track. Thanks, Ben -- Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ Xorp-hackers mailing list [email protected] http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
