[andrewcooke]

if anyone is in a similar situation, the tools you need (for linux at least) are etherape and then wireshark. the first will show you which machine is transmitting lots of data. the second will give you a good idea what that data is (if it's not already obvious from the destination computer shown in etherape).

what are the windows and mac equivalents?

[TillE]

Wireshark. After all, libpcap has been ported to all platforms worth mentioning.

I suspect that JungleDisk is primarily to blame here. Most programs (certainly the Windows search indexer) already know to treat files on network drives differently, otherwise they'd be unusable in business environments where you have a variety of SMB shares mounted on every computer.

If JungleDisk appears as a local drive, there's your problem. This is just speculation though, as I can't be bothered to give them my credit card details just to test that theory.

[sp4rki]

You misunderstood what the problem was. It was not that JungleDisk was downloading backup data, it was that since the AWS 'drive' is mounted as a local drive, when indexing happened (or when the antivirus scanned the files), Windows (or the antivirus) would download all the data they where trying to access. I'd actually go with the antivirus in this case, but it certainly is not JungleDisk's fault.

[cowpewter]

Yeah, still Wireshark on Mac, though if you wanted something a little user friendlier, you might be able to get a clue from LittleSnitch's network monitor. If you open it up, it shows all the applications that are currently making network requests and where the request is going to. I suspect in a case like the article's, it would show JungleDisk constantly connecting to AWS, and if you knew it wasn't supposed to be uploading/downloading something right now, that would narrow it down pretty fast.