Port Forwarding

[MrMazda]

@mgr:

… As good as UPnP can help you get "unwilling" equipment to open ports: there is a hidden danger in using UPnP though: If you catch a malware program one way or another that program is able to silently open a port for its own use by using UPnP system-calls, not only in your firewall but also in your router for outgoing and incoming traffic which enables this "pilot" malware to download a really harmful program to your computer without the knowledge of your router, your "security system" / firewall and, worst, your own knowledge!!!

I admit it is easy to use UPnP to open ports in your equipment - but be sure to log such attempts (if at all possible) and watch that log carefully!

I recommend though to have at least one secure "last barrier" which will not react on UPnP and handle that barrier (in my case my external router to the internet) manually. Call my paranoid, but I'm very cautious about the security of my LAN - that pays off too - I had several intrusion attempts in the last couple of years but I always could delete the regarding software without harm being done

For this very reason I would suggest also using a firewall such as ZoneAlarm. It will allow you to lock your machine down in such a manner that upon malware attacks, the firewall must first be configured to allow the program, port, etc prior to it being able to make the connection.

[blackdid]

Thx mgr for the great 3 tables + "talk of the narrator" 

[blackdid]

Ahhh…at last I found again Mgr's virtual dialog between the tracker and 2 clients A-B (btw, it would be great to be able to bookmark a post within a whole topic, giving him the name we want in the bookmark window, then we would retrieve any post at the speed of sound in our bookmark window)

In fact, I found again that post doing this : Forum search window :

Search For: tracker client A client B
By User: mgr
=> "Each word must be at least two characters long" 

Search For: tracker "client A" "client B"
By User: mgr
Re: Port Forwarding by mgr 

---

In the 1st attached pic ("case 1.jpg") we notice the tracker "registers client B as downloading" blindly, and it works because client B is connectable.

In the 2nd attached pic ("case 2a.jpg") we notice the tracker "registers client B as downloading" blindly, but the tracker information is wrong because client "B" is not connectable.

My question is : why doesn't the tracker wait for an acknowledgment from client "B" (like the "thanks mate" found in 1st pic), before it registers client B as downloading ?

[mgr]

@blackdid:

…
My question is : why doesn't the tracker wait for an acknowledgment from client "B" (like the "thanks mate" found in 1st pic), before it registers client B as downloading ?

Easy answer: the BitTorrent protocol does not require (or tolerate) an acknowledgement of such a first contact.

[blackdid]

Thanks Mgr  
Easy question, easy answer lol

First contact you said… mmm... we should ask Jodie Foster and all Star Trek Crews if 1st contacts shouldn't be full of "thank you" from both sides, to avoid a quick disconnection

[mgr]

@blackdid:

…
we should ask Jodie Foster and all Star Trek Crews
...

How about asking Bram Cohen (the BitTorrent protocol developer) about such an approach ???

[blackdid]

@mgr:

@blackdid:

…
we should ask Jodie Foster and all Star Trek Crews
...

How about asking Bram Cohen (the BitTorrent protocol developer) about such an approach ???

lol you probably realised I choosed Jodie Foster (who played in "Contact") and, more important, the Star Trek Crews (who keep on repeating in the TV series how important are 1st contacts with other species, when exchanges need to be well understood from both sides, to avoid a lack of understanding)

After all, if I already exchanged nice emails with Eugene Roshal (creator of Winrar), why not with Bram Cohen ?  

If I ever email him, I'll ask him too about the seeding status in the client, when the tracker shows a leeching status (i.e. why didn't he create a 3rd status, in case a user unselects some files in a torrent before downloading it ? For example "Partial Seeding" would be a good choice, if both client and tracker displayed it, just after the user finished to download his selected files in the torrent)

Hey, there's a post from Tim just before Mgr's "virtual talk" upper in this page, it's so great to read him.
And to look at his smiling face :hug:

[amice]

it can't be named 'partial seeding', 'cause there only can be either seeding or leeching. the status could be named 'incomplete'. even if there is no support from Cohen's side {as it is said, he doesn't plan to develope this protocol anymore}, trackers are capable to sort out these peers correctly with some software changes.

@blackdid:

In the 2nd attached pic ("case 2a.jpg") we notice the tracker "registers client B as downloading" blindly, but the tracker information is wrong because client "B" is not connectable.
My question is : why doesn't the tracker wait for an acknowledgment from client "B" (like the "thanks mate" found in 1st pic), before it registers client B as downloading ?

