Proxytunnel is a program that connects stdin and stdout to a server somewhere on the network, through a standard HTTPS proxy. Getting it built seems to be pretty straight forward stuff.

Which is better? Which is faster? For a desktop system, I don’t think it really matters if you have to process a bunch of rules. How many can there be, and how much network traffic are you seeing anyway? It’s probably more efficient to modify your sysctl.conf, but it seems more organized to do it all with iptables.

I still prefer a flat ascii file either loading the rules one at a time, or the built in iptables save/restore which basically does the same thing. But if you like/want/need a GUI application, then skip the lokkit firewall configuration tool in favor of system-config-firewall. It makes configuration of your firewall as easy as the simple Windows firewall, but with the option detail you expect from Linux.

If you’re behind a proxy and you run that, you’ll get something like “the other end hung up” or “Cannot get remote repository information” because git is trying to connect using port 9418 by default. I found a few sites saying all you need to do is change git to http in the url and it will work, but that did not work for me. But it’s an easy fix. Change git’s http.proxy and you’re done. Here’s how: (replace my proxy host and port 8002 with your own)

There’s a hidden directory called “.subversion” in your home directory. Edit the servers file. Everything should be self explanatory. Scroll down to the bottom and you’ll find a global section. The proxy settings in there should cover it…