Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Chris Lawrence <lordsutch@gmail.com>
Cc: cerowrt@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] 6to4 [bug #406]
Date: Mon, 24 Sep 2012 17:56:45 -0700	[thread overview]
Message-ID: <CAA93jw5Qz72fvT4cnJM=-eJ8ghPkzGZEn67uA1kw4s016=UPRw@mail.gmail.com> (raw)

On Wed, Sep 19, 2012 at 3:58 PM, Chris Lawrence <lordsutch@gmail.com> wrote:
> I've only noticed one real problem thus far: radvd is still
> advertising incorrect subnet addresses for 6to4 connections (addresses
> that start with 0:0:0:$adv_subnet, which clearly are wrong since all
> the addresses should be under 2002: to be routable on the ipv6
> Internet).  The fix is simple: in /lib/netifd/proto/6to4.sh, line 162
> should read:
>
>                                 "$wancfg" "$subnet6" \
>
> instead of the printf call that's there now.  This is probably an
> upstream OpenWRT problem too.

Actually, no, the correct line would be:

                        set_6to4_radvd_prefix    "$sid" "$adv_interface" \
                                "$wancfg" "$(printf "%s:%x::/64"
$prefix6 $adv_subnet) \
                                "$adv_valid_lifetime" "$adv_preferred_lifetime"

arguably "subnet6" is misnamed.

There is another bug in this script in correctly adding multiple
interfaces. It succeeds on the first, but not the rest, and thus far I
can't figure out why.

There is another bug in that arguably the interface itself should have
a prefix lifetime (monitored somehow) and mtu set and I'd argue for
marking it secondary in the hope that someday real ipv6 addresses
would become common.

And last bug, in that with the latest quagga OR dnsmasq, radvd is not
needed, except for detecting and generating the 6to4 prefix.



>
>
> Chris
> --
> Chris Lawrence <lordsutch@gmail.com>
>
> Website: http://www.cnlawrence.com/
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
with fq_codel!"

                 reply	other threads:[~2012-09-25  0:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAA93jw5Qz72fvT4cnJM=-eJ8ghPkzGZEn67uA1kw4s016=UPRw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cerowrt@lists.bufferbloat.net \
    --cc=lordsutch@gmail.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