Re: Strange behavior behind Tomato router
Tomato 1.23 or 1.25 does not handle VoIP well, after a reboot of the router. I went through a series of issues with VoIP losing registration, during the period of problems that VoIPo had. However, while watching this series of events, I also uncovered a problem with my Linksys router rebooting about every 3 to 4 days on it's own. When that happened, the ATA would lose connection and not register and after 10 to 20 minutes, vPanel would show no devices registered and the ATA status lights would go dim (except for network and power of course). The only way to resolve was to remove power to ATA for about 30 to 45 seconds and re-power. BTW, I use Static DHCP. While this was not a good work-around (especially while at work and wife/kids complaining when phone did not work), I configured the ATA into my DMZ and I am able to login to the ATA from anywhere I have a connection (which is almost anywhere/anytime as I have connectivity at work and broadband on my laptop). I would login as admin and change the IP address of the ATA, causing it to reboot after the save. This work-around is acceptable to me. On the Linksys front, only thing I could find was that using the router as an AP was the culprit. I turned off AP mode and I have not seen a reboot in weeks (except when I upgraded to Tomato 1.25). I also went on eBay and bought a WRT54GS model, which has more ram. I have been running this on Tomato 1.25 as well, with no problems. I went to Frys and bought a cheap Trendnet WIreless G AP and to use instead. All if fine now.
Tomato's ease of use, graphing, and QoS settings are excellent. I will not being going to anything else. Also, after I installed Tomato, the amount of BW or packets the router could process went up about 30%. You can not beat the combination of the Linksys router ($50 on ebay or less) with Tomato (free), and a small UPS ($40) for the DSL/Cable modem and router.
-bird
Reply With Quote
Originally Posted by 1bird2
Bookmarks