Freezing problem clue.

The Seeker · #1 September 10th, 2001

I woke up to a frozen XoloX. I was running the debugger, but I couldn't understand what was going on past the fact that it wasn't in a small infinate loop so far as I could tell.

What I did to was run a netstat to see who I was connected to, and lo and behold, I saw this:

Code:

Proto  Local Address          Foreign Address        State
TCP    computer:4414          127.16.255.17:6346     ESTABLISHED
TCP    computer:6346          127.16.255.17:4414     ESTABLISHED

Which I assume is very very bad, considering that this is a loopback address. Somewhere in your code I think you made it so you can't connect to your own IP, but it seems that some people are 'force real IP'ing to be a loopback address, and it's killing XoloX.

Pasman · #2 September 10th, 2001

Hi Seeker. Thanks for this useful tip.

>Which I assume is very very bad, considering that this is a loopback address. Somewhere in your code I think you made it so you can't connect to your own IP, but it seems that some people are 'force real IP'ing to be a loopback address, and it's killing XoloX.

I will check the outgoing HTTP download, outgoing gnutella and HTTP push for valid downloading IP's. Maybe there is a leak somewhere.

Greets,
Pasman

l0ts · #3 September 10th, 2001

I've been having same problem with loopback addresses on 98 and 2kpro, hoped it would go away with 1.11 upgrade from 1.09 but it didn't.

Moak · #4 September 11th, 2001

Hi,
following Seekers idea, I noted every open connection after a crash. I had 3 crashs the last days:

Code:

  Proto  Local Address          Foreign Address        State
  TCP    computer:1469          127.0.135.5:6346       ESTABLISHED
  TCP    computer:6346          127.0.135.5:1469       ESTABLISHED

  Proto  Local Address          Foreign Address        State
  TCP    computer:3409          computer:6346          ESTABLISHED
  TCP    computer:6346          computer:3409          ESTABLISHED

  Proto  Local Address          Foreign Address        State
  TCP    computer:1965          127.187.8.70:6346      ESTABLISHED
  TCP    computer:6346          127.187.8.70:1965      ESTABLISHED

Yeah, there must be a dead lock when XoloX connects to loopback (127/8) or his own IP, a get/push freezes XoloX in that case.

Cya, Moak

PS: Propably there could be another dead lock, when you use multiple IPs or a misconfigured router.... so that a private network address in your LAN points back to the Xolox host. It might be worth to test this case.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
I really haven't got a clue!	Loops	Getting Started Using LimeWire + WireShare	2	February 24th, 2007 11:59 AM
not a clue	cobalt	General Windows Support	1	August 13th, 2005 04:59 PM
Same problem.....more ppl please respond to my freezing problem!!	bomb13	General Windows Support	3	August 7th, 2005 03:06 PM
A clue please?	ST	Open Discussion topics	0	November 9th, 2002 02:15 PM
not a clue	thumper71	General Discussion	1	April 14th, 2001 02:53 AM