$(document).ready(function() {
  $("#my-scroll-pane").jScrollPane();
});

In firefox, the scroll pane never showed up, and clicking on links inside the page to call it again also produced no results.

Luckily, firebug exists and I was able to discover that the div we were attempting to turn into a scroll pane had a javascript-calculated width and height of 0. Debugging the actual jScrollpane.js file and following its path in calculating these values showed that when it was attempting to find the innerWidth/innerHeight of the div, it was getting the answer of 0, so that’s what it used.

Thankfully someone had a similar problem and had filed a bug here. Essentially the problem is, as Kevin Luck described, that while the iframe is loading it is not visible, and so jScrollpane gets innerWidth and innerHeight of 0. The solution that is suggested is to utilize a callback method of the fancybox library, callbackOnShow which is called when the content *is* visible. For some reason, merely calling the jScrollpane code inside of this callback was still was a bit wonky, so I bound it to the load event and all was well:

'callbackOnShow': function() { 
  jQuery('#fancy_frame').bind("load", function() {   
    jQuery('#fancy_frame').contents().find('#my-scroll-pane').jScrollPane();
  }
}

(Note: I’m really not sure why, but this is the only way I could get this to work via binding on load. E.g., if I put the code inside of the iframe’s source inside of $(window).bind(“load”) code block, it still exhibits the undesired behavior. It’s a mystery to me, but this works anyhow!)

WARNING: Openwrt requires a case-sensitive filesystem! Default MacOS and Windows partitions are case-insensitive so it will not work, and make menuconfig will tell you as much.

$ svn checkout svn://svn.openwrt.org/openwrt/trunk openwrt-kamikaze
$ cd openwrt-kamikaze/scripts
$ ./feeds update
$ ./feeds install tcpdump
$ cd ../
$ make menuconfig

If you have ever compiled your own kernel before, this screen should look somewhat familiar. Either way, go into the “Network” subsection and select tcpdump, hit the spacebar until an “M” shows next to it, indicating that it will be built but not built directly into the image. Exit out of all the screens until it asks you if you want to save your configuration and select yes.

The last thing you need to do is make sure that tcpdump compiles with static libraries, because the libraries it needs are most likely not on your router now. (If you compiled it dynamically it would most likely result in this kind of error when trying to run it: ./tcpdump: can't load library 'libpcap.so.1.0') To compile it statically linked, edit the file feeds/packages/net/tcpdump/Makefile and add -static to the CCOPT, like so:

define Build/Compile
        $(MAKE) -C $(PKG_BUILD_DIR) \
                CCOPT="-static $(TARGET_CFLAGS)" INCLS="-I. $(TARGET_CPPFLAGS)" \
                DESTDIR="$(PKG_INSTALL_DIR)" \
                $(MAKE_FLAGS) \
                all install
endef

Now just type make in the parent directory of openwrt and wait a while. It will go through and compile the cross-compiler as well as the image and some other stuff you won’t be using (if anyone knows how to just compile the stuff that’s necessary, please comment! Otherwise, this will do just fine.) Once it is complete, you will probably want to isolate tcpdump from everything else, so to do something like copying it to /tmp/tcpdump just run something like this:

$ find ./staging_dir/ -name tcpdump -exec cp {} /tmp/tcpdump \;

To ensure that the file was compiled properly and statically, run the following command and you should receive the following response

$ file /tmp/tcpdump
/tmp/tcpdump: ELF 32-bit LSB executable, MIPS, MIPS32 version 1 (SYSV), statically linked, not stripped

Once you have tcpdump compiled, you will need to put it onto your tomato-backed router. To do that, go to the administration page for the wireless router, select “Administration” and ensure that the SSH daemon starts up. You will ssh in as root, using the same password setup to access the administration interface via HTTP. Before you do that, however, under the “Administration” tab that is now open, click on “JFFS2″. If not enabled, click on “Enable” and “Format/Erase”. Once this is done, there should be a device mounted on your wireless router when you login, like so:

# mount
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
/proc on proc type rw (0)
/tmp on ramfs type rw (0)
/dev/mtdblock/3 on /jffs type jffs2 (rw,noatime,nodiratime)

The JFFS2 partition is quite small (1.0M on my router), but will be large enough to hold tcpdump. This is a place for files that will permanently stay on your router through reboots and the like. If you were to put tcpdump in /root, for example, it would be gone the next time you rebooted.

Now that you have JFFS2 and ssh enabled, simply scp the tcpdump binary to /jffs on the wireless router and you should be able to execute it.

Unfortunately, again due to the storage limits on the wireless router, if you intend to save the output of tcpdump to a file (for example, to examine with wireshark later, etc), you will likely need to enable the “CIFS Client” under the same Administration tab that JFFS2 and ssh were inside of. The CIFS Client is essentially a SMB client, so you can use it to mount a samba share, windows share, mac os share shared via SMB, and so on. Under the /cifs1 entry, the UNC will be the familiar SMB url to the share, for example:

\\192.168.1.2\myshare

Fill in the username/password/etc as necessary. Once it is enabled and saved and the router mounts it, you should have a /cifs1 entry in your mounted devices list, and you can use it to save your tcpdump files to. For example:

# /jffs2/tcpdump -s 1500 -w /cifs1/mynetwork.out

dpkg-deb -x squeezeboxserver_7.4.1_all.deb src/
dpkg-deb -e squeezeboxserver_7.4.1_all.deb src/DEBIAN

Now edit the control file in src/DEBIAN/control and remove all mysql dependencies.  The Depends line should look like this:

Depends: perl (>= 5.8.8), adduser

Go back down to the directory below src/ and run:

dpkg-deb -b src/ squeezeboxserver_7.4.1_new.deb

It will build you a new package, and you can install it with dpkg -i like normal. There are probably some other ways to fix it, but this one was pretty simple for me.