New Build - 08/03/2022 - r49626

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


Joined: 01 May 2022
Posts: 32

PostPosted: Mon Aug 08, 2022 20:17    Post subject: r49547 Reply with quote
Router/Version: Linksys WRT54GL v1.1
File/Kernel: dd-wrt.v24 mini generic r49547 / Linux 2.4.37 #69223 Sat Jul 23 04:50:35 +07 2022 mips
Previous/Reset: dd-wrt.v24 mini generic r49392 / yes
Mode/Status: Gateway / Working
Issues/Errors: yes.

The secret assembly is installed r49547 Shocked
Sponsor
foreverforgotten
DD-WRT Novice


Joined: 16 Jun 2022
Posts: 11
Location: Dallas, TX

PostPosted: Tue Aug 09, 2022 13:04    Post subject: Reply with quote
Firmware: DD-WRT v3.0-r49626 std (08/03/22)
Router/Version: ASUS RT-AC5300
Kernel: Linux 4.4.302-st20 #6850 SMP Wed Aug 3 03:56:41 +07 2022 armv7l
Previous: DD-WRT v3.0-r49492 std (07/14/22)
Mode/Status: Wired and Wireless (1x 2.4 GHz, 2x 5 GHz) as Router (with DHCP), Switch and AP. DNS is offloaded to PiHole.
Uptime: 5 days, 20:42
Reset: Yes
Temperatures: CPU 52.5 °C / WL0 42.5 °C / WL1 43.5 °C / WL2 48.0 °C
Issues/Errors: Short version ... ultimately determined unit was overheating, nothing related to DD-WRT.

Long version...
I was experiencing an increase in random issues, mainly drops/inability to connect to the WL0 or WL1 antenna. A few times the router stopped responding completely and rebooted itself. I thought perhaps an NVRAM reset would help as a first step, so I proceeded to upgrade with the reset selected, then reconfigured everything by hand.

Unfortunately the issues continued. I came to suspect the unit was overheating based on the temperatures being reported by DD-WRT, which at the time 5 days ago were the following:

CPU 69.7 °C / WL0 50.0 °C / WL1 51.0 °C / WL2 54.5 °C 

Doing some searches on the web, I found posts on various forums (including one on DD-WRT) about users experiencing similar random stability issues they ultimately attributed to the unit being too hot for RT-AC5300.

I then proceeded to increase air circulation around the router (a fan) and also elevated the router on a wire-rack to increase its intake air vs. sitting on a wood surface. Been completely stable for the past 5 days now, current temps:

CPU 52.5 °C / WL0 42.5 °C / WL1 43.5 °C / WL2 48.0 °C

In short, the problems were not related to DD-WRT, just my unit's ability to keep itself cool. Cool
manchesterblack
DD-WRT User


Joined: 04 Mar 2021
Posts: 60
Location: Manchester

PostPosted: Tue Aug 09, 2022 15:13    Post subject: Works with issues Reply with quote
Works fine but when I activate the firewall, there is no internet connection and the router cannot be accessed.
I also found powering off the router a few times resets it back to default settings and I had to configure it from scratch.

_________________
Netgear R7000
DD-WRT DD-WRT v3.0-r50595 std (10/23/22)
Manchester
Enable dnsmasq- Yes
Encrypt DNS- NO
DNSCrypt Resolver- No Using Smart DNS
Cache DNSSEC Data- Yes
Validate DNS Replies (DNSSEC)- NO
Check Unsigned DNS Replies- NO
No DNS Rebind- Enable
Query DNS in Strict Order- Enable
Add Requestor MAC to DNS Query- Disable
RFC4039 Rapid Commit Support- Enable
Maximum Cached Entries- 1500

Smart DNS - YES

server-https https://9.9.9.9/dns-query
server-tls 9.9.9.9:853 -host-name: dns.quad9.net
server-tls 5.2.75.75:853 -host-name: dot.nl.ahadns.net
server-https https://1.1.1.1/dns-query

Additional VPN Configuration-
pull-filter ignore "dhcp-option DNS6 "
pull-filter ignore "dhcp-option DNS "

