New Build - 07/26/2021 - r47090

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2  Next
Author Message
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 3161

PostPosted: Mon Jul 26, 2021 5:05    Post subject: New Build - 07/26/2021 - r47090 Reply with quote
[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 specific 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.


Downloads: (DD-WRT website) HTTPS & FTP (try another if a link does not work)

CLI Flash: 'cd /tmp' then 'wget {file URL}' (or 'curl -k {file URL} -o {file}') with http (not https) or ftp. Then 'write {file} linux'.

Repository: Trac SVN changelog since last build r47086 (GitHub mirror)

Notes:
OpenVPN 2.5.3: Guides, Server, PBR, Reverse PBR, Client (see second post), Kill Switch, update tips, scripts and more.
WireGuard 1.0.20210606/Tools: Guides, Client, Server, Advanced, PBR, KS, update tips, scripts & more. Thanks BS & egc!
• CVE-2019-14899 VPN fix (applicability depends on VPN setup) and GUI toggle since r41813.
Experimental build option for Broadcom 8MB+ K2.x devices (limited currently): broadcom_K3X_mipsel32r1
• Broadcom MIPS devices are now on kernel 4.4. • Support added for TP-Link Archer C8 v2 and v3.
SmartDNSMiniDLNAUnboundCoovaChilliOpenSSLdnsmasqPrivoxyTorSquidFreeRADIUSiperf3cake
In-kernel Samba (ksmbd 3.3.9+): default min/max versions changed. • WSD updateANTFS/NTFS3 kernel mode driver++
• Added swconfig support for Broadcom devices.
CVE-2020-26147, CVE-2020-24586, CVE-2020-24587 & CVE-2020-24588 (Fragattack) fixed.
• "Assign WAN port to Switch" feature removed to be reworked in a future release.

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 boot fixed for unbridged VAPs in 40562 - 40566. Effective startup commands discussion 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.

Example Template:
Code:
[b]Router/Version: [/b]
[b]File/Kernel: [/b]
[b]Previous/Reset: [/b]
[b]Mode/Status: [/b]
[b]Issues/Errors: [/b]
Sponsor
mwchang
DD-WRT Guru


Joined: 26 Mar 2013
Posts: 856
Location: Hung Hom, Hong Kong

PostPosted: Mon Jul 26, 2021 7:36    Post subject: DD-WRT BS build 47090 and Asus RT-N18U Reply with quote
Router/Version: Asus RT-N18U (rev. A1)
Firmware: DD-WRT v3.0-r47090 std (07/26/21)
Kernel: Linux 4.4.276 #3721 Mon Jul 26 02:33:59 +07 2021 armv7l
Previous: DD-WRT v3.0-r46979 std (06/21/21)
Mode: WAN @ DHCP, Wireless @ AP
Status: Working (
Not 24/7; DDNS OK; Port-forwarding OK;
Not using IPv6, VAP, VPN, CTF, FA;
Using NAS (ksmbd, minidlna), USB (jffs, opt), Recursive DNS Unbound;
Entware core (CPU: armv71) installed to /opt
)
Reset: NO reset during firmware upgrade but cold boot
File: https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2021/07-26-2021-r47090/asus-rt-n18u/asus_rt-n18u-firmware.trx

Summary

In /tmp/smb.conf, "map to guest" defaults to "bad user" now, so I no longer needed /jffs/etc/smb.conf!!

Should smb.conf appear in /tmp or /etc? I was confused.... Sorry.

Suggestions

  1. In Basic Setup -> Optional Settings, change "Domain Name" to "WAN Domain Name".
  2. In Services -> NAS -> Samba Server, should it be "Server String" or "NETBIOS Name"?

    The full Samba 4 package does allow both in smb.conf, where NETBIOS Name is the name displayed in the Windows workgroup browser. "Server String" is just a comment line with macro substitution. I dunno about ksmbd, but looks like they do the same.

    Samba's "netbios name" is Windows' "Computer Name", "Network ID" or "Full Computer Name"; "server string", Windows' "Computer description"!

    I noticed that Basic Setup -> Optional Settings -> Hostname should be the *default* NETBIOS Name chosen by ksmbd. But this is NOT visible in /tmp/smb.conf. There is no explanation/comment about the origin of "netbios name =" in /tmp/smb.conf!

    When I changed the value of Basic Setup -> Optional Settings -> Hostname, that value became "server string=" instead of "netbios name" in /tmp/smb.conf! This is wrong, I believe! If I blanked that field, "netbios name" in /tmp/smb.conf became Basic -> Setup -> Router Name. Router Name is mandatory, but not Hostname.

    There is a one-step delay issue with this that needs fixing! I believe it's due to the fact that both Samba Server and Basic Setup trigger a re-generation of /tmp/smb.conf!!

    I have edited this paragraph multiple times, coz it's rather confusing as I tested and observed the changes.

    For clarity, better add an item "NETBIOS Name" in Services -> NAS -> Samba Server that displays the actual workgroup computer name AND ITS ORIGIN!!

    Better, let users alter "NETBIOS Name", de-couple it from hostname (esp. in scripts). It'll be more flexible and easier to understand. But this might have impact on LAN domain's DNS records. Um....

    BTW, I hadn't mentioned /tmp/hosts. And I noticed that there was no /tmp/hostname! Smile


System Log

Samba error(s): grep -E 'wsdd|smbd' /var/log/messages
Code:

Jan  1 08:00:24 ROUTER user.info : smbd : samba started
Jan  1 08:00:24 ROUTER user.info wsdd2[1161]: starting.
Jan  1 08:00:24 ROUTER local5.err ksmbd: [ksmbd-manager/1166]: ERROR: Can't open `/tmp/ksmbd.subauth': No such file or directory
Jan  1 08:00:24 ROUTER local5.info ksmbd: [ksmbd-worker/1168]: INFO: User already exists nobody
Jan  1 08:00:24 ROUTER user.err wsdd2[1161]: error: wsdd-mcast-v4: wsd_send_soap_msg: send: Network unreachable
Jan  1 08:00:30 ROUTER user.err wsdd2[1161]: error: wsdd-mcast-v4: wsd_send_soap_msg: send: Network unreachable
Jan  1 08:00:30 ROUTER user.err wsdd2[1161]: error: wsdd-mcast-v4: wsd_send_soap_msg: send: Network unreachable
Jul 26 17:51:26 ROUTER user.info : wsdd2 : windows service discovery daemon successfully stopped
Jul 26 17:51:26 ROUTER user.err wsdd2[1161]: Terminated received.
Jul 26 17:51:26 ROUTER user.info wsdd2[1161]: terminating.
Jul 26 17:51:26 ROUTER user.info : ksmbd.mountd : samba daemon successfully stopped
Jul 26 17:51:26 ROUTER local5.info ksmbd: [ksmbd-worker/1168]: INFO: Child received signal: 15 (Terminated)
Jul 26 17:51:26 ROUTER local5.err ksmbd: [ksmbd-manager/1166]: ERROR: WARNING: child process exited abnormally: 1168
Jul 26 17:51:26 ROUTER local5.err ksmbd: [ksmbd-manager/1166]: ERROR: can't execute kill 1168: No such process
Jul 26 17:51:26 ROUTER local5.info ksmbd: [ksmbd-manager/1166]: INFO: Exiting. Bye!
Jul 26 17:51:30 ROUTER user.info wsdd2[2790]: starting.
Jul 26 17:51:30 ROUTER user.info : smbd : samba started
Jul 26 17:51:30 ROUTER local5.info ksmbd: [ksmbd-worker/2797]: INFO: User already exists nobody
Jul 26 17:51:31 ROUTER user.info : smbd : samba started
Jul 26 17:51:31 ROUTER user.info wsdd2[2866]: starting.
Jul 26 17:51:31 ROUTER user.info : smbd : samba started
Jul 26 17:51:31 ROUTER local5.info ksmbd: [ksmbd-manager/2874]: INFO: File '/tmp/ksmbd.lock' belongs to pid 2796
Jul 26 17:51:31 ROUTER user.info wsdd2[2872]: starting.
Jul 26 17:51:31 ROUTER local5.err ksmbd: [ksmbd-manager/2874]: ERROR: Failed to create lock file: File exists
Jul 26 17:51:31 ROUTER local5.info ksmbd: [ksmbd-manager/2874]: INFO: Exiting. Bye!
Jul 26 17:51:31 ROUTER local5.info ksmbd: [ksmbd-manager/2878]: INFO: File '/tmp/ksmbd.lock' belongs to pid 2796
Jul 26 17:51:31 ROUTER local5.err ksmbd: [ksmbd-manager/2878]: ERROR: Failed to create lock file: File exists
Jul 26 17:51:31 ROUTER local5.info ksmbd: [ksmbd-manager/2878]: INFO: Exiting. Bye!



_________________
Router: Asus RT-N18U (rev. A1)

May the Force and farces be with you! Live long and proper!

Facebook: https://www.facebook.com/changmanwai
Website: https://sites.google.com/site/changmw
SETI@Home profile: http://setiathome.berkeley.edu/view_profile.php?userid=211832


Last edited by mwchang on Tue Jul 27, 2021 10:48; edited 1 time in total
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 8185
Location: Netherlands

PostPosted: Mon Jul 26, 2021 13:42    Post subject: Reply with quote
Router Model: Netgear R6400v1

Firmware Version: DD-WRT v3.0-r47090M Community Build (07/26/21)
Kernel Version: Linux 4.4.276 #1 SMP Mon Jul 26 12:35:12 CEST 2021 armv7l

Upgraded from: DD-WRT v3.0-r47087M Community Build (07/22/21)
Reset: No not this time

Status: Up and running for 2 hours, basic setup as Gateway, static leases, Advanced routing, Port Forwarding, IPv4, DynDNS, 2.4 GHz and 5 GHz.
Running one WireGuard tunnel to Keepsolid and second WireGuard tunnel to own WG server for site-to-site connection.

Running three WireGuard tunnels to Mullvad in fail over group, when the first is down the next is activated automatically Smile

OpenVPN server tested and working, OpenVPN client tested and working
Errors: No

Big Thanks to BS and other forum members and developers.

_________________
Routers:Netgear R7800, R6400v1, R6400v2, Linksys EA8500, EA6900 (XvortexCFE), E2000 (converted WRT320N), WRT54GS v1.
WireGuard Documents & Guides:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=327397
OpenVPN Documents & Guides: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=327398
IPSET: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=327261
Install guide R6400v2:http://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
IONK
DD-WRT User


Joined: 19 Aug 2011
Posts: 321

PostPosted: Mon Jul 26, 2021 14:14    Post subject: Reply with quote
Router/Version: D-Link DIR-868L Rev.A1
File/Kernel: dir868a-webflash.bin / Linux 4.4.276 #3717 SMP Thu Jul 22 03:10:07 +07 2021 armv7l
Previous/Reset: DD-WRT v3.0-r47086 std (07/22/21) / no
Mode/Status: Repeater Bridge on 5GHz AC/N-Mixed (wl0 is purposely turned off) + USB Storage + lighttpd + ProFTPD + Cron / working
Issues/Errors: none

_________________
▫ RSS feed for DD-WRT releases: https://politepol.com/fd/NfCoAP5bUJXU
easyddup - A simple upgrade/downgrade utility by yoyoma2
saphirely
DD-WRT User


Joined: 13 Dec 2020
Posts: 75

PostPosted: Mon Jul 26, 2021 15:06    Post subject: Reply with quote
Router/Version: Netgear R6250
Firmware: DD-WRT v3.0-r47090 std (07/26/21)
Kernel: Linux 4.4.276 #3717 SMP Thu Jul 22 03:10:07 +07 2021 armv7l
Mode: Gateway, Wireless AP, unbound
Reset: No, not this time
Previous : r47086
Upgrade: Web and 1st succeed without reset.
Temperatures CPU 78.0 °C / WL1 56.4 °C
Load: 0.05 0.05 0.01
Uptime 1h
Errors: No, not at this moment.

Working well.
thommy181
DD-WRT User


Joined: 16 Mar 2019
Posts: 223
Location: Szczecin, Poland EU

PostPosted: Mon Jul 26, 2021 16:02    Post subject: New Build - 07/26/2021 - r47090 Reply with quote
Router/Version: Netgear WNR3500L v2
Kernel: Linux 4.4.276 #10711 Mon Jul 26 02:51:40 +07 2021 mips
Reset: No
Mode: Internet gateway, WIFI AP, Dnsmasq server
Issues/Errors: SFE feature starting many times.
Status: Working
Uptime: 4h

Device is updated via ssh. Router working rather good. Internet is available with full speed - correct with ISP plan. I'm attach start log. We will see there the SFE feature is launched many times. That's incorrect in my opinion.
Quote:

Jan 1 01:00:13 Myrouter syslog.info syslogd started: BusyBox v1.33.1
Jan 1 01:00:13 Myrouter user.info : klogd : daemon successfully started
Jan 1 01:00:13 Myrouter kern.notice kernel: klogd started: BusyBox v1.33.1 (2021-07-26 02:48:11 +07)
Jan 1 01:00:13 Myrouter kern.notice kernel: Linux version 4.4.276 (root@linux) (gcc version 11.1.0 (OpenWrt GCC 11.1.0 r16896+6-3c46ba053d) ) #10711 Mon Jul 26 02:51:40 +07 2021
Jan 1 01:00:13 Myrouter kern.info kernel: prom_init:194
Jan 1 01:00:13 Myrouter kern.info kernel: CPU0 revision is: 00019749 (MIPS 74Kc)
Jan 1 01:00:13 Myrouter kern.warn kernel: Found a AMD NAND flash with 2048B pages or 128KB blocks; total size 128MB
Jan 1 01:00:13 Myrouter kern.info kernel: Using bcma bus
Jan 1 01:00:13 Myrouter kern.info kernel: Determined physical RAM map:
Jan 1 01:00:13 Myrouter kern.info kernel: memory: 07fff000 @ 00000000 (usable)
Jan 1 01:00:13 Myrouter kern.warn kernel: Primary instruction cache 32kB, 4-way, VIPT, I-cache aliases, linesize 32 bytes.
Jan 1 01:00:13 Myrouter kern.warn kernel: Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Jan 1 01:00:13 Myrouter kern.info kernel: Zone ranges:
Jan 1 01:00:13 Myrouter kern.info kernel: Normal [mem 0x0000000000000000-0x0000000007ffefff]
Jan 1 01:00:13 Myrouter kern.info kernel: HighMem empty
Jan 1 01:00:13 Myrouter kern.info kernel: Movable zone start for each node
Jan 1 01:00:13 Myrouter kern.info kernel: Early memory node ranges
Jan 1 01:00:13 Myrouter kern.info kernel: node 0: [mem 0x0000000000000000-0x0000000007ffefff]
Jan 1 01:00:13 Myrouter kern.info kernel: Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffefff]
Jan 1 01:00:13 Myrouter kern.debug kernel: On node 0 totalpages: 32767
Jan 1 01:00:13 Myrouter kern.debug kernel: free_area_init_node: node 0, pgdat 804695a0, node_mem_map 81007000
Jan 1 01:00:13 Myrouter kern.debug kernel: Normal zone: 256 pages used for memmap
Jan 1 01:00:13 Myrouter kern.debug kernel: Normal zone: 0 pages reserved
Jan 1 01:00:13 Myrouter kern.debug kernel: Normal zone: 32767 pages, LIFO batch:7
Jan 1 01:00:13 Myrouter kern.debug kernel: pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Jan 1 01:00:13 Myrouter kern.debug kernel: pcpu-alloc: [0] 0
Jan 1 01:00:13 Myrouter kern.info kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32511
Jan 1 01:00:13 Myrouter kern.notice kernel: Kernel command line: console=ttyS0,115200 root=1f05 rootfstype=squashfs noinitrd init=/bin/sh
Jan 1 01:00:13 Myrouter kern.info kernel: PID hash table entries: 512 (order: -1, 2048 bytes)
Jan 1 01:00:13 Myrouter kern.info kernel: Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Jan 1 01:00:13 Myrouter kern.info kernel: Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Jan 1 01:00:13 Myrouter kern.info kernel: Writing ErrCtl register=00000000
Jan 1 01:00:13 Myrouter kern.info kernel: Readback ErrCtl register=00000000
Jan 1 01:00:13 Myrouter kern.info kernel: Memory: 124396K/131068K available (3676K kernel code, 179K rwdata, 780K rodata, 216K init, 611K bss, 6672K reserved, 0K cma-reserved, 0K highmem)
Jan 1 01:00:13 Myrouter kern.info kernel: SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Jan 1 01:00:13 Myrouter kern.info kernel: NR_IRQS:128
Jan 1 01:00:13 Myrouter kern.info kernel: CPU: BCM5357 rev 2 at 533 MHz
Jan 1 01:00:13 Myrouter kern.info kernel: clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7171708994 ns
Jan 1 01:00:13 Myrouter kern.info kernel: sched_clock: 32 bits at 266MHz, resolution 3ns, wraps every 8058100222ns
Jan 1 01:00:13 Myrouter kern.info kernel: console [ttyS0] enabled
Jan 1 01:00:13 Myrouter kern.info kernel: Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
Jan 1 01:00:13 Myrouter kern.info kernel: pid_max: default: 32768 minimum: 301
Jan 1 01:00:13 Myrouter kern.info kernel: Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 01:00:13 Myrouter kern.info kernel: Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 01:00:13 Myrouter kern.info kernel: BRCM Errata: Enable CPU_WAIT
Jan 1 01:00:13 Myrouter kern.info kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Jan 1 01:00:13 Myrouter kern.info kernel: futex hash table entries: 256 (order: -1, 3072 bytes)
Jan 1 01:00:13 Myrouter kern.info kernel: NET: Registered protocol family 16
Jan 1 01:00:13 Myrouter kern.warn kernel: PCI: no core
Jan 1 01:00:13 Myrouter kern.warn kernel: PCI: no core
Jan 1 01:00:13 Myrouter kern.info kernel: PCI: scanning bus
Jan 1 01:00:13 Myrouter kern.info kernel: PCI host bridge to bus 0000:00
Jan 1 01:00:13 Myrouter kern.info kernel: pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
Jan 1 01:00:13 Myrouter kern.info kernel: pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffff]
Jan 1 01:00:13 Myrouter kern.info kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:00.0: [14e4:0800] type 00 class 0x050100
Jan 1 01:00:13 Myrouter kern.warn kernel: PCI: Fixing up bridge
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:00.0: reg 0x10: [mem 0x18000000-0x18000fff]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:00.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:01.0: [14e4:4329] type 00 class 0x028000
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:01.0: reg 0x10: [mem 0x18001000-0x18001fff]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:01.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:02.0: [14e4:4715] type 00 class 0x020000
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:02.0: reg 0x10: [mem 0x18002000-0x18002fff]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:02.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:04.0: [14e4:471a] type 00 class 0x0c0310
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:04.0: reg 0x10: [mem 0x18009000-0x18009fff]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:04.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:04.1: [14e4:471a] type 00 class 0x0c0320
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:04.1: reg 0x10: [mem 0x18004000-0x18004fff]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:04.1: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:05.0: [14e4:082e] type 00 class 0x050000
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:05.0: reg 0x10: [mem 0x18005000-0x18005fff]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:05.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:06.0: [14e4:4711] type 00 class 0x040100
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:06.0: reg 0x10: [mem 0x18006000-0x18006fff]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:06.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:07.0: [14e4:080e] type 00 class 0x050000
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:07.0: reg 0x10: [mem 0x18007000-0x18007fff]
Jan 1 01:00:13 Myrouter kern.debug kernel: pci 0000:00:07.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 Myrouter kern.warn kernel: PCI: Fixing up bus
Jan 1 01:00:13 Myrouter kern.info kernel: clocksource: Switched to clocksource MIPS
Jan 1 01:00:13 Myrouter kern.info kernel: NET: Registered protocol family 2
Jan 1 01:00:13 Myrouter kern.info kernel: IP idents hash table entries: 2048 (order: 2, 16384 bytes)
Jan 1 01:00:13 Myrouter kern.info kernel: TCP established hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 01:00:13 Myrouter kern.info kernel: TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 01:00:13 Myrouter kern.info kernel: TCP: Hash tables configured (established 1024 bind 1024)
Jan 1 01:00:13 Myrouter kern.info kernel: UDP hash table entries: 256 (order: 0, 4096 bytes)
Jan 1 01:00:13 Myrouter kern.info kernel: UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Jan 1 01:00:13 Myrouter kern.info kernel: NET: Registered protocol family 1
Jan 1 01:00:13 Myrouter kern.debug kernel: PCI: CLS 0 bytes, default 32
Jan 1 01:00:13 Myrouter kern.info kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
Jan 1 01:00:13 Myrouter kern.info kernel: io scheduler noop registered (default)
Jan 1 01:00:13 Myrouter kern.info kernel: HDLC line discipline maxframe=4096
Jan 1 01:00:13 Myrouter kern.info kernel: N_HDLC line discipline registered.
Jan 1 01:00:13 Myrouter kern.info kernel: serial8250_init
Jan 1 01:00:13 Myrouter kern.info kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Jan 1 01:00:13 Myrouter kern.info kernel: serial8250: ttyS0 at MMIO 0x0 (irq = 8, base_baud = 1250000) is a U6_16550A
Jan 1 01:00:13 Myrouter kern.info kernel: brd: module loaded
Jan 1 01:00:13 Myrouter kern.err kernel: pflash: found no supported devices
Jan 1 01:00:13 Myrouter kern.warn kernel: ERROR: Unknown flash, device_id:0x00
Jan 1 01:00:13 Myrouter kern.err kernel: bcmsflash: found no supported devices
Jan 1 01:00:13 Myrouter kern.debug kernel: Bad block table found at page 65472, version 0x01
Jan 1 01:00:13 Myrouter kern.debug kernel: Bad block table found at page 65408, version 0x01
Jan 1 01:00:13 Myrouter kern.notice kernel: Creating 2 MTD partitions on "brcmnand":
Jan 1 01:00:13 Myrouter kern.notice kernel: 0x000000500000-0x000002000000 : "linux"
Jan 1 01:00:13 Myrouter kern.notice kernel: 0x000004000000-0x000007f00000 : "ddwrt"
Jan 1 01:00:13 Myrouter kern.warn kernel: Boot partition size = 524288(0x80000)
Jan 1 01:00:13 Myrouter kern.warn kernel: lookup_nflash_rootfs_offset: offset = 0x500000
Jan 1 01:00:13 Myrouter kern.notice kernel: found trx at 500000, len =26288128
Jan 1 01:00:13 Myrouter kern.notice kernel: scan filesys at 690000
Jan 1 01:00:13 Myrouter kern.notice kernel: nflash: squash filesystem with lzma found at offset 500000
Jan 1 01:00:13 Myrouter kern.notice kernel: Creating 4 MTD partitions on "nflash":
Jan 1 01:00:13 Myrouter kern.notice kernel: 0x000000000000-0x000000080000 : "cfe"
Jan 1 01:00:13 Myrouter kern.notice kernel: 0x000000080000-0x000000200000 : "nvram"
Jan 1 01:00:13 Myrouter kern.notice kernel: 0x000000500000-0x000002000000 : "nandimage"
Jan 1 01:00:13 Myrouter kern.notice kernel: 0x000000690000-0x000002000000 : "rootfs"
Jan 1 01:00:13 Myrouter kern.notice kernel: mtd: partition "rootfs" set to be root filesystem
Jan 1 01:00:13 Myrouter kern.info kernel: add netgear boarddata for pflash if exists
Jan 1 01:00:13 Myrouter kern.info kernel: add netgear boarddata for sflash if exists
Jan 1 01:00:13 Myrouter kern.info kernel: PPP generic driver version 2.4.2
Jan 1 01:00:13 Myrouter kern.info kernel: PPP BSD Compression module registered
Jan 1 01:00:13 Myrouter kern.info kernel: PPP Deflate Compression module registered
Jan 1 01:00:13 Myrouter kern.info kernel: PPP MPPE Compression module registered
Jan 1 01:00:13 Myrouter kern.info kernel: NET: Registered protocol family 24
Jan 1 01:00:13 Myrouter kern.info kernel: Broadcom Watchdog Timer: 0.07 initialized.
Jan 1 01:00:13 Myrouter kern.info kernel: GACT probability NOT on
Jan 1 01:00:13 Myrouter kern.info kernel: Mirror/redirect action on
Jan 1 01:00:13 Myrouter kern.info kernel: Simple TC action Loaded
Jan 1 01:00:13 Myrouter kern.info kernel: netem: version 1.3
Jan 1 01:00:13 Myrouter kern.info kernel: u32 classifier
Jan 1 01:00:13 Myrouter kern.info kernel: Performance counters on
Jan 1 01:00:13 Myrouter kern.info kernel: input device check on
Jan 1 01:00:13 Myrouter kern.info kernel: Actions configured
Jan 1 01:00:13 Myrouter kern.info kernel: Netfilter messages via NETLINK v0.30.
Jan 1 01:00:13 Myrouter kern.info kernel: nf_conntrack version 0.5.0 (1943 buckets, 7772 max)
Jan 1 01:00:13 Myrouter kern.warn kernel: nf_conntrack_rtsp v0.7 loading
Jan 1 01:00:13 Myrouter kern.info kernel: xt_time: kernel timezone is -0000
Jan 1 01:00:13 Myrouter kern.info kernel: gre: GRE over IPv4 demultiplexor driver
Jan 1 01:00:13 Myrouter kern.warn kernel: nf_nat_rtsp v0.7 loading
Jan 1 01:00:13 Myrouter kern.info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 01:00:13 Myrouter kern.info kernel: NET: Registered protocol family 17
Jan 1 01:00:13 Myrouter kern.info kernel: bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Jan 1 01:00:13 Myrouter kern.notice kernel: Bridge firewalling registered
Jan 1 01:00:13 Myrouter kern.info kernel: 8021q: 802.1Q VLAN Support v1.8
Jan 1 01:00:13 Myrouter kern.info kernel: startup nvram driver
Jan 1 01:00:13 Myrouter kern.emerg kernel: found nvram
Jan 1 01:00:13 Myrouter kern.info kernel: max nvram space = 65536
Jan 1 01:00:13 Myrouter kern.info kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
Jan 1 01:00:13 Myrouter kern.info kernel: Freeing unused kernel memory: 216K
Jan 1 01:00:13 Myrouter kern.info kernel: create ctf proc
Jan 1 01:00:13 Myrouter kern.warn kernel: et_module_init: passivemode set to 0x0
Jan 1 01:00:13 Myrouter kern.warn kernel: et_module_init: txworkq set to 0x0
Jan 1 01:00:13 Myrouter kern.warn kernel: et_module_init: et_txq_thresh set to 0xce4
Jan 1 01:00:13 Myrouter kern.warn kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Jan 1 01:00:13 Myrouter kern.warn kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Jan 1 01:00:13 Myrouter kern.warn kernel: et_module_init: et_rxlazy_dyn_thresh set to 0
Jan 1 01:00:13 Myrouter kern.info kernel: robo attach
Jan 1 01:00:13 Myrouter kern.info kernel: robo id 3115
Jan 1 01:00:13 Myrouter kern.info kernel: attach ctf for eth%d
Jan 1 01:00:13 Myrouter kern.info kernel: _ctf_attach:attach eth%d
Jan 1 01:00:13 Myrouter kern.info kernel: bind ctf to eth if
Jan 1 01:00:13 Myrouter kern.warn kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.164.18 (r692288)
Jan 1 01:00:13 Myrouter kern.warn kernel: wl: module license 'Proprietary' taints kernel.
Jan 1 01:00:13 Myrouter kern.warn kernel: Disabling lock debugging due to kernel taint
Jan 1 01:00:13 Myrouter kern.info kernel: _ctf_attach:attach wl0
Jan 1 01:00:13 Myrouter kern.info kernel: switch id 15
Jan 1 01:00:13 Myrouter kern.info kernel: switch id32 53115
Jan 1 01:00:13 Myrouter kern.info kernel: b5301x_common: found switch: BCM53115, rev 8
Jan 1 01:00:13 Myrouter kern.info kernel: bcm_robo_config_vlan_fun vid=1, vlan->members=0x11e, vlan->untag=0x1e
Jan 1 01:00:13 Myrouter kern.info kernel: bcm_robo_config_vlan_fun ports=1 2 3 4 8t
Jan 1 01:00:13 Myrouter kern.info kernel: bcm_robo_config_vlan_fun vid=2, vlan->members=0x101, vlan->untag=0x101
Jan 1 01:00:13 Myrouter kern.info kernel: bcm_robo_config_vlan_fun ports=0 8
Jan 1 01:00:13 Myrouter user.info : resetbutton : resetbutton daemon successfully started
Jan 1 01:00:13 Myrouter kern.info kernel: device eth0 entered promiscuous mode
Jan 1 01:00:13 Myrouter kern.info kernel: bcm_robo_config_vlan_fun vid=1, vlan->members=0x118, vlan->untag=0x18
Jan 1 01:00:13 Myrouter kern.info kernel: bcm_robo_config_vlan_fun ports=3 4 8t
Jan 1 01:00:13 Myrouter kern.info kernel: bcm_robo_config_vlan_fun vid=2, vlan->members=0x101, vlan->untag=0x1
Jan 1 01:00:13 Myrouter kern.info kernel: bcm_robo_config_vlan_fun ports=0 8t
Jan 1 01:00:13 Myrouter user.info : bridge : bridge br0 successfully added
Jan 1 01:00:14 Myrouter user.info : bridge : bridge br0 successfully added
Jan 1 01:00:14 Myrouter kern.info kernel: device br0 entered promiscuous mode
Jan 1 01:00:14 Myrouter kern.info kernel: device eth0 left promiscuous mode
Jan 1 01:00:14 Myrouter kern.info kernel: device eth0 entered promiscuous mode
Jan 1 01:00:14 Myrouter kern.info kernel: device eth0 left promiscuous mode
Jan 1 01:00:14 Myrouter user.info : bridge : interface vlan1 successfully added to bridge br0
Jan 1 01:00:14 Myrouter kern.info kernel: device eth0 entered promiscuous mode
Jan 1 01:00:14 Myrouter kern.info kernel: device vlan1 entered promiscuous mode
Jan 1 01:00:14 Myrouter kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 1 01:00:14 Myrouter kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 1 01:00:15 Myrouter user.info : bridge : interface eth1 successfully added to bridge br0
Jan 1 01:00:15 Myrouter kern.info kernel: device eth1 entered promiscuous mode
Jan 1 01:00:15 Myrouter kern.info kernel: br0: port 2(eth1) entered forwarding state
Jan 1 01:00:15 Myrouter kern.info kernel: br0: port 2(eth1) entered forwarding state
Jan 1 01:00:15 Myrouter kern.info kernel: device br0 left promiscuous mode
Jan 1 01:00:15 Myrouter kern.info kernel: device br0 entered promiscuous mode
Jan 1 01:00:15 Myrouter kern.info kernel: device br0 left promiscuous mode
Jan 1 01:00:15 Myrouter kern.info kernel: device eth0 left promiscuous mode
Jan 1 01:00:15 Myrouter kern.info kernel: br0: port 1(vlan1) entered disabled state
Jan 1 01:00:15 Myrouter kern.info kernel: device eth0 entered promiscuous mode
Jan 1 01:00:15 Myrouter kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 1 01:00:15 Myrouter kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 1 01:00:15 Myrouter user.info : bridge : interface vlan1 successfully added to bridge br0
Jan 1 01:00:15 Myrouter kern.info kernel: device eth0 left promiscuous mode
Jan 1 01:00:15 Myrouter kern.info kernel: br0: port 1(vlan1) entered disabled state
Jan 1 01:00:15 Myrouter kern.info kernel: device eth0 entered promiscuous mode
Jan 1 01:00:15 Myrouter kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 1 01:00:15 Myrouter kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 1 01:00:15 Myrouter user.info : bridge : interface vlan1 successfully added to bridge br0
Jan 1 01:00:15 Myrouter kern.info kernel: bcm_robo_config_vlan_fun vid=1, vlan->members=0x118, vlan->untag=0x18
Jan 1 01:00:15 Myrouter kern.info kernel: bcm_robo_config_vlan_fun ports=3 4 8t
Jan 1 01:00:15 Myrouter kern.info kernel: bcm_robo_config_vlan_fun vid=2, vlan->members=0x101, vlan->untag=0x1
Jan 1 01:00:15 Myrouter kern.info kernel: bcm_robo_config_vlan_fun ports=0 8t
Jan 1 01:00:16 Myrouter kern.info kernel: device vlan2 entered promiscuous mode
Jan 1 01:00:16 Myrouter user.info : klogd : kernel log daemon successfully stopped
Jan 1 01:00:16 Myrouter user.info : sfe : shortcut forwarding engine successfully stopped
Jan 1 01:00:16 Myrouter kern.info kernel: CTF: disabled
Jan 1 01:00:16 Myrouter kern.notice kernel: klogd: exiting
Jan 1 01:00:17 Myrouter user.info : syslogd : syslog daemon successfully stopped
Jan 1 01:00:17 Myrouter syslog.info syslogd exiting
Jan 1 01:00:17 Myrouter syslog.info syslogd started: BusyBox v1.33.1
Jan 1 01:00:17 Myrouter user.info : klogd : daemon successfully started
Jan 1 01:00:17 Myrouter kern.notice kernel: klogd started: BusyBox v1.33.1 (2021-07-26 02:48:11 +07)
Jan 1 01:00:17 Myrouter user.info : cron : daemon successfully started
Jan 1 01:00:17 Myrouter cron.info cron[1388]: (CRON) STARTUP (fork ok)
Jan 1 01:00:17 Myrouter user.info : wland : daemon successfully started
Jan 1 01:00:20 Myrouter user.info : dnsmasq : daemon successfully started
Jan 1 01:00:21 Myrouter daemon.info httpd[1391]: httpd : httpd SSL server started at port 443
Jan 1 01:00:22 Myrouter kern.alert kernel: fast-classifier (PBR safe v2.1.6b): starting up
Jan 1 01:00:22 Myrouter kern.alert kernel: fast-classifier: registered
Jan 1 01:00:22 Myrouter user.info : sfe : shortcut forwarding engine successfully started
Jan 1 01:00:22 Myrouter kern.info kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 01:00:23 Myrouter user.info : sfe : shortcut forwarding engine successfully started
Jan 1 01:00:23 Myrouter kern.info kernel: device vlan2 left promiscuous mode
Jan 1 01:00:23 Myrouter user.info : ttraff : traffic counter daemon successfully started
Jan 1 01:00:25 Myrouter user.info : nas : wait for network init
Jan 1 01:00:30 Myrouter kern.info kernel: br0: port 2(eth1) entered forwarding state
Jan 1 01:00:30 Myrouter kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 1 01:00:35 Myrouter user.info : nas : start nas lan
Jan 1 01:00:35 Myrouter user.info : nas : start nas for wl0
Jan 1 01:00:35 Myrouter user.info : nas : NAS lan (wl0 interface) successfully started
Jan 1 01:00:36 Myrouter user.info : nas : daemon successfully stopped
Jan 1 01:00:36 Myrouter user.info : nas : start nas lan
Jan 1 01:00:36 Myrouter user.info : nas : start nas for wl0
Jan 1 01:00:36 Myrouter user.info : nas : NAS lan (wl0 interface) successfully started
Jan 1 01:00:36 Myrouter user.info : httpd : daemon successfully stopped
Jan 1 01:00:37 Myrouter daemon.info httpd[1391]: httpd : httpd server shutdown
Jan 1 01:00:37 Myrouter user.info : httpd : https daemon successfully started
Jan 1 01:00:37 Myrouter daemon.info httpd[1594]: httpd : httpd SSL server started at port 443
Jan 1 01:01:04 Myrouter kern.notice kernel: random: nonblocking pool is initialized
Jan 1 01:01:04 Myrouter user.info : dropbear : ssh daemon successfully started
Jan 1 01:01:04 Myrouter authpriv.info dropbear[1605]: Running in background
Jan 1 01:01:04 Myrouter user.info : httpd : https daemon successfully started
Jan 1 01:01:04 Myrouter user.info : resetbutton : daemon successfully stopped
Jan 1 01:01:04 Myrouter user.info : resetbutton : resetbutton daemon successfully started
Jan 1 01:01:08 Myrouter daemon.info httpd[1609]: httpd : Authentication fail
Jan 1 01:01:08 Myrouter daemon.err httpd[1609]: httpd : Request Error Code 401: Authorization required. Wrong username and/or password!
Jan 1 01:02:22 Myrouter authpriv.info dropbear[1808]: Child connection from X
Jan 1 01:02:28 Myrouter authpriv.notice dropbear[1808]: Password auth succeeded for 'root' from X
flyzipper
DD-WRT Guru


