Is WCS Still Causing Network Disruption ?

[..Ñøßߥ..]

Hey Silver Stripes, this was my point we KNOW an older version of WCS causes this, we KNOW some rooms are likely still using this version, we KNOW km isnt exactly falling over himself to ensure WCS is watertight. So it seems to me if we rule out what we KNOW by getting WCS off the network, then anything that remains MUST be coming from another source, a simple process of elemination..........

[White Stripes]

well... good luck in getting the stubborn to help in that endevor...

[Snick512]

I'd like to say.. that Eagle (creator of E-Serv) has patched his server against that 1.x.x.x attack.

And to GhostShip; You are over reacting, this is not all KM's fault... there is something else creating these attacks, as I've tried to point out to people in winMX World several times....the only person in WinMX World that offered to take a peak was Mrs Toad.. I told her I'd post it somewhere myself. I did so. And the only person that went with me was Tiny.

I've kept an eye on WinMX a few weeks ago, and seen that there are other IP's out there that are attacking the network with floods... of either fake files, or just hosting bad primaries.

I've also seen mass room drops, and Have had the logger on while these mass drops happened, and nothing of the 1.x.x.x showed up because it is blocked in my firewall.. However, I will not release any IP's.. that showed up before and after the room drop.

Another thing... I think that you guys need to lay off Tiny, and KM (and you know who you are).. because all they are doing is using their common sense. And James, power to you, even if you are a little confused with how things work, at least you are trying to help.

[GhostShip]

Snick I am always pleased to hear how things may look to others but what I personally would rather hear is some tech info brought to the table to dispute any claims I make, it does no one any good to say "I,m right/your wrong" unless facts are shown that others can replicate and see for themselves the problem and its effects.

If you can re-read my posts again you will see that I am asking KM to do what he can to ensure there can be no further blame of WCS, I,m asking him to use the info he has to ensure those on older versions are updated or blocked from connecting to the network, I have received information back that this is now occuring and am happy to hear this, I hope you share my sentiments.

Tiny is not under attack here btw, he like yourself stated something that I found strange and I merely asked how he was able to detect what he made claim to have detected, I have not heard back on any method and will speak to him privately as its likely he may not want to tell the whole world.

KM whilst being a pain sometimes has been a good friend to us here at the world and to winmx in general, lets be honest when your held in such high regard any acting out of turn or show of anger is likely to be viewed as something worrying, let us hope with his efforts now underway, we can move on to locating any nodes spreading this traffic and lock them from the network, it was not the wish of anyone here to drive folks from WCS but to ensure folks would leave the playing field open to make specific detection of the problem causing nodes easier, this looks like where we now are.

[Lagerlout666]

The removal of bad WCS versions is a welcome sign and the simplest method is this, Load up Xnet stat/wireshark or any tool of your liking, and watch everynow and again oukar drop connections at the same time. Now we all know that a rooms stability is in its primarys, if the server is unstable what chance has a user got of staying in the room. Now i dont know how oukar is blocking the flooding traffic, an i had not heard of this problem before the addition of the blocking all though i have not tested it in previous versions. But back to your chosen network tool oukar will drop nearly all of its primarys in one hit. Now if this is some sort of rotating tool christ one primary every now and again would suffice. But dropping down to one primary before loading anymore is dicing with death in my eyes.

Now i suppose i best give you what tools i use, so we can rule out any sort of problems with my connection or anything like that.

Xnet-stat was the tool i used for visually seeing the conenction drops. I have a router in bridge mode so as to loose the restrictabilities in many connections coming towards my computer caused by a router, straight ethernet connection from computer. And a brand new machine running XP with all the nessicary updates/ tcp patch set to 999999. I avarage speeds off 600-700k apart from at nights at the moment but thats another story.

I have hosted succesfully many times on FXServe, WCS. I run a 1600 strong open-nap server and as always a peercache. All on this machine and running at the same time. I see know such dropping of primarys in WCS or even FXServe. Now that is the simplest way for everyone to test and either confirm or disprove what i personally have seen myself.

And as for quicks, we never normally see eye to eye, we are both to are peril highly strung when it comes to winmx. An sometimes i think i enjoy it when he blows his top ;-D. That is something that will never change for as long as we are both involved with winmx. But it doesnt mean we cant work together when the muck hits the fan. If it wasnt for half the hot heading i think sometimes nothing would get done round here lol.

[MinersLantern]

Now...
I keep seeing 'older version' of WCS does the gooftard 1.x.x.x thing...
which version is the older version? (on wcs 1.81 atm, which also does the 1x thing)
182 is available, but I dont wanna shut off everything just for another update.
Esp since 181 'cured' the 1x problem... until lately.