Sometimes, when the intarweb-connection (da tubez) is crippled, I just fire up some ssh-connection and use SOCKS over that ssh-connection tunneled through that ssh-connection. In that case I can tell all my local applications to use a SOCKS-proxy at 127.0.0.1:$some_port – nifty nifty!
However, one application on that Windows-laptop simply refuses to work today (although it used to work yesterday) so I fired up Wireshark to figure out what could be wrong.
Started, went to “Capture -> Interfaces” and gazed. Where’s the loopback-device? You know, 127.0.0.1. Gazed again. S’not there. Hu. Started to read the Wireshark documentation, then started to read the Winpcap FAQ where I found that:
A: No. Only physical interfaces are supported. This is a limitation of Windows and not of WinPcap.