Here's a possible bug in Gnucleus 1.4.2.0. I've noticed that on the Statistics window's Memory tab the number of upload sockets seems to increase over time. After running Guncleus overnight it's now up to 63 for example (I have two actual uploads going). Along with this, Tiny Personal Firewall's connection window shows a ton of sockets listening and bound to specific addresses that never seem to go away and the system gets rather slow.

At first I thought this was a TPF bug (showing sockets that didn't exist), but now I'm wondering if perhaps Gnucleus is opening up new sockets (for example when a push is requested) and not closing them all the time? Also after running overnight, I'm showing one download socket that won't go away even if I kill all my downloads, so perhaps something's getting lost there too...

If TPF's own status window is to be believed (and I'm not really sure it is), these sockets hang around even after Gnucleus is closed. Odd...

You are correct. The same thing happens to me, I highly doubt it's Tiny's problem.

The number of upload sockets you see in the statistics window is not actual open sockets. That number is actually the number of upload 'shells' which contain upload sockets, but only when an upload is going. If an upload is pending or closed or completed, the socket in that upload shell is deleted.

Until version like 1.3, there was no shell encapsulating the sockets so I probably need to fix the wording in the statistics.

You are right though, there are some problems with sockets. Some mine, some microsofts, there is a new developer on the team with a lot of windows sockets experience and I've asked him to start going over the code. We hope to resolve these problems soon, getting sockets stable, will make gnucleus extrmely reliable.

Closing sockets properly is another issue, it wil be fixed. An improperly closed and deleted socket can linger in windows resources for hours.

There seems to be 3 or 4 issues with sockets, first opening too many too quickly causes an "out of memory" box to pop up, hitting the disconnect button seems to fix it, the box stays away after you clear it and Gnucleus continues working...


The total number of opened sockets reaches a limit per windoze session when I get an "illegal operation" in MFC42, this also seems to corrupt the TCP/IP stacks(s) since I can maintain or even re-establish a dial-up connection but no data will pass - even ICMP, including the DCC intranet connection, it kills the NetBEUI (udp 137-138, tcp 139) along with it, only restarting windoze will cure this

I *get the same thing* with the original Gnutella v.56 if I open a large number of connections a few times...

The weakness in windoze's sockets seems to be showing here (GetRight & Teleport along with SOCKSCap & VSOCKS all show this problem only if many sockets are opened fast)

note that I get an illegal operation box (which only exits Gnucleus) and not BSOD however the effect is the same - windoze must be restarted (including the network connections must be brought up in the right order otherwise it sets "default" IP's as it goes (the 192.168.55.x range)

This is a 5.min process on my hardware (firewall, dial-up, DCC, proxy, client DCC, dial-up server, dial-up, serial bypass, route add(s), proxomitron, browser) - then launch gnut on the gateway after this...

Reliability is important to me, I've found Oasis (which appears to be almost exactly the same as Gnucleus) and was wondering if you could tell me (or direct me to a specific URL) anything about it.

I swear it runs faster, seems quite stable, uses less resources (it's able to run without thrashing the HD for example) and has a few extra features

(comparing to 1.3.5 and 8.MB RAM wi***OSR w/ dun & winsock upgrades)

I click on updates/notes and nothings there... There doesn't seem to be any documentation for it