From: Dave Taht <dave.taht@gmail.com>
To: "cb.list6" <cb.list6@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] 6relayd
Date: Fri, 3 Jan 2014 11:40:58 -0500 [thread overview]
Message-ID: <CAA93jw6ecqJGtGhm1LckKhrCrAknCcOPBc7KOdssScotTGKyqA@mail.gmail.com> (raw)
In-Reply-To: <CAD6AjGTnTubaxcRdMx=B+NZFCEZYuCJe6vXOnv0VaCWFYLUSbA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]
At one level I am happy to figure out this is a recently introduced bug.
On the other hand I am not sure if it is 6relayd.
What version of cero was working for you?
On Jan 3, 2014 12:21 AM, "cb.list6" <cb.list6@gmail.com> wrote:
> Hi,
>
> I have been using CeroWRT on Comcast with a 3800 for about 6 month. The
> DHCP-PD config has always been a little unstable for me, but working.
>
> I recently upgraded to:
>
> root@cerowrt:/etc/config# uname -a
> Linux cerowrt 3.10.24 #1 Tue Dec 24 10:50:15 PST 2013 mips GNU/Linux
>
> My WAN gets a /128, but i cannot get DHCP-PD to work to get addresses on
> the rest of my interfaces. The router does seem to have good IPv6 access.
>
>
> I fiddled with the 6relayd config and came up with this, but it does not
> work. Any pointers on how to get this back on track? The result of the
> below config is that the /128 from the WAN interfaces is now present on all
> the interfaces but my attached computers get no addresses.
>
>
> config server 'default'
> option rd 'server'
> option dhcpv6 'server'
> option management_level '1'
> list network 'ge01'
> list network 'gw00'
> list network 'gw01'
> list network 'gw10'
> list network 'gw11'
> list network 'se00'
> list network 'sw00'
> list network 'sw10'
> option fallback_relay 'rd dhcpv6 ndp'
> option master 'ge00'
>
> root@cerowrt:/etc/config# uname -a
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
[-- Attachment #2: Type: text/html, Size: 2382 bytes --]
next prev parent reply other threads:[~2014-01-03 16:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 5:18 cb.list6
2014-01-03 16:40 ` Dave Taht [this message]
2014-01-03 16:50 ` cb.list6
2014-01-03 17:31 ` Dave Taht
2014-01-03 18:15 ` Steven Barth
2014-01-03 18:43 ` Dave Taht
2014-01-04 9:30 ` Steven Barth
2014-01-06 0:42 ` Matt Mathis
2014-01-06 0:48 ` cb.list6
2014-01-06 3:15 ` Dave Taht
2014-01-06 3:48 ` Dave Taht
2014-01-17 6:52 ` Matt Mathis
2014-01-17 12:58 ` Dave Taht
2014-01-18 14:23 ` Steven Barth
2014-01-18 14:38 ` Dave Taht
2014-01-18 14:46 ` Steven Barth
2014-01-18 16:22 ` Dave Taht
2014-01-18 16:34 ` Steven Barth
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=CAA93jw6ecqJGtGhm1LckKhrCrAknCcOPBc7KOdssScotTGKyqA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cb.list6@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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