Check this out: [8.4.2010 5792261] Notice of Copyright Infringement

[Reerun_KC]

Originally Posted by Consistent1

Don't even get in the position to deny it like Reaper said. Just be careful with what you do from now on and act like it never happened. Maybe introduce the boy to pron, you shouldn't get hassled there. Plus it will teach him to respect women. hahaha.

I disabled and blocked all leaches and ports outbound for bitcomet on the firewall.

I think I will run it through another country from now one and do those downloads across a vpn through an overseas IP....

[Fish]

Originally Posted by Reerun_KC

I disabled and blocked all leaches and ports outbound for bitcomet on the firewall.

I think I will run it through another country from now one and do those downloads across a vpn through an overseas IP....

Somebody's been watching too much CSI or something...

[Reerun_KC]

Originally Posted by KC Fish

Somebody's been watching too much CSI or something...

Just have that capability to route protocols and ports over to our office in the Middle East.

sometimes all this network knowledge can pay off....

[Fish]

Originally Posted by Reerun_KC

Just have that capability to route protocols and ports over to our office in the Middle East.

sometimes all this network knowledge can pay off....

Uhh huhh..... and spoofing IPs on the firewall too?

[Reerun_KC]

Originally Posted by KC Fish

Uhh huhh..... and spoofing IPs on the firewall too?

Are we talking over your head?

[Fish]

Originally Posted by Reerun_KC

Are we talking over your head?

Yeah.... somebody is at least....

The thing about P2P is that you're creating a direct connection between your computer and the torrent tracker. So whatever you think you're "spoofing" is irrelevant. Even if you managed to figure out how to spoof your IP(which I really doubt), doing so would effectively kill your entire connection in Bitcomet, and you couldn't use it for anything. You see, when you spoof an IP, you're changing the header info to use an IP other than your own. So when something tries to reply, it goes to a different IP than the one you have. Spoofing your IP would cause the torrent tracker to send info back to a different IP, and you'd never get a response from it and could never download anything.

Like CrazyPhud pointed out, even apps like Peer Guardian aren't doing what you think they're doing. They're not hiding your IP at all. They're simply blocking certain known addresses from returning info to your IP. But your IP is still out there for the tracker to see. It has to be for it to work.

And a VPN connection wouldn't do anything for you in this case either. As a VPN connection restricts IP access outside of whatever network you're connecting to. That's the entire point of a VPN connection. So while your VPN connection was running, you would have no access to any torrent trackers. You could access a computer on your VPN network in another country, and use that computer to download stuff. But they'd still be able to see its IP, and you'd still have to transport your downloads from that network to yours, which would make it unusable.

But you're the network expert here... I'm sure you already knew all this...

[Reerun_KC]

Originally Posted by KC Fish

Yeah.... somebody is at least....

The thing about P2P is that you're creating a direct connection between your computer and the torrent tracker. So whatever you think you're "spoofing" is irrelevant. Even if you managed to figure out how to spoof your IP(which I really doubt), doing so would effectively kill your entire connection in Bitcomet, and you couldn't use it for anything. You see, when you spoof an IP, you're changing the header info to use an IP other than your own. So when something tries to reply, it goes to a different IP than the one you have. Spoofing your IP would cause the torrent tracker to send info back to a different IP, and you'd never get a response from it and could never download anything.

Like CrazyPhud pointed out, even apps like Peer Guardian aren't doing what you think they're doing. They're not hiding your IP at all. They're simply blocking certain known addresses from returning info to your IP. But your IP is still out there for the tracker to see. It has to be for it to work.

And a VPN connection wouldn't do anything for you in this case either. As a VPN connection restricts IP access outside of whatever network you're connecting to. That's the entire point of a VPN connection. So while your VPN connection was running, you would have no access to any torrent trackers. You could access a computer on your VPN network in another country, and use that computer to download stuff. But they'd still be able to see its IP, and you'd still have to transport your downloads from that network to yours, which would make it unusable.

But you're the network expert here... I'm sure you already knew all this...

I am very impressed! I think I better quit my job now, since I know nothing compared to you. So Can you tell me what I was planning on doing and how I was planning on getting the files?

Obviously I dont have a clue...

[dirk digler]

Originally Posted by Reerun_KC

I disabled and blocked all leaches and ports outbound for bitcomet on the firewall.

I think I will run it through another country from now one and do those downloads across a vpn through an overseas IP....

I would think the download times would be pretty slow doing it that way.

[Reerun_KC]

Originally Posted by dirk digler

I would think the download times would be pretty slow doing it that way.

We will see... I rarely download movies or music, so to be honest its not that big of a deal...

but yes when the hop gets to NYC the latency jumps from 57ms to over 300Ms when it hits the seabone.net carrier....

but I could grab it over there and bring it across the pond through the vpn...

But its really fun to make it work that way, but the speeds would absolutely suck.

[BigRock]

Originally Posted by Reerun_KC

We will see... I rarely download movies or music, so to be honest its not that big of a deal...

but yes when the hop gets to NYC the latency jumps from 57ms to over 300Ms when it hits the seabone.net carrier....

but I could grab it over there and bring it across the pond through the vpn...

But its really fun to make it work that way, but the speeds would absolutely suck.

Not worth it if you rarely download, but if you're already familiar with VPNs and stuff, you should look into a seedbox.