[Mldonkey-bugs] [bug #16507] firewalled source is treated as direct?

[Kozarezov Artem]

Follow-up Comment #3, bug #16507 (project mldonkey):

Yeah,
i know for the fact that the other peer is firewalled (because the other peer
is my own eDonkey running behind a NAT), and that it has a low-id, and i see
that MLDonkey (at least at the time when the bug was submitted) displays that
peer as "Indirect" but, as it seems, still tries to contact that firewalled
peer directly...
I thought that this is due the fact, that some part of MLDonkey code decides
on how to contact the peer based on its IP, and for my peer it sees the
public NAT IP, not the private one.
I may have been mistaking in diagnosis, but the fact is that NAT-firewalled
peer, which is both connected to a EDK server and have a KAD buddy, and have
a file to share: a) is found by MLDonkey; b) MLDonkey tries to contact it; c)
there is no sign in the firewalled peer that it has been contacted (no new
clients in queue), nor there is any sign that the peer has been contacted in
the MLDonkey interface.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?16507>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/