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

[Sebastian Moeller <moeller0@gmx.de>]

Ho Toke,

> On Jun 13, 2018, at 15:24, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
> Pete Heist <pete@eventide.io> writes:
> 
>> Trying one thing at a time, as legacy_rates=‘1’ didn’t do anything
>> noticeable, which is not surprising when we probably don’t have many
>> ‘b' devices connecting. We hit 4.9s ping times this morning, good
>> work. :)
>> 
>> Even though isolation couldn’t be turned on in the admin interface
>> (because it says it can’t do it when bridging to a VLAN, for some
>> reason), I was able to enable isolation for both SSIDs and it still
>> seems to work, so that’s the change as of now:
>> 
>> wireless.ap0_1.isolate='1'
>> wireless.ap0_2.isolate=‘1’
>> 
>> Before I could ping between clients, and now I can’t, so apparently
>> isolation is doing what it should. The next test will be tonight.
>> 
>> I’m still waiting for the digging / cabling project to happen, which
>> is what I expect to bring the biggest benefit. Again, that will add a
>> new cabled AP which will serve as a gateway for cabin 12 and split
>> cabins 12 and 20. This should also improve the signal to 12 vastly,
>> which is one of the most loaded APs and currently only has RSSI -71 /
>> MCS 5 or 6 to its parent AP, now that the leaves are full on the
>> trees.
> 
> How to improve WiFi? Run cables! :D

	Just consider this to be a cheap* way to create a favorable RF environment for the signals ;)


Best Regards
	Sebastian

*) arguable cheaper than cleaning the fesssnel zoe of the wifi link and putting a faraday cage around it




> 
> -Toke
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast