I switched off the HTTP proxy cache setting; I was just experimenting anyway. Apparently the entry is still listed even if proxy cache is off. I noticed it also interferes with browsing remote hosts.

Ok, henceforth I will not add IPs to the black list and let the anti-"greedy servent" routines handle leechers.

Otherwise, 3.9.9 seems excellent: loads quickly, searches are fast , and generally seems quite stable. I haven't used any other other P2P packages so I can't really compare, but LimeWire 4 looks like a winner.

In the search results window, why are some IP numbers listed in red and others in black? I couldn't find an explanation in the userguide on Limeware.com

This is explained in the FAQ. Red hosts are either firewalled or NAT-routed without port-forwarding.

This means that you can't connect directly to them; you can however download from them as Limewire sill send back a "PUSH" request along the same path from which the Query Result was received.

If that host has not disconnected from that path through which it sent its result, then it should receive the PUSH message, and then will connect itself to the downloader (you) using a "GIV" connection. Then your servent will be able to send its download request to the firewalled servent, now connected with you.

LimeWire has increased a lot the reliability of PUSH:
- first, it uses a "High-Degree/Low-TTL" topology that allows reducing the routing path between querying downloaders and replying uoloaders.
- second, PUSH messages can now traverse the cloud and get directly to the UltraPeer where the firewalled leaf node is currently connected.

A host is detected as "firewalled" (shown in red), if its IP address (indicated in its QueryHits) is local only (unreachable via Internet) for example 10.*.*.*, 172.16.*.* to 172.31.*.*, 192.168.*.* or other non routable IP addresses. Or if the replying host indicates this status in its QueryHits.

A few hosts are also firewalled but not detected like this. They are shown in black, but any attempt to connect directly to them may not give a reply or may timeout. In that case LimeWire will retry by sending a routed PUSH back to that servent.

Note that firewalled servents cannot download directly from other firewalled servents with this method.

However LimeWire implements now "Push Proxies", where an intermediate non-firewalled servent acts to relay the push and the transfer. Currently, push proxies are supported by UltraPeers, but this may change in the future to also allow non-firewalled leaf nodes acting as push proxies.

__________________
LimeWire is international. Help translate LimeWire to your own language.
Visit: http://www.limewire.org/translate.shtml

Limewire has just announced publicly that 4.0 should be released around Tuesday May 18. There has been so much improvements and bugs tests that releasing 4.0 will definitely boost the network. The Lime crew is preparing a feature list showing the many improvements that occured.

Last year most work was within the core protocol and the GUI was not enhanced a lot. 4.0 now gives more immediately visible changes for users. The core engine is still being worked on very actively to improve its speed or increse its reliability. The new anti-corruption THEX support will certainly improve swarmed downloads for better download success. Stay tuned... You should see the annoucement by an alert in your servent when it is released and starts being deployed (note that LimeWire versions can be downloaded very fast from Gnutella, with LimeWire itself, as the installer adds itself to the list of shared files).

__________________
LimeWire is international. Help translate LimeWire to your own language.
Visit: http://www.limewire.org/translate.shtml

Cool! I keep hoping LW will implement some kind of security so they could trust their Pro versions to be downloaded this way too.

btw--thanks guys for the questions and detailed answers. I'm reading along and appreciating the clarifications.

Until now, this was the SHA1 file content signature that allowed detecting malicious/corrupted/modified versions.
Now, starting Limewire 3.9.8, THEX data is also used so that corruption can be detected long before the end of the download.

LimeWire downloadable versions are found directly from Gnutella using signed queryhits, where the signature comes from a secure strong encryption key owned only by Limewire, but whose decryption key is publicly announced within the LimeWire released code. See for example what you have in your "update.ver" file. It contains some XML and that signature from your current version, and it is compared with incoming update.ver which may also contain some messages to display in the dialog box.

For now, this has just been used to indicate that a new version was available, but soon you you be able to download directly from that dialog instead of being directed to the LimeWire download site.

But already today, you can seek for LimeWire version by searching for "LimeWire" in a application search. When Limewire will be released, the main download site may become slower for a few days, but you'll be able to download the new version by searching from it in LimeWire directly, as newly installed versions will also be shared immediately.

__________________
LimeWire is international. Help translate LimeWire to your own language.
Visit: http://www.limewire.org/translate.shtml

Hmmm--Interesting. I'll try using the same installer for the different user accounts and machines on my LAN (I hadn't tried this since - - LW 2.7.13?) for the next release, and save some bandwidth.

btw--a search for "LimeWire" on 3.9.9 Pro just now only returns images from within package contents

[edit--search type was intended to be "Any Type", which returns 1037 results; "Programs" found 3 results]

I said you to search for Programs.
LimeWire shares its "LimeWireWin.exe" file with an extension specifying its version.
It's quite useful to see which LimeWire version are the most widely used (however users are still free to delete the installer from their default shared directory after the installation, so not all people will share this file).
I made such a search, and I immediately got 201 replies. Most of them for the version 3.6.9.10, followed by 3.5.8 and then 3.8.5. But even the current beta 3.9.9 could be located on multiple sources.
There remains some copies of LimeWire 2.x...

__________________
LimeWire is international. Help translate LimeWire to your own language.
Visit: http://www.limewire.org/translate.shtml

Hmmm I'm confused here I thought that LW didn't share LW installers since 3.8.x for the what's new feature. I thought that searching for LW would return the what's new results.... Philippe or Sam can you enlighten me SVP?

Merci

Edit: I think I'm right on track, I've just done a limewire search in any type and it gave results as the what's new feature... Philippe what are you talking about

Edit2: ah Phil responded 1 minute before... ak, ok a search in programs....

__________________
Liens d'intérêt /Links of interest:
Gnutellaforums en français /The House's rules you have to respect / First search the forum, then create a thread / Free software alternatives! - Logiciels alternatifs gratuits!/

I actually don't know what is done in the "what's new" search. That's something I'll look later. But traditional searches will correctly find the copy of the installer, made by the installer itself within the default shared directory.
I just verified this in 3.9.9, and this copy is there...

__________________
LimeWire is international. Help translate LimeWire to your own language.
Visit: http://www.limewire.org/translate.shtml