Are you speaking about SQM or OpenWrt?It's also super unreliable unfortunately.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Are you speaking about SQM or OpenWrt?It's also super unreliable unfortunately.
Could you provide some context as to why you think that?QOS in general...
Also curious.Could you provide some context as to why you think that?
If I may ask, what version of RouterOS did you use? And what type of queues did you use?Unless things have changed, QOS uses inaccurate methods to schedule packets - in some cases it's applied per connection and not per IP. I ran it in an office of around 10 people and had very mixed results and got the same feedback from others trying to do the same thing. I've used Tomato, DD-WRT and RouterOS. The results were good for some things but it borked other apps.





Around 2010-2011 I would agree. I could label it as 'clunky'. I do feel the price of MT hardware and Queue management alone is not bad currently. We wont talk about other stuff of MT but Queue management is not bad, PfSense does the other stuff.It's been a while... like 10 years, so it's very likely things have improved dramatically. My experience at the time though was meh...
Did you come right with your TP-Link c20 v5?I want to upgrade to 19.xx due to some performance enhancements they made for 5ghz WiFi.
I'm on a snapshot at the moment, device info here:
[OpenWrt Wiki] Techdata: TP-Link Archer C20 v5
openwrt.org
Will I be able to upgrade to the latest stable release from my snapshot?
I want to upgrade to 19.xx due to some performance enhancements they made for 5ghz WiFi.
I'm on a snapshot at the moment, device info here:
[OpenWrt Wiki] Techdata: TP-Link Archer C20 v5
openwrt.org
Will I be able to upgrade to the latest stable release from my s
When some ”contributors” on the OpenWRT forum say a router isnt supported because of the SoC, I laugh. The guiding principle of GNU/Linux and OpenWRT’s toolchain is to be patched. So any device that supplies drivers for the Router can be patched. In this case it’s the WiFI SoC dhipset.@andreasrza
I think I did yes; Was running openWRT nicely, but a few months later I upgraded to a gigabit router.
@andreasrza
I think I did yes; Was running openWRT nicely, but a few months later I upgraded to a gigabit router.
Still have the TP-Link here somewhere stashed in a box in the garage.
Still have the TP-Link here somewhere stashed in a box in the garage.
Brilliant!When some ”contributors” on the OpenWRT forum say a router isnt supported because of the SoC, I laugh. The guiding principle of GNU/Linux and OpenWRT’s toolchain is to be patched. So any device that supplies drivers for the Router can be patched. In this case it’s the WiFI SoC dhipset.
i have patched a the source-code on GitHub. I have also released v21.02.1 for the TP-Link C5 v4. The firmware includes support for exroot USB devices. So, you could essentially plug in a 8gig USB thumb drive in the back of the router and never worry about resources again. It essentially acts as part of the routers resources.
have a look: https://github.com/andreasrsa/OpenWRT-Archer-C5
My GitHub
Hi, I have a hAP ac2 with OpenWrt for sale. PM if you are interested.I'm so sad now I didn't buy one of those fallen off the back of the truck Vox MikroTiks on Takealot that time to have a second one as an AP in the lounge.
Never realized there was a decent use for a Fortinet!!!I ported/built a OpenWRT image for a Fortinet FAP321C.
EOLed 2018. Found one in the trash, still working today. 3x3 MIMO, both 2.4 and 5GHz.
Gigabit phy with POE.
OEM firmware was useless, wanted a separate wireless controller.
The power of Open-Source, boet.Never realized there was a decent use for a Fortinet!!!