Dear Users
Please one question . Actually firmware openwrt for model WRT3200acm support technology MU-MIMO? Or only with stock firmware?
Only Stock firmware. But before you go, I would ask my self some questions about it first.
- Do you have clients that can utilize MU-MIMO? Not all devices can.
- Do you have 2 or more clients in the same room needing excessive bandwidth? Reason being MU-MIMO will only serve multiple streams to clients in the same room. This means if you have clients in different room demanding bandwidth then MU-MIMO makes no difference.
- 4 device limitation for MU-MIMO. This means if you have 2 or more devices in the same room demanding bandwidth OR 2 separate rooms with 2 devices in each room demanding high bandwidth.
Really, a vast vast majority of consumers aren't going to notice any difference with MI-MIMO, so if you're thinking of jumping ship for that technology you might be a little disappointed.
4 Likes
I have not had this kind of trouble, but I'm not using sshd as my primary server. TLDR for the devcrypto engine: DES, AES-CBC works well; everything else is dubious, use
CIPHERS=DES-CBC, DES-EDE3-CBC, AES-128-CBC, AES-192-CBC, AES-256-CBC
ECB should be working, but that problem with forks may still be an outstanding issue. ECB's use is pretty much restricted to openssl prng, and you won't gain any performance by using /dev/crypto there, as it is used in tiny blocks. CTR-mode could be useful, but I have doubts that cryptodev's auto-IV handling (COP_FLAG_WRITE_IV) is working with anything but CBC (it could be disabled with a small patch).
Try that CIPHERS line above and tell me if it works for you.
https://dc502wrt.org/snapshots/r10512/
New build incoming, @davidc502? 
Did you get your sshd working? That error message was only shown to me with digests enabled. Disabling ECB is a good idea on its own, but it maybe best to check the output of
openssl engine -t -c -pre DUMP_INFO
This will tell you exactly what algorithms are enabled--just in case there's an error somewhere else. You may add devcrypto to the end of the line if you don't like the error messages for other engines, but looking at them all may show otherwise hidden surprises.
I wasn't going to say anything, noticed this morning that folder. However give davidc502 some time.
Great explanation. I think the same thing. It is impossible for everyone at home to use the band excessively at the same time. But explain one thing, it seems that they have already released the source code for the MU-MIMO feature. In the current DD-WRT firmware the SU-MIMO and MU-MIMO enabled in the 5Ghz band appear. You can see the features through the great android app named Analiti (playstore). I believe that in the future these resources will be added in OPENWRT. Thank you
1 Like
Yeah, I already built r10512, but the router had some serious issues, so I trashed it. I'm going to try another build today.
4 Likes
I think the issue was with the new Ubuntu machine. The exact same thing happened yesterday. After the router came up I could ping 1.1.1.1 but after 5 seconds it stopped pinging, and I couldn't ping the gateway either. I physically looked at the router and wifi was up and all the switch lights were blinking. Because the machine could not get to the router, I assumed the build was faulty. Today with a new build the exact same thing happened. I picked up the router and all the lights looked good, so I went over to a Windows machine and there were no problems going to the internet or LAN. After a few minutes I made my way back to the Linux machine, and suddenly it was pinging 1.1.1.1. For some reason there is a network delay on this new Ubuntu station, and I have no idea why.... Seems to be it wouldn't need DHCP again because the router just rebooted.
Long story short, I'm going to observe this build for a couple more hours and if all is good it will be uploaded to the server.
fwiw, I've been running r10512 with a few performance patches for 2 days now without any issues (WRT3200ACM).
1 Like
New builds have been uploaded to the server. We have several kernel bumps and various fixes. However, no changes with the wifi driver.
Kernel version = 4.19.57
WiFi driver = 10.3.8.0-20181210
Build = r10525
This was finally built on the new Ryzen system. Instead of taking over 4 hours (old system) it completed in 1 hour using 12 threads. My first test used 24 threads, and it finished at around 47 minutes and not in half the time. Appears there is diminishing returns dealing with more threads that are thrown at it.
6 Likes
samba isnt working in this build. It keeps crashing even after after i factory reset it.
Went back to previous build and samba is fine
I have the same issue with samba. It doesn't work on r10525.
I have a fix for that was just about to mention it.
to fix this issue create via putty a folder called ipk in /root/
cd /tmp
mkdir ipkthen make fixsamba4.sh
nano fixsamba4.shNow Paste the below into fixsamba4.sh
#!/bin/sh
opkg update
opkg remove --force-removal-of-dependent-packages samba4-admin samba4-client samba4-libs samba4-server samba4-utils luci-app-samba4 luci-i18n-samba4-cs luci-i18n-samba4-en
mv /etc/config/samba4 sambaold
mv /etc/samba/smb.conf.template smb.conf.template.old
wget https://dc502wrt.org/snapshots/r10307/packages/arm_cortex-a9_vfpv3/packages/samba4-admin_4.9.8-1_arm_cortex-a9_vfpv3.ipk -O /tmp/ipk/samba4-admin_4.9.8-1_arm_cortex-a9_vfpv3.ipk
wget https://dc502wrt.org/snapshots/r10307/packages/arm_cortex-a9_vfpv3/packages/samba4-client_4.9.8-1_arm_cortex-a9_vfpv3.ipk -O /tmp/ipk/samba4-client_4.9.8-1_arm_cortex-a9_vfpv3.ipk
wget https://dc502wrt.org/snapshots/r10307/packages/arm_cortex-a9_vfpv3/packages/samba4-libs_4.9.8-1_arm_cortex-a9_vfpv3.ipk -O /tmp/ipk/samba4-libs_4.9.8-1_arm_cortex-a9_vfpv3.ipk
wget https://dc502wrt.org/snapshots/r10307/packages/arm_cortex-a9_vfpv3/packages/samba4-server_4.9.8-1_arm_cortex-a9_vfpv3.ipk -O /tmp/ipk/samba4-server_4.9.8-1_arm_cortex-a9_vfpv3.ipk
wget https://dc502wrt.org/snapshots/r10307/packages/arm_cortex-a9_vfpv3/packages/samba4-utils_4.9.8-1_arm_cortex-a9_vfpv3.ipk -O /tmp/ipk/samba4-utils_4.9.8-1_arm_cortex-a9_vfpv3.ipk
wget https://dc502wrt.org/snapshots/r10307/packages/arm_cortex-a9_vfpv3/luci/luci-app-samba4_git-19.170.41626-1154c41-1_all.ipk -O /tmp/ipk/luci-app-samba4_git-19.170.41626-1154c41-1_all.ipk
wget https://dc502wrt.org/snapshots/r10307/packages/arm_cortex-a9_vfpv3/luci/luci-i18n-samba4-cs_git-19.170.41626-1154c41-1_all.ipk -O /tmp/ipk/luci-i18n-samba4-cs_git-19.170.41626-1154c41-1_all.ipk
wget https://dc502wrt.org/snapshots/r10307/packages/arm_cortex-a9_vfpv3/luci/luci-i18n-samba4-en_git-19.170.41626-1154c41-1_all.ipk -O /tmp/ipk/luci-i18n-samba4-en_git-19.170.41626-1154c41-1_all.ipk
opkg install --force-downgrade /tmp/ipk/*.ipk
/etc/init.d/samba4 enable
/etc/init.d/samba4 startPress CTRL+O and then enter then CTRL+x
now type
chmod +x fixsamba4.sh
./fixsamaba4.shReboot Router After!!!!
After that do not upgrade the packages as its the packages that are faulty not the firmware.
3 Likes
see my reply to SESNut that has the fix.
1 Like
@solidus1983 I tried this, but it didn't work. First, I'd already installed the compressed version ofdns-crypt-proxy v2 so there wasn't enough space available on /root so I did everything in /tmp. I got the following errors during the opkg install:
root@OpenWrt:/tmp/ipk# opkg install --force-downgrade /tmp/ipk/*.ipk
Installing luci-app-samba4 (git-19.170.41626-1154c41-1) to root...
Installing luci-i18n-samba4-cs (git-19.170.41626-1154c41-1) to root...
Installing luci-i18n-samba4-en (git-19.170.41626-1154c41-1) to root...
Installing samba4-admin (4.9.8-1) to root...
Installing samba4-client (4.9.8-1) to root...
Downgrading samba4-libs on root from 4.10.6-2 to 4.9.8-1...
Downgrading samba4-server on root from 4.10.6-2 to 4.9.8-1...
Installing samba4-utils (4.9.8-1) to root...
Configuring samba4-server.
Configuring luci-app-samba4.
Configuring luci-i18n-samba4-cs.
uci: Entry not found
uci: Entry not found
Configuring luci-i18n-samba4-en.
uci: Entry not found
uci: Entry not found
Configuring samba4-client.
Configuring samba4-utils.
Configuring samba4-admin.
Collected errors:
* verify_pkg_installable: Only have 2736kb available on filesystem /overlay, pkg samba4-libs needs 6020
* opkg_install_cmd: Cannot install package samba4-libs.
* resolve_conffiles: Existing conffile /etc/config/samba4 is different from the conffile in the new package. The new conffile will be placed at /etc/config/samba4-opkg.
* resolve_conffiles: Existing conffile /etc/samba/smb.conf.template is different from the conffile in the new package. The new conffile will be placed at /etc/samba/smb.conf.template-opkg.
When I do a df -h to look at /overlay, I get:
Filesystem Size Used Available Use% Mounted on
/dev/root 18.5M 18.5M 0 100% /rom
tmpfs 249.5M 3.3M 246.2M 1% /tmp
/dev/ubi0_1 9.0M 4.8M 3.7M 57% /overlay
overlayfs:/overlay 9.0M 4.8M 3.7M 57% /
ubi1:syscfg 29.6M 368.0K 27.7M 1% /tmp/syscfg
tmpfs 512.0K 0 512.0K 0% /dev
/dev/sda1 28.1G 6.7G 19.9G 25% /mnt/sda1
/dev/ubi1_0 29.6M 368.0K 27.7M 1% /mnt/ubi1_0
Any ideas?
mv /etc/config/samba4 sambaold
mv /etc/samaba/smb.conf.template smb.conf.template.oldthen try again will add the following above to the script
@solidus1983 No such luck for me. In this case, I get the following errors on install:
Collected errors:
* pkg_write_filelist: Failed to open //usr/lib/opkg/info/samba4-libs.list: No space left on device.
* opkg_install_pkg: Failed to extract data files for samba4-libs. Package debris may remain!
* opkg_install_cmd: Cannot install package samba4-libs.
* verify_pkg_installable: Only have 0kb available on filesystem /overlay, pkg samba4-server needs 147
* opkg_install_cmd: Cannot install package samba4-server.
* verify_pkg_installable: Only have 0kb available on filesystem /overlay, pkg samba4-utils needs 64
* opkg_install_cmd: Cannot install package samba4-utils.
I have to run off and start my day, but I appreciate the help. I should mention I'm now doing this after a clean install of r10525, prior to installing dnscrypt-proxy v2 so I should have plenty of space on my WRT1900ACS V2.
Yea makes sense, the physical cores are going to scale much better than the additional the SMT threads, just like Intel HT.
Reading that Samba is broken gonna hold off, I use a 3TB USB 3.0 external drive for storage and Kodi so an important feature for me.
1 Like
What version of hardware do you own? I am concerned about the following line.
overlayfs:/overlay 9.0M 4.8M 3.7M 57% /