Tomato RAF Releases


The results I'm getting are confused, some routers are working fine, other have some issues with known bugs (miniupnpd, QoS, I think the first users didn't use these modules or did not noticed the malfunction yet..) and others like KGB-7 have serious problems as he describe.

RMerlin, we are working in team (shibby and me with sporadic help from roadkill due to lack of time .. as almost all of us) with same code, different model but same platform and very slight differences, all my code is in the git.

The begining for each new model and in this case for new platform is difficult, what's confuse me are the disparity of the feedback, so, I'll stop releasing public betas and if someone is interested to test the firmware please PM with the model you have and I'll answer with the link to download. At least I can follow who's using RAF ARM release because now I don't know what release do you use, the model you own and the problem you have.

I have both routers (RT-AC56U sent by Asus and RT-AC68U bought from my pocket because the donations don't allow me to buy one router ...), both units are working since two weeks now and I flashed from Ausus original firmware with Asus restoration utility, my configuration is PPPoE+IPv6 tunnel (one unit) and DHCP (other unit). I cleared nvram using the tomato gui menu to do so, that's all.... and it works.

I appreciate the feedback, but let's organize a little bit to see clear water in this disparity of opinions and behavior.

Thanks!

Edit: I'm not asking you for donations if you understood in my post, the beta version has been loaded by 185 users... and I got two donations ... ;) .. I do because it's my hobby and I learn also. So, few problems I read compared with the downloads ... so, I'll restrict and ask for feedback from now on.

The other people asking for EA6700, EA6900, R7000 ... If I have one router we can try, without it it's a big risk for you to try Tomato.
 
Last edited:
Well I understand the work and such you guys put in for tomato, so I appreciate it all, and have run tomato on multiple routers I have owned. I currently have a R7000, and want to run tomato on it as much as anyone. One of the main reason I like tomato, is it's QoS, and I understand that's something that is currently not possible. As it does need some time, and effort put in first.

Also I understand the donations are not active enough for you guy's to support certain router's currently. So some people just don't understand this, or don't want to understand it, which I find sad. At this point, just seeing the work you guy's are putting in with ARM makes me happy. As I know there is a good chance sometime in the future there will be support for router's like my R7000.

Also I find it smart on your part, not to try building firmwares for router's you don't have one to test on properly. As we all know early build's will have many problem's, that will require a unit to use to figure out. Plus no need in taking the chance on bricking more router's over not being able to test like needed. An as we all know the netgear routers aren't like the newer Asus routers, in which are pretty hard to totally brick.
 
First of all I would like to explain that adding another CPU arch for an existing project is in most cases harder than building from scratch as the guys who are using the beta already noticed we maintained the Tomato look and feel but it became much snappier, Hopefully we'll be able to release a stable version soon as this becomes more stable by fixing issues we come across on a daily basis.

Secondly this is all done as volunteers and none of us is a professional developer we also make mistakes so bare with us as we have more exciting plans for Tomato as this is my own favorite platform and I personally have invested a lot of time into it and I don't see myself quitting anytime soon.

Third those issues some of you are experiencing could be due to variations in the hardware as we are still unaware of exactly how many models exists for each router and we are limited in models that we can get our hands on but I'm confident we'll get to stable build eventually one bug at a time as both Victek and I are pushing towards it as we can.

If any of you have the developing skills required and is willing to contribute from their time please contact us there is much to be done in order to achieve our plans for Tomato.


Sent from my iPhone using Tapatalk
 
First of all, thanks to the team for bringing Tomato to these routers. Effort much appreciated (donated to Shibby in the past; shall be donating to Victek this time as a token of appreciation).

Ok now, I have got TomatoRAF on AC56U. Working well except that I cannot issue the following command anymore while setting up optware:

... nvram setfile2nvram /etc/fstab ...
It gives "... usage: nvram [get name] [set name=value] ..." error as if the command is incorrect!

What changed? Is there some other way to commit file to nvram now? Any other alternative to commit modified fstab?
 
command is not implemented yet, you can use winscp meanwhile, fstab is accessible.
 
Last edited:
finally got my usb to serial ttl, firt order of business after gettng into the CFE prompt is checking http_passwd and this is the encoded passwd "$1$X/Vc3hCN$vSbO4zSKp.CbKj167.RCA1", was able to login in gui and reset nvram.
 
@godraab I'm looking sources, in my poor opinion they fixed a temporary patch (not a solution) for one issue (CTF+PPP+IPv6) connection, I didn't see noticeable changes. I'm looking in another direction with better improvements over the source code we're handling and kernel 3.xx.x ..
 
Victek said:
@godraab I'm looking sources, in my poor opinion they fixed a temporary patch (not a solution) for one issue (CTF+PPP+IPv6) connection, I didn't see noticeable changes. I'm looking in another direction with better improvements over the source code we're handling and kernel 3.xx.x ..
Click to expand...
CTF+PPP+IPv6 still in ASUS latest beta, no fix at all. Maybe the source you are looking at is slightly newer than the binary.
 
kIssGlaY said:
CTF+PPP+IPv6 still in ASUS latest beta, no fix at all. Maybe the source you are looking at is slightly newer than the binary.
Click to expand...

That's why I wrote 'temporary patch (not a solution)' ... when the third variable is not gathered then it crash.. about time stamp of sources and binary.. don't know, but as I wrote and you confirm (I was waiting your experience on it ;) ), it looks not fixed yet ..
 
Last edited:
godraab said:
So if I disable IPv6, my connection will be more stable?
Now I have constant disconnects/freezes/reboots.
Click to expand...
Disable CTF or disable IPv6 tunnel, just FYI. Maybe this is not the cause of your freeze/disconnects.

BTW, Vik, just saw a new FW airing, gotta try that and then report back.

ASUS RT-AC68U Firmware version 3.0.0.4.374.5047
Security related issues:
1. Fixed remote command execution vulnerability
2. Fixed cross site scripting vulnerability

Others:
1. Added universal beamforming to enhance the wireless speed for non 802.11ac devices
2. Fixed IPTV related issues.
 
kIssGlaY said:
Disable CTF or disable IPv6 tunnel, just FYI. Maybe this is not the cause of your freeze/disconnects.

BTW, Vik, just saw a new FW airing, gotta try that and then report back.

ASUS RT-AC68U Firmware version 3.0.0.4.374.5047
Security related issues:
1. Fixed remote command execution vulnerability
2. Fixed cross site scripting vulnerability

Others:
1. Added universal beamforming to enhance the wireless speed for non 802.11ac devices
2. Fixed IPTV related issues.
Click to expand...

Nice, they are working hard to solve it, please test and feedback.
 
You must log in or register to reply here.

Back
Top