From: Richard Brown <richard.e.brown@dartware.com>
Cc: "<jow@openwrt.org>" <jow@openwrt.org>,
Richard Brown <richard.e.brown@dartware.com>,
"<cerowrt-devel@lists.bufferbloat.net>"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] UPDATE: IPv6 & 3.3.8-21 - working fine...
Date: Sat, 15 Sep 2012 00:21:16 +0000 [thread overview]
Message-ID: <D3BCDB20-27E5-454F-8A5C-C44CC032342B@intermapper.com> (raw)
In-Reply-To: <CAA93jw5ooOjTVXknOjtfoaaA=Qp_Y_-+_nMqK=xxy7tUepfXsw@mail.gmail.com>
Folks,
Here's an update on functioning of IPv6 in CeroWrt. I had posted a note in mid-August saying that I had troubles making IPv6 work properly in 3.3.8-17. Specifically, I was using the script from http://www.bufferbloat.net/projects/cerowrt/wiki/IPv6_Tunnel to configure IPv6 to work with Hurricane Electric's free Tunnelbroker.net service, and it not all interfaces got addresses as expected.
After a bit of testing, I am happy to say that the script on the IPv6 Tunnel page above seems to work properly on 3.3.8-21, the latest CeroWrt build. This script is substantially the same as earlier versions: I didn't have to tweak any radvd or other configs beyond what's in this script.
Best,
Rich Brown
Hanover, NH
PS I also posted a note about using mDNS/Bonjour on CeroWrt. By default, this works as desired on all the local interfaces; the note (http://www.bufferbloat.net/projects/cerowrt/wiki/Using_Bonjour_mDNS_or_ZeroConf_with_CeroWrt) gives instructions for passing the mDNS traffic out the WAN port, for instances where you are using CeroWrt as a secondary router in your home.
next prev parent reply other threads:[~2012-09-15 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 11:56 [Cerowrt-devel] IPv6 doesn't work quite right in 3.3.8-17 as 3.3.8-6 Richard Brown
2012-08-20 17:36 ` Dave Taht
2012-08-20 18:01 ` Richard Brown
2012-09-15 0:21 ` Richard Brown [this message]
2012-09-15 11:27 ` [Cerowrt-devel] UPDATE: IPv6 & 3.3.8-21 - working fine Sébastien Gaggini
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=D3BCDB20-27E5-454F-8A5C-C44CC032342B@intermapper.com \
--to=richard.e.brown@dartware.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=jow@openwrt.org \
/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