Re: [Make-wifi-fast] [Cake] Airtime fairness patch merged upstream, and the Turris Omnia debloated

[Dave Taht <dave.taht@gmail.com>]

Heh. Of all the hackerboards I tried, the odroid c2 was the fastest
and is generally my default target these days.

The "chip" is coming along nicely but lacks network.

The odroid c1 and rpi2 have been the most reliable.

(I'm still looking for a board with a decent toslink port....)

...

I just foolishly tried to update my linksys 1200ac, but... it turned
out the cable modem behind it was acting up and I lost touch with it
(lacking a babel pre-installed)... aha! (/me worms his way through
multiple hops through another modem)

It looks like my default command line, post install is basically:

opkg install luci-ssl luci-app-sqm babeld kmod-sched-cake netperf

The 1200ac still has bug

https://bugs.lede-project.org/index.php?do=details&task_id=294&order=status&sort=asc&order2=severity&sort2=desc

I triggered it with:

root@apu2:~/t# flent -H 172.26.64.1 -t 'isitfixed'
--te=download_streams=12 tcp_ndown

Warning: Program exited non-zero (1).
Command: /usr/bin/netperf -P 0 -v 0 -D -0.20 -4  -H 172.26.64.1 -t
TCP_MAERTS -l 60 -f m   --   -H 172.26.64.1
Program output:
  netperf: send_omni: connect_data_socket failed: No route to host

Warning: Command produced no valid data.
Data series: TCP download::5
Runner: NetperfDemoRunner
Command: /usr/bin/netperf -P 0 -v 0 -D -0.20 -4  -H 172.26.64.1 -t
TCP_MAERTS -l 60 -f m   --   -H 172.26.64.1
Standard error output:
  netperf: send_omni: connect_data_socket failed: No route to host

The way I was dealing with it was with running cake at 900mbit on the
internal ethernet. I guess it's one way around bugs like this.




On Fri, Dec 23, 2016 at 6:51 PM, Aaron Wood <woody77@gmail.com> wrote:
> Excellent. I'll run more tests, and see if I can get some more boxes with
> flent installed. I'm short of test clients, myself.
>
> -Aaron
>
> On Fri, Dec 23, 2016 at 18:29 Dave Taht <dave.taht@gmail.com> wrote:
>>
>> On Fri, Dec 23, 2016 at 6:18 PM, Aaron Wood <woody77@gmail.com> wrote:
>> > On Fri, Dec 23, 2016 at 6:03 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> >>
>> >> The simplest way to verify if you have the airtime fairness stuff is
>> >> to look for a sysfs file named "airtime". The best way to test it is
>> >> to drive more than one wifi device over it simultaneously from a wired
>> >> link, and not through the ISP link.
>> >
>> >
>> > /sys/kernel/debug/ieee80211/phy[N]/ath9k/airtime_flags?
>>
>> yep. there's also a per station one that only a parser could love.
>> Example:
>>
>>
>> ./kernel/debug/ieee80211/phy0/netdev:wlp2s0/stations/04:f0:21:1f:36:e2/airtime
>>
>> I'm getting on a plane to florida in a few hours, but I'm packing a
>> ubntlite with me (as a gift for mom). Sounds like no more debugging
>> required....
>>
>> It sounds like we are on the verge of breaking out the eggnog, and
>> raising a glass... (but I'd like a few more testers first - got a c7
>> anyone?)
>>
>> A merry bloat-free christmas to all, and to all, a good firmware!
>>
>> >>
>> >>
>> >> flent -H device1 -H device2 -H device1 -H device2 rtt_fair_up # example
>> >>
>> >> What is your wifi client presently?
>> >
>> >
>> > Mid 2015 MacBook Pro, very short range (<10 feet).  My test bed is down
>> > for
>> > the evening, sadly.
>>
>>
>>
>> --
>> Dave Täht
>> Let's go make home routers and wifi faster! With better software!
>> http://blog.cerowrt.org



-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org