----- Forwarded message from "Robert E. Seastrom" <[email protected]> -----
From: "Robert E. Seastrom" <[email protected]> Date: Fri, 30 Nov 2012 09:35:10 -0500 To: Henning Brauer <[email protected]> Cc: [email protected] Subject: Re: carping about CARP User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (berkeley-unix) Henning Brauer <[email protected]> writes: > * Robert E. Seastrom <[email protected]> [2012-11-30 13:46]: >> My problem is not with Theo nor with the IETF. My problem is with a >> crappy and credulous implementation. When an outage is caused by >> redundancy software that comes from an organization that prides itself >> on well-written code, the irony meter goes off the scale. > > vrrp and carp share the vhid space. you have to use unique vhids per > network segment, that's about it. > > the openbsd box was nice enough to tell you about the mac address > conflict, the other's didn't. pfSense is FreeBSD, but who's counting? The problem is magnified when ill-behaved software ends up in appliances. Good thing we were able to get a shell on the box. > if you looked at the carp boxes you had seen that carp had continued > to work just fine. the mac address (which is basically "fixed prefix + > vhid) conflict is your "outage". there's nothing we could do about > that. > > and re IANA, they made it clear they would not give us a proto number > no matter what; we didn't have a choice but to ignore that > industry-money-driven committee. Between choosing an Ethernet OUI which was assigned to IANA by IEEE (another "industry-money-driven committee") and choosing protocol 112 (odds of coincidence 1 in what, 120 or so at the time?), "ignore" is not the word I would have chosen here. -r ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org";>leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
