Current Prices (10/17/08):
ZipZoomFly [zipzoomfly.com]: $47.00 - $20 MIR = $27.00 with Free Shipping
Newegg [newegg.com]: $46.99 - $20 MIR = $26.99 with Free Shipping
Mwave [mwave.com]: $45.00 + ~$9 Shipping - $20 MIR = $34.00 Shipped


Tomato w/ USB printer support for the WL520GU:
This version has USB printer support that is plug and play. Just enable USB support in the GUI and your set. No need to install packaged and lunix commands like DD-WRT!
http://www.linksysinfo.org/forums...hp?t=60185

USB instructions for wl500g (alternative to dd-wrt) can be found here [wl500g.info]

Installing DD-WRT v24 with Printer Sharing:

Download DD-WRT v24 Eko SVN 10431 mini+USB from this link. [dd-wrt.com]
This build handles USB print serving with a few Linux commands and a little bit of Linux knowledge. All of the USB kernel modules necessary are already included but the p910nd print daemon isn't. Here's a link to the DD-WRT wiki page describing the specifics:
http://www.dd-wrt.com/wiki/index....v24_Stable

Specifically:

• use version 10431 or later - it resolves a USB 2.0 driver bug in the Broadcom chip
• use the _mini_usb version - it leaves JFFS room free for the print daemon
• enable JFFS
• disable USB 1.0
• disable USB 1.1
• enable USB 2.0
• enable USB printing

After you've configured everything, login to your router via telnet or ssh (whichever you chose when you set it up.) Create a new directory for the ipkg package installer, update the ipkg repository, then install the p910nd print daemon. These commands create the directory, update the repository, fetches it from the web, and installs it on the router.

mkdir -p /jffs/tmp/ipkg
ipkg update
ipkg install p910nd

Edit the print daemon startup script to correct the location of the defaults file. There's a note about this on the DD-WRT USB Printing wiki page. The script is missing the '/jffs' path defining the defaults file:

cd /jffs/etc/init.d/
vi p910nd

and change this line (Putty VI Commands [wireplay.co.uk]):
DEFAULT=/etc/default/p910nd
to this:
DEFAULT=/jffs/etc/default/p910nd
then save the file

Finally, you need to add the print daemon startup to your router startup. Go to the Administration / Commands web page, and add the following command. Note this has an extra argument 'start' the wiki page was formerly missing:

/jffs/etc/init.d/p910nd start

Finally, click on 'Save Startup' so this command will execute every time your router restarts.


Installing Optware, Swap space, and Samba file sharing:
Refer to this tutorial in post # 205 for instructions on formatting your external USB hard disk drive, installing Optware, activating Linux swap space and installing Samba file sharing. Please post comments to the thread, and I'll revise the post as necessary.
(11/12/2008 - Added ipkg-opt install commands for busybox)
(11/17/2008 - Added second mkswap command from Optware)

11/15/2008 [fatal1ty44]
Note: there are a couple of things in the filesharing guide above that aren't so clear to newbs like me and could confuse you, so below is a short list of helpful hints to keep in mind as you read VorlonFog's amazing guide. These are problems that I ran into when I was following it, and resulted in the process taking me around 20 hours rather than 2 or 3, so hopefully this list helps someone!

1. First off, real basic tip, but for people not familiar with using the terminal, when the guide says to "start a terminal session to your router", just use the command "telnet 192.168.1.1" (without the quotes). Note that when it asks for the login id and password, for some reason it has to be the router's default "root" and "admin". So that means if you've changed the login or pw on your router, no combinations will let you in. If that's the case, go to your router and change it back to "root" and "admin" and then you should be able to connect via terminal. Don't ask me why that is...

2. For the paranoid, it's ok if when you use the command ipkg update your files start downloading from a different URL than the one the guide posted. My URLs contained things like "whiterussian" and "non-free", and it actually downloaded stuff from 3 locations rather than just the one. ITS OK! Everything will still work, it shouldn't really matter too much where it downloads from since those URLs are setup by default in the configuration file.

