Random restarts andDetailed rsyslog (ddwrt kernel) messages.

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Author Message
tkmds
DD-WRT User


Joined: 04 Sep 2011
Posts: 161
Location: SA

PostPosted: Fri Jul 01, 2022 17:52    Post subject: Random restarts andDetailed rsyslog (ddwrt kernel) messages. Reply with quote
I have 3 AC-RT88U running DDWRT 47000+ firmware. After a recent power outage, all 3 randomly reboot outside regular reboot cycles I defined.

Logs's don't show anything of particular use. Not even messages around the time when the router restarted.

How can I increase the verbosity of the syslog messages coming out of the router to be able to tell why they keep resetting at random times?

Cheers,
Tom

_________________
Cheers, TK
------------------------
Sponsor
the-joker
DD-WRT Developer/Maintainer


Joined: 31 Jul 2021
Posts: 2146
Location: All over YOUR webs

PostPosted: Fri Jul 01, 2022 17:59    Post subject: Reply with quote
You can open a terminal to DD-WRT login and run nvram set console_debug=1 && nvram commit && reboot this enables verbose kernel messages.

Best really are serial logs, these will show whats going on behind the curtains.

However you are running as seriously outdated DD-WRT version my recommendation is upgrade, nvram reset and reconfigure from scratch , many issues fixed and security patches amongst at few.

http://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2022/06-29-2022-r49392/asus-rt-ac88u

Also detail which driver youre using, standard or experimental.

For your DD-WRT version however there is no support.

_________________
Saving your retinas from the burn!🔥
DD-WRT Inspired themes for routers
DD-WRT Inspired themes for the phpBB Forum
DD-WRT Inspired themes for the SVN Trac & FTP site
Join in for a chat @ #style_it_themes_public:matrix.org or #style_it_themes:discord

DD-WRT UI Themes Bug Reporting and Discussion thread

Router: ANus RT-AC68U E1 (recognized as C1)
dale_gribble39
DD-WRT Guru


Joined: 11 Jun 2022
Posts: 1900

PostPosted: Fri Jul 01, 2022 18:08    Post subject: Re: Random restarts andDetailed rsyslog (ddwrt kernel) messa Reply with quote
tkmds wrote:
I have 3 AC-RT88U running DDWRT 47000+ firmware. After a recent power outage, all 3 randomly reboot outside regular reboot cycles I defined.

Have you examined the devices and their AC power adapters and associated surge suppressors for signs of damage?

_________________
"The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost

"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio

<fact>code knows no gender</fact>

This is me, knowing I've ruffled your feathers, and not giving a ****
Some people are still hard-headed.

--------------------------------------
Mac Pro (Mid 2012) - Two 2.4GHz 6-Core Intel Xeon E5645 processors 64GB 1333MHz DDR3 ECC SDRAM OpenSUSE Leap 15.5
tkmds
DD-WRT User


Joined: 04 Sep 2011
Posts: 161
Location: SA

PostPosted: Fri Jul 01, 2022 19:26    Post subject: Reply with quote
"nvram set console_debug=1 && nvram commit"

I've set this. Thank you very much for this. Do you know if this also helps log WiFi connectivity issues? Also struggling why disconnects occur here.

So the 4 routers have these firmware versions:

DD-WRT v3.0-r49139 std (06/10/22) - WRT3200
DD-WRT v3.0-r48646 std (04/12/22) - AC-RT88U - Router 1
DD-WRT v3.0-r49326 std (06/23/22) - AC-RT88U - Router 2
DD-WRT v3.0-r47153 std (08/13/21) - AC-RT88U - Router 3

Router 3 is most stable so far. Though, given your comment, I think I'll try the latest here as well and see how that fares in the next few days.

I think I figured out the culprit though I'm not 100% yet. Each router is configured to reboot at 2AM each night but is also configured to source the time from a single internal NTP server.

