Bitcomet 11004 Dns Error
Contents |
Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. 2 IPv6 Support Started by mlewellyn, Aug 04 socket error 11001 host not found 2011 01:37 PM You cannot reply to this topic Go to
Socket Error #11001
first unread post 3 replies to this topic #1 mlewellyn Seeder Members 6 posts Posted 04 August 2011 error code 11001 host not found - 01:37 PM Now that ISPs are starting to roll out native IPv6 support, and Toredo/6to4 being almost ubiquitous and almost well-supported even in the lowest-grade consumer gear, I'm seeing
Socket Error 11004
more IPv6 trackers and peers. Unfortunately, BitComet is not yet able to connect to these resources. Quite notably, trackers which only have an AAAA record (no A record and thus no direct IPv4 connectivity) give an "Tracker connection error: 11004 DNS error" in BitComet (verified that this is still an issue in 1.28). A public tracker which only has an AAAA record, for testing purposes, is Ubuntu's IPv6 tracker: http://ipv6.torrent.ubuntu.com/ Note that if you do not have IPv6 (native, tunneled, 6to4, Teredo, or otherwise) connectivity, you won't be able to view the page (and therefore download the torrents). Note that this particular tracker provides torrents which have both IPv4 and IPv6 trackers listed (though it is trivial to just remove the IPv4 tracker for testing purposes). There are some private communities already which do not: it's IPv6 for their communities or bust. Considering that many communities still have misgivings over allowing BitComet due to the missteps of years ago (0.6x and 0.85 come to mind), offering superb IPv6 torrenting on Windows would likely help BitComet's image amongst those who have closed their minds toward it bar any reason of reconsidering. At the moment, uTorrent is the only viable choice for IPv6-only trackers on Windows. Back to top #2 greywizard Grand Wizard BitComet Tech Support 3041 posts Gender:Male Location:127.0.0.1 Posted 04 August 2011 - 11:40 PM I kind of second this. I think sooner or later all B
by CloudFlare Ray ID: 2eb8606206531425
just finished my torrent download. What are the files in the download? (e.g. so many numbered files, .iso, etc) What is “rubbish data” and why am I downloading so much of it? What are Private and Public Trackers? What can I do about tracker errors when http://wiki.bitcomet.com/torrent_related I start a task? How do I create a .torrent file? How do I seed it? How do I configure a torrent for Multi-Trackers when I create one? Torrent Related I've just finished my torrent download. What are the files in the download? (e.g. so many numbered files, .iso, etc) Refer to this post in our forum to follow the step-by-step guide. What is “rubbish data” and why am I downloading so much of it? socket error Rubbish data or garbage data, is a term used to describe, in the BitTorrent scene, downloaded pieces which failed to pass the hash-check and consequently are discarded. They are regarded as garbage since they are of no use to the downloading client and only waste bandwidth and time. Possible causes Rubbish data is basically caused by peers sending bad packets to the swarm. Whether intentionally or unintentionally, that can't be easily determined. It could either be 11001 host not caused by peers having bad connections, by a bad/unreliable/congested segment of network in the path between the other peer and you, as well as a variety of other things or by anti-piracy organizations which mingle into the torrent swarms using modified clients and release bad data intentionally, so as to hinder torrent users (in case you're downloading copy-righted material). Another more prosaic reason for occurrences of garbage data might be your router. Certain routers are known to have a particular firmware implementation which may lead to corrupt data, especially on BitTorrent downloads (which by definition use a huge number of simultaneous connections). A good indicator for this, is getting garbage data for all or most of your torrents. Solutions The only solution, so far, to this problem is to download an IP-blocking program (such as Peer Guardian: http://phoenixlabs.org). Download and install the client, and when it comes to the screen of 'Updates' click on the check-boxes: Government, P2P, Ads. Then let PeerGuardian update its lists. Allow PeerGuardian to run every time your BitComet client is functioning. This may reduce, in some cases, the amount of garbage data you get, by refusing connections to some IPs known to interfere with P2P downloading. A reminder to users: This program does not guarantee that you will receive nil rubbish data, or that you'll be “protected” from g