Very cool that Gnutelliums is now hosting a forum for Gnucleus, I'll try to stay up to date with what's happening here.

1.3.2 is moving along, we have some new features in store for everyone, plus some stability improvements.

I read some posts requesting more documentation, I admit we're are lacking in this area, but fortunately I've gotten lots of emails from people who would like to do it, so I'll try to set something up soon.

Thanks for your support,
John Marshall

[1.3.2 is moving along, we have some new features in store for everyone, plus some stability improvements.]
Glad to hear!

[Thanks for your support,]
Not you have to thank, we do! Keep up the good work!

Greetings......

I'm really looking forward to a new version,and addressing stability is a main concern of mine,its a great servant and I cant wait

I'm really happy to see Gnucleus here too! I've had some problems with the SourceForge forums.

Gnucleus is really some nice work! It really has potential to steal the show from some of the more commercial gnet programs.

I'm using it now in fact. One possible bug though: it seems to not want to push when attempting a download from some addresses. No rhyme or reason I can see - sometimes the push works, sometimes it doesn't. However once I find a "unpushable" host it stays unpushable - even if I do a new search and download or restart Gnucleus. In such cases I often have to switch to Gnotella to download the file.

[However once I find a "unpushable" host it stays unpushable - even if I do a new search and download or restart Gnucleus. In such cases I often have to switch to Gnotella to download the file.]

Hallo:

I tried if this bug 'crawls' here also, but it was not possible for me to reproduce it. Every unpushable host I found was unpushable with Gnotella too, but I fear this will not help you further, for a non-occurence is no proof. But I will try further, if I could reproduce it I will let you know.
Did you report this already at sourceforge bug report form? You said you have problems with the forum, if you have problems with the bug report form also I will report it for you, if you want.

I think the coordinator [swabby] will read this anyway, (he has joined recently, even as moderator :) so maybe it is already known...

Greetings....

I did post it into the SourceForge bug forum but couldn't create a proper login to do so.

The bug is hard to pin down because it only happens under some unknown situations. Try looking for this: First the remote host should show as "Available" and "Firewalled" in the extended info (wish this was more accessible BTW, sub-folders like LimeWire uses would be nice for showing individual hosts).

Downloads will try a regular connection which will quickly fail after a few seconds - the delay normally required to wait for a push reply will be absent. It's as if no push attempt is made at all. These are addresses that show as a red "Available" or "+Available" under Gnotella.

Really I can't tell if the remote IP address, my IP address, or just some left-over pointer or flag value causing the trouble. It happens fairly often, but hard to notice since at first glance since it looks just like any other failed download. The give-away is the absence of any delay before the firewalled connection attempt fails (a push must wait about a minute for the server to reply).

Every host that you fail to download from is sent a push request.

Gnucleus does not wait for this push request before trying the next host. If the host responds to the push, then Gnucleus will drop what its doing and start transfering from there.

This process speeds the time in finding someone to download from, push works fine.

I'm not so sure. I mainly notice this when there's only one host in the group. I'll try and download a search result, the download starts, waits a few seconds and is then marked as failed. I've never seen a download start after that.

I can see the value of not waiting before trying other hosts, but are you sure there isn't a problem when there's actually no other hosts in the list to try for that download? Does it know it has to hang on for a bit before giving up entirely?

When a download batch only has 1 host in it, or is at the last host in the list you'll see 'Checking Firewall...', this is the send push / wait for response process in action.

I guess this is what I wasn't seeing happen all the time.

When I see the "checking firewall" message the download will probably work (at least as well as in other clients), but sometimes the download will fail after only a few seconds - without ever showing this message.

I'll check some more to see if I can find any specific examples. Although it's something that's hard to find when you're actually looking. ;-) To be honest I haven't seen this in the latest "evolved" version (1.3.1.0) I'm using, but I haven't used it to download much yet either (mainly because of the stability problems).

Actually you've made me hopeful I'm completely wrong and it's been fixed already. ;0)