From owner-freebsd-current@FreeBSD.ORG Sat Mar 2 17:19:34 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0DE191A6 for ; Sat, 2 Mar 2013 17:19:34 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oa0-f46.google.com (mail-oa0-f46.google.com [209.85.219.46]) by mx1.freebsd.org (Postfix) with ESMTP id A34C389B for ; Sat, 2 Mar 2013 17:19:33 +0000 (UTC) Received: by mail-oa0-f46.google.com with SMTP id k1so7338543oag.33 for ; Sat, 02 Mar 2013 09:19:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=zvC4MIlKq6CnrDIdPuzB11mQb53ry/TcV+uKCiM5BGw=; b=xfuhV4luA09Mq9lQNcV8iPHDmNEYvIp3E5jR3ddw6Eds7jHOYqTD8+SYK/kxTbUhgD lG2ogNdvli407V0ceVhctTPo8gTZ2Cs6UJIEXk7uBH9ush3fQU8ac4JWCQ0JM7FBgIpt HOkIWItpYdHvR9qjQmrANdb0LaRaRkFrAALcPHDk1DiJ+VxX+3kZZs/YptWCmyHdBjiE veGbBC/0Otmsgaxwbqk0gA8ifU4uHEE8lDSFiU4RT8jqIm+DuRmHixkvIaLmkDWeFcum PcwYHYorYPRqkqFxc3RX88s6uP+tFkn7pk3zkiWmPly6CZMnjG4La2Maq6jqpgUYGRFi EAvQ== MIME-Version: 1.0 X-Received: by 10.182.156.103 with SMTP id wd7mr11747912obb.33.1362244767020; Sat, 02 Mar 2013 09:19:27 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.76.34.197 with HTTP; Sat, 2 Mar 2013 09:19:26 -0800 (PST) In-Reply-To: <5132129F.1020108@a1poweruser.com> References: <512DE205.4010202@digsys.bg> <512E4D3F.6050900@gmail.com> <512E64CA.6030408@daemonic.se> <512F431E.7080507@a1poweruser.com> <5132129F.1020108@a1poweruser.com> Date: Sat, 2 Mar 2013 09:19:26 -0800 X-Google-Sender-Auth: B1nM3yUAfYz9zAEC7eGDMz0TQUQ Message-ID: Subject: Re: Response of *.freebsd.org websites are very slow From: Kevin Oberman To: Fbsd8 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: matt , Peter Wemm , Current , Daniel Kalchev , Niclas Zeising , Daniel Nebdal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Mar 2013 17:19:34 -0000 On Sat, Mar 2, 2013 at 6:54 AM, Fbsd8 wrote: > Peter Wemm wrote: > >> On Thu, Feb 28, 2013 at 3:44 AM, Fbsd8 wrote: >> [..] >> >>> From cleveland ohio and www.freebsd.org is un-reachable again. It comes >>> and >>> gos. To me it's acting like someone high up is making dns changes. >>> Some freebsd official better contact yahoo and put a stop to what ever >>> there >>> fooling around with. >>> >> >> Nope. It isn't DNS, but there is a routing issue for ipv6 space >> between Level-3 and and Yahoo. I'm working on it. >> >> > Peter Wemm; > Just to keep you up to date, it's now March 02 and the same slowness / > time out problem still exists. What ever your doing is causing it. Please > don't leave your trial ipv6 fix in effect when your not actively working on > the problem. Your trial fix is effecting all the "freebsd" sites. Leaving > your nonworking trial fix in live production status is NOT the correct way > of testing it. Restoring the environment to the known working condition in > between cycles of testing your trial fix is the normal accepted method of > testing such production level fixes to limit the un-desirable effects of > said production level testing. > As of this time there is NO IPv6 address for www.freebsd.org. I assume that it was removed until the issues of routing between Y! and Level(3) are resolved. I'm not at all sure why you refer to the IPv6 support as a "trial". As far as I know, the IPv6 was intended to be normal, production service and, for almost everyone, it worked fine, Unfortunately, the routing via Level(3) was not set up correctly and freebsd.org could not be reached via Level(3). It was NOT an IPv6 issue. The same thing has caused the same sort of problems with IPv4 and will continue to do so as it is simply two parties not understanding what the other expects in terms of routing. Also, please don't blame either side unless you know more details of the address assignment than are publicly available. I do find it disturbing that it is taking so long to fix, though. It really is not rocket science for people who understand BGP and routing policy. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com