After a few too many attempts and a lot of Googling, I finally figured out how to make a reliable ssh tunnel for my wireless network.
I got it to work on the command line (ssh red -L 8080:red:3128) and then decided to turn it over to SSH Tunnel Manager. It turned my simple command to something a bit more precise (/usr/bin/ssh -N -v -p 22 -C -c 3des paul@red -L 8080/red/3128)
So far, so good. If I can stand the speed loss, it should be useful.
What’s happening is easier to work out from the first command. I’m connecting to an internet-connected machine via ssh, but rather than just creating a terminal, I am opening a secured, compressed connection that anything can use, from port 8080 on the local system to port 3128 on the remote system. Since port 3128 is a squid proxy cache, it may not be as slow as I fear.