This internal NTP server is currently offline. Meaning the date on each router is pretty much random. So the cron that kicks off the job now kicks off against the time of the current set date and time, which is already off.

Idea behind the internal NTP sever is not to have 100's of devices off my network ping an external source, but just one, then the rest of the 99 devices can use the internal one for time sync.

Part of being a good 'netizen' I suppose, and not overload external NTP servers too much. Smile

"Have you examined the devices and their AC power adapters and associated surge suppressors for signs of damage?"
Did examine them. Aside from some more frequent WiFi disconnects, which could be attributed to the reboots, everything else seems to work ok.

Cheers,

_________________
Cheers, TK
------------------------
dale_gribble39
DD-WRT Guru


Joined: 11 Jun 2022
Posts: 1900

PostPosted: Fri Jul 01, 2022 19:31    Post subject: Reply with quote
tkmds wrote:
I think I figured out the culprit though I'm not 100% yet. Each router is configured to reboot at 2AM each night but is also configured to source the time from a single internal NTP server.

This internal NTP server is currently offline. Meaning the date on each router is pretty much random. So the cron that kicks off the job now kicks off against the time of the current set date and time, which is already off.

I suspect that aside from updating firmware, this is the crux of your problems; there are things that rely on NTP to be in sync, such as your scheduled reboot.

_________________
"The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost

"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio

<fact>code knows no gender</fact>

This is me, knowing I've ruffled your feathers, and not giving a ****
Some people are still hard-headed.

--------------------------------------
Mac Pro (Mid 2012) - Two 2.4GHz 6-Core Intel Xeon E5645 processors 64GB 1333MHz DDR3 ECC SDRAM OpenSUSE Leap 15.5
the-joker
DD-WRT Developer/Maintainer


Joined: 31 Jul 2021
Posts: 2146
Location: All over YOUR webs

PostPosted: Sat Jul 02, 2022 12:17    Post subject: Reply with quote
So you know, NTP is essential on consumer routers since they dont have a real time clock only software clock and depending on CPU load this will skew more on higher loads.

Everything then that depends on cron will be all over the place, firewall, some services and logging, all affected by bad local time.

You can on recent current dd-wrt release, tweak the NTP update interval, by default its one hour, but 48 hours will be a never mind (little skew then if any) and better your Netizenship status.

As for console_debug, no it shouldn't help anything wifi related best it will do is print verbose kernel messages it will be a great deal of entries as you will notice,

You should be running same builds across routers, some wifi drivers were updated recently, since this is broadcom its also closed source wifi drivers.

You still didn't say which drivers you were using, standard or experimental... Which reports on older fw dont matter until you're running latest dd-wrt, then reports matter and accurate driver info matters.

_________________
Saving your retinas from the burn!🔥
DD-WRT Inspired themes for routers
DD-WRT Inspired themes for the phpBB Forum
DD-WRT Inspired themes for the SVN Trac & FTP site
Join in for a chat @ #style_it_themes_public:matrix.org or #style_it_themes:discord

DD-WRT UI Themes Bug Reporting and Discussion thread

Router: ANus RT-AC68U E1 (recognized as C1)
Duxa
DD-WRT User


Joined: 16 Aug 2013
Posts: 191

PostPosted: Sat Jul 02, 2022 18:33    Post subject: Reply with quote
use any one of the following ntp servers (or use built in defaults):

Code:

pool.ntp.org
time.google.com
time.cloudflare.com
time.apple.com
time-a-g.nist.gov
time.esa.int


Alternatively you can set up your own ntp server running on pretty much anything (like a RaspberryPi, although something with internal battery would be better), or with one of those public NTP servers have the ddwrt router be your NTP server for rest of your network.

I run my own server, and use time.is to check the deviation from atomic clock.
tkmds
DD-WRT User


Joined: 04 Sep 2011
Posts: 161
Location: SA

