I have disable the option to detect the if the port is open but BitComet shows my ip and port with green light see pic.
/monthly_01_2011/post-59166-12964934518957.png" rel=“”>
Yep, that seems like a bug. The team is on holiday now but when they’ll be back they will be able address this.
That is, provided that you’ll say what BitComet version you were using and what OS.
I`m using Windows 7 x86 SP1 latest version, 1.26 but i have seen this bug from beta but i was thinking what will be fixed.
Actually, scratch my previous post. I totally forgot that v.1.26 introduced an entirely new feature (which has been since long requested), namely: “GUI Improved: green light appears after incoming connection established from a remote peer”.
That is to say that if you have at least one running torrent (downloading or seeding), as soon as you get a “Remote” peer even if your port status was previously “undetected” or “blocked” it will change to “Open”.
So, did you have any running torrent?
Actually, scratch my previous post. I totally forgot that v.1.26 introduced an entirely new feature (which has been since long requested), namely: “GUI Improved: green light appears after incoming connection established from a remote peer”.
That is to say that if you have at least one running torrent (downloading or seeding), as soon as you get a “Remote” peer even if your port status was previously “undetected” or “blocked” it will change to “Open”.
So, did you have any running torrent?
Yes
Well, that could account for your green light.
If you want to test it properly start your client with all torrents stopped and see if you still get a green one.
On a side note, the tool-tip balloon message doesn’t seem to be consistent with the green light status of the port, so that definitely looks like a little bug (albeit a harmless one) that will need to be addressed.
Lucy, when you come back please forward this.
Thank you guys, for reporting the bug. This bug will be forwarded to the development team. 