Staying Connected
That’s right. I said it. Big whoop. Wanna fight about it?
The llama has had a stable uptime of over 12 hours for the first time in awhile with no sign of any 502 errors.
The main problem was the shell script that was being used to connect the llama to the unblocked internet. I created a script because my ISP blocks inbound traffic to my server. It worked, for the most part, but wasn’t pretty at all.
I’ve opted to start using something with a pretty GUI to ssh and keep the connect alive. First I tried using Internet Secure Tunneling from Han-soft and SSH Tunnel 4.0 from rs4u.com, then I found Bitvise’s Tunnelier. IST was ok, just freeware with a 30 Day trail period, which doesn’t seem free to me. SSH Tunnel was just plain confusing at first. After you setup what tunnel you wanna create, you have to reload that app to have the changes take place. Took me 20 minutes to realize that. Tunnelier is free and has everything I need and more. I advise anyone looking for an app that auto tunnels to check this one out.
On top of all that my voip router was in front of the house router. For a week or so it was dropping packets left and right. I could only sign on AIM for about 30 seconds after a router reboot. The internet was unbearably sporadic. I put my voip router back behind the other router and that seemed to stopped whatever was causing the problem.
We had put the voip router first thinking that the house traffic was taking precendence over the voip traffic because my calls would drop after a minute or so on the phone. Dragging out a 3 minute phone call in to about a 10 minute process. I found out it was the first gen cable modem Cox gave us [read:cheap bastards] had issues with the new lines they had laid.