WiFi development was abandoned when Davidc was building.
Try @SkewedZeppelin examples, I have pretty stable wifi on my 1900ACS V2. As far as EOL, not by a long shot. These are still very robust, capable wired devices. You can source a reliable WAP at a reasonable price.
Performance using DSA went down a bit, this is a disapointment since if anything performance should improve over time. No idea what upstream Linux is thinking if they are putting 'features' in that hurt performance. Other than that I love my WRT32X, it's perfectly stable and very fast for my 500/35 Mbit cable, SQM Cake gets A+ bufferbloat/A+ quality, USB 3.0 SSD gets 110 MB/s read-write over Samba, adblock, nftables, etc. all working great. I don't know what other targets that can achieve this speed. 5GHz wifi is decent for me, but I also have a U6-Lite (wifi 6 ap) plugged in sitting in a more central location of my house. Wifi 6 is faster and lower latency anyway.
I don't know any other target that is this stable and have a CPU fast enough for all that.
I consider these targets EOL in the sense that they are over 5 years old and no longer retail. We really should have better options these days, but we don't. If Ath11k ever works then maybe that (RAX120 or similar?). Otherwise it's move up to a R5S and seperate 2.5Gbe switch along with U6-Lite combo, but that setup is... cluttered. Who knows. WRT32X is good for the time being.
Thanks
Looks like I'm digging out the 1900ACS. I agree these are good machines. Too bad we weren't given full access to the radios.
Also I'll look into the adding a WAP.
Thanks...I get the picture now.
First of all, thank you so much for this custom build, I've been able to compile the 20220915 version, the only thing that I want to ask is:
Do you've applied the CPU frequency scaling driver for mvebu to your custom build??, if the answer it's no, can be applied at the compiling time without problems? (there is a kernel 5.10 version available at the author's dropbox
EDIT: @solidus1983, the patch that you comment in this post is the same that I've commented?
Slightly off-topic, but very straight forward question on the wifi performance:
Is the OpenWrt Wifi performance (especially 5Ghz) for WRT32x
a) better
b) worse
c) the same
as on the OEM Linksys (venom) firmware?
Thanks!
Worse. Almost all open source firmwares have worse wifi than oem due to drivers. The MediaTek devices are apparently about on par.
Hi all,
I installed the r20681+10-5110cf7ebd on my 1900acs.
Excuse me for the OT, but tomorrow my ISP will enable my FTTH line, and i'm trying to get all ready for testing it while the technician will be there.
I'd like to ask for some help
The ISP gave me this params for the router configuration:
VLan: 835(data)
VLan: 836(voice)
Protocol: PPPoE
Encapsulation: LLC
NAT: enabled
COS data: 0 (IEEE 802.1 P)
COS voice: 5 (IEEE 802.1 P)
I changed the wan interface to wan.835 (VLAN 802.1q) and moved, after the picture has been taken, the wan6 to wan.835 as well.
Do i also need to add a wan.836 interface for the voice?
Eventually, the 836 interface has to be routed in any way to the lan ports?
There's anything more i need to do to make, at least, it connect to my new line and let me "surf"?
Thanks a lot to anyone who could help me clarify this
And again, sorry for the OT
Wouldn't be around here someone with a pre-fw4 image/sysupgrade for the wrt1900acV1 (mamba) ?
I've been using your build for a while after upgrading from a very old LEDE firmware but I really need banIP .
Thanks anyway for your work, your build is really non nonsense and very stable.
My 1G/200M ftth line has been enabled.
And this is the speedtest result:
190 M download, 190 M upload
Really disappointing.
Is there anything i could have messed on the router side?
irqbalance -on
Software flow offloading-on
Packet Steering-on
This is my network config
cat /etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'redacted::/48'
option packet_steering '1'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '192.168.2.1'
config device
option name 'wan'
option macaddr 'redacted'
config interface 'wan'
option proto 'pppoe'
option ipv6 'auto'
option device 'wan.835'
option username 'user'
option password 'pass'
config interface 'wan6'
option proto 'dhcpv6'
option reqaddress 'try'
option reqprefix 'auto'
option device 'wan.835'
i'm really sad
Not sure what you mean by packet steering, but software offloading is incompatible with SQM. Something is wrong for you, I can get 500/35 Mbits even with SQM enabled on my WRT32X with OpenWrt 22.03. Keep in mind Irqbalance will not help this, there is no multi-CPU DSA it'll stay on CPU0 best I can tell.
/etc/config/network
config globals 'globals'
option packet_steering '1'
Thanks and I saw your post on the other thread but what is the purpose in this? I've been using my mvebu (WRT32X) for years and it's been perfectly stable without doing this. Why would the OpenWrt project not just enable it for this target if it's actually needed?
commit outlined the default and why on a mvebu target you would probably want to enable. Personally, on my build I am using MQPrio with the queue restriction patch removed, running fine, YMMV.
Thanks, I think the ultimate issue is that multi-CPU DSA is needed. The move to DSA without it always seemed very odd, even though it's from upstream Linux, because it lowered performance for all of OpenWrt devices.
I find it hard to attribute decline in throughput specifically to DSA change, there have been a lot of mvneta changes with kernel version bumps. Unless you have an ISP feed in the neighbourhood of a symmetric 1G/1G link, the multi-cpu-port DSA support should be a non-issue. And if you do, maybe the PR allowing support might still build.
Yeah, I think there's something wrong with my line, which is not related to the build or router config
But I was trying to check everything, just to be sure
Thanks
Fair enough, but there seems to be no disputing a performance hit with DSA. It's not an issue for me and I've had good experience and perfect stablity on 22.03, but I saw threads showing DSA is even worse on the ipq806x.
Nevertheless I went ahead and enabled packet steering on my WRT32X under Network > Interfaces > Global network options. Don't see any difference yet in a quick speedtest but I'll keep testing it out.
After a month of trying to upgrade my WRT3200 from the Davidc502 r13342 snapshot...
I gave up. Tried all the suggestions on here. WiFi plain and simple is broke after this build. I dug my WRT1900acs out and gee what do you know? As reported above upgrading to 22.03.0 is stable!!
I played around with Divested, and PureFusion. Both stable WiFi and speeds. Nice builds!
Right now I'm running a basic 22.03.0-rc6 using packages I like from the other 2 builds. And added adblock, dnscrypt-proxy2, bcp38, dashboard, etc.
I even added luci-app-attendedsysupgrade. It took the installed packages and my settings and made an upgraded image on the other partition. Stable so far.
I enabled packet steering...and it seems as if WiFi speed tests are more consistent. And now as good as my WRT3200 (running Davidc502 r13342)
As far as my WRT3200 vs WRT1900acs. It reboots faster and I haven't given up. I'll keep trying to get it to work. But for now I'm happy as heck to have a up to date stable build with decent WiFi.
Wonder if I should dig my WRT1200 out of the closet and upgrade it? LOL
After lot of fighting with my ISP, they came and made some checks on my ftth 1gb line.
All was good ISP side, and with the ISP's modem and the ISP's notebook they made some speed tests with results over 800 mbps download speed. Using my 1900acs they weren't able to get past ~300/400 Mbps, even with the stock firmware we had same results.
The connections is, sadly, made with ppoe
I can't get what's going wrong with my linksys.
[OT]
Beginning to think about moving to a x86_64, wich could also get me ready for the switch to a 2,5g/500m line.
But I'm totally noob about this and dunno what should I aim to, in terms of hardware and software, considering European market availability and affordability.
[/OT]