3 ms·
You're not using multicast IP, are you? I've heard (a while ago) that this doesn't work at all on EC2, e.g. their routers don't support or have limited support
by eklitzke 17y ago
You're not using multicast IP, are you? I've heard (a while ago) that this doesn't work at all on EC2, e.g. their routers don't support or have limited support for IGMP. If you had a protocol that mixed unicast and multicast then that may explain why some nodes aren't visible.
- swolchok 17y agoNope, this has nothing to do with multicast, sadly. My current solution is to just get off EC2 and run the crawler locally. I have a DHT-layer ping utility, and observed that the failing node could not ping some peers that the successful node (crawling the other network) could, so I hypothesize that either EC2 or the file-sharing network was doing some rate limiting. The puzzling thing is that the local scanner has been running for hours without showing any signs of failure.