802.11s mesh appears to not transport TCP/IP even though the mesh
appears up, for commits on master after late September, 2018.
(Steps to replicate at the end of this message)
The output of `iw dev mesh0 station dump` yields similar results for
working and non-working builds, along the lines of:
see what happens when you're too savy on few lines of code that will
not reduce image size a bit in the selected target...do it proper and
have each device have it's own profile
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lis
Op zondag 3 februari 2019 om 14:54 schreef Felix Fietkau :
On 2019-02-02 19:08, Stijn Segers wrote:
Hi Felix,
I built 18.06 HEAD with your 2019-01-30 bump, and with the
mt76-disable-edcca.patch applied. That seemed very stable (up since
30/01 evening, very high throughput - never seen an
On Wednesday, January 23, 2019 6:54:11 PM CET Christian Lamparter wrote:
> On Wednesday, January 23, 2019 2:26:20 PM CET Koen Vandeputte wrote:
> > Hi Christian,
> >
> > fwiw, I've been using every musl git bump up to this release on my
> > devices offshore. It has been running on ~65 devices cov
On 2/4/19 4:20 AM, w...@reboot.ch wrote:
Hello Jeff, thanks for adding GL.iNet AR-300M-Lite !
I can't test it as it's not yet merged into master I think,
I'm currently using GL.iNet AR-300M settings with a GL.iNet AR-300M-Lite box
and USB is not working, lsusb shows nothing.
Wondering if it's
done & verified.
Thanks Ben!
Koen
On 03.02.19 04:27, Ben Greear wrote:
Here are the sha-sums, the 002 version changes to 003.
If someone could update openwrt to use them I'd appreciate it. Changelog
is at the bottom. I am hoping this resolves the crashes related to
rate-ctrl.
9980
6685623e
On 13.01.2019 23:49, Tomasz Maciej Nowak wrote:
This is aftermath of partially failed series [1].
When I was searching for ways to upgrade of bootloader on existing
OpenWrt installations, I noticed that it'll be difficult to add this
feature within existing code creating x86 target images. I deci