Joined: 21 Feb 2016
Posts: 504

PostPosted: Tue Jul 27, 2021 1:06    Post subject: Reply with quote
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r47090 std (07/26/21)
Kernel: Linux 4.4.276 #3717 SMP Thu Jul 22 03:10:07 +07 2021 armv7l
Previous: r47086
Mode/Status: Gateway / working
Issues/Errors: Working well so far.

Uptime: 6hrs 34mins
Upgrade: via web UI, no issues
Reset: no
Temperatures: CPU 73.6 °C / WL0 49.0 °C / WL1 54.8 °C
cameloid
DD-WRT Novice


Joined: 27 Jul 2021
Posts: 2

PostPosted: Tue Jul 27, 2021 2:41    Post subject: Netgear R8500 - Broken VHT160 support Reply with quote
Router Model: Netgear R8500
Firmware Version: DD-WRT v3.0-r47090 std (07/26/21)
Kernel Version: Linux 4.4.276 #3723 SMP Mon Jul 26 02:49:12 +07 2021 armv7l
Mode: AP only
File: https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2021/07-26-2021-r47090/netgear-r8500/netgear-r8500-webflash.bin

Issue

Possibly it's a long-time known issue but I've just upgraded to the latest build (which I normally do like twice a year) and it seems that VHT160 stopped working on my 5 GHz radios. The corresponding setting is just unavailable in the "Channel Width" drop-down menu, and both 5 GHz radios default to VHT80 giving me only 173/173 Mbps speeds.

