Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Richard Brown <richard.e.brown@dartware.com>
Cc: "<cerowrt-devel@lists.bufferbloat.net>"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Still trouble with 6in4 tunnel
Date: Sun, 10 Jun 2012 10:33:59 -0400	[thread overview]
Message-ID: <CAA93jw6kLy8PFUKF0P6vW=i7P0yBzjTEkz0uo_a9SuYCTPSwpA@mail.gmail.com> (raw)
In-Reply-To: <CEF5A6A5-C89C-434D-ABEE-B2C9AE711687@intermapper.com>

I will take a look at this after I get 3.3.8-2 done

On Sun, Jun 10, 2012 at 10:23 AM, Richard Brown
<richard.e.brown@dartware.com> wrote:
> Folks,
>
> I have been working off and on to get IPv6 addressing working on multiple interfaces on CeroWrt 3.3.6-2. I can make it work on any single interface, but not two at once.
>
> I did ask on the openwrt-devel list, but got some unhelpful answers (they said that my demo file had the wrong info because I had obfuscated my userid and password). Furthermore CeroWrt *is* somewhat different in that each of its interfaces has a different subnet, and I suspect this may be related, and thus my question:
>
> Here's my setup: I have a 6in4 tunnel from Hurricane Electric working fine. When I ssh into CeroWrt and ping and traceroute to IPv6 addresses, everything work as expected.
>
> I tested the attached script from a fresh installation of CeroWrt 3.3.6-2. The script assigns two interfaces with IPv6 addresses from the /48 that HE assigns, like this:
>
> uci set network.se00.ip6addr='2001:470:8a63:100::1/64'
> uci set network.sw10.ip6addr='2001:470:8a63:200::1/64'
>
> Restarting the router with this configuration allows one to work, but not the other. Specifically, my MacBook gets an IPv6 address on one interface, but after unplugging and switching to the other interface, it does not get an IPv6 address. (It may be related to which interfaces was up/had something connected when the router  when it restarted.)
>
> My questions:
>
> 1) Are the commands in the attached script "going in the right direction"?
>
> 2) Should I be assigning separate /64s on each of the interfaces?
>
> 3) What other information could I provide?
>
> Once I get this working, I'll update my posting on the wiki - http://www.bufferbloat.net/projects/cerowrt/wiki/IPv6_Tunnel Many thanks.
>
> 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/

  reply	other threads:[~2012-06-10 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2.1339182003.1217.cerowrt-devel@lists.bufferbloat.net>
2012-06-10 14:23 ` Richard Brown
2012-06-10 14:33   ` Dave Taht [this message]
2012-06-12  0:52   ` Chris Lawrence
     [not found] <mailman.2.1339354802.28006.cerowrt-devel@lists.bufferbloat.net>
2012-06-19 15:26 ` Richard Brown
2012-06-19 16:05   ` 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='CAA93jw6kLy8PFUKF0P6vW=i7P0yBzjTEkz0uo_a9SuYCTPSwpA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --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