Discussion in 'Tomato Firmware' started by Toastman, Dec 18, 2011.
Shibby doing tests ...
If I recall correctly from what I have been reading openlinksys.info forums two weeks ago, Shibby just married, so I don't think he has any time for Tomato at the moment. It's perfectly understandable if his life priorities won't allow him to look into Tomato any further.
Hello. How do I enable DHCP?
You misunderstood, someone just such an example gave that once in another forum as the administrator was absent it turned out so,
I think hehe so bed, so young wife, he probably will not bed the pain hehe.
Let's respect Shibbie's work, though his incest is annoying ;-)
Is the wireless client mode ever going to get fixed?
Don't hold your breath. Tomato's Client Mode has been broken some time as some say here. If it hasn't been fixed by now, it probably will not be anytime soon. Maybe with enough demand, someone could take a look and try to fix but overall it seems a very low priority. It may take some compensation, maybe $$, to make it worthwhile to fix. If you want a third party firmware with a working Client Mode, DD-WRT is the only viable option at this time.
What is the preferred way to communicate patches for Tomato dev? I have seen people pasting Github links but the repositories don't seem to exist any more. I'm spoiled now by the fork, commit, pull-request workflow by this point : )
You may attach patches here on this thread. Any contribution is welcome.
There's not really a "Tomato developer". The two main branches nowadays are "Toastman" and "Shibby".
Toastman uses a more stable codebase.
Shibby is the bleeding edge, where things may break and requires a fix.
Ok, and where do I get the latest source? I am not seeing it in the 4shared folder.
It's a repository: http://repo.or.cz/tomato.git
The main tree is the ancient Tomato 1.28, so after cloning the repository, you need to checkout the branch you want. Usually Toastman or Shibby branches.
http://repo.or.cz/tomato.git/heads may give you a consolidated views of all the branches, depending on which architecture you will work with.
For ARM architecture, Shibby maintains a separate repository, at https://bitbucket.org/pl_shibby/tomato-arm/commits/all
Bitbucket is where I maintain my own fork as well: https://bitbucket.org/AndreDVJ/advancedtomato-arm
So in the end, there are forks all over the place. Tomato sources can be very confusing to work with, and compiling the source with a Linux distro other than Debian can be a nightmare, so please let us know if you need additional information.
Are you planning any further releases?
We could use a more current stable Tomato platform
Latest release is only few months old and there have been no show-stopper bugs (AFAIK). It's as current as it gets (imho)...
Is that something to be corrected?