From: Vincent Frentzel <zcecc22@c3r.es>
To: Dave Taht <dave.taht@bufferbloat.net>
Cc: cerowrt-devel@lists.bufferbloat.net, g@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] IPV6 success on 3.10.28-14 with 6to4 tunnel and 6relayd
Date: Mon, 24 Feb 2014 02:35:38 +0000 [thread overview]
Message-ID: <CACCCjEUtkTw+Od7xgnJBCuUyQkd9DPCnSyiAYduEYWMvBtiyUg@mail.gmail.com> (raw)
In-Reply-To: <20140223170738.GA24483@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]
>
> > Hi everyone,
> >
> > After struggling a while with odhcpd and route propagation I wanted to
> > report that I got ipv6 working with the following config for 6relayd.
>
> I am under the impression that 6relayd is now obsolete and that these
> are controlled in the /etc/config/dhcp file.
>
That is correct. However, when using odhcpd I could nt get IPV6 routing
over different segments (ie pings from SW10 to SE00 gave network
unreachable).
In the end 6relayd worked althoug Im not sure why.
Im curious to see if anyone has encountered the same issue.
On Sun, Feb 23, 2014 at 5:07 PM, Dave Taht <dave.taht@bufferbloat.net>wrote:
> On Fri, Feb 21, 2014 at 12:15:13AM +0100, Vincent Frentzel wrote:
> > Hi everyone,
> >
> > After struggling a while with odhcpd and route propagation I wanted to
> > report that I got ipv6 working with the following config for 6relayd.
>
> I am under the impression that 6relayd is now obsolete and that these
> are controlled in the /etc/config/dhcp file.
>
> >
> > config server se00
> > list network se00
> > option rd server
> > option dhcpv6 server
> > option management_level 1
> >
> > config server sw00
> > list network sw00
> > option rd server
> > option dhcpv6 server
> > option management_level 1
> >
> > config server sw10
> > list network sw10
> > option rd server
> > option dhcpv6 server
> > option management_level 1
> >
> >
> > Hope this can be of use to someone or contribute to the next release :)
> >
> >
> > BR,
> >
> > Vincent
>
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 3461 bytes --]
next prev parent reply other threads:[~2014-02-24 2:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 23:15 Vincent Frentzel
2014-02-23 17:07 ` Dave Taht
2014-02-24 2:35 ` Vincent Frentzel [this message]
2014-02-24 3:15 ` Dave Taht
[not found] ` <631f38e0-0042-4f4d-a8df-4975dc497ab7@email.android.com>
2014-02-24 15:27 ` Dave Taht
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=CACCCjEUtkTw+Od7xgnJBCuUyQkd9DPCnSyiAYduEYWMvBtiyUg@mail.gmail.com \
--to=zcecc22@c3r.es \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@bufferbloat.net \
--cc=g@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