Tofu 7.0 is available for the WRT54G

Discussion in 'HyperWRT Firmware' started by nanana1, Oct 30, 2005.

  1. nanana1

    nanana1 Network Guru Member

    From Tofu himself :

    Changes in tofu 7

    - Linksys 4.20.9 code base. [The only difference between 4.20.8 and 4.20.9 are changes in the simplified Chinese language files (not included here).]
    - Added Client, WET, and WDS modes from Thibor's project.
    - Added an experimental fix for the "Capture(xxx)" problem with Opera (only?) browser. To enable, run "nvram set capfix=1".
    - Fixed the 4GB bug in transfer statistics. A program now watches every 2 minutes to avoid the rollover problem.
    - Active Client List renamed as Device List. It now shows all the ARP entries that it finds. Interface names and RSSI information are now shown if available. DHCP lease can now be deleted, and static lease can now be transferred automatically to the Static DHCP page. AJAX support added.
    - Static DHCP page rewritten into a more cleaner, simplier table design.
    - Dnsmasq upgraded to 2.23. It now also functions as the DHCP server, replacing udhcpd. It's bigger that udhcpd + the old Dnsmasq, but hopefully this will fix the problems some are having with udhcpd. udhcpc still functions as the client. Dnsmasq is also now used for DNS inside the router.
    - Some light optimization in the httpd's asp parser.
    - Fixed a small httpd leak I fixed before but broke again.

    Download: (Firmware), (Source Code).

    Client and WET modes have been tested lightly, but WDS modes have not since I don't have another WDS router. Please help each other out with the setups as I have no experience with these.

    Enjoy! :)
  2. ravn

    ravn Network Guru Member

    Going to flash at once :)
  3. larciel

    larciel Network Guru Member

  4. Toxic

    Toxic Administrator Staff Member

    Added to downloads thanks.
  5. pharma

    pharma Network Guru Member


    Just loaded this, but wasn't certain I wanted to remove Tofu 6.2 which was running so well on my WRT54G v1.0.

    No problems with Tofu 7.0 and is running extremely well!! :thumb: Excellent firmware!

    Many thanks,
  6. 4Access

    4Access Network Guru Member


    I'm a big supporter of BrainSlayer + his DD-WRT firmware... Yesterday I installed the latest v23beta2 (10/27/05 build) onto a WRT54G v4 and spent over an hour trying to get Client Bridge mode with WPA to work but never succedded.

    Today I downloaded Tofu v7.0 and in less than 10 minutes had WET with WPA working which is equivelent to DD-WRT's Client Bridge Mode. Based on this experience I have to tip my hat to you and Thibor (noticed change log said you grabbed the WET code from him) for a job well done. :clap:

    A suggestion though: Have you considered hiding the whole "Internet Setup" section on the Setup > Basic Setup page when WET mode is enabled? It's confusing to have both WAN & LAN IP configuration options when in bridge mode. (For those curious I simply set the WAN option to Disabled which works fine and allows you to use the LAN address for configuring the router.)

    Keep up the great work! :thumb:
  7. bashy

    bashy Network Guru Member

    By adding WET client, would this mean that Using this Firmware One could Purchase or Use a second WRT54G as a bridge instead of buying the "over priced" dedicated linksys bridges? If so how easy would the setup be! Very nice....
  8. 4Access

    4Access Network Guru Member

    Yup! Quite honestly I can't think of a single reason to buy the $180 WET54GS5 anymore. There's nothing it can do that a WRT54G/GS can't do when running custom firmware! :D

    I'm assuming that was supposed to be a question? Setup is just as easy as using the dedicated bridges. It should only take about 10 min (maybe less) to get a working bridge configuration! (And that includes the time it takes to flash the firmware, hold reset button for 30 sec & then configure!) :thumbup:
  9. Maugus

    Maugus Network Guru Member

    Great Firmware. Just L7filter is missing ...
  10. vais

    vais Network Guru Member

    Flashed tofu 7 this morning.

    Works fine. :clap:

    wl scan and wl scanresults now work excellent.

    there was some strange hiccup with dhcp, apparently dhcp was granted but somehow this hasn't been shown in the device list. However it worked later excellent.
  11. vais

    vais Network Guru Member

    Reporting tofu 7.0 probable bugs:


    when rebooting the computer, even though it is set to lease IP address from the router, the information is not being recorded in the Device List table appropriately. However, it acquires an IP address.

    Only after I release and renew the lease using ipconfig /release ipconfig /renew it finally appears in the Device Lsit.

    Looks like it doesn't work for the first time ? Strange.

    Before ipconfig /renew but after computer restart:

    After ipconfig /renew

    host computer suddenly in the list !


    When going to device list from static dhcp page, and trying to add lease, it alerts "Please open the device list from the static dhcp page"; even though I do open it from there.


    In the previous tofu release I was always given IPs started from 100, so it was 100, 101, 102 etc.

    In this version, i got outright .131 IP. This is kind of weird.

    Thanks a lot for the excellent work. :cheer: :cheer:
  12. bashy

    bashy Network Guru Member

    Maybe we can setup a How To on the using the WRT54G In Bridge Mode. So far I've failed to get to work...

    Using a v2 and v4.

    V2 unit is my main router, Wireless mode set to : Access point, wireless is running unsureced, Using Tagu 7.0. Firewall Disabled

    V4 is running in WET mode. Wireless Mode seto to : WET, Firewall Disabled, Internet Connection Type set to : Disabled. DHCP is Disabled...

    Anyone know what it I'm missing..
  13. 4Access

    4Access Network Guru Member

    Here's an example config that's almost exactly how mine is stetup.

    It might be worth resetting both routers to defaults with a 30 sec hold of reset button before configuring.

    WRT54G #1
    WAN Info: Defined by ISP
    LAN IP:
    DHCP Server: Enabled
    Wireless Mode: AP
    Channel: 11
    SSID: ExampleSSID
    SSID Broadcast: Enabled (Haven't tried disabling it)
    Security: WPA TKIP (Haven't tested AES)
    WPA Key: ExampleWPAKey
    MAC Filtering: Disabled

    WRT54G #2
    WAN Info: Disabled
    LAN IP:
    DHCP Server: Disabled
    Wireless Mode: WET
    Channel: 11
    SSID: ExampleSSID
    SSID Broadcast: Shouldn't matter
    Security: WPA TKIP
    WPA Key: ExampleWPAKey
    MAC Filtering: Disabled

    The most important things are making sure you've configured the wireless channel, SSID, & security settings the same on both routers. I'd also double check to make sure the Advanced Wireless settings are configured the same on both routers. Also you obviously have to make sure that one router isn't set to G only and the other to B only.

    And to state more obvious facts, you must connect your computers to the LAN ports on Router #2, the WAN port can't be used. (Although it's worth noting that there are ways to make the WAN port function as a 5th LAN port.)

    Good luck, let us know how it goes!
  14. bashy

    bashy Network Guru Member

  15. tofu

    tofu Network Guru Member


    1: The lease time disappears when the lease table is cleared like after a router reboot or upgrade. A computer with an ip address already will stay up as is and will not contact dhcp until it's time is up, so they don't appear in the lease table until that time. Not sure if this was the same... The computer restart should have renewed though... Strange.

    2: What browser are you using?

    3: I hope it just looks weird, and not bad weird. :grin: Dnsmasq just allocates new addresses differently than udhcpd.
  16. coolzero

    coolzero Guest

    :cheer: Upgraded my Linksys Wireless-B v4 router today to Linksys WRT54G v4.0. Performed a hard reset. Flashed it with new Tofu v7.0. Performed a hard reset again. Configured my new WRT54G v4.0 to my liking and everything works fine.

    Great firmware :thumb:
  17. Cassius

    Cassius Network Guru Member

    Hi guys,

    I've upgraded and it seems to work fine...

    I'm using my WRT54g v2 in WDS mode connecting to another Modem/Router AP... this seems to work flawlessly...

    What im curious about though, is do i have to set the default gateway on the wrt54g when in WDS mode??

    This is something i used to do, becuase i thought this was required if i wanted to talk to clients connected on the other modem/router, but i have not done that this time and it still seems to work perfectly?? \0/

    My second question is regarding WET, I was interested in running the router in this mode as there appear to be some performance advantages over WDS, however i havent been successful in getting this to work. This is what i have done:

    1. Set router to WDS mode in advance wireless settings
    2. Set the SSID to be the same as the other Modem/router
    3. Set the channel to be the sam os other router

    Is ther something obvious im missing??

    I turned security off until i am able to connec both through WET any suggestions would be helpful thanks :)

    Oh and whats the difference between WDS-AP and WDS??? as they both seem to work
  18. 4Access

    4Access Network Guru Member

    No, there's no need to set the gateway in the LAN configuration area for most implementations.

    Well the first thing is that you need to be in WET mode not WDS mode... (Probably just a typo? Expecially considering there is no WDS option in the Advanced Wireless settings...)

    Did you look at my post avove about this topic? At least 3 people have gotten it working using those instructions...

    I'm curious about this too although I'll admit I've done no testing or searching for the answer...

    How about the Bridge Restrict option? (I know, I know, I should search but I'm already posting... :D)
  19. Cassius

    Cassius Network Guru Member

    oops definitely a spelling mistake...

    i meant:

    1. Set router to WET mode in advance wireless settings
    2. Set the SSID to be the same as the other Modem/router
    3. Set the channel to be the same as other router

    And yeah i did look at your post above 4access... but i really cant see what im doing wrong..... is there a step im missing?? Although i am running static ip's all round... does this make a difference??
  20. bashy

    bashy Network Guru Member

    With my setup I using the 2nd router with WET without any encryption set however when I enable Wireless MAC filter on the MAIN router I lose the bridge. I've added the MAC of the 2nd router on the access list and I've also added the MAC to the LAN PC using the bridge without any luck.. so far this option HAS to be diabled on your main AP router!
  21. DallasFlier

    DallasFlier Network Guru Member

    L7 filter is not missing. It does not belong in this firmware. Of course, you posted this request several weeks ago in the HyperWRT forum, and not a single other user of HyperWRT supported your request. So now you've come to this forum to whine. The userbase of HyperWRT does not WANT this to become bloated with all sorts of other things like L7 - L7 is NOT a router function. Set up a Linux box and run L7 if that's what you want, but its not something that the HyperWRT users want to see the firmware bloated with.
  22. 4Access

    4Access Network Guru Member

    If you really want L7 there's always DD-WRT. ;) (Although honestly I'm surprised more people don't want it in HyperWRT...)
  23. Toxic

    Toxic Administrator Staff Member

    you have to look at the bigger picture. not everyone wants/users l7 filters in the first place. becuase one person does, should everyone else say yes to it?

    I am sure if enough customers wanted it it may be added however the HypwerWRT userbase shows they are happy with what they have got now.
  24. 4Access

    4Access Network Guru Member

    Maybe I wasn't clear in my last post... I was trying to suggest to the user that requested L7 that they consider using the DD-WRT firmware instead of HyperWRT since DD-WRT includes L7.

    I also understand and appreciate that HyperWRT only wants to include the most requested features to keep the firmware as close to the Linksys codebase as possible. I wasn't suggesting that L7 be added to HyperWRT at this time, I was just stating that I was surprised more people haven't requested L7 be included in HyperWRT.

  25. Toxic

    Toxic Administrator Staff Member

    yeah sure. if you want L7 then use something else take makes sense.
  26. nicktang

    nicktang Guest

    Does anyone know is overclocking possible in this firmware?
    I have tried this
    nvram set clkfreq=228,114
    nvram commit
    but it returns to 215Mhz after reboot
  27. SteelersFANinMA

    SteelersFANinMA Network Guru Member

    nvram set clkfreq=228,114?

    Are you trying to turn your WRT into a bomb?
  28. vais

    vais Network Guru Member

    1. Exactly. The computer has restarted and this is when I was expecting it to renew dhcp. Another one: I have .131 assigned to me by the DHCP server. I added static lease to be .100. And it indeed renewed successfully and I got .100 address. However it is still .131 in the device list !! Looks like it has not updated

    2. Yes, with Firefox it works. Doesn't work with IE.

    3. Understood.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice