Latest firmware for WRT54GL

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


Joined: 25 Oct 2013
Posts: 2613
Location: Indy

PostPosted: Sun Jan 26, 2020 15:16    Post subject: Reply with quote
ThaCrip wrote:
but assuming the caps are going to bad... is it even worth fixing? ; because I suspect it depends on cost as if it can be fixed for next to nothing it might be worth attempting to fix it and, if I bother with that, I wonder if it would be worth swapping the caps on the Linksys WRT54GS v1.1 I got(which I never opened up yet to see what's in there)? (but I am still testing to see how it fairs over the next month or two as I figure if it does not act up by then, it should be stable).
[...]
even touching it (WL-520gU's main chip) with my finger [...] it's a bit warm (as I can feel some heat in it vs some of the other chips feel more neutral to the touch) but it's not even slightly close to burning me.
BCM53xx chips run pretty cool, so a heatsink isn't needed unless in extreme ambients (or clocking over 250, but the Asus' 5354 is locked at 240 anyway).

Should you bother? ...that all depends on you. Wink They are pretty easy to swap. Fwiw, I've got caps that I could sell cheap, and so far have been able to ship w/ just a stamp. PM if interested. Smile

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 20.7.4|FT2020.6: EA6900v1.1@1GHz, F7D8302@532|DD 44758: DIR-810L, WNDR4500v2 & 4000@533,
R6300v1, RT-N66U@663, E1500@353, WRT54G{Lv1.1,Sv6}@250
|OpenWRT 19.7.3: RT-ACRH13, R6220, WNDR3700v4
Sponsor
ThaCrip
DD-WRT User


Joined: 05 May 2008
Posts: 299

PostPosted: Fri Feb 07, 2020 1:54    Post subject: Reply with quote
I see in the more recent builds it shows...

"9. CVE-2019-14899 VPN fix (r41784: applicability depends on VPN setup) and GUI toggle (r41812): ticket 6920, 6928, 6931, 6932"

I realize I am not using VPN, so I assume r41686 is still secure for me, but I figure it would be a good idea to use a more recent one for good measure on the chance VPN is used at some point in the future.

so what do you suggest for the recent builds on a Linksys WRT54GS v1.1? ; I mainly just need to make sure the router does not get bricked flashing and that I can change back to another build if something acts up as I know r41686 is okay in this regard since I had no issues changing from DD-WRT to FreshTomato and from FreshTomato back to DD-WRT through the interface and I think I had about 8 days of uptime on r41686 before I was messing with other stuff etc.

is r41813 stable enough for general AP use?

on a side note... I believe you said it was safe to overclock to 250Mhz on a stock WRT54GS v1.1? ; or is 240Mhz a bit safer? ; assuming I can, there is no chance this can brick the router, correct?

p.s. I got capacitors (Panasonic brand) on the way which ill be using to fix the WRT54GS v1.1 router I got.

_________________
Linksys WRT54GS v1.1 /w dd-wrt.v24_mini_generic (r43190 May 18th 2020) @ 240Mhz ; new Panasonic capacitors Feb 11th 2020 | ASUS WL-520gU /w dd-wrt.v24_mini_generic (r43192 May 19th 2020) | Linksys WRT54GS v6 /w DD-WRT v24-12548_NEWD_micro | Belkin F5D7230-4 v1444 /w dd-wrt.v24_micro_generic (r41392 May 19th 2020) @ 240Mhz
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2613
Location: Indy

PostPosted: Fri Feb 07, 2020 17:29    Post subject: Reply with quote
ThaCrip wrote:
I believe you said it was safe to overclock to 250Mhz on a stock WRT54GS v1.1? ; or is 240Mhz a bit safer? ; assuming I can, there is no chance this can brick the router, correct?
I've never run a WRT54 at less than 250 (note the 5354 is locked at 240). The original 4000-series SoC spec was at 250 MHz with heatsink, and the 5000-series run much cooler and don't need one regardless.

I just updated mine yesterday actually. Wink If you need IPv6, use nokaid-generic or voip_generic.

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 20.7.4|FT2020.6: EA6900v1.1@1GHz, F7D8302@532|DD 44758: DIR-810L, WNDR4500v2 & 4000@533,
R6300v1, RT-N66U@663, E1500@353, WRT54G{Lv1.1,Sv6}@250
|OpenWRT 19.7.3: RT-ACRH13, R6220, WNDR3700v4
ThaCrip
DD-WRT User


Joined: 05 May 2008
Posts: 299

PostPosted: Fri Feb 07, 2020 18:05    Post subject: Reply with quote
Well after about 6 days of uptime on FreshTomato 2020.1 the ASUS WL-520gU acted up and lost it's uptime so I am thinking it might be more of a issue with FreshTomato than the router itself(?), which is why I switched back to DD-WRT to give this a try. but for whatever reason the AIR light (the Wifi light) on the ASUS router will not come on at all, so I have no wireless.

I was trying to reset it etc (using https://wiki.dd-wrt.com/wiki/index.php/Asus_WL-520GU ) but nothing seems to work.

any suggestions?

p.s. I had this issue not all that long ago before I replaced the capacitors and out of no where it seemed to come back on. but currently it's off and it's like wireless does not exist on that router.

@jwh7 ; thanks for the info on the WRT54 series as after I replace the caps (which ill likely be doing sometime early next week) ill switch it to 250Mhz and see what happens.

EDIT: maybe it was a fluke but I flashed back to 14929 build with the .trx file on the WL-520gU and then waited a while and flashed to r41686 and, for whatever reason, the AIR led is back on and everything seems okay. but last time I had this issue, before replacing the capacitors, I never did this and it came back on, which seemed to be out of no where. so it's hard to say if what I did above had any real effect on things. maybe it's a weird glitch changing from FreshTomato back to DD-WRT (or vice versa) occasionally etc(?) because that's the only time I noticed the wireless AIR light completely staying off as it never done that once things were in decent running order on FreshTomato or DD-WRT (even after losing uptime on FreshTomato etc) as it seemed to only do that (at least on the two times it occurred so far) when changing firmware if I recall correctly. but hopefully DD-WRT stays stable so I won't have to upgrade the firmware anytime soon Wink

so now at this point ill just have to sit back and see how DD-WRT r41686 fairs over the next couple of weeks on my ASUS WL-520gU as I figure if it does not act up within a couple of weeks (maybe a month tops), chances are DD-WRT r41686 is stable where as FreshTomato 2020.1 is not.

p.s. but I guess maybe there is still a possibility the replacement capacitors I used on the ASUS WL-520gU, which were used, are faulty, just not as faulty as the ones that were originally in it? ; but I would imagine if DD-WRT is stable and FreshTomato is not, that would get one thinking it's more of a FreshTomato firmware issue and less likely it's a hardware issue. but if DD-WRT also acts up, maybe that opens the possibility the used capacitors I am using on the ASUS router might be a bit so-so, just not as bad as the original ones previously in it. either way, given I am replacing the capacitors on my Linksys WRT54GS v1.1 soon with name brand ones (i.e. Panasonic) then I can be confident those won't be faulty and then I can test FreshTomato and DD-WRT and see what plays out Wink

-------------------------------------------------

EDIT #2: is there any way for the following script to work with static IP's instead of just DHCP connections? ... https://wiki.dd-wrt.com/wiki/index.php/Ad_blocking ; because that seems to work for DHCP connected clients but does not work when I setup a manual IP address given the ping times etc as the one with a static IP will ping something blocked in that MVPS HOSTS file (i.e. the MVPS HOSTS file is not working) but on the DHCP connected devices, stuff listed in that HOSTS file is blocked (i.e. the MVPS HOSTS file is working).

but will that MVPS hosts file be automatically updated once in a while with that general script? ; or does it only do it upon reboot? ; because it would be nice if one could update it about once a week.

EDIT#3: well I noticed a moment ago that it appears even my computer with the static IP is filtered properly with the MVPS HOSTS file now. I would assume it's on a slight delay after boot up before it takes effect(?)

but assuming all of that is fixed, does anyone know if that script there on the site (the first one listed(which just works with MVPS HOSTS file), not the long one that seems to require 32MB of RAM) automatically updates here and there WITHOUT having to reboot the router?

EDIT #4 (Feb 9th 2020): well in relation to my "EDIT #2" I think I figured out how the 'cron' thing works, which does automatically update it, given this website... https://opensource.com/article/17/11/how-use-cron-linux ; at the "Other scheduling tricks" section I can change it to update once a week instead of updating once every day (as I figure updating once a day is too often as once a week is plenty) at 12pm like it does given the way the cron stuff is entered on that ad blocking website in my 'EDIT #2'. so basically...

instead of what's shown...

0 12 * * * root /tmp/.rc_startup

I can change it to something like...

0 12 * * Sat root /tmp/.rc_startup

so instead of updating every day at 12pm it would then only update once a week, on Saturday at 12pm. or to change to 1pm on Saturday, I can do this...

0 13 * * Sat root /tmp/.rc_startup

_________________
Linksys WRT54GS v1.1 /w dd-wrt.v24_mini_generic (r43190 May 18th 2020) @ 240Mhz ; new Panasonic capacitors Feb 11th 2020 | ASUS WL-520gU /w dd-wrt.v24_mini_generic (r43192 May 19th 2020) | Linksys WRT54GS v6 /w DD-WRT v24-12548_NEWD_micro | Belkin F5D7230-4 v1444 /w dd-wrt.v24_micro_generic (r41392 May 19th 2020) @ 240Mhz


Last edited by ThaCrip on Sun Feb 09, 2020 8:45; edited 7 times in total
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 1777

PostPosted: Fri Feb 07, 2020 20:03    Post subject: Reply with quote
You guys are troopers and I salute you. Carry on.
ThaCrip
DD-WRT User


Joined: 05 May 2008
Posts: 299

PostPosted: Tue Feb 11, 2020 3:22    Post subject: Reply with quote
@jwh7 (or anyone else)...

What voltage do you get from your 12v rated Linksys WRT54GS power supplies?

because mine, which is the official adapter for it, is rated at 12v 1000mA. using a multimeter it measures 16.98v (give or take a little). that seem a bit high to you?

I even have some random generic power supply (see "p.s." section below) that's rated @ 12v 1000mA and that measures 14.19v and this also seems to plug into the Linksys WRT54GS v1.1 router I have and it powers up (but that was about as far as I have went with it so far is a basic power on test). I have not really tested it for stability, which I might once I replace the caps as they should be here soon (should have been here today but got delayed), especially if the official adapter acts up.

one last thing... when plugging in the power to the WRT54GS router and it's on you can hear some noise coming from the router. I assume that's likely from bad caps? ; it's not loud or anything but audible as shortly after you unplug it, the noise is gone.

on a side note... DD-WRT r41686 (Dec 10th 2019) is still working okay so far on my ASUS WL-520gU as it's got 3 days and 8 hours of uptime and so far everything feels good. I am going to try to get at least a full 7 days maybe a bit longer out of it as FreshTomato 2020.1 made it to about 6 days of uptime before resetting. but based on my gut feeling... I suspect DD-WRT r41686 will stay stable and FreshTomato 2020.1 is a bit suspect and given I got a HOSTS file to work on DD-WRT (for some general ad-blocking), I am not as concerned with going back to FreshTomato now.

but I may still test out FreshTomato 2020.1 on the Linksys WRT54GS v1.1 once I replace the caps just to see if it still acts up as if it does not, within say a full 7 days, maybe the used caps in the ASUS are a bit suspect(?), but if not, it's probably a FreshTomato issue I would imagine. but personally I am starting to lean towards DD-WRT being more stable than FreshTomato on these older routers.

p.s. but I got a hold of that generic one at a auction bundled with some crap not all that long ago. but apparently, given what it shows on the side of the sticker, it's made for charging some 'RAZOR Power Core 90' electric scooter apparently and shows a May 21st 2018 date on the sticker.

EDIT (Feb 12th 2020): I installed the quality Panasonic capacitors (low-esr/105c etc) in the Linksys WRT54GS v1.1 on Feb 11th 2020. it currently has DD-WRT r41686 on it (so I might just stick with this and skip FreshTomato for now). but my ASUS router currently has 4 days 13 hours+ of uptime as I figure if I can get another week or so I would imagine the odds are good it's stable in general. then ill shut it down and switch to the Linksys WRT54GS v1.1 since it's the better router anyways (and ill use the ASUS router as a backup to the WRT54GS) and I might as well use it since it's got brand new quality caps in it.

but I noticed as far as overclocking options on the WRT54GS v1.1 it shows 192Mhz/200Mhz/216Mhz(which is default)/228Mhz/240Mhz/252Mhz/264Mhz/280Mhz/300Mhz ; but I simply am not going to try anything over 252Mhz as I don't want to risk a bricked router.

but just playing around with it a moment ago... 252Mhz does not seem stable (wireless dropped connection and router seems to reboot itself once every 5-10min in my brief testing) where as using 240Mhz it does seem stable as I am currently at 20 something minutes of router uptime. since I am still using the ASUS ill probably let the Linksys sit for a day or two and see if it holds it's uptime overclocked at 240Mhz.

I checked CPU info using "cat /proc/cpuinfo" (without the ") and it shows BogoMIPS = 239.20 ; and "dmesg|grep -i hz" (without the ") shows... CPU: BCM4712 rev 1 at 240Mhz.

but since we are on the topic of overclocking... is it safe to upgrade firmware when the router/DD-WRT is in a overclocked state? ; or is it much safer to put the CPU back to it's default speed (which is 216Mhz) before any DD-WRT firmware upgrades/downgrades?

ill probably edit this post if anything new comes up.

_________________
Linksys WRT54GS v1.1 /w dd-wrt.v24_mini_generic (r43190 May 18th 2020) @ 240Mhz ; new Panasonic capacitors Feb 11th 2020 | ASUS WL-520gU /w dd-wrt.v24_mini_generic (r43192 May 19th 2020) | Linksys WRT54GS v6 /w DD-WRT v24-12548_NEWD_micro | Belkin F5D7230-4 v1444 /w dd-wrt.v24_micro_generic (r41392 May 19th 2020) @ 240Mhz
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2613
Location: Indy

PostPosted: Wed Feb 12, 2020 17:24    Post subject: Reply with quote
ThaCrip wrote:
What voltage do you get from your 12v rated Linksys WRT54GS power supplies?

because mine, which is the official adapter for it, is rated at 12v 1000mA. using a multimeter it measures 16.98v (give or take a little). that seem a bit high to you?
Because it's an unregulated supply; 14-17v is common for a 12v unreg. As the load (current) increases, the voltage drops. Naturally, regulated supplies are more expensive to make. Wink Out of all the older Linksys routers I've had, only one (for the GSv6 I think) is regulated. Measure it when you plug it in; it will drop then slowly come up as boot completes.
ThaCrip wrote:
one last thing... when plugging in the power to the WRT54GS router and it's on you can hear some noise coming from the router. I assume that's likely from bad caps? ; it's not loud or anything but audible as shortly after you unplug it, the noise is gone.
Most likely it's inductor ringing; that's why they usually have epoxy (or hot glue) on the coils.
ThaCrip wrote:
but I may still test out FreshTomato 2020.1 on the Linksys WRT54GS v1.1 once I replace the caps
That would be difficult since there isn't a build for it (no k2.4). Smile

GSv1.1 defaults to 216? The specs I've seen still show 200 until the GSv2. Granted, the manuf sometimes changes things leading up to model rollover. Is the S/N prefix CGN2, or did you change the CFE? Did you add a heatsink? As I said, the BCM4712 was specs at ~250 with a heatsink. I ran my GSv1 at 264 actually, but 240 is a good default due to the pll tables. Last I knew, DD did not set clkfreq correctly for the v1 (perhaps fixed with v1.1) and the CFE did not failsafe, thus bricking until I fixed it via serial. There's an old tomatousb post I made about it...
Ah ha, ref'd here:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1060781#1060781

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 20.7.4|FT2020.6: EA6900v1.1@1GHz, F7D8302@532|DD 44758: DIR-810L, WNDR4500v2 & 4000@533,
R6300v1, RT-N66U@663, E1500@353, WRT54G{Lv1.1,Sv6}@250
|OpenWRT 19.7.3: RT-ACRH13, R6220, WNDR3700v4
ThaCrip
DD-WRT User


Joined: 05 May 2008
Posts: 299

PostPosted: Wed Feb 12, 2020 22:02    Post subject: Reply with quote
jwh7 wrote:
Because it's an unregulated supply; 14-17v is common for a 12v unreg. As the load (current) increases, the voltage drops. Naturally, regulated supplies are more expensive to make. Wink Out of all the older Linksys routers I've had, only one (for the GSv6 I think) is regulated. Measure it when you plug it in; it will drop then slowly come up as boot completes.


I see. thanks for the solid info.

jwh7 wrote:
Most likely it's inductor ringing; that's why they usually have epoxy (or hot glue) on the coils.


I noticed the hot glue there when replacing caps but I never knew exactly why until now.

so basically it's got nothing to do with the router dying, thankfully Wink

but I am not worried as it's faint to where I can't hear it unless I my my ear really close to the router.

p.s. but I noticed when removing the caps and installing new ones into the WRT54GS v1.1 router things went much smoother this time around when I added a tiny bit of solder to the end of the soldering tip as it seems to help transfer heat a bit better into things that way and you can really feel when the solder is soft as things slide in much easier with just a little pressure on the cap when installing or pulling a bit when removing and I just alternate a little between each capacitors prongs until it's out.

jwh7 wrote:
That would be difficult since there isn't a build for it (no k2.4). Smile


I assume that's probably why it's unstable? (come to think of it... it's a bit embarrassing as I am starting to think that may have been my problem the entire time Sad lol (still, replacing caps helps ensure it's good for many years to come and was a little learning experience etc) )

because for the most part it works but does have trouble keeping a solid uptime to where, at least on the ASUS router(but given what you said I am assuming WRT54GS will be basically the same), it was losing uptime once every day to several days.

jwh7 wrote:
GSv1.1 defaults to 216? The specs I've seen still show 200 until the GSv2. Granted, the manuf sometimes changes things leading up to model rollover. Is the S/N prefix CGN2, or did you change the CFE? Did you add a heatsink? As I said, the BCM4712 was specs at ~250 with a heatsink. I ran my GSv1 at 264 actually, but 240 is a good default due to the pll tables. Last I knew, DD did not set clkfreq correctly for the v1 (perhaps fixed with v1.1) and the CFE did not failsafe, thus bricking until I fixed it via serial. There's an old tomatousb post I made about it...
Ah ha, ref'd here:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1060781#1060781


Yeah, I think it was 200Mhz but they changed it to 216Mhz due to some wireless instability and even the official Linksys firmware done the same as the following post talks about it a bit... https://www.linksysinfo.org/index.php?threads/overclocking-toastman-on-wrt54gs-v2-1.54553/

I guess I must have mid-read you on the 252Mhz thing as I thought one could use passive cooling (i.e. stock cooling without a heatsink) up to 250Mhz range. but since you just mentioned that it appears what I am experiencing is normal with 240Mhz being THE limit on passive cooling, correct?

as far as the CFE, the only thing I did was this years ago now... https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=143775 ; but I just made a recent post at the end of that as I just noticed when backing up the CFE from the router hours ago that it's size is a tiny bit smaller than it originally was.

but speaking of that stuff... I assume without a proper failsafed CFE, if I try to overclock beyond a certain point it will lock and basically brick the router? ; like, with a properly setup CFE it will reset Mhz back to a safe setting should a overclock cause it to freeze up etc. because that's the impression I got from reading around a bit.

but given what I have found online I would imagine my CFE is not protected from bricks due to overclock given the following post at post #13... https://forum.archive.openwrt.org/viewtopic.php?id=22645

EDIT: I just noticed after I let the WRT54GS router sit there for a day(was a bit over 24 hours), just to see if the 240Mhz overclock was fairly stable, which it appears to be, I then went to 'Administration > Factory Defaults' tab and applied that and after a reboot I got to reconfigure everything as expected. but... I noticed the 240Mhz overclock REMAINS instead of shifting back to 216Mhz. then I decided to try holding reset button for 30+ seconds at which point it does reset the WRT54GS v1.1 back to 216Mhz.

_________________
Linksys WRT54GS v1.1 /w dd-wrt.v24_mini_generic (r43190 May 18th 2020) @ 240Mhz ; new Panasonic capacitors Feb 11th 2020 | ASUS WL-520gU /w dd-wrt.v24_mini_generic (r43192 May 19th 2020) | Linksys WRT54GS v6 /w DD-WRT v24-12548_NEWD_micro | Belkin F5D7230-4 v1444 /w dd-wrt.v24_micro_generic (r41392 May 19th 2020) @ 240Mhz
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2613
Location: Indy

PostPosted: Thu Feb 13, 2020 21:31    Post subject: Reply with quote
ThaCrip wrote:
things went much smoother this time around when I added a tiny bit of solder to the end of the soldering tip
You're welcome... Cool and wow that's a long sentence... Shocked
ThaCrip wrote:
Yeah, I think it was 200Mhz but they changed it to 216Mhz due to some wireless instability
Ya, I'm aware of that, but hadn't heard of it on the v1.1. Smile Toastman actually refers to the failsafe issue in that link, but I think it was fixed for the v1.1. (see below)
ThaCrip wrote:
I guess I must have misread you on the 252Mhz thing as I thought one could use passive cooling (i.e. stock cooling without a heatsink) up to 250Mhz range. but since you just mentioned that it appears what I am experiencing is normal with 240Mhz being THE limit on passive cooling, correct?
The heatsink thing I mentioned was that the old BCM47x2 chips were orig spec'd w/ one at 250, but 535x chips didn't. Wink The clock limit is dependent on the individual chip (and voltage, etc), plus other components esp on older hardware. And as Toastman noted, he's runs hundreds of various WRT54*'s at 250.
ThaCrip wrote:
I assume without a proper failsafe'd CFE, if I try to overclock beyond a certain point it will lock and basically brick the router? ; like, with a properly setup CFE it will reset Mhz back to a safe setting should a overclock cause it to freeze up etc. because that's the impression I got from reading around a bit.
Failsafe means (as also alluded by Toastman that a wrong value is either ignored or select the nearest match) that the CFE doesn't hang if the set clkfreq doesn't match a value in the appropriate pll table. In my case (GSv1.0), it's pll table had...
    { 240000000, 120000000, [...]
    { 252000000, 126000000, [...]
So by selected clkfreq=250,125 (that most newer WRT54's used), instead of failsafing to 240,120, it bricked, and hard reset (very annoyingly) didn't fix it since the clkfreq is part of CPU init, before it even looks for a reset button input. When a device is said to have a locked clock, it means the CFE only reads it's default clkfreq (or could be hard-coded).
ThaCrip wrote:
EDIT: I just noticed after I let the WRT54GS router sit there for a day(was a bit over 24 hours), just to see if the 240Mhz overclock was fairly stable, which it appears to be, I then went to 'Administration > Factory Defaults' tab and applied that and after a reboot I got to reconfigure everything as expected. but... I noticed the 240Mhz overclock REMAINS instead of shifting back to 216Mhz. then I decided to try holding reset button for 30+ seconds at which point it does reset
That's is entirely expected, a GUI reset doesn't clear the clkfreq nvram parameter (and 'overclocking' in DD), so will survive a reboot. A full reset clears all nvram and then must restore certain required defaults (incl clkfreq) from the CFE, in order to boot. You can search the strings in e.g. mtd0 to see them.
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 20.7.4|FT2020.6: EA6900v1.1@1GHz, F7D8302@532|DD 44758: DIR-810L, WNDR4500v2 & 4000@533,
R6300v1, RT-N66U@663, E1500@353, WRT54G{Lv1.1,Sv6}@250
|OpenWRT 19.7.3: RT-ACRH13, R6220, WNDR3700v4
ThaCrip
DD-WRT User


Joined: 05 May 2008
Posts: 299

PostPosted: Tue Feb 18, 2020 8:51    Post subject: Reply with quote
Well for the moment I decided to go back to FreshTomato 2020.1 on the Linksys WRT54GS v1.1 router (I overclocked it 240Mhz from telnet prompt since the FreshTomato interface does not seem to offer any overclocking ability) as I figure having a functioning WAN DHCP auto-renew should be safer as even if the router with FreshTomato firmware had a slight uptime issue once every some odd days, besides losing my traffic data (which I would rather avoid but it's probably a better trade off than potentially having to deal with WAN DHCP renewal issues with DD-WRT), it should be 'good enough' as I never had any obvious wired/wireless issues with general internet connection as far as I noticed.

plus, I can test to see if the new Panasonic capacitors I installed on Feb 11th 2020 fixed FreshTomato's instability issues on the WRT54GS v1.1. taking a guess, probably not, but ill likely find out within the next couple of weeks and maybe even a week as if it reaches 7+ full days, it's looking positive. NOTE: ill likely edit this post to report what happened whether it's fixed and is stable or if it resets the uptime randomly within the usual 1-6 days like it was previously doing before I replaced the caps.

for those wondering how I did the overclock on my WRT54GS v1.1 on FreshTomato 2020.1 you just telnet into the router (i.e. from command prompt 'telnet 192.168.1.1' (without the ') and press enter then enter your username/password to the router) and issue the following commands...

nvram set debug_clkfix=0
nvram set clkfreq=240
nvram commit
reboot

because it seems that 'nvram set debug_clkfix=0' is critical as doing the above without that command, after the router reboots, it's still showing it's default 216Mhz. but after issuing that clkfix command above then the other ones after it and rebooting, the 240Mhz sticks as FreshTomato's interface reports 240Mhz and when I telnet back into the router and issue "cat /proc/cpuinfo" (without the ") shows 'BogoMIPS = 238.38' which is basically 240Mhz.

p.s. even a user (PGalati) over on the linksysinfo forums said that, at least in his experience, the GL routers are stable with uptime with FreshTomato but he had issues with his GS.

EDIT (Feb 25th 2020): the router lost it's uptime on FreshTomato 2020.1 around the 7 days and 2 hours of uptime range. but given DD-WRT's potential WAN DHCP renewal issue, ill just deal with it the FreshTomato 2020.1 uptime reset occasionally. I might consider trying to mess with other things to see if I can get the uptime reset to go away.

EDIT (May 22nd 2020): for those with the WAN DHCP renew issue on DD-WRT where 'Status > WAN' "Remaining Lease Time" is reaching all zero's, use DD-WRT r43192 (from May 19th 2020) (i.e. https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2020/05-19-2020-r43192/ ). NOTE: r41686 (from Dec 10th 2019), which the general word is you don't want to use builds older than r41686, may still be okay but it has the all zero's 'Remaining Lease Time' issue but it might be just a cosmetic issue since I never tested it long enough to see if my internet would go out but there is a reasonable chance it might not and that the all zero's issue is purely cosmetic (i.e. the WAN DHCP renew is actually working, just not reporting to the GUI properly). so for those who want to make sure that issue is gone use r43192.

_________________
Linksys WRT54GS v1.1 /w dd-wrt.v24_mini_generic (r43190 May 18th 2020) @ 240Mhz ; new Panasonic capacitors Feb 11th 2020 | ASUS WL-520gU /w dd-wrt.v24_mini_generic (r43192 May 19th 2020) | Linksys WRT54GS v6 /w DD-WRT v24-12548_NEWD_micro | Belkin F5D7230-4 v1444 /w dd-wrt.v24_micro_generic (r41392 May 19th 2020) @ 240Mhz
ThaCrip
DD-WRT User


Joined: 05 May 2008
Posts: 299

PostPosted: Tue Sep 29, 2020 6:39    Post subject: Reply with quote
I just wanted to let others know that the following ad-blocking link (to MVPS hosts) does not seem to work... https://forum.dd-wrt.com/wiki/index.php/Ad_blocking ; I don't know the details but I suspect it's got something to do with the HTTPS connection where as DD-WRT requires HTTP(?). because I noticed even when trying to go to that site with HTTP instead of HTTPS, it seems to force HTTPS in a browser.

either way, that does not work where as the following link does... https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1198315#1198315 ; as you can see that script is not using a HTTPS connection but is HTTP instead. that one actually works as you can see shortly after booting the CPU usage shoots up for a while (roughly a couple of minutes) until it's done processing it. but I am not sure how that would fair on 16MB of RAM routers as mine (WRT54GS v1.1) is 32MB and only about 12MB of RAM or so is free. so it might not work if your router has 16MB of RAM.

p.s. I know it's working as pinging 'abcstats.com' comes back with 127.0.0.1 and ping times are "0.0xx ms" instead of 200-300ms or so when it pings the real site.

_________________
Linksys WRT54GS v1.1 /w dd-wrt.v24_mini_generic (r43190 May 18th 2020) @ 240Mhz ; new Panasonic capacitors Feb 11th 2020 | ASUS WL-520gU /w dd-wrt.v24_mini_generic (r43192 May 19th 2020) | Linksys WRT54GS v6 /w DD-WRT v24-12548_NEWD_micro | Belkin F5D7230-4 v1444 /w dd-wrt.v24_micro_generic (r41392 May 19th 2020) @ 240Mhz
Goto page Previous  1, 2, 3, 4 Display posts from previous:    Page 4 of 4
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