New Build - 09/10/2020 - r44340

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
hurleyp
DD-WRT User


Joined: 10 Sep 2009
Posts: 313
Location: Ottawa, Ontario, Canada

PostPosted: Sat Sep 12, 2020 13:32    Post subject: Reply with quote
Firmware: v3.0-r44340 std (09/10/20)
Router/Version: Netgear R7000
Kernel: Linux 4.4.235 #1025 SMP Wed Sep 9 09:23:50 +04 2020 armv7l
Previous: v3.0-r44251 std (08/27/20)
Mode/Status: AP wired and wireless, Up and running for 1 day
Reset: Soft boot before and after upgrade
Temperatures: CPU 60.2 °C / WL0 46.5 °C / WL1 51.6 °C
Issues/Errors: Nothing significant

Updated via webif. No 'nvram erase' this time, last one was in July 2018 (r36325).

There is a minor issue with the packet count on wl0.1 and "Connected Clients" stuck at zero. The wl0 and wl1 counts seem correct.
Upload and Download speeds are good. Nothing unexpected in the syslog. GRC port probe shows "stealth".

Current basic R7000 setup (subject to change of course):
- Static WAN IP
- SFE - On
- STP - On
- IPv4 only, both WAN and LAN
- LAN DHCP Enabled
- Wireless: AP, Regulatory Domain = CANADA, wl0 Mixed (ch. 6), wl1 AC/N-Mixed (ch. 149, VHT80), AES
- 1 wireless VLAN on wl0
- SNMP disabled, SSH enabled, Telnet disabled
- Firewall enabled, Log Level high
- Syslog: to local server. klogd: disabled.
- USB support - Off
- No custom scripts
- NO: ttraf, Tor, VNC, Zabbix, VPN, Radius
- NO: UPnP, DMZ, QoS
- NO: Samba, CIFS, JFFS2, miniDLNA, Entware, Optware

_________________
Netgear R7000: v3.0-r46604 std (05/09/21)
EdgeRouter-X: EdgeOS v2.0.9-hotfix 1
Sponsor
ikwyl6
DD-WRT Novice


Joined: 23 Apr 2013
Posts: 25

PostPosted: Sat Sep 12, 2020 14:20    Post subject: Reply with quote
Router/Version: Netgear R7000
File: netgear-r7000-webflash.bin
Firmware: DD-WRT v3.0-r44340 std (09/10/20) (prev. DD-WRT v3.0-r43324 std (06/02/20) )
Kernel: Linux 4.4.235 #1025 SMP Wed Sep 9 09:23:50 +04 2020 armv7l
Mode: AP
Reset: Yes (used web gui factory reset before upgrade and then 'nvram erase && reboot' after flashing updated webflash.bin file and manually added settings back in)
Status: 10h up, fine.

_________________
[ NetGear R7000 : DD-WRT v3.0-r44340 std (09/10/20) - Local dnsmasq with caching using syslogd to send logs to remove server
TP-Link Archer C5 Stock Firmware
TP-Link Archer A9 Stock Firmware - Not Being Used ]
thommy181
DD-WRT User


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

PostPosted: Sat Sep 12, 2020 16:20    Post subject: New Build - 09/10/2020 - r44340 Reply with quote
Router: Netgear WNR3500L v2
Kernel: Linux 4.4.235 #3788 Thu Sep 10 14:35:56 +04 2020 mips
Mode: Internet gateway and WIFI AP
Reset: No
Status: Working
Errors: Nothing significant
Uptime: -> 28h

Device is updated via ssh. Router working rather good. I don't see any significant problems.
kristianissimo
DD-WRT Novice


Joined: 12 Sep 2020
Posts: 3

PostPosted: Sat Sep 12, 2020 22:40    Post subject: DD-WRT Build r44340 (09/10/2020) Mega on ASUS RT-N66U Reply with quote
Router:
ASUS RT-N66U (Dark Knight) ver. B1
Broadcom BCM5300 chip rev 1
CPU Features MIPS32r1 MIPS32r2 MIPS16 DSP DSP2
CFE 1.0.19 64k

Version: DD-WRT v3.0-r44340 mega 09/10/20
File: dd-wrt.v24-44340_NEWD-2_K3.x_mega_RT-N66U.trx
Kernel: Linux 4.4.235 #3804 Thu Sep 10 14:56:20 +04 2020 mips
Previous: ASUS stock firmware 3.0.0.4.382_51640
Reset: No
Mode: Internet gateway - router
Status: Working
Issues/Errors: No WiFi 2,4 GHz (only WiFi 5 GHz is working)