PostPosted: Sat Jul 02, 2022 22:03    Post subject: Reply with quote
The routers with the 49000+ firmware didn't exhibit the same reboot after NTP was set. The routers running the older firmware did reboot outside their scheduled reboot cycle. All are running OSPF for my multiple VLAN's defined off 2 Cisco switches. Works great. All VLAN's are visible. So I need OSPF.

dmesg messages:

[ DD-WRT v3.0-r49139 std (06/10/22) - WRT3200 ]

# dmesg|grep -Ei "warn|error|fail|denied|invalid|inacc"
[ 0.000000] mvebu_mbus: [Firmware Warn]: deprecated mbus-mvebu Device Tree, suspend/resume will not work
[ 0.049412] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.049419] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 12.868015] ubi1 warning: ubi_eba_init: cannot reserve enough PEBs for bad PEB handling, reserved 32, need 40
[ 12.943064] UBIFS error (pid: 1087): cannot open "ubi1:ddwrt", error -19
[ 54.108999] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x4d error, result=0x1
[ 54.116849] mwifiex_sdio mmc0:0001:1: set mac address failed: ret=-1



[ DD-WRT v3.0-r48646 std (04/12/22) - AC-RT1300 - Router 1 ] - AC RT1300 not AC RT88U

# dmesg|grep -Ei "warn|error|fail|denied|invalid|inacc"
pci 0000:00:11.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
wl driver 7.14.164.18 (r692288) failed with code 1
wl driver 7.14.164.18 (r692288) failed with code 1
CONSOLE: 026738.675 Malloc failure count: 0
CONSOLE: 026738.679 Malloc failure count: 0
hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)



[ DD-WRT v3.0-r49326 std (06/23/22) - AC-RT88U - Router 2 ]

# dmesg|grep -Ei "warn|error|fail|denied|invalid|inacc"
[ 0.248371] pci 0000:00:11.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
[ 11.111480] wl driver 7.14.164.18 (r692288) failed with code 1
[ 11.223370] wl driver 7.14.164.18 (r692288) failed with code 1
[ 13.597424] CONSOLE: 026738.674 Malloc failure count: 0
[ 14.336037] CONSOLE: 026738.679 Malloc failure count: 0
[ 19.895357] wl0.1: set cur_etheraddr failed
[ 19.899780] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 19.910375] wl0.2: set cur_etheraddr failed
[ 19.914908] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 21.709979] wl1.1: set cur_etheraddr failed
[ 21.714375] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 21.722020] wl1.2: set cur_etheraddr failed
[ 21.726408] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 29.465379] wl0.1: set cur_etheraddr failed
[ 29.469877] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 29.489397] wl0.2: set cur_etheraddr failed
[ 29.499236] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 31.659748] wl1.1: set cur_etheraddr failed
[ 31.664292] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 31.713850] wl1.2: set cur_etheraddr failed
[ 31.718313] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 47.809102] hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)
[19649.434054] jffs2: warning: (1680) jffs2_sum_write_data: Not enough space for summary, padsize = -1449



[ DD-WRT v3.0-r47153 std (08/13/21) - AC-RT88U - Router 3 ]

# dmesg|grep -Ei "warn|error|fail|denied|invalid|inacc"
pci 0000:00:11.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
wl driver 7.14.164.18 (r692288) failed with code 1
wl driver 7.14.164.18 (r692288) failed with code 1
CONSOLE: 026738.675 Malloc failure count: 0
CONSOLE: 026738.679 Malloc failure count: 0
hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)


Looking at the syslog messages:

[ DD-WRT v3.0-r49139 std (06/10/22) - WRT3200 ]
[ DD-WRT v3.0-r48646 std (04/12/22) - AC-RT1300 - Router 1 ] - AC RT1300 not AC RT88U
[ DD-WRT v3.0-r49326 std (06/23/22) - AC-RT88U - Router 2 ]
[ DD-WRT v3.0-r47153 std (08/13/21) - AC-RT88U - Router 3 ]





After the upgrade to r49392:

