FS#5854 - giFT can't connect to any network

Attached to Project: Arch Linux
Opened by name withheld (Gullible Jones) - Saturday, 18 November 2006, 18:08 GMT
Last edited by Kevin Piche (kpiche) - Thursday, 24 April 2008, 02:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Kevin Piche (kpiche)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

In spite of being properly configured, and all the right ports being forwarded giFT apparently cannot connect to Gnutella, FastTrack, or OpenFT. The daemon doesn't give me any console output to indicate why, either. Have there been network protocol changes that render giFT - which I don't think is developed any more - obsolete?
This task depends upon

Closed by  Kevin Piche (kpiche)
Thursday, 24 April 2008, 02:44 GMT
Reason for closing:  Not a bug
Additional comments about closing:  It takes a long time to find working peer servers.
Comment by Roman Kyrylych (Romashka) - Monday, 20 November 2006, 16:26 GMT
You didn't mention this, so... have you installed gift-gnutella/gift-fasttrack/gift-openft?
Comment by name withheld (Gullible Jones) - Monday, 20 November 2006, 20:10 GMT
Yep, I did.

(Dang. Knew there was something I forgot to mention.)
Comment by name withheld (Gullible Jones) - Friday, 15 December 2006, 01:18 GMT
Still no-go with latest gift-gnutella. Sees network but never connects, reports no users online. I think I can guess about the problem though: when I start giftoxic from the command line I get a message like this:

[HH:MM:SS] giFT: 32XX

Where "XX" is two random digits and HH:MM:SS is the time. It's "32XX" that interests me - it looks like a port number. Maybe the daemon is using a random port as per default rather than the one I specified?
Comment by pete (drg006) - Wednesday, 11 April 2007, 03:00 GMT
I'm having the same problem.
Comment by pete (drg006) - Wednesday, 11 April 2007, 03:01 GMT
P.S. I think giFToxic starts its own giftd process if there is not one already running and that's why you use that line with the port number.
Comment by Loui Chang (louipc) - Tuesday, 08 May 2007, 05:38 GMT
I noticed in the logs when trying to connect to the gnutella it takes a REALLY long time because the records of servers to connect to were mostly outdated or defunct. It tries to connect to the server, but the server isn't there, etc. Eventually it catches on and the records are cleaned up and updated mostly. After that it doesn't take as long to connect.
Comment by Roman Kyrylych (Romashka) - Saturday, 09 February 2008, 14:33 GMT
@Kevin: ping
Comment by Kevin Piche (kpiche) - Thursday, 24 April 2008, 02:44 GMT
I think louipc's explanation seems the most likely. Plus with gift no longer being developed there wouldn't be much we could do if there was a problem. Closing.

Loading...