By cassie
From forum_name, BitComet Forum
*moved to Port Forwarding and Router Setup*
By kluelos
From forum_name, BitComet Forum
First thing to get clear on, is that there is no "magic" port number. An open port is not something that you seek, like a hidden treasure. It is something that you set, like a thermostat, or the channel of a television.
Next thing is to understand routers. For this you need to study your router's manual.
The router has a firewall. You can instruct the router to open a port on that firewall (which action is sometimes called "forwarding the port", and sometimes called "setting up a virtual server on the port") but only under certain, limited conditions.
An open port is a vulnerability. It's potentially dangerous. Because of that, you don't want to have a port open to a computer or device that doesn't know that port is open and expects it.
Therefore, most routers will only permit you to open a port to a particular and specific IP address, which you must detail in the forwarding rule. Your computer or device needs to be AT that IP address, and it's your responsibility to make that so. If you do not, then the setup won't work.
Set up a rule that says, "Allow incoming traffic, both TCP and UDP, into port number 65432, for IP address 192.168.2.254"
With that rule in place on my router, my computer must have the IP address 192.168.2.254, and if it does not, then port 65432 (and all other ports) will be blocked on all other addresses including whatever IP address my computer does have.
If I have the default windows setup, my computer uses DHCP to ask the router to assign it a random IP address out of a pool that the router keeps for the purpose. (The size and contents of that pool can be adjusted. Let's say the pool addresses all have the first three octets of 192.168.2 and the last octet can be 2 through 255.)
The router gives the computer a random address, as requested. Let's say that 254 is within the pool, and my computer just happens to get 254 assigned to it. My address matches the IP address that the port is being held open for, so everything works. I get a green light.
Then I turn off my computer, go away for a while, come back and turn the computer back on. Again the computer asks the router for an adddress assignment, and this time is assigned the address .3 out of the pool. Now this address does NOT have a port opened for it on the firewall, so this does not work. I get a yellow light.
Every time I reconnect, I ask for and get a random address. Sometimes I happen to get the one address where the port is open, most times I don't. So sometimes my light is green, most times it's yellow, and this seems to me to happen randomly. But it's all because I'm using DHCP to ask for a random address, rather than having set a static address set into my computer for this network.
What I needed to do, was to tell my computer to never use DHCP, but to always use a fixed address of 192.168.2.254 where the port is being held open. Instead of asking the router for an address, I TELL the router that this is my address. It is my charge, as the network administrator, to make damn sure that nothing else on my little network has or can get that same address. MY job, not the router's or the computer's. Mine. If I screw that up I deserve the chaos I'll get.
----- Digression
Ok, now wait a second. Let's say that I have more than one computer. I hook them both up to the router and they both use DHCP to get IP addresses. Sometimes, it could be that my other computer gets the .254 address. When it does, port 65432 is open, and a malicious port-prober could find it. I'm not running BitComet on this computer, and the computer is not even aware that the port is open. That's a security hole. Not good. So this is what the rule is there to prevent.
----- /digression
If I now try to hook this computer up to a modem instead of a router, with those same network settings, I am telling my ISP, through the modem, that I am taking the address of 192.168.2.254, and my ISP will tell me, "not on my network, you're not. Get lost."
I must change my setting BACK to using DHCP and asking for an IP address assignment from them, if I'm going to connect directly to the modem without going through the router. Then I must change it back again whenever I change between the two networks.
I must always adapt my network settings to the requirements of the network I'm connecting to.
It would be great if windows supported various network configurations on a single network card, but it does not and never has. That means that I have to adjust the network settings by hand every time I change, so I need to memorize IP addresses, DNS servers, default gateway settings and so forth for every network I connect to.
(If I get the settings wrong, because I memorized incorrectly, wrote them down wrong, or mistyped when I set them, I will spend an enjoyable couple of hours trying to figure out why I can't communicate.)
I hope you got that very clear. What we accomplished is to allow unsolicited traffic from other computers, into your computer at a specific port. Your bittorrent client is watching that port and receiving that traffic. It only understands certain, very specific messages, and because it discards anything that it doesn't understand, you're safe from attack on that port.
Unsolicited traffic, only on the specific port, only to the computer that's expecting it, where BitComet sits watching the port.
Now adding a second router into the mix, it gets messier. The same principles apply, but you have to go through Router B. Router B has to sit in place of your computer. It has to have a static IP address on Router A's subnet, just as your computer used to. Router A's firewall has to forward the chosen port to Router B, at that same IP address, just as it used to do for your computer.
Your computer's connection to router B will be unchanged from its former connection to router A. Your computer can even use the same IP address as before, because it is now connected to a sub-sub-network.
You can't have two files with the same name, in a single directory, but you can if one is in a subdirectory. Same principle.
Router A can only see Router B, but not B's subnet or any devices connected to Router B. As far as router A is concerned, all of this traffic is coming from Router B with no idea what, if anything, may actually be connected to B. This isolation flows both ways.
It's still the same principle. Get the unsolicited traffic through the first firewall on the right port, to and through the second firewall on the right port, to the computer that's expecting it and where BitComet is waiting for it. You use the same tools to test it.
By kluelos
From forum_name, BitComet Forum
Stop the task, right-click it and do a manual hash check on it. Then restart it and see if this clears it up. If not, come back and we'll try a couple of other things.
By kluelos
From forum_name, BitComet Forum
That's ten tasks. 8 + 2. Yes, that's 'way too many. Try keeping it to one seeding task and one downloading task for a total of two.
This shouldn't have any effect on your computer's speed though, it only affects your download speed. For your computer slowdown, try downgrading to version 0.70 and see if it eases up or goes away. If so, then only upgrade cautiously and be prepared to go back to 0.70 if you don't see satisfactory performance.
By rocambole
From forum_name, BitComet Forum
yes i have just 2 task for downloads, and 8 for seeding. is this so much?
By Imperium
From forum_name, BitComet Forum
We strongly recommend that you only run one or two tasks at a time, as it best for download speed as well as for your computer in general if you are experiencing slowdowns with so many tasks.
By XSTREM
From forum_name, BitComet Forum
Bary: It will be 1.02. You see, all the bugs are getting fixed one by one now.
I think that's the first time a new release have had 3 (and counting) BETA versions. Normally, they only have one.
Around some minutes ago, the 3rd 1.02 BETA ([20080530]) version got released! And another reported bug is fixed, exactly as promised from the developer.
GUI Improved: BitComet resource browser (CometBrowser.exe) will exit immediately after close all its window
GUI Improved: Changelog in Help menu links to changelog webpage of Beta version
Core Bugfix: HTTP download task do not reconnect server after connection disconnected by server
Core Bugfix: HTTP download task do not drop invalid data from out-of-date mirror server, lead to redownload after hash check failure
- XSTREM.
By Bary
From forum_name, BitComet Forum
Franpa:
No, they told me in person and gave kudos for my effort, which is appreciated. ;-)
Oddly enough, everyone but the developers were very pessimistic. They said, as I've written in some of my topics, that it had nothing to do with BitComet. However, the friendly developers understood perfectly and now the bugs are getting fixed one by one.
Of course, the "Zero Response Error" was reported once before as I did my search through the board. No particular response was made though, which seemed odd.
My good Chinese friend, oioi21, tells me that the "CometBrowser.exe" was reported, but never fixed.
Now they are, and that is perfect. Frankly, I don't care who actually made the breakthrough - if it was me or not, what counts is that they're finally getting fixed.
- XSTREM.
well XSTREAM if not in 1.02 it would be in 1.03 so finaly world would see real strong and bugsfree client of p2p world.
By XSTREM
From forum_name, BitComet Forum
Franpa:
No, they told me in person and gave kudos for my effort, which is appreciated. ;-)
Oddly enough, everyone but the developers were very pessimistic. They said, as I've written in some of my topics, that it had nothing to do with BitComet. However, the friendly developers understood perfectly and now the bugs are getting fixed one by one.
Of course, the "Zero Response Error" was reported once before as I did my search through the board. No particular response was made though, which seemed odd.
My good Chinese friend, oioi21, tells me that the "CometBrowser.exe" was reported, but never fixed.
Now they are, and that is perfect. Frankly, I don't care who actually made the breakthrough - if it was me or not, what counts is that they're finally getting fixed.
- XSTREM.
By franpa
From forum_name, BitComet Forum
Um how do you know they did this because of you xstrem? probably some chinese guy reported the bug to them and that is why it was fixed
By XSTREM
From forum_name, BitComet Forum
Finally! If I'm happy? Yes, I'm happy.
Not only have the developers showed that they want to make both sides (Eastern and Western) happy! They've also showed an increadible speed in how fast they're really fixing the bugs. I'm very glad we have this breakthrough! I'm glad I took the bull by the horns and my report was taken seriously - it has taken a hell of a time to write all these different reports and synopsis, and I'm glad it was to a great help. If any major bugs are found, I'll gladly support the development again - but for now, we can all sit back and watch our favorite client is close to bugfree.
Now, let's get the "User-agent" user-changeable, make it final and let us announce it everywhere! The world shall know that BitComet finally is compatible on every tracker in East and West, and it still respects every security aspect. V. 1.02 will be a client that makes it into the BitComet history, I'm sure on that.
A big thanks to the developers and Tech Staff.
- XSTREM.
By cassie
From forum_name, BitComet Forum
Hi,
QUOTE
So where do I find my UD ratio?
Usually, you can find it to the right of your 'Seeds/Peers[All]' column, on the main window (where your tasks are listed).
By ellgie
From forum_name, BitComet Forum
Yes indeed, the learning curve escalates!
Your response is exactly what I need, that is to understand how this works. It makes perfect sense that peer-to-peer (I even have to get used to those abbreviations! p2p) relies on true sharing. So where do I find my UD ratio? I hope it is good so far as I know it is only correct to give as you receive.
Occasionally I suspect that I have bitten off more than I can chew; but I also love to learn to lets continue this hourney. You are a good teacher. Thanks.
By kluelos
From forum_name, BitComet Forum
I understand your question very well, and while it may not be quite full of jargon, you're also not misusing any and the question is clear.
Bittorrent and P2P generally is not at all like anything else you've used before. Most downloading heretofore has involved a large server with a fat pipe and it's all been a) one-way, server to you, and one-on-one, just the server and you.
In P2P, the source of the files is you, and people just like you, with computers like yours and connections like yours - not the latest or greatest or fastest. As you download via P2p, you also upload to others. Get a piece from someone else, share that piece with others. With Bittorrent, you can't fail to do that because it will badly harm your download speed if you don't upload too.
Your connection is asymmetric: your download speed's a lot faster than your upload speed. It takes more time for you to upload a given amount of data, than it does to download it, irrespective of the source. So when your download reaches 100%, you will have downloaded more than you've uploaded. This is reflected in your U/D ratio, also called your Share ratio. Your client will show you what this ratio is for a given task. When this ratio reaches 1:1 it means that you've uploaded as much as you have downloaded -- given back as much as you've taken.
Since this community depends on people like you sharing, that's considered the minimum that's expected of everyone: give at least as much as you take. When your download reaches 100% it is complete, yes, but then your client will automatically change modes and begin uploading (seeding) exclusively. You should check your ratio to see if you've reached the point where you want to stop seeding. If you stop when your download is complete your ratio will probably be terrible. Folk who do that as a general rule are disliked. Enough people doing that would eliminate this community.
You can set the ratio you want to stop at, or the amount of time you want to spend seeding (at least in most clients). For example, stop when I've shared to 1.5:1, or stop after I've seeded for 3 hours. Or you can keep seeding until there's nobody left who wants to download. Or if you're using a private tracker that requires you to maintain a minimum ratio, you may want to keep the task seeding in hopes that somebody else will show up and want a few bytes from you. (This is a common situation with those sorts of trackers, as everybody tries to improve their ratios.)
Hey, you thought Bittorrent's learning curve was steep? You ain't seen nothing yet. Wait until you dive into digital video, which is your second question. Rocket science is easier.
By Dark_Shroud
From forum_name, BitComet Forum
1) Get your torrents from respectable index sites. (
www.mininova.org)
2) Learn to read the comments on .torrent files before you download.
3) If you're asked to install something and you don't know what it is do some research first. Any search engine would do.
4) Downloading newly released movies is a sure fire way to get caught illegally downloading.
5) What you download has nothing to do with BitComet.
help
Tue May 27, 08 09:29 PM
By cassie
From forum_name, BitComet Forum
Hi,
If the download has completed, BitComet's job has concluded... and this is in the wrong forum.
Before we can give you any type of help, you must be able to tell us what format /file extension (eg. *.iso, *.jpg, etc.) your downloaded file/s is/are in.
Please be as descriptive as possible, when doing this (if you're not able to view these extensions, please go to the How-To's section and read the tutorial on how to do this) - the game's name/title will not suffice.
*moved to General Questions*
hello,
Mon May 26, 08 08:17 PM
By cassie
From forum_name, BitComet Forum
Hello and
Your friend is one smart cookie!! (Of course, I'm biased... )
By kluelos
From forum_name, BitComet Forum
Why say anything here? Most members won't even know what you're talking about. Such comments should be made on the tracker where the torrent originates, to warn others off of it.
By Dark_Shroud
From forum_name, BitComet Forum
Consider it a blessing that it won't trigger the warning message as long as your OS version isn't supported.
By kluelos
From forum_name, BitComet Forum
We've been telling people not to do this, that the whole issue is bogus and the patch is very dangerous. Microsoft has finally locked tcpip.sys down so it can't be modified. Do not try. It would not help in the first place, and can easily foul things up.
We've been asking the developers to remove this dumb, pointless warning for months, but they don't listen to us in this or any other area.