still the same misunderstanding over & over: 'not connectable' doesn't mean the same as 'blocked'. it means that the user has an indirect access, usually based on non-1:1 scenario. the information hence is correct. if you are in the [desc=not connectable]passive mode[/desc], you need at least 1 direct-access user to connect to and use them as a "bridge" between. the new uTP protocol in uTorrent is told to overcome even this problem. give it a try and let us know 

[blackdid]

@amice:

it can't be named 'partial seeding', 'cause there only can be either seeding or leeching…

@amice:

…but i agree that this should be called a bit different, as you say, 'partial seeding' perhaps …

---

@amice:

still the same misunderstanding over & over: 'not connectable' doesn't mean the same as 'blocked'.

My point was I didn't like a lot the tracker to immediately show client B as "downloading" (case 2a) when in fact this user will not download a single byte in mgr's diagram (case 2a)

Maybe I'm wrong, but it seems to me that you would have preferred us (mgr and me) not to use at all the words "not connectable" in case 2a ?

mgr in his title => case 2a Client B is "not connectible"
me in the sentence you quoted => because client "B" is "not connectable"

As client "B" is fully blocked, then we shouldn't use at all the words "not connectable" as you made a clear distinction in your answer between "not connectable" and "blocked" ?

[amice]

'partial seeding' .. hey, you!    ok, ok, i realized my own nonsense {and forgot to correct it in that posting}, but you can see the word "perhaps" - i wasn't sure how to call this event either. it's 'partial content seeding', not partial seeding as such, as both actions are firmly defined about what they do.

i don't know what Mgr exactly thought in his diagrams, it's all about agreed definitions only. usually it means that such a peer is NATed with 1:multi IP pool scenario {= sort of indirect access}. users used to uTorrent definitions then may get confused with the distinction between 'blocked' and 'non-connectable'. it's not the same.

normally, every solid ISP gives you 1:1 NAT scenario {in case they need to do it this way}, i.e. your private or dedicated IP address gets translated with 1:1 NAT to a public IP address. these users are always connectable. but, here comes the clue: some users share their connection with other family members or friends, etc. with cheap devices that, in default settings, are configured for 1:multi IP pool scenario. if they were clever enough, they could read manuals and set their devices to open a direct access, usually with DMZ or 'special applications', or UPnP settings. so, here is the reason why there are so many not connectable users around.

[Bonk]

I followed the tutorial to forward ports on my router. I added the static IP/DNS information in the IPv4 preferences. I turned off UPnP in my router. Tixati is approved in my firewall on Windows. I listed the ports as exception in the router firewall.

Upload doesn't work, except maybe twice a year for five minutes, for whatever reason I can't look up.

Tell me what else I need to check for.

[DirtyNick]

How do I know which port do I have?

[Pawpcorn]

Discussion on this topic is continued… here:  https://community.gaytor.rent/index.php?topic=30201.0
  This topic is now locked.

…For what it's worth... here's the standard advice I've been sending members in the past, who have written in with ratio problems, and also have turned out to NOT be "Connectable" :  MANY members have followed this advice, and been able to resolve the issue. Have a look:

....The main problem I see is that you are currently shown as "NOT connectable"

Your µTorrent is reported as not connectible by our tracker. That means requests from other peers to get parts of the file don't reach it, and in YOUR case you only have a FEW torrents that are actively seeding, which all have DOZENS of other (connectable) members also seeding... so it's going to be rare that you actually get a request for data.

Did you already set up port forwarding on your DSL modem to match to match the port used by your uTorrent program?  If you're unsure how to configure the internal settings of your DSL modem, you may need to consult a computer technician, or have alook here: http://portforward.com/english/applications/port_forwarding/Torrent/Torrentindex.htm

After you have established the port forwarding with your DSL Modem:

a) Select the UPnP port forwarding and Windows firewall exception in µTorrent's connection settings. Then restart µTorrent.

b) Reboot your modem/router (the box to connect to the internet)

You can test if your µTorrent is connectible there: µTorrent > Options > Setup Guide > select the "Network" test only and run it. The result should be a green check sign. If it is yellow/orange, your µTorrent is not connectible.

Visiting http://www.canyouseeme.org/ can also confirm the port you've chosen to forward, to confirm that it is actually open. This is a free utility for remotely verifying if a port is open or closed. It is useful to users who wish to verify port forwarding and check to see if a server is running or a firewall or ISP is blocking certain ports.

There are a good number of other possibilities making a torrent client not connectible, such as security software and the such…"

Take care,
Pawpcorn, GTRU Staff