[ DD-WRT v3.0-r49139 -> r49392 std (06/10/22) - WRT3200 ]

# dmesg|grep -Ei "warn|error|fail|denied|invalid|inacc"
[ 0.000000] mvebu_mbus: [Firmware Warn]: deprecated mbus-mvebu Device Tree, suspend/resume will not work
[ 0.049492] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.049498] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 12.878996] ubi1 warning: ubi_eba_init: cannot reserve enough PEBs for bad PEB handling, reserved 32, need 40
[ 12.954072] UBIFS error (pid: 1088): cannot open "ubi1:ddwrt", error -19
[ 54.268395] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x4d error, result=0x1
[ 54.276347] mwifiex_sdio mmc0:0001:1: set mac address failed: ret=-1



[ DD-WRT v3.0-r48646 -> r49392 std (04/12/22) - AC-RT1300 - Router 1 ]

# dmesg|grep -Ei "warn|error|fail|denied|invalid|inacc"
[ 8.685687] wl driver 7.14.164.18 (r692288) failed with code 1
[ 8.797533] wl driver 7.14.164.18 (r692288) failed with code 1
[ 11.352140] CONSOLE: 026738.680 Malloc failure count: 0
[ 12.001882] CONSOLE: 026738.691 Malloc failure count: 0
[ 17.543360] wl0.1: set cur_etheraddr failed 1
[ 17.543369] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 18.918273] wl1.1: set cur_etheraddr failed 1
[ 18.922902] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 22.623565] jffs2: Error: jffs2_decompress returned -5
[ 22.628805] jffs2: read_cache_page() returned error: -5
[ 22.634155] jffs2: Error garbage collecting node at 058c06f0!
[ 25.816489] wl0.1: set cur_etheraddr failed 1
[ 25.821123] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 27.526213] wl1.1: set cur_etheraddr failed 1
[ 27.530870] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 43.575850] hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)
[ 93.798710] jffs2: Error: jffs2_decompress returned -5
[ 93.803950] jffs2: read_cache_page() returned error: -5
[ 93.809195] jffs2: Error garbage collecting node at 058c06f0!
[ 143.781753] jffs2: Error: jffs2_decompress returned -5
[ 143.786943] jffs2: read_cache_page() returned error: -5
[ 143.792213] jffs2: Error garbage collecting node at 058c06f0!


[ DD-WRT v3.0-r49326 -> r49392 std (06/23/22) - AC-RT88U - Router 2 ]

# dmesg|grep -Ei "warn|error|fail|denied|invalid|inacc"
[ 0.248780] pci 0000:00:11.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
[ 11.001317] wl driver 7.14.164.18 (r692288) failed with code 1
[ 11.113173] wl driver 7.14.164.18 (r692288) failed with code 1
[ 13.337648] CONSOLE: 026738.675 Malloc failure count: 0
[ 14.352764] CONSOLE: 026738.679 Malloc failure count: 0
[ 19.976269] wl0.1: set cur_etheraddr failed 1
[ 19.980882] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 19.987772] wl0.2: set cur_etheraddr failed 2
[ 19.992404] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 21.771865] wl1.1: set cur_etheraddr failed 1
[ 21.776523] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 21.784117] wl1.2: set cur_etheraddr failed 2
[ 21.788691] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 29.915405] wl0.1: set cur_etheraddr failed 1
[ 29.920080] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 29.941538] wl0.2: set cur_etheraddr failed 2
[ 29.946181] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 32.083386] wl1.1: set cur_etheraddr failed 1
[ 32.088079] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 32.118015] wl1.2: set cur_etheraddr failed 2
[ 32.122763] dhd_set_mac_addr_handler: _dhd_set_mac_address() failed
[ 48.328340] hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)



[ DD-WRT v3.0-r47153 -> r49392 std (08/13/21) - AC-RT88U - Router 3 ]