Also, beamforming seems to be broken, too. When I enable it (tried a combination of explicit + implicit), I can still connect to an AP but the speeds are extremely low (like 10 Mbps) accompanied by massive packet loss.

My regulatory domain is Singapore, just in case it makes any difference. For other settings, see the screen shot attached.

What exactly am I missing? I did some basic googling and ran through changelogs before asking. Unfortunately, couldn't find any direct answer. I tried the 'brcm_unlock=1' setting as mentioned in the OP (although it didn't seem quite related) with no result. Sorry again if those issues are well-known.



Screenshot 2021-07-27 104127.png
 Description:
 Filesize:  50.19 KB
 Viewed:  1826 Time(s)

Screenshot 2021-07-27 104127.png




Last edited by cameloid on Tue Jul 27, 2021 4:31; edited 4 times in total
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 10206
Location: Texas, USA

PostPosted: Tue Jul 27, 2021 2:44    Post subject: Reply with quote
Note and word to the wise: Read the OP, don't ask stupid questions. Everything you need to know is in the OP or in the flash reports.
_________________
Official Forum Rules, Guidelines & Helpful InformationFirmware FAQInstallation WikiWhere Do I Download Firmware‽
DON'T use Chromium-based browsersRTFM/STFW TL;DR is NOT an excuse. • Why Should I Care What Color the Bikeshed Is‽
Please DO NOT PM me with questions; Ask in the forum. ---------------------- Linux User #377467 counter.li.org / linuxcounter.net
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 3161

