It happens when LimeWire doesn't find any ultrapeers to connect to.

hmm...

I guess an ideal solution then for people in my situation would be to compose a gnutella.net file consisting only of morpheus users.

I don't have the expertise to do something like that, though.

or...


Anyone know where in the source LimeWire decides that ultrapeer connection in not viable and goes to peer?

That is something in which I do have some knowledge, I might be able to tweak it so it instantly assumes UPs are out. Its a lot of source to wade, though.

Fiddling with Lime for a bit, I got it back to the morp connections.

Use only one or two connections, and remove UPs when they show up. After a while, you get a .6 connection. Then raise the number of connections and repeat.

Well, if you like to keep constant watch over your connection panel, this could be your solution - however stupid it might be.

Well it isn't stupid if you need a peer connection.

Well, maybe a little stupid, but only in terms of there not being a method of automating it.

OK I think the answer lies somewhere in here or possibly here.

They could really have done a better job commenting this...

It's all in the ConnectionManager.java , if you really want to make LimeWire connect to older clients only.

Hmm, I'll take a look, thanks.

I still don't see why they couldn't make this a toggle or something, its not like it would be that hard for them, and would save a lot of work for people for whom leafing isn't an option.

'They' didn't make it an option because 'they' don't want people to become anything else but leafs or ultrapeers. Old 0.6 connections are simply too ineffective.