It is not missing:
root@OpenWrt:~# ls -1 /usr/lib/samba/vfs/
btrfs.so
cap.so
catia.so
crossrename.so
fake_perms.so
fruit.so
io_uring.so
offline.so
readonly.so
recycle.so
shadow_copy2.so
streams_xattr.so
widelinks.so
xattr_tdb.so
I don't know why it breaks the setup for you.
The 23.05 image was one with a customized package list. As i threw it away a new is build now to be inspected. We'll see
Successfully upgraded mine from rc1 to rc4 in my Mi router 4A GE, however the speed in 5G wifi is still not fix...This happened since 21.02 and until now it's still not fixed...my ISP can go 400Mbps but the 5G wifi can only go 250Mbps even though my devices can handle beyond that, the only fix i can find is going back to 19.07 build by @db260179 which is outdated
i receive mr90x today i will make feedabck if i can flash the openwrt firmware 
I would guess BW means BandWidth...
I added an extra case for this in the current server, should work now. I'll implement something more generic later, it's a bit hard to keep track of all packages changes. Sorry for the inconvenience.
And a new 23.05 custom image and some new tests did not yield an answer.
Listing the shares locallly on the router with smbclient works, so does making a connection from a Debian 12 smb client (Gnome), but connecting from any macOS client is to no avail. A test with the default smb.conf.template and package example UCI samba4 file with just one test share could be connected from macOS either. The samba log for the macOS (13.6) client shows:
[2023/10/10 16:04:31.575213, 3] ../../source3/smbd/smb2_oplock.c:1408(init_oplocks)
init_oplocks: initializing messages.
[2023/10/10 16:04:31.576523, 3] ../../source3/smbd/server_exit.c:229(exit_server_common)
Server exit (failed to receive request length)
[2023/10/10 16:04:31.577020, 3] ../../source3/smbd/smb2_oplock.c:1408(init_oplocks)
init_oplocks: initializing messages.
[2023/10/10 16:04:31.577424, 3] ../../source3/smbd/smb2_negprot.c:1110(smb2_multi_protocol_reply_negprot)
Requested protocol [NT LM 0.12]
[2023/10/10 16:04:31.577541, 3] ../../source3/smbd/smb2_negprot.c:1110(smb2_multi_protocol_reply_negprot)
Requested protocol [SMB 2.002]
[2023/10/10 16:04:31.577631, 3] ../../source3/smbd/smb2_negprot.c:1110(smb2_multi_protocol_reply_negprot)
Requested protocol [SMB 2.???]
[2023/10/10 16:04:31.578691, 3] ../../source3/smbd/smb2_negprot.c:342(smbd_smb2_request_process_negprot)
Selected protocol SMB2_FF
[2023/10/10 16:04:36.585796, 3] ../../lib/util/util_net.c:255(interpret_string_addr_internal)
interpret_string_addr_internal: getaddrinfo failed for name gw (flags 34) [Try again]
[2023/10/10 16:04:36.585985, 3] ../../source3/lib/util_sock.c:1034(get_mydnsfullname)
get_mydnsfullname: getaddrinfo failed for name gw [Unknown error]
[2023/10/10 16:04:41.596585, 3] ../../lib/util/util_net.c:255(interpret_string_addr_internal)
interpret_string_addr_internal: getaddrinfo failed for name gw (flags 34) [Try again]
[2023/10/10 16:04:41.596764, 3] ../../source3/lib/util_sock.c:1034(get_mydnsfullname)
get_mydnsfullname: getaddrinfo failed for name gw [Unknown error]
[2023/10/10 16:04:41.596992, 3] ../../auth/gensec/gensec_start.c:1083(gensec_register)
GENSEC backend 'gssapi_spnego' registered
[2023/10/10 16:04:41.597076, 3] ../../auth/gensec/gensec_start.c:1083(gensec_register)
GENSEC backend 'gssapi_krb5' registered
[2023/10/10 16:04:41.597156, 3] ../../auth/gensec/gensec_start.c:1083(gensec_register)
GENSEC backend 'gssapi_krb5_sasl' registered
[2023/10/10 16:04:41.597232, 3] ../../auth/gensec/gensec_start.c:1083(gensec_register)
GENSEC backend 'spnego' registered
[2023/10/10 16:04:41.597306, 3] ../../auth/gensec/gensec_start.c:1083(gensec_register)
GENSEC backend 'schannel' registered
[2023/10/10 16:04:41.597380, 3] ../../auth/gensec/gensec_start.c:1083(gensec_register)
GENSEC backend 'ncalrpc_as_system' registered
[2023/10/10 16:04:41.597456, 3] ../../auth/gensec/gensec_start.c:1083(gensec_register)
GENSEC backend 'sasl-EXTERNAL' registered
[2023/10/10 16:04:41.597530, 3] ../../auth/gensec/gensec_start.c:1083(gensec_register)
GENSEC backend 'ntlmssp' registered
[2023/10/10 16:04:41.597605, 3] ../../auth/gensec/gensec_start.c:1083(gensec_register)
GENSEC backend 'ntlmssp_resume_ccache' registered
[2023/10/10 16:04:41.597680, 3] ../../auth/gensec/gensec_start.c:1083(gensec_register)
GENSEC backend 'http_basic' registered
[2023/10/10 16:04:41.597757, 3] ../../auth/gensec/gensec_start.c:1083(gensec_register)
GENSEC backend 'http_ntlm' registered
[2023/10/10 16:04:41.597835, 3] ../../auth/gensec/gensec_start.c:1083(gensec_register)
GENSEC backend 'http_negotiate' registered
[2023/10/10 16:04:41.598624, 3] ../../source3/smbd/smb2_negprot.c:1176(smb2_multi_protocol_reply_negprot)
Selected protocol SMB 2.???
[2023/10/10 16:04:41.599382, 3] ../../source3/smbd/server_exit.c:229(exit_server_common)
Server exit (NT_STATUS_INVALID_PARAMETER)
The log for the Debian workstation differs and most relevant seems that it shows Selected protocol SMB3_11 (i.s.o. Selected protocol SMB 2.???), after which authentication etc continues successfully. The log of the failed connection attempt never gets to authenticating the principal.
Please note that in the OpenWrt 23.05 image samba4 4.18.6 is build against libopenssl3 i.s.o. libopenssl1.1 in 22.03.5's samba4 4.18.0.
So, it seems that for some reason the macOS client protocol negotiation with the samba server fails. Reason ?
Hello, I am getting 404 for TP-Link Archer C7 v4 Kernel and Sysupgrade images. Is this device not supported yet?
Hello everyone! I recently purchased a Mercusys MR90X from Amazon India. I installed OpenWRT following these instructions: https://openwrt.org/toh/mercusys/mr90x_v1 which was the snapshot version: https://downloads.openwrt.org/snapshots/targets/mediatek/filogic/openwrt-mediatek-filogic-mercusys_mr90x-v1-initramfs-kernel.bin
Later @patrakov took a look at my installation and instructed me to use the latest release candidate. So first we installed version 23.05 rc3 using System -> Backup / Flash Firmware and then upgraded to 23.05 rc4 using the attended-sysupgrade package. We also tried to directly upgrade to rc3 from the initial snapshot installation but the package found no available upgrades. So we had to resort to flashing the rc3 image directly.
I have a 1 gigabit connection from ACT Fibernet (https://www.actcorp.in/broadband/delhi/broadband-plans) and I have to use PPPoE to connect. To get the full gigabit, I had to enable:
root@marc:~# cat /usr/share/nftables.d/table-pre/pppoe_fix.nft
flowtable ft {
hook ingress priority filter
devices = { br-lan, pppoe-wan }
}
root@marc:~# cat /usr/share/nftables.d/chain-pre/forward/pppoe-fix.nft
meta l4proto { tcp, udp } flow add @ft
Here are some tests. All of the wifi tests were done with: Mode AX, Channel 149 and 80 Mhz Width.
Speedtest on a Macbook Pro (M2 Max, 16 inch) over ethernet connected over a thunderbolt dock:
Speedtest on the same MBP over WiFi:
Making a separate post as I am not allowed to post more than 8 links.
Software offloading workaround removed and router rebooted:
MBP over LAN:
MBP over WiFi:
Software offloading workaround removed, packet steering disabled and router rebooted:
MBP over LAN:
MBP over WiFi:
Additionally I found that while enabling 5 Ghz with 160 Mhz on Channel 100 (with country selected as India), DFS is checked and WiFi is automatically disabled. This seems to be an incorrect conclusion as DFS is supported on Channel 100 at 160 mhz: https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/tree/db.txt
Relevant system log is attached. It's important to note here there is no mention of RADAR in the log. https://bin.kayg.org/?7c61f4722be63f02#6tSiv3Xx8xmjM4iB9yfEaKQiTvcHMCiqEUNBagQrGAsJ
yes i has MR90x too my config is like this
config wifi-device 'radio0'
option type 'mac80211'
option path '**********'
option channel '11'
option band '2g'
option htmode 'HE40'
option country 'FR'
option cell_density '0'
config wifi-device 'radio1'
option type 'mac80211'
option path '**********'
option channel '36'
option band '5g'
option htmode 'HE160'
option country 'FR'
option cell_density '0'
i don't know if i right of my cofnig
These work, thank you!
In France, Channel 100 is the only one suitable for 160 MHz operation.
thanks for info
where do you found this info ? please
The official source of the allowed bandwidths and power levels for each country is https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/tree/db.txt
Alternatively, you can use the iw reg get command after setting the correct country code.
i have this
country FR: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
(57000 - 71000 @ 2160), (N/A, 40), (N/A)
so same my 2.4ghz is good for all ? but 5ghz wifi ax only 160 as two possiblity
country FR: DFS-ETSI
(2400 - 2483.5 @ 40), (100 mW)
(5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
(5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW, wmmrule=ETSI
(5470 - 5725 @ 160), (500 mW), DFS, wmmrule=ETSI
# short range devices (ETSI EN 300 440-1)
(5725 - 5875 @ 80), (25 mW)
# WiFi 6E low power indoor
(5945 - 6425 @ 160), (23), NO-OUTDOOR, wmmrule=ETSI
# 60 GHz band channels 1-6 (ETSI EN 302 567 v2.2.1)
(57000 - 71000 @ 2160), (40)
if i put auto then channel out right automaticly ?
Yes - in France, 40 MHz works on any channel number from 1 to 13.
Regarding the "auto" channel, try it. I do not use this feature because I tried all non-equivalent choices manually and verified that channel 149 is optimal in my place for 80 MHz.
OpenWrt 23.05 stable has been tagged as of 8 hours ago.
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=86e852bcd01c4e43423c03984ee431118d57f855
FYI - multiple brcm53xx devices have broken Ethernet since 23.05.0-rc3 (at least Netgear R8000 and Linksys EA9200) leading to an inaccessible router (soft brick) after installing anything newer than 23.05-rc2, including the stable 23.05.0 release from 8 hours ago. If wifi-enabled configs were not carried over, one needs to flash rc2 or some other working firmware to recover.
The cause is most likely this issue: bcm53xx: Linksys EA9200 ethernet is broken #13548