# dmesg|grep -Ei "warn|error|fail|denied|invalid|inacc"
[ 0.248655] pci 0000:00:11.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
[ 11.050770] wl driver 7.14.164.18 (r692288) failed with code 1
[ 11.162606] wl driver 7.14.164.18 (r692288) failed with code 1
[ 13.474664] CONSOLE: 026738.675 Malloc failure count: 0
[ 14.662378] CONSOLE: 026738.680 Malloc failure count: 0
[ 43.760580] hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)




DD-WRT v3.0-r48646, DD-WRT v3.0-r47153 - Seems most stable for WiFi however the NTP setting to reach a remote NTP server did not work. So date was still wrong and both rebooted at different times. Date was probably wrong since host resolution didn't work so couldn't get an IP from the NTP server name. However, fixed this with a few F/W rules:

# ----------------------
# Google DNS
# ----------------------
iptables -A INPUT -s 8.8.8.8 -p tcp --sport 53 -j ACCEPT
iptables -A INPUT -s 8.8.4.4 -p tcp --sport 53 -j ACCEPT
iptables -A INPUT -s 8.8.8.8 -p udp --sport 53 -j ACCEPT
iptables -A INPUT -s 8.8.4.4 -p udp --sport 53 -j ACCEPT

# ----------------------
# NTP Date/Time
# ----------------------
iptables -A OUTPUT -p udp --dport 123 -j ACCEPT
iptables -A INPUT -p udp --sport 123 -j ACCEPT

OSPF seems to be running fine on all of the routers with the latest F/W.

By drivers, did you mean this line?

[ 11.050770] wl driver 7.14.164.18 (r692288) failed with code 1

Now date is ok. Resolves to ca.pool.ntp.org just fine. (facepalm). When switching to an external NTP pool from an internal one, forgot external ones may be blocked via iptables. Will see tomorrow or later today to see how things fared and if there's any unintended reboots.

Cheers,

_________________
Cheers, TK
------------------------
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 6414
Location: UK, London, just across the river..

PostPosted: Sun Jul 03, 2022 9:10    Post subject: Reply with quote
-update drivers as last builds contain security fixes..IMPORTANT 49392 is the current
-use numeric format (IP) for NTP time, best NTP time:

216.239.35.4 or 216.239.35.8 (google)
162.159.200.1 or 162.159.200.123 (cloudflare)

p.s. i rather to stay away from google DNS...@#$%^&*( Twisted Evil
i use 9.9.9.9 instead...gives me a better sleep Razz Razz

also you can fairly use the SmartDNS encrypted DNS to improve security ... on the last build 49392 after you turn it on you need to add only few lines in this format to SmartDNS box....

server-https https://1.1.1.1/dns-query
server-https https://9.9.9.9/dns-query
server-tls 9.9.9.9:853 -host-name: dns.quad9.net/dns-query
server-tls 78.46.244.143:853 -host-name: dot-de.blahdns.com

use your preferred servers... Cool

_________________
Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
the-joker
DD-WRT Developer/Maintainer


Joined: 31 Jul 2021
Posts: 2146
Location: All over YOUR webs

PostPosted: Sun Jul 03, 2022 9:29    Post subject: Reply with quote
@tkmds and still, I hate to be a nag but no report from you whether you are using default driver firmware or experimental.
_________________
Saving your retinas from the burn!🔥
DD-WRT Inspired themes for routers
DD-WRT Inspired themes for the phpBB Forum
DD-WRT Inspired themes for the SVN Trac & FTP site
Join in for a chat @ #style_it_themes_public:matrix.org or #style_it_themes:discord

DD-WRT UI Themes Bug Reporting and Discussion thread

Router: ANus RT-AC68U E1 (recognized as C1)
kernel-panic69
DD-WRT Guru


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

PostPosted: Sun Jul 03, 2022 17:49    Post subject: Reply with quote
Any wl driver 7.14.164.18 (r692288) and dhd entries in syslog/klog mean proprietary binary driver blobs, usually. Pretty sure that it would likely have brcmfmac entries if it were experimental driver.

DD-WRT: Missing 5Ghz settings and kern.warn kernel: wl driver 7.14.164.18 (r692288) failed with code 1

#7456 closed (fixed)
D-Link 868L Rev A - nvram reset when re-booting - build r47182


New Build - 12/09/2021 - r47822 - Page 2 (Abboo)

New Build - 05/13/21 - r46640 - Page 3(claudinel)

_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

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


Joined: 04 Sep 2011
Posts: 161
Location: SA

PostPosted: Mon Jul 04, 2022 0:16    Post subject: Reply with quote
the-joker wrote:
@tkmds and still, I hate to be a nag but no report from you whether you are using default driver firmware or experimental.


Ehhh ... though you're referring to the

wl driver 7.14.164.18

driver? Smile Which driver and how do I tell the version?

@Alozaros ---

Tyvm! Had no idea 9.9.9.9 and 1.1.1.1 existed. Appreciate this!

"-update drivers as last builds contain security fixes..IMPORTANT 49392 is the current"

So we can update the wireless driver outside of the FW upgrade? How?

@kernel-panic69 ---

Ya, I moved my FW rules to a file on /jffs or /opt (In the case of WRT3200ACM router) to save on nvram. So many issues went away when I moved the rules to permanent storage. ( Btw, you've stumbled on my blog post. Wink )

Need more time to go through the rest of the posts however. So far with the NTP update, all routers restarted when scheduled, and WiFi has been stable, aside from some above quirks I mentioned and notes on this post:

https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1266283#1266283

On the topic of nvam being exhausted, just ran a check for 'backtrace:' in the syslog files collected earlier. Back in April it was indeed caused due to the F/W rules clogging up the nvram it seems:

-----
Code:
dd-wrt-heimdall.the.abyss.log-20220607.gz:--
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: 2231 total pagecache pages
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: 0 pages in swap cache
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: Swap cache stats: add 0, delete 0, find 0/0
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: Free swap  = 0kB
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: Total swap = 0kB
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: 131072 pages RAM
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: 98304 pages HighMem/MovableOnly
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: 2645 pages reserved
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ pid ]   uid  tgid total_vm      rss nr_ptes nr_pmds swapents oom_score_adj name
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [  668]     0   668      195       39       4       0        0             0 hotplug2
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [  672]     0   672      206       64       3       0        0             0 mstpd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [  676]     0   676      245      139       3       0        0             0 irqbalance
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [  736]     0   736      394      202       3       0        0             0 watchdog
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 1060]     0  1060      363      194       3       0        0             0 syslogd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 1062]     0  1062      363      170       4       0        0             0 klogd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 1071]     0  1071      187       13       3       0        0             0 p910nd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 1122]     0  1122      307       59       3       0        0             0 dropbear
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 1501]     0  1501      424      114       5       0        0             0 ttraff
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 1650]     0  1650      321       41       3       0        0             0 dhcp6c
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 1676]     0  1676      367      191       4       0        0             0 watchquagga
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 1678]     0  1678      379      110       4       0        0             0 wland
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 1690]     0  1690      425      171       3       0        0             0 dnsmasq
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 1700]     0  1700      317      173       3       0        0             0 radvd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 1701]     0  1701      317       40       3       0        0             0 radvd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2143]     0  2143      394       70       3       0        0             0 process_monitor
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2146]     0  2146      286      115       4       0        0             0 scc
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2147]     0  2147      363       88       3       0        0             0 udhcpc
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2155]     0  2155      392      223       5       0        0             0 nas
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2156]     0  2156      392      118       3       0        0             0 nas
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2157]     0  2157      392      212       4       0        0             0 nas
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2158]     0  2158      392      117       5       0        0             0 nas
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2164]     0  2164     1140      154       5       0        0             0 httpd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2165]     0  2165      329      141       3       0        0             0 resetbutton
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2265]     0  2265      248       57       4       0        0             0 usbipd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2338]     0  2338      368       72       3       0        0             0 zabbix_agentd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2340]     0  2340      368      219       3       0        0             0 zabbix_agentd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2341]     0  2341      370      207       3       0        0             0 zabbix_agentd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2342]     0  2342      370      108       3       0        0             0 zabbix_agentd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2343]     0  2343      370      207       3       0        0             0 zabbix_agentd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2344]     0  2344      370      109       3       0        0             0 zabbix_agentd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2345]     0  2345      370      108       3       0        0             0 zabbix_agentd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2410]     0  2410      188      104       4       0        0             0 cron
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [ 2461]     0  2461      454      316       3       0        0             0 ripd
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: Out of memory: Kill process 2461 (ripd) score 2 or sacrifice child
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: Killed process 2461 (ripd) total-vm:1816kB, anon-rss:392kB, file-rss:872kB
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: zabbix_agentd invoked oom-killer: gfp_mask=0x26040d0, order=0, oom_score_adj=0
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: zabbix_agentd cpuset=/ mems_allowed=0
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: CPU: 1 PID: 2340 Comm: zabbix_agentd Tainted: P                4.4.302 #5717
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: Hardware name: Northstar Prototype
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: Backtrace:
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<80012988>] (dump_backtrace) from [<80012c0c>] (show_stack+0x18/0x1c)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r7:87265388 r6:20000013 r5:00000000 r4:8055e9e4
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<80012bf4>] (show_stack) from [<80014b84>] (dump_stack+0x94/0xa8)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<80014af0>] (dump_stack) from [<800140e4>] (dump_header+0x54/0x17c)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r7:87265388 r6:00000000 r5:8374bbec r4:87265380
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<80014090>] (dump_header) from [<800b74c4>] (oom_kill_process+0x8c/0x3b8)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r10:87265380 r9:00000001 r8:87265728 r7:87265388 r6:0001f5ab r5:8374bbec
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r4:87265380
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<800b7438>] (oom_kill_process) from [<800b7a34>] (out_of_memory.part.0+0x244/0x2ec)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r10:87265380 r9:000000de r8:80551fe0 r7:80552188 r6:0001f5ab r5:8374bbec
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r4:879f58ec
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<800b77f0>] (out_of_memory.part.0) from [<800b7b80>] (out_of_memory+0x64/0x6c)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r10:00000000 r9:026040d0 r8:aaaaaaab r7:00000000 r6:00000000 r5:00000000
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r4:8374bbec
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<800b7b1c>] (out_of_memory) from [<800bc068>] (__alloc_pages_nodemask+0x7c0/0x8ac)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r4:8374a000
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<800bb8a8>] (__alloc_pages_nodemask) from [<800ef0bc>] (allocate_slab+0x1fc/0x294)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r10:00000000 r9:8780c320 r8:0000000a r7:022152d0 r6:026040d0 r5:00000000
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r4:8780c320
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<800eeec0>] (allocate_slab) from [<800efb78>] (___slab_alloc.constprop.0+0x2d4/0x43c)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r10:00020000 r9:8780c320 r8:86964880 r7:00000014 r6:80140014 r5:00000000
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r4:00000000
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<800ef8a4>] (___slab_alloc.constprop.0) from [<800efdf0>] (kmem_cache_alloc+0x110/0x1b0)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r10:00020000 r9:874c3f94 r8:8740c020 r7:60000013 r6:024000c0 r5:00000000
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r4:8780c320
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<800efce0>] (kmem_cache_alloc) from [<801499d0>] (proc_alloc_inode+0x28/0x94)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r9:874c3f94 r8:8740c020 r7:874c3f68 r6:879f7180 r5:8780a400 r4:879f71c0
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<801499a8>] (proc_alloc_inode) from [<801155d8>] (alloc_inode+0x24/0xac)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r5:8780a400 r4:879f71c0
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<801155b4>] (alloc_inode) from [<801161d4>] (new_inode+0x14/0xa0)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r5:879f7180 r4:879f71c0
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<801161c0>] (new_inode) from [<8014a140>] (proc_get_inode+0x18/0x120)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r5:879f7180 r4:879f71c0
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<8014a128>] (proc_get_inode) from [<8014f3c8>] (proc_lookup_de+0x11c/0x158)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r5:00000004 r4:879f71c0
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<8014f2ac>] (proc_lookup_de) from [<8014f420>] (proc_lookup+0x1c/0x20)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r9:874c3f68 r8:00000000 r7:8374beb0 r6:00000101 r5:874c3f68 r4:8740c020
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<8014f404>] (proc_lookup) from [<8014a690>] (proc_root_lookup+0x34/0x38)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<8014a65c>] (proc_root_lookup) from [<8010a1c0>] (path_openat+0xa10/0x1258)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r7:8374beb0 r6:8374bf5c r5:8740c020 r4:87402198
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<801097b0>] (path_openat) from [<8010c1b8>] (do_filp_open+0x6c/0xd0)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r10:00000000 r9:8374a000 r8:80009784 r7:8374beb0 r6:00000001 r5:8374bf5c
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r4:00000005
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<8010c14c>] (do_filp_open) from [<800fb010>] (do_sys_open+0x168/0x1e8)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r7:fffff000 r6:8372a000 r5:ffffff9c r4:00000005
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<800faea8>] (do_sys_open) from [<800fb0b4>] (SyS_open+0x24/0x28)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel:  r9:8374a000 r8:80009784 r7:00000005 r6:00040494 r5:0003eaa7 r4:00000000
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: [<800fb090>] (SyS_open) from [<800095c0>] (ret_fast_syscall+0x0/0x40)
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: Mem-Info:
dd-wrt-heimdall.the.abyss.log-20220607.gz:Jun  5 14:52:34 dd-wrt-heimdall.the.abyss kernel: active_anon:840 inactive_anon:54 isolated_anon:0

