Author Topic: KM Actions And How They Affect You (Read 10508 times)

reef · « **Reply #60 on:** September 11, 2007, 03:03:34 am »

E-Serv is another option worth looking at.... after using FXServer for 3 years i had to
find something with this mess thats going on.... its not as fancy but has no shortage of commands
Anyways worth having a look at for anybody interested in changing

*^*Åü§§ïëgïrl*^* · « **Reply #61 on:** September 11, 2007, 04:14:09 am »

Thankyou reef. I've downloaded E-Serv. In the meantime, I found the FXS beta version, and with the third-party patch it's able to connect. I just hope I'm not going to be told to ditch that server as well... lol.

reef · « **Reply #62 on:** September 11, 2007, 05:23:54 am »

lol....... well actually FXServer right now is in the same boat as WCS.... these IP's are hitting
FXServer hosts as well.And for myself like Raven mentioned earlier in this post,my modem/router
can't hold up against this many hits and forced my connection to drop time and time again.This
is what forced me to switch to E-Serv,which so far is unaffected by these IP's that were hitting FXServer
But anyways good luck and hope you can run FXServer successfully.... if not E-Serv , Ouka,and Roboserv
are a few alternatives

..Ñøßß¥.. · « **Reply #63 on:** September 11, 2007, 06:47:00 am »

IMHO Ouka is a the best available right now, KMware free and stable, i would encourage all users to move away from WCS asap.

Scyre · « **Reply #64 on:** September 11, 2007, 05:32:55 pm »

Agreed Nobby.

BTW, Reef, I agree FX is in the same boat as far as getting affected by the problem, but it will not CAUSE the problem like WCS does... Also, Thx for mentioning E-Serv, and if it is unaffected by the WCS bug, then it may be a good switch for a lot of users.

Be Good!
Scyre

~~birdman~~ · « **Reply #65 on:** September 12, 2007, 09:26:48 pm »

Do we need to block the ip range mentioned if using fx or wcs to host with and if so how ?

Me Here · « **Reply #66 on:** September 12, 2007, 10:37:20 pm »

Humm.. just been testing sincei first posted and the problem is this, FX and any chat server other then Ouka is being poisoned by the WCS traffic and resend the same ips back out in the same way its effecting the caches. So basically unless you swith to Ouka (which Im going to do soon) you'll need to do the following...

After some testing today it was blocked successfully by using pg2, It can also be done with certain firewalls, however some of those dont block outgoing traffic and some dont allow you to add a IP Ranges.

For those with that problem you can use PG2, now I know all about those ppl going to tell me here we go again, your recommending PG2 when you've said it was evil..... but you have to understand, a few things..

1. Ive always said its not so much PG2 (peerguardian 2) that i have a problem with its the lists that are provided with it that are evil. Ive often recommended it to hosts to keep pesky users from even seeing the room in the list.
2. That using it with just the list of ips mentioned above its perfectly fine and wont block anything its not supposed to.
3. For this purpose it wont need to be updated as IPs change because they are not changing out of this range.

If you do need to use PG2 for this job here is a quick over view of how:

Download the attachment here on this post.
Open PG2, click on List manager.
Make sure that all default lists are unticked (no lists ticked).
Click on Add.
Name it, Tick File, then browse to the file you downloaded here. Select it. Make sure Block is ticked. Then Say OK.
You should then see a bazillion 1.x.x.x IPs rolling on the screen blocked.

Zénar · « **Reply #67 on:** September 13, 2007, 01:31:37 am »

Well, if some are using OutPost firewall, you can block ip range by downloading a plugin called BlockPost.

http://www.outpostfirewall.com/plug-ins/Blockpost_2007_03_25.exe

So, if you don't want to use PG2 with your outpost, I suggest to use this plugin.

~~birdman~~ · « **Reply #68 on:** September 13, 2007, 06:17:24 am »

will this i.p range also block the web site being used displaying everyones ip when they do a search or refresh their chat rooms list, if not can that be blocked with the same list we are now using with pg 2 as mentioned above please ?

~~birdman~~ · « **Reply #69 on:** September 13, 2007, 06:43:32 am »

i think for this blocking to work would every host using wcs or fx need to block this ip range to stop the attack ?

..Ñøßß¥.. · « **Reply #70 on:** September 13, 2007, 08:44:58 am »

Quote from: birdman on September 13, 2007, 06:43:32 am

i think for this blocking to work would every host using wcs or fx need to block this ip range to stop the attack ?

Or simply get all such hosts to move to Ouka, end of problem and no further chances of KM messing with the network via his Wcs. I would call on everyone reading this forum to spread the word, and let every host on Winmx know what is happening and what to do about it.

Lagerlout666 · « **Reply #71 on:** September 13, 2007, 09:38:42 am »

