RE: Re: PUSH packet !!

"Philippe Verdy" <[email protected]>
Newsgroups gmane.network.gnutella.devel
Organization Ordinateur Personnel
Message-ID <[email protected]>
The file index is deprecated, as well as the name specified in the GIV
request as it's difficult to match it with a local file that the remote host
accepting this connection will request. The effective file will be specified
in the HTTP GET request by this host.

Many servants don't care about this info. The only important thing that a
host (accepting a incoming TCP connection with a GIV request) need to check
is whever it has recently sent a PUSH message to a host for which he tried
to get a connection with.

There are extensions of the Gnutella protocol that uses this connect back
mechanism by ignoring completely the data provided with the incoming GIV
request: it is used to establish a connection for something else than just a
Gnutella connection.

Note that the reply to a incoming GIV request is either to reject it or to
close it (if no PUSH was initiated, or nothing is needed from that remote
host), or to initiate a Gnutella connection asif it was an outgoing TCP
connection.

Note that if the PUSH message may be delivered through UDP, the GIV request
is implicitly sent only through TCP (there's still no connect back mechanism
that works through UDP, despite it could work as well, with a UDP-based GIV
message that would trigger the port forwarding from the firewalled servent,
without having this firewalled servent to establish a full TCP session).

Such extension would be interesting with NAT routers that support port
triggering for defining a (temporary) routing from the Internet to the
firewalled servent, and this would not absolutely require using a proxy:
If you received a UDP-based GIV message from a host, it would just mean that
you are authorized to establish an outgoing connection to the source of that
UDP message, or to send it USP messages that will reach it directly.

With such extension, you would not need ANY TCP connection to reach a
firewalled servent.

But see also the "Firewall-to-Firewall" (FW2FW) protocol extension...

Philippe.

> -----Message d'origine-----
> De : [email protected] [mailto:[email protected]] De la part
> de rakesh
> Envoyé : lundi 4 juin 2007 07:57
> À : [email protected]
> Objet : RE: [the_gdf] Re: PUSH packet !!
> 
> Thanks for detailed and very informative reply.
> 
> Why do we need to send File Index in PUSH packet ? Because in any case
> requestor need to ask for a file ones a connection is established between
> a firewalled peer and requestor. It seems that file index is useless in
> PUSH packet.It gives  wrong impression to requestor that he  will get the
> file for that file  index ones firewalled servant connect back !!
> 
> Am I correct ?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.