PostPosted: Tue Jul 27, 2021 4:28    Post subject: Reply with quote
cameloid wrote:
What exactly am I missing?
Some posts were deleted and trust this bold statement is not directed towards you, so only a coincidence. =)

BTW what was the previous build? If too old you might have to invert your extension channel to upper upper.

Also, avoid using any auto channel select. https://forum.dd-wrt.com/wiki/index.php/Basic_Wireless_Settings
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 10206
Location: Texas, USA

PostPosted: Tue Jul 27, 2021 5:13    Post subject: Reply with quote
I guess I will have to do more cleanup on aisle 5 later Cool
_________________
Official Forum Rules, Guidelines & Helpful InformationFirmware FAQInstallation WikiWhere Do I Download Firmware‽
DON'T use Chromium-based browsersRTFM/STFW TL;DR is NOT an excuse. • Why Should I Care What Color the Bikeshed Is‽
Please DO NOT PM me with questions; Ask in the forum. ---------------------- Linux User #377467 counter.li.org / linuxcounter.net
MrPickles
DD-WRT User


Joined: 14 Jan 2017
Posts: 50

PostPosted: Tue Jul 27, 2021 6:30    Post subject: Reply with quote
R7000 here ...

Finally able to format a NAS USB to ExFat through the dd-wrt firmware, and use Samba 3.11 to connect to shares. Previously, had to use Samba 2.10 as the Max protocol.