Dnsmasq Additional Options

server=/pool.ntp.org/9.9.9.9
server=/pool.ntp.org/1.0.0.1
server=/adquard-dns.com/9.9.9.9


BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 10799
Location: Netherlands

PostPosted: Tue Aug 09, 2022 15:45    Post subject: Re: Works with issues Reply with quote
manchesterblack wrote:
Works fine but when I activate the firewall, there is no internet connection and the router cannot be accessed.
I also found powering off the router a few times resets it back to default settings and I had to configure it from scratch.


Powering on and off without letting the router properly start 5 times will reset the router.
That is a setting on the Administration page: "BootFail handling"

For your other problem make a separate thread describe your setup screenshots are helpful

_________________
Routers:Netgear R7800, R7000, R6400v1, R6400v2, Linksys EA8500, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: 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
Lanchon
DD-WRT Novice


Joined: 05 Oct 2019
Posts: 20

PostPosted: Tue Aug 09, 2022 18:17    Post subject: Reply with quote
Linksys WRT160N v3
WRT160N v3 DD-WRT v3.0-r49626 mini (08/03/22)

previous installed build was from 2020

reset during flash via web, reset after flash via web, reset using reset button... but problem persists

DHCP server is non-functional on wired LAN (did not try WLAN), but if I configure a static IP on the PC, the router seems to work fine.

all configuration is default. this even happens in the forced password reset screen after reset.

Code:

root@Linksys WRT160N v3:~# cat /tmp/var/log/messages
Dec 31 21:00:02 Linksys WRT160N v3 syslog.info syslogd started: BusyBox v1.35.0
Dec 31 21:00:02 Linksys WRT160N v3 user.info syslog: [syslogd] : daemon successfully started
Dec 31 21:00:02 Linksys WRT160N v3 user.info syslog: [resetbutton] : resetbutton daemon successfully started
Dec 31 21:00:02 Linksys WRT160N v3 user.info syslog: [bridge] : bridge br0 successfully added
Dec 31 21:00:03 Linksys WRT160N v3 user.info syslog: [bridge] : interface vlan1 successfully added to bridge br0
Dec 31 21:00:04 Linksys WRT160N v3 user.info syslog: [bridge] : interface eth1 successfully added to bridge br0
Dec 31 21:00:04 Linksys WRT160N v3 user.info syslog: [syslogd] : syslog daemon successfully stopped
Dec 31 21:00:05 Linksys WRT160N v3 syslog.info syslogd exiting
Dec 31 21:00:05 Linksys WRT160N v3 syslog.info syslogd started: BusyBox v1.35.0
Dec 31 21:00:06 Linksys WRT160N v3 user.info syslog: [dnsmasq] : daemon successfully started
Dec 31 21:00:06 Linksys WRT160N v3 authpriv.info dropbear[797]: Running in background
Dec 31 21:00:06 Linksys WRT160N v3 user.info syslog: [dropbear] : ssh daemon successfully started
Dec 31 21:00:06 Linksys WRT160N v3 user.info syslog: [cron] : daemon successfully started
Dec 31 21:00:06 Linksys WRT160N v3 cron.info cron[798]: (CRON) STARTUP (fork ok)
Dec 31 21:00:07 Linksys WRT160N v3 daemon.info httpd[807]: [httpd] : httpd server started at port 80
Dec 31 21:00:07 Linksys WRT160N v3 user.info syslog: [httpd] : http daemon successfully started
Dec 31 21:00:12 Linksys WRT160N v3 user.info syslog: [nas] : wait for network init
Dec 31 21:00:22 Linksys WRT160N v3 user.info syslog: [nas] : start nas lan
Dec 31 21:00:22 Linksys WRT160N v3 user.info syslog: [nas] : start nas for wl0
Dec 31 21:00:23 Linksys WRT160N v3 user.info syslog: [nas] : start nas for wl0
Dec 31 21:00:23 Linksys WRT160N v3 user.info syslog: [httpd] : daemon successfully stopped
Dec 31 21:00:23 Linksys WRT160N v3 daemon.info httpd[815]: [httpd] : httpd server shutdown
Dec 31 21:00:23 Linksys WRT160N v3 daemon.info httpd[933]: [httpd] : httpd server started at port 80
Dec 31 21:00:23 Linksys WRT160N v3 user.info syslog: [httpd] : http daemon successfully started
Dec 31 21:00:23 Linksys WRT160N v3 user.info syslog: [resetbutton] : daemon successfully stopped
Dec 31 21:00:23 Linksys WRT160N v3 user.info syslog: [resetbutton] : resetbutton daemon successfully started
Dec 31 21:02:00 Linksys WRT160N v3 user.info syslog: [dnsmasq] : maybe died, we need to re-exec it
Dec 31 21:02:00 Linksys WRT160N v3 user.info syslog: [dnsmasq] : daemon successfully started
Dec 31 21:02:36 Linksys WRT160N v3 authpriv.info dropbear[991]: Child connection from 192.168.1.15:36388
Dec 31 21:02:44 Linksys WRT160N v3 authpriv.notice dropbear[991]: Pubkey auth succeeded for 'root' with ssh-rsa key SHA256:[...] from 192.168.1.15:36388


