Re: Does the Push message still exist?
"wwiltse25150" <[email protected]>
| Newsgroups | gmane.network.gnutella.devel |
|---|---|
| Message-ID | <[email protected]> |
Thanks for the good information. I believed that using UDP was a programmer's preference and not an accepted standard for certain messages. I used TCP exclusively in my application so it makes sense I wouldn't see UDP PUSH messages. That brings up a few more questions for me: 1. What port do I listen to so I might catch a UDP message? Is it the same port I'm connected to other ultrapeers on via TCP? 2. Is there any difference in the PUSH message structure sent vis UDP? I'm just wondering if there will need to be any changes in my code that increases the hops and decreases the TTL value. 3. When the firewalled servent receives the PUSH message, will they respond to the requesting computer using TCP or UDP? Thanks again! --- In [email protected], "Philippe Verdy" <verdy_p@...> wrote: > > Try runnin your servent from behind a NAT router, without configuring it > with port forwarding. PUSH messages will be sent to you only in this case, > and if you have something interesting to share so that some people will > request you this way. Your servent should then run as a leaf node, and it is > the Ultrapeer yo which you are connected that will forward the PUSH message > coming from other people. > > There's not a lot of PUSH messages. But if your servent runs as an > Ultrapeer, you should see more PUSH messages coming from anywhere, mostly > via UDP, and that your servent should formward to the firewalled node > connected to it via TCP. > > So it's probable that you don't implement Gnutella via UDP; PUSH messages > are more frequently sent via UDP now, they transit by TCP now only on the > last hop from the ultrapper to the target firewalled leaf node. > > If you support Gnutella through UDP, may be your ISP is filtering incoming > unsollicitated UDP messages coming from random sources that you have not > sollicitated directly. I know that mobile ISPs (through GPRS or UMTS) make > such limitations, but this is probably to avoid costly traffic for their > customers (because the traffic on such connection is billed above about 50MB > to 100MB per month, and P2P can easily exhaust this limit). It's probably a > bad idea trying to run a P2P program over a mobile connection.