My files, My IP in search results

[hopalong]

Now with 4.15.4 PRO. This occurs probably version independently, about one-two times in every 3 months, therefore please don't ask to reproduce it.
"Browse host" brings no result, "download" ends with "Need More Sources".

[Sam]

When it does happen, do subsequent searches from that same session continue to show your own results? Or is it just one search and then not again?

[hopalong]

Originally it was the 3rd or 4th search attempt for the term, and doesn't occur again.

[hopalong]

...and here is again the same problem, now only after 1 week, with 4.16.2.
I see in Location column, in direct connection, in my router as WAN IP the same IP address.
I really don't understand, how can LW do this. . A simple compare doesn't work ?

[Sam]

Unfortunately, no, a simple compare doesn't work. IP addresses are shared if you're both behind a NAT, and internal IP addresses can't match because two people across the world can have the same one.

We'd like to fix every problem, but obviously some things slip through the cracks. Maybe all those people using the open source code for other products want to chip in and help?

[hopalong]

Unfortunately, no, a simple compare doesn't work. IP addresses are shared if you're both behind a NAT, and internal IP addresses can't match because two people across the world can have the same one.

We'd like to fix every problem, but obviously some things slip through the cracks. Maybe all those people using the open source code for other products want to chip in and help?

I'm not really understand you, why do you talk about internal addresses. The IP address what I talk about is my external - WAN - IP (I am behind a router), and as I know it must be unique together with the port number-I think these two are the basis of a browse host.

I agree, there are some kind of cracks always, but this one is very old. True, there's no problem from this. I only thought, after two years I speak about this.
Unfortunately I can't help, I'm retired already and don't know Java programming.

[Sam]

Ya, you're definitely right that a WAN IP/Port combo are pretty much unique. It'd be great if we could use that info to solve the problem, but it doesn't always work. Any firewalled client sends their internal address (not the external), and internal addresses are the same for different people.

I'd be delighted (and I'm sure everyone else would be too) if age fixed old cracks... but usually it's the opposite. With age comes more cracks, and we have to pick & choose which ones get fixed. The best way to make sure it stays on our radar and eventually is fixed is to add it to JIRA ( www.limewire.org/jira. )

[hopalong]

Ya, you're definitely right that a WAN IP/Port combo are pretty much unique. It'd be great if we could use that info to solve the problem, but it doesn't always work. Any firewalled client sends their internal address (not the external), and internal addresses are the same for different people.

I'd be delighted (and I'm sure everyone else would be too) if age fixed old cracks... but usually it's the opposite. With age comes more cracks, and we have to pick & choose which ones get fixed. The best way to make sure it stays on our radar and eventually is fixed is to add it to JIRA (www.limewire.org/jira).

I must note, that I am firewalled, and I see both in the location column and in direct connection my external IP. LW seems to know which address is internal (or private), writes them with red color in location column, but I think my own IP in direct connection always external, so a compare must work. Maybe you could create an option defaulting to false, to compare IP and port, if the option is set to true.

Please don't follow the old bug is good bug idea.

For your radar: see https://www.limewire.org/jira/browse/LWC-1234

[Sam]

Thanks for that JIRA. You sure you're firewalled & behind a router? The direct connection option should only show your IP address if LW detects you're not firewalled. Does the globe at the bottom have a brick infront of it?

Don't worry -- so long as something's a bug, it'll be fixed. :)

[hopalong]

Thanks for that JIRA. You sure you're firewalled & behind a router? The direct connection option should only show your IP address if LW detects you're not firewalled. Does the globe at the bottom have a brick infront of it?

Don't worry -- so long as something's a bug, it'll be fixed. :)

I have a router and Zonealarm firewall. I specified manual port forwarding in LW and in the router, and gave the needed permissions for Zonealarm, there's no brickwall, I am not firewalled !! (Sorry, didn't know what means 'firewalled' exactly.)

[hopalong]

Don't worry -- so long as something's a bug, it'll be fixed. :)

The question is: when ?

[Sam]

