The random reboots are happening when my computer is on or off. My brother's computer is on or off (different times than mine). The only other computer will be turned off tonight. Pretty sure our mobile devices are all airplane moded or scheduled off at night, and the wireless is restricted to approved MAC IDs only.
Takes no more than a minute for the router to reboot. I haven't run a stopwatch because my apps don't alert the instant they lose connection. This has been happening for a few days. I changed nothing in the router config immediately before the random reboots started happening.
Before I did the 30/30/30, I printed all the config pages to PDF (showing I was on the same build) so after everything was reset to default, I could copy and paste the fields. Bittorrent has not been run for months. When Bittorrent was running, everything was fine, go fig.
4096 max ports should be OK for v1.1 GL's 16MB RAM?
Left UDP at default 120, and just modified TCP timeout to 120 from build 14896's default of 3600. No fix is ever that easy for me though, so I'm posting this for any other ideas, or chastisement if I missed something in the avalanche of readmes.
Approximate times UTC-8, some observed by me, some by brother, some from working back from the uptime:
2330- 30/30/30 complete
0500- reboot
0710- reboot
last uptime length marked as 13:58, then...
2109- reboot
2310- reboots
2355- I submit this post
0800- reboot
1033- I edit this post
1132- soft reboot completed after manually reprogramming upgrade to build 14929
1213- reboot
1500- reboot
Last edited by N6ATF on Tue Jan 23, 2018 23:00; edited 4 times in total
The RD reset all the indicated file dates, probably due to a database upgrade or something.
These 'random resets' are reboots? Or you're losing nvram settings? But first, read the Peacock announcement, which states:
1. Do not use the Router Database (esp bad now that the dates were reset)
2. 14896 is a bad build
Short version: put 14929 on it, reset, manually set up, then report back. Note that many (incl me) are using recent builds on old WRT's.
How old is this GLv1.1? Every WRT54G* older than my GSv6 had bad caps which I replaced. None had visible signs of failure. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Power supply brick and bad electrolytic caps in the router's power supply stage are the 1st thing I would look at. [...] Look for any obvious bulging, cracks in the top of the can, any dried liquid reside that might have leaked out. If you google bulging caps or leaking caps you should find many examples of what to look for.
I agree (well I'd try 14929 first), but as I stated, I have had bad caps in many old G and N routers*, and not one of them had any visible sign. I test them with an ESR meter. OTOH, I've replaced lots of caps in power supplies and motherboards, and they usually are bulging and/or leaking.
*As a result of this, I have a whole bag of 330uF 25F caps that I use for router voltage regulator cap replacements. I've sold some of them here (like $0.75 for one, $0.50 addl.); they're just thin enough to mail with a stamp (embedded in cardboard for protection). _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Is it possible either the old/new UPS (same model) are to blame? The old one was putting out the tone for "Overload - Occurs when connected equipment exceeds the listed capacity of the UPS." and its 12V battery was at 3.5 years, expected end of life. I popped it out after 10 hours of charging with nothing else connected, & despite being hot to the touch, multimeter read just a few volts.
The new UPS (7/2017 battery) went in service 1/6/2018 & I haven't been here/awake to hear the power outage alarm go off (I know I made sure it was turned on), and no batteryless clocks have been flashing. The reboots didn't start until well after the UPS replacement.
Is there anything I can do with my Craftsman 034-82141 multimeter once I crack open the router, including test the power supply?
No soldering for me regardless of whether the caps are provably busted or not. If the multimeter can prove the power supply is busted, I'll buy https://www.amazon.com/dp/B00BWAP9WG but if this is an unprovable hardware issue, I'm just going to buy a new one*, reflash it with 14929 & restore my 14929 config file.
And be careful using older builds, esp. if used as your primary router. There have been numerous vulnerabilities found and fixed over the years. I strongly recommend getting a more recent build from BS (Brainslayer).
I've also had them listed on here for $40. My last tm-ac1900 converted to an rt-ac68p, I sold on Craigslist for $35. _________________ I am far from a guru, I'm barely a novice.
You never mentioned what other services you have enabled; that might also use up nvram or ports. I have a GLv1.1 and GSv6 setup as AP's at my in-laws, been running fine for years (since replacing the former's caps).
Also, at least use your multimeter to check the power supply voltage. My GL's were unregulated, so open-circuit they'd be 14-16v (my GSv6 supply is regulated; max 12.4v). If you open the case, you can measure voltage while powering up the router to see if it has any issues. I've never had a power supply fail, but I know others here have.
I also doubt the UPS is an issue, but easy enough to bypass it to test, esp if you're rebooting anyway.
Malachi wrote:
I've also had them listed on here for $40. My last tm-ac1900 converted to an rt-ac68p, I sold on Craigslist for $35.
While we're comparing...I got a Netgear R6300 at Goodwill for $6 (or 7?) a couple months ago, with original power supply. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Currently running off a Linksys EZXS55W hub that I had in reserve, between my 'puter & the SB6141 modem, which said
Code:
DHCP Server Enabled The SURFboard cable modem can be used as a gateway to the Internet by a maximum of 32 users on a Local Area Network (LAN). When the Cable Modem is disconnected from the Internet, users on the LAN can be dynamically assigned IP Addresses by the Cable Modem DHCP Server. These addresses are assigned from an address pool which begins with 192.168.100.11 and ends with 192.168.100.42. Statically assigned IP addresses for other devices on the LAN should be chosen from outside of this range
I'm now assigned the same IP for this computer that the router was assigned, as I had cloned MAC ID. I'd hoped the DHCP would assign me a usable IP when I had the coax out, but it just gave me 192.168.100.10 & once the coax was back in, the internet wasn't accessible, so I rebooted it to get back to the previous WAN IP & this config.
The WRT54GL is not screwed together. There are a couple of holes under the front feet, and snap-together bits under the back feet. I'm not sure how to pull it apart or disengage the locking mechanisms. The power supply is the OEM AD12V/1A-SW switching supply, 100-240V AC 50/60Hz 0.5A & 12V DC 1A. The multimeter is only reading volts, not amps: 11.9 with some fluctuations to 11.91 & back down.
Debrick successful even after Linksys stock firmware wouldn't upload the previous time. Order requested to be cancelled. Cancellation Failed.
DD-WRT v3.0-r34578 std (01/19/18) is on now.
Manually programmed, hit apply settings immediately, got stuck in an endless loop where the power, WLAN, and all ethernet port indicator lights would alternately flash, go solid. Seemed like I bricked it again so I hard reset and it came back without a TFTP reflash. Manually reprogrammed again, same loop started again after applying settings. I unplugged my ethernet port & the orange light came on shortly. Plugged back in, applied settings again, endless loop, unplugged, orange light came back on.
The beta added loads of settings (yet the help column overlaps in places & still doesn't explain each of the settings) but it can't even apply them without this bug? WTF?
Left my router page up overnight and the last auto-refreshed entry was 05:04:28 up 3:35. 3 (personal) emails were received at 0546, 0708, 0842.
Refreshed the page at about 9AM and it went back into reboot loop. Somehow I managed to reset button it out of the loop after a few short presses. The orange light is back on and I have WAN connection without having to unplug/replug the eth cable.
Seems to me this is a clear case of failing hardware. It's perhaps bad caps, bad a/c adapter, etc. I don't see the point of just repeating the same tests. I'd either fix the caps/adapter, replace the hardware completely w/ a new WRT54GL, or (my preference) embrace something new and more modern.
Which is the best DD-WRT router on walmart.com actually sold by Walmart & not a third-party seller? I have a 10% off coupon up to $200.
Odd thought, since your username looks a lot like a HAM callsign, and since it looks like you are still having trouble with your new router per that thread you just linked.
If you are a HAM, do the issues at all coincide with keying up a radio in the vicinity of the router? These are very unshielded devices. Keying up a high powered radio in the vicinity of the router might cause random errors on the data buses within the router. Really the only shielding on these devices is the can soldered over the radio chipset. The CPU, RAM, Ethernet switch chips are all out in the open.
Yes that's my callsign. No, haven't keyed up for a few weeks. The closest radio is the WRT54GL's own radio, and the next nearest is the ATA-connected 5.8ghz Uniden base across the room, getting no use because no internet. I don't use a cellphone but the nearest one isn't visible within the same radius as the Uniden base (including on other side of wall).
I've just had my cable modem learn the new GL's MAC ID, and cloned it to the old GL, so I can hot-swap & power up the other when either one starts cycling after what I thought fixed it, didn't.
Marking
Time: 13:44:27 up 21 min
Time: 16:06:33 up 2:43
Time: 16:43:45 up 3:20
Time: 18:45:57 up 5:22
Time: 23:49:01 up 10:26
Time: 13:17:06 up 23:54
Time: 15:58:12 up 1 day, 2:35
