From: Dave Taht <dave.taht@gmail.com>
To: Richard Brown <richard.e.brown@dartware.com>
Cc: jow@openwrt.org,
"<cerowrt-devel@lists.bufferbloat.net>"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Good news with 3.3.8-6 (was: Still trouble with 6in4 tunnel)
Date: Tue, 19 Jun 2012 22:39:19 -0400 [thread overview]
Message-ID: <CAA93jw5AKM8GFhoq0-q+c7RQg0fsuaSQwUYu-K0_7+--fJPXQw@mail.gmail.com> (raw)
In-Reply-To: <BC328B92-D219-40EA-9406-73798D542C2B@intermapper.com>
On Tue, Jun 19, 2012 at 10:29 PM, Richard Brown
<richard.e.brown@dartware.com> wrote:
> Good news on the IPv6 tunneling front. A 6in4 tunnel to Hurricane Electric's Tunnelbroker.net simply works out of the box for build 3.3.8-6.
>
> Use the script at the bottom of the page below to establish the tunnel. Copy the info from the Tunnelbroker web page to the script and run the script. CeroWrt will establish the tunnel and assign IPv6 addresses to each of the interfaces. The script and instructions are at:
>
> http://www.bufferbloat.net/projects/cerowrt/wiki/IPv6_Tunnel
>
> NB The script does not assign an IPv6 address to either of the babel interfaces: I could not test it, so I left those lines commented out.
Babel interfaces use the same /128 for all interfaces. What I
typically do with a 48 available is is
2001:XXXX:YYYY:bab1::1/128
And then give ahcp
2001:XXXX:YYYY:bab1::2/64
to distribute.
And this script can be automated somewhat more, but I'm delighted to
hear it works now...
>
> Best regards,
>
> Rich Brown
> Hanover, NH USA
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
SKYPE: davetaht
http://ronsravings.blogspot.com/
prev parent reply other threads:[~2012-06-20 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6.1340132403.3495.cerowrt-devel@lists.bufferbloat.net>
2012-06-20 2:29 ` Richard Brown
2012-06-20 2:39 ` Dave Taht [this message]
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=CAA93jw5AKM8GFhoq0-q+c7RQg0fsuaSQwUYu-K0_7+--fJPXQw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=jow@openwrt.org \
--cc=richard.e.brown@dartware.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