From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 2C8B221F0D3 for ; Tue, 30 Apr 2013 16:42:36 -0700 (PDT) Received: by mail-wg0-f50.google.com with SMTP id m15so957005wgh.17 for ; Tue, 30 Apr 2013 16:42:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=0O7HOCnzRU8dOCa+3IQyWM0KD5Zv79iFNVOAtZE4KJ8=; b=fi9NLh/HC2RO9XZtmo0GWHkS8R9Nd531Cyyu4fC26zKR4k54hAnq0zgcQnQqnYS8Dv nN7RZsJ/dBNxTJTjEgUu87BEh9VVHaY+LBPiB8rMdCAWaDeFthcqDtM1b7rA0V1fu1UG LZ/e04f22ulwOsDWSH/SfebZw4YEEberpz5cLZHQ0WIwfefuJhqWaVrYWkzkuQkhQcfO /Q+ot5ADh1nEoxwAdT8PmG3zfdAlIv65RiBlFQtfX589k9/g63WLjXfrdlWmNov+ppi6 UVi0ac8xOFys1GSM6OSNW8BbF8qgREbhcnTIyZpr26rsorgj4da5BPDgcD1+Q2jJg4q0 n5Cw== MIME-Version: 1.0 X-Received: by 10.194.7.68 with SMTP id h4mr391214wja.49.1367365355034; Tue, 30 Apr 2013 16:42:35 -0700 (PDT) Received: by 10.194.170.67 with HTTP; Tue, 30 Apr 2013 16:42:34 -0700 (PDT) In-Reply-To: References: <29781.1367350165@sandelman.ca> Date: Wed, 1 May 2013 00:42:34 +0100 Message-ID: From: Robert Bradley To: Dave Taht Content-Type: multipart/alternative; boundary=047d7b450a2243ddb604db9c8e9d Cc: cerowrt-devel Subject: Re: [Cerowrt-devel] shaggy dog story on 3.8.8-4 experiences X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 23:42:37 -0000 --047d7b450a2243ddb604db9c8e9d Content-Type: text/plain; charset=UTF-8 On 30 April 2013 21:45, Dave Taht wrote: > On Tue, Apr 30, 2013 at 12:29 PM, Michael Richardson > wrote: > > 5) I did get prefixes assigned to interfaces... alas, it duplicated > > prefixes which were already assigned to other interfaces!!! > > I did setup the hints, but perhaps not for all interfaces. > > I'm not sure what you are talking about here. ipassign 64 will take > the 64 hint and assign something to it. > This is referring to something I have run into before, where the auto-assignment code ignores any manually assigned /64 prefixes. If you hypothetically assign fd00:0:1::/64 to se00 and fd00:0:2::/64 to sw00, the auto-assignment has a tendency to assign fd00:0:1::/64 to sw00 along with your manually-assigned prefix. I don't know how well auto-assignment plays with AHCP, so I have tended to set things up manually to get around this. -- Robert Bradley --047d7b450a2243ddb604db9c8e9d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On 3= 0 April 2013 21:45, Dave Taht <dave.taht@gmail.com> wrote:=
On Tue, Apr 30, 2013 at 12:29 PM, Michael Richardson <= mcr@sandelman.ca> wrote:
> 5) I did get prefixes assigned to interfaces... alas, it duplicated > =C2=A0 =C2=A0prefixes which were already assigned to other interfaces!= !!
> =C2=A0 =C2=A0I did setup the hints, but perhaps not for all interfaces= .

I'm not sure what you are talking about here. ipassign 64 will ta= ke
the 64 hint and assign something to it.

This is referring to something I have run into before, where the auto-assi= gnment code ignores any manually assigned /64 prefixes.=C2=A0 If you hypoth= etically assign fd00:0:1::/64 to se00 and fd00:0:2::/64 to sw00, the auto-= assignment has a tendency to assign fd00:0:1::/64 to sw00 along with your = manually-assigned prefix.=C2=A0 I don't know how well auto-assignment p= lays with AHCP, so I have tended to set things up manually to get around th= is.
--
Robert Bradley
--047d7b450a2243ddb604db9c8e9d--