Firmware 3.022 on GL-B1300 is OpenWrt Chaos Chalmer 15.05.1 r48067

Any plans to update to 18.06.02?

Is there and updated imagebuilder somewhere?

We have covered this in other threads. The B1300/S1300 routers are dependent on the Qualcomm build environment which is currently stuck on 15.05.1, nothing that GL can do at the moment about upgrading to a later OpenWRT version.

As soon as Qualcomm updates their build environment, GL will put up an update shortly after.

If you want you can build your own 18.06.2 following the OpenWRT build guides, but you will loose a lot of wifi performance since it won’t contain the Qualcomm closed source drivers.

1 Like

Ok, thanks for your answer.

That is QSDK? Is it like a copy of openwrt at a specific time (15.05.1 tag)?

I suppose that nobody will provide a compiled driver without sources to do not loose perfomance. Negative point for Qualcomm.

Yeah its the QSDK. They basically took 15.05.1, added their kernel modifications, various changes and placed their closed source optimized drivers.

The drivers are blobs and not compiled by GL at all, just used in the final firmware, dropped in.

Asus has had similar problems with Broadcom were they don’t even release kernel sources :frowning:

It’s mostly the WiFi drivers - QSDK has this sorted already - both for Wave1 and Wave2 - and the MESH stuff.

The ath10k drivers for IPQ40xx - still a bit under development, and Wave2 features are needed a lot of work - and no MESH.

Smart choice by the GL-iNet team to stick with QSDK for now…

Not that I disagree that Qualcomm’s proprietary drivers may not have advantages over the open-source options, but IPQ4019 under ath10k-ct supports mesh, including 802.11s.

        valid interface combinations:
                 * #{ managed } <= 16, #{ AP, mesh point } <= 16, #{ IBSS } <= 1,
                   total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
mesh8     ESSID: "SoC"
          Access Point: 30:23:03:xx:xx:xx
          Mode: Mesh Point  Channel: 36 (5.180 GHz)
          Tx-Power: 23 dBm  Link Quality: unknown/70

Now there are some other “challenges” with the open-source, Ethernet/switch support on the ipq40xx platform. Even DSA/qca8k isn’t even close to resolving these (even on Linux master at this time), including flexible handling of multiple MACs (the hardware kind) and handling of VLANs. The SoC works great for “home-router” use where one MAC handles “WAN” and the other handles “LAN”, but can be a challenge for advanced users with multiple VLANs.

That said, I’ve got three, IPQ4019-based, triple-radio devices here and would seriously consider the Convexa if I needed another router.

There’s some issues with the ethernet switch element, and I’m think it might intersect with the Wave2 and Mesh items for WiFi.

DSA is a thing unto its own, and many switch elements can have issues with this set of API’s and their own special sauce for flow offloading.

Keep in mind that DSA has deep roots into a specific vendor’s switch chip - Marvell Linkstreet…

Not make excuses for Qualcomm - just saying they do have their priorities with that chipset, and multiple VLAN’s (outside of the typical one that can be static in the build) is likely not the highest priority.