... when we can reproduce it. :( ... Sorry.

[hopalong]

... when we can reproduce it. :( ... Sorry.

Can I help you with some console log or any other way?

I'll try to block my IP address everytime the problem appears, (my IP changes every day). May this cause some kind of problem in some LW function ?

[hopalong]

hopalong, what do u mean with "see the title of the thread"? i can clearly read that this thread is about problems with 'search results'

No, the thread title is: "My files, My IP in search results".
Your problems are real, see the gnutella forums how to try to solve them.
The origin of most problems is the nature of the gnutella network, not the LW program, it cannot control the network after all.

[Only A Hobo]

scyriacus' posts moved to new thread in the Hangout forum ....

[Only A Hobo]

I have very occasionally found my share coming up in searches. I am firewalled. The thing I do share with hopalong is that I have an ever changing ip, perhaps this is a clue. I have once also had this occur in Frostwire 4.13.5 .... but from what I gather this little bug has been around a long time. I found it would possibly recur in subsequent searches, and re starting the programme seemed to cure it. If it happens again I shall try to get some more details.

[hopalong]

Although I am not firewalled (no brickwall), I am behind a router and firewall, using port forward. So the firewall itself is common.
Yes , this is an old, little bug, now occurs here every day, recurring in subsequent searches. I already tried to get new ultrapeers removing the old ones, but in most cases there were no change - I have the suspicion that one or more ups do this thing.

[Only A Hobo]

I am seeing more of this ... I have been doing a lot of repeat searches for rare subjects recently and all or some of my share is coming up at least once in a session. I am at a loss to find any definite cause and it is happening equally with Frostwire 4.13.5. I have tried removing all or some up connections .. which sometimes helps .. sometimes not ...

Is it just a problem for Hopalong and me? :)

[hopalong]

I am usually searching for albums or for album series, hence it occurs that I have some tracks from those, but I (LW) rarely find anything and easy to see if I find my own tracks.

I think some UP cause this.

I can avoid this, if I block my IP address, I don't see any problem so far - unfortunately my IP is dynamic.

Only A Hobo, if you have fix IP address, you could try this blocking.

If proposed already to Sam, to filter out the IP and the port if the IP is not red colored in the location column, but this is not exact, as I understand it.

It is interesting. that this occurs sometime on the Opennap network too.

[Only A Hobo]

Hopalong .. I have not forgotten this .. as it continues to happen .... and has just been reported by a Froswire user who may be able to add a bit of information. I have a dynamic IP and have blocked my ip when the problem arises .. which was your suggestion .. The Frostwire case involves a static ip .. I had previously thought it might be a dynamic IP problem .. but apparently not.

Ultrapeers should prevent this from happening .. You mentioned above that this seemed to be a UP causing this ... but I have tried removing all connections and this does not seem to help ...

[hopalong]

Thanks the info.
What can cause this? LW, the OS environment or the gnutella network - a developer could think about this, even if he can't reproduce it, and find a solution.
I think my UPs are connecting to other UPs - and when I release my UPs and then reconnect, my new UPs will find probably the same UPs in the gnutella network.
This time it was only 1 hour, and here is the problem, and from now I can only block my IP, or restart LW - nono ! this time the problem has gone after I connected to new UPs -- but with these connections my searches find only spams ! That's a real delight !
I have no idea about the OS environment or the LW, except to block my own IP - for me it would be useful, to block my IP by clicking a button in LW.

[Only A Hobo]

Hi Hopalong. I have reached the conclusion that this is to do with having a dynamic ip and reckon that by setting up a static ip and configuring all the computers that, from time to time connect to my home network that it would be cured ..probably. Banning your own ip is simple .. by just right clicking on a search result and selecting black host. I can think of no thing else to do. The other person with the problem never came back to me ... I think I'm saying that I have given up LOL :D

[hopalong]

[QUOTE=Only A Hobo;16962 ... I think I'm saying that I have given up LOL :D[/QUOTE]
_We_ can't do anything else.

[hopalong]

This occurs with 5.0.2 alpha too !

With only 3 UPs, I have to work more.

[hopalong]

Again, my good old files came as search results - it's true, this occurs much rarer than in LW4. EnchantingHawk237-37 is me: 195.56.237.37.

[Sam]

You're quite enchanting, hopalong. :-)

[hopalong]

You make this with me, Sam :)

[hopalong]

How is it possible, that viewing a file properties in search results, I see my address and the filename 3 times ? Probably it means, LW gets it 3 times - but why does it display 3 times ?

[Aaron.Walkhouse]

Is it a new search or one that has been running for awhile?

[hopalong]

Is it a new search or one that has been running for awhile?

I got my files (a full album of mine based on "album") immediately in the original search, and later when I made "find more results" I got the other results - in the case of some tracks 4 times, 5 times or 6 times. But I did at least 15 research.

[Aaron.Walkhouse]

BearShare does that too, once in awhile. It couldn't be too hard
to avoid but it's probably hard to find test cases because it's one
of the bugs that won't appear on cue. You have to wait for it.

[Lord of the Rings]

Reminds me of the inaccuracy of the Uploads figures in Library. Those figures are not accurate. If a person drops connection for a moment, then reconnects, then that figure is added to attempts & uploads figures. eg: I've had a 1.5 GB file in shares. Figures showed something like 6 uploads whereas it had obviously only been uploaded once by same person (verified by checking bandwidth used & many hours watching). And each time they reconnected the attempts figures also increased. I'd have imagined at least for uploads that it would count each individual uploader as a single figure. 'Upload Attempts' figure, well at least this gives more meaning to what it really means. So a file might show 23 'upload attempts' but 22 of them might be the same person. (My example was one of many I'd noticed, not a one off, & not related to others partially downloaded files completing. Specifically a single user.)

I'm guessing in a similar way, LW is counting each find of your ip separately. Something wrong in the way LW is treating its figures when it finds them. OK perhaps my example is rather different but roughly similar situation with how LW is treating its data for reporting back to the user. Sorry if you think my post is slightly off-topic, I just felt there was a slight similarity, such as the multiple ip's shown.

BTW I had same situation of finding my files in a search recently, though it was only showing my files, not any other results. Only happened once.

[hopalong]

BearShare does that too, once in awhile. It couldn't be too hard
to avoid

I fully agree.

At first, LW should avoid the same IP results with some code in the client. It's a very little work - filter the results for the client IP (it may be dynamic)

It is conceivable, that it is not necessary to do more, because of the rare occurrence.

And although I like the perfect solutions, in many cases it's better to do something that is not fully perfect, than nothing.

, but it's probably hard to find test cases because it's one
of the bugs that won't appear on cue. You have to wait for it.

When you say "You have to wait for it" , "you" probably means LimeWire, "I" not really can help , I think.

[hopalong]

Reminds me of the inaccuracy of the Uploads figures in Library. Those figures are not accurate. If a person drops connection for a moment, then reconnects, then that figure is added to attempts & uploads figures. eg: I've had a 1.5 GB file in shares. Figures showed something like 6 uploads whereas it had obviously only been uploaded once by same person (verified by checking bandwidth used & many hours watching). And each time they reconnected the attempts figures also increased. I'd have imagined at least for uploads that it would count each individual uploader as a single figure. 'Upload Attempts' figure, well at least this gives more meaning to what it really means. So a file might show 23 'upload attempts' but 22 of them might be the same person. (My example was one of many I'd noticed, not a one off, & not related to others partially downloaded files completing. Specifically a single user.)

I'm guessing in a similar way, LW is counting each find of your ip separately. Something wrong in the way LW is treating its figures when it finds them. OK perhaps my example is rather different but roughly similar situation with how LW is treating its data for reporting back to the user. Sorry if you think my post is slightly off-topic, I just felt there was a slight similarity, such as the multiple ip's shown.

BTW I had same situation of finding my files in a search recently, though it was only showing my files, not any other results. Only happened once.

I don't know, whether there is a coherency or not, they are bug or not, but they need an explanation - the programmer(s) should know the exact answer to these problems.