search for: ungagging

...ill be generated, but be transparently dropped. Likewise, if the primary process is on B or C. Let''s say you have an Apache process running on A and B. B is shadowing A on everything. It''s at the same point, has the same connections established, etc. Failover becomes merely "ungagging" B. How is this a LARTC problem? Uhhh... because this approach is seriously abusing the entire networking stack. We essentially have all three machines running with an identical MAC and IP address visible to the outside. The "distinct" address is purely internal. What this require...