Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Fri Mar 26, 2021 15:01 Post subject: New Build - 03/26/2021 - r46177
[WARNING]: This thread is only for feedback on this beta release for developers and the community's benefit.
DO NOT flash this beta release unless you understand the risks involved and device specificrecovery methods.
Avoid discussions! Create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.
Issues, observations, and/or workarounds reported:
• DNScrypt 1.95 can still be used in the GUI, but v2 (not compatible) requires Golang and thus Entware. #6246
• WDS does not work on Broadcom ARM devices(only MIPS<->MIPS) & bridge modes on k4.4 devices may sometimes work
in some configurations for certain builds but are not supported by the bcmdhd driver. Use client or repeater instead.
• VAPs not working at bootfixed for unbridged VAPs in40562 - 40566. Effective startup commandsdiscussion thread is here.
• If start-up scripts do not work from USB add a delay, e.g. wait script or 'sleep 25'.
• Broadcom ARM devices if 5 GHz channels are missing, via Telnet/SSH: 'nvram set brcm_unlock=1' 'nvram commit' 'reboot'
• Show us your findings with steps to reproduce, configuration, output, logs and important information below!
Important:
• For issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog, klog, serial, strace, tcpdump, wireshark etc.
• Any firewall NAT or WAN issues, show output: 'iptables -vnL', 'iptables -t nat -vnL', 'iptables -t mangle -vnL' and /tmp/.ipt file.
• Search SVN tickets & discuss in forum before opening. Before reporting: reset & manually set up, not restore from a backup.
• Please include operating & wireless modes (e.g. Gateway, Router, AP, CB, WDS, Mesh) & relevant configuration information.
Joined: 18 Mar 2014 Posts: 12917 Location: Netherlands
Posted: Fri Mar 26, 2021 15:04 Post subject:
Router Model: Netgear R6400v2, board_id: U12H332T
Firmware Version: DD-WRT v3.0-r46177M Community Build (03/25/21)
Kernel Version: Linux 4.4.263 #1 SMP Thu Mar 25 11:10:52 CET 2021 armv7l
Upgraded from: DD-WRT v3.0-r46166M Community Build (03/25/21)
Reset: No not this time
Status: Up and running for 24 hours, basic setup as Gateway, static leases, OpenVPN client with Policy Based Routing up and running, 2,4GHz and 5Ghz with excellent range and speed, OpenVPN server working, WireGuard server working with 8 clients (phones , windows and two other routers for site-to-site setup).
Router/Version: Netgear R7000
File: netgear-r7000-webflash.bin
Firmware: DD-WRT v3.0-r46177 std (03/26/21) (prev. DD-WRT v3.0-r46130 std (03/21/21))
Kernel: Linux 4.4.263 #2347 SMP Fri Mar 26 10:55:53 +07 2021 armv7l
Mode: Gateway, Wifi disabled, Wireguard for external access, WAN to DSL, Keep Alive reboot 5:00 in the morning
Reset: No
Status: 2:25h up, ok.
Router/Version: Asus RT-N66U
File: dd-wrt.v24-46177_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r46177 big (03/26/21) (prev. DD-WRT v3.0-r46130 big (03/21/21))
Kernel: Linux 4.4.263 #7751 Fri Mar 26 16:32:11 +07 2021 mips
Mode: Gateway, Wifi disabled, WAN disabled, Wireguard Endpoint for external VPS, connected via LAN to WRT1900ACS v2, Keep Alive reboot 6:05 in the morning
Reset: No
Status: 2:42h up, ok.
Router/Version: Linksys WRT54GL 1.1
File/Kernel: 46177, dd-wrt.v24_std_special_generic.bin
Firmware: DD-WRT v3.0-r46177 std-special (03/26/21)
Linux 2.4.37 #64714 Fri Mar 26 09:31:42 +07 2021 mips
Previous/Reset: 44715 , no reset
Mode/Status: LAN and AP, router
Issues/Errors: took 20s to get back active
update via web-interface, after boot no problem, works fine
Firmware Version: DD-WRT v3.0-r46177 Community Build (03/26/21)
Router Model: Netgear R7000
Firmware Version: DD-WRT v3.0-r46177 std (03/26/21)
Kernel Version: Linux 4.4.263 #2347 SMP Fri Mar 26 10:55:53 +07 2021 armv7l
Flashed: Using FireFox browser using BIN file netgear-r7000-webflash.bin
Upgraded from: DD-WRT v3.0-r45993 Community Build (03/17/21)
Reset: No
Temperatures: CPU 58.0 °C / WL0 47.0 °C / WL1 46.8 °C
Status: Up and running for 24 hours, basic setup as AP, DHCP server, running 2.4GHz and 5Ghz radios with same excellent speeds, working with 24 clients curently connected.
Errors: None to report ATT....still testing _________________ Routers: Netgear R8000,R7000, WRT610N, WRT320N, WRT54GS, Switches: Cisco SG350 10 port, Storage: Linkstation 4TB Buffalo NAS.
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Sun Mar 28, 2021 16:12 Post subject:
Oh well, all **public** Samba shares could not be accessed because of bad password, with account name "guest". I think the kernel-mode Samba was refusing all logins. Re-creating those shares didn't help. Also, NET VIEW also failed with minimum version set to "NT 1.0". All these happened after cold boot following firmware upgrade.
Otherwise, most basic functions are working.
Update:
So I `cat /tmp/smb.conf`, and I found that "map to guest = never", "force user = root", and "usershare allow guests = Yes". Are these normal?
I don't remember doing these when I was using the full Samba.
"map to guest=bad password" should be a norm?
"log file = /var/smbd.log" was also suspicious as I could NOT find that file!
Some entries from my smb.conf in the old days:
Code:
...
guest account = nobody
invalid users = root
map to guest = bad password
null passwords = yes
...
[public_share]
...
guest ok = yes
public = yes
writable = no
browsable = yes
readonly = yes
...
Update 2:
When I used "netstat -anp | grep smb", I found that ksmbd was NOT listening to ports of Samba, which should have been:
Router Model: Netgear R8000
Firmware Version: DD-WRT v3.0-r46177 std (03/26/21)
Kernel Version: Linux 4.4.263 #2355 SMP Fri Mar 26 11:30:54 +07 2021 armv7l
Previous Version: DD-WRT v3.0-r43845
Drivers: Experimental
Services: samba, dlna server, wireguard client, openvpn client, dhcp, wifi 2.4 ghz, usb, nas
Status: working
Updated: via webgui
Mode: AP/gateway
Issue(s): cannot write to the share folder via windows explorer
Reset: no
Reboot: yes
Uptime: information not accurate
Load Average: 27.97, 20.48, 10.76
Temperatures: CPU 50.2 °C
Errors: as reported in the syslog below (with external drive of 4T and data 2.5T stored attached to router)
Dec 31 20:00:10 DD-WRT kern.err kernel: bcmsflash: found no supported devices
Dec 31 20:00:13 DD-WRT kern.err kernel: brcmfmac: brcmf_cfg80211_dump_survey: cca_get_stats failed (-52)
Dec 31 20:00:20 DD-WRT user.err wsdd2[1234]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Address not available
Dec 31 20:00:20 DD-WRT local5.err ksmbd: [ksmbd-manager/1239]: ERROR: Can't open `/tmp/ksmbd.subauth': No such file or directory
Dec 31 20:00:20 DD-WRT user.err wsdd2[1234]: error: wsdd-mcast-v4: wsd_send_soap_msg: send: Network unreachable
Dec 31 20:00:23 DD-WRT kern.err kernel: hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)
Mar 28 10:28:33 DD-WRT user.err wsdd2[1234]: Terminated received.
Mar 28 10:28:33 DD-WRT local5.err ksmbd: [ksmbd-manager/1239]: ERROR: WARNING: child process exited abnormally: 1241
Mar 28 10:28:33 DD-WRT local5.err ksmbd: [ksmbd-manager/1239]: ERROR: can't execute kill 1241: No such process
Mar 28 10:28:36 DD-WRT local5.err ksmbd: [ksmbd-manager/2605]: ERROR: can't execute kill 2606: No such process
Mar 28 10:28:40 DD-WRT local5.err ksmbd: [ksmbd-manager/3176]: ERROR: Failed to create lock file: File exists
Mar 28 10:30:30 DD-WRT daemon.err httpd[1440]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Mar 28 10:36:46 DD-WRT kern.err kernel: ksmbd: ksmbd_vfs_lookup_in_dir:2351: cannot open directory /mnt
Mar 28 10:49:28 DD-WRT kern.err kernel: brcmfmac: brcmf_cfg80211_dump_survey: cca_get_stats failed (-52)
Mar 28 10:56:06 DD-WRT daemon.err httpd[1440]: httpd : Request Error Code 408: No request appeared within a reasonable time period.
Warnings: as reported in the syslog below
Mar 28 10:28:37 DD-WRT kern.warn kernel: EXT4-fs (sdb3): Ignoring removed nobh option
Issues:
Attached an external 4T drive with 17.6G data to the router. The .meta folder appeared and started growing. Data on that drive is now 167.7G, the difference 150.1G is all the .meta folder and still growing. I can view the data on the drive by windows explorer but cannot access all of it from any other medium until the growing finishes. At least an hour has passed since the growth started and I cannot wait for at least nine (9) hours before I can access all the files on this drive.
This occurred when I detached the external drive from the router and connect it directly to the computer and I copied the data to the external drive.
You cannot write, but you can delete, data across the network with windows explorer directly to the share folder on the external drive. You must directly attached the external drive to a computer.
Other than the above, everything is great, you can see improvements but I must return to the old builder with ntfs.
Update:
At the time of delete the .meta folder, it had grown to 224G.
I have reinstalled r43845 and its backup and everything is working fine. All my external drives were fully operational in under one (1)minute. Thanks B.S.
Last edited by Abboo on Sun Mar 28, 2021 18:14; edited 1 time in total
Oh well, all **public** Samba shares could not be accessed because of bad password, with account name "guest". I think the kernel-mode Samba was refusing all logins. Re-creating those shares didn't help. Also, NET VIEW also failed with minimum version set to "NT 1.0". All these happened after cold boot following firmware upgrade.
Otherwise, most basic functions are working.
Update:
So I `cat /tmp/smb.conf`, and I found that "map to guest = never", "force user = root", and "usershare allow guests = Yes". Are these normal?
I don't remember doing these when I was using the full Samba.
"map to guest=bad password" should be a norm?
"log file = /var/smbd.log" was also suspicious as I could NOT find that file!
Some entries from my smb.conf in the old days:
Code:
...
guest account = nobody
invalid users = root
map to guest = bad password
null passwords = yes
...
[public_share]
...
guest ok = yes
public = yes
writable = no
browsable = yes
readonly = yes
...
Update 2:
When I used "netstat -anp | grep smb", I found that ksmbd was NOT listening to ports of Samba, which should have been:
I think you have to remove the tick on 'public' and create at least two users with passwords. Save and apply and you should be able to access your share folders across the network via windows explorer. I believe ksmbd is performing but it is a work-in-progress. I get better quality.
Router/Version: Asus RT-AC68U rev A1
Firmware: asus_rt-ac68-firmware.trx
Kernel: Linux 4.4.263 #2347 SMP Fri Mar 26 10:55:53 +07 2021 armv7l
Mode: Gateway, Wireless AP.
Reset: No, flasked using CLI
Previous: 03-24-2021-r46166
Status: Working well in general but smb is broken. Refuse userid/password with identical setup as with previous builds.
Relevant log entries:
Mar 28 22:44:43 Guardian3 user.info : smbd : samba started
Mar 28 22:44:43 Guardian3 user.info wsdd2[3117]: starting.
Mar 28 22:44:43 Guardian3 local5.info ksmbd: [ksmbd-manager/3121]: INFO: File '/tmp/ksmbd.lock' belongs to pid 2886
Mar 28 22:44:43 Guardian3 local5.err ksmbd: [ksmbd-manager/3121]: ERROR: Failed to create lock file: File exists
Mar 28 22:44:43 Guardian3 local5.info ksmbd: [ksmbd-manager/3121]: INFO: Exiting. Bye!
Have had similar entries for a while but this one is new:
Mar 28 22:44:43 Guardian3 local5.info ksmbd: [ksmbd-manager/3121]: INFO: Exiting. Bye! _________________ Netgear R7000 on Build 55109
Asus AC-AC68U rev. C1 (AP) on Build 55109
Asus AC-68U rev. A1 on Build 54604
Asus AC-68U rev. A1 on Build 53339
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Mon Mar 29, 2021 10:24 Post subject:
Abboo wrote:
I think you have to remove the tick on 'public' and create at least two users with passwords. Save and apply and you should be able to access your share folders across the network via windows explorer. I believe ksmbd is performing but it is a work-in-progress. I get better quality.
Adding users worked as you said. But null/empty passwords should be allowed for account "guest". That's expected behavior for Window$ workgroup, notably public shares. It's equivalent to "Turn off password protected sharing" in Window$' terminology.
netstat still didn't reveal ksmbd nor its port binding.
Thank you anyway!!
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
I think you have to remove the tick on 'public' and create at least two users with passwords. Save and apply and you should be able to access your share folders across the network via windows explorer. I believe ksmbd is performing but it is a work-in-progress. I get better quality.
Adding users worked as you said. But null/empty passwords should be allowed for account "guest". That's expected behavior for Window$ workgroup, notably public shares. It's equivalent to "Turn off password protected sharing" in Window$' terminology.
netstat still didn't reveal ksmbd nor its port binding.
Thank you anyway!!
What you said is true but it applied to the older ntfs prior to ntfs3. Since the arrival of ntfs3, guest nolonger work and the external drive must be 'clean' for ntfs to mount. The advancement of technology.