Be sure to hit the “Save” then “Apply Settings” button on the bottom of the page.


Next we are going to go to the Administration section. Under Management if you have not already reset the default password to your router change the password here. You have enabled ssh and now someone can ssh to your router you want a strong password at a minimum.

Scroll down the page a little further and find the JFFS2 Support section. Here we want to Enable JFFS2 Support and also Enable Clean JFFS2 (Warning if you already have used JFFS2 and you select Enable Clean if will erase/format the disk partition) You only want to select this once when you first turn on JFFS2 in most cases)

Scroll to the bottom of the page and select “Save” then “Apply” Once the router is done you will not see how much space you have available for the JFFS2 filesystem, and note that the Clean JFFS2 is not set to Disable. Once the file system has been cleaned (Formatted) DD-WRT sets this radio button back to Disable as seen below.

I am not sure if it is needed or not but I rebooted my router as this point.

Now we are going to ssh into the router from another computer.

From a linux terminal window

$ ssh -l root 192.168.40.1


$ ssh -l root 192.168.40.1
DD-WRT v24-sp2 big (c) 2010 NewMedia-NET GmbH
Release: 11/21/10 (SVN revision: 15778)
root@192.168.40.1's password:

Enter your root password (Same as the admin password you set up on the web configuration page) and you should see the DD-WRT Logo on the screen and get a # root prompt.

OK so now lets check if everything we did so far is correct. lets see if the jffs2 filesystem is mounted in our environment. Enter the df command at the prompt.

# df

You should see something similar to

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 6016      6016         0 100% /
/dev/mtdblock/4          24960       904     24056   4% /jffs

The numbers are not important what is important is that the /jffs is shown and mounted.

Now we have a file system that we can write to which will allow us to save things and install additional software.

Now we need to update the package manager to get the latest versions of software that we can install.

# ipkg update

….......
Connecting to downloads.openwrt.org (78.24.191.177:80)
ipkg_download: ERROR: Failed to retrieve http://downloads.openwrt.org/backports/rc5/Packages, returning t
ipkg_update: Error downloading http://downloads.openwrt.org/backports/rc5/Packages to /jffs/usr/lib/ipkg/lists/backports

Notice that we received an error when trying to download updates from http://downloads.openwrt.org/backports/rc5/Packages to /jffs/usr/lib/ipkg/lists/backports

So we need to fix the ipkg system. If we look at the URL that failed in a browser there are no files in the rc5 section any more. After snooping around a bit I did find that there is a backports/0.9 section, so we need to point ipkg to the 0.9 folder in place of the rc5 folder.

The file that contains the configuration information for ipkg is at /etc/ipkg.conf which is a read only file system so we can not change it there. Instead we need to make a copy of it to the  jffs file system we now have mounted. The we can tell ipkg where to get its configuration file from with a shell variable.

# mkdir /jffs/etc
# cp /etc/ipkg.conf /jffs/ipkg.conf

We now need to edit our new ipkg.conf file to point to the 0.9 folder

# vi /jffs/ipkg.conf

Change the line that reads
src backports http://downloads.openwrt.org/backports/rc5
To read
src backports http://downloads.openwrt.org/backports/0.9

Save the file, and lets try the update again.

We now need to tell ipkg to use the new config file

# export IPKG_CONF_DIR=/jffs/etc/

Now lets try the update again

# ipkg update


It should be successful this time. note that the next time you need to install something you will have the enter the export IPKG_CONF_DIR=/jffs/etc/ command after you log in to let ipkg know to use this alternate config file. Or as an option you can add it into your .profile for the root user so it will be set every time you log in.

Now we need to install some packages that lftop is dependent on.

# ipkg install libpcap libncurses libpthread

Now we are going to install iftop but it complains about some of the libraries not being the correct version. I have not problems with the versions of the library installed above. So we just need to tell it to not stop the install on the version error.

# ipkg -force-depends install iftop

Ignore the errors that say it depends on libraries not install.

Note: iftop needs to be run at the root user.

You should now be able to run iftop from the command prompt. To look at the traffic on the bridge interface where most of the action is we will specify the interface on the command line with the -i option.

Enter the following command.

# iftop -i br0


Your terminal screen should now be filled with the iftop information.



10-15-1012
dwentz