On 12/2/2012 5:28 PM, Adrian Farrel wrote:
Far be it from me to get involved in a private pissing match, but...
Owen wrote:
Perhaps we should ask IETF/IANA to allocate a group of protocol numbers
to "the wild west". A protocol-number equivalent of RFC-1918 or private ASNs.
You can use these fo
Far be it from me to get involved in a private pissing match, but...
Owen wrote:
> Perhaps we should ask IETF/IANA to allocate a group of protocol numbers
> to "the wild west". A protocol-number equivalent of RFC-1918 or private ASNs.
> You can use these for whatever you want, but so can anyone e
On 30/11/2012 21:01, Claudio Jeker wrote:
> Still carp packets can coexist with vrrp packets. They use a different
> version numbers.
And the same mac address pool, which means that if you use the same vhid as
vrrp group number, you will trash both your carp and vrrp virtual IPs.
Carp was coded e
On Fri, Nov 30, 2012 at 10:01:54PM +0100, Claudio Jeker wrote:
> implementation would not have been accepted. The result would be a draft
> that would never be adopted and so it is back to start.
"Adopted" by whom? The procedure, even at the time, did not require
in any way IETF consensus. Getti
On Sat, Dec 01, 2012 at 02:05:14AM +1030, David Walker wrote:
> As far as not using the same protocol number, that's neither here nor there.
Horse pucky. On the Internet, the secure and reliable players
co-ordinate their protocol actions through the IANA, using the
published IANA rules for how yo
On Fri, Nov 30, 2012 at 08:48:48AM -0800, David Conrad wrote:
> On Nov 30, 2012, at 5:08 AM, Henning Brauer wrote:
> > and re IANA, they made it clear they would not give us a proto number
>
> As they should have. IANA abides by the rules laid down for it by the
> IETF/IESG/IAB. The openbsd folks
>> I believe that idea has legs regardless of practical considerations
>> and stands on it's own.
>>
>> Besides, I won't discount OpenBSD out of hand for forging ahead,
>> withstanding practical issues, considering the runs they've got on the
>> board and the many facepalm fails we see in the diam
This issue came up originally during my tenure at IANA, and FWIW I
concur with David. I have a vague memory of engaging directly with some
folks from OpenBSD and letting them know that I was sympathetic with
their situation, but IANA has strict rules to follow, and unless they
followed procedure my
On Nov 30, 2012, at 5:08 AM, Henning Brauer wrote:
> and re IANA, they made it clear they would not give us a proto number
As they should have. IANA abides by the rules laid down for it by the
IETF/IESG/IAB. The openbsd folks couldn't be bothered to even write up a draft
and chose to squat on a
Comments inline ... as best I can.
On 30/11/2012, Robert E. Seastrom wrote:
>
> David Walker writes:
>
>> [ patent fight recap ]
>
> Thanks for posting those. I recall the discussions surrounding the
> HSRP patents well, but it's been a while and I have proportionally
> more gray hair (and less
Stuart Henderson writes:
> I don't see anything here indicating that it's to do with CARP
> believing things sent over the wire, I suspect the problem would still
> occur if CARP were disabled on the pfSense box. (Do people really
> run CARP in the wild without authentication anyway?)
1) it did
Jussi Peltola writes:
> The amount of detail in the original posting is rather disappointing,
> with absolutely no hope of anyone being able to reproduce the problem
> with the data given.
It was not intended as a bug report, instead merely an expression of
disappointment and an advsory to fell
Henning Brauer writes:
> * Robert E. Seastrom [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-wri
On 2012-11-30, Randy Bush wrote:
>> case of the same situation all[1] 'software md5 tcp' implementations
>> have? sign but never verify...
>
> and freebsd :(
>
>
openbsd verifies these, btw.
On 2012-11-30, Robert E. Seastrom wrote:
>
> I can't seem to recall anyone griping about this here on our august
> little list but google finds that I'm by no means the first to have
> been burned by an unholy interaction between VRRP and CARP.
>
> Let's skip the protocol discussions (same protoco
* Robert E. Seastrom [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
On 30/11/2012 05:52, Robert E. Seastrom wrote:
> [*] The OpenBSD side of the story can be read at
> http://en.wikipedia.org/wiki/Common_Address_Redundancy_Protocol#No_official_Internet_protocol_number
>
> Seems that there is a lesson to be learned here:
>
> "o hai, we wrote this software but can
David Walker writes:
> [ patent fight recap ]
Thanks for posting those. I recall the discussions surrounding the
HSRP patents well, but it's been a while and I have proportionally
more gray hair (and less overall) now.
My problem is not with Theo nor with the IETF. My problem is with a
crapp
The amount of detail in the original posting is rather disappointing,
with absolutely no hope of anyone being able to reproduce the problem
with the data given.
Did the vhid and vrrp group overlap? Were there duplicate IP addresses?
> case of the same situation all[1] 'software md5 tcp' implementations
> have? sign but never verify...
and freebsd :(
On 30/11/2012, Robert E. Seastrom wrote:
> [*] The OpenBSD side of the story can be read at
> http://en.wikipedia.org/wiki/Common_Address_Redundancy_Protocol#No_official_Internet_protocol_number
>
> Seems that there is a lesson to be learned here:
>
> "o hai, we wrote this software but can not be
On Fri, Nov 30, 2012 at 12:52 AM, Robert E. Seastrom wrote:
> Note that the Ciscos didn't exhibit any untoward behavior, and there
> were "passwords" on the VRRP sessions too.
case of the same situation all[1] 'software md5 tcp' implementations have?
sign but never verify...
-chris
[1]: solaris
22 matches
Mail list logo
