Posted: Mon Jul 19, 2021 11:10 Post subject: RETRACTED New Build - 07/19/2021 - r47073
[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:
• 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.
Status: Up and running for 2 hours , basic setup as Gateway, static leases, 2,4GHz, 5Ghz (Vanilla Firmware), OpenVPN client to Keepsolid with PBR working, OpenVPN Server with site-to-site setup and local DNS working.
WireGuard client to Keepsolid working, WireGuard client for site-to-site setup to own server working.
Errors: Nothing encountered yet (but not tested USB/NAS)
Joined: 18 Mar 2014 Posts: 12908 Location: Netherlands
Posted: Mon Jul 19, 2021 12:02 Post subject:
Router Model: Linksys EA8500
Firmware Version: DD-WRT v3.0-r47073 std (07/19/21)
Kernel Version: Linux 4.9.274 #325 SMP Sat Jul 17 14:25:31 +07 2021 armv7l
Upgraded: DD-WRT v3.0-r46681 std (05/15/21)
Reset: No not this time
Status: Up and running for 2 hours, basic setup as Gateway, static leases, 2.4 GHz and 5 GHz working (vanilla firmware), OpenVPN server working, WireGuard Server working,
Netgear WNDR3700 V4
DD-WRT v3.0-r47073 std (07/19/21)
Linux 3.18.140-d6 #121130 Mon Jul 19 08:58:35 +07 2021 mips
GUI install over r47040 --- all ok
#
Linksys EA8500...main gateway unit
DD-WRT v3.0-r47073 std (07/19/21)
Linux 4.9.274 #325 SMP Sat Jul 17 14:25:31 +07 2021 armv7l
GUI install over r47033 ---worky ok so far...
...if its as good as r47033 I be happy
Upgraded from: DD-WRT v3.0-r47040 via CLI
Reset: No
Status:Operational 12h+
Errors: nothing for my set up WiFi issues from the previous builds resolved, using 2,4ghz Mixed, instead of NG mixed and no fixed rates...also revised few other settings removed ipset rules and some others...still investigating the source of my previous issues...just don't have much time this days...
so far so good, on this build and previous 47040 R7800 got back to rock solid... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Temperature: CPU 55.224 °C / wlan0 45 °C
Status: OK
Issues: None
Issues:
As mentioned first in build (r47000), every time I do a reset using the GUI or Shell the swconfig tab disappears. It only shows up when I install a new firmware without resetting. This happens on this build and the last few builds that I tested dating back to the May build. This also happens on my Netgear XR500.
I also lose access to the router (shell and GUI) when I try to add VLANS after a reset. As soon as I add a VLAN and hit apply, I lose access to the router. I need to reset the router in order to access it again. Perhaps it has something to do with the GUI showing lan ports on VLAN0 while in the CLI lan ports are on VLAN1. See attached picture (before adding VLAN3). Let me know if you need additional info.
Partial Output of "swconfig dev switch0 show" command before adding VLAN3
Status: Working Fine; running vanilla firmware type for 2.4ghz & DD-wrt for 5ghz, uptime 12+ Hrs
WiFi speeds on both 2.4 & 5GHz are better, now I am able to achieve 600+Mbps up & down on 5GHz (wireless channel width 80+80, Connected Link speed 866/866Mbps, client - Intel(R) Wireless-AC 9560 160MHz) & around 850+ Mbps on wired client, it used to be 400-450Mbps earlier for both wired & wireless, can not be a placebo; with no change to configuration & no reset, I think some tweaks by BS has helped to get better work out of R7800, CPU usage around 1%
for what the mention? the card does not support 80+80
(866Mbit is VHT80 with 2 spatial streams)
and every client that doesn't support VHT80+80 connects only to the first 80Mhz block (the second block remains completely unused)
there are practically no clients at all that support 80+80 (actually only supported by a few Atheros Cards)
If the card would support 80+80 (which it does not) then the card would show VHT160 and 1733,3Mbit in the WLAN status.
Wi-Fi gurus may ask: Why not bond two discontiguous 80 MHz channels together? This would give network designers five 80 MHz channels in the 5 GHz band to work with in the U.S., including two without DFS constraints. But the devil is in the details.
At the chip level, 80+80 MHz mode requires a device to operate on two channels simultaneously. This means duplication of subsystems to support the second discontiguous channel, making integrated circuits much larger than for contiguous channel support. Smartphone manufacturers would be faced with scaling back other technical upgrades on cameras, processors or sensors in order to make room for larger Wi-Fi chips. Even if these devices did meet size constraints, reduced energy efficiency from running two separate 80 MHz subsystems would drain the phone battery faster. For mobile devices, battery life is paramount, and the key performance indicators of the discontiguous approach will not meet the market needs.
The additional downside of growing a chip to support a second radio subsystem is increased cost. Even if a router or smartphone maker solved the size and power challenges of discontiguous 80+80 support, they would have to further sacrifice other technical upgrades in order to maintain their existing cost structure. In markets where every penny counts, this is clearly a non-starter.
so a pretty useless feature for 99% of the users
unless you connect two dd-wrt routers with VHT80+80 or you have one of the few wifi cards that support it
Quote:
now I am able to achieve 600+Mbps up & down on 5GHz
Nothing new, a normal throughput of an 80Mhz Intel card, has already been on the level for a very very long time.
