On Nov 2, 2005, at 3:35 PM, Yu Safin wrote:
Agree, I apologize for the poor use of words. However, I am still confused as to the explanation about using a routing daemon. can you be more specific as to what this is all about. We have our solution fully implemented and we have no such daemon.
....
Right on. We now have a solution for getting to our VIPA dummy address from the network. However, we have done nothing yet about the return IP address from our network services. Most of them would use the first eth. Source-VIPA and "ip route" will get us to the complete solution.
I want to know how the solution for getting to the dummy address from the network works in the absence of a routing daemon. Basically, let's say you've got physical interfaces A and B, and dummy D. Initially D--which is the IP address everyone should use-- gets to/from the network via A. Then A dies. How does the network know to use B to get to D, and how does the host know to get to the network via B and not A, in the absence of a routing daemon? I can see using "ip route" to create a failover on the host (or indeed equal cost multipathing across A and B when both interfaces are up (iproute2 is SOOOOO cool!))--but how does the network know which way to get back to D? This is where you'd traditionally use OSPF and send out an update when A fell over saying "get to D via B instead." Adam ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