Where, I can utilize Linux & other manufacturers to read & write to the NAS USB attached to the router.

Thank you!
cameloid
DD-WRT Novice


Joined: 27 Jul 2021
Posts: 2

PostPosted: Tue Jul 27, 2021 6:43    Post subject: Reply with quote
blkt wrote:
cameloid wrote:
What exactly am I missing?
Some posts were deleted and trust this bold statement is not directed towards you, so only a coincidence. =)

BTW what was the previous build? If too old you might have to invert your extension channel to upper upper.

Also, avoid using any auto channel select. https://forum.dd-wrt.com/wiki/index.php/Basic_Wireless_Settings


Okay, here are my findings.

1. To exclude potential edge effects of the upgrade from the previous build, I have reset the device to factory settings.

2. According to you instruction, I have assigned designated channel numbers to all three radios (even though I never experienced any problems with the 'Auto' setting before).

There's not a lot of flexibility available here, by the way. When you choose Singapore as your regulatory domain, and then select the maximum 'Channel Width' (VHT80 for 5 GHz and VHT40 for 2.4 GHz), the choice of channels narrows down to 161 for wl0, 5-13 for wl0, and 48 for wl2. In other words, there's nothing to choose from when it comes to the 5 GHz spectrum.

3. I have also adjusted the extension channels as per the guidance on this page: https://forum.dd-wrt.com/wiki/index.php/Basic_Wireless_Settings

