Discussion in 'Tomato Firmware' started by kille72, Mar 24, 2017.
thanks for your advice to clear the cache. It worked!
transmission doesnt work properly on 2017.3 on my ac68
none of the torrents can connect to the tracker
cleared the nvram too, no dice
it works fine on 2017.2
No problems here on 2017.3...
Any thoughts on supporting the new ASUS RT-AC86U?
No plans... We will try to get the AC68U C1/E1 to work first, waiting for source code from Shibby.
it cant resolve hosts for some reason, it still connect to peers thru dht
if i try and ping a domain name it says bad address
it works fine if i revert to 2017.2
How long do you think we will wait?
I have had both an E3000 and N66 crap out due to heat issues. In both cases I did not monitor the temperature routinely which led to premature death. In both cases 2-3 years was the lifecycle before death.
A replacement N66 and my curent R7000 sit on a laptop cooler and maintain CPU temperatures at or below 50C. The N66 is now 3 years old and running fine (at the parents house) and the R7000 is now approaching 1.5 years with no issues.
YMMV but 80C (175F) is probably cooking the components and when there is even a slight cooling (at night) then something is separating or flexing leading to issues.
You may be able to extend the life by keeping it cool, but probably the unit is done for.
The other thing you might first check is the power connector (wall-wart). If this is failing and under/over volting that could lead to problems too. But I would cool your unit too. A laptop cooler is $10 and uses <1 watt of power. Cheap insurance.[/QUOTE]Thanks for that insight. I thought of the power the other night. Sourcing a PSU to test, but I think your right about it being cooked.
Sent from my Pixel XL using Tapatalk
You can try to fix a programmer who can high-level trix at kernel level, then it will be quick....
We will make some changes:
1. Update Nginx from Legacy version 1.10.3 to Mainline version 1.13.8
2. Fixes in MultiWAN-Watchdog (in some cases, the network connection is still considered by Tomato as active)
3. MultiWAN connection status in the GUI, whether it works whether it is fail-over (standby) or fail-over (active):
wan2: Failover (standby)
If everything goes well, I will compile test versions in a few days
I don't think anybody recently left Tomato running for a long time recently. I've been quiet not doing anything since December 5th, and haven't rebooted my router ever since.
Good news! I left my AC56U running for 1 year with the Tomato v130 once
Latest version, nvram reset and no configuration. I connect to the default open Said Tomato 24 and below is the performance. Seriously, what's wrong with this??
Not sure if anyone else has ask about this or if you are even aware but there has been a long time (before your fork) know issue with using the 'captive portal' when you are using VPN. In my case when using the VPN client with routing policies the captive portal does not work when using on my guest WiFi LAN1(BR1). I was hoping that maybe you could review the code and see if you could fix it. Thanks for any help you can provide.
Check the results on version 2017.2 with the older WLAN driver. Erase NVRAM after the upgrade.
I do not think it's possible to do that. Can anyone correct me if it's wrong?
I just tried it and there is no difference, still 10-15mbps downstream and 80-90mbps upstream with factory defaults.
Open new thread and ask others with the same router what they have for speeds with Tomato. I am sorry but I do not really know how to help you...
i dont know if i ask you this but is it possible to add "Yearly" to "WAN Bandwidth" or make the Monthly List LONGER 2-xx Years.
Thanks for your hard work.