Good News For WinMX Network Chat

[GhostShip]

That got your attentiuon eh folks 

Ok its been a long time in happening but over the last few days we have no longer been able to detect any of the chat server and peer-cache damaging 1.x.x.x traffic generated by a caching bug in one type of chatserver.

I hope you agree with me this is good news for all users of the network and will allow users of older server types that where unable to cope with the unfamilair traffic to use them once again.

All's well that ends well I say, as usual my thanks go out to those who took the time and effort to help reduce the damage to a trickle by advising users of the problem and thanks go to those room hosts who where inadvertedly operating the problem release for their speedy upgrading, Cheers to you all 

[bu44er]

I have to agree Ghost this is good news. Less Damaging Traffic means a more stable Network. The only way is up, WinMx as had alot of bad things happen to it but is still here and here to stay.

[]2aven (R.I.P.)]

  I think it's misleading ppl to say the 1xxx ip traffic is completely gone because it isn't.It has slowed down substantialy though and around the same time as the anti-p2p orgs pulled out. I guess you didn't want ppl to see the coincidence there by reporting them seperately.

  I also think it's misleading to tell ppl it's ok to use a old discontinued server now because I think fxs still has some issues. I dont use it anymore but I helped a friend host just 2 days ago and I still struggled with it and so are some of my winmx friends that are using it. It's still dropping ppl in clumps,showing connection errors, and ghosting ppl.

[GhostShip]

I resent your claims Raven, and for your information I checked with others who also monitor this type of traffic and they have confirmed it has completely ceased, now I dont know about you but if no 1.x.x traffic is visible on the network then it is legitimate to state so.

You are also completely wrong about the timescale of the lessening of fake file flooding, this was something we detected before xmas but only recently where we shown conclusive proof of the macrovision company withdrawing from further offering this service. There is no correlation with the months ago reduction of fake flooding and the recently ended 1.x.x. server bug disruption.

If you wish to draw my character into this and accuse me of misleading people then I think its only fair for folks to know you are one of those who sit in the "stuff" room supporting WCS and its programmer, in short your opinion is jaded to say the least.


Giving people information is what we do here Raven, it will always be their decision on what they do with it, and it most certainly is not for me to tell folks what chat server they should use unless it is likely to affect all other network users in detrimental way.

[]2aven (R.I.P.)]

  First of all I dont understand why you would reccomend a server to ppl that you wont even use yourself. Last I looked ya'll were using eserv to host your help room with. There are 3 other perfectly good servers that are being updated and maintained. The longer fxs goes unmaintained the worse it's gonna get.

  Secondly, the 1xxx ip mess was something i've felt strongly about from the beginning. It's a issue i've been keeping an eye on because i've been hosting a backup room with fxs. People are entiltled to their honest opinions here aren't they.

  Dont get me wrong this is good news for winmx and hopefully all copies of the buggy server have been destroyed because any idiot or org. knows it can be used to disrupt the network so I'm not off to celebrate just yet.

[]2aven (R.I.P.)]

  I wanted to add this screenshot taken 10 mins ago. It isnt my intention to discredit ppl only to let ppl know that this still is an issue with fxs.

[GhostShip]

I agree the network now has a return of 1.x flooding Raven.

This then makes it clear folks that some lamer has decided to do this on purpose and I will spend as much time as necessary hunting them down and adding them to the blocklist, attacks against the network and its users will be treated as so, whoever you are you will be tracked down and exposed for this anti-winmx activity.

[Lagerlout666]

Thank god the caches are protected from this basic DOS attack. Their is no other way of describing what this is.

[James420]

...You think by now you'd stop trying to block people that could just be mistaken users using a server they think works great. You act as if you now get to decide who can and who can't use WinMX, banning the ones you don't like or if you THINK they're doing something wrong.

Seems as if it'd just be easier to make a basic patch for programs like FXS that just simply blocks the 1.x.x.x range...which if I'm not mistaken. You said you or someone you know was working on...like 6 months back. So now you're instead just blocking anyone that is emitting the 1.x.x.x stuff? Sounds effective for you, maybe not the few that actually don't know they're causing harm.

Then again, your method seems to be working so great. I'm sure there are people that do it on purpose since they know about the bug, so what good does it do to block them? If they're doing it on purpose, has it crossed your mind that...they can also change their IP? Even if you ban full ranges, if they're so set on doing it. They'll get around the block. So instead of just banning people from the whole WPN, why not just block the damn 1.x.x.x stuff? Although, your way seems to be working great. Driving many away from winmx. Then there won't be anyone left to worry about the 1.x.x.x flooding, lol.

[James420]

* James420 Won't be surprised if he ends up on the block list and banned on here for his last post. D:

[]2aven (R.I.P.)]

  Well I'm sorry that I come on so strong but this has always been a touchy subject for me. I think my blood pressure rises whenever this topic comes up. No one was more po'ed about having to leave fxs behind. It's not even about which server is better, it's about things like I learned to host with fxs, im comfortable with it, my bots are all configfured for it, etc.
  Anyways, this is an unfortunate situation and I wont bother asking what can be done about it cause i've been down that road before.

[James420]

Mhmm, it's just so much easier to use a server that has it blocked correctly. Such as WCS or Ouka. Makes more sense doing it that way, instead of banning the people from the WPN completely.

[Zénar]

That's true it would be useless to block the users who are sending 1.x.x.x since it would be easy to connect to the network again even if they were banned. All we can do is to block these 1.x.x.x packets directly by intercepting them from the TCP protocols because all datas are travelling through WinMX by the TCP protocol...

All new or updated programs that are connecting as a primary should block these malformed packets.

[GhostShip]

And yes James it has been noticed this new flooding started after you read my reply here,, strange eh 

If you want me to ban you from here just say so, the only person going on the blocklist however will be the network flooder operating the rogue server deliberately, and I,m still sifting through snifffer dumps to catch them, I,m very patient 

[James420]

So you're accusing me of using an old WCS, which can't even be bothered with trying to find a copy of. After I read this post? Funny, I've been talking to Raven about this for a while. Before I even came here to try and find the topic she spoke of, and she had already noted that there was flooding going on.

If you're going to blame me for this shit, at least have something to back it up...you sure like to accuse people for stuff they didn't do. Just because they don't agree with you. May as well just jump on that Pie bandwagon.

[GhostShip]

Go back to troll your friends forum James your childish talk is not fit for decent winmx users.

[]2aven (R.I.P.)]

Seriously, James has been running madness with me for a while now. This was a discussion we had 2 days ago when I was running fxs not something that started back up today.

Sometimes I think ppl get so clouded with winmx politics and drama that it prevents them from doing the right thing, like admitting when theyre wrong about something.

[GhostShip]

Unfortunately Raven thats not actually the case, despite your own messing in politics by accusing me of misleading folks and claiming I was asking folks to use FX (I did not state that at any time), you are now calling myself and two of the peer cache operators liars, just why that is beats me but it seems you have your own agenda and reasons for your claims, claims I will continue to dispute due to the fact that I myself checked the primary traffic and it has been clean for days now and this was confirmed by the absence of such traffic hitting the caches, those are logged btw so whilst we have your word I have hard figures to believe and my own eyes.


I have already made a complete list of rooms and am working my way down the list to find the problem room, if rooms either shut down or change names along with the flooding I think it will be even simpler to pinpoint the guilty party.

[Me Here]

Good Lawdy,

I'd like to clarify if i may be so bold here, No one 'recommended' using any particular server in this thread that I can read. 

The fact is some of us here couldn't agree with you more about your opinions (which yes you are allowed to have lol) about FXS, it wasn't even mentioned specifically and you could say the same for any server that is not being worked on anymore such as RoboServe or Nacs even, they don't have any built in protection for this traffic. 

Of course I would say it is safe to assume that FXS was far more widely used and ppl have their reasons for this, so this traffic (if someone could get past the faults you already mentioned and the issues with FXS bugs) was the reason some stopped using it, and because it was no longer an annoyance but a detriment to the network itself any server not protected was discouraged by us.  Now I don't think anywhere on this thread have I read for everyone to run out and download FXS and use it, I agree there are far superior servers being kept up to date, however if this traffic could be stopped and if its a bug in old wcs version then it definitely CAN be stopped, these ppl could once again go back to their chat servers of choice.

Id also like to clarify that I was also privy to seeing the tools used to monitor this traffic and was pleased to see for myself that it had finally ceased to be on the network.

Raven if your point was to inform us of something, starting out putting words in mouths about recommending FXS specifically and claiming we are trying to mislead or hide information about flooders and correlations or the lack there of between them and the 1.xx traffic, and that we are portraying what we want you to see instead of the truth,  was not the best way to go about it. 

