Discussion in 'Tomato Firmware' started by Toastman, May 4, 2011.
So d/l version dated 6/11?
6/12 is latest
I only see 6/11.....
6/11 is 6/12 inside, Built on Sun, 12 Jun 2011 03:00:15 +0700
Didn't the folder/file date change? Maybe I should have deleted the old one first. It's set to write over the destination without asking. Bother.
Mmmm different time zone - maybe ?
I'm good. Build date in "About" section is 6/12. Good catch kt....
Does anyone else have this problem where the bandwidth graph (download part) dips to 0 at a regular interval? See http://imgur.com/xLHJv&BQxBKl
I watched my connection during this and I didnt get any disconnects or drop in speed
Toast, one suggestion... Enable dhcp by default for those of us that don't use 192.168.1.1 as a gateway... I thought I bricked my router, and had to hook up the laptop in the closet by the router to troubleshoot... Luckily it was just dhcp was off
Will report back after a week of use or so...
Toastman screen "about" 7474 is more nicer than 7475.
I agree, I like it better than the original too. One line seems to have disappeared in the "about.asp" page code, probably due to an update from another branch. I'll put it back. The "enlightened" theme in particular.
Do we need to watch for new compile date or new .x version?
Do you know where the "README" file in the RT-N16 folder went? I went to download it from 4shared, but when the download link appeared and I clicked it, I got a file not found and now it's disappeared from the file list.
Also is 1.28.7475.4 the latest version?
Yes, I had started with 7476 but I found a possible bug in nocatspash, so I'm holding it back, that's why the readme was missing.
I could'nt agree more. I'm wondering why you had to disable it in the latest two or three (?) builds when it has always been the default. It caused me a PITA for an hour trying to figure it out until I was able to access my routers without my PC's and laptops getting a 169.x.x.x IP's. I found it the hard way after I flashed my E3000. Tried to save a setting and the router froze (only experienced this freezing after saving a setting in Builds 7475.3 and 7475.4) And my only recourse was to power cycle the router...
Y'know, this is a problem. I make these builds for myself and for the use mostly of those with rather more users than most, a lot of AP's and need the utmost in stability, which has generally been going downhill of late. This DHCP default change was done at the suggestion of several such users, and it makes sense. It is a fairly common occurrence to have AP's or secondary routers lose their NVRAM settings, reboot using the defaults, and then pop back up as 192.168.1.1 (making another problem, now there are 2 routers using the same IP address) issuing the wrong IP's to everyone, which can take several hours to sort itself out - causing mayhem to a residential wifi system. So what do I do ? OK, I can probably reinstate it. But ultimately, if someone flashes a new version and retains their old NVRAM settings, they will still have DHCP. And if they are flashing and using the defaults, (No DHCP) then surely when they are setting up by hand afterwards they **should** notice the DHCP is turned off? Would a reminder in bold letters help?
I might add that although for simplicity it has become normal practice for SOHO routers to have IP's issued by DHCP, no sane network admin would ever consider doing that.
Aha! Now I see the reasoning behind!
I believe it's fair enough to have a warning somewhere then? :redface:
Thank you Toast.
Great. Trying to keep everyone happy, isn't so easy. There's already one mention in the "About" page. I will also add one on the "basic" setup page.
Actually, I'm one of those who's very easy to please Considering how much time you're putting into your builds, it's only fair that your main cause should be taken into consideration. Thank you, Toast for always keeping an open mind
As always, much appreciated. Cheers!
Most people clear nvram when flashing, as that is still the recommended way to flash, unless it isn't needed anymore? Also, some people don't use the 192.168.1 network, which means when they flash the router, they have to change a computer in their network to have a static ip in that network or it won't be able to access the router. I would just suggest a warning in the first post.
Thanks again for all the hard work!
in Execute System Commands
nvram export --set >config.txt
button execute and then error
/tmp/.wxa1zOfy: line 5: can't create config.txt: Read-only file system
Create a file somewhere that your router can write to. But it's much, much easier to cut and paste it from the command box.
I am getting almost the same error "/tmp/.wxKHRPxz: line 5: can't create config.txt: Read-only file system
" after execution of nvram export --set >config.txt. I have seen several people say this should be easy but I don't know linux at all. I have no idea where /tmp/ is or I would go there and check the ownership and permissions.
Lost in linux space,
PS - I figured it out. My son said I need to study a beginners manual on the syntax of tomato firmware linux. That's why I am getting lost. Also he taught me you can't put the config.txt in that position. Have to put it in the /home/root like nvram export --set >/home/root/config.txt. That works and doesn't throw the error. I have some studying to do and I'll be back to impress my friends - I hope.
tomato firmware linux student,
I just found what I was hunting for. If you don't know linux at all, go here:
Just the basics for me cause it looks like you could easily turn this learning process into a very long study indeed.