2. The next issue I hit literally had me ready to kill someone, and wasted probably about 5 hours to figure out (I'm a complete terminal newb). In the guide, when you get to the section about Acitivating Swap, the first step is to test your swap partition with busybox swapon command. Well, if you get an error that says "Invalid Argument", it means you need to use the busybox mkswap command first, AND THEN use the busybox swapon command. From my super duper limited understanding of linux and swaps, the mkswap command formats your little swap partition and prepares it for the swapon command. Why can some people get it working without using the mkswap command? I don't know, but apparently some people can since it was left out of the guide. So basically, instead of just pasting /opt/bin/busybox swapon /dev/scsi/host0/bus0/target0/lun0/part2 into your terminal session, paste /opt/bin/busybox mkswap /dev/scsi/host0/bus0/target0/lun0/part2 first, hit enter, then paste /opt/bin/busybox swapon /dev/scsi/host0/bus0/target0/lun0/part2. Note: this is only if your having the error "Invalid Argument"

3. This one is a real gem. Took me about 5 hours online to finally find the answer to this obscure bug. IF YOU ARE TRYING TO ACCESS YOUR SAMBA SHARE USING MAC OSX, READ THIS!. Apparently not many people try to do this, so finding any info on this is like digging for mushrooms on the moon. Mac OSX has a bug whereby Samba shares are not accessible through the finder. So unlike in WinXP where you would just connect straight to the drive with no username or pw required, OSX will ask you for a user/pw (even when you haven't set one) and no combination that you enter will work. This essentially denies you access to the drive: you'll get some errors like "Alias broken" or "Incorrect username and password". The solution to this can be found here http://ge.ubuntuforums.com/showth...p?t=917156. Its essentially three posts by one guy essentially talking to himself since no one decided to help the poor fella out, but he managed to solve the problem (since I did what he says in his last post and it works for me now). Basically, you need to make a couple modifications to your smb.conf file, the most important one being setting encrypt passwords = yes. After following his instructions, when you connect to your drive on OSX through the Finder >> Go >> Network, it still shows the screen that has your Name prefilled and a blank password, but this time around when you just click ok without touching anything it will actually connect and work rather than giving you an "Fix Alias" error msg. Awesome? I think so.

4. One last final hint for the newbs out there like me. When editing the smb.conf file using the vi smb.conf command, to start making changes use the arrow keys to get to where you want to go (the entire file isn't loaded at once, so you have to scroll down using the arrow keys to see the rest) and press a letter on your keyboard to get started editing. If nothing happens, press your key a couple times (the first key press basically lets the editor know that your not trying to type a command, and that your are trying to edit the file). To stop editing, hit esc and that will bring you out of "edit mode" and allow you to issue commands such as :wq which will save your changes and exit the smb.conf edit screen and bring you back to the command line. This may seem totally obvious to most people, but when I was following the guide, I first off tried to paste the entire block of code (including the vi smb.conf and the beginning and the :wq at the end) in one go, and that obviously didn't work. Then it took me a while to figure out that in order to navigate the damn file in terminal, you have to use arrow keys rather than using the scrollbar, since the entire file isn't actually slapped into the terminal at once. Then, I swear it took me an hour to figure out how to leave the damn thing and have it save my changes. I kept trying to type in :wq and pressing enter, without realizing that I first had to hit escape to get out of file editing mode and be able to issue editor commands.

Hopefully these tips helped you, again full credit goes to VorlonFog's amazing guide, this list of tips is only meant as a supplement to his guide if you get stuck. Except the part about using OSX with Samba. That part was pure genius


Loading DD-WRT to the router:
1. Download firmware (I used dd-wrt.v24_std_generic.bin)
2. Set the IP on your computer to 192.168.1.2 (255.255.255.0 for mask) (gateway is 192.168.1.1)
to do this go to Network Connections, right click on your LAN icon and go to properties
find 'Internet Protocol (TCP/IP)' go to properties and instead of 'Obtain an IP address automatically' change that to the addresses above
3. Open command prompt and type:
tftp -i 192.168.1.1 put "<path to your firmware file>"
but do not hit Enter yet
example: tftp -i 192.168.1.1 put "C:\Downloads\dd-wrt.v24-10431_NEWD_mini_usb.bin"
4. Power off the WL520GU
5. Press & hold the restore button, then power on
6. When the power LED flashes, release the reset button
7. Hit Enter in your command prompt window (step 3) within a few seconds of releasing the restore button
8. The transfer takes only a few seconds but give the router a minute or so to reboot (just to be sure)
9. Unplug the router, wait at least 10-15 seconds, then plug it back in
more info can be found here [dd-wrt.com]

DD-WRTv24 SP1 Special Version
Only download and use this if you fully understand what the Special version is.
If you do not, go browse the DD-WRT Store.
http://rapidshare.com/files/13280...rt-sp1.rar

This post can be edited by Slickdeals users to provide up-to-date information about developments of this thread based on user responses, and user findings. Feel free to add, change or remove information shown here as it becomes available.