Joined: 18 Aug 2009 Posts: 597 Location: Antigua/Seattle
Posted: Sun Feb 18, 2018 15:58 Post subject:
I've had it going for almost 24 hours no issues but I didn't expect any still older Kernel.
Router Name
DD-WRT
Router Model
Linksys WRT3200ACM
Firmware Version
DD-WRT v3.0-r35034 std (02/17/1
Kernel Version
Linux 4.9.82-rc1 #103 SMP PREEMPT Sat Feb 17 02:15:39 CET 2018
35034
driver name: mwlwifi
chip type: 88W8964
hw version: 7
driver version: 10.3.4.0-20180118
firmware version: 0x09030204
power table loaded from dts: no
firmware region code: 0x10
mac address: 60:38:e0:13:xx:xx
2g: enable
5g: disable
antenna: 4 4
irq number: 47
ap macid support: 0000ffff
sta macid support: 00010000
macid used: 00000001
radio: enable
iobase0: e1000000
iobase1: e1280000
tx limit: 1024
rx limit: 16384 _________________ WRT3200ACM
Joined: 02 Aug 2017 Posts: 153 Location: Central Michigan
Posted: Sun Feb 18, 2018 17:04 Post subject:
Up and running but I just loaded, so a little early to tell for me. _________________ ISP: Charter
Modem: Netgear CM600
Router:(2) Asus RT-AC86U Merlin 384.5
Router: LinksysWRT3200Acm{RIP}
Router: Linksys EA8500 kongat r35030m (Vpn)
Router: Netgear X4S kongat r35965M
Vpn: IpVanish
Unbrick your 3200acm with usb to ttl cable: https://tinyurl.com/y9azvrkg
Posted: Mon Feb 19, 2018 2:25 Post subject: Frequency of updates?
I'm wondering how often it makes sense to update my WRT1900ACS/v2. Is it prudent to update with every new release, if I'm not experiencing any problems?
Thanks!
P.S. With R34929, I'm seeing these lines in the syslog, which I've not seen in previous releases.
Feb 19 02:00:47 xxxxx daemon.debug ntpclient[5732]: Connecting to time.apple.com [17.253.20.253] ...
Feb 19 02:00:47 xxxxx daemon.info ntpclient[5732]: Time set from time.apple.com [17.253.20.253].
Feb 19 02:00:47 xxxxx daemon.err process_monitor[1697]: cyclic NTP Update success (servers time.apple.com _________________ Router: Linksys WRT1900ACSv2
Modem: Verizon Fios DD-WRT v3.0-r44048 std (08/02/20)
ISP: Verizon Fios
NAS: ReadyNas314
Joined: 18 Aug 2009 Posts: 597 Location: Antigua/Seattle
Posted: Mon Feb 19, 2018 3:13 Post subject: Re: Frequency of updates?
giles02134 wrote:
I'm wondering how often it makes sense to update my WRT1900ACS/v2. Is it prudent to update with every new release, if I'm not experiencing any problems?
Thanks!
P.S. With R34929, I'm seeing these lines in the syslog, which I've not seen in previous releases.
Feb 19 02:00:47 xxxxx daemon.debug ntpclient[5732]: Connecting to time.apple.com [17.253.20.253] ...
Feb 19 02:00:47 xxxxx daemon.info ntpclient[5732]: Time set from time.apple.com [17.253.20.253].
Feb 19 02:00:47 xxxxx daemon.err process_monitor[1697]: cyclic NTP Update success (servers time.apple.com
Those are debug messages not meant for public consumption.
They show in red simply to make them stand out better.
It's not an actual error as you can see by reading it.
I would NEVER update if my router were working perfectly for my needs! Unless it was needed for security. _________________ WRT3200ACM
Joined: 18 Aug 2009 Posts: 597 Location: Antigua/Seattle
Posted: Mon Feb 19, 2018 4:26 Post subject:
giles02134 wrote:
Yes...I figured as much. I only asked because it was new for me in this release.
Point taken about updates. Thanks again!
I thought the debug has been there for some time but I'm not so sure now because I've been testing some builds not released so maybe it's new since the last beta I guess.
There is a little story there if you follow the git hubs in development it was found at one point the removal of it caused the ntp to quite again so maybe to expedite things it was just left.
It would probably take a bit of time to figure out why something that's supposed to only monitor a function could effect it like that.
Most likely a call that's captured by the logging script and it needs to be mended/forwarded before the debug can be removed.
As for using the latest builds I think it would depend on what your goal is. If you just want the most reliable set up with the least abount of effort I'd find a build that does everything you want, and stick with it.
In my case with this particular router I need some functions that it's raw computing power will be handy for, there are few options for what I'm doing.
The CPU is pretty fast by router standards and it is a lot of stuff in a small box, I've settled on an older build that fits my needs, I've only followed the updates to help testing and submitting in the Git Hub discussions.
There are some on these forums who will load a new beta version just because it's the latest and I see this typical post.... "Just flashed rxxxxx and now my xxx stopped working what's the problem the last build was just fine."
And I'm sittin here on my crusty old ass saying, in my forgetful gray head......WTF?..........as it moves slowly side to side. _________________ WRT3200ACM
Installed r35034-2018.02.17 on my WRT1900ACS_v1 as a flash upgrade, keeping existing config. No issues for my config noticed yet, will report if find anything big.
DD-WRT config reference for my WRT1900ACS_v1 (not vanilla, not overly complex): mostly wired devices ~75, mixed wireless mode + fixed channels using 5GHz & 2.4GHz @ 20MHz width ~20 clients, IPv6 on, OpenVPN server + segmented network, DHCP reservations for all known devices, access rules (internet block sec cameras), port forwards, no QOS, firewall rules (OpenVPN & Guest), Guest 2.4GHz wifi segmented network
Joined: 11 Feb 2016 Posts: 198 Location: South London
Posted: Mon Feb 19, 2018 16:51 Post subject:
DaveI wrote:
For those that use it (like me)...
DLNA has not been fixed yet in this version.
Ticket submitted in previous recent version
by Eyerex.
--------------
WRT1900ACSV2
Cheers for the info only good thing about it not working is i've been playing with Plex on a Pi _________________ | Netgear Nighthawk X4S R7800 | Linksys WRT1900ACS V1 | Huawei Echolife HG612 3B |
Posted: Mon Feb 19, 2018 18:12 Post subject: Re: Frequency of updates?
aairon wrote:
I would NEVER update if my router were working perfectly for my needs! Unless it was needed for security.
And unless you very careful track all the changelog and often completely cryptic commit messages, you won't know if it's needed for security, so it's better to update it fairly often