[21864] in North American Network Operators' Group
Re: SOLVED! The cause of puzzling TCP (eg. WHOIS) connection failureswith some InterNIC.net hosts
daemon@ATHENA.MIT.EDU (Jared Mauch)
Sun Nov 22 01:52:18 1998
Date: Fri, 20 Nov 1998 19:18:06 -0500
From: Jared Mauch <jared@puck.nether.net>
To: "Rubens Kuhl Jr." <rkj@uol.com.br>, Marc Slemko <marcs@znep.com>
Cc: North America Network Operators Group <nanog@merit.edu>
Mail-Followup-To: "Rubens Kuhl Jr." <rkj@uol.com.br>,
Marc Slemko <marcs@znep.com>,
North America Network Operators Group <nanog@merit.edu>
In-Reply-To: <003501be14df$77e5e450$0518e6c8@rubens.uol.com.br>; from Rubens Kuhl Jr. on Fri, Nov 20, 1998 at 09:42:43PM -0200
I would guess bigIP as that's what their sales folks said
they used. Our luck with them was less than that of what they said
it would be. It's now no longer in our network.
*big* mistake and big headache.
- jared
On Fri, Nov 20, 1998 at 09:42:43PM -0200, Rubens Kuhl Jr. wrote:
> > The problem in this case is probably the load balancing systems that
> > NSI is now using, which have known bogus behaviour when interacting
> > with PMTU-D. NSI should disable PMTU-D on their servers until they
> > can fix this problem; fixing this problem probably involves having
> > the vendor for their load balancing boxes fixing their broken
> > software.
>
> What load balancing systems are known to mess up with PMTU-D ?
>
>
>
> Rubens Kuhl Jr.
--
Jared Mauch | pgp key available via finger from jared@puck.nether.net
clue++; | http://puck.nether.net/~jared/
