« DVD: Avatar | Wow Cox can be pretty snappy » |
In the aftermath of the summer storm of August 13th, (hmmm, totally missed that it was a Friday the 13th), I made a tweak to my ddclient config for updating dyndns for my DSL line. Because I found that it wasn't able to update the IP change while Cox was down.
Couldn't find a way to make ddclient to bind to the local IP that routes out by DSL (or use non-default gateway). But, since I have squid proxy on the same box...and depending on what port I come in on, it can use either of my connections.
I set proxy=box.lhaven.homeip.net:3128
Couldn't use localhost, because ddclient does some kind of validation to require an fqdn+port, and localhost isn't an fqdn. And, yes, I use my dyndns domain as my home domain. So I can have bookmarks that'll work whether I'm at home or on the road
But, this change wasn't tested...as it has been less than 28 days for a refresh, and no IP change.
That was until this morning, when my IP did change.
The updates weren't working....seems that ddclient wants to do SSL all the way or not at all. No using an http proxy to connect out on SSL. But, I didn't feel like sending my dyndns password out non-SSL.... So, after some thought, I decided I would figure out how to set up SSL on squid.
I made the necessary configuration change, but no go. Seems that ubuntu doesn't distribute squid with SSL, because squid and openssl have incompatible open source licenses. So, I did a quick search to find the ubuntu way of rebuilding it from source.
apt-get source squid apt-get build-dep squid apt-get install devscripts build-essential fakeroot cd squid-2.7.STABLE7 vi debian/rules Add --enable-ssl \ to “# Configure the package” section debuild -us -uc -b cd .. dpkg -i squid??? squid-common???
Change to proxy=box.lhaven.homeip.net:3218, and it worked.
But, wait...now update-manager keeps popping in wanting to upgrade from squid-2.7.STABLE7-ubuntu12 to squid-2.7.STABLE7-ubuntu12. Say what? why? argh!
Tried removing it, first and then dpkg installing again...still happens. Did some more googling....guess I want to hold the package? Hopefully that'll mean I can see when there are updates, but not get it?
% sudo dpkg --set-selections squid hold squid-common hold squid-cgi hold ^D
Let's see how that goes....
Meanwhile, I changed the port....wonder how to make firefox use it?
Great content and very helpful thank and keep up the good work.
Because the only way to tell if there’s been a new squid, is to use update-manager…and I generally don’t use the head on the server running squid. Can’t tell if there’s a new package or not… There was one a while back, but its probably not going to change until I upgrade to precise….
But, an alternate process would be to alter the version string abit… using this process:
apt-get source squid
apt-get build-dep squid
apt-get install devscripts build-essential fakeroot
cd squid-2.7.STABLE7
dch -v $CURRENT_VERSION+local
vi debian/rules
Add –enable-ssl \ to “# Configure the package” section
debuild -us -uc -b
cd ..
dpkg -i squid??? squid-common???
Where $CURRENT_VERSION is from the top of debian/changelog. It in fact has you add a new entry to the changelog….
To remove the hold use:
% sudo dpkg –set-selections
squid install
squid-common install
squid-cgi install
^D
or
% sudo dpkg-unhold squid squid-common squid-cgi
Which does the dpkg --set-selections
process for you.