Posted: Wed Jul 08, 2020 16:40 Post subject: New Build - 07/08/2020 - r43711
[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 specific device recovery 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.
Notes:
• CVE-2019-14899 VPN fix (applicability depends on VPN setup) and GUI toggle. 6920, 6928, 6931, 6932 (WIP 7040)
• In-kernel Samba has been implemented this year and default min/max versions have changed 6954, 6957, with WSD support.
• VAP issue is fixed! For any Wireless Mode, create a VAP and both ath0/ath1 should now function properly.
• Local DNS option removed from Services->DNSMasq in changesets 43080 and 43081; ref: #7092
• DHCP and DNS help (English) updated in 43083; ref: #7091
• WireGuard 1.0.20200623: PBR, Kill Switch, Inbound Firewall, Naming of Peers, Status, Key, Guides. Thanks egc!
Issues:
• There may be remaining issues for Samba (for example NTFS), with frequent updates.
Important:
• If reporting issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog/serial output, strace etc.
• For firewall issues provide 'iptables -L', 'iptables -t nat -L' and the /tmp/.ipt file.
• Search existing SVN tickets before opening a new one. Before reporting, reset and manually setup (no nvram backup).
• Be sure to include operating and wireless modes (Gateway, AP, CB, etc.) along with relevant configuration information.
Posted: Wed Jul 08, 2020 17:46 Post subject: WZR-600DHP
This build bricked my WZR-600DHP. Previous build was 43652 and was working well. I let the router sit for 10 min prior to doing a power cycle with no luck. Off to attempt a recovery. _________________ Asus RT-N66R 50841 big
Netgear WNDR4500v2 50841 mega
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Wed Jul 08, 2020 18:25 Post subject:
Did you try doing a reset? There were some devices, I think mostly Ralink/MediaTek, that got a driver upgrade. Not sure if any of the Atheros Buffalo devices were part of that or not. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
wds stations connected to qca6174 wds ap transfer no data no ping nothing. (and had enough, qca9886 on the way)
not part of this build but x86 beware if u change the hdd/sdd in the system, not even anything else, u have to buy the damn activation again.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Did you try doing a reset? There were some devices, I think mostly Ralink/MediaTek, that got a driver upgrade. Not sure if any of the Atheros Buffalo devices were part of that or not.
I did not perform a reset when flashing from 43652. I flash my routers like a layman would to find issues. I did try a 30-30-30 after it bricked but no luck. trying to get the TFTP timing down to recover the router, no luck yet. _________________ Asus RT-N66R 50841 big
Netgear WNDR4500v2 50841 mega
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Jul 08, 2020 18:41 Post subject:
kernel-panic69 wrote:
tatsuya46 wrote:
not part of this build but x86 beware if u change the hdd/sdd in the system, not even anything else, u have to buy the damn activation again..
I thought you had to re-flash the entire image, not webupgrade on x86. Not sure how it magically detected the hardware change and balked.
yes reflash onto the new drive, but it picks up the different drive (serial # i guess?) and refuses to activate with previous key. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
When browsing the Samba share, in particular if from Windows Explorer I:
(Windows10, ver 1909)
1. browse to, say \\192.168.1.1\usb_dsk\videos
2. open a file
3. In Windows Explorer address bar I click on \\192.168.1.1 part of the address
So far, I have not been able to make SMB make the kernel crash!
[Edit] It did not take long. It still crashes. See next post.[/Edit]
Thanks BS for all the effort!
Last edited by marcelo3d on Wed Jul 08, 2020 21:21; edited 1 time in total
What I did:
1. connect to Samba share from Win10
2. Open/close some files
3. turn off WiFi on the client (Win10)
4. Wait a few seconds
5. turn WiFi back on on the client
6. wait a few seconds.
7. Kernel crashes
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Thu Jul 09, 2020 8:33 Post subject:
please try the attached image for the r7800 and gimme feedback if it solves your problem. if not, can you provide a tcpdump/wireshark capture if your samba traffic at the time the problem occures?
What I did:
1. connect to Samba share from Win10
2. Open/close some files
3. turn off WiFi on the client (Win10)
4. Wait a few seconds
5. turn WiFi back on on the client
6. wait a few seconds.
7. Kernel crashes
Joined: 06 Feb 2020 Posts: 167 Location: Maharashtra, India
Posted: Thu Jul 09, 2020 14:59 Post subject:
Tried this build, No crash Observed which there earlier.
one observation, while transferring the file to USB attached to router from windows 10 , router CPU usage reaches 100%, free memory reduces to 9%. the file transfer happens successfully, tried both to & fro from Samba share. the only thing i found is CPU usage took about 1 Hour to reduce, but reduced till 85% only. Memory is not freed after transfer is complete. needed a router reboot to restore memory and CPU usage.
Frankly speaking except high CPU usage and memory usage everything worked.
router : Netgear R7800
Firmware Build : 43721
Windows Client: Windows 10 2004
