Re: [Make-wifi-fast] mesh deployment with ath9k driver changes

[Pete Heist <pete@heistp.net>]

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


> On Jul 9, 2018, at 7:17 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
> 
>> On 9 Jul, 2018, at 5:20 am, Aaron Wood <woody77@gmail.com> wrote:
>> 
>> Do the AP-to-AP links use the same packet scheduling as the AP-to-STA links? (especially the prohibition on aggregation for VO, which seems counter-productive on a backhaul link).
> 
> I believe they do, since they go through the same type of MAC grant process.  To avoid that, the AP would need to ignore the traffic class when assigning backhaul packets to queues.

I’m also almost sure of that. However, since I set all DSCP values to 0 in PREROUTING, most traffic going over the backhauls is now best effort, and I haven’t been able to detect a change in ping times to the APs. The change was made July 5 around 10am and, for example, this is probably our most challenged AP: https://www.drhleny.cz/smokeping/Cabin12.html <https://www.drhleny.cz/smokeping/Cabin12.html>

I still think making backhaul traffic best effort makes sense. In my point-to-point tests, I sometimes do this using IPIP tunnels, so the DSCP value of the inner packet is hidden from the WiFi stack, but the value is still maintained after it passes through the tunnel. A drawback of this is that the MTU is shortened by 20 bytes.

Tomorrow I’ll be setting up a 5GHz point-to-point backhaul link for Cabin 28 (higher standard cabins), so I expect a significant change there.

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