Date: Sat, 02 Mar 2013 09:54:23 -0500 From: Fbsd8 <fbsd8@a1poweruser.com> To: Peter Wemm <peter@wemm.org> Cc: matt <sendtomatt@gmail.com>, Kevin Oberman <rkoberman@gmail.com>, Current <freebsd-current@freebsd.org>, Daniel Kalchev <daniel@digsys.bg>, Niclas Zeising <zeising@daemonic.se>, Daniel Nebdal <dnebdal@gmail.com> Subject: Re: Response of *.freebsd.org websites are very slow Message-ID: <5132129F.1020108@a1poweruser.com> In-Reply-To: <CAGE5yCq-esiAmvBBHR4hBp6kOjhY_jkstTVdxa74yZY0UASJ0g@mail.gmail.com> References: <CAOgwaMvs2%2Bff0Y-VBdrzG7813GhGx5-TF_7D6WjAoAtD_BCtFQ@mail.gmail.com> <CA%2Bt49PJ6seVBWKW3u3pQE%2BdNbdvCrX2tL5_RmXOa5b6funb_kw@mail.gmail.com> <512DE205.4010202@digsys.bg> <CAOgwaMvtXLhj1m2iQxaZ-NeUkY_DQ1Mu0KeKUhCwvkFyht1y=w@mail.gmail.com> <CA%2Bt49PLjs%2Bp56S%2B8bu3QUi936LGhG1kt0NNwZS4YNQWFirOHhw@mail.gmail.com> <CAOgwaMtfYKbcJ9BiWCK5US2n7GGHJzLH6YTOfNTiDSe6nJxriw@mail.gmail.com> <512E4D3F.6050900@gmail.com> <CAOgwaMucYBEF9OXeuNWjugEFOsG6fm3k5fZase4091E7B4rADw@mail.gmail.com> <512E64CA.6030408@daemonic.se> <CAN6yY1vZYFKrhCYASemSFPRvScma32BqSZFErAZKF587Ke%2BsOQ@mail.gmail.com> <CAGE5yCrjna1Gr3WDmt5Z1aaGLLQb-E3a_2PN9=pDxV75_GUZHA@mail.gmail.com> <512F431E.7080507@a1poweruser.com> <CAGE5yCq-esiAmvBBHR4hBp6kOjhY_jkstTVdxa74yZY0UASJ0g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Wemm wrote: > On Thu, Feb 28, 2013 at 3:44 AM, Fbsd8 <fbsd8@a1poweruser.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5132129F.1020108>