From: Robert Bradley <robert.bradley1@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] shaggy dog story on 3.8.8-4 experiences
Date: Wed, 1 May 2013 00:42:34 +0100 [thread overview]
Message-ID: <CAA=Zby5jsLiqD-o+E53fGnX2d4f6Q=nkjwsif78vzGCBjLQqpw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw434b66dmZigbmPNH2cRigK3h9qN_-P9ZqrcrMK1hGpFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
On 30 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
> > 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
[-- Attachment #2: Type: text/html, Size: 1375 bytes --]
next prev parent reply other threads:[~2013-04-30 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 19:29 Michael Richardson
2013-04-30 20:45 ` Dave Taht
2013-04-30 23:42 ` Robert Bradley [this message]
2013-05-01 12:58 ` Michael Richardson
2013-05-05 15:25 ` Steven Barth
2013-05-16 19:21 ` Michael Richardson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA=Zby5jsLiqD-o+E53fGnX2d4f6Q=nkjwsif78vzGCBjLQqpw@mail.gmail.com' \
--to=robert.bradley1@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox