Posted: Wed Feb 17, 2021 17:36 Post subject: New Build - 02/17/2021 - r45767
[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 missing 5GHz channels, via Telnet/SSH: 'nvram set brcm_unlock=1' 'nvram commit' 'nvram 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.
Same problem as explained in build r45711. Reverted back to build r45592
Extract from build r45711
My diagnosis of the NAS problem: the file sharing path is /mnt; there should also be this path which is in the older builds, /mnt/sda1; I believe it originates from /tmp/mnt/sda1 but I can be wrong. I do not know how to point the path to /mnt/sda1.
Once you upgrade with no reset the message you get from NAS file sharing path:mnt/sda1(unavailable)
Also when you click on the share folder on the network from internet explorer in Windows 7 you get an empty folder
Same problem as explained in build r45711. Reverted back to build r45592
Extract from build r45711
My diagnosis of the NAS problem: the file sharing path is /mnt; there should also be this path which is in the older builds, /mnt/sda1; I believe it originates from /tmp/mnt/sda1 but I can be wrong. I do not know how to point the path to /mnt/sda1.
Once you upgrade with no reset the message you get from NAS file sharing path:mnt/sda1(unavailable)
Also when you click on the share folder on the network from internet explorer in Windows 7 you get an empty folder
Same problem as explained in build r45711. Reverted back to build r45592
Extract from build r45711
My diagnosis of the NAS problem: the file sharing path is /mnt; there should also be this path which is in the older builds, /mnt/sda1; I believe it originates from /tmp/mnt/sda1 but I can be wrong. I do not know how to point the path to /mnt/sda1.
Once you upgrade with no reset the message you get from NAS file sharing path:mnt/sda1(unavailable)
Also when you click on the share folder on the network from internet explorer in Windows 7 you get an empty folder
What is not a factor is the OS; I have Win7 and I read another person with Win10 having the same issue.
Can it be the size of the data drive, almost 2T?
Note: in the photo of the usb for build 45767 under Partition sda; it says /dev/sda1 mounted to /tmp/mnt/sda1 but under Disk info there is no information on 'Diskspace /tmp/mnt/sda1
This looks conflicting; is sda1 there or not. Yet automatic mount drive is enabled
Something is seriously wrong with the usb and nas.
Wiki literature seems outdated, it speaks of FAT32 and ext2/3, I am using NTFS and ext4
--> init 0 via console does result in all settings lost , will not stress this further, since it isn't supposed to work at all in my opinion.
My R7000 caused me some headache, therefore I ceased testing and downgraded to old release. (Nothing very bad, only Wireguard seems to not want my settings, further information:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=328253)
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Thu Feb 18, 2021 8:54 Post subject:
Abboo wrote:
twindragon6 wrote:
Abboo wrote:
Same problem as explained in build r45711. Reverted back to build r45592
Extract from build r45711
My diagnosis of the NAS problem: the file sharing path is /mnt; there should also be this path which is in the older builds, /mnt/sda1; I believe it originates from /tmp/mnt/sda1 but I can be wrong. I do not know how to point the path to /mnt/sda1.
Once you upgrade with no reset the message you get from NAS file sharing path:mnt/sda1(unavailable)
Also when you click on the share folder on the network from internet explorer in Windows 7 you get an empty folder
What is not a factor is the OS; I have Win7 and I read another person with Win10 having the same issue.
Can it be the size of the data drive, almost 2T?
Note: in the photo of the usb for build 45767 under Partition sda; it says /dev/sda1 mounted to /tmp/mnt/sda1 but under Disk info there is no information on 'Diskspace /tmp/mnt/sda1
This looks conflicting; is sda1 there or not. Yet automatic mount drive is enabled
Something is seriously wrong with the usb and nas.
Wiki literature seems outdated, it speaks of FAT32 and ext2/3, I am using NTFS and ext4
in the extended info you see the size /mnt is a symbolic link to /tmp/mnt. so all is correct
btw. your partition layout is crazy _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Thu Feb 18, 2021 9:57 Post subject:
i'm also missing the device in your description. i did a quick test with 2 ntfs drives formated with windows 10. works. also disk info shows them both. but i dont know how to reproduce your non standard 6 partition layout with 2 partition tables gpt usually
i would also like to see kernel logs or logfiles at all. we switched to use a new ntfs driver. usually the newer fs driver has a problem with your very special filesystem layout _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Router/Version: Netgear R6250
Firmware: DD-WRT v3.0-r45767 std (02/17/21)
Kernel: Linux 4.4.257 #2063 SMP Wed Feb 17 10:53:21 +06 2021 armv7l
Mode: Gateway, Wireless AP
Reset: No
Previous:r45735
Upgrade: Web and 1st succeed without reset.
Temperatures CPU 74.7 / WL0 51.4 / WL1 55.1
Uptime 4h
DHCP Server: Enabled - Running (no need to dial-up like DSL, it is cable connection after modem)
Disable (Samba, WRT-radauth, WRT-rflow, MAC-upd,CIFS Automount, Sputnik Agent)
No settings in Additional Dnsmasq Options;
No need to config jffs internal or USB-plugin disk,
unbound works well (/tmp/unbound.conf), simple for end-user! Great.
Posted: Thu Feb 18, 2021 15:51 Post subject: My drive issue (Not related to Firmware)
Router: Netgear R8500
Firmware:45767
Status: working
My drive issue was in Windows 10 20h2. After further testing my issue seems to be a windows explorer issue and not related to the firmware at this time. Still troubleshooting it.
Router/Version: Asus RT-AC68U
File/Kernel: Linux 4.4.257 #2063 SMP Wed Feb 17 10:53:21 +06 2021 armv7l
Previous/Reset: 42557/Yes
Mode/Status: AP + NAS
Issues/Errors: No