Joined: 08 May 2018 Posts: 14129 Location: Texas, USA
Posted: Wed Jul 15, 2020 13:24 Post subject: New Build 07-15-2020-r43813
[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:
• r41664 or later for SFE NAT (k3.2+), KRACK (k24+), PBR+SFE, CAKE & FQ_CODEL_FAST (reset!), GTK Rekey timer fixes.
• Reset button was broken at 40571, then fixed in build r40750.
• Experimental build option for Broadcom 8MB+ K2.x devices (limited currently): broadcom_K3X_mipsel32r1
• 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.
• Broadcom MIPS devices are now on kernel 4.4. N66U/AC66U half memory is fully resolved.
• Local DNS option removed from Services->DNSMasq in changesets 43080 and 43081; ref: #7092
• DHCP and DNS help (English) updated in 43083; ref: #7091
• WAN lease time approaching zero bug on WRT54* devices fixed in 43191; ref: #6456
• Images for WNR3500Lv2 (BRCM NAND flash crash bug) fixed in 43219 (43217); ref: #7098
• WireGuard 1.0.20200623: PBR, Kill Switch, Inbound Firewall, Naming of Peers, Status, Key, Guides. Thanks egc!
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) and bridge modes on k4.4 devices may sometimes work
in some configurations in certain builds but are not supported by the bcmdhd driver. Use client or repeater instead.
• VAPs not working at bootfixed for unbridged VAPs with r40564:40566.Workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas(there are a few alternatives, search).
• If start-up scripts do not work from USB add a delay (e.g. wait script or 'sleep 25').
• For Broadcom ARM devices that do not show all 5GHz channels, via telnet/ssh: nvram set brcm_unlock=1(enter),
nvram commit(enter), nvram reboot(enter)
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.
Router/Version: Netgear R6400v2
File/Kernel: 43813
Previous/Reset: 43516, no reset, update via CLI
Mode/Status: Access point
Issues/Errors: Just like the 43800 build (noted in another post), installing this over the 43516 build turned on the "Filter Multicast" setting. This caused IPv6 issues for me.
Joined: 08 May 2018 Posts: 14129 Location: Texas, USA
Posted: Wed Jul 15, 2020 19:44 Post subject:
Router/Version: Netgear R7000P
Firmware: DD-WRT v3.0-r43813 std (07/15/20)
Kernel: Linux 4.4.230 #583 SMP Wed Jul 15 08:35:08 +04 2020 armv7l
Previous: DD-WRT v3.0-r43812 std (07/14/20)
Reset: No
Mode: 2.4 Wireless Client, 5GHz AP, Gateway
Status: OK
Uptime: ~6hrs
Temps: CPU 60.2 °C / WL0 47.4 °C / WL1 50.5 °C
Issues/Errors: Bootloop on intial reboot; Opened new tab in IE, closed old tab and rebooted and stayed up fine after that. Still good on channel selection on 5GHz band.
Router/Version: Cisco Linksys E4200v1
Firmware: DD-WRT v3.0-r43813 mega (07/15/20)
Kernel: Linux 4.4.230 #2618 Wed Jul 15 14:36:40 +04 2020 mips
Previous: DD-WRT v3.0-r43516 mega (06/25/20)
Reset: No
Mode: Switch
Status: OK
Uptime: ~6hrs
Issues/Errors: None _________________ "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
flashed 38570 then did a gui reset
flashed 39345 then did a nvram erase
then flashed the rest of the kong builds without reset
then flashed the most recent build and did a gui reset
the high and low channels are there just like kernel-panic69 said
even though i did do one nvram erase on kong i thing the lesson is don't use nvram erase
apologies for all my grief
I'm assuming a bs build will work as well. I think the key is to install a build before the wifi changes first before updating to the current
Posted: Wed Jul 15, 2020 23:54 Post subject: r8000
Router/Version: Netgear R8000
Firmware: DD-WRT v3.0-r43813 std (07/15/20)
Kernel: Linux 4.4.230 #585 SMP Wed Jul 15 08:52:15 +04 2020 armv7l
Previous: 2020-06-25 r43516
Reset: Yes, reset to factory defaults during upgrade, and another one done afterwards
Mode: 2.4ghz AP, 5ghz AP, 5ghz client
Issues/Errors:
I use this router as a mobile hotspot in the RV - I connect it either to my home network, hotspot, or campground wifi as I find it.
This release is the first one that I've tested that actually seems to work with using one 5ghz radio as a client to the hotspot, and the other as an AP. I've usually been able to use the 2.4ghz radio as a client no problem.
However, in this release, every time I change the IP from the default of 192.168.1.1/24 to another range (say 10.0.70.1/24), I lose DHCP server functionality. It stops responding to DHCP requests. Once I set it back to 192.168.1.1 it works just fine.
Below is a snippet from a DHCP test client. I started with the router freshly reset to factory defaults, and DHCP server functionality working. I then only changed the router internal IP address, and observed loss of DHCP responses. I tried several configurations, before finally going back to 192.168.1.1/24, when DHCP started answering again.
I'll try to get more logs, but I wanted to capture this before we went on a trip.
Like I said in the beginning, using the 2nd 5ghz radio as a client is working well for me in this release. Don't have a lot of uptime yet to see if has restarts/etc.
failed dhcp configuration.png
Description:
router IP configuration causing DHCP server failure
Joined: 08 May 2018 Posts: 14129 Location: Texas, USA
Posted: Thu Jul 16, 2020 1:51 Post subject:
@novasbc: If you are using class A or B subnets, use the proper subnet mask and desired start IP address. There have been changes to the configuration and that's probably why it's not working. Just a thought.
@Abboo: Did you ensure your network settings were correct after upgrading?
@tinkeruntilitworks: Good to hear, and sorry for all the grief. I don't always remember everything, and I guess I expect people to have read a lot of the same threads and posts I have, perhaps. No worries, all good! _________________ "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
Router/Version: Netgear R7000P
File/Kernel: netgear-r7000p-webflash.bin
Previous/Reset: 43718 / gui reset
Issues/Errors: Can't access all 5ghz channels even with work around applied. Didn't work in 43718 either
It's too much to do, I'll wait until it's fixed in later builds. The channel I have access to with 80mhz on 5Ghz is fine for where the router is in use.