Firewall hits with BitTorrent installed

[mvdu]

Hi,

I was using BitTorrent, but even after I close the program and closing the DNA process, I continue to get hits on mainly ports 49648 and 50347. Is this normal? I have a router, but with no port forwarding. I'm thinking of uninstalling BitTorrent if I can't find a harmless reason for this.

[Wolfeymole]

They that sow so shall they reap mvdu.

I heartily suggest you remove any Torrent software as it can cause you nothing but problems.

[mvdu]

-{ Quote: "They that sow so shall they reap mvdu.

I heartily suggest you remove any Torrent software as it can cause you nothing but problems." }-

But how do you explain these hits I'm still getting? Is it normal with the software, or could there be an infection?

[Wolfeymole]

I cannot advise further on torrent software I'm afraid as it can and is predominantly used for illegal purposes.

This is not to suggest you utilise the medium for such practices.

[Meriadoc]

Bittorrent is a very good way to distribute files, mvdu hasn't mentioned any 'illegal purposes'

[mvdu]

-{ Quote: "I cannot advise further on torrent software I'm afraid as it can and is predominantly used for illegal purposes.

This is not to suggest you utilise the medium for such practices." }-

You don't know how I'm using it. Why come in the thread just to give a morality lesson? I have a legit question here.

[mvdu]

And also, I ALWAYS buy music. When I do download stuff to try out, I delete it after listening.

[Wolfeymole]

I am not suggesting mvdu has Meriadoc and I'm not casting aspersions but it has to be acknowledged that P2P can create problems that may be thought of as an otherwise aspect.

[gb63]

Simple reason for what you see -
It is normal. When you use a torrent, the connection with server(s) adds your ISP number to the current list of online seeders/leechers.
Until all servers detect you are offline due to some timelimit of no access or keep-alive feedback, software on a number of other user machines will be sending a request to you, and your firewall will react because the torrent is no longer running on your machine.

[Stem]

Let us stay on topic.


As mentioned by gb63, what you are seeing is other users of the torrent still attempting to connect in.
It is one reason to allow outbound ICMP destination/port unreachable.


- Stem

[mvdu]

Thanks, gb63 and Stem! I won't worry, then. How long does it take for the hits to go away?

[chrome_sturmen]

yeah like gb63 said, it's normal - even after you close your torrent client you'll still see incoming and outgoing connections related to your torrenting - it eventually stops, but if you want it to stop immediately after you're done torrenting, reboot your computer. i assume you're using peer-guardian or another blocklist?

[dw426]

-{ Quote: "Thanks, gb63 and Stem! I won't worry, then. How long does it take for the hits to go away?" }-

They're called ghost packets, and usually they stop after about an hour at most.

[mvdu]

-{ Quote: "They're called ghost packets, and usually they stop after about an hour at most." }-

I'm seeing blocked packets continue to come in according to the Outpost Packet log, but nothing really blocked in the Firewall log. These packets still come in long after the program has been closed - I don't think they have stopped, in fact.

I do use Peer Guardian even though I'm not a big downloader or sharer.

[gb63]

With some torrent clients when you think you are exiting, they drop to the taskbar and remain running. You may also check the Task Manager to see if the process is indeed dead.

[dw426]

-{ Quote: "With some torrent clients when you think you are exiting, they drop to the taskbar and remain running. You may also check the Task Manager to see if the process is indeed dead." }-

uTorrent as a matter of fact does just that. You won't likely get any blocks unless the IP is in Peerguardians blocklist. I deal with this all the time with Emule and uTorrent, I'm sure you're just fine. Post back though if it hasn't stopped at all or at least slowed, or if another problem shows up.

Edit: I noticed it's been about 5 hours from your original post until your last. Stem would know much better than me, but that doesn't seem right. My packets quit after about an hour, sooner if I reboot. Try rebooting and see what happens, ok?

[mvdu]

-{ Quote: "uTorrent as a matter of fact does just that. You won't likely get any blocks unless the IP is in Peerguardians blocklist. I deal with this all the time with Emule and uTorrent, I'm sure you're just fine. Post back though if it hasn't stopped at all or at least slowed, or if another problem shows up.

Edit: I noticed it's been about 5 hours from your original post until your last. Stem would know much better than me, but that doesn't seem right. My packets quit after about an hour, sooner if I reboot. Try rebooting and see what happens, ok?" }-

I'll try rebooting again, but it didn't help before. Maybe Stem can explain why I'm still getting packets even though the program isn't loaded at all.

[Stem]

The other clients on the torrent will still have your IP from when you where connected, so they will still attempt to connect in. I do not know how the different clients store the info for other clients, but they may still attempt to connected in until the client is closed or they have finished the download, which ever comes first.

Dont worry about it, the inbound will stop eventually.


- Stem