So yes its possible (if you believe in coincidences) that suddenly today ppl started using the old wcs versions again, and yes i do realize that is quite possible, or if some lamers have read this and thought 'oh what fun, lets run the old one just to mess things up for others'  which is just as likely, then yes I can understand Ghosts passion to remove or make everyone aware of who they are doing this. 

Ghost has spent many hours tracking these ppl down having polite conversations with hosts to inform them of the problem and how to rectify it, most of which were more then happy to update to the newer WCS to help.  None of these were ever even considered to be put on the block list and as Zenar mentions it would be ineffective anyway.  I  think what Ghost means is that they need to be held accountable for this since it seems more likely at this point that it is intentional.

In case anyone has missed it the thread started as some good news for folks    
Like Raven states some ppl are quite upset about not being able to use these  unprotected servers and it has turned into yet another opportunity for some to make false claims about thousands of ppl that are on the blocklists *cough James* and the millions soon to be *cough James*  and has turned into the awareness that KMs bug in wcs will now always be a tool for lamers to attack innocent room hosts.

[ñòóKýçrÕôK]

I agree the network now has a return of 1.x flooding Raven.

This then makes it clear folks that some lamer has decided to do this on purpose and I will spend as much time as necessary hunting them down and adding them to the blocklist, attacks against the network and its users will be treated as so, whoever you are you will be tracked down and exposed for this anti-winmx activity.

  I think it's misleading ppl to say the 1xxx ip traffic is completely gone because it isn't.It has slowed down substantialy though and around the same time as the anti-p2p orgs pulled out. I guess you didn't want ppl to see the coincidence there by reporting them seperately.

  I also think it's misleading to tell ppl it's ok to use a old discontinued server now because I think fxs still has some issues. I dont use it anymore but I helped a friend host just 2 days ago and I still struggled with it and so are some of my winmx friends that are using it. It's still dropping ppl in clumps,showing connection errors, and ghosting ppl.

  I wanted to add this screenshot taken 10 mins ago. It isnt my intention to discredit ppl only to let ppl know that this still is an issue with fxs.

...You think by now you'd stop trying to block people that could just be mistaken users using a server they think works great. You act as if you now get to decide who can and who can't use WinMX, banning the ones you don't like or if you THINK they're doing something wrong.

Seems as if it'd just be easier to make a basic patch for programs like FXS that just simply blocks the 1.x.x.x range...which if I'm not mistaken. You said you or someone you know was working on...like 6 months back. So now you're instead just blocking anyone that is emitting the 1.x.x.x stuff? Sounds effective for you, maybe not the few that actually don't know they're causing harm.

Then again, your method seems to be working so great. I'm sure there are people that do it on purpose since they know about the bug, so what good does it do to block them? If they're doing it on purpose, has it crossed your mind that...they can also change their IP? Even if you ban full ranges, if they're so set on doing it. They'll get around the block. So instead of just banning people from the whole WPN, why not just block the damn 1.x.x.x stuff? Although, your way seems to be working great. Driving many away from winmx. Then there won't be anyone left to worry about the 1.x.x.x flooding, lol.

* James420 Won't be surprised if he ends up on the block list and banned on here for his last post. D:

First of all I would say that if someone wished to block anyone in the blocklist to protect this network then that would be using it fo what it is intended to be used for. To protect this network. Now if you'll notice there's like 6 hours difference in the first post of Raven's saying it's still happening and the second post she she made just 10 minutes after taking the snapshot which pretty much says she's "oneupped" Ghost on that. To which I say it's not impossible for that to happen to anyone. Perhaps since Raven caught it and Ghost and his friends missed it she could explain how she caught it so that Ghost or others won't miss it again. This is not something that can't be worked around. And James I don't know or care if it were your intention just to make your first post to flame on Ghost but it was entirely uncalled for and if it wasn't your intention it definately looked as if it were. In which case I might suggest you choose your wording more carefully next time. Do you really believe that any one individual would be banned through the blocklist without more than sufficient proof that their intentions were to deliberately harm this network? If you do then I'd like to suggest that perhaps you stop listening to KM and his brainwashing bullshit and step back down to this little planet called Earth because even for the obvious distaste and contempt that Ghost has for KM I don't even think KM is on the blocklist really. So hopefully that will put your mind at ease on that subject. We have a saying here in Tennessee goes a little something like "It is better to keep your mouth closed and let the world think you are a fool than to open it and prove the world right." Yall act right and use your own good judgement and stop relying so much on others that could care less about this network or at the very least much less than either of you do.