dmesg
Quote:
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65022
Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd init=/bin/sh
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Writing ErrCtl register=800001c0
Readback ErrCtl register=800001c0
Cache parity protection enabled
Memory: 235908K/262136K available (5490K kernel code, 455K rwdata, 996K rodata, 280K init, 372K bss, 26228K reserved, 0K cma-reserved, 131068K highmem)
SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:128
CPU: BCM5300 rev 1 at 600 MHz
clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370868154 ns
sched_clock: 32 bits at 300MHz, resolution 3ns, wraps every 7158278654ns
console [ttyS0] enabled
Calibrating delay loop... 299.82 BogoMIPS (lpj=1499136)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
BRCM Errata: Disable CPU_WAIT
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 256 (order: -1, 3072 bytes)
NET: Registered protocol family 16
enable BCMA BUS Errata
boardflags are 110
PCI: Initializing host
PCI: Reset RC
boardflags are 110
PCI: Initializing host
PCI: Reset RC
PCI: scanning bus 0
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
pci 0000:00:00.0: [14e4:0800] type 00 class 0x050100
PCI: Fixing up bridge
pci 0000:00:00.0: reg 0x10: [mem 0x18000000-0x18000fff]
pci 0000:00:00.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:01.0: [14e4:4715] type 00 class 0x020000
pci 0000:00:01.0: reg 0x10: [mem 0x18002000-0x18002fff]
pci 0000:00:01.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:04.0: [14e4:471a] type 00 class 0x0c0310
pci 0000:00:04.0: reg 0x10: [mem 0x18009000-0x18009fff]
pci 0000:00:04.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:04.1: [14e4:471a] type 00 class 0x0c0320
pci 0000:00:04.1: reg 0x10: [mem 0x18004000-0x18004fff]
pci 0000:00:04.1: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:05.0: [14e4:0820] type 01 class 0x060400
pci 0000:00:05.0: reg 0x10: [mem 0x18005000-0x18005fff]
pci 0000:00:05.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
pci 0000:00:06.0: [14e4:0820] type 01 class 0x060400
pci 0000:00:06.0: reg 0x10: [mem 0x1800e000-0x1800efff]
pci 0000:00:06.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
pci 0000:00:07.0: [14e4:052e] type 00 class 0xffffff
pci 0000:00:07.0: reg 0x10: [mem 0x18006000-0x18006fff]
pci 0000:00:07.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:08.0: [14e4:080e] type 00 class 0x050000
pci 0000:00:08.0: reg 0x10: [mem 0x18007000-0x18007fff]
pci 0000:00:08.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:09.0: [14e4:0534] type 00 class 0xffffff
pci 0000:00:09.0: reg 0x10: [mem 0x18008000-0x18008fff]
pci 0000:00:09.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
PCI: Fixing up bus 0
pci 0000:00:05.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0000:00:06.0: bridge configuration invalid ([bus 00-00]), reconfiguring
PCI/PCIe coreunit 0 is set to bus 1.
pci 0000:01:00.0: [14e4:5300] type 00 class 0x060000
pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x07ffffff 64bit]
pci 0000:01:00.0: supports D1 D2
pci 0000:01:00.1: [14e4:0000] type 00 class 0x060000
pci 0000:01:00.1: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:01:00.1: reg 0x18: [mem 0x00000000-0x07ffffff 64bit]
pci 0000:01:00.1: supports D1 D2
pci 0000:01:01.0: [14e4:4331] type 00 class 0x028000
pci 0000:01:01.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:01:01.0: supports D1 D2
PCI: Fixing up bus 1
pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
PCI/PCIe coreunit 1 is set to bus 2.
pci 0000:02:00.0: [14e4:5300] type 00 class 0x060000
pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:02:00.0: reg 0x18: [mem 0x00000000-0x07ffffff 64bit]
pci 0000:02:00.0: supports D1 D2
pci 0000:02:00.1: [14e4:0000] type 00 class 0x060000
pci 0000:02:00.1: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:02:00.1: reg 0x18: [mem 0x00000000-0x07ffffff 64bit]
pci 0000:02:00.1: supports D1 D2
pci 0000:02:01.0: [14e4:4331] type 00 class 0x028000
pci 0000:02:01.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:02:01.0: supports D1 D2
PCI: Fixing up bus 2
pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
clocksource: Switched to clocksource MIPS
NET: Registered protocol family 2
TCP established hash table entries: 1024 (order: 0, 4096 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
PCI: CLS 0 bytes, default 32
Asus-RT-N66U init
Asus-RT-N66U init
squashfs: version 4.0 (2009/01/31) Phillip Lougher
bounce: pool size: 64 pages
io scheduler noop registered (default)
HDLC line discipline maxframe=4096
N_HDLC line discipline registered.
serial8250_init
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 8, base_baud = 1562500) is a U6_16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 8, base_baud = 1562500) is a U6_16550A
brd: module loaded
Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x002201
Amd/Fujitsu Extended Query Table at 0x0040
Amd/Fujitsu Extended Query version 1.3.
number of CFI chips: 1
Flash device: 0x2000000 at 0x1c000000
try to find cfe size up to 33554432
bootloader size: 262144
nvram size: 65536
Physically mapped flash: Filesystem type: squashfs, size=0x522306
partition size = 5427200
Creating 5 MTD partitions on "Physically mapped flash":
0x000000000000-0x000000040000 : "cfe"
0x000000040000-0x000001fe0000 : "linux"
0x000000253000-0x000000780000 : "rootfs"
mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
mtd: partition "rootfs" set to be root filesystem
0x000001fe0000-0x000002000000 : "nvram"
0x000000780000-0x000001fe0000 : "ddwrt"
ERROR: Unknown flash, device_id:0x00
bcmsflash: found no supported devices
No NAND flash type found
brcmnand: found no supported devices
No NAND flash type found
nflash: found no supported devices
et_module_init: passivemode set to 0x0
et_module_init: txworkq set to 0x0
et_module_init: et_txq_thresh set to 0xce4
et_module_init: et_rxlazy_timeout set to 0x3e8
et_module_init: et_rxlazy_framecnt set to 0x20
et_module_init: et_rxlazy_dyn_thresh set to 0
ET Corerev -2147483648
bcm_robo_enable_switch: EEE is disabled
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
cmd 2 new_cmd 0
PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
cmd 2 new_cmd 0
PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
Broadcom Watchdog Timer: 0.07 initialized.
u32 classifier
Performance counters on
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (3686 buckets, 14744 max)
nf_conntrack_rtsp v0.7 loading
xt_time: kernel timezone is -0000
ip_set: protocol 6
gre: GRE over IPv4 demultiplexor driver
nf_nat_rtsp v0.7 loading
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 17
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
startup nvram driver
found nvram
max nvram space = 65536
VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Freeing unused kernel memory: 280K
roboswitch: Probing device 'eth0'
roboswitch: trying a 53125! at eth0
roboswitch: found a 53125! at eth0
device br0 entered promiscuous mode
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device vlan2 entered promiscuous mode
fast-classifier (PBR safe v2.1.6b): starting up
fast-classifier: registered
device vlan2 left promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
random: nonblocking pool is initialized
nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
device vlan1 left promiscuous mode
device eth0 left promiscuous mode
br0: port 1(vlan1) entered disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entered disabled state
device br0 entered promiscuous mode
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
br0: port 1(vlan1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device eth1 entered promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device vlan2 entered promiscuous mode
device vlan2 left promiscuous mode
br0: port 1(vlan1) entered forwarding state
br0: port 2(eth1) entered forwarding state
wabe
DD-WRT Guru


Joined: 17 Jun 2006
Posts: 795

PostPosted: Sun Sep 13, 2020 15:25    Post subject: Reply with quote
Router/Version: Asus RT-AC68U rev. A1
File: asus_ac68u-firmware.trx
Firmware: DD-WRT v3.0-r44340 std (09/10/20)
Kernel: Linux 4.4.235 #1025 SMP Wed Sep 9 09:23:50 +04 2020 armv7l
Mode: Gateway / AP
Reset: No, flashed from command line
Status: Everything seems to work quite well

_________________
AC-68U rev. C1 on Build 46604
AC-68U rev. A1 on Build 46446
AC-68U rev. A1 on Build 46069
twindragon6
DD-WRT User


Joined: 29 Jun 2008
Posts: 180

PostPosted: Sun Sep 13, 2020 17:28    Post subject: Netgear Nighthawk R7000 Reply with quote
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r44340 std (09/10/20)
Kernel: Linux 4.4.235 #1025 SMP Wed Sep 9 09:23:50 +04 2020 armv7l
Mode: Gateway
Reset: No
Previous: 08-28-2020-r44251
Status: Working, so far



Logs.txt
 Description:
Logs

Download
 Filename:  Logs.txt
 Filesize:  38.54 KB
 Downloaded:  33 Time(s)

BrainSlayer
Site Admin


Joined: 06 Jun 2006
Posts: 7126
Location: Dresden, Germany

PostPosted: Mon Sep 14, 2020 13:38    Post subject: Re: DD-WRT Build r44340 (09/10/2020) Mega on ASUS RT-N66U Reply with quote
kristianissimo wrote:
Router:
ASUS RT-N66U (Dark Knight) ver. B1
Broadcom BCM5300 chip rev 1
CPU Features MIPS32r1 MIPS32r2 MIPS16 DSP DSP2
CFE 1.0.19 64k

Version: DD-WRT v3.0-r44340 mega 09/10/20
File: dd-wrt.v24-44340_NEWD-2_K3.x_mega_RT-N66U.trx
Kernel: Linux 4.4.235 #3804 Thu Sep 10 14:56:20 +04 2020 mips
Previous: ASUS stock firmware 3.0.0.4.382_51640
Reset: No
Mode: Internet gateway - router
Status: Working
Issues/Errors: No WiFi 2,4 GHz (only WiFi 5 GHz is working)

dmesg
Quote:
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65022
Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd init=/bin/sh
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Writing ErrCtl register=800001c0
Readback ErrCtl register=800001c0
Cache parity protection enabled
Memory: 235908K/262136K available (5490K kernel code, 455K rwdata, 996K rodata, 280K init, 372K bss, 26228K reserved, 0K cma-reserved, 131068K highmem)
SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:128
CPU: BCM5300 rev 1 at 600 MHz
clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370868154 ns
sched_clock: 32 bits at 300MHz, resolution 3ns, wraps every 7158278654ns
console [ttyS0] enabled
Calibrating delay loop... 299.82 BogoMIPS (lpj=1499136)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
BRCM Errata: Disable CPU_WAIT
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 256 (order: -1, 3072 bytes)
NET: Registered protocol family 16
enable BCMA BUS Errata
boardflags are 110
PCI: Initializing host
PCI: Reset RC
boardflags are 110
PCI: Initializing host
PCI: Reset RC
PCI: scanning bus 0
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
pci 0000:00:00.0: [14e4:0800] type 00 class 0x050100
PCI: Fixing up bridge
pci 0000:00:00.0: reg 0x10: [mem 0x18000000-0x18000fff]
pci 0000:00:00.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:01.0: [14e4:4715] type 00 class 0x020000
pci 0000:00:01.0: reg 0x10: [mem 0x18002000-0x18002fff]
pci 0000:00:01.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:04.0: [14e4:471a] type 00 class 0x0c0310
pci 0000:00:04.0: reg 0x10: [mem 0x18009000-0x18009fff]
pci 0000:00:04.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:04.1: [14e4:471a] type 00 class 0x0c0320
pci 0000:00:04.1: reg 0x10: [mem 0x18004000-0x18004fff]
pci 0000:00:04.1: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:05.0: [14e4:0820] type 01 class 0x060400
pci 0000:00:05.0: reg 0x10: [mem 0x18005000-0x18005fff]
pci 0000:00:05.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
pci 0000:00:06.0: [14e4:0820] type 01 class 0x060400
pci 0000:00:06.0: reg 0x10: [mem 0x1800e000-0x1800efff]
pci 0000:00:06.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
pci 0000:00:07.0: [14e4:052e] type 00 class 0xffffff
pci 0000:00:07.0: reg 0x10: [mem 0x18006000-0x18006fff]
pci 0000:00:07.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:08.0: [14e4:080e] type 00 class 0x050000
pci 0000:00:08.0: reg 0x10: [mem 0x18007000-0x18007fff]
pci 0000:00:08.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:09.0: [14e4:0534] type 00 class 0xffffff
pci 0000:00:09.0: reg 0x10: [mem 0x18008000-0x18008fff]
pci 0000:00:09.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
PCI: Fixing up bus 0
pci 0000:00:05.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0000:00:06.0: bridge configuration invalid ([bus 00-00]), reconfiguring
PCI/PCIe coreunit 0 is set to bus 1.
pci 0000:01:00.0: [14e4:5300] type 00 class 0x060000
pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x07ffffff 64bit]
pci 0000:01:00.0: supports D1 D2
pci 0000:01:00.1: [14e4:0000] type 00 class 0x060000
pci 0000:01:00.1: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:01:00.1: reg 0x18: [mem 0x00000000-0x07ffffff 64bit]
pci 0000:01:00.1: supports D1 D2
pci 0000:01:01.0: [14e4:4331] type 00 class 0x028000
pci 0000:01:01.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:01:01.0: supports D1 D2
PCI: Fixing up bus 1
pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
PCI/PCIe coreunit 1 is set to bus 2.
pci 0000:02:00.0: [14e4:5300] type 00 class 0x060000
pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:02:00.0: reg 0x18: [mem 0x00000000-0x07ffffff 64bit]
pci 0000:02:00.0: supports D1 D2
pci 0000:02:00.1: [14e4:0000] type 00 class 0x060000
pci 0000:02:00.1: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:02:00.1: reg 0x18: [mem 0x00000000-0x07ffffff 64bit]
pci 0000:02:00.1: supports D1 D2
pci 0000:02:01.0: [14e4:4331] type 00 class 0x028000
pci 0000:02:01.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:02:01.0: supports D1 D2
PCI: Fixing up bus 2
pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
clocksource: Switched to clocksource MIPS
NET: Registered protocol family 2
TCP established hash table entries: 1024 (order: 0, 4096 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
PCI: CLS 0 bytes, default 32
Asus-RT-N66U init
Asus-RT-N66U init
squashfs: version 4.0 (2009/01/31) Phillip Lougher
bounce: pool size: 64 pages
io scheduler noop registered (default)
HDLC line discipline maxframe=4096
N_HDLC line discipline registered.
serial8250_init
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 8, base_baud = 1562500) is a U6_16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 8, base_baud = 1562500) is a U6_16550A
brd: module loaded
Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x002201
Amd/Fujitsu Extended Query Table at 0x0040
Amd/Fujitsu Extended Query version 1.3.
number of CFI chips: 1
Flash device: 0x2000000 at 0x1c000000
try to find cfe size up to 33554432
bootloader size: 262144
nvram size: 65536
Physically mapped flash: Filesystem type: squashfs, size=0x522306
partition size = 5427200
Creating 5 MTD partitions on "Physically mapped flash":
0x000000000000-0x000000040000 : "cfe"
0x000000040000-0x000001fe0000 : "linux"
0x000000253000-0x000000780000 : "rootfs"
mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
mtd: partition "rootfs" set to be root filesystem
0x000001fe0000-0x000002000000 : "nvram"
0x000000780000-0x000001fe0000 : "ddwrt"
ERROR: Unknown flash, device_id:0x00
bcmsflash: found no supported devices
No NAND flash type found
brcmnand: found no supported devices
No NAND flash type found
nflash: found no supported devices
et_module_init: passivemode set to 0x0
et_module_init: txworkq set to 0x0
et_module_init: et_txq_thresh set to 0xce4
et_module_init: et_rxlazy_timeout set to 0x3e8
et_module_init: et_rxlazy_framecnt set to 0x20
et_module_init: et_rxlazy_dyn_thresh set to 0
ET Corerev -2147483648
bcm_robo_enable_switch: EEE is disabled
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
cmd 2 new_cmd 0
PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
cmd 2 new_cmd 0
PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
Broadcom Watchdog Timer: 0.07 initialized.
u32 classifier
Performance counters on
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (3686 buckets, 14744 max)
nf_conntrack_rtsp v0.7 loading
xt_time: kernel timezone is -0000
ip_set: protocol 6
gre: GRE over IPv4 demultiplexor driver
nf_nat_rtsp v0.7 loading
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 17
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
startup nvram driver
found nvram
max nvram space = 65536
VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Freeing unused kernel memory: 280K
roboswitch: Probing device 'eth0'
roboswitch: trying a 53125! at eth0
roboswitch: found a 53125! at eth0
device br0 entered promiscuous mode
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device vlan2 entered promiscuous mode
fast-classifier (PBR safe v2.1.6b): starting up
fast-classifier: registered
device vlan2 left promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
random: nonblocking pool is initialized
nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
device vlan1 left promiscuous mode
device eth0 left promiscuous mode
br0: port 1(vlan1) entered disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entered disabled state
device br0 entered promiscuous mode
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
br0: port 1(vlan1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device eth1 entered promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device vlan2 entered promiscuous mode
device vlan2 left promiscuous mode
br0: port 1(vlan1) entered forwarding state
br0: port 2(eth1) entered forwarding state


according to your log both wifi interfaces are detected. are you sure that you did not disable 2.4 in gui?

_________________
"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
Welshchris
DD-WRT User


Joined: 05 May 2010
Posts: 122

PostPosted: Mon Sep 14, 2020 18:40    Post subject: Reply with quote
Im having issues saving files especially picture files.

The odd file will corrupt and i will have to re download it.

I Have a Netgear Nighthawk X6 R8000.
goodlander
DD-WRT Novice


Joined: 16 Sep 2020
Posts: 1

PostPosted: Wed Sep 16, 2020 12:37    Post subject: Reply with quote
Zyxx wrote:
Router/Version: Asus RT-N66U
File: dd-wrt.v24-44340_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r44340 big (09/10/20) (prev. DD-WRT v3.0-r44251 big (08/28/20))
Kernel: Linux 4.4.235 #3800 Thu Sep 10 14:51:32 +04 2020 mips
Mode: Gateway, Wifi disabled, Wireguard Endpoint for external VPS, connected via DHCP WAN to WRT1900ACS v2, Keep Alive reboot 6:05 in the morning
Reset: No
Status: 6h up and running.


I don't see RT-N66U listed in any of the download links above. Where should I be looking for this?
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 2816

PostPosted: Wed Sep 16, 2020 12:53    Post subject: Reply with quote
goodlander wrote:
I don't see RT-N66U listed in any of the download links above. Where should I be looking for this?

https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2020/09-10-2020-r44340/broadcom_K3X/

ftp://ftp.dd-wrt.com/betas/2020/09-10-2020-r44340/broadcom_K3X/
ohnoo
DD-WRT Novice


Joined: 31 May 2020
Posts: 24

PostPosted: Wed Sep 16, 2020 17:13    Post subject: Open firewall ports Reply with quote
Router/Version: Linksys WRT54G2 V1
File/Kernel: r44340 dd-wrt.v24_micro_generic.bin/Linux 2.4.37 #61962
Previous/Reset: v24-sp2-14929 / Yes
Mode/Status: Gateway
Issues/Errors: Open firewall ports checked with https://www.grc.com/shieldsup

Here the results:

"GRC Port Authority Report created on UTC: 2020-09-16 at 16:19:23
Results from scan of ports: 0-1055

2 Ports Open
1047 Ports Closed
7 Ports Stealth
---------------------
1056 Ports Tested

Ports found to be OPEN were: 53, 80
Ports found to be STEALTH were: 113, 135, 136, 137, 138, 139,
593
Other than what is listed above, all ports are CLOSED.

TruStealth: FAILED - NOT all tested ports were STEALTH,
- NO unsolicited packets were received,
- A PING REPLY (ICMP Echo) WAS RECEIVED."

IP tables commands don't work, I'm attaching a picture of what it returs.
I've already share this in another thread where someone else confirmed this issue:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=326407&highlight=



CLI.jpg
 Description:
 Filesize:  70.31 KB
 Viewed:  2301 Time(s)

CLI.jpg


liweilee
DD-WRT Novice


Joined: 17 Sep 2020
Posts: 10

PostPosted: Thu Sep 17, 2020 5:59    Post subject: Reply with quote
Router/Version: TP-Link Archer C8 V1
Firmware: DD-WRT v3.0-r44340 std (09/10/20)
Kernel: Linux 4.4.235 #1027 SMP Thu Sep 10 08:20:07 +04 2020 armv7l
Previous: r44251
Mode: Gateway, AP
Reset: Yes
Status: Working fine on IOS 13 but after upgraded iPhone to IOS 14, usb tethering iPhone not work.

syslog below: (physical address modified to xx:xx:xx:xx:xx:xx)

Jan 1 08:00:08 TP-Link Archer C8 syslog.info syslogd started: BusyBox v1.32.0
Jan 1 08:00:08 TP-Link Archer C8 user.info : syslogd : daemon successfully started
Jan 1 08:00:08 TP-Link Archer C8 user.info : resetbutton : resetbutton daemon successfully started
Jan 1 08:00:08 TP-Link Archer C8 user.info : bridge : bridge br0 successfully added
Jan 1 08:00:08 TP-Link Archer C8 daemon.info mstpd[646]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 8
Jan 1 08:00:08 TP-Link Archer C8 daemon.info mstpd[646]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 8
Jan 1 08:00:08 TP-Link Archer C8 user.info : bridge : interface vlan1 successfully added to bridge br0
Jan 1 08:00:08 TP-Link Archer C8 user.info : bridge : interface vlan2 successfully added to bridge br0
Jan 1 08:00:09 TP-Link Archer C8 user.info : bridge : interface eth1 successfully added to bridge br0
Jan 1 08:00:14 TP-Link Archer C8 user.info : bridge : interface eth2 successfully added to bridge br0
Jan 1 08:00:15 TP-Link Archer C8 user.info : wland : daemon successfully started
Jan 1 08:00:15 TP-Link Archer C8 user.info : syslogd : syslog daemon successfully stopped
Jan 1 08:00:15 TP-Link Archer C8 user.info : telnetd : daemon successfully started
Jan 1 08:00:15 TP-Link Archer C8 syslog.info syslogd exiting
Jan 1 08:00:15 TP-Link Archer C8 syslog.info syslogd started: BusyBox v1.32.0
Jan 1 08:00:15 TP-Link Archer C8 user.info : cron : daemon successfully started
Jan 1 08:00:15 TP-Link Archer C8 cron.info cron[902]: (CRON) STARTUP (fork ok)
Jan 1 08:00:15 TP-Link Archer C8 user.info : sfe : shortcut forwarding engine successfully started
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[912]: started, version 2.82 cachesize 1500
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[912]: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua no-TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect no-inotify no-dumpfile
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq-dhcp[912]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
Jan 1 08:00:15 TP-Link Archer C8 user.info : dnsmasq : daemon successfully started
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[912]: using only locally-known addresses for domain test
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[912]: using only locally-known addresses for domain onion
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[912]: using only locally-known addresses for domain localhost
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[912]: using only locally-known addresses for domain local
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[912]: using only locally-known addresses for domain invalid
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[912]: using only locally-known addresses for domain bind
Jan 1 08:00:15 TP-Link Archer C8 daemon.warn dnsmasq[912]: no servers found in /tmp/resolv.dnsmasq, will retry
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[912]: read /etc/hosts - 3 addresses
Jan 1 08:00:16 TP-Link Archer C8 kern.crit usbmuxd[980]: [0] libusb_init failed: LIBUSB_ERROR_OTHER
Jan 1 08:00:17 TP-Link Archer C8 user.info : ppp_redial : redial process successfully started
Jan 1 08:00:17 TP-Link Archer C8 user.info : ttraff : traffic counter daemon successfully started
Jan 1 08:00:17 TP-Link Archer C8 daemon.info httpd[999]: httpd : httpd server started at port 80
Jan 1 08:00:17 TP-Link Archer C8 user.info : httpd : http daemon successfully started
Jan 1 08:00:23 TP-Link Archer C8 daemon.info dnsmasq-dhcp[912]: DHCPDISCOVER(br0) xx:xx:xx:xx:xx:xx
Jan 1 08:00:23 TP-Link Archer C8 daemon.info dnsmasq-dhcp[912]: DHCPOFFER(br0) 192.168.1.136 xx:xx:xx:xx:xx:xx
Jan 1 08:00:23 TP-Link Archer C8 daemon.info dnsmasq-dhcp[912]: DHCPDISCOVER(br0) xx:xx:xx:xx:xx:xx
Jan 1 08:00:23 TP-Link Archer C8 daemon.info dnsmasq-dhcp[912]: DHCPOFFER(br0) 192.168.1.136 xx:xx:xx:xx:xx:xx
Jan 1 08:00:23 TP-Link Archer C8 daemon.info dnsmasq-dhcp[912]: DHCPREQUEST(br0) 192.168.1.136 xx:xx:xx:xx:xx:xx
Jan 1 08:00:23 TP-Link Archer C8 daemon.info dnsmasq-dhcp[912]: DHCPACK(br0) 192.168.1.136 xx:xx:xx:xx:xx:xx MikroTik
Jan 1 08:00:24 TP-Link Archer C8 user.info : nas : wait for network init
Jan 1 08:00:34 TP-Link Archer C8 user.info : nas : start nas lan
Jan 1 08:00:34 TP-Link Archer C8 user.info : nas : start nas for wl0
Jan 1 08:00:34 TP-Link Archer C8 user.info : nas : NAS lan (wl0 interface) successfully started
Jan 1 08:00:34 TP-Link Archer C8 user.info : nas : start nas lan
Jan 1 08:00:34 TP-Link Archer C8 user.info : nas : start nas for wl1
Jan 1 08:00:34 TP-Link Archer C8 user.info : nas : NAS lan (wl1 interface) successfully started
Jan 1 08:00:35 TP-Link Archer C8 user.info : nas : daemon successfully stopped
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : daemon hanging, send SIGKILL
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : start nas lan
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : start nas for wl0
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : NAS lan (wl0 interface) successfully started
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : start nas lan
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : start nas for wl1
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : NAS lan (wl1 interface) successfully started
Jan 1 08:00:37 TP-Link Archer C8 user.info : httpd : daemon successfully stopped
Jan 1 08:00:37 TP-Link Archer C8 daemon.info httpd[1007]: httpd : httpd server shutdown
Jan 1 08:00:37 TP-Link Archer C8 daemon.info httpd[1046]: httpd : httpd server started at port 80
Jan 1 08:00:37 TP-Link Archer C8 user.info : httpd : http daemon successfully started
Jan 1 08:00:37 TP-Link Archer C8 user.info : resetbutton : daemon successfully stopped
Jan 1 08:00:37 TP-Link Archer C8 user.info : resetbutton : resetbutton daemon successfully started
Jan 1 08:01:18 TP-Link Archer C8 user.info : dnsmasq : daemon successfully stopped
Jan 1 08:01:18 TP-Link Archer C8 daemon.info dnsmasq[912]: exiting on receipt of SIGTERM
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: started, version 2.82 cachesize 1500
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua no-TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect no-inotify no-dumpfile
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq-dhcp[1318]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using only locally-known addresses for domain test
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using only locally-known addresses for domain onion
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using only locally-known addresses for domain localhost
Jan 1 08:01:19 TP-Link Archer C8 user.info : dnsmasq : daemon successfully started
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using only locally-known addresses for domain local
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using only locally-known addresses for domain invalid
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using only locally-known addresses for domain bind
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: reading /tmp/resolv.dnsmasq
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using only locally-known addresses for domain test
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using only locally-known addresses for domain onion
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using only locally-known addresses for domain localhost
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using only locally-known addresses for domain local
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using only locally-known addresses for domain invalid
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using only locally-known addresses for domain bind
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: using nameserver 172.20.10.1#53
Jan 1 08:01:19 TP-Link Archer C8 daemon.info dnsmasq[1318]: read /etc/hosts - 3 addresses
Jan 1 08:01:19 TP-Link Archer C8 user.info : wland : daemon successfully stopped
Jan 1 08:01:19 TP-Link Archer C8 user.info : wland : daemon successfully started
Jan 1 08:01:19 TP-Link Archer C8 user.info : wan : WAN is up. IP: 172.20.10.2
Jan 1 08:01:19 TP-Link Archer C8 user.info : vpn modules : vpn modules successfully unloaded
Jan 1 08:01:19 TP-Link Archer C8 user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 08:01:19 TP-Link Archer C8 user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 08:01:19 TP-Link Archer C8 user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 08:01:19 TP-Link Archer C8 user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 1 08:01:19 TP-Link Archer C8 user.info : sfe : shortcut forwarding engine successfully started
Jan 1 08:01:19 TP-Link Archer C8 user.info : process_monitor : successfully started
Jan 1 08:01:20 TP-Link Archer C8 daemon.debug ntpclient[1418]: Connecting to 2.pool.ntp.org [220.132.100.157] ...
Jan 1 08:01:20 TP-Link Archer C8 user.info : vpn modules : vpn modules successfully unloaded
Jan 1 08:01:20 TP-Link Archer C8 user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 08:01:20 TP-Link Archer C8 user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 08:01:20 TP-Link Archer C8 user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 08:01:20 TP-Link Archer C8 user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 1 08:01:20 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:01:21 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:01:21 TP-Link Archer C8 user.info : dnsmasq : daemon successfully stopped
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1318]: exiting on receipt of SIGTERM
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: started, version 2.82 cachesize 1500
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua no-TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect no-inotify no-dumpfile
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq-dhcp[1534]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
Jan 1 08:01:21 TP-Link Archer C8 user.info : dnsmasq : daemon successfully started
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using only locally-known addresses for domain test
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using only locally-known addresses for domain onion
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using only locally-known addresses for domain localhost
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using only locally-known addresses for domain local
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using only locally-known addresses for domain invalid
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using only locally-known addresses for domain bind
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: reading /tmp/resolv.dnsmasq
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using only locally-known addresses for domain test
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using only locally-known addresses for domain onion
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using only locally-known addresses for domain localhost
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using only locally-known addresses for domain local
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using only locally-known addresses for domain invalid
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using only locally-known addresses for domain bind
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: using nameserver 172.20.10.1#53
Jan 1 08:01:21 TP-Link Archer C8 daemon.info dnsmasq[1534]: read /etc/hosts - 3 addresses
Jan 1 08:01:21 TP-Link Archer C8 user.info : wland : daemon successfully stopped
Jan 1 08:01:21 TP-Link Archer C8 user.info : wland : daemon successfully started
Jan 1 08:01:21 TP-Link Archer C8 user.info : wan : WAN is up. IP: 172.20.10.2
Jan 1 08:01:22 TP-Link Archer C8 user.info : vpn modules : vpn modules successfully unloaded
Jan 1 08:01:22 TP-Link Archer C8 user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 08:01:22 TP-Link Archer C8 user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 08:01:22 TP-Link Archer C8 user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 08:01:22 TP-Link Archer C8 user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 1 08:01:22 TP-Link Archer C8 user.info : sfe : shortcut forwarding engine successfully started
Jan 1 08:01:22 TP-Link Archer C8 user.info : process_monitor : daemon successfully stopped
Jan 1 08:01:22 TP-Link Archer C8 daemon.info process_monitor[1415]: process_monitor : cleanup timers
Jan 1 08:01:22 TP-Link Archer C8 user.info : process_monitor : successfully started
Jan 1 08:01:22 TP-Link Archer C8 daemon.debug ntpclient[1626]: Connecting to 2.pool.ntp.org [220.132.100.157] ...
Jan 1 08:01:23 TP-Link Archer C8 daemon.debug ntpclient[1418]: Timed out waiting for 2.pool.ntp.org [220.132.100.157].
Jan 1 08:01:23 TP-Link Archer C8 daemon.debug ntpclient[1418]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 08:01:25 TP-Link Archer C8 daemon.debug ntpclient[1626]: Timed out waiting for 2.pool.ntp.org [220.132.100.157].
Jan 1 08:01:25 TP-Link Archer C8 daemon.debug ntpclient[1626]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 08:01:26 TP-Link Archer C8 daemon.debug ntpclient[1418]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 08:01:26 TP-Link Archer C8 daemon.debug ntpclient[1418]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 08:01:28 TP-Link Archer C8 daemon.debug ntpclient[1626]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 08:01:28 TP-Link Archer C8 daemon.debug ntpclient[1626]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 08:01:29 TP-Link Archer C8 daemon.debug ntpclient[1418]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 08:01:31 TP-Link Archer C8 daemon.debug ntpclient[1626]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 08:01:31 TP-Link Archer C8 daemon.err process_monitor[1625]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 08:01:31 TP-Link Archer C8 daemon.err process_monitor[1625]: Last update failed, we need to re-update after 30 seconds
Jan 1 08:01:31 TP-Link Archer C8 daemon.debug process_monitor[1625]: We need to re-update after 3600 seconds
Jan 1 08:01:31 TP-Link Archer C8 daemon.info process_monitor[1625]: process_monitor : set timer: 3600 seconds, callback: ntp_main()
Jan 1 08:02:01 TP-Link Archer C8 daemon.debug ntpclient[1684]: Connecting to 2.pool.ntp.org [183.177.72.201] ...
Jan 1 08:02:04 TP-Link Archer C8 daemon.debug ntpclient[1684]: Timed out waiting for 2.pool.ntp.org [183.177.72.201].
Jan 1 08:02:04 TP-Link Archer C8 daemon.debug ntpclient[1684]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 08:02:07 TP-Link Archer C8 daemon.debug ntpclient[1684]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 08:02:07 TP-Link Archer C8 daemon.debug ntpclient[1684]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 08:02:10 TP-Link Archer C8 daemon.debug ntpclient[1684]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 08:02:10 TP-Link Archer C8 daemon.err process_monitor[1625]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
mwchang
DD-WRT Guru


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

PostPosted: Thu Sep 17, 2020 16:32    Post subject: Re: Open firewall ports Reply with quote
ohnoo wrote:
Router/Version: Linksys WRT54G2 V1
File/Kernel: r44340 dd-wrt.v24_micro_generic.bin/Linux 2.4.37 #61962
.... more ....

IP tables commands don't work, I'm attaching a picture of what it returs.
I've already share this in another thread where someone else confirmed this issue:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=326407&highlight=

"iptables -L" works in my RT-N18U, but not options glued together as in "-Lvn"!!

However, "iptables -L --verbose --numeric" is working flawlessly!!! So is "iptables -L -v -n"! 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
kristianissimo
DD-WRT Novice


Joined: 12 Sep 2020
Posts: 3

PostPosted: Fri Sep 18, 2020 13:34    Post subject: Re: DD-WRT Build r44340 (09/10/2020) Mega on ASUS RT-N66U Reply with quote
BrainSlayer wrote:
kristianissimo wrote:
Router:
ASUS RT-N66U (Dark Knight) ver. B1
Broadcom BCM5300 chip rev 1
CPU Features MIPS32r1 MIPS32r2 MIPS16 DSP DSP2
CFE 1.0.19 64k

Version: DD-WRT v3.0-r44340 mega 09/10/20
File: dd-wrt.v24-44340_NEWD-2_K3.x_mega_RT-N66U.trx
Kernel: Linux 4.4.235 #3804 Thu Sep 10 14:56:20 +04 2020 mips
Previous: ASUS stock firmware 3.0.0.4.382_51640
Reset: No
Mode: Internet gateway - router
Status: Working
Issues/Errors: No WiFi 2,4 GHz (only WiFi 5 GHz is working)


according to your log both wifi interfaces are detected. are you sure that you did not disable 2.4 in gui?

Hello. Sorry for delay in replying. How can I do that - turn on WiFi 2,4 in GUI? There is only 5 GHz WiFi under the Wireless tab (under wl0 adapter). Status page for Wireless tab shows 5 GHz wl0 only. The LED light for WiFi 5 on router's case works. LED for WiFi 2,4 is dimmed. Under ASUS firmware both LEDs work and both WiFi networks are active.



DD-WRT-ASUS-RT-N66U-Wireless.png
 Description:
 Filesize:  40.59 KB
 Viewed:  1991 Time(s)

DD-WRT-ASUS-RT-N66U-Wireless.png


RageX
DD-WRT Novice


Joined: 01 Jan 2020
Posts: 36

PostPosted: Fri Sep 18, 2020 13:49    Post subject: Reply with quote
@kristianissimo try changing the regulatory domain to the US or Germany and see if it appears

@ohnoo BS found and patched your open port bug earlier today as per your main thread, it appears to be specific to your router model, you can wait for the next build release
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
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