Further to what Andy said, make sure the server which is having issues has no players in it either by rebooting it or by putting a password on it. This is to limit the amount of legitimate traffic going through it. Once the server is empty, run the following command:
tcpdump -A 'dst host 123.123.123.123 and dst port 27015' Where 123.123.123.123 is obviously the IP of your server and 27015 is the port. If it is being DOS'd it is typical to see lots of packets coming in from the same IP over and over again with the same content. You will also see packets coming in from various legitimate game server queries but the DOS packets are generally fairly easy to spot. On Windows you can do something similar using WinDump with the same command syntax as tcpdump: http://www.mirrorservice.org/sites/ftp.wiretapped.net/pub/security/packet-ca pture/winpcap/windump/ -- Regards, Vaughan -----Original Message----- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Terry Robinson Sent: Monday, 22 February 2010 8:34 PM To: hlds@list.valvesoftware.com Subject: [hlds] Server Performance Metrics When troubleshooting an issue with our team's dedicated server I generally look at player ping, ping to other web locations, CPU usage, RAM usage, and bandwidth usage but there seem to be cases where these obvious metrics don't quite cut it. There are periods where a game server or voice server seems to be suffering from hiccups and warping with no obvious resource deficiency. Are there other metrics at which I can look to analyze issues or tools that one can use to simulate server activity to help poke at problems? Terry Robinson _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
