[Cerowrt-devel] cerowrt dev 3.8.13-7 released

[Cerowrt-devel] cerowrt dev 3.8.13-7 released

[Dave Taht]

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

And is at:

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

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

Re: [Cerowrt-devel] cerowrt dev 3.8.13-7 released

[Steven Barth]

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

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

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/
>
> 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
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

Re: [Cerowrt-devel] cerowrt dev 3.8.13-7 released

[Dave Taht]

[-- 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 --]

Re: [Cerowrt-devel] cerowrt dev 3.8.13-7 released

[Steven Barth]

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

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.

I haven't heard about TOS inherit until now either and this am not sure 
how it can be setup on Linux.


On 12.06.2013 09:37, Dave Taht wrote:
> 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 
> <mailto: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
>
>     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
>
>     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/%7Ecero2/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
>
>
>         _______________________________________________
>         Cerowrt-devel mailing list
>         Cerowrt-devel@lists.bufferbloat.net
>         <mailto:Cerowrt-devel@lists.bufferbloat.net>
>         https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>     _______________________________________________
>     Cerowrt-devel mailing list
>     Cerowrt-devel@lists.bufferbloat.net
>     <mailto:Cerowrt-devel@lists.bufferbloat.net>
>     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: 8153 bytes --]

Re: [Cerowrt-devel] cerowrt dev 3.8.13-7 released

[Dave Taht]

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

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

>  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.
>
>
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.


> I haven't heard about TOS inherit until now either and this am not sure
> how it can be setup on Linux.
>

it's just part of the ip tunnel line, wherever that gets called... example:

ip tunnel add he-ipv6 mode sit remote 72.52.104.74 local 172.20.26.36 ttl
255 tos inherit

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.


>
>
>
> On 12.06.2013 09:37, Dave Taht wrote:
>
> 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
>>
>> 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
>>
>> 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/
>>>
>>> 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
>>>
>>>
>>>  _______________________________________________
>>> Cerowrt-devel mailing list
>>> Cerowrt-devel@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>>
>>>
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> 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: 9549 bytes --]

Re: [Cerowrt-devel] cerowrt dev 3.8.13-7 released

[Ole Troan]

Steven,

> 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.

out of curiosity, is this SADR as described in http://tools.ietf.org/html/draft-troan-homenet-sadr-00?

cheers,
Ole

Re: [Cerowrt-devel] cerowrt dev 3.8.13-7 released

[Steven Barth]

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

Hi Ole,

it sounds similar, however its probably a more simplified version for now.

As we have DHCPv6-PD as the only officially integrated way of receiving 
prefixes from upstream routers (and that doesn't really allow to assign 
prefixes to a specific router) - and all other methods are either static 
configuration or point-to-point tunnels we currently don't differentiate 
between different routers on the same upstream-interface.
That means we have one routing table per upstream interface.

However if anyone is to integrate something like OSPF protocol handlers 
into netifd which allows to associate source prefixes with routes this 
will probably be added. For now we just wanted to be as compliant as 
possible regarding RFC 6204 and 6204-bis12 and we need the source-based 
routing for generic multiwan and to send out the ingress/egress policy 
failed stuff.


Btw. we backported the new IPv6-stack to Attitude Adjustment as well:
See 
<http://wiki.openwrt.org/doc/uci/network6#features>http://wiki.openwrt.org/doc/uci/network6 
for our current status, list of features and so on.


Cheers,

Steven



On 12.06.2013 11:38, Ole Troan wrote:
> Steven,
>
>> 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.
> out of curiosity, is this SADR as described in http://tools.ietf.org/html/draft-troan-homenet-sadr-00?
>
> cheers,
> Ole


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

Re: [Cerowrt-devel] cerowrt dev 3.8.13-7 released

[Ole Troan]

Steven,

> it sounds similar, however its probably a more simplified version for now.
> 
> As we have DHCPv6-PD as the only officially integrated way of receiving prefixes from upstream routers (and that doesn't really allow to assign prefixes to a specific router) - and all other methods are either static configuration or point-to-point tunnels we currently don't differentiate between different routers on the same upstream-interface.
> That means we have one routing table per upstream interface.

right, as long as you also install RFC4191 MSR routes into the correct table per upstream I think you'll have the exact same behaviour as described in the draft.

> However if anyone is to integrate something like OSPF protocol handlers into netifd which allows to associate source prefixes with routes this will probably be added. For now we just wanted to be as compliant as possible regarding RFC 6204 and 6204-bis12 and we need the source-based routing for generic multiwan and to send out the ingress/egress policy failed stuff.

Markus has done that in the IETF homenet project. but the Linux multiple routing table support either needs to be extended for full support, or routes must be duplicated among tables.

> Btw. we backported the new IPv6-stack to Attitude Adjustment as well:
> See http://wiki.openwrt.org/doc/uci/network6 for our current status, list of features and so on.

splendid! really good to see progress on IPv6 support in openwrt.

cheers,
Ole

Re: [Cerowrt-devel] cerowrt dev 3.8.13-7 released

[Steven Barth]

Ole Troan <otroan@employees.org> wrote:
>
>right, as long as you also install RFC4191 MSR routes into the correct
>table per upstream I think you'll have the exact same behaviour as
>described in the draft.
Good. Yeah we do. we turned off kernel-side RA handling for similar matters for a while and added user-space RA-handling code to the dhcpv6-client.


>splendid! really good to see progress on IPv6 support in openwrt.
It was about time finally. ;)


Steven