-----


All my routers have been upgraded to version r49392 since my earlier post.

Cheers,

_________________
Cheers, TK
------------------------
the-joker
DD-WRT Developer/Maintainer


Joined: 31 Jul 2021
Posts: 2146
Location: All over YOUR webs

PostPosted: Mon Jul 04, 2022 8:21    Post subject: Reply with quote
tkmds wrote:
the-joker wrote:
@tkmds and still, I hate to be a nag but no report from you whether you are using default driver firmware or experimental.


Ehhh ... though you're referring to the

wl driver 7.14.164.18

driver? Smile Which driver and how do I tell the version?


No, Im talking about the DD-WRT version you flashed.

See screenshot.

Anything in the Experimental folder will likely have issues. And you shouldnt switch between those builds without a nvram reset and re-configuring from scratch just in case.

The regular file will be better as those drivers are pretty much default broadcom and dhd driver has recently been updated.



Capture.PNG
 Description:
 Filesize:  23.53 KB
 Viewed:  2627 Time(s)

Capture.PNG



_________________
Saving your retinas from the burn!🔥
DD-WRT Inspired themes for routers
DD-WRT Inspired themes for the phpBB Forum
DD-WRT Inspired themes for the SVN Trac & FTP site
Join in for a chat @ #style_it_themes_public:matrix.org or #style_it_themes:discord

DD-WRT UI Themes Bug Reporting and Discussion thread

Router: ANus RT-AC68U E1 (recognized as C1)
tkmds
DD-WRT User


Joined: 04 Sep 2011
Posts: 161
Location: SA

PostPosted: Tue Jul 05, 2022 3:15    Post subject: Reply with quote
Ah, no, I never choose experimental.

I stick to the FW off this FTP site. For example.

http://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2022/06-29-2022-r49392/linksys-wrt3200acm/

_________________
Cheers, TK
------------------------
Display posts from previous:    Page 1 of 1
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