That diagnal pipe coming out of the tub going into the main toilet
drain is where the problem lies. Next step is to replace it. My arms
are so freakin tired.

We went over to Buffalo reuse to find more hex tile for the bathroom
floor and we got a whole bag for $4 but that was all they had.

I bought this award for (e:terry) at (e:mike)'s garage sale. For those of
you that missed it, it is still going till 3ish and you can buy the
high school musical board game.

Not that I don't think the bench has some awesome craftsmanship but I
am ready for some comfortable porch furniture.

I feel like the more I dig the worse it gets.

If this makes no sense to you, then you don't need it - I don't plan on helping anyone with it. However, if it does make sense it might be very useful.

What I am going to demonstrate allows you to secure you internet connection on your laptop when you are a coffee shop or when you are somewhere where they are blocking your favorite site and you want to get around that by piping all your laptop traffic through you home computer or external server, encrypted over SSH.

This assumes both machines have SSH and are *nix flavor (mac,unix,linux). If you are using windows I think you can still do this somehow but I don't care and you can figure it out yourself.

Its really just a few simple steps. The first step is to connect to your server/home computer from from the laptop:

ssh -p SSH_PORT -D LOCAL_PORT USERNAME@SERVER

SSH_PORT = The addres you communicate over ssh with. You can leave off the -p SSH_PORT if you are using ssh on the vanilla port 22.

LOCAL_PORT - The local port you want to use for the SOCKS proxy. I would suggest something like 8080 but it really doesn't matter. Just make sure its one you are not using.

USERNAME@SERVER - The normal username@server you use to connect to your home machine or server over ssh. e.g. myuser@mysite.com. It can also be the IP address if you don't have a domain name.

Once you have connected open up a SOCKS proxy complaint app. A common one is Firefox and great because its a web browser, so that is the kind of traffic you want to secure when surfing somewhere sketchy.

In your firefox prefs, choose the network tab.


Then set up the proxy settings to point to localhost 127.0.0.1 and the LOCAL_PORT port you choose above.


You should be set to go. To test and make sure open you /etc/hosts files and add an entry for:
0.0.0.0 google.com

Now open up another browser. When you go to google it should be site not found as you are redirecting google to 0.0.0.0 for your comp. However, when you use firefox with the SOCKS proxy it should still work when you go to google.com because the traffic is being piped through SSH to your server or home machine.

Once you are done with this test remember to take the google.com entry out of /etc/hosts and also remember all you traffic is only encrypted and piped via firefox.

Another simple test is to check your IP from your browser. Visit in firefox. The IP should be the same as your home computer/server.

To shut down the proxy just kill the process for the ssh connection to the server.

You can also set you entire system to use the proxy but that is for another day. Well here is a clue on a mac. This is in the system network preferences. Safari should be proxied afterwards.

(E:southernyankee) sent me this pic she took of me at zoar. I wish I
could have got this pic a month ago when I was much buffer but it's
better than no pic.

Despite (e:jon)'s tale of friend gone dead on rocks I decided to go climbing today and brought (e:southernyakee) with me.

It's done and I survived this time.

Seriously, news channel 4 just did a special report about the "growing
trend of staycations."

There is a wikipedia page explaining staycation.

Despite the wind throwing lots of pear babies on the ground, it looks like we might have the most pears ever. This year I am just doing pots of juice and a pear themed party.