Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Steven Barth <cyrus@openwrt.org>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt dev 3.8.13-7 released
Date: Wed, 12 Jun 2013 00:37:19 -0700	[thread overview]
Message-ID: <CAA93jw6aw0c7v8oXXJJbLnby2gTE5=ncX0f0A+gsoz7XT63LJA@mail.gmail.com> (raw)
In-Reply-To: <51B82AB8.3090204@openwrt.org>

[-- Attachment #1: Type: text/plain, Size: 4378 bytes --]

Thank you! I'll look into it in the morning. Do you do a tos inherit on the
setup? Seems useful (copies the entire tos field, including ecn bits,
to the header and back)

Also you might want to look over the patch at:

https://lists.bufferbloat.net/pipermail/bloat-devel/2013-June/000435.html

You can see the effect on (a saturated) 6in4 system via tc class show dev
your_device. I only slammed it in yesterday so I haven't been able to A/B
the results against a system without the patch, so no warrantees express,
written or implied....

On Wed, Jun 12, 2013 at 1:00 AM, Steven Barth <cyrus@openwrt.org> wrote:

> Not having looked at your particular 6in4 setup but I can imagine where
> the issue comes from.
>
> Source-based IPv6 routing was introduced a few weeks ago to properly
> support multiple IPv6 uplink-interfaces. Therefore OpenWrt only let's you
> route through the tunnel if it knows you have a suitable source address.
>
> That means you now have to add your routed /64 or /48 in the 6in4 tunnel
> settings (UCI-variable ip6prefix) either through the WebUI or in
> /etc/config/network directly. See: http://wiki.openwrt.org/doc/**
> uci/network6#in4.tunnel.henet.**tunnelbroker.sixxs.static.**tunnel<http://wiki.openwrt.org/doc/uci/network6#in4.tunnel.henet.tunnelbroker.sixxs.static.tunnel>
>
> In addition configuring the downstream interfaces using ip6addr is not
> supported any more. One has to use the ip6assign/ip6hint/ip6class method as
> described here:
> http://wiki.openwrt.org/doc/**uci/network6#downstream.**
> configuration.for.lan-**interfaces<http://wiki.openwrt.org/doc/uci/network6#downstream.configuration.for.lan-interfaces>
>
> If you still use ip6addr instead of the new mechanism you might simply get
> "Network Unreachable" errors or - in newer versions - "Source address
> failed ingress/egress policy".
>
>
> I hope this helps.
>
>
> Cheers,
>
> Steven
>
>
>
>
> On 12.06.2013 08:10, Dave Taht wrote:
>
>> And is at:
>>
>> http://snapon.lab.bufferbloat.**net/~cero2/cerowrt/wndr/3.8.**13-7/<http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.8.13-7/>
>>
>> I've had it up and running a few days on a couple routers,
>>
>> and yes, I'm still trying to take some time off but:
>>
>> + can't crash it over wifi anymore
>> + AQM + gui is coming along, am looking at gargoyle's methods a bit now...
>>
>> - Known bug: 6in4 does not work via the gui or openwrt config file -
>> this bug has existed for about a month now
>> and I haven't looked into it. I did look into fixing fq_codel
>> performance under 6in4, and that patch is in here,
>> so after a bit more testing I'll try to get that upstream...
>>
>> - the results I get from 802.11e are even more dismal than usual when
>> the VI and VO queues are in full use.
>> + For purely best effort wifi traffic, things look pretty good.
>>
>> I am seriously considering disabling 802.11e negotiation in the next
>> release.
>>
>> I did prove 6in4 is working with the std-from-hurricane-electric script,
>> so it's a bug in netifd, cero's config, or elsewhere at the openwrt
>> level...
>>
>> modprobe ipv6
>> ip tunnel add he-ipv6 mode sit remote $the_he_tunnel  local $my_local_ip
>> ttl 255 tos inherit
>>
>> # Note that I don't know if openwrt turns on tos inherit or not, btw,
>> need to look into it. It's potentially useful
>>
>> ip link set he-ipv6 up
>> ip addr add $mylink/64 dev he-ipv6
>> ip route add ::/0 dev he-ipv6
>> ip -f inet6 addr
>>
>>
>> --
>> Dave Täht
>>
>> Fixing bufferbloat with cerowrt:
>> http://www.teklibre.com/**cerowrt/subscribe.html<http://www.teklibre.com/cerowrt/subscribe.html>
>>
>>
>> ______________________________**_________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.**bufferbloat.net<Cerowrt-devel@lists.bufferbloat.net>
>> https://lists.bufferbloat.net/**listinfo/cerowrt-devel<https://lists.bufferbloat.net/listinfo/cerowrt-devel>
>>
>>
> ______________________________**_________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.**bufferbloat.net<Cerowrt-devel@lists.bufferbloat.net>
> https://lists.bufferbloat.net/**listinfo/cerowrt-devel<https://lists.bufferbloat.net/listinfo/cerowrt-devel>
>



-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

[-- Attachment #2: Type: text/html, Size: 5488 bytes --]

  reply	other threads:[~2013-06-12  7:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12  6:10 Dave Taht
2013-06-12  8:00 ` Steven Barth
2013-06-12  7:37   ` Dave Taht [this message]
2013-06-12  9:11     ` Steven Barth
2013-06-12  9:40       ` Dave Taht
2013-06-12  9:38   ` Ole Troan
2013-06-12  9:58     ` Steven Barth
2013-06-12 10:10       ` Ole Troan
2013-06-12 10:30         ` Steven Barth

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='CAA93jw6aw0c7v8oXXJJbLnby2gTE5=ncX0f0A+gsoz7XT63LJA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cyrus@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