<br><br><div class="gmail_quote">On Wed, Jun 12, 2013 at 2:11 AM, Steven Barth <span dir="ltr"><<a href="mailto:cyrus@openwrt.org" target="_blank">cyrus@openwrt.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    <div>Hmm I don't currently run 6in4 on an
      OpenWrt router but directly on my proprietary DSL-router which
      does PD so I can't test this right now. <br>
      <br></div></div></blockquote><div><br>I'll be testing over the next week or so, more if I can line up the usual suspects to install this release... or another quick one if I can figure out the delta between 6in4 last month and now.<br>
 <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div>
      I haven't heard about TOS inherit until now either and this am not
      sure how it can be setup on Linux.</div></div></blockquote><div><br>it's just part of the ip tunnel line, wherever that gets called... example:<br><br>ip tunnel add he-ipv6 mode sit remote 72.52.104.74 local 172.20.26.36 ttl 255 tos inherit<br>
<br>I have no idea why it's not on by default. It's useful having the ECN bits if you are using ECN, useful having the tos field if you are trying to make ssh work with the imm bits over ipv6, etc, etc. <br> <br></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div><div><div class="h5"><br>
      <br>
      <br>
      On 12.06.2013 09:37, Dave Taht wrote:<br>
    </div></div></div><div><div class="h5">
    <blockquote type="cite">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,<br>
      to the header and back)<br>
      <br>
      Also you might want to look over the patch at:<br>
      <br>
      <a href="https://lists.bufferbloat.net/pipermail/bloat-devel/2013-June/000435.html" target="_blank">https://lists.bufferbloat.net/pipermail/bloat-devel/2013-June/000435.html</a><br>
      <br>
      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....<br>
      <br>
      <div class="gmail_quote">On Wed, Jun 12, 2013 at 1:00 AM, Steven
        Barth <span dir="ltr"><<a href="mailto:cyrus@openwrt.org" target="_blank">cyrus@openwrt.org</a>></span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
          Not having looked at your particular 6in4 setup but I can
          imagine where the issue comes from.<br>
          <br>
          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.<br>
          <br>
          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: <a href="http://wiki.openwrt.org/doc/uci/network6#in4.tunnel.henet.tunnelbroker.sixxs.static.tunnel" target="_blank">http://wiki.openwrt.org/doc/uci/network6#in4.tunnel.henet.tunnelbroker.sixxs.static.tunnel</a><br>

          <br>
          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:<br>
          <a href="http://wiki.openwrt.org/doc/uci/network6#downstream.configuration.for.lan-interfaces" target="_blank">http://wiki.openwrt.org/doc/uci/network6#downstream.configuration.for.lan-interfaces</a><br>
          <br>
          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".<br>
          <br>
          <br>
          I hope this helps.<br>
          <br>
          <br>
          Cheers,<br>
          <br>
          Steven
          <div>
            <div><br>
              <br>
              <br>
              <br>
              On 12.06.2013 08:10, Dave Taht wrote:<br>
            </div>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div>
              <div>
                And is at:<br>
                <br>
                <a href="http://snapon.lab.bufferbloat.net/%7Ecero2/cerowrt/wndr/3.8.13-7/" target="_blank">http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.8.13-7/</a><br>
                <br>
                I've had it up and running a few days on a couple
                routers,<br>
                <br>
                and yes, I'm still trying to take some time off but:<br>
                <br>
                + can't crash it over wifi anymore<br>
                + AQM + gui is coming along, am looking at gargoyle's
                methods a bit now...<br>
                <br>
                - Known bug: 6in4 does not work via the gui or openwrt
                config file -<br>
                this bug has existed for about a month now<br>
                and I haven't looked into it. I did look into fixing
                fq_codel<br>
                performance under 6in4, and that patch is in here,<br>
                so after a bit more testing I'll try to get that
                upstream...<br>
                <br>
                - the results I get from 802.11e are even more dismal
                than usual when<br>
                the VI and VO queues are in full use.<br>
                + For purely best effort wifi traffic, things look
                pretty good.<br>
                <br>
                I am seriously considering disabling 802.11e negotiation
                in the next<br>
                release.<br>
                <br>
                I did prove 6in4 is working with the
                std-from-hurricane-electric script,<br>
                so it's a bug in netifd, cero's config, or elsewhere at
                the openwrt level...<br>
                <br>
                modprobe ipv6<br>
                ip tunnel add he-ipv6 mode sit remote $the_he_tunnel
                 local $my_local_ip<br>
                ttl 255 tos inherit<br>
                <br>
                # Note that I don't know if openwrt turns on tos inherit
                or not, btw,<br>
                need to look into it. It's potentially useful<br>
                <br>
                ip link set he-ipv6 up<br>
                ip addr add $mylink/64 dev he-ipv6<br>
                ip route add ::/0 dev he-ipv6<br>
                ip -f inet6 addr<br>
                <br>
                <br>
                --<br>
                Dave Täht<br>
                <br>
                Fixing bufferbloat with cerowrt:<br>
                <a href="http://www.teklibre.com/cerowrt/subscribe.html" target="_blank">http://www.teklibre.com/cerowrt/subscribe.html</a><br>
                <br>
                <br>
              </div>
            </div>
            _______________________________________________<br>
            Cerowrt-devel mailing list<br>
            <a href="mailto:Cerowrt-devel@lists.bufferbloat.net" target="_blank">Cerowrt-devel@lists.bufferbloat.net</a><br>
            <a href="https://lists.bufferbloat.net/listinfo/cerowrt-devel" target="_blank">https://lists.bufferbloat.net/listinfo/cerowrt-devel</a><br>
            <br>
          </blockquote>
          <br>
          _______________________________________________<br>
          Cerowrt-devel mailing list<br>
          <a href="mailto:Cerowrt-devel@lists.bufferbloat.net" target="_blank">Cerowrt-devel@lists.bufferbloat.net</a><br>
          <a href="https://lists.bufferbloat.net/listinfo/cerowrt-devel" target="_blank">https://lists.bufferbloat.net/listinfo/cerowrt-devel</a><br>
        </blockquote>
      </div>
      <br>
      <br clear="all">
      <br>
      -- <br>
      Dave Täht<br>
      <br>
      Fixing bufferbloat with cerowrt: <a href="http://www.teklibre.com/cerowrt/subscribe.html" target="_blank">http://www.teklibre.com/cerowrt/subscribe.html</a>
    </blockquote>
    <br>
  </div></div></div>

<br>_______________________________________________<br>
Cerowrt-devel mailing list<br>
<a href="mailto:Cerowrt-devel@lists.bufferbloat.net">Cerowrt-devel@lists.bufferbloat.net</a><br>
<a href="https://lists.bufferbloat.net/listinfo/cerowrt-devel" target="_blank">https://lists.bufferbloat.net/listinfo/cerowrt-devel</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Dave Täht<br><br>Fixing bufferbloat with cerowrt: <a href="http://www.teklibre.com/cerowrt/subscribe.html" target="_blank">http://www.teklibre.com/cerowrt/subscribe.html</a>