Thanks for the detailed explanation Luke... makes sense now.

Hi NeoRouter,

Is there any way to enable the server to be deployed on existing "Tomato" installations in the same way that you provide for "DD-WRT" installations? "Tomato" contains "ipkg" (but no associated "conf" file, I think).

I am in no way a Linux expert but I can run simple commands via SSH and follow simple instructions.

I have an old WRT54G (v1.1) router and I am keen to be able to deploy new "Tomato" releases when they become available so it would be great if I could deploy NeoRouter as an optional package. Thanks.

Cheers, Twincam.

Hi Twincam,

It's not possible to deploy NeoRouter packages to an official release of Tomato, because Tomato does not work like OpenWrt which provides a basic core and allows users to add modules, while Tomato needs recompile an application if you use some APIs which are not included in the release.

We will keep updating NeoRouter for the latest stable Tomato.

thanks,
KevinZ - NeoRouter team

I'm attempting to set up NeoRouter on a Linksys WRT54GL.
I have successfully flashed with your Tomato, and when I telnet in to the router I do not have a /usr/local directory, nor can I mkdir that directory--I get the error that the file system is read-only. Can you help?
Or does your team recommend the OpenWRT Kamikaze setup instead?
TIA, Larry

hi drfox,

Tomato and Openwrt have different FS management by design. On Tomato, /jffs is writable only; while on kamikaze, you can use it just like a Linux.

NR in-a-box for Tomato store files in /jffs, and other folders are read-only.

Since you have a WRT54gl, I may recommend you use Kamikaze instead as it may give you more space (FS) than Tomato and make your NRserver support more clients.

Thanks,
KevinZ - NeoRouter team