1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Tomato ND USB Mod

Discussion in 'Tomato Firmware' started by teddy_bear, Dec 17, 2008.

  1. Rasky

    Rasky Addicted to LI Member

    Hello everybody,

    sorry in advance if my questions are naive, but I have little experience with tomato and all its world :)

    I'm especially interested in the ntfs-3g support in the new build. I've yet to configure Optware, but all the guides seem to hint at putting /opt on an external USB disk. I've got a little chicken-egg problem here, since I've tons of NTFS-only disks, and I don't feel like adding a FAT partition on all of them just for optware.

    Is it possible to install Optware somewhere else (eg: within the router itself somehow)? What are other alternatives? Maybe using a USB pendrive? Is it feasable to integrate ntfs-3g within the standard extra build of tomato-usb, just like ext2/ext3?
     
  2. teddy_bear

    teddy_bear Network Guru Member

    Sure. I have my /opt partition on 1GB USB flashdrive which is just permanently attached to the router via usb hub.

    You need to format the Optware partition as ext2 (if using flashdrive) or ext3 (if using HDD) - FAT or NTFS won't work!

    If you have 8MB flash router, you can even use JFFS space for Optware, and mount it on /opt - just remember that ~4MB is not much, and you won't be able to install a lot of software (whereas 1 GB flash would probably be enough for all available Optware packages!)

    Prepare the partition (with Ext version of this mod, you can partition and format the drive right on the router using built-in utilities), mount it on /opt, and follow the instructions from the "Installing ipkg-opt and uclibc-opt" paragraph of dd-wrt wiki. Do not modify search PATH or LD_LIBRARY_PATH as dd-wrt wiki says though!
    Then configure the router to auto-mount your Optware partition on /opt on startup (for example, you can echo lines into /etc/fstab file in your Init script as I do), and you are good to go - just run "ipkg update" first, and then use ipkg command to install additional packages.

    Integrating ntfs-3g within the standard extra build is unlikely, since it's too big. Although it still barely fits on 4MB flash, it leaves absolutely no free space, so in case of any future updates or changes - even minor ones - it may no longer fit...
     
  3. Rasky

    Rasky Addicted to LI Member

    OK thanks, this got me started. I've got everything running on JFFS right now but I'll go buying a flashdrive later today.

    I've got an additional question. A friend has a DSL connection so he needs a solution that involves a DSL modem. I read that tomato can run pppoe (is it true of tomato-nd-usb too?) so you can probably connect a DSL modem in ppp bridge mode. But is there an all-in-one solution? Is there a DSL+router+AP+USB thingie that is supported by tomato? I like Asus routers but WL-600g (with DSL modem) seems unsupported (is that because of the broadcom 6348, or anything else?).
     
  4. greenythebeast

    greenythebeast LI Guru Member

    Quick question: I have my optware installed on a 512MB flashdrive that is permanently attached to the router. If I want to upgrade the firmware to the latest release by teddy will I have to reinstall all of my optware packages?
     
  5. Toastman

    Toastman Super Moderator Staff Member Member

    Did anyone do a throughput test on this "downgraded" driver yet?
     
  6. TexasFlood

    TexasFlood Network Guru Member

    Nothing I tried has helped yet, at least in terms of really fixing the issue.

    If I reboot the main router and not the WDS client routers, they never all seem to link back up.

    If I reboot them all at the same (or as nearly as possible) to the same time, again they don't all link back up.

    If however I reboot all routers offset by a couple of seconds between each, with the main router last, they always seem to sync back up fine.

    Not sure what that behaviour means, if anything. But at least I have a seemingly reliable workaround way to reboot.
     
  7. teddy_bear

    teddy_bear Network Guru Member

    Does anyone else beside TexasFlood have the same WDS issues with this mod?

    Toastman,
    I don't have any good testing software (like IxChariot or something), so I only did some basic testing transfering large files between several wireless clients. There was no noticeable difference between versions 4.158.4.0 and 4.150.10.29 - at least on my Asus there wasn't.

    greenythebeast,
    No, you won't have to reinstall the Optware - it will still be working. In fact, you can move your flashdrive to dd-wrt router, and it still will be working (aside from some custom firmware-specific scripts you might have added). The same is true about moving Optware drive from dd-wrt to Tomato.
     
  8. greenythebeast

    greenythebeast LI Guru Member

    I know that restoring settings from older firmware is a bad idea. But is there a way to backup the various static routes I have set up or is the best way to do that just to copy/paste to a txt document and replace them after upgrading?
     
  9. madduru

    madduru Addicted to LI Member

    Sorry for posting this in this forum. I recently bought ASUS WL520GU router and flashed it with the official Tomato 1.25. But I want to to add USB support to it and I am looking for the "teddy_bear" mod for Tomato 1.25. Can someone please post the link to the firmware download? I am going round and round to find one, still in vain? I appreciate your help on this, Thanks.
     
  10. teddy_bear

    teddy_bear Network Guru Member

    madduru,
    Have you read the 1st post in this thread? If you did, read it again... Don't let the topic title to mislead you - I just don't know how to rename it ;)...

    greenythebeast,
    What version are you upgrading from? If it's any flavor of Tomato 1.24 or 1.25 (and even 1.23 I think), you don't need to reset your settings unless you experience some problems.
     
  11. greenythebeast

    greenythebeast LI Guru Member

    Thanks for the info teddy_bear. I just upgraded to build 35 and cleared my NVRAM, but from now on I'll leave the settings in place when I upgrade.

    Also, I have a question regarding my router WL500GPv2. I see you downgraded the broadcom driver to fix some problems on this type of router. What were the problems that were occuring, since I've been experiencing poor signal strength on my router from not more than 7 feet away.
     
  12. teddy_bear

    teddy_bear Network Guru Member

    greeny,
    Search for posts by koszpa in this thread for the details of what connectivity issues he and a few others experienced with this router.
    As for the poor signal, there could be 1001 different reasons for this. The driver in the last build may or may not help. Again - search the forum - this has been discussed many times here, along with various possible solutions...

    Also, don't take it that you never need to eraze nvram when upgrading. It all depends on actual changes in the firmware from one version to another. Sometimes you absolutely have to eraze nvram to keep things working properly. So the rule should be - always eraze nvram and reconfigure manually unless the firmware developer tells you not to :wink:... In case of my mod though, I will always post it in the release notes if nvram has to be erazed (but of course, if you miss a few builds, you won't know for sure unless you read all previous release notes :) ).
     
  13. TexasFlood

    TexasFlood Network Guru Member

    I don't know if it's limited to this mod, I suspect not but would have to do more testing.

    So the problem is if I do one of two things:
    1) Reboot my main router but not the WDS client routers (I have 3 of them currently)
    or
    2) Reboot the main router at or very nearly at the same time as my client routers

    In either case I will almost always end up with one or two of the WDS links showing up under the devices list but the routers unable to communicate across the link(s). Rebooting a client router by itself or rebooting them staggered with the main router last both seem to be fine.

    In case you're wondering, these WDS clients are to get wired ports where they are needed around the house since I don't have Ethernet wiring, :-( . None of them are acting as wireless bridges or access points, just adding remote wired ports for those wired devices. So the impact is whatever wired devices are attached to the "disconnected" WDS client router (be it a printer, DVR, etc) are cut off from the network. Other wireless devices are fine as they all connect to the main router with no issues.
     
  14. teddy_bear

    teddy_bear Network Guru Member

    TexasFlood, I have a test version for you if you want to try it. If so, PM me...
     
  15. TexasFlood

    TexasFlood Network Guru Member

    I like the scrapbook extension for firefox to capture settings or backup or copy/paste. There is still manual labor involved in re-entering the settings but it does capture everything in an offline form for cutting & pasting back in so helps eliminate human error. I have also used adobe acrobat for this in the past but that's not a free tool. One of the most difficult configs I had to move recently was my static IP table which has a lot of entries. If you go to that page and select the data correctly, you can paste it right into excel which is a nice way to keep a offline copy of that.
     
  16. greenythebeast

    greenythebeast LI Guru Member

    Oh yeah, I'd also like to report that with the latest build, the wireless survey function doens't work on my WL500GPv2. This was also the case in the previous build.

    Also, is there any way to add HFS+ file system support for USB drives?
     
  17. teddy_bear

    teddy_bear Network Guru Member

    What do you mean by "not working"? What does it do exactly when you hit "Refresh" on that page? Just tries for a few seconds, and shows nothing? Or does your router, or this page hang? Does "Measure Noise Floor" work on the "Device List" page?

    As for HFS+, the compiled module that you can insmod - hfsplus.o - is available in the package of extra stuff (extras.tar.gz) from the main download location. Just make sure you download one from the "Experimental" section, because the old modules won't work with v35 or newer. HFS+ won't be built-in into the firmware because of the size restrictions.
     
  18. TexasFlood

    TexasFlood Network Guru Member

    Works on my WL500GPv2, wonder what the difference is? You tried clicking on "refresh"?
     
  19. greenythebeast

    greenythebeast LI Guru Member

    I'm sorry I should have explained the problem. It's not the wireless survey that doesn't work. What I am referring to is when you are setting the Wireless channel in the basic wireless menu and you press Scan it is supposed to bring up how many APs are on each channel. When I press Scan it takes a few seconds like it is working but ultimately doesn't show the results.

    Also, I'm not sure how to use insmod. Could you explain to me how I can go about installing hfsplus.o?
     
  20. TexasFlood

    TexasFlood Network Guru Member

    FYI, that also works on my wl500gpv2, although I didn't even know that function was there, first time I'd ever tried it.
     
  21. teddy_bear

    teddy_bear Network Guru Member

    This "Scan" and Wireless Survey both use the same exact code to obtain the data, so if one works the other one just can't fail.
    Where are you expecting to see the results after clicking "Scan" ;)?
    Did you figure out how to find, download and install Tomato? Insmod is easier ;). Just search - here, google, dd-wrt wiki's, etc - I gave you all the keywords to get started... Remember, you're always welcome to ask questions here, but it's not a support forum, so don't always expect the answers...
     
  22. greenythebeast

    greenythebeast LI Guru Member

    I think I've figured out both problems. Thanks for your help.
     
  23. goRt

    goRt LI Guru Member


    I'm not sure why you guys have problems with WDS - I have WDS enabled on 3 WHR-HP-G54s without any problem. All set-up as WDS+AP.

    *** I could only get them working with AES NOT TKIP (and WPA/2 - AES being the part that caused earlier problems)
    I reboot whichever whenever and everything always recovers without intervention.

    Hope that helps​
     
  24. jnappert

    jnappert LI Guru Member

    I can confirm this.

    WPA/AES is rock solid. WPA/WPA2 with AES may cause problems. WPA or WPA/WPA2 with TKIP or AES/TKIP ist simply impossible.
     
  25. TexasFlood

    TexasFlood Network Guru Member

    My WDS has been pretty solid for at least the last year, I don't really remember how much over a year. But yes I've been running WPA AES on 4 routers all of nearly identical vintage, corerev of 7 across the board, running non-ND Tomato. Your routers look to be virtually identical like mine were during the period when my WDS was rock solid.

    When I just recently bought a WL500GPv2, I introduced much newer hardware (corerev=13) with a new wireless driver into the mix which I suspect that is the root of the issue with WDS not always syncing up. When this happens I lose touch with 1 or more remote routers and either have to go power cycle it or reboot the rest until communication is restored.

    Back when I ran DD-WRT and mixed DD-WRT & Tomato environments with a few different encryption schemes, I did have issues with WDS links losing communication. I had forgotten what I used to do about this when it happened before. Back then I used the built in "WDS watchdog" function of DD-WRT to reboot the remote WDS router if it lost contact and used a script to do the same on Tomato remote WDS routers. It had been so long since I had this problem that I'd forgotten but remembered last night. I still had the script squirreled away and had also posted it here over a year ago.

    I put that script back in my Tomato WDS remotes and it's working fine so think I have an adequate workaround for the issue now. Although it would be great to figure out why it's happening, I'm not going to hold my breath waiting for it. Teddy bear is trying to solve it and I'll test possible solutions he comes up with.
     
  26. madduru

    madduru Addicted to LI Member

    teddy_bear,
    thank you very much for your reply. As you suggested I did reread the first post and was able to get to the downloads page. Also I want to share my experience on becoming a recent convert of teddy_bear mod of Tomato on Asus WL520GU router. I wanted to help out all those newbies trying to get into Tomato. What I learnt during the Tomato installation process is: the quick and easy way to install Tomato firmware is to first downgrade the router firmware and then upgrade to the latest tomato mod.

    The steps I used are:

    Installing Tomato on ASUS WL520GU
    =============================
    1) Go to ASUS website to downgrade to oldest firmware (WL520gu_2.0.0.8_EN.trx). Make sure you use Internet Explorer browser. (If you use Firefox, you may not be able to scroll the list of downloads!)
    2) Download Tomato with USB support (1.25 ND USB). from here: http://www.mediafire.com/tomatousb
    3) Rename Tomato_modded file to WL520gu_2.0.0.9_EN.trx and save to c:/Temp
    4) Login to router (http://192.168.1.1), go to administration, upgrade Firmware with above file
    5) Now you are ready to play with Tomato
     
  27. Anzial

    Anzial Addicted to LI Member

    First of, thanks for an awesome mod, teddy bear. Now, I hope you can help to figure something about the traffic counter in this firmware. I'm new to Tomato (been running DD-WRT for a while) and I have Asus 520GU. Since I wanted to use USB for something, I've decided to flash to your latest developmental version 35 (hopefully, since you running it on your 520gu, it won't ruin mine lol :D)

    Anyways, for some reason, wan (vlan1) reports about 20%-25% more traffic through the WAN port than it should. I mean, when I compare my usual activities tracked by DD-WRT and same activities tracked by Tomato, vlan1 reports much more. I mean, let's say I download a 1gb file, Tomato shows 1.2gb went through WAN. Br0 and vlan0, on other hand, show a much closer figure (well, still about 2%-5% inflated) to what I do traffic-wise. Now, this happened with both stock and your modded Tomato so in no way I'm blaming you, all I need is your help with figuring out what's going on here. Does Tomato generate overhead traffic? or am I reading the traffic report wrong?
     
  28. teddy_bear

    teddy_bear Network Guru Member

    Anzial,
    Don't worry, Tomato doesn't generate the extra traffic :).
    Try to add br0 and eth1 (the names of LAN and WLAN interfaces on 520gu) to the "Excluded Interfaces" list on "Administration -> Bandwidth Monitoring" page in the GUI, and see if the numbers will come closer to what you expect.
     
  29. shibby20

    shibby20 Network Guru Member

    teddy_bear - can you compile fuse module? i want to mount ntfs (rw) partition on your tomato 1.25 v34 :)
     
  30. teddy_bear

    teddy_bear Network Guru Member

    shibby20,
    No. You can use v35, or wait until v36.

    By the way, remember the lan NAS drive you had problems with? I believe it should work now with CIFS in v35 - you'll need to specify netbios name in addition to UNC path, and LANMAN security option. Let me know if you try it, and if it works. If you don't want to flush experimental build, wait for v36 - should be out in a few days.
     
  31. shibby20

    shibby20 Network Guru Member

    i sold landisk few months ago and buyed dlink dns-313. in august i sold dns-313 and now i`m waiting for asus RT-N16 or netgear wnr3500l :)

    tell me... fuse module from v35 will be work with v34 or definitely not? if not, i have to wait for v36. i don`t want to flush experimental build.
     
  32. teddy_bear

    teddy_bear Network Guru Member

    It will not.
     
  33. shibby20

    shibby20 Network Guru Member

    true :)

    if i upgrade firmware from v34 to v35, i have to clear nvram or not?
     
  34. Anzial

    Anzial Addicted to LI Member

  35. Rasky

    Rasky Addicted to LI Member

    What performance are you guys getting out of an USB disk? I'm around 1Mbyte/s, with WL-500gP, 802.11g, ext3 partition. smbd peaks at 30-40% in top, and I'm not sure how to measure if ext3 itself is bottlenecking.
     
  36. CsBubo

    CsBubo Addicted to LI Member

    My question goes to Ray123.
    I'm trying to load the videodev.o in v35, but propably because of the new kernel, I'm getting:

    Code:
    insmod videodev.o
    insmod: unresolved symbol __up
    So can You try to compile the modules for the new kernel.
    Thanks in advance.

    @Rasky
    Try ext2, it should be around 3-3,5MB/s.
    Note, that You can mount ext3 partitions, just You'd need to mount it manually like:

    Code:
    mount -t ext2 /dev/scsi/<your_disc_here> /where/you/want/to/mount/it
    The -t ext2 param will cause to not to use the journal.
     
  37. teddy_bear

    teddy_bear Network Guru Member

    For v35, you need to download the new extras.tar.gz package from "Experimental" folder (link in the 1st post) that has optional modules compiled for the new kernel.
    I don't know what application you're trying to use with it though - if it's something that you or Ray compiled for previous Tomato builds, most probably it won't work because the new firmware is compiled against new uClibc. However Optware applications will keep working since Optware uses its own copy of all shared libraries.
    Yep, manually or via fstab. Populate fstab in your Init script (or save it to nvram), and you won't have to manually do mount every time.
     
  38. ghostknife

    ghostknife Addicted to LI Member

    You figured it out but just for other ppl benefit, survey only displays any result if there is some other wireless network i.e. it won't detect its own [tomato] network.
    Chanel scan displays used channels in the drop box after it's finished.
     
  39. swwitch

    swwitch Addicted to LI Member

    teddy_bear - can you compile module to support modems 3G (e.g. Huawei E160, E220, E169 etc)?
     
  40. teddy_bear

    teddy_bear Network Guru Member

    swwitch,
    With upcoming v36 build, I will publish all modules needed to support 3G modems as part of the optional "extras.tar.gz" package.

    Be aware though that I have absolutely no way to test them as I don't own any 3G modems now, and I won't be able to anwser any questions pertaining to 3G modems and configuration.

    In the "extras" package I'll include usbserial.o and option.o kernel modules, libusb library and usb_modeswitch application. For usb_modeswitch to find libusb shared library, you will need to put libusb files (or symlinks to libusb files) to either /opt/usr/lib or /usr/local/share directory - whichever is more convenient for you. From there you're on your own :)... If you figure everything out, configure your modem and get it working, please don't hesitate to post a short "how-to" - I'm sure there will be others who can benefit from it.
     
  41. teddy_bear

    teddy_bear Network Guru Member

    Update - build 36.

    This is mostly a bug fix release. Updated kernel is no longer experimental - seems to be very stable for me. Despite its experimental status, the previous build 35 got 200+ downloads and no bug reports except of a minor issue with igmpproxy being noisy in system log. I found a couple bugs myself though, and fixed them ;). Also, playing with optimization flags allowed me to reduce the firmware size a little more, and made it possible to include NTFS support into "Extras" build. Although the size of "Extras" build is increased compare to v35, it's still a little smaller than it was in v34 - even after all the updates and adding NTFS support!
    • Fixed setting TCP and UDP timeout values on "Advanced -> Conntrack/Netfilter" page, removed obsolete timeouts, added Generic and ICMP timeouts.
    • Fixed incorrect detection of JFFS partition size in all builds.
    • Do not start igmpproxy when WAN is disabled, allow alternative config file for igmpproxy.
    • Full NTFS support via ntfs-3g is now included in "Extras" build. Other builds still can mount writeable NTFS partitions with installed Optware ntfs-3g package.
    • Minor USB driver fixes from 2.6 kernel tree.
    • MiniUPnPd updated to ver. 20091010 (just the version number update - no real changes, since all fixes from this version were already applied to the previous build 35).
    • Dnsmasq updated to ver. 2.51.
    • Other minor fixes, cosmetics, code optimization and clean-up.
    Known issues with this build (will be fixed in the next update):
    • "Wireless Client" and "Wireless Ethernet Bridge" mode may not work properly on some routers even though it was working in build 34 and earlier.
    • Dynamic DNS doesn't work when using secure SSL connection.
    The package of optional modules "extras.tar.gz" (available via links from the 1st post - same location as main firmware binaries) now extended to include support for usb serial devices, usb 3G modems, webcams, mppe/mppc, and also reiserfs, xfs, smbfs and hfs+ filesystems. But don't ask me what to do with these, if you don't know - you don't need them ;)...

    I also made a build with no USB support (of course, ND only as well) - but with all other enhancements included in my regular builds. This is for those who would like to try a version with newer kernel but don't have USB ports on their routers.

    Links to the firmware binaries and the git repository with sources are in the 1st post. All sources are in the git now, including the new toolchain sources, and compiled toolchain. The complete source code of this build can also be downloaded as a git snapshot in tar format.

    No USB+VPN merged build yet - as of now the VPN sources from git still can't be compiled with new toolchain.
     
  42. esac

    esac Addicted to LI Member

    Hi teddy_bear,

    Thanks for a wonderful release.

    I was just on 35 earlier today and I was having speed issues (although it was probably my ISP), but then I noticed 36 was out. I downloaded it, upgraded my firmware, and then reset the NVRAM on my router (thorough). I proceeded to reconfigure everything.

    My laptop has no issues getting onto wireless, but my wifes laptop will not connect. I deleted the wireless network profile, rebooted her computer, disabled and reenabled the wireless nic on her laptop, ipconfig release renew, and no luck. I can see from the Devices list that her computer shows up, is given an IP of 192.168.1.128, and it lists her MAC address. It doesn't list her computer name either, and then it just drops to the bottom of the list and she never gets an IP.

    Most likely this is something on my end but I just wanted to post in case you knew of anything that might cause it, or if anybody else hits the issue.

    Thanks
     
  43. teddy_bear

    teddy_bear Network Guru Member

    esac and others,

    There are wireless connectivity issues with some hardware. When posting about such issues - please indicate your client hardware make, model and driver version. Search this forum and google for the same wireless client model to see if others also experienced similar problems. Update to the latest driver version if possible.

    If the same client worked with vanilla Tomato, previous builds of this mod, or any other firmware - indicate this as well. If you can - test it with other firmwares.

    Just saying that your "client can't connect" gives me and others absolutely zero information, and without the information nobody can help you, as well as nothing can be done without a lot of testing.
     
  44. esac

    esac Addicted to LI Member

    Sorry about that, I thought to do this before I started typing the post and then it slipped my mind.

    My wifes laptop is a Dell Vostro 1510, which has the Dell Wireless 1395 WLAN Mini-Card with a Broadcom Chipset.
    It is running driver version 4.176.75.21
    The laptop is Windows 7 64-Bit RTM

    Her computer worked with your v34 for sure, and v35 as well.

    My router is an ASUS WL-500W.

    The only other firmwares I have tested and both work are stock Asus 2.0.0.6 and latest Oleg's firmware.

    I have looked on the forum for any information, but this is a new issue that I have seen with only v36.

    If I am missing any details please let me know and I will gladly post them.

    Thanks


     
  45. teddy_bear

    teddy_bear Network Guru Member

    There were absolutely no changes in wireless driver, or handling wireless network code between v35 and v36. Something else must be interfering... Anything of interest in the syslog?
    By the way, do you have the configuration saved from v35? If so, try to restore it (nothing's changed between these 2 builds that would require nvram reconfiguration anyway)... Could it be that you forgot to enter some of the important settings after clearing nvram?
     
  46. esac

    esac Addicted to LI Member

    Thanks, that's what I was wondering. I did backup my config before clearing it, so I will backup current and then restore the previous config and see if I missed something. I wanted to clear the nvram because I had gone from v34 -> asus stock -> olegs -> v35 -> v36 and I just wanted to make sure nothing was messed up.

     
  47. teddy_bear

    teddy_bear Network Guru Member

    Hmm... All of that, and only cleared nvram between the last 2 steps ;)?
     
  48. esac

    esac Addicted to LI Member

    Well i've been trying everything. When I am on wireless I am getting 100+ms ping times to yahoo.com, but if I am wired it is in the 40-80 range. If I am on wireless and ping 192.168.1.1 it is only 1-2 ms pings to there. But this 'issue' shows up with any firmware or anything i've done so it is not a Tomato problem.

    For closure, went back to old config and it worked. tried new config again, still didn't work, looked at all the settings under dhcp, dns, wireless, advanced wireless, access restriction and firewall and couldn't find anything different. So I went to the old config again, no reason why I can't run it in case I am being stupid and missing something. Sorry for troubling you.
     
  49. teddy_bear

    teddy_bear Network Guru Member

    Interesting, especially because you can't find the difference... I too would like to know what was the culprit... Let me know if you figure it out.

    Or you can run "nvram show > /tmp/nvram.txt" command (it will save your nvram to a sorted text file in /tmp directory on your router) on both configurations (well, you'll need to restore your "bad" config for that), and then compare these text files - maybe then you'll see what was different. Or send these files to me (mask out your passwords etc first)...
     
  50. freddyspam

    freddyspam Addicted to LI Member

    Hello there again. I missed the v35 build and today I tried the v36.
    So v34 ->v36.
    My setup:

    ISP<--->Main Wireless Router<--->520gu Router with your firmware<--->Desktop

    The 520gu connects to the main router using the wireless bridge mode. Under v34, the signal strength was 40-60. After the update to v36, the signal strength is 0-30. From the desktop, I cannot contact the main router even though the 520gu says it is connected. I obviously cannot connect to the internet with the desktop either. The 520gu cannot update its time. When I use a computer connected to the main router, I cannot access the 520gu. When I log into the main router, it shows the 520gu as connected. No settings were changed for the upgrade. I then tried v35, and have the same issues. Disabling USB core changes nothing. Going to v34 fixes all of these issues. Below are my logs for v34, v35 and v36 (all of them ext):

    v34:
    Code:
    Dec 31 16:00:15 NAS syslog.info syslogd started: BusyBox v1.14.3
    Dec 31 16:00:15 NAS user.notice kernel: klogd started: BusyBox v1.14.3 (2009-08-17 20:49:23 EDT)
    Dec 31 16:00:15 NAS user.warn kernel: CPU revision is: 00029029
    Dec 31 16:00:15 NAS user.warn kernel: Primary instruction cache 16kb, linesize 16 bytes (4 ways)
    Dec 31 16:00:15 NAS user.warn kernel: Primary data cache 16kb, linesize 16 bytes (2 ways)
    Dec 31 16:00:15 NAS user.warn kernel: Linux version 2.4.20 (root@tomato) (gcc version 3.2.3 with Broadcom modifications) #2 Mon Aug 17 21:02:06 EDT 2009
    Dec 31 16:00:15 NAS user.warn kernel: Setting the PFC to its default value
    Dec 31 16:00:15 NAS user.warn kernel: Determined physical RAM map:
    Dec 31 16:00:15 NAS user.warn kernel:  memory: 01000000 @ 00000000 (usable)
    Dec 31 16:00:15 NAS user.warn kernel: On node 0 totalpages: 4096
    Dec 31 16:00:15 NAS user.warn kernel: zone(0): 4096 pages.
    Dec 31 16:00:15 NAS user.warn kernel: zone(1): 0 pages.
    Dec 31 16:00:15 NAS user.warn kernel: zone(2): 0 pages.
    Dec 31 16:00:15 NAS user.warn kernel: Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
    Dec 31 16:00:15 NAS user.warn kernel: CPU: BCM5354 rev 3 at 240 MHz
    Dec 31 16:00:15 NAS user.warn kernel: Calibrating delay loop... 197.83 BogoMIPS
    Dec 31 16:00:15 NAS user.info kernel: Memory: 14372k/16384k available (1420k kernel code, 2012k reserved, 108k data, 64k init, 0k highmem)
    Dec 31 16:00:15 NAS user.info kernel: Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
    Dec 31 16:00:15 NAS user.info kernel: Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
    Dec 31 16:00:15 NAS user.warn kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    Dec 31 16:00:15 NAS user.warn kernel: Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
    Dec 31 16:00:15 NAS user.warn kernel: Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
    Dec 31 16:00:15 NAS user.warn kernel: Checking for 'wait' instruction...  unavailable.
    Dec 31 16:00:15 NAS user.warn kernel: POSIX conformance testing by UNIFIX
    Dec 31 16:00:15 NAS user.warn kernel: PCI: no core
    Dec 31 16:00:15 NAS user.warn kernel: PCI: Fixing up bus 0
    Dec 31 16:00:15 NAS user.info kernel: Linux NET4.0 for Linux 2.4
    Dec 31 16:00:15 NAS user.info kernel: Based upon Swansea University Computer Society NET3.039
    Dec 31 16:00:15 NAS user.warn kernel: Initializing RT netlink socket
    Dec 31 16:00:15 NAS user.warn kernel: Starting kswapd
    Dec 31 16:00:15 NAS user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
    Dec 31 16:00:15 NAS user.info kernel: devfs: boot_options: 0x1
    Dec 31 16:00:15 NAS user.info kernel: squashfs: version 3.0 (2006/03/15) Phillip Lougher
    Dec 31 16:00:15 NAS user.warn kernel: pty: 256 Unix98 ptys configured
    Dec 31 16:00:15 NAS user.info kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
    Dec 31 16:00:15 NAS user.info kernel: ttyS00 at 0xb8000300 (irq = 3) is a 16550A
    Dec 31 16:00:15 NAS user.info kernel: ttyS01 at 0xb8000400 (irq = 0) is a 16550A
    Dec 31 16:00:15 NAS user.warn kernel: HDLC line discipline: version $Revision: 1.1.1.4 $, maxframe=4096
    Dec 31 16:00:15 NAS user.info kernel: N_HDLC line discipline registered.
    Dec 31 16:00:15 NAS user.info kernel: PPP generic driver version 2.4.2
    Dec 31 16:00:15 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x400000 for the chip at 0x0
    Dec 31 16:00:15 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
    Dec 31 16:00:15 NAS user.debug kernel: Physically mapped flash: Found an alias at 0xc00000 for the chip at 0x0
    Dec 31 16:00:15 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
    Dec 31 16:00:15 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x1400000 for the chip at 0x0
    Dec 31 16:00:15 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
    Dec 31 16:00:15 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x1c00000 for the chip at 0x0
    Dec 31 16:00:15 NAS user.notice kernel:  Amd/Fujitsu Extended Query Table v1.1 at 0x0040
    Dec 31 16:00:15 NAS user.notice kernel: number of CFI chips: 1
    Dec 31 16:00:15 NAS user.notice kernel: Flash device: 0x400000 at 0x1c000000
    Dec 31 16:00:15 NAS user.notice kernel: Creating 5 MTD partitions on "Physically mapped flash":
    Dec 31 16:00:15 NAS user.notice kernel: 0x00000000-0x00020000 : "pmon"
    Dec 31 16:00:15 NAS user.notice kernel: 0x00020000-0x003f0000 : "linux"
    Dec 31 16:00:15 NAS user.notice kernel: 0x000cccb4-0x003d0000 : "rootfs"
    Dec 31 16:00:15 NAS user.notice kernel: 0x003d0000-0x003f0000 : "jffs2"
    Dec 31 16:00:15 NAS user.notice kernel: 0x003f0000-0x00400000 : "nvram"
    Dec 31 16:00:15 NAS user.err kernel: sflash: found no supported devices
    Dec 31 16:00:15 NAS user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
    Dec 31 16:00:15 NAS user.info kernel: IP Protocols: ICMP, UDP, TCP, IGMP
    Dec 31 16:00:15 NAS user.info kernel: IP: routing cache hash table of 16384 buckets, 128Kbytes
    Dec 31 16:00:15 NAS user.info kernel: TCP: Hash tables configured (established 1024 bind 2048)
    Dec 31 16:00:15 NAS user.info kernel: Linux IP multicast router 0.06 plus PIM-SM
    Dec 31 16:00:15 NAS user.warn kernel: ip_conntrack version 2.1 (16384 buckets, 8192 max) - 368 bytes per conntrack
    Dec 31 16:00:15 NAS user.warn kernel: ip_tables: (C) 2000-2002 Netfilter core team
    Dec 31 16:00:15 NAS user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    Dec 31 16:00:15 NAS user.info kernel: NET4: Ethernet Bridge 008 for NET4.0
    Dec 31 16:00:15 NAS user.alert kernel: 802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>
    Dec 31 16:00:15 NAS user.alert kernel: All bugs added by David S. Miller <davem@redhat.com>
    Dec 31 16:00:15 NAS user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly.
    Dec 31 16:00:15 NAS user.info kernel: Mounted devfs on /dev
    Dec 31 16:00:15 NAS user.info kernel: Freeing unused kernel memory: 64k freed
    Dec 31 16:00:15 NAS user.warn kernel: Algorithmics/MIPS FPU Emulator v1.5
    Dec 31 16:00:15 NAS user.warn kernel: ip_conntrack_pptp version 1.9 loaded
    Dec 31 16:00:15 NAS user.warn kernel: ip_nat_pptp version 1.5 loaded
    Dec 31 16:00:15 NAS user.warn kernel: ip_conntrack_rtsp v0.01 loading
    Dec 31 16:00:15 NAS user.warn kernel: ip_nat_rtsp v0.01 loading
    Dec 31 16:00:15 NAS user.warn kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 4.158.4.0
    Dec 31 16:00:15 NAS user.warn kernel: eth1: Broadcom BCM4318 802.11 Wireless Controller 4.158.4.0
    Dec 31 16:00:15 NAS user.warn kernel: tomato_ct.c [Aug 17 2009 21:07:01]
    Dec 31 16:00:15 NAS user.info kernel: usb.c: registered new driver usbdevfs
    Dec 31 16:00:15 NAS user.info kernel: usb.c: registered new driver hub
    Dec 31 16:00:15 NAS user.warn kernel: USB20H fcr: 0x64
    Dec 31 16:00:15 NAS user.warn kernel: USB20H shim cr: 0x8f7
    Dec 31 16:00:15 NAS user.warn kernel: USB20H syn01 register : 0xfe00fe
    Dec 31 16:00:15 NAS user.warn kernel: USB20H syn03 register : 0x1
    Dec 31 16:00:15 NAS user.info kernel: ehci_hcd 00:03.1: PCI device 14e4:471a
    Dec 31 16:00:15 NAS user.info kernel: ehci_hcd 00:03.1: irq 6, pci mem b8003800
    Dec 31 16:00:15 NAS user.info kernel: usb.c: new USB bus registered, assigned bus number 1
    Dec 31 16:00:15 NAS user.warn kernel: PCI: 00:03.1 PCI cache line size set incorrectly (0 bytes) by BIOS/FW, correcting to 32
    Dec 31 16:00:15 NAS user.info kernel: ehci_hcd 00:03.1: USB 0.0 enabled, EHCI 1.00, driver 10 Dec 2004/2.4
    Dec 31 16:00:15 NAS user.info kernel: hub.c: USB hub found
    Dec 31 16:00:15 NAS user.info kernel: hub.c: 2 ports detected
    Dec 31 16:00:15 NAS user.info kernel: SCSI subsystem driver Revision: 1.00
    Dec 31 16:00:15 NAS user.info kernel: Initializing USB Mass Storage driver...
    Dec 31 16:00:15 NAS user.info kernel: usb.c: registered new driver usb-storage
    Dec 31 16:00:15 NAS user.info kernel: USB Mass Storage support registered.
    Dec 31 16:00:15 NAS user.info kernel: hub.c: new USB device 00:03.1-1, assigned address 2
    Dec 31 16:00:15 NAS user.info kernel: hub.c: USB hub found
    Dec 31 16:00:15 NAS user.info kernel: hub.c: 4 ports detected
    Dec 31 16:00:15 NAS user.info kernel: Journalled Block Device driver loaded
    Dec 31 16:00:15 NAS user.info kernel: usb.c: registered new driver usblp
    Dec 31 16:00:15 NAS user.info kernel: printer.c: v0.13: USB Printer Device Class driver
    Dec 31 16:00:15 NAS user.info kernel: hub.c: new USB device 00:03.1-1.2, assigned address 3
    Dec 31 16:00:15 NAS user.info kernel: vlan0: dev_set_promiscuity(master, 1)
    Dec 31 16:00:15 NAS user.info kernel: device eth0 entered promiscuous mode
    Dec 31 16:00:15 NAS user.info kernel: device vlan0 entered promiscuous mode
    Dec 31 16:00:15 NAS user.info kernel: scsi0 : SCSI emulation for USB Mass Storage devices
    Dec 31 16:00:15 NAS user.warn kernel:   Vendor: Generic   Model: External          Rev: 2.10
    Dec 31 16:00:15 NAS user.warn kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
    Dec 31 16:00:15 NAS user.warn kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
    Dec 31 16:00:15 NAS user.warn kernel: SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
    Dec 31 16:00:15 NAS user.info kernel: Partition check:
    Dec 31 16:00:15 NAS user.info kernel:  /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3
    Dec 31 16:00:15 NAS user.debug kernel: WARNING: USB Mass Storage data integrity not assured
    Dec 31 16:00:15 NAS user.debug kernel: USB Mass Storage device found at 3. Host: 0
    Dec 31 16:00:15 NAS user.info kernel: device eth1 entered promiscuous mode
    Dec 31 16:00:15 NAS user.info kernel: vlan1: dev_set_promiscuity(master, 1)
    Dec 31 16:00:15 NAS user.info kernel: device vlan1 entered promiscuous mode
    Dec 31 16:00:15 NAS user.info kernel: br0: port 3(vlan1) entering learning state
    Dec 31 16:00:15 NAS user.info kernel: br0: port 2(eth1) entering learning state
    Dec 31 16:00:15 NAS user.info kernel: br0: port 1(vlan0) entering learning state
    Dec 31 16:00:15 NAS user.info kernel: br0: port 3(vlan1) entering forwarding state
    Dec 31 16:00:15 NAS user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:15 NAS user.info kernel: br0: port 2(eth1) entering forwarding state
    Dec 31 16:00:15 NAS user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:15 NAS user.info kernel: br0: port 1(vlan0) entering forwarding state
    Dec 31 16:00:15 NAS user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:15 NAS user.info kernel: br0: port 3(vlan1) entering disabled state
    Dec 31 16:00:15 NAS user.warn kernel: vlan1: Setting MAC address to  00 24 8c 00 a6 4a.
    Dec 31 16:00:15 NAS user.info kernel: br0: port 3(vlan1) entering learning state
    Dec 31 16:00:15 NAS user.info kernel: br0: port 3(vlan1) entering forwarding state
    Dec 31 16:00:15 NAS user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:15 NAS user.warn kernel: SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
    Dec 31 16:00:15 NAS user.info kernel:  /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3
    Dec 31 16:00:15 NAS user.info kernel: kjournald starting.  Commit interval 5 seconds
    Dec 31 16:00:15 NAS user.warn kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
    Dec 31 16:00:15 NAS user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
    Dec 31 16:00:15 NAS user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
    Dec 31 16:00:15 NAS user.warn kernel: MSDOS FS: IO charset utf8
    Dec 31 16:00:17 NAS user.info kernel: Adding Swap: 1052216k swap-space (priority -1)
    Dec 31 16:00:18 NAS cron.err crond[246]: crond (busybox 1.14.3) started, log level 9
    Dec 31 16:00:20 NAS user.info init[1]: Tomato 1.25.8634 ND USB Ext
    Dec 31 16:00:20 NAS user.info init[1]: Asus WL-520GU
    Oct 19 15:55:55 NAS user.info ntpc[103]: Time Updated: Mon, 19 Oct 2009 15:55:55 -0700 [+1255992913.830s]
    Oct 19 15:55:56 NAS daemon.err nmbd[260]: [2009/10/19 15:55:56, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(405)
    Oct 19 15:55:56 NAS daemon.err nmbd[260]:   *****
    Oct 19 15:55:56 NAS daemon.err nmbd[260]:   
    Oct 19 15:55:56 NAS daemon.err nmbd[260]:   Samba name server NAS is now a local master browser for workgroup WORKGROUP on subnet 192.168.10.2
    Oct 19 15:55:56 NAS daemon.err nmbd[260]:   
    Oct 19 15:55:56 NAS daemon.err nmbd[260]:   *****
    Oct 19 15:56:15 NAS cron.err crond[246]: time disparity of 20933215 minutes detected
    v35:
    Code:
    Dec 31 16:00:12 NAS syslog.info syslogd started: BusyBox v1.14.4
    Dec 31 16:00:12 NAS user.info kernel: PPP generic driver version 2.4.2
    Dec 31 16:00:12 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x400000 for the chip at 0x0
    Dec 31 16:00:12 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
    Dec 31 16:00:12 NAS user.debug kernel: Physically mapped flash: Found an alias at 0xc00000 for the chip at 0x0
    Dec 31 16:00:12 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
    Dec 31 16:00:12 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x1400000 for the chip at 0x0
    Dec 31 16:00:12 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
    Dec 31 16:00:12 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x1c00000 for the chip at 0x0
    Dec 31 16:00:12 NAS user.notice kernel:  Amd/Fujitsu Extended Query Table v1.1 at 0x0040
    Dec 31 16:00:12 NAS user.notice kernel:  Flash Id: Vendor: 0x00c2 Device: 0x00a8
    Dec 31 16:00:12 NAS user.notice kernel: number of CFI chips: 1
    Dec 31 16:00:12 NAS user.notice kernel: cfi_cmdset_0002: Disabling fast programming due to code brokenness.
    Dec 31 16:00:12 NAS user.notice kernel: Flash device: 0x400000 at 0x1c000000
    Dec 31 16:00:12 NAS user.notice kernel: Physically mapped flash: squashfs filesystem found at block 799
    Dec 31 16:00:12 NAS user.notice kernel: Creating 5 MTD partitions on "Physically mapped flash":
    Dec 31 16:00:12 NAS user.notice kernel: 0x00000000-0x00020000 : "pmon"
    Dec 31 16:00:12 NAS user.notice kernel: 0x00020000-0x003f0000 : "linux"
    Dec 31 16:00:12 NAS user.notice kernel: 0x000c7f14-0x003c0000 : "rootfs"
    Dec 31 16:00:12 NAS user.notice kernel: 0x003c0000-0x003f0000 : "jffs2"
    Dec 31 16:00:12 NAS user.notice kernel: 0x003f0000-0x00400000 : "nvram"
    Dec 31 16:00:12 NAS user.err kernel: sflash: found no supported devices
    Dec 31 16:00:12 NAS user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
    Dec 31 16:00:12 NAS user.info kernel: IP Protocols: ICMP, UDP, TCP, IGMP
    Dec 31 16:00:12 NAS user.info kernel: IP: routing cache hash table of 16384 buckets, 128Kbytes
    Dec 31 16:00:12 NAS user.info kernel: TCP: Hash tables configured (established 1024 bind 2048)
    Dec 31 16:00:12 NAS user.info kernel: Linux IP multicast router 0.06 plus PIM-SM
    Dec 31 16:00:12 NAS user.warn kernel: ip_conntrack version 2.1 (16384 buckets, 8192 max) - 332 bytes per conntrack
    Dec 31 16:00:12 NAS user.warn kernel: ip_tables: (C) 2000-2002 Netfilter core team
    Dec 31 16:00:12 NAS user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    Dec 31 16:00:12 NAS user.info kernel: NET4: Ethernet Bridge 008 for NET4.0
    Dec 31 16:00:12 NAS user.info kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
    Dec 31 16:00:12 NAS user.info kernel: All bugs added by David S. Miller <davem@redhat.com>
    Dec 31 16:00:12 NAS user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly.
    Dec 31 16:00:12 NAS user.info kernel: Mounted devfs on /dev
    Dec 31 16:00:12 NAS user.info kernel: Freeing unused kernel memory: 80k freed
    Dec 31 16:00:12 NAS user.warn kernel: Algorithmics/MIPS FPU Emulator v1.5
    Dec 31 16:00:12 NAS user.warn kernel: ip_conntrack_pptp version 1.9 loaded
    Dec 31 16:00:12 NAS user.warn kernel: ip_nat_pptp version 1.5 loaded
    Dec 31 16:00:12 NAS user.warn kernel: ip_conntrack_rtsp v0.01 loading
    Dec 31 16:00:12 NAS user.warn kernel: ip_nat_rtsp v0.01 loading
    Dec 31 16:00:12 NAS user.debug kernel: PCI: Setting latency timer of device 00:01.0 to 64
    Dec 31 16:00:12 NAS user.warn kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 4.150.10.29
    Dec 31 16:00:12 NAS user.debug kernel: PCI: Setting latency timer of device 00:05.0 to 64
    Dec 31 16:00:12 NAS user.warn kernel: eth1: Broadcom BCM4318 802.11 Wireless Controller 4.150.10.29
    Dec 31 16:00:12 NAS user.warn kernel: tomato_ct.c [Oct  7 2009 01:09:01]
    Dec 31 16:00:12 NAS user.info kernel: usb.c: registered new driver usbdevfs
    Dec 31 16:00:12 NAS user.info kernel: usb.c: registered new driver hub
    Dec 31 16:00:12 NAS user.debug kernel: PCI: Setting latency timer of device 00:03.1 to 64
    Dec 31 16:00:12 NAS user.info kernel: ehci_hcd 00:03.1: PCI device 14e4:471a
    Dec 31 16:00:12 NAS user.info kernel: ehci_hcd 00:03.1: irq 6, pci mem b8003800
    Dec 31 16:00:12 NAS user.info kernel: usb.c: new USB bus registered, assigned bus number 1
    Dec 31 16:00:12 NAS user.info kernel: ehci_hcd 00:03.1: USB 0.0 enabled, EHCI 1.00, driver 10 Dec 2004/2.4
    Dec 31 16:00:12 NAS user.info kernel: hub.c: USB hub found
    Dec 31 16:00:12 NAS user.info kernel: hub.c: 2 ports detected
    Dec 31 16:00:12 NAS user.info kernel: SCSI subsystem driver Revision: 1.00
    Dec 31 16:00:12 NAS user.info kernel: Initializing USB Mass Storage driver...
    Dec 31 16:00:12 NAS user.info kernel: usb.c: registered new driver usb-storage
    Dec 31 16:00:12 NAS user.info kernel: USB Mass Storage support registered.
    Dec 31 16:00:12 NAS user.info kernel: hub.c: new USB device 00:03.1-1, assigned address 2
    Dec 31 16:00:12 NAS user.info kernel: hub.c: USB hub found
    Dec 31 16:00:12 NAS user.info kernel: hub.c: 4 ports detected
    Dec 31 16:00:12 NAS user.info kernel: Journalled Block Device driver loaded
    Dec 31 16:00:12 NAS user.info kernel: usb.c: registered new driver usblp
    Dec 31 16:00:12 NAS user.info kernel: printer.c: v0.13: USB Printer Device Class driver
    Dec 31 16:00:12 NAS user.info kernel: hub.c: new USB device 00:03.1-1.2, assigned address 3
    Dec 31 16:00:12 NAS user.debug kernel: vlan0: dev_set_promiscuity(master, 1)
    Dec 31 16:00:12 NAS user.info kernel: device eth0 entered promiscuous mode
    Dec 31 16:00:12 NAS user.info kernel: device vlan0 entered promiscuous mode
    Dec 31 16:00:12 NAS user.info kernel: scsi0 : SCSI emulation for USB Mass Storage devices
    Dec 31 16:00:12 NAS user.warn kernel:   Vendor: Generic   Model: External          Rev: 2.10
    Dec 31 16:00:12 NAS user.warn kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
    Dec 31 16:00:12 NAS user.warn kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
    Dec 31 16:00:12 NAS user.warn kernel: SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
    Dec 31 16:00:12 NAS user.info kernel: Partition check:
    Dec 31 16:00:12 NAS user.info kernel:  /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3
    Dec 31 16:00:12 NAS user.debug kernel: WARNING: USB Mass Storage data integrity not assured
    Dec 31 16:00:12 NAS user.debug kernel: USB Mass Storage device found at 3. Host: 0
    Dec 31 16:00:12 NAS user.info kernel: device eth1 entered promiscuous mode
    Dec 31 16:00:12 NAS user.debug kernel: vlan1: dev_set_promiscuity(master, 1)
    Dec 31 16:00:12 NAS user.info kernel: device vlan1 entered promiscuous mode
    Dec 31 16:00:12 NAS user.info kernel: vlan1: attempt to add interface with same source address.
    Dec 31 16:00:12 NAS user.info kernel: br0: port 3(vlan1) entering learning state
    Dec 31 16:00:12 NAS user.info kernel: br0: port 2(eth1) entering learning state
    Dec 31 16:00:12 NAS user.info kernel: br0: port 1(vlan0) entering learning state
    Dec 31 16:00:12 NAS user.info kernel: br0: port 3(vlan1) entering forwarding state
    Dec 31 16:00:12 NAS user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:12 NAS user.info kernel: br0: port 2(eth1) entering forwarding state
    Dec 31 16:00:12 NAS user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:12 NAS user.info kernel: br0: port 1(vlan0) entering forwarding state
    Dec 31 16:00:12 NAS user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:12 NAS user.info kernel: br0: port 3(vlan1) entering disabled state
    Dec 31 16:00:12 NAS user.warn kernel: vlan1: Setting MAC address to  00 24 8c 00 a6 4a.
    Dec 31 16:00:12 NAS user.info kernel: br0: port 3(vlan1) entering learning state
    Dec 31 16:00:12 NAS user.info kernel: br0: port 3(vlan1) entering forwarding state
    Dec 31 16:00:12 NAS user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:12 NAS user.warn kernel: SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
    Dec 31 16:00:12 NAS user.info kernel:  /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3
    Dec 31 16:00:12 NAS user.info kernel: kjournald starting.  Commit interval 1 seconds
    Dec 31 16:00:12 NAS user.warn kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
    Dec 31 16:00:12 NAS user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
    Dec 31 16:00:12 NAS user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
    Dec 31 16:00:12 NAS user.warn kernel: MSDOS FS: IO charset utf8
    Dec 31 16:00:15 NAS cron.err crond[241]: crond (busybox 1.14.4) started, log level 9
    Dec 31 16:00:17 NAS user.info init[1]: Tomato 1.25.8735 ND USB Ext
    Dec 31 16:00:17 NAS user.info init[1]: Asus WL-520GU
    Dec 31 16:00:21 NAS user.info kernel: Adding Swap: 1052216k swap-space (priority -1)
    Dec 31 16:00:45 NAS daemon.err nmbd[236]: [1969/12/31 16:00:45, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(405)
    Dec 31 16:00:45 NAS daemon.err nmbd[236]:   *****
    Dec 31 16:00:45 NAS daemon.err nmbd[236]:   
    Dec 31 16:00:45 NAS daemon.err nmbd[236]:   Samba name server NAS is now a local master browser for workgroup WORKGROUP on subnet 192.168.10.2
    Dec 31 16:00:45 NAS daemon.err nmbd[236]:   
    Dec 31 16:00:45 NAS daemon.err nmbd[236]:   *****
     
  51. freddyspam

    freddyspam Addicted to LI Member

    v36:
    Code:
    Dec 31 16:00:12 NAS syslog.info syslogd started: BusyBox v1.14.4
    Dec 31 16:00:12 NAS user.info hotplug[82]: USB ext3 fs at /dev/discs/disc0/part2 mounted on /tmp/mnt/Linux-Part
    Dec 31 16:00:12 NAS user.info hotplug[82]: USB vfat fs at /dev/discs/disc0/part3 mounted on /tmp/mnt/Fat-Part
    Dec 31 16:00:13 NAS user.notice kernel: klogd started: BusyBox v1.14.4 (2009-10-18 22:08:28 EDT)
    Dec 31 16:00:13 NAS user.warn kernel: CPU revision is: 00029029
    Dec 31 16:00:13 NAS user.warn kernel: Primary instruction cache 16kB, physically tagged, 4-way, linesize 16 bytes.
    Dec 31 16:00:13 NAS user.warn kernel: Primary data cache 16kB, 2-way, linesize 16 bytes.
    Dec 31 16:00:13 NAS user.warn kernel: Linux version 2.4.37.6 (root@tomato) (gcc version 3.4.6) #1 2009-10-18 22:23:26 EDT
    Dec 31 16:00:13 NAS user.warn kernel: Setting the PFC to its default value
    Dec 31 16:00:13 NAS user.warn kernel: Determined physical RAM map:
    Dec 31 16:00:13 NAS user.warn kernel:  memory: 01000000 @ 00000000 (usable)
    Dec 31 16:00:13 NAS user.warn kernel: On node 0 totalpages: 4096
    Dec 31 16:00:13 NAS user.warn kernel: zone(0): 4096 pages.
    Dec 31 16:00:13 NAS user.warn kernel: zone(1): 0 pages.
    Dec 31 16:00:13 NAS user.warn kernel: zone(2): 0 pages.
    Dec 31 16:00:13 NAS user.warn kernel: Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
    Dec 31 16:00:13 NAS user.warn kernel: CPU: BCM5354 rev 3 pkg 0 at 240 MHz
    Dec 31 16:00:13 NAS user.warn kernel: Using 100.000 MHz high precision timer.
    Dec 31 16:00:13 NAS user.warn kernel: Calibrating delay loop... 197.83 BogoMIPS
    Dec 31 16:00:13 NAS user.info kernel: Memory: 14356k/16384k available (1417k kernel code, 2028k reserved, 100k data, 80k init, 0k highmem)
    Dec 31 16:00:13 NAS user.info kernel: Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
    Dec 31 16:00:13 NAS user.info kernel: Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
    Dec 31 16:00:13 NAS user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
    Dec 31 16:00:13 NAS user.info kernel: Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
    Dec 31 16:00:13 NAS user.warn kernel: Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
    Dec 31 16:00:13 NAS user.warn kernel: Checking for 'wait' instruction...  unavailable.
    Dec 31 16:00:13 NAS user.warn kernel: POSIX conformance testing by UNIFIX
    Dec 31 16:00:13 NAS user.warn kernel: PCI: no core
    Dec 31 16:00:13 NAS user.warn kernel: PCI: Fixing up bus 0
    Dec 31 16:00:13 NAS user.info kernel: Linux NET4.0 for Linux 2.4
    Dec 31 16:00:13 NAS user.info kernel: Based upon Swansea University Computer Society NET3.039
    Dec 31 16:00:13 NAS user.warn kernel: Initializing RT netlink socket
    Dec 31 16:00:13 NAS user.warn kernel: Starting kswapd
    Dec 31 16:00:13 NAS user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
    Dec 31 16:00:13 NAS user.info kernel: devfs: boot_options: 0x1
    Dec 31 16:00:13 NAS user.info kernel: squashfs: version 3.0 (2006/03/15) Phillip Lougher
    Dec 31 16:00:13 NAS user.warn kernel: pty: 256 Unix98 ptys configured
    Dec 31 16:00:13 NAS user.info kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
    Dec 31 16:00:13 NAS user.info kernel: ttyS00 at 0xb8000300 (irq = 3) is a 16550A
    Dec 31 16:00:13 NAS user.info kernel: ttyS01 at 0xb8000400 (irq = 3) is a 16550A
    Dec 31 16:00:13 NAS user.warn kernel: HDLC line discipline: version $Revision: 3.7 $, maxframe=4096
    Dec 31 16:00:13 NAS user.info kernel: N_HDLC line discipline registered.
    Dec 31 16:00:13 NAS user.info kernel: PPP generic driver version 2.4.2
    Dec 31 16:00:13 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x400000 for the chip at 0x0
    Dec 31 16:00:13 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
    Dec 31 16:00:13 NAS user.debug kernel: Physically mapped flash: Found an alias at 0xc00000 for the chip at 0x0
    Dec 31 16:00:13 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
    Dec 31 16:00:13 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x1400000 for the chip at 0x0
    Dec 31 16:00:13 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
    Dec 31 16:00:13 NAS user.debug kernel: Physically mapped flash: Found an alias at 0x1c00000 for the chip at 0x0
    Dec 31 16:00:13 NAS user.notice kernel:  Amd/Fujitsu Extended Query Table v1.1 at 0x0040
    Dec 31 16:00:13 NAS user.notice kernel:  Flash Id: Vendor: 0x00c2 Device: 0x00a8
    Dec 31 16:00:13 NAS user.notice kernel: number of CFI chips: 1
    Dec 31 16:00:13 NAS user.notice kernel: cfi_cmdset_0002: Disabling fast programming due to code brokenness.
    Dec 31 16:00:13 NAS user.notice kernel: Flash device: 0x400000 at 0x1c000000
    Dec 31 16:00:13 NAS user.notice kernel: Creating 5 MTD partitions on "Physically mapped flash":
    Dec 31 16:00:13 NAS user.notice kernel: 0x00000000-0x00020000 : "pmon"
    Dec 31 16:00:13 NAS user.notice kernel: 0x00020000-0x003f0000 : "linux"
    Dec 31 16:00:13 NAS user.notice kernel: 0x000c8cdc-0x003d0000 : "rootfs"
    Dec 31 16:00:13 NAS user.notice kernel: 0x003d0000-0x003f0000 : "jffs2"
    Dec 31 16:00:13 NAS user.notice kernel: 0x003f0000-0x00400000 : "nvram"
    Dec 31 16:00:13 NAS user.err kernel: sflash: found no supported devices
    Dec 31 16:00:13 NAS user.info kernel: Initializing Cryptographic API
    Dec 31 16:00:13 NAS user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
    Dec 31 16:00:13 NAS user.info kernel: IP Protocols: ICMP, UDP, TCP, IGMP
    Dec 31 16:00:13 NAS user.info kernel: IP: routing cache hash table of 16384 buckets, 128Kbytes
    Dec 31 16:00:13 NAS user.info kernel: TCP: Hash tables configured (established 1024 bind 2048)
    Dec 31 16:00:13 NAS user.info kernel: Linux IP multicast router 0.06 plus PIM-SM
    Dec 31 16:00:13 NAS user.warn kernel: ip_conntrack version 2.1 (16384 buckets, 8192 max) - 332 bytes per conntrack
    Dec 31 16:00:13 NAS user.warn kernel: ip_tables: (C) 2000-2002 Netfilter core team
    Dec 31 16:00:13 NAS user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    Dec 31 16:00:13 NAS user.info kernel: NET4: Ethernet Bridge 008 for NET4.0
    Dec 31 16:00:13 NAS user.info kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
    Dec 31 16:00:13 NAS user.info kernel: All bugs added by David S. Miller <davem@redhat.com>
    Dec 31 16:00:13 NAS user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly.
    Dec 31 16:00:13 NAS user.info kernel: Mounted devfs on /dev
    Dec 31 16:00:13 NAS user.info kernel: Freeing unused kernel memory: 80k freed
    Dec 31 16:00:13 NAS user.warn kernel: Algorithmics/MIPS FPU Emulator v1.5
    Dec 31 16:00:13 NAS user.warn kernel: ip_conntrack_pptp version 1.9 loaded
    Dec 31 16:00:13 NAS user.warn kernel: ip_nat_pptp version 1.5 loaded
    Dec 31 16:00:13 NAS user.warn kernel: ip_conntrack_rtsp v0.01 loading
    Dec 31 16:00:13 NAS user.warn kernel: ip_nat_rtsp v0.01 loading
    Dec 31 16:00:13 NAS user.debug kernel: PCI: Setting latency timer of device 00:01.0 to 64
    Dec 31 16:00:13 NAS user.warn kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 4.150.10.29
    Dec 31 16:00:13 NAS user.debug kernel: PCI: Setting latency timer of device 00:05.0 to 64
    Dec 31 16:00:13 NAS user.warn kernel: eth1: Broadcom BCM4318 802.11 Wireless Controller 4.150.10.29
    Dec 31 16:00:13 NAS user.warn kernel: tomato_ct.c [Oct 18 2009 22:28:25]
    Dec 31 16:00:13 NAS user.info kernel: usb.c: registered new driver usbdevfs
    Dec 31 16:00:13 NAS user.info kernel: usb.c: registered new driver hub
    Dec 31 16:00:13 NAS user.debug kernel: PCI: Setting latency timer of device 00:03.1 to 64
    Dec 31 16:00:13 NAS user.info kernel: ehci_hcd 00:03.1: PCI device 14e4:471a
    Dec 31 16:00:13 NAS user.info kernel: ehci_hcd 00:03.1: irq 6, pci mem b8003800
    Dec 31 16:00:13 NAS user.info kernel: usb.c: new USB bus registered, assigned bus number 1
    Dec 31 16:00:13 NAS user.info kernel: ehci_hcd 00:03.1: USB 0.0 enabled, EHCI 1.00, driver 10 Dec 2004/2.4
    Dec 31 16:00:13 NAS user.info kernel: hub.c: USB hub found
    Dec 31 16:00:13 NAS user.info kernel: hub.c: 2 ports detected
    Dec 31 16:00:13 NAS user.info kernel: SCSI subsystem driver Revision: 1.00
    Dec 31 16:00:13 NAS user.info kernel: Initializing USB Mass Storage driver...
    Dec 31 16:00:13 NAS user.info kernel: usb.c: registered new driver usb-storage
    Dec 31 16:00:13 NAS user.info kernel: USB Mass Storage support registered.
    Dec 31 16:00:13 NAS user.info kernel: hub.c: new USB device 00:03.1-1, assigned address 2
    Dec 31 16:00:13 NAS user.info kernel: hub.c: USB hub found
    Dec 31 16:00:13 NAS user.info kernel: hub.c: 4 ports detected
    Dec 31 16:00:13 NAS user.info kernel: Journalled Block Device driver loaded
    Dec 31 16:00:13 NAS user.info kernel: usb.c: registered new driver usblp
    Dec 31 16:00:13 NAS user.info kernel: printer.c: v0.13: USB Printer Device Class driver
    Dec 31 16:00:13 NAS user.info kernel: hub.c: new USB device 00:03.1-1.2, assigned address 3
    Dec 31 16:00:13 NAS user.debug kernel: vlan0: dev_set_promiscuity(master, 1)
    Dec 31 16:00:13 NAS user.info kernel: device eth0 entered promiscuous mode
    Dec 31 16:00:13 NAS user.info kernel: device vlan0 entered promiscuous mode
    Dec 31 16:00:13 NAS user.info kernel: scsi0 : SCSI emulation for USB Mass Storage devices
    Dec 31 16:00:13 NAS user.warn kernel:   Vendor: Generic   Model: External          Rev: 2.10
    Dec 31 16:00:13 NAS user.warn kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
    Dec 31 16:00:13 NAS user.warn kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
    Dec 31 16:00:13 NAS user.warn kernel: SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
    Dec 31 16:00:13 NAS user.info kernel: Partition check:
    Dec 31 16:00:13 NAS user.info kernel:  /dev/scsi/host0/bus0/target0/lun0:<6>device eth1 entered promiscuous mode
    Dec 31 16:00:13 NAS user.debug kernel: vlan1: dev_set_promiscuity(master, 1)
    Dec 31 16:00:13 NAS user.info kernel: device vlan1 entered promiscuous mode
    Dec 31 16:00:13 NAS user.info kernel: vlan1: attempt to add interface with same source address.
    Dec 31 16:00:13 NAS user.warn kernel:  p1 p2 p3
    Dec 31 16:00:13 NAS user.debug kernel: WARNING: USB Mass Storage data integrity not assured
    Dec 31 16:00:13 NAS user.debug kernel: USB Mass Storage device found at 3. Host: 0
    Dec 31 16:00:13 NAS user.info kernel: br0: port 3(vlan1) entering learning state
    Dec 31 16:00:13 NAS user.info kernel: br0: port 2(eth1) entering learning state
    Dec 31 16:00:13 NAS user.info kernel: br0: port 1(vlan0) entering learning state
    Dec 31 16:00:13 NAS user.info kernel: br0: port 3(vlan1) entering forwarding state
    Dec 31 16:00:13 NAS user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:13 NAS user.info kernel: br0: port 2(eth1) entering forwarding state
    Dec 31 16:00:13 NAS user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:13 NAS user.info kernel: br0: port 1(vlan0) entering forwarding state
    Dec 31 16:00:13 NAS user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:13 NAS user.info kernel: br0: port 3(vlan1) entering disabled state
    Dec 31 16:00:13 NAS user.warn kernel: vlan1: Setting MAC address to  00 24 8c 00 a6 4a.
    Dec 31 16:00:13 NAS user.info kernel: br0: port 3(vlan1) entering learning state
    Dec 31 16:00:13 NAS user.info kernel: br0: port 3(vlan1) entering forwarding state
    Dec 31 16:00:13 NAS user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:13 NAS user.warn kernel: SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
    Dec 31 16:00:13 NAS user.info kernel:  /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3
    Dec 31 16:00:13 NAS user.info kernel: EXT3-fs: recovery starting.
    Dec 31 16:00:13 NAS user.info kernel: kjournald starting.  Commit interval 1 seconds
    Dec 31 16:00:13 NAS user.warn kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
    Dec 31 16:00:13 NAS user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
    Dec 31 16:00:13 NAS user.info kernel: EXT3-fs: recovery complete.
    Dec 31 16:00:13 NAS user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
    Dec 31 16:00:13 NAS user.warn kernel: MSDOS FS: IO charset utf8
    Dec 31 16:00:14 NAS cron.err crond[232]: crond (busybox 1.14.4) started, log level 9
    Dec 31 16:00:17 NAS user.info init[1]: Tomato 1.25.8736 ND USB Ext
    Dec 31 16:00:17 NAS user.info init[1]: Asus WL-520GU
    Dec 31 16:00:21 NAS user.info kernel: Adding Swap: 1052216k swap-space (priority -1)
    Dec 31 16:00:48 NAS daemon.err nmbd[247]: [1969/12/31 16:00:48, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(405)
    Dec 31 16:00:48 NAS daemon.err nmbd[247]:   *****
    Dec 31 16:00:48 NAS daemon.err nmbd[247]:   
    Dec 31 16:00:48 NAS daemon.err nmbd[247]:   Samba name server NAS is now a local master browser for workgroup WORKGROUP on subnet 192.168.10.2
    Dec 31 16:00:48 NAS daemon.err nmbd[247]:   
    Dec 31 16:00:48 NAS daemon.err nmbd[247]:   *****
     
  52. teddy_bear

    teddy_bear Network Guru Member

    freddyspam,
    As you may have noticed, the wireless driver has been changed in v35 to version 4.150.10.29 to resolve connectivity issues experienced by some wl500gpv2 owners. There was a big discussion about that around pages 105-110, and Ray and I posted different versions of wireless driver module to try here.

    I would like to know if the driver 4.150.10.29 works for you or not when used in v34. Please try that (the instructions are in the Ray's archive), and let me know the results. Also - what is the main router you're connecting to, and what firmware you're running on it?

    EDIT: Looks like you're using the "no lock" usb mode (usb_nolock=1). Could you also try to set it back to normal "locking" mode in v36 (nvram set usb_nolock=0; nvram commit; reboot), and see if your drives still get mounted? Another thing you can try is to explicitly set both - Receive and Transmit - Antennas to "B" from "Auto" in "Advanced -> Wireless". This may or may not make any difference...
     
  53. easy-1

    easy-1 Guest

    It's nice with v36. But rtorrent can't work with ntfs-3g.
     
  54. Anzial

    Anzial Addicted to LI Member

  55. teddy_bear

    teddy_bear Network Guru Member

    easy-1,
    Yes, rtorrent is only compatible with fuse/ntfs-3g in kernels 2.6.26 or later. Use different torrent client, or don't use NTFS partition for torrenting.

    Anzial,
    All fixes are listed in the post announcing v36. I don't think there was any change that could affect the traffic or the logging.
     
  56. TexasFlood

    TexasFlood Network Guru Member

    Anzial is getting a significant amount of broadcast traffic. The log sample he posted was -all- broadcast traffic. I actually hadn't looked at my WAN side traffic for a while so checked it earlier today. At least for the moment, my router WAN is fortunately very quiet, no broadcasts, no malicious probes like I saw years ago. Anzial mentioned that he was trying to track ISP bandwidth and of course this broadcast traffic, which I would think is not counted against any ISP cap, is skewing the measurement. I don't have the skill or time to figure out how to ignore the broadcast traffic in measuring WAN throughput.
     
  57. Anzial

    Anzial Addicted to LI Member

    Well, maybe ISP fixed whatever issue they were having lol :)
     
  58. freddyspam

    freddyspam Addicted to LI Member

    Update:
    My main router is a Dlink-825 on stock firmware.

    I flashed v34 on the 520gu. Checked that the wireless/internet connection was working. I then removed the wireless drivers. Checked and the wireless/internet was down. I then installed 4.150.10.29. Afterwords, the wireless connection reestablished itself and the internet connect was fine. So I guess it's is not solely a drivers issue.

    I then flashed v36. I set usb_nolock to 0. Rebooted, and the drives mounted just fine.

    I then set both the Receive and Transmit Antennas to B. After I clicked save, the swap partition disassociated for some reason. I checked the wireless and it still was not working. I then rebooted. All the drives mounted again, and the swap was working again, but the wireless was a no go. The signal quality really bounces around from 0 to 45.

    Still on v36, I removed the wireless drivers and tried wl_4_150_10_5.o and then wl_4_158_4_0.o. No change in wireless behavior. But every time I saved the wireless settings in the gui, it would disconnect all the drives and I would have to remount them again by hand or reboot. I don't remember this being the norm but maybe I'm mistaken.
     
  59. teddy_bear

    teddy_bear Network Guru Member

    freddyspam,
    Yep, looks like it's not a driver issue, since the same version - 4.150.10.29 - worked for you in v34. Something else is causing the problem. Have you tried to reset the nvram yet just in case? By the way - what mode is your Asus set to - "wireless client", "ethernet bridge" or "wds"?

    When changing wireless settings, Tomato restarts all services including USB. If your drives didn't remount automatically it means at leas one of the partitions could not be unmounted on restart (probably because it was busy). Interesting that nobody noticed it so far... I'll add a workaround for this.

    And you can't test other WL drivers in v35-36 since they were compiled for v34 using older toolchain, so they won't load in v36. If you want to try wl_4_158_4_0.o with v36, I can compile it for you - but based on your tests I don't think it will work...
     
  60. freddyspam

    freddyspam Addicted to LI Member

    That explains why it was freaking out when I tried to load them. I just finished reading over all of the changes you've made. Wow, you've been busy. If you would like to compile the driver, I'll test it.

    I am using the router in wireless ethernet bridge mode. Under v36, I did try resting the nvram (complete erase) and reconfiguring just the wireless to the same wireless settings. That's when it really started acting weird. The computer wired to the router could no longer access it or get an IP. I had to use the asus restoration tool to flash v34 onto it. The v34 worked perfectly right away even though it was using the same settings that caused the v36 firmware to lock out all access. The v34 firmware gave the wired computer access and connected to the main router flawlessly. I tried this twice, once with the dhcp server on the 520gu on, and once with it set to off (since the main router should be the one assigning the IP anyway). The outcome was exactly the same with the v34 firmware working, while the v36 locking out all access.

    I don't know if it'll matter but my wireless security is WPA-AES and I'm using mixed b-g mode. I know security settings are usually the culprit when setting up a wireless ethernet bridge, but I know the settings are correct because of my success with the v34 firmware.
     
  61. mstombs

    mstombs Network Guru Member

    teddy_bear,

    thanks for the special non-usb release, and the full source with new toolchain - that gives me lots of jffs to use!

    A couple of comments/questions about compiling the source on my PC (Ubuntu 64 bit 9.10 beta), yes - bleeding edge and instability... but it is supposed to be released in 10 days..

    1. In contrast to stock tomato have to use "dash" as default shell, or else config doesn't get copied correctly and configure complains and prompts...

    2. The Makefile for www, uses a "for" syntax which my "dash" doesn't like, changing the last loop to same syntax as earlier in the file to "for F in $(wildcard *.js *jsx); do \" fixes that.

    3. You must be building as root (which I do not do anymore!) - my built images were bigger, and found that "rc nvram mssl mdu rstats ntpc httpd" were not being stripped, because they were installed readonly first. Changing the makefiles to strip before installing fixes this, and it is reassuring the images end up same kB as yours, but haven't yet tried the image incase something else is broken!
     
  62. Bill_S

    Bill_S Network Guru Member

    I sorry but I am confused, I have a WRT54SLGS currently running Tomato 1.25.7 but I would like to try this firmware with USB support. I went the site that had the downloads but based on what I read, I could not tell which one to download. I would like the full version with the extras. According to the first page there are only four different flavors but I see 8, I think?
    I would like the one described as EXTRAS on the first posting. Would someone be kind enough to tell me which of these listed firmwares meets my needs?

    Here is the list I see on the download page:
    extras.tar.gz
    samba_extra_codepages.tar.gz
    tomato-1.25-ND-8736.rar
    tomato-1.25-ND-USB-8634-vpn3.4.rar
    tomato-1.25-NDUSB-8736-Ext.rar
    tomato-1.25-NDUSB-8736-Lite.rar
    tomato-1.25-NDUSB-8736-NoCIFS.rar
    tomato-1.25-NDUSB-8736-Std.rar

    Thanks for the help
     
  63. teddy_bear

    teddy_bear Network Guru Member

    mstombs,
    Thanks for sharing your findings...

    I too use non-standard default shell in Ubuntu - I think it was you who directed me to do that a year ago, when I first tried to compile Tomato ;)...

    Yes, I noticed just recently that some executables are not getting stripped when building as non-root, but have not got around fixing the makefile yet. Mostly because I do build it as root now - for cosmetic reasons - to have "root" listed as an owner of all directories in Tomato instead of "1000" (user id of my non-root Ubuntu user).

    I can make changes you mentioned to the Makefile but I guess we'll need to let Jon know about them too so he can fix it for stock Tomato.

    Bill_S,
    The file that has "Ext" in the name is the "Extras" build.
     
  64. Bill_S

    Bill_S Network Guru Member

    Thanks teddy, I am looking forward to trying it.
     
  65. Bill_S

    Bill_S Network Guru Member

    I downloaded the file entitled tomato-1.25-NDUSB-8736-Ext.rar and extracted the compressed file but when I attempted to update the router I received a message saying that the file was incompatible. Is there something else I need to do with the file?
    Thanks
     
  66. Bill_S

    Bill_S Network Guru Member

    Sorry, please disregard, I installed the stock firmware prior to doing the update, once I reinstalled Tomato the update worked fine. Sorry to have troubled anyone.
     
  67. madduru

    madduru Addicted to LI Member

    With v36, Apple iphone can not connect as a wireless client.

    teddy_bear,
    Just as an fyi...I have upgraded my WL520GU with the latest v36. With v34, my iPhone was able to connect seemlessly, now it is asking me to enter userid/password. The difference between now and then was:
    - Then I had flashed my router with v34 "std" version
    - Now I have flashed my router with v36 "ext" version.

    Other than upgrading to v36 through Tomato GUI I did not perform any additional tasks. Your post mentioned that there were known issues with wireless client on v36. I thought I would let you know.

    Thanks.

     
  68. Cyrix

    Cyrix Addicted to LI Member

    Hi Teddy_Bear, i flashed your new build v1.25.8736 ND USB Ext to my Asus WL-500gp V1 and when I started rtorrent I found my log is full with this:

    user.notice kernel: __alloc_pages: 0-order allocation failed (gfp=0x20/0)

    I have never seen this row in your previous bilds. Could you tell me what this row means, and what can I do to avoid it? Thx
     
  69. jnappert

    jnappert LI Guru Member

    Hi Teddy_Bear.

    I was very happy to see the none usb-builds since i have 7 WRT54GLs in WDS connected to my ASUS WL 500gp. I updated to ND 36 without USB to have the same wireless drivers on every device.

    On the devices that are connected between two others, the log is filled with:
    Oct 20 21:33:27 unknown user.info kernel: br0: received tcn bpdu on port 2(wds0.2)
    Oct 20 21:33:27 unknown user.info kernel: br0: topology change detected, sending tcn bpdu

    This happens every two seconds. The connection is established and working. The devices which are "end-points" and have only 1 WDS-link behave fine.

    A---WDS---B---WDS---C (occurs only at AP "B", "A" and "C" are fine)

    Note: I need to have STP (Spanning Tree Protocol) enabled. Disabling solves the issue but thats not realy a solution.
     
  70. shibby20

    shibby20 Network Guru Member

    i have "tablica v3" on tomato.
    http://openlinksys.info/forum/viewthread.php?forum_id=38&thread_id=7628
    It`s polish board, where i can watch DL/UL statistics, send message to users and block internet on MAC address.

    On v34 all work great. When i upgraded to v36 board not work. it was writed on haserl language. When i try to use haserl from optware, then board work but not correct.

    teddy_bear can you restore previous version of haserl?
     
  71. Anzial

    Anzial Addicted to LI Member

    any reason why v36 would hang the router? After 4-5 hours, with computers in sleep, my Asus 520GU with v36 appeared to be frozen - no internet connections. LEDs seemed to be on but I didn't look, I just cycled power and it came back alive. I just wonder if WAN broadcast traffic inundated the router and caused the hang... or is it just dying?
     
  72. teddy_bear

    teddy_bear Network Guru Member

    Cyrix,
    This message means that the kernel is running very low on memory. This will happen if you allow torrents to run unrestricted. It doesn't mean that the kernel will crach - but it may... The older kernel used in v34 and before simply did not output these warning messages into the syslog, the new one does.

    jnappert,
    The only "solution" I could google out for your issue was to turn off STP - which is not a solution for you... I PM'd you the test build to try...

    shibby20,
    I don't know what the "tablica" is, and I can't read Polish. But as fas as I understand, it's a set of CGI scripts. To run CGI script in my mod you don't need haserl - the support for CGI scripts is built into http daemon, you just need to place them into /www/user/cgi-bin directory - unless of course tablica uses some specific haserl extensions.
    As for haserl, I have no idea what version tablica uses. If it's an executable built for Tomato - it will not work in v35 and newer because of the toolchain update. Optware haserl should work, and if tablica doesn't work with it correctly, it's tablica's problem - ask the author to resolve it.

    Anzial,
    Of course there could be "reasons" why router hangs... Many of them... Any firmware version... And there's zero info in your post to help you. I.e. what does "no internet" mean? No connection from router to the cable/dsl modem? Or no connections from clients to the router (wired or/and wireless)? Were you able to access the router via ssh/telnet, or ping it? Did you have a chance to look at the logs? Guys - before posting questions, please think if there's any way to answer them ;)...
    And yes - very high traffic can cause the router to hang.
     
  73. toolbox

    toolbox Addicted to LI Member

    Hi Teddy_Bear, how do I setup "Allow multiple MAC addresses per device for static leases."? When I try to have two entries (one MAC address) per entry with the same static IP for my laptop, GUI rejects the 2nd one indicateing IP address is duplicated. I don't see a way to enter more than one MAC per entry under static DHCP.
    Thank you.
     
  74. teddy_bear

    teddy_bear Network Guru Member

    toolbox,
    This feature is copied over from VPN mod. You need to create separate entries for each MAC - but the ip address and the host name fields must be identical.

    This will change when Tomato 1.26 is out - Jon has implemented the same functionality differently.
     
  75. Anzial

    Anzial Addicted to LI Member

    Sorry, I was in a rush, so I just rebooted the router without investigating it much (lol, I didn't even look at status LEDs). The reason I asked, it never happened to me before lol... so I guess it's more or less regular thing and I should've looked into it. AFAIK, there was no way to access the router, any web-address gave me 'timeout' message, including the router admin access (so, no logs either), and my computer was connected via ethernet.

    BTW, yesterday wireless stopped working for no apparent reason (i.e. network status on the router shows it's on but it's not found by my wireless devices). I fixed it by turning off and on from the status overview page on the router. It also happened for the first time and with v36 firmware. The wireless in secure mode (WPA2 Personal (PSK) + TKIP / AES) but it was like there was no signal at all although like I said, I fixed it from the admin account without rebooting the router.
     
  76. shibby20

    shibby20 Network Guru Member

    i have to downgrade to v34 :/

    on v34 board v3 (tablica v3) work correctly. this version is very stable and have everything what i want :)
     
  77. teddy_bear

    teddy_bear Network Guru Member

    shibby20,
    Sure, I'm glad v34 is working good for you, and supports "tablica" you're using :)... By the way, what does it do, and is there an English version of it?
     
  78. shibby20

    shibby20 Network Guru Member

    this is a news board. you can send message to users, you can block internet access, you see, who is online, you see message delivery status. yes, board is also english version. Unfortunately news board is still alfa version and has lot of bugs but works :)

    2 picture
    http://update.groov.pl/board1.jpg
    http://update.groov.pl/board2.jpg

    this is board without minihttpd
    http://update.groov.pl/board_nohttpd.tar.gz

    to run you have to install from optware gawk and minihttpd. unpack archive to /opt/share and run

    /opt/sbin/mini_httpd -p 8000 -u root -c "**.cgi" -d /opt/share/board
    /opt/share/board/board/messages.sh
    /opt/share/board/board/blocked.sh
    iptables -A INPUT -p tcp --dport 8000 -j ACCEPT

    www access http://ip:8000/board :)

    change login:password:
    http://home.flash.net/cgi-bin/pw.pl
    and replace new login:password in /opt/share/board/board/.htpasswd

    autor: tabor
    autor profile: http://openlinksys.info/profile.php?lookup=3628
     
  79. infernus

    infernus Guest

    Teddy Bear, I have a quick question. I am very interested in building my own firmware mod. I LOVE yours, but have no need for USB support, since I'm using a WRT54G. <s>I was wondering if you would be able to provide me with a sample .config file for building the mips kernel for the router? I'd definitely like to upgrade to the latest in the 2.4.x series and have never cross-compiled for the MIPSel architecture.</s> And, less important, if you happen to have any links to articles regarding the compilation (tips on adding features, proper versions to use, etc). I would greatly appreciate any info/help provided. Thank you in advance for your time and consideration. Keep up the good work.

    *EDIT* I feel like an idiot. I found the .config along with the linux sources in the latest git tarball. But, I would still love it if you had any links to articles or howtos. I basically want to combine the best features of yours with the best features of Victek's mod, but I want to try to make a smaller image for my own router to preserve more jffs2 space. Thanks again.
     
  80. mstombs

    mstombs Network Guru Member

    see http://soft-haus.com/blog/2009/04/1...-in-ubuntu-linux-810-beefing-up-your-wrt54gl/ for a guide to building Tomato, but my problems are always down to paths and host build tools and shells. I posted earlier my specific issues on my current PC setup, but the GIT download is excellent, easier than building stock Linksys or unmodified Tomato - its a pretty steep learning curve! Read all the comments - and if you use downloaded scripts make sure they are saved with unix not windows line endings!
     
  81. ghostknife

    ghostknife Addicted to LI Member

    Anyone having problem with DDNS on v.8736? Mine just keeps having error like:
    Friday, 23 October 2009 8:58:28 PM:
    Unknown error (-1).
    (1/3: Automatically retrying in 16 minutes)

    This is on DNS-O-Matic and OpenDNS, using the External IP Checker (because WAN is Disabled).

    EDIT: It hasn't updated at DNS-O-Matic since [Oct 21, 2009 8:45 pm] which I think is when i flashed latest build, can't remember exact time.
    EDIT2: Reconfigured as WAN PPPoE, DDNS set to [Use WAN IP...(recommended)], same result. Have checked passwords are correct, re-entered etc....so dunno don't think it's me.
     
  82. teddy_bear

    teddy_bear Network Guru Member

    Yep... Known issue :frown:. Doesn't work in v36 when using SSL connections because of updated MatrixSSL library. Fixed if you rebuild from git now, but I didn't publish another build yet...
     
  83. ghostknife

    ghostknife Addicted to LI Member

    Was going nuts trying to get it to work. By the time i figure out how to build from git it will be xmas, so i'll wait for yours :)
     
  84. swwitch

    swwitch Addicted to LI Member


    hello, :)
    i try to sturt up usb_modeswitch ( LD_LIBRARY_PATH=/tmp/mnt/usb:$LD_LIBRARY_PATH /tmp/mnt/usb/usb_modeswitch)

    but receives message "can't resolve symbol 'pthread_mutex_init'" :sad:
     
  85. teddy_bear

    teddy_bear Network Guru Member

    Do not set LD_LIBRARY_PATH! Who told you to do so ;)?
    Instead, follow my direction here to place usblib files correctly. Also please note that it will only work in v36 or later in USB-enabled builds - previous build or non-USB builds don't have symbols needed in libc.
     
  86. micko_escalade

    micko_escalade Network Guru Member

    Hi,

    My USB flash drive does not auto mount after router reboot. I need to physically remove the drive and plug it back in then it finally appears under
    USB and NAS > USB Support > Attached Devices
    Any solution for this?
    Screenshot > http://i37.tinypic.com/2zxxue0.jpg
     
  87. teddy_bear

    teddy_bear Network Guru Member

    Not enough info to say anything...
     
  88. micko_escalade

    micko_escalade Network Guru Member

    I'm not trying to be smart a.. but what other info would be helpful?
    All what I see once flash drive is plugged under Attached Devices
    is this :
    Type Host Vendor Description Mounted?
    Storage 0 Unknown Unknown Yes
    [ Unmount ]
    Partition 'USB DISK' vfat is mounted on /tmp/mnt/USB DISK

    http://i35.tinypic.com/211vuye.jpg
     
  89. DCX2

    DCX2 Addicted to LI Member

    Hi teddy_bear, first I want to thank you for this awesome firmware. Second, I would like to make use of the scsi-stop ability, but I seem to be having difficulty.

    If I call scsi-stop, my disk won't automatically start up. However, if I call scsi-stop, and then scsi-start before trying to access it, rather than immediately spinning back up it will automatically start up whenever I go to access it next. So I was going to modify the auto-shutdown script from the page linked to from the build 19 info and add the call to scsi-start...

    This is where the difficulty comes in. I can't seem to figure out how to get the automatic script saved onto the router. When I telnet in and try to cat > scsi-auto-shutdown.sh, it complains about being read-only.

    I'm a total novice with tomato, and I'm sure there's something brain-dead simple that I'm clueless about. FYI, here's my setup. Asus 520-GU, the most recent no CIFS build, external USB enclosure using the JMicron JM20336 chip.
     
  90. teddy_bear

    teddy_bear Network Guru Member

    What firmware version are you running? What's in your system log after reboot when drive doesn't get mounted? Is it the problem with this particular flash drive, or with any other drive as well? Do you have any custom scripts running at startup?
    By "reboot" did you mean the reboot from the web gui, or powercycling the router, or both?...
     
  91. teddy_bear

    teddy_bear Network Guru Member

    These instructions are for Oleg's firmware, so you need to make some adjustments for Tomato... Do not try to save the script to /usr/local/sbin directory - it's read-only. Instead, use jffs partition - you should have plenty of JFFS space on your Asus with no-CIFS build. So save the scsi-stop.sh script in /jffs directory (make sure you enable JFFS in the Web GUI), and add a line to your "Init" script to start it on reboot:
    /jffs/scsi-stop.sh /dev/scsi/host0/bus0/target0/lun0/disc &
    Also, replace
    SCSISTOP=/usr/local/sbin/scsi-stop
    line in the script by the following:
    SCSISTOP=scsi-stop
     
  92. micko_escalade

    micko_escalade Network Guru Member

    - I'm running your latest version tomato-1.25-NDUSB-8736-Std
    - I only have this 256MB drive and don't have any other at the moment.
    - Rebooting thru the web gui or powercycling creates same log.
    - No other scripts.

    Here's the full log after powercycling http://textsnip.com/f126fc (ie. auto mount does not occur)

    This is what is added to the log after unplugging and plugging back in:
    Code:
    Oct 24 19:24:23 tomato user.info kernel: usb.c: USB disconnect on device 00:03.1-1 address 2
    Oct 24 19:25:01 tomato user.info kernel: hub.c: new USB device 00:03.1-1, assigned address 3
    Oct 24 19:25:03 tomato user.info kernel: scsi0 : SCSI emulation for USB Mass Storage devices
    Oct 24 19:25:03 tomato user.warn kernel:   Vendor:           Model:                   Rev: 1100
    Oct 24 19:25:03 tomato user.warn kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
    Oct 24 19:25:03 tomato user.warn kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
    Oct 24 19:25:03 tomato user.warn kernel: SCSI device sda: 506880 512-byte hdwr sectors (260 MB)
    Oct 24 19:25:03 tomato user.warn kernel: sda: Write Protect is off
    Oct 24 19:25:03 tomato user.info kernel: Partition check:
    Oct 24 19:25:03 tomato user.info kernel:  /dev/scsi/host0/bus0/target0/lun0: p1
    Oct 24 19:25:03 tomato user.debug kernel: WARNING: USB Mass Storage data integrity not assured
    Oct 24 19:25:03 tomato user.debug kernel: USB Mass Storage device found at 3. Host: 0
    Oct 24 19:25:03 tomato user.debug hotplug[386]: Waiting for device /proc/bus/usb/001/003 [INTERFACE=8/6/80 PRODUCT=90c/1000/1100] to settle before scanning
    Oct 24 19:25:06 tomato user.warn kernel: SCSI device sda: 506880 512-byte hdwr sectors (260 MB)
    Oct 24 19:25:06 tomato user.warn kernel: sda: Write Protect is off
    Oct 24 19:25:06 tomato user.info kernel:  /dev/scsi/host0/bus0/target0/lun0: p1
    Oct 24 19:25:06 tomato user.warn kernel: MSDOS FS: IO charset utf8
    Oct 24 19:25:06 tomato user.warn kernel: MSDOS FS: Using codepage 437
    Oct 24 19:25:06 tomato user.info hotplug[386]: USB vfat fs at /dev/discs/disc0/part1 mounted on /tmp/mnt/USB DISK
    
    
     
  93. teddy_bear

    teddy_bear Network Guru Member

    micko_escalade,
    Maybe a "bad" drive - for some reason it's not recognized by the SCSI system on startup. Normally you should see these in log:
    Code:
    Oct 24 19:25:03 tomato user.warn kernel:   Vendor:           Model:                   Rev: 1100
    Oct 24 19:25:03 tomato user.warn kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
    not only when you replug the drive, but on startup too.

    It may help if you uncheck UHCI and OHCI support, and only use USB 2.0 (which is backward compatible with 1.1). You only need to load USB 1.1 driver if some of your devices don't work without it. In any case, do not load both - choose either
    OHCI or UHCI depending on what works for your hardware.

    By the way what is your WAN type set to on "Basic -> Network" page?
     
  94. DCX2

    DCX2 Addicted to LI Member

    Thanks for your reply! That was quite an awesome reply.

    I couldn't find awk, so I had to modify the script a bit more to make it work. Thankfully, grep only returns one line for me, so I managed to come up with an awk-less solution. However, a more robust solution is desirable, in case there are additional hard drives added. Is there a way to add awk? Somehow put it in /jffs? Is there a replacement (sed..?)?

    Here is the draft script I have right now. I added your changes, removed the awk stuff, changed /bin/true to true, added scsi-start, and changed the cooltime to 10 minutes instead of 20. I have tested it by using a watt-meter; it goes from 9W to 4W when the disk spins down, and jumps back up once I start accessing the drive.

    Code:
    #!/bin/sh
    if /usr/bin/[ $# -ne 1 ]; then
            /bin/echo 1>&2 "Usage: $0 <device>"
            exit 1
    fi
    
    PERIOD=30
    BOUNDARY=600
    SCSISTOP=scsi-stop
    SCSISTART=scsi-start
    LOGFILE=/tmp/scsi-stop.log
    
    searchstr="disk_io:"
    
    str=`/bin/grep "$searchstr" /proc/stat`
    cooltime=0
    stopped=0
    
    while true; do
            /bin/sleep $PERIOD
            newstr=`/bin/grep "$searchstr" /proc/stat`
            if /usr/bin/[ "$newstr" = "$str" ]; then
                    cooltime=$(($cooltime + $PERIOD))
                    if /usr/bin/[ $cooltime -ge $BOUNDARY -a $stopped -eq 0 ]; then
                            $SCSISTOP $1
                            $SCSISTART $1
                            time=`/bin/date '+%b %e %H:%M:%S'`
                            /bin/echo "$time: Cooled down..." >> $LOGFILE
                            stopped=1
                    fi
            else
                    if /usr/bin/[ $cooltime -ne 0 ]; then
                            time=`/bin/date '+%b %e %H:%M:%S'`
                            /bin/echo "$time: Disk first used after $cooltime seconds" >> $LOGFILE
                    fi
                    cooltime=0
                    str=$newstr
                    stopped=0
            fi
    done
    
     
  95. teddy_bear

    teddy_bear Network Guru Member

    Yeah... Forgot about that... awk is only included in "Extras" build since it's rarely used, and takes quite a lot of space.
    But even the Extras build has ~64KB available for JFFS partition to store small files like scripts etc - so maybe you can jump to "Extras"...
     
  96. micko_escalade

    micko_escalade Network Guru Member

    Well guess what? :)
    Unchecking USB 1.1 Support (OHCI) and USB 1.1 Support (UHCI) solved my problem!!!
    Like you said USB 2.0 is backwards compatible with 1.1 so I won't worry about it.
    There I have DHCP.

    Do you recommend any particular brand of drives?
    I was thinking to get SanDisk 16GB will all be visible or it will be limited to FAT32 4GB?
     
  97. teddy_bear

    teddy_bear Network Guru Member

    Sure, it will all be visible. The single file size on FAT32 can't exceed 4GB, not the partition.
    No particular brand recommendation. I had success and failures with both - well known brand name and no-name - products.
     
  98. micko_escalade

    micko_escalade Network Guru Member

    Thanks for your help!
    Correct me if I'm wrong but if I format new 16GB drive in Ext3 then I should be able to have files larger then 4GB and should be able to store them from Win machine?

    I also noticed under Status > Overview
    is it normal to have that much free memory?
    Total / Free Memory 14.10 MB / 656.00 KB (4.54%)
    Asus WL-520GU
     
  99. teddy_bear

    teddy_bear Network Guru Member

    micko_escalade,
    Yes, you should be able to access files 4GB+ on Ext3 (actually, if it's a flash drive, format is as Ext2 instead to prolong the life of the drive), but remember - there are hardware limitations.

    USB speed is pretty low on these routers (especially on wl520gu), and transferring huge files can take all the resources of the router effectively killing your network, and it may not even be able to complete the transfer. I'm not saying that this is impossible - I successfully moved 2GB+ files over wired connection to/from USB drives attached to wl520gu - just warning you that this is not a full-blown NAS device.

    As for the memory usage - yes, it's normal with USB features and FTP/Samba activated. But to see the "real" picture, turn on the "Count cache memory as free memory" checkbox on "Administration -> Debugging" page.
     
  100. micko_escalade

    micko_escalade Network Guru Member

    Yeah, I'm aware that this is not a real server but its really cool to be able to store small files access them from any computer on the network and all of that without running a separate server.

    I thought I looked at every option but for some reason I missed that one. Now it makes more "sense" :)

    Thank You!
     

Share This Page