Swanny-CG

I found the logs, they just weren't refreshing in the web interface. Here is the last bit I tried with a md5 interval of 300: [11.27.2011 18:51:43] VIOLATION (IGNORING QUERIES) #9013: Swanny-CG (slot #17) Ignoring MD5Tool Queries [519167e3e1c6b18cdeeeb25f784997a6(-) 24.7.127.40:60450] [11.27.2011 18:59:09] VIOLATION (IGNORING QUERIES) #9013: Nestor Kirchner (slot #5) Ignoring MD5Tool Queries [dbf2d1a129d383b63f2a7a7830bb6101(-) 186.18.36.175:1750] [11.27.2011 18:59:09] VIOLATION (IGNORING QUERIES) #9013: killroy (slot #8) Ignoring MD5Tool Queries [0afb4c9e22e42a871a3fe4fdbe17b657(-) 76.16.130.228:4333] [11.27.2011 19:10:48] VIOLATION (IGNORING QUERIES) #9013: AIDS (slot #4) Ignoring MD5Tool Queries [5834e8b93e90acfa93b20e426e5bb01c(-) 96.61.170.53:3586] [11.27.2011 19:11:21] VIOLATION (IGNORING QUERIES) #9013: Fullfaulkner (slot #12) Ignoring MD5Tool Queries [23cfe0d284d7a8253fcd7b283e4c363d(-) 173.32.219.212:1270] [11.27.2011 19:11:37] VIOLATION (IGNORING QUERIES) #9013: BloodclanScourge (slot #19) Ignoring MD5Tool Queries [ae4d14cec71a8d972c7c7325f1b9df4b(-) 173.49.167.65:1058] [11.27.2011 19:12:08] VIOLATION (IGNORING QUERIES) #9013: Reggiano (slot #7) Ignoring MD5Tool Queries [8fd1935b1f44160926005ca25192d7c0(-) 204.195.3.227:1573] [11.27.2011 19:20:54] VIOLATION (IGNORING QUERIES) #9013: 3ANDREW (slot #11) Ignoring MD5Tool Queries [f73bb194bfd8bd734223d21fed55eb6a(-) 184.32.94.68:50208] [11.27.2011 19:24:52] VIOLATION (IGNORING QUERIES) #9013: Reggiano (slot #5) Ignoring MD5Tool Queries [8fd1935b1f44160926005ca25192d7c0(-) 204.195.3.227:1661] [11.27.2011 19:25:13] VIOLATION (IGNORING QUERIES) #9013: [OWiH] Pisterio (slot #8) Ignoring MD5Tool Queries [4c7237dfb530494f49fbcc7f5501880d(-) 94.248.221.142:2211] [11.27.2011 19:30:22] VIOLATION (IGNORING QUERIES) #9013: Cpt. Paul [uw] (slot #11) Ignoring MD5Tool Queries [e6d1e1a8334d671d5ad1909cd0d8c2fb(-) 96.253.97.33:3396] [11.27.2011 19:35:05] VIOLATION (IGNORING QUERIES) #9013: -=OL(fr)=- (slot #7) Ignoring MD5Tool Queries [65b6519f4ad19502179623864131393e(-) 79.86.120.27:4597] Should I keep trying higher numbers until it goes away or do I need to pick between having this and turning it off, do you think?

I believe I did try it back in the day with a single map (I seem to remember Gazala or El Alamein) but it's been long enough I won't swear to it. All of our errors are 9013s but yesterday we had 12 in one hour. Today I re-implemented it and when I joined I started rubberbanding really badly and I got kicked for ignoring md5tool queries but there isn't an entry in the sv_viol.log - should I be looking somewhere else? I see the ones from yesterday in there. I changed the md5 timeout to 300 instead of 200 and I only saw one person get kicked so far but is that all I can do (other than turn md5 checks off completely)? Thanks.

I hope it's not inappropriate to say this here but if you copy the map rfas and overwrite the dc versions, you will have the low-fog versions running client side. Thanks for the tip on the typo. Any other ideas for avoiding the kicks? Thanks!

I PMed you the info. Incidentally, people are still getting pb kicks when I include the pbsvuser.cfg file. Is there something else I can try? It's a majority of my users getting kicked, and regularly. Thanks -

I made the change in my pbsvuser.cfg from 50 to 200. I have an entry in my pbsv.cfg that says pb_sv_uconignore "pb_sv_md5toolfreq" Should I remove that or leave it? One more question - I'm trying to add an entry for BFHD and I used to have a cheat sheet for adding entries, what the w did vs. a, but it seems it was lost. I looked in the information center and tried some googling but I don't see any info on it - do you have a link handy that I can read to get it? Edit - I just found it here: http://evenbalance.com/index.php?page=md5tool.php I'll post back with how it goes on the server, thanks for taking the time to help.

Hi guys, I got the pbsvuser.cfg from the master config index. When we implement it we get a BIG percentage of players that get kicked for ignoring client queries. We were running streaming and had the MD5 config implemented for years, and everything was fine. The last big exploit crashed our server many times before the fix came out and suddenly people were getting crazy pb kicks that seemed to relate to MD5 checks (it's been a while, I don't remember the errors from then). We would usually get things working again but finally even disabling the MD5 checks didn't help; people were still getting kicked. We wiped and reloaded the server (linux on gameservers) and got streaming again. Every time we add in the MD5 checks though, almost our entire population starts getting kicked at some point for violations. I'm not *positive* but I think the majority are for ignoring client queries. Do you guys have any suggestions? I had added in a kick for Battlefield: High Definitiion but even took that back out and it still kicks people like nuts. I'd like to have the Md5 checks in but not if it kicks everyone, obviously. I did search before posting but I don't see anything that looks like the ticket, and like I said, we just reloaded the whole server. Thanks, Swanny