Gnutella Forums

Gnutella Forums (https://www.gnutellaforums.com/)
-   General Discussion (https://www.gnutellaforums.com/general-discussion/)
-   -   Every transfer queued? / Export IP issues (https://www.gnutellaforums.com/general-discussion/12602-every-transfer-queued-export-ip-issues.html)

Lurkah June 20th, 2002 09:22 AM

Every transfer queued?
 
Just set up a couple of instances of Phex on a private network but every attempt to download just results in 'Queued'.

I see no restrictive settings in the options, no reason why it shouldn't get on with it. Anyone have an idea?

GregorK June 20th, 2002 09:49 AM

Check your download settings:
- Total parallel downloads and
- Max parallel downloads per file

If this is not solving the problem you can try to turn on debug output

If you set
loggerVerboseLevel=0
and
logType=2
in your phex.cfg file Phex will generate a phex.log file that contains detailed statements of what is happening during download.

Don't forget to set the values back to get much better Phex performance!!!
Default values:
loggerVerboseLevel=6
logType=1

You might also like to display the log output on a console.
Set the value:
logToConsole=true
Use Phex_debug under Windows to see the console.

Gregor

Lurkah June 20th, 2002 10:00 AM

I'll try this out Gregor but I did notice something.

The client which I'm using as a server type thing (it's not connecting to anyone else), says My Address: 127.0.0.1

Now I notice that connecting with another client to this server works fine. Then suddenly the My Address: changes to a real correct IP. Interesting.

Now I noticed that when a download was happening, it listed the host as 127.0.0.1. This didn't seem right.

Do you think it likely that the process would be confused if Phex didn't know what IP address it was?

Oh and there's no phex.cfg, I created one with those lines but still no log file. This is win32.

Lurkah June 20th, 2002 10:15 AM

Problem solved buddy. I was right. Phex was confused and didn't know its IP because it hadn't connected to anyone to get a response which it gets it's IP from. (Same process as those dynamic DNS clients discovering an IP even though they're behind NAT).

The solution was sneaky. First allow Phex to connect to the open GNUTELLA network. That'll get Phex to learn it's IP. Then disconnect, change to the private network and bingo. Everything is fine.

Gregor you might want to save that one for some documentation or maybe put in a field to enter a real IP address. This was what I assumed (wrongly) that Export Host IP As: would do.

Lurkah June 20th, 2002 01:13 PM

This is weirder. The Export IP actually works for other people. It didn't work on that machine I was using as a server.

So it looks like that's what it was for after all. Gosh some docs would be nice ;)

GregorK June 26th, 2002 01:19 AM

Hi...

thanks for the nice observation.
I debuged the problem a little deeper and changed the behavior.

I hope this fixes the problem and you can see it work better in the next release.

Gregor

GregorK June 28th, 2002 07:35 AM

To explain the issue a little better I wrote a little doc about it.
http://phex.kouk.de/exportip.htm
I would be happy if you could review it and tell me what I missed to explain or what I should add from your experience.
I'm don't have much knowledged in all this different IP issues and appreciate all the help I get to document Phex better.

Gregor


All times are GMT -7. The time now is 01:26 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.

Copyright © 2020 Gnutella Forums.
All Rights Reserved.