This din't help much. The speeds I'm getting are still limited to 173/173, and VHT160 channel width is not available (but it used to be in the previous builds).

Hope this helps.
mwchang
DD-WRT Guru


Joined: 26 Mar 2013
Posts: 856
Location: Hung Hom, Hong Kong

PostPosted: Tue Jul 27, 2021 10:40    Post subject: Reply with quote
cameloid wrote:
There's not a lot of flexibility available here, by the way. When you choose Singapore as your regulatory domain, and then select the maximum 'Channel Width' (VHT80 for 5 GHz and VHT40 for 2.4 GHz), the choice of channels narrows down to 161 for wl0, 5-13 for wl0, and 48 for wl2. In other words, there's nothing to choose from when it comes to the 5 GHz spectrum


Is "Rgulatory Domain" really important and useful? I've never touched it, keeping it "United States"... Smile


_________________
Router: Asus RT-N18U (rev. A1)

May the Force and farces be with you! Live long and proper!

Facebook: https://www.facebook.com/changmanwai
Website: https://sites.google.com/site/changmw
SETI@Home profile: http://setiathome.berkeley.edu/view_profile.php?userid=211832
kushwavez
DD-WRT Novice


Joined: 15 Jun 2020
Posts: 32

PostPosted: Tue Jul 27, 2021 10:44    Post subject: Reply with quote
Router/Version: ASUS RT-AC56U
File/Kernel: DD-WRT v3.0-r47090 std (07/26/21) / Linux 4.4.276 #3717 SMP Thu Jul 22 03:10:07 +07 2021 armv7l
Previous/Reset: DD-WRT v3.0-r47086 std (07/22/21) / No
Mode/Status: Gateway, WireGuard, DHCP, QoS Off, CTF
Issues/Errors:

Flow Acceleration is not showing up in GUI.
According to the wiki, the chip is supported (Northstar).

Log:
Code:

[...]
Jan  1 01:00:11 RT-AC56U-VPN kern.info kernel: attaching FA
Jan  1 01:00:11 RT-AC56U-VPN kern.info kernel: CHIPID 53010, rev 2
Jan  1 01:00:11 RT-AC56U-VPN kern.info kernel: not FA capable
[...]


More info here: https://svn.dd-wrt.com/ticket/7444



rtac56u-r47090_syslog_kernlog.txt
 Description:

Download
 Filename:  rtac56u-r47090_syslog_kernlog.txt
 Filesize:  46.74 KB
 Downloaded:  24 Time(s)

Goto page 1, 2  Next Display posts from previous:    Page 1 of 2
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum