Oh, you were asking about which software version is being used. I'm running OpenWrt 21.02.0-rc3, r16172-2aba3e9784.
After updating the opkg lists, I do not have the "wireguard" or "kmod-wireguard" packages availble. Besides the luci-i18n packages, the only ones I have related to wireguard are luci-proto-wireguard, wg-installer-client, wg-installer-server, wg-installer-server-hotplug-babeld, wireguard-tools, luci-app-wireguard.
So this is kind of strange. Anyone know why they're missing?
I suppose this should be used in addition to the other command but it seems the path doesn't exist? I realize the path for the other command doesn't exist either. Do these commands really work then?
Thank you very much for the link, not sure how I missed that.
Yes, I'm currently using wolfssl, although I haven't had the time yet to test it thoroughly.
But the mesh has been up for two days now and appears to work fine so far.
Is there any current reason why one would want to use openssl instead?
So for unknown reason kmod-wireguard has suddenly appeared in the package list after it was missing for a few days. But the actual wireguard package is still absent and I guess that is the package containing the wg binary so I can't run it without installing it. Anyone know what's up with the missing wireguard package? I'm on 20.02 rc3.
Is it fair to say since OpenWrt 21.02 is using kernel 5.4 that exFAT support is "native" now with the new drivers built-into the kernel? I'm getting 120 MB/s read-write on my USB 3.0 drive with minor CPU impact (no noticible drop with SQM cake 500mbit, adblock, etc.), this speed maxes out gigabit LAN. Just wondering if the kmod-fs-exfat is using this, thanks. EDIT: using a WRT32X.
nice, so now another hidden helpful gem for routers was identified in 21.02 (at least I have not seen this in announcements so far). So, now there is native exfat and Airtime fairness queue management for MT76 and Atheros.
I run across many wireless problems till uncheck Keep settings and retain the current configuration while installation firmware.
I don't why, but It proceeds former error characteristic. Likewise, I did uncheck before installing then used a while. Cleaning former config should prefer.
I'm a RC2 user a while and my comparisons between RC3 and RC2. Cause need native Wi-Fi 5
It's massive update after RC2!
It's contain great Wi-Fi 5 development ever!
Thank you.
Also, I should say this is not perfect stability but the stablest Wi-Fi till now!
Openwrt core
Great development, Ping minimized even cable connection
Soo smooth
Ethernet
Ports works
Not recognized any problem
Wi-Fi
Not duplicate propagation
Not droping suddenly
Speed limit increased
(I didn't test maximum of the device capacity, but getting similar cable.
I would rather test it, if you show a guide. Don't know how)
Ping issue looks good
Leds brightness
Alongside all this, all indicator leds dimmed in RC3. Just usb led bright normally others is dimmed in RC2 .
In RC3 all LEDs dimmed which cannot see in daylight but except USB indicator in RC2.
I was edited led configuration in RC2, just at last LED lighted up as much as USB led.
Similarly, I added below on RC3 via LuCI.
config led
option name 'Refreh'
option sysfs 'blue:wps'
option trigger 'heartbeat'
It is bright as much as RC2's usb led heartbeat and Defaultstate. Notable in daylight.
Nowadays, my VDSL line little problematic.
I'd rather db gain getting more speed. But it's causing enormous instability.
Yeah, it's not a single side problem. This instability affects everything, even Wi-Fi ping,
Even sometimes LuCI refuse my login on Firefox (trivially) [but chromium works same moment so interesting] Wi-Fi dropping suddenly. But this is trivial. I'll mention my ISP.
I get mesh authentication errors in my system log with wolf. Are you using the full wolfssl library or wolfssl-mesh. I tried the wolfssl-mesh library when I got the errors
I've been using the full wpad-wolfssl, because I need 802.11r, k, and v support.
I can't say that I've seen any mesh auth errors.
What encryption did you use on the mesh?
Last time I checked luci only allowed sae and no encryption on 802.11s, you can use psk2 as well though if you configure it manually.
In my tests sae performed quite a bit worse than psk2, so that is what I'm currently using.
Notwithstanding the errors you see in the logs, Is the mesh working or not?
I have obveserved errors like MESH-SAE-AUTH-FAILURE even if the mesh works normally and explained why I think this is happening here but I got no confirmation from anyone more technically involved yet.
WRT3200ACM, freshly installed 21.02 rc4, almost vanilla, from scratch :
Working great since 1 hour.
To make the wifi appear, I had to :
-well, remember my previous config in my backup (/etc/config/network)
-Wifi0 and wifi1 refused to start. So I followed instructions below.
Indeed, at least in my country Wifi0 and Wifi1 are disabled by the firmware, if they are set to country 'XX' which is different from the 'US' for Wifi2, that cannot be changed. This is because DFS is checked through the antenna used by Wifi2. For US, there might be no such issue, as I understand.
After that, on 5Ghz, with 2 different devices, I get 350-450Mbps Down/Up, with peaks at 500Mbps, which I find already nice.
No drops experienced.
I had similar results with the last Davidc build.