Davidc502- wrt1200ac wrt1900acx wrt3200acm wrt32x builds

I have the same issue too with OpenWrt SNAPSHOT r10726. I just got gigabit internet recently. I thought my router's processor is not strong enough for gigabit SQM, so it's limited to 4 - 500Mbps. I hope it's just the software, not hardware.

I'm pretty sure it is just a software issue because on the current stable OpenWRT 18.06.4 firmware, I can set the traffic up to 700-850Mbps with fq_codel/Cake. I'm wondering what can limited the download speed in the SQM setup?

1 Like

So, in my point of view, if you want to build ALL the packages and maybe you keeps a server and provides the download services to others, you may need to keep these configs. Otherwise it may not be necessary for you.

RPC call failed with error -32002: Access denied
  at ClassConstructor.handleCallReply (http://192.168.1.1/luci-static/resources/rpc.js:8:12)

I get an error after installing luci-theme-rosy

Curious if it's an issue with the move to the 4.19 kernel that hasn't been noticed yet. Some performance regression maybe? Makes me wonder what the hell ever happened to a OpenWrt 2019 release, there is still nothing official and it's Q3.

I also noticed that the download speed wifi on WRT32X is slower and the SQM is not enabled.

I have a Linksys WRT32X, on r10307. When I try to upgrade to the latest build via the WebUI, it gives this message. Should I force upgrade?

Do you have Openwrt on both partitions?

If you do, then as long as you have the right sysupgrade bin, it should not be a problem to force.

Hi guys, i discover an issue recently.

Seems like peak 5G wifi speed dropped twice in latest releases, now i only got 250Mbps by iperf3 sitting next to router (it was 450Mbps before)!
As i see in statistics, this issue coming into mid-July, i just don't mention it before.

In fact, i don't sure it's firmware-related, maybe it's another hug from always-buggy Killer drivers, so let me investigate deeper.

But the question - did anyone else mention it as well?

Hello all,
I use the version proposed by Daniel Petre, SuperWrt works well on wrt1900acs v2.
SuperWRT SNAPSHOT r10865-c3a78955f3 / LuCI Master (git-19.238.65398-f8e30d5)
Kernel Version 4.19.66


The only problem I see on the wi-fi side is not correctly displaying channel 40 ...

Details about this problem can be found here!

@davidc502 you encounter these issues on your firmware version?

You know how weird it is, on wdr3600 rev 1.5, I don't encounter this issue of displaying 5Ghz channels..

1 Like

I'm not on latest david's snapshot and the 5ghz's channel 40 is correctly displayed, don't know if that's the same on latest.

comcast xfinty the normal build works but your build every time i try dount work

1 Like

Hello,

Has anyone had any issues with Adblock (3.8.2-1) not working with the latest release? My runtime information is blank and am not sure what I am missing. I'm using the defaults of dnsmasq, uclient-fetch, and have libustream-openssl installed.

Just downloaded latest firmware for WRT3200ACM and tried to set up openvpn. The OpenVPN service starts, and then continues to start again and again non-stop. Not sure what is causing this. The logs do not provide any info:

Snippet from System Log

Googled the error and it came up with this:
https://www.sparklabs.com/support/kb/article/error-socket-bind-failed-on-local-address/

EDIT:
Follow didbot's advice posted below mine

Best luck

1 Like

Please don't do it! The config check is intentional, e.g. new mandatory parameters and omitted source sections ... just follow the log message and re-install with the "--force-maintainer" opkg option.

1 Like

Ok
I'm not on last release so i didn't try none of those.
So, will just follow last instructions, reinstall & reconfigure
ty dibdot for the advice

Thanks, but this is a symptom of the issue. The first time openvpn starts, there is no error because it starts up successfully. OpenVPN is caught in some kind of startup loop.

The error starts to show up in the system log when the OpenVPN service tries to start up the 2nd, 3rd, 4th time(and on and on), because openvpn is already bound to that port from the first time when it successfully started.

Are you using an old config or did you start from scratch?