Sorry to report this, and maybe it's just me, but in the beta version of 1.3.5.1 and now 1.4.0.0 push downloads seem completely broken.

In these versions I've yet to see a push reply of any kind from any server in the extended info (even a busy reply), and no firewalled host has ever worked. Yet if I load up the older version I see the very same servers respond to the push (at least until the push route dies).

There was a bug with re-searching Swabby fixed in 1.3.5.0, but sadly, perhaps the fix is worse than the disease.

I'm using V. 1.3.5 and I had a MP3 pushed to me this morning from a firewalled intranet IP (10.x.x.x)

Remember that you cannot connect to the host at all directly and your push request has to make it's way to it through it's peers (whoever it's connected to)

This means the success of push depends not only on you & the host but also whoever else they are connected to..

This makes push not very reliable but the option of last resort. If your request didn't make it there you wouldn't get any status (server busy) either plus other factors like max outgoing connections - D/L's exceeded ( normally it will at least allow beyond the limit for such replies or give you a shot of hosts then disconnect but with push you may not get *any* response at all... ) Really you can only make the request and only hope :

1.) it circulates back to the host through it's peer(s)
2.) it isn't busy - may not respond at all then
3.) is itself configured properly (usually firewall settings)

My experience is no reply at all until actually ready & willing to push the file to you - your end just sits there "in the dark" re-trying the request until that time - likely by the time you tried the older version that host had a slot free for you...

The file I got - it totally ignored me for *4 hours* then suddenly the file came... I was host hopping the whole time hoping to find a common peer, the file came right after a search turned up that host again.

That means I finally hit one of it's peers who could relay the request for me AND it was no longer busy *at that time*, while it was busy there was no reply at all...



Some of the servants ports fall outside the "temp port range" (1024 to 5000) and my firewall was blocking a few push attempts until I noticed that ( my firewall is configured to be "transparent" to Gnutella net yet block DNS/evolving/IRC so pushes coming in above 5000 were being blocked.. )

I've seen Gnutella servants with ports as low as 1 and as high as the mid 40,000's (normally source ports should/would be restricted to above 1024 to 5000 or to upper limits of most hosts - usually 9000 or so)

I allow only 1024 to 5000 source and 6340 to 6360 on my end generally - I'll make an exception for the occasional important file or allow up to 9000 or so too..

Push bug has been found and fixed, thanks for the heads up. This will be part of the very close release of 1.4.1.

Here's another one for you to fix for the 1.4.1 release:
The Shared Files window does not update the hit list on
my files. I have to close the window and open the window
again to be able to see the update.
And of course: the Retry download after XX seconds
does not work either.

When searching for files I often get 2 or more hosts. The problem is that often one host is listed as two or more.

The shared files problem will remain until the shared files code is re-written. There was a problem with the share thread notifying the share window and it effected stability. For that reason it was disabled, and will be re-enabled at a later date.

Evolved to 1.4.1.0 today and the push is working great again. In fact everything seems to be working really well in this version.

Thanks, Swabby, for the great work!