2 edits | tomato crashes with white screen on WHR-HP-G54 every once in a while (I would say about once every 3 weeks or less) when I try to access the tomato UI, after entering the router's IP, I just see a blank screen. No prompt for username and password, no nothing. Just a white screen.
The only way I can fix it is by unplugging the power from my router and plugging it back in to reboot.
I've tried re-flashing the firmware, upgrading, downgrading, everything. I'm currently running Tomato 1.27
Has anyone experience this before? And how can I figure out what's wrong? |
|
| Yes, that router has an unusually high failure rate. I've had several flake out in similar ways. |
|
 PeeWeePremium
join:2001-10-21
Madera, CA
1 edit | said by 38632383:Yes, that router has an unusually high failure rate. I've had several flake out in similar ways. I believe that to be a false statement. I have installed and recommended this router many times with only one failure, and that was caused by the being plugged into the wrong transformer.
And for the OP...
Check that it is not getting overheated. It should barely feel warm to the touch.
edit. The next thing to try is setting a IP address for the computer at an address outside of the DHCP range. A power glitch can cause a problem with the IP address assignment (now that is common with this router, and is simply fixed in this manner).
--
My grandkids ARE cuter than yours!  |
|
1 edit | reply to 38632383
said by PeeWee:And for the OP... Check that it is not getting overheated. It should barely feel warm to the touch. edit. The next thing to try is setting a IP address for the computer at an address outside of the DHCP range. A power glitch can cause a problem with the IP address assignment (now that is common with this router, and is simply fixed in this manner). Are you saying set a static IP for computers? If so, all the computers in my network have a static IPset through Static DHCP in Tomato and they are all outside the set DHCP range (100-149) |
|
v4npro
join:2008-10-24
Pasadena, MD | reply to atomicrabbit
Never had that problem, I'm also using Tomato 1.28 Beta version. Always best to do a clean flash, reset router then flash. |
|
PeeWeePremium
join:2001-10-21
Madera, CA | reply to atomicrabbit
I would say that you should follow v4npro's advice and if the problem continues you may need to post here a list of all changes from the default you have made in the router's settings. This is one of the best 54g routers out there (with Tomato firmware) and this problem should be easily fixed.
--
My grandkids ARE cuter than yours! |
|
|
|
| i'll definitely try that today and come back here if the problem persists |
|
3 edits | reply to PeeWee
said by PeeWee:I would say that you should follow v4npro's advice and if the problem continues you may need to post here a list of all changes from the default you have made in the router's settings. Ok just for the sake of thoroughness, I reset the router, re-flashed and entered all my settings manually from scratch. Here's what I did, in the order you see it as:
NOTE: If you guys see anything that raises any flags in your head(s), please do tell.
Basic > Network
Changed DNS to OpenDNS IPs
Basic > Static DHCP
Set all computers Static IPs
Basic > Wireless Filter
Set all wifi devices, permit only
Basic > DDNS
Added my DynDNS-Static account info to the Dynamic DNS 1 slot
Basic > Identification
Changed Router name
Port Forwarding > Basic
Added all my required port forwards
QoS > Basic Settings
Enabled QoS
Set In/Outbound limits
QoS > Classication
Added all my required classifications
Administration > Admin Access
Allowed Remote Access, HTTP on port 8080
Changed router's admin password
Administration > CIFS Client
Set new CIFC Client in CIFS1 slot
Administration > Bandwidth Monitoring
Set 'Save History Location' to CIFS 1
Set 'Save Frequency' to Every 24 Hours
Set 'First Day of the Month' to 10
Administration > Debugging
Checked 'Avoid displaying LAN to router connections' |
|
1 edit | ok it's been about 2 weeks since I manually re-inputted all my settings from scratch and it hasn't crashed yet. I think the problem was a couple L7 and IPP2P rules I had set in QoS before the reset. I didn't add those rules after the reset, and I think those were the problem settings.
I read that L7 and IPP2P rules slows QoS and the router down. |
|
PeeWeePremium
join:2001-10-21
Madera, CA | said by atomicrabbit:ok it's been about 2 weeks since I manually re-inputted all my settings from scratch and it hasn't crashed yet. I think the problem was a couple L7 and IPP2P rules I had set in QoS before the reset. I didn't add those rules after the reset, and I think those were the problem settings. I read that L7 and IPP2P rules slows QoS and the router down. Did you dump NVRAM at the same time? That may be why it works better now.
--
My grandkids ARE cuter than yours! |
|
