Author Topic: Fake or not? Not sure (Read 72443 times)

Stevi · « **Reply #60 on:** May 13, 2011, 09:26:06 pm »

If you are unable to use that website, you can also try https://www.winmxradio.com/chat. Its not as good, but it is something.

White Stripes · « **Reply #61 on:** May 13, 2011, 09:58:09 pm »

Quote from: curiousminds on May 13, 2011, 09:24:17 pm

Silver Stripes, that link you gave to park in a room. It wants me to download a web browser instead. Is that what it's supposed to do? Thanks.

what that link is - is a 'filtered' list of channels... they all show rather than being flooded out by the attackers... makes it easier to find a room....

as for the browser download -- you went there with internet explorer didnt you.... (i had to check this myself cos i dont use ie) um... download something better than ie or.. try http://anonymouse.org/cgi-bin/anon-www.cgi/https://www.winmxunlimited.net/utilities/wpnlist/ (an ad from anonymouse will show over the page... just click the 'x' in the ads upper right corner to make it go away)

tho i really recommend downloading something better than ie in the long run cos there are a lot of sites out there that block it...

curiousminds · « **Reply #62 on:** May 13, 2011, 10:00:01 pm »

Thanks. That one was much better. At least it didn't ask which browser to use. Went straight into the search.

Stevi · « **Reply #63 on:** May 13, 2011, 11:10:41 pm »

Josh's is filtered, mine is not, at least not yet. I tend to only run it when the network is not being attacked, however, I have been running it for 2 days.

steed_and_emma · « **Reply #64 on:** May 14, 2011, 01:53:52 am »

Hello All

Has there been any progress made toward resolving this problem?

Should we anticipate a new program download to fix or are there any alternate short term measures we should follow?

Thanks for all your help!

GhostShip · « **Reply #65 on:** May 14, 2011, 02:25:10 am »

As posted recently

Quote

For the moment its best to read this and pass it on to others.

https://www.winmxworld.com/tutorials/wpn_attack_information_.html

jimr · « **Reply #66 on:** May 15, 2011, 08:41:06 am »

@Silver Stripes; no, it's a black desktop, and I'm pretty sure it's past warranty. I did try leaving it unplugged overnight, it lights up and can feel a little pulsing vibe - but after leaving it on a while, the light is pulsing about 2x/second and there does seem to be movement in synch with the light.

Could it be software? When I first checked the Device Manager it said there was an error #10, but no clue how to fix it. I tried deleting it in hope it would prompt me to replace it, but nothing. The Seagate troubleshooting info says that "probably the drive or the power supply has failed".

Quote from: Silver Stripes on May 13, 2011, 09:18:27 pm

@jimr; if its the seagate freeagent desk (the big white one) it most likely died from overheat... those things are in horrid cases that basically cook the drive to death (i nearly lost mine a while back and ripped the case off... it resides -inside- the computer now... lol) if you still hear the drive spin up unplug its power source and let it sit for about a day... plug it back in and try again... if its still fail and you still have it under warranty you can get a new one but youve lost the data.... if you don't care about the warranty the drive itself is a standard sata drive with a usb bridge... if your computer has sata you can try connecting it that way...

White Stripes · « **Reply #67 on:** May 15, 2011, 09:32:36 am »

if you have a different computer (laptop perhaps) try connecting it to that... do -not- install seagates drivers if prompted just let the other computer see it as a standard mass storage device..... that is if it still works....

the seagate software causes just as many problems as the overheat.... if still nothing and you know exactly what you are doing when it comes to 'wall brick' power supplies try a new one... but if in doubt in any way that the 'new' wall brick will work do -not- use it... you may blow things completely...

if all else fails take the drive out of its enclosure and connect it directly to the computer as a regular internal drive and start from there getting your data back....

posting a new thread in general computer help with the model number of your drive (so we can work this out in a thread thats relavent to the subject at hand) would be a good idea...

synesthetize · « **Reply #68 on:** May 15, 2011, 03:10:20 pm »

Concidentally or not, have you noticed we are in the WPN 10th anniversary?

wavoka · « **Reply #69 on:** May 16, 2011, 02:19:22 pm »

Has there been any progress on solving this problem?

9th Night of Theory · « **Reply #70 on:** May 16, 2011, 04:24:49 pm »

My question: How come somebody can't back-track the hacker in some way? Isn't there some way to keep him from gaining access into WinMX? My guess is he is "spoofing" which would make it a little hard to identify him as he gains access to the networks.

synesthetize · « **Reply #71 on:** May 16, 2011, 05:57:18 pm »

Nope yet, but yet there is a way to get them bored with their cheap tricks and so be the ones who laugh last by moving all to OpenNap servers for a while, until there's a concrete solution.

GhostShip · « **Reply #72 on:** May 16, 2011, 07:23:59 pm »

@ Wavoka: The IP spoofing is the core issue we face as parts of the WPN protocol are not validated and allow a low level attacker to leverage the power of the primary network, we can track them back to the attackers neighbouring nodes but we cant 100% be sure which of the neighbours it is unless we have an idea of the attackers IP beforehand .

@ Synesthetize:
I did suggest folks move temporarily to OpenNap until this issue is resolved as at least that way we have some method of holding the community firm and together but that was only suggested as a temporary solution, as we have made clear folks are working on a solution still, the theory behind the solution is one that's common sense however the implementation of the suggested protection method is not but we can all have hope and rest assured we are all doing our best here to look for further solutions and mechanisms that may be of usage, no one is leaving any stone unturned.

synesthetize · « **Reply #73 on:** May 16, 2011, 10:39:32 pm »

Could one of those stones be a new client software?

White Stripes · « **Reply #74 on:** May 16, 2011, 10:53:42 pm »

that stone hasnt burped out of the volcano yet... is still forming...

wavoka · « **Reply #75 on:** May 19, 2011, 01:50:45 pm »

Over 2000 have read thids thread yet there's nothing new? Any progress on solving the problem? I've found that what I'm searching for will likely show up before the weird files. You have to be fast and click on it before it gets drowned in a sea of hundreds of file names. Also, if you browse those who are in your qeue and whose qeues you're in they might have what you're looking for. But, seriously, it's been over 10 days. Is there nothing good to report?

wavoka · « **Reply #76 on:** May 19, 2011, 01:55:19 pm »

Quote from: wavoka on May 19, 2011, 01:50:45 pm

Over 2000 have read thids thread yet there's nothing new? Any progress on solving the problem? I've found that what I'm searching for will likely show up before the weird files. You have to be fast and click on it before it gets drowned in a sea of hundreds of file names. Also, if you browse those who are in your qeue and whose qeues you're in they might have what you're looking for. But, seriously, it's been over 10 days. Is there nothing good to report?

=============

Judst read about what's being done. Glad to see some good news. I'm still getting action on regular network and have found ways to deal with the problem mentioned above. Good luck on solving this.

wavoka · « **Reply #77 on:** May 20, 2011, 02:15:49 pm »

Did y'all do something? Or did they give up?

achilles · « **Reply #78 on:** May 20, 2011, 03:25:42 pm »

I'm trying to find out what changed as well. I would say it's most likely just a temporary cease fire. I hope i'm wrong though.

silicon_toad2000 · « **Reply #79 on:** May 20, 2011, 11:09:15 pm »

No technical solution has been provided as yet.
You all run the network so any technical solution will involve all the users, you will know when one has been completed.

It seems the attacker has stopped for now for some reason.