From owner-freebsd-gnome@FreeBSD.ORG Wed Feb 27 17:09:38 2013 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9C9A38B1 for ; Wed, 27 Feb 2013 17:09:38 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by mx1.freebsd.org (Postfix) with ESMTP id 62970F40 for ; Wed, 27 Feb 2013 17:09:38 +0000 (UTC) Received: by mail-oa0-f48.google.com with SMTP id j1so1648558oag.21 for ; Wed, 27 Feb 2013 09:09:37 -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=tSTEps9iOD6/MmTH/MHWAtNnwex9N1XskfNGRWDgFx4=; b=WfpDE3nIG67yjMm02+On/pi7nCt4wAdTurkGsBdnwo73bOV31ztFID+xud5Dyc7PLI TgIx3mXihWNGxAOPECboy2jak8TMBEmz4XuaZ8LqqFQQZglIyq6iG4fFemmpTGmtsmqa CZzcaAk6MxrYxfaiK9Stpuyhtomq4oj455QeYd3JdEFzFROvZ0B9cUmcWR0xOcbcEjV/ MW4WBCCSagI6MQi5iNFHKy+QgU6vn2VwABgnV3o7FOXxq8QBsnB141D1WzSrhW7hLeSG HEwqZixtDMcOepqVtL4xHG5VOkEE0fE/kz/HgpQvNbKNvxbs7wLoYjc5y24xKdETpiYX M/iQ== MIME-Version: 1.0 X-Received: by 10.182.156.103 with SMTP id wd7mr2905159obb.33.1361984977633; Wed, 27 Feb 2013 09:09:37 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.76.34.197 with HTTP; Wed, 27 Feb 2013 09:09:37 -0800 (PST) In-Reply-To: References: Date: Wed, 27 Feb 2013 09:09:37 -0800 X-Google-Sender-Auth: u1Osg7n5q_NPYJU4aAs7-THcuf4 Message-ID: Subject: Re: Issue with IPv6 address for www.freebsd.org From: Kevin Oberman To: Keng Soon Goh Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-gnome@FreeBSD.org" X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2013 17:09:38 -0000 On Wed, Feb 27, 2013 at 5:44 AM, Keng Soon Goh wrote: > Kevin, > > I found the issue. It is on Level3. Level3 gave away two /48 IPv6 subnet > to his client, but when in their network, they summaries the subnet to /32. > I do not believe they advertised out to the whole world an existing /48. I > worked with another upstream provider whom their upstream is Level3, and > they said they only see one /32. So, whoever use Level3 as their upstream > provider will have issue accessing to these IPv6 subnet. I already worked > with Level3 yesterday evening on this. > > * 2001:1900::/32 2001:1890:FF:FFFF:12:122:125:6 > 0 7018 3356 i > * 2001:1900:2254::/48 > 2001:1890:FF:FFFF:12:122:125:6 > 0 7018 6939 > 10310 i > * 2001:1900:2262::/48 > 2001:1890:FF:FFFF:12:122:125:6 > 0 7018 6453 > 21775 i > Glad you at least understand the issue. Now, if it can just get fixed. Before I retired I knew enough senior people at L3 to get it fixed quite easily. now they have mostly moved on and I'm quite unsure. This is why I hate punching holes in network blocks...either IPv4 or IPv6. It's too easy to forget and put in some filter, static or policy that breaks the net for those holes if they are announced to peers other than the owner of the block. I always recommend that specific blocks for use as PI addresses be set up so that this does not happen and I am surprised that L3 dis not do this for IPv6. I'll drop a note to my successor who maintains good contacts with senior routing people and is also a strong proponent of IPv6. L3 is also their fiber provider, so they deal with a different part of L3 quite a bit. As use of IPv6 grows, these problems will become rate as they will result it trouble calls much more quickly and in larger numbers. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com