Its all well and good saying all move to oukar, but i dont want to, for me to change server would requier me to change all my bot coding etc, little time i have to spair, now wcs may be fundermentally flawed at the moment but add PG2 and installing FX serve, or even e serve has the choice to offer replacements so as to set up its config to run like a wcs room. So im sorry but oukar to me just isnt a viable option, unless of course the nest oukar release has the abilty of a option to run like a wcs room, ie same colours, same codes, same pass word setups.

..Ñøßß¥.. · « **Reply #72 on:** September 13, 2007, 11:32:56 am »

There are clearly 2 options Tiny, block, or change, perhaps unsurprisingly after all the recent KM crap, i would prefer users to move as far as possible away from KMware fullstop, although i do understand there may be an unacceptable amout of work for some users.

bu44er · « **Reply #73 on:** September 13, 2007, 11:52:41 am »

I know why people are saying that you might want to change, but what about the people with pre defined bots and what about people who like WCS. I would like to say come on KM sort this out we all know he thinks there is no problem.

bu44er · « **Reply #74 on:** September 13, 2007, 11:53:43 am »

I do not agree with the fact that there is a problem with WCS and KM decided not to do anything about it, but no one can make him change what he does not want to change can they.

Me Here · « **Reply #75 on:** September 13, 2007, 12:50:57 pm »

Thats exactly the point Zero, we cant make him fix this, Im one of those ppl with bots and passwords and all manor of work to change over and we are doing that now moving to Ouka, and in all likihood once that amount of work is finished will stay with Ouka.

After seeing the effects this has on the rest of the servers its clear that just changing to FX or another server like Eagles is not going to stop the problem (unless no wcs versions are in use, since the data originates from it). I hope Eagle has a moment to read all of this and decides as Ouka did to make sure his is not just getting the bad data from WCS and passing it along as well, Im not sure it is or isnt at this time.. not tested that one. If anyone else has and knows let us know here. Fedez is gone and in all liklihood will not be fixing that server for this problem or any other in the future, we have to assume that for now.

Im with everyone else I say that as much as I hate it, we must stop using this as long as he is not going to fix it.

Birdman: No that range will not block that site, so you would need to add this range:

Searchsite :207.210.117.53-207.210.117.53

~~birdman~~ · « **Reply #76 on:** September 13, 2007, 02:11:07 pm »

can i ask for a closed page on this topic elsewhere out lining what room hosts need to do, what to block and why please theres so much to read through here just want a one page so the link can be passed around to inform hosts what to do etc thanks

i use fx and no way have the time to re write bot configs etc so iam going for the blocking option not moving sever and i think most will do the same, there two thinks we need to block the attack via the fx and wcs server programes and the web site thats displaying all our ips when we use winmx thats the info i would like on a single page with how to deal with it .

bu44er · « **Reply #77 on:** September 13, 2007, 03:40:23 pm »

Well we are all still trying to decide what is the best route to advise users. At the moment the only practical thing any room host can do is Switch to another server, i know this means re writing all of your configuration files for bots but we need to save our Network not damage it further more.

]2aven (R.I.P.) · « **Reply #78 on:** September 13, 2007, 05:27:27 pm »

I noticed that there are alot of people who wont even give ouka a chance. When I first dl'ed it I said wth is all this. It does have seperate config files for motd, server, room, etc. but by simply looking things up at the help site http://www.webfrik.com/Oukahelp/ (help file is downloadable) and figuring out where your configs should be placed it's all copy and paste after that. Yes some variables need to be changed in metis but Zenars bot (ZCB) works perfectly in ouka so not alot of changes had to be made for me. I strongly recommend people use ouka if they're gonna switch because it's the only server not being hammered by the packet requests and it's very stable. I've had my room up 8 or 9 days now with not a single crash, router problem, dropping etc. I think it's closer to WCS than it is to FXS as far as commands go. It has the hidecmd and hasleft just like the latest wcs and all color codes will work by simply replacing them in word replace (ex. Word[0]="#c51#=#c10#"). This is my 1st time using ouka but my co-host has used it before so we have most things all figured out and would be glad to personally help anyone who needs it. Just post in the chat servers help section or stop by my room.

I hope this helps anyone who is still undecided.

Scyre · « **Reply #79 on:** September 13, 2007, 07:43:59 pm »

Zero has a very good point, and I hope all who read it give it serious consideration.

It may indeed be a lot of work to rewrite bots and client configs, but in the end, it is not so much to do if you really want to get serious about getting rid of the problem.

I don't know of a single room where the regulars wouldn't mind a few days to wait on bots or things to be straightened back out.
If they are there for the company of other users that they share something with, then they will STILL be there after a little bit of work on the rooms.

Be Good,
Scyre