note the line -> [dnsmasq] : maybe died, we need to re-exec it

Code:

root@Linksys WRT160N v3:~# dmesg
[42949372.960000] Linux version 2.6.24.111 (root@linux) (gcc version 4.1.2) #28033 Wed Aug 3 01:33:50 +07 2022
[42949372.960000] CPU revision is: 00019749
[42949372.960000] Found a 4MB ST compatible serial flash
[42949372.960000] Determined physical RAM map:
[42949372.960000]  memory: 02000000 @ 00000000 (usable)
[42949372.960000] Entering add_active_range(0, 0, 8192) 0 entries of 256 used
[42949372.960000] Zone PFN ranges:
[42949372.960000]   Normal          0 ->     8192
[42949372.960000]   HighMem      8192 ->     8192
[42949372.960000] Movable zone start PFN for each node
[42949372.960000] early_node_map[1] active PFN ranges
[42949372.960000]     0:        0 ->     8192
[42949372.960000] On node 0 totalpages: 8192
[42949372.960000]   Normal zone: 0 pages used for memmap
[42949372.960000]   Normal zone: 0 pages reserved
[42949372.960000]   Normal zone: 8192 pages, LIFO batch:1
[42949372.960000]   HighMem zone: 0 pages used for memmap
[42949372.960000]   Movable zone: 0 pages used for memmap
[42949372.960000] Built 1 zonelists in Zone order.  Total pages: 8192
[42949372.960000] Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd
[42949372.960000] Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
[42949372.960000] Primary data cache 32kB, 4-way, linesize 32 bytes.
[42949372.960000] Synthesized TLB refill handler (20 instructions).
[42949372.960000] Synthesized TLB load handler fastpath (32 instructions).
[42949372.960000] Synthesized TLB store handler fastpath (32 instructions).
[42949372.960000] Synthesized TLB modify handler fastpath (31 instructions).
[42949372.960000] PID hash table entries: 256 (order: 8, 1024 bytes)
[42949372.960000] CPU: BCMb83a rev 0 at 300 MHz
[42949372.960000] Using 150.000 MHz high precision timer.
[42949372.960000] console [ttyS0] enabled
[42949372.970000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[42949372.970000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[42949372.990000] Memory: 26004k/32768k available (3474k kernel code, 6748k reserved, 1374k data, 188k init, 0k highmem)
[42949373.000000] Calibrating delay loop... 149.50 BogoMIPS (lpj=747520)
[42949373.210000] Mount-cache hash table entries: 512
[42949373.210000] NET: Registered protocol family 16
[42949373.230000] Generic PHY: Registered new driver
[42949373.240000] PCI: no core
[42949373.240000] PCI: no core
[42949373.250000] PCI: Fixing up bus 0
[42949373.290000] NET: Registered protocol family 2
[42949373.300000] Time: MIPS clocksource has been installed.
[42949373.380000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[42949373.380000] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
[42949373.390000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[42949373.400000] TCP: Hash tables configured (established 1024 bind 1024)
[42949373.400000] TCP reno registered
[42949373.440000] WRT160Nv3/M10/E1000 GPIO Init
[42949373.460000] devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
[42949373.460000] devfs: boot_options: 0x1
[42949373.470000] squashfs: version 3.0 (2006/03/15) Phillip Lougher
[42949373.470000] io scheduler noop registered
[42949373.480000] io scheduler deadline registered (default)
[42949373.920000] HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
[42949373.920000] N_HDLC line discipline registered.
[42949373.930000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[42949373.940000] serial8250: ttyS0 at MMIO 0x0 (irq = 8) is a 16550A
[42949373.950000] PPP generic driver version 2.4.2
[42949373.950000] PPP Deflate Compression module registered
[42949373.960000] PPP BSD Compression module registered
[42949373.960000] MPPE/MPPC encryption/compression module registered
[42949373.970000] NET: Registered protocol family 24
[42949373.980000] tun: Universal TUN/TAP device driver, 1.6
[42949373.980000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[42949373.990000] et_module_init: passivemode set to 0x0
[42949374.000000] PCI: Setting latency timer of device 0000:00:02.0 to 64
[42949374.180000] eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138.9
[42949374.190000] PCI: Setting latency timer of device 0000:00:01.0 to 64
[42949374.450000] pflash: found no supported devices
[42949374.460000] bootloader size: 262144
[42949374.460000] nvram size: 32768
[42949374.460000] sflash: Filesystem type: squashfs, size=0x2191d9
[42949374.470000] partition size = 2241536
[42949374.470000] Creating 5 MTD partitions on "sflash":
[42949374.480000] 0x00000000-0x00040000 : "cfe"
[42949374.480000] 0x00040000-0x003f0000 : "linux"
[42949374.490000] 0x0019cc00-0x003c0000 : "rootfs"
[42949374.490000] mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
[42949374.500000] 0x003f0000-0x00400000 : "nvram"
[42949374.510000] 0x003c0000-0x003f0000 : "ddwrt"
[42949374.510000] Broadcom Watchdog Timer: 0.07 initialized.
[42949374.520000] u32 classifier
[42949374.520000]     Performance counters on
[42949374.530000]     Actions configured
[42949374.530000] Netfilter messages via NETLINK v0.30.
[42949374.540000] nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
[42949374.540000] ctnetlink v0.93: registering with nfnetlink.
[42949374.550000] IPv4 over IPv4 tunneling driver
[42949374.560000] GRE over IPv4 tunneling driver
[42949374.560000] ip_tables: (C) 2000-2006 Netfilter Core Team
[42949374.570000] ClusterIP Version 0.8 loaded successfully
[42949374.570000] TCP bic registered
[42949374.580000] TCP cubic registered
[42949374.580000] TCP westwood registered
[42949374.580000] TCP highspeed registered
[42949374.590000] TCP hybla registered
[42949374.590000] TCP htcp registered
[42949374.590000] TCP vegas registered
[42949374.600000] TCP scalable registered
[42949374.600000] NET: Registered protocol family 1
[42949374.610000] NET: Registered protocol family 17
[42949374.610000] Welcome to PF_RING 3.2.1
[42949374.610000] (C) 2004-06 L.Deri <deri@ntop.org>
[42949374.620000] NET: Registered protocol family 27
[42949374.630000] PF_RING: bucket length    128 bytes
[42949374.630000] PF_RING: ring slots       4096
[42949374.630000] PF_RING: sample rate      1 [1=no sampling]
[42949374.640000] PF_RING: capture TX       No [RX only]
[42949374.650000] PF_RING: transparent mode Yes
[42949374.650000] PF_RING initialized correctly.
[42949374.650000] PF_RING: registered /proc/net/pf_ring/
[42949374.660000] 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
[42949374.670000] All bugs added by David S. Miller <davem@redhat.com>
[42949374.700000] decode 1f02
[42949374.710000] VFS: Mounted root (squashfs filesystem) readonly.
[42949374.720000] Mounted devfs on /dev
[42949374.730000] Freeing unused kernel memory: 188k freed
[42949377.110000] roboswitch: Probing device eth0: found a 5325!
[42949380.230000] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
[42949380.330000] device br0 entered promiscuous mode
[42949380.650000] device vlan1 entered promiscuous mode
[42949380.650000] device eth0 entered promiscuous mode
[42949381.350000] device eth1 entered promiscuous mode
[42949381.370000] br0: port 2(eth1) entering learning state
[42949381.380000] br0: port 1(vlan1) entering learning state
[42949381.390000] device br0 left promiscuous mode
[42949381.410000] device br0 entered promiscuous mode
[42949381.450000] device br0 left promiscuous mode
[42949382.710000] device vlan2 entered promiscuous mode
[42949387.650000] device vlan2 left promiscuous mode
[42949396.380000] br0: topology change detected, propagating
[42949396.380000] br0: port 2(eth1) entering forwarding state
[42949396.390000] br0: topology change detected, propagating
[42949396.390000] br0: port 1(vlan1) entering forwarding state
Zyxx
DD-WRT Guru


Joined: 28 Dec 2018
Posts: 566

PostPosted: Wed Aug 10, 2022 6:42    Post subject: Reply with quote
Router/Version: Asus RT-N66U
File: dd-wrt.v24-49599_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r49626 big (08/03/22) (prev. DD-WRT v3.0-r49599 big (07/30/22))
Kernel: Linux 4.4.302-st20 #17708 Wed Aug 3 05:13:48 +07 2022 mips
Mode: Gateway, SFE disabled, Wifi disabled, WAN disabled, Wireguard Endpoint for external VPS, connected via LAN to WRT1900ACS v2, Keep Alive reboot 6:05 in the morning
Reset: No
Status: Installed at release, ok.
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 10799
Location: Netherlands

PostPosted: Wed Aug 10, 2022 11:00    Post subject: Reply with quote
Lanchon wrote:
Linksys WRT160N v3
WRT160N v3 DD-WRT v3.0-r49626 mini (08/03/22)

previous installed build was from 2020

reset during flash via web, reset after flash via web, reset using reset button... but problem persists

DHCP server is non-functional on wired LAN (did not try WLAN), but if I configure a static IP on the PC, the router seems to work fine.

all configuration is default. this even happens in the forced password reset screen after reset.



confirmed on the next build also, will take action Smile

_________________
Routers:Netgear R7800, R7000, R6400v1, R6400v2, Linksys EA8500, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: 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
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 10799
Location: Netherlands

PostPosted: Thu Aug 11, 2022 14:13    Post subject: Reply with quote
egc wrote:
Lanchon wrote:
Linksys WRT160N v3
WRT160N v3 DD-WRT v3.0-r49626 mini (08/03/22)

previous installed build was from 2020

reset during flash via web, reset after flash via web, reset using reset button... but problem persists

DHCP server is non-functional on wired LAN (did not try WLAN), but if I configure a static IP on the PC, the router seems to work fine.

all configuration is default. this even happens in the forced password reset screen after reset.



confirmed on the next build also, will take action Smile


@lanchon, I am working with Sebastian to solve this issue, the last working build seems 47665 but I am still dissecting can you test if 47665 is working for you?

_________________
Routers:Netgear R7800, R7000, R6400v1, R6400v2, Linksys EA8500, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: 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
kernel-panic69
DD-WRT Guru


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

PostPosted: Thu Aug 11, 2022 14:42    Post subject: Reply with quote
@egc, @lanchon: I would have to dig out my K26 E4200 to see what build is on it. Some devices haven't really been touched in a while, but I'm pretty sure that it's a January 2022 build. But I haven't reset that device in a while, either. There are no caveats in the device wiki regarding LAN ports, so it may be a matter of wrong nvram / swconfig mapping (?).
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
At some point, people just get plain tired of this place.
Because they are tired of bottom-feeders and the same old hat.

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 10799
Location: Netherlands

PostPosted: Thu Aug 11, 2022 14:51    Post subject: Reply with quote
kernel-panic69 wrote:
@egc, @lanchon: I would have to dig out my K26 E4200 to see what build is on it. Some devices haven't really been touched in a while, but I'm pretty sure that it's a January 2022 build. But I haven't reset that device in a while, either. There are no caveats in the device wiki regarding LAN ports, so it may be a matter of wrong nvram / swconfig mapping (?).


That is what I first thought as there is something in the wiki about that but if I set a static IP on my PC all is fine and dandy Smile

It is just that DNSMasq is not running (and thus no DHCP)
For me Build 47665 is working and build 47695 is not

But it is always good if someone can confirm this

In between these builds there has been a DNSMasq update

_________________
Routers:Netgear R7800, R7000, R6400v1, R6400v2, Linksys EA8500, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: 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
kernel-panic69
DD-WRT Guru


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

PostPosted: Thu Aug 11, 2022 15:27    Post subject: Reply with quote
In the past, there have been "hands in the cookie jar", so if it was dnsmasq-specific breaking it, then it would be broken across all devices. Check nvram variables and dnsmasq configs. Listen interface should be br0, and check nvram show | grep dhcp , nvram show | grep dnsmasq , nvram show | grep lan_ output.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
At some point, people just get plain tired of this place.
Because they are tired of bottom-feeders and the same old hat.

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
fox95
DD-WRT Novice


Joined: 08 Aug 2022
Posts: 34

PostPosted: Thu Aug 11, 2022 16:00    Post subject: R8500 49626 Reply with quote
Router Name
Router Model Netgear R8500
Firmware Version DD-WRT v3.0-r49626 std (08/03/22)
Kernel VersionLinux 4.4.302-st20 #6851 SMP Wed Aug 3 04:03:45 +07 2022 armv7l
MAC Address
Hostname
WAN Domain Name
LAN Domain Name
Current TimeTime
Uptime 15:38

CPU ModelBroadcom BCM4709
CPU Cores2
CPU Features
EDSP FASTMULT HALF TLS
CPU Clock1400 MHz
Load Average
0%0.00, 0.01, 0.00
TemperaturesCPU 73.0 °C / WL0 55.3 °C / WL1 53.5 °C / WL2 52.5 °C


As stated in two forum threads the issues encountered have been loss of WIFI which was recovered by flashing in a very old dd wrt firmware version from year 2016 (ver. 30xxx) then flashing in the newest firmware 49626 and this caused the wifi to reappear.

second issue is that not all 6 physical ports are behaving properly. the first 4 act normal but ports 5 and 6 cannot have their own ip address and dhcp server. ports 5 and 6 will follow port 4 configuration. (ie. so whatever port 4 is setup to do, 5 and 6 appear to copy this)

other than that everything seems to work fine. i have various wifi clients on and off the router in the past 12 hours without loss or drop out.

the wifi speed is not ideal. more investigation into wifi speeds is necessary.
internet speeds over wired conections are fine and able to reach max available from cable modem into the facilty.
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 10799
Location: Netherlands

PostPosted: Thu Aug 11, 2022 16:35    Post subject: Reply with quote
kernel-panic69 wrote:
In the past, there have been "hands in the cookie jar", so if it was dnsmasq-specific breaking it, then it would be broken across all devices. Check nvram variables and dnsmasq configs. Listen interface should be br0, and check nvram show | grep dhcp , nvram show | grep dnsmasq , nvram show | grep lan_ output.


Two users with K2.6 report it is broken so it looks like it is broken for K2.6.

In the build thread in which I reported I already showed my dnsmasq.conf which looks OK

dnsmasq is present although a lot smaller than on my other routers, probably by design, further problem is that dnsmasq does not give any output also probably by design, the router reports it is not running so is syslog.

DNSMasq is running in build 47665 but not in build 47965, between those builds there has been a DNSMasq update. So that is suspicious

But it would be nice if someone with a k2.6 router can confirm that it works in 47665 and not in 47695 Smile

_________________
Routers:Netgear R7800, R7000, R6400v1, R6400v2, Linksys EA8500, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: 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
kernel-panic69
DD-WRT Guru


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

PostPosted: Thu Aug 11, 2022 23:03    Post subject: Reply with quote
@egc:

Probably need to see if this commit is culprit and only specific to mini (or other) builds:

https://github.com/mirror/dd-wrt/commit/aee319c696e033d97e7a34301001e79775aa93cd

This file existed @ 47665 (and so did that install line):

https://svn.dd-wrt.com/browser/src/router/udhcpd/config/dhcpd.startup?rev=47665

There is only one other location with similar code in /opt/micro/config:

https://svn.dd-wrt.com/browser/opt/etc/micro/config/dhcpd.startup?rev=47665

So I presume the one no longer being installed is for all non-micro builds across the board.
It looks to check use of jffs related to dhcp and set the proper nvram variables, and I couldn't track down any related code elsewhere yet. That is the only thing I can find at the moment and have not had the chance to check my K2.6 E4200 yet - but I have a feeling it's on mini builds only for K2.6 (and possibly other 4MB flash devices?) or related to doing a reset to defaults (caveat emptor?). I would check the associated nvram variables to see if that is what got b0rked as well. I could be totally wrong, it's been a long weary day.

_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
At some point, people just get plain tired of this place.
Because they are tired of bottom-feeders and the same old hat.

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Lanchon
DD-WRT Novice


Joined: 05 Oct 2019
Posts: 20

PostPosted: Fri Aug 12, 2022 5:20    Post subject: Reply with quote
hi @egc, @kernel-panic69,

thanks for helping.

dd-wrt.v24-47665_NEWD-2_K2.6_mini_wrt160nv3.bin: DHCP works
dd-wrt.v24-47692_NEWD-2_K2.6_mini_wrt160nv3.bin: DHCP does not work

some more info captured on dd-wrt.v24-49626_NEWD-2_K2.6_mini_wrt160nv3.bin:
Code:

root@Linksys WRT160N v3:/tmp# cat dnsmasq.conf
interface=br0
resolv-file=/tmp/resolv.dnsmasq
dhcp-leasefile=/tmp/dnsmasq.leases
dhcp-lease-max=190
dhcp-option=br0,3,192.168.1.1
dhcp-authoritative
dhcp-range=br0,192.168.1.64,192.168.1.253,255.255.255.0,1440m
bogus-priv
conf-file=/etc/rfc6761.conf
clear-on-reload
stop-dns-rebind
dhcp-option=252,"\n"
cache-size=1500

root@Linksys WRT160N v3:/tmp# cat resolv.dnsmasq

root@Linksys WRT160N v3:/tmp# cat dnsmasq.leases

root@Linksys WRT160N v3:/tmp# cat /etc/rfc6761.conf
# RFC6761 included configuration file for dnsmasq
#
# includes a list of domains that should not be forwarded to Internet name servers
# to reduce burden on them, asking questions that they won't know the answer to.

server=/bind/
server=/invalid/
server=/local/
server=/localhost/
server=/onion/
server=/test/

=====

root@Linksys WRT160N v3:/tmp# cat services/dnsmasq.0
sroot@Linksys WRT160N v3:/tmp#

======

root@Linksys WRT160N v3:/tmp# nvram show | grep dhcp
dhcpfwd_ip=0.0.0.0
pptp_use_dhcp=1
dhcp_start=192.168.1.64
dhcp_lease=1440
dhcpd_usenvram=0
dhcp_wins=wan
wan_proto=dhcp
lan_proto=dhcp
dhcpfwd_enable=0
dhcp_domain=wan
dhcp_num=190
l2tp_use_dhcp=1
dhcpd_options=
dhcpd_usejffs=0
dhcpc_vendorclass=
dhcpc_requestip=
size: 21137 bytes (11631 left)

root@Linksys WRT160N v3:/tmp# nvram show | grep dnsmasq
dnsmasq_enable=1
dnsmasq_cachesize=1500
dnsmasq_add_mac=0
dnsmasq_strict=0
dns_dnsmasq=1
auth_dnsmasq=1
dnsmasq_options=
dnsmasq_no_dns_rebind=1
dnsmasq_rc=0
size: 21137 bytes (11631 left)

root@Linksys WRT160N v3:/tmp# nvram show | grep lan_output
size: 21137 bytes (11631 left)

Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT 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