[hlds_linux] Pointers for setting up a TF2 server in a XEN appliance
Hi, We run a TF2 server on a ClearOS-machine today (CentOS 5 based OS). We would like to learn more about virtualization, specifically XEN cloud. Anyone here have any pointers on which OS to run a TF2 server on in a XEN appliance? General setup pointers would also be nice. Thanks, oGre -- =MUPP= oGre | o...@muppfarmen.se | http://muppfarmen.se ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Pointers for setting up a TF2 server in a XEN appliance
We have been using Fedoracore, CentOS and now debian witch I prefer as gameserver OS. I belive its a better OS then the first 2 for srcds servers and we are using both rt and zen kernels from http://www.ulrich-block.de/ its possible to download pre compiled kernels or compile your own (witch is the best). Peter -Ursprungligt meddelande- From: oGre Sent: Friday, January 07, 2011 9:42 AM To: Valve SRCDS_linux list Subject: [hlds_linux] Pointers for setting up a TF2 server in a XEN appliance Hi, We run a TF2 server on a ClearOS-machine today (CentOS 5 based OS). We would like to learn more about virtualization, specifically XEN cloud. Anyone here have any pointers on which OS to run a TF2 server on in a XEN appliance? General setup pointers would also be nice. Thanks, oGre -- =MUPP= oGre | o...@muppfarmen.se | http://muppfarmen.se ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Pointers for setting up a TF2 server in a XEN appliance
are those kernels outperforming redhat mrg? As for now I've yet to find a platform better rhel mrg... maybe it's just me used to rhel and would never run vanilla patched kernels :P I prefer to have them take cares of the updates, stability and compatibility ^^ On Fri, Jan 7, 2011 at 1:05 PM, Svensk Ljud Ljus Produktion i...@teaterljud.se wrote: We have been using Fedoracore, CentOS and now debian witch I prefer as gameserver OS. I belive its a better OS then the first 2 for srcds servers and we are using both rt and zen kernels from http://www.ulrich-block.de/ its possible to download pre compiled kernels or compile your own (witch is the best). Peter -Ursprungligt meddelande- From: oGre Sent: Friday, January 07, 2011 9:42 AM To: Valve SRCDS_linux list Subject: [hlds_linux] Pointers for setting up a TF2 server in a XEN appliance Hi, We run a TF2 server on a ClearOS-machine today (CentOS 5 based OS). We would like to learn more about virtualization, specifically XEN cloud. Anyone here have any pointers on which OS to run a TF2 server on in a XEN appliance? General setup pointers would also be nice. Thanks, oGre -- =MUPP= oGre | o...@muppfarmen.se | http://muppfarmen.se ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] tf2 denial of service - please do something!
box keeping up :) 50k packets dropped in just 15minutes Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 346357 17999035 ACCEPT all -- * * 0.0.0.0/00.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 12 604 DROP all -- * * 0.0.0.0/00.0.0.0/0 20 minutes later: Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 396253 20611768 ACCEPT all -- * * 0.0.0.0/00.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 50483 2675483 DROP all -- * * 0.0.0.0/00.0.0.0/0 another box of ours that generally suffer a lot of is now reporting: Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 52 16966756 ACCEPT all -- * * 0.0.0.0/00.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 563098 29844034 DROP all -- * * 0.0.0.0/00.0.0.0/0 dropped accept ... nobody complained yet... so looks like its holding :) thanks for your suggestions 3 Il 07/01/2011 01:19, frostschutz ha scritto: On Fri, Jan 07, 2011 at 12:36:10AM +0100, Marco Padovan wrote: hashlimit was exactly what I needed! Set it up correctly ... will see tomorrow what will happen :) Great... :) My own box runs without iptables and TF2 servers without mods. No problems so far - I'm not running anything well known (small clan and idle servers) so it seems the DoS is directed to specific servers only... then again I probably wouldn't notice as the clan servers are empty most of the time and the idlers don't complain much. Regards frostschutz ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] tf2 denial of service - please do something!
On Fri, Jan 07, 2011 at 08:09:40PM +0100, Marco Padovan wrote: 20 minutes later: Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 396253 20611768 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 50483 2675483 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 If the number of dropped packets keeps rising slowly here, you are probably dropping legitimate queries. Maybe the limit is a bit too low then. Also consider using a larger burst. The burst will allow short, random spikes, but under actual and constant DoS, the limit will still be respected, same as without burst. I'd try limit 20 burst 40 here and see how that goes. You can be generous with burst as it will vanish completely during a DoS attack anyhow (and it will take 40 below-limit seconds to recharge). another box of ours that generally suffer a lot of is now reporting: Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 52 16966756 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 563098 29844034 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 drop accept is to be expected during a DoS attack. nobody complained yet... so looks like its holding :) Test it yourself - see if you can get a complete server list using the standard steam server browser. If half of your servers are missing there most of the time (while there is NO DoS going on), chances are your limit is too low. Regards frostschutz ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] tf2 denial of service - please do something!
I thoutgh about that too... but monitoring the situation closely it appear to be cristal clear: http://pastebin.com/asHm8GkW I getting spikes of 50k packets in very short periods (60seconds) I'll try to monitor all my servers in HLSW seeing how much time they are going offline... btw... seeing the spikes were that big I think I can increase the limit a lot... maybe 25 :) Il 07/01/2011 22:22, frostschutz ha scritto: On Fri, Jan 07, 2011 at 08:09:40PM +0100, Marco Padovan wrote: 20 minutes later: Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 396253 20611768 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 50483 2675483 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 If the number of dropped packets keeps rising slowly here, you are probably dropping legitimate queries. Maybe the limit is a bit too low then. Also consider using a larger burst. The burst will allow short, random spikes, but under actual and constant DoS, the limit will still be respected, same as without burst. I'd try limit 20 burst 40 here and see how that goes. You can be generous with burst as it will vanish completely during a DoS attack anyhow (and it will take 40 below-limit seconds to recharge). another box of ours that generally suffer a lot of is now reporting: Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 52 16966756 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 563098 29844034 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 drop accept is to be expected during a DoS attack. nobody complained yet... so looks like its holding :) Test it yourself - see if you can get a complete server list using the standard steam server browser. If half of your servers are missing there most of the time (while there is NO DoS going on), chances are your limit is too low. Regards frostschutz ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] tf2 denial of service - please do something!
No offense, but have you tried to look at where those dos attack comes from? You could block the IP-address of the attacker. /Chris Den 07/01/2011 kl. 22.32 skrev Marco Padovan: I thoutgh about that too... but monitoring the situation closely it appear to be cristal clear: http://pastebin.com/asHm8GkW I getting spikes of 50k packets in very short periods (60seconds) I'll try to monitor all my servers in HLSW seeing how much time they are going offline... btw... seeing the spikes were that big I think I can increase the limit a lot... maybe 25 :) Il 07/01/2011 22:22, frostschutz ha scritto: On Fri, Jan 07, 2011 at 08:09:40PM +0100, Marco Padovan wrote: 20 minutes later: Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 396253 20611768 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 50483 2675483 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 If the number of dropped packets keeps rising slowly here, you are probably dropping legitimate queries. Maybe the limit is a bit too low then. Also consider using a larger burst. The burst will allow short, random spikes, but under actual and constant DoS, the limit will still be respected, same as without burst. I'd try limit 20 burst 40 here and see how that goes. You can be generous with burst as it will vanish completely during a DoS attack anyhow (and it will take 40 below-limit seconds to recharge). another box of ours that generally suffer a lot of is now reporting: Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 52 16966756 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 563098 29844034 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 drop accept is to be expected during a DoS attack. nobody complained yet... so looks like its holding :) Test it yourself - see if you can get a complete server list using the standard steam server browser. If half of your servers are missing there most of the time (while there is NO DoS going on), chances are your limit is too low. Regards frostschutz ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] tf2 denial of service - please do something!
I suppose those are all spoofed udp packets as they were the last time I checked them :( I do not have direct access to the upstream links so I cannot trace them and link them to a specific bw supplier :( just increased the limits but still getting the drop rule hit hard... it's difficult to justify these spikes as legit traffic.. check from 23:21 onward http://pastebin.com/jUjzyKY6 I do not think I'm the only one in this situation as I saw many people discussing these problems recently :/ Il 07/01/2011 23:27, Christoffer Pedersen ha scritto: No offense, but have you tried to look at where those dos attack comes from? You could block the IP-address of the attacker. /Chris Den 07/01/2011 kl. 22.32 skrev Marco Padovan: I thoutgh about that too... but monitoring the situation closely it appear to be cristal clear: http://pastebin.com/asHm8GkW I getting spikes of 50k packets in very short periods (60seconds) I'll try to monitor all my servers in HLSW seeing how much time they are going offline... btw... seeing the spikes were that big I think I can increase the limit a lot... maybe 25 :) Il 07/01/2011 22:22, frostschutz ha scritto: On Fri, Jan 07, 2011 at 08:09:40PM +0100, Marco Padovan wrote: 20 minutes later: Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 396253 20611768 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 50483 2675483 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 If the number of dropped packets keeps rising slowly here, you are probably dropping legitimate queries. Maybe the limit is a bit too low then. Also consider using a larger burst. The burst will allow short, random spikes, but under actual and constant DoS, the limit will still be respected, same as without burst. I'd try limit 20 burst 40 here and see how that goes. You can be generous with burst as it will vanish completely during a DoS attack anyhow (and it will take 40 below-limit seconds to recharge). another box of ours that generally suffer a lot of is now reporting: Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 52 16966756 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 563098 29844034 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 drop accept is to be expected during a DoS attack. nobody complained yet... so looks like its holding :) Test it yourself - see if you can get a complete server list using the standard steam server browser. If half of your servers are missing there most of the time (while there is NO DoS going on), chances are your limit is too low. Regards frostschutz ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] tf2 denial of service - please do something!
You could use iptraf do look after the packets. You can configure it to put all the packet-logs into a file and then take a look at the file. /Chris Den 07/01/2011 kl. 23.50 skrev Marco Padovan: I suppose those are all spoofed udp packets as they were the last time I checked them :( I do not have direct access to the upstream links so I cannot trace them and link them to a specific bw supplier :( just increased the limits but still getting the drop rule hit hard... it's difficult to justify these spikes as legit traffic.. check from 23:21 onward http://pastebin.com/jUjzyKY6 I do not think I'm the only one in this situation as I saw many people discussing these problems recently :/ Il 07/01/2011 23:27, Christoffer Pedersen ha scritto: No offense, but have you tried to look at where those dos attack comes from? You could block the IP-address of the attacker. /Chris Den 07/01/2011 kl. 22.32 skrev Marco Padovan: I thoutgh about that too... but monitoring the situation closely it appear to be cristal clear: http://pastebin.com/asHm8GkW I getting spikes of 50k packets in very short periods (60seconds) I'll try to monitor all my servers in HLSW seeing how much time they are going offline... btw... seeing the spikes were that big I think I can increase the limit a lot... maybe 25 :) Il 07/01/2011 22:22, frostschutz ha scritto: On Fri, Jan 07, 2011 at 08:09:40PM +0100, Marco Padovan wrote: 20 minutes later: Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 396253 20611768 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 50483 2675483 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 If the number of dropped packets keeps rising slowly here, you are probably dropping legitimate queries. Maybe the limit is a bit too low then. Also consider using a larger burst. The burst will allow short, random spikes, but under actual and constant DoS, the limit will still be respected, same as without burst. I'd try limit 20 burst 40 here and see how that goes. You can be generous with burst as it will vanish completely during a DoS attack anyhow (and it will take 40 below-limit seconds to recharge). another box of ours that generally suffer a lot of is now reporting: Chain QUERYLIMIT (4 references) pkts bytes target prot opt in out source destination 52 16966756 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 15/sec burst 5 mode dstport 563098 29844034 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 drop accept is to be expected during a DoS attack. nobody complained yet... so looks like its holding :) Test it yourself - see if you can get a complete server list using the standard steam server browser. If half of your servers are missing there most of the time (while there is NO DoS going on), chances are your limit is too low. Regards frostschutz ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] tf2 denial of service - please do something!
On Fri, Jan 07, 2011 at 11:50:56PM +0100, Marco Padovan wrote: I suppose those are all spoofed udp packets as they were the last time I checked them :( Only you can tell. (We can't look at the packets you're getting:) it's difficult to justify these spikes as legit traffic.. 10k spikes are not legit, I was thinking more along the lines of randomly getting 40 instead of just 10-20 packets in one particular second. A spike of 40 could be allowed, a spike of 1 certainly not. ;) check from 23:21 onward http://pastebin.com/jUjzyKY6 Since the DROP stays at 0 for several minutes that looks fine. If it increased like 1-5 packets every other second that would point to a too low limit. You had 3 unlucky queries between 23:00 and 23:01 (legit spike that got dropped), then again nothing for minutes, and then comes the DoS that gets dropped correctly. I think that's okay. Regards frostschutz ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
[hlds_linux] Team Fortress 2 Update Released
A required update for Team Fortress 2 is now available. The specific changes include: Source Engine Changes (CS:S, DoD:S, TF2, HL2:DM) - Added the Server can execute flag to the r_cleardecals command. - Fixed a problem where the microphone transmit volume sometimes had no associated control and was disabled in the Audio options dialog. - Fixed a crash on exit for Mac clients. Team Fortress 2 - Added community submitted kill icons. - Fixed enemies seeing death notices when you backstab their team mates with Your Eternal Reward. - Fixed the attack animation not always playing correctly for Your Eternal Reward. - Fixed the critboost sound not playing when the Kritzkrieg charge is deployed. - Fixed a broken texture on the Flipped Trilby. - Updated the material for the Jag. - Community Request - Fixed spawn points associated with a control point not being enabled/disabled correctly when the control point owner is set using the SetOwner input. - Added the Server can execute flag to the firstperson and thirdperson commands. Jason ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Team Fortress 2 Update Released
Once again no version change on server so un able to connect, this is becoming a habit! -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Jason Ruymen Sent: 08 January 2011 00:05 To: 'Half-Life dedicated Linux server mailing list'; 'Half-Life dedicated Win32 server mailing list'; 'hlds_annou...@list.valvesoftware.com' Subject: [hlds_linux] Team Fortress 2 Update Released A required update for Team Fortress 2 is now available. The specific changes include: Source Engine Changes (CS:S, DoD:S, TF2, HL2:DM) - Added the Server can execute flag to the r_cleardecals command. - Fixed a problem where the microphone transmit volume sometimes had no associated control and was disabled in the Audio options dialog. - Fixed a crash on exit for Mac clients. Team Fortress 2 - Added community submitted kill icons. - Fixed enemies seeing death notices when you backstab their team mates with Your Eternal Reward. - Fixed the attack animation not always playing correctly for Your Eternal Reward. - Fixed the critboost sound not playing when the Kritzkrieg charge is deployed. - Fixed a broken texture on the Flipped Trilby. - Updated the material for the Jag. - Community Request - Fixed spawn points associated with a control point not being enabled/disabled correctly when the control point owner is set using the SetOwner input. - Added the Server can execute flag to the firstperson and thirdperson commands. Jason ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Team Fortress 2 Update Released
So is this only TF2 update or all source engines ? A required update for Team Fortress 2 is now available. The specific changes include: Source Engine Changes (CS:S, DoD:S, TF2, HL2:DM) I did not see a version change on dods when i updated it, yet it said the engine was updated. On Fri, Jan 7, 2011 at 7:17 PM, D3vilfish - Simiancage.org priv...@caterhamhill.net wrote: Once again no version change on server so un able to connect, this is becoming a habit! -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Jason Ruymen Sent: 08 January 2011 00:05 To: 'Half-Life dedicated Linux server mailing list'; 'Half-Life dedicated Win32 server mailing list'; 'hlds_annou...@list.valvesoftware.com' Subject: [hlds_linux] Team Fortress 2 Update Released A required update for Team Fortress 2 is now available. The specific changes include: Source Engine Changes (CS:S, DoD:S, TF2, HL2:DM) - Added the Server can execute flag to the r_cleardecals command. - Fixed a problem where the microphone transmit volume sometimes had no associated control and was disabled in the Audio options dialog. - Fixed a crash on exit for Mac clients. Team Fortress 2 - Added community submitted kill icons. - Fixed enemies seeing death notices when you backstab their team mates with Your Eternal Reward. - Fixed the attack animation not always playing correctly for Your Eternal Reward. - Fixed the critboost sound not playing when the Kritzkrieg charge is deployed. - Fixed a broken texture on the Flipped Trilby. - Updated the material for the Jag. - Community Request - Fixed spawn points associated with a control point not being enabled/disabled correctly when the control point owner is set using the SetOwner input. - Added the Server can execute flag to the firstperson and thirdperson commands. Jason ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Team Fortress 2 Update Released
I got an update on HL2:DM. It's only required for TF2, for the other games it's optional. On Fri, 2011-01-07 at 19:30 -0500, clad iron wrote: So is this only TF2 update or all source engines ? A required update for Team Fortress 2 is now available. The specific changes include: Source Engine Changes (CS:S, DoD:S, TF2, HL2:DM) I did not see a version change on dods when i updated it, yet it said the engine was updated. On Fri, Jan 7, 2011 at 7:17 PM, D3vilfish - Simiancage.org priv...@caterhamhill.net wrote: Once again no version change on server so un able to connect, this is becoming a habit! -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Jason Ruymen Sent: 08 January 2011 00:05 To: 'Half-Life dedicated Linux server mailing list'; 'Half-Life dedicated Win32 server mailing list'; 'hlds_annou...@list.valvesoftware.com' Subject: [hlds_linux] Team Fortress 2 Update Released A required update for Team Fortress 2 is now available. The specific changes include: Source Engine Changes (CS:S, DoD:S, TF2, HL2:DM) - Added the Server can execute flag to the r_cleardecals command. - Fixed a problem where the microphone transmit volume sometimes had no associated control and was disabled in the Audio options dialog. - Fixed a crash on exit for Mac clients. Team Fortress 2 - Added community submitted kill icons. - Fixed enemies seeing death notices when you backstab their team mates with Your Eternal Reward. - Fixed the attack animation not always playing correctly for Your Eternal Reward. - Fixed the critboost sound not playing when the Kritzkrieg charge is deployed. - Fixed a broken texture on the Flipped Trilby. - Updated the material for the Jag. - Community Request - Fixed spawn points associated with a control point not being enabled/disabled correctly when the control point owner is set using the SetOwner input. - Added the Server can execute flag to the firstperson and thirdperson commands. Jason ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Team Fortress 2 Update Released
Can you please update the version on the master server for those of us using nemrun? Thank you. On Fri, Jan 7, 2011 at 4:05 PM, Jason Ruymen jas...@valvesoftware.com wrote: A required update for Team Fortress 2 is now available. The specific changes include: Source Engine Changes (CS:S, DoD:S, TF2, HL2:DM) - Added the Server can execute flag to the r_cleardecals command. - Fixed a problem where the microphone transmit volume sometimes had no associated control and was disabled in the Audio options dialog. - Fixed a crash on exit for Mac clients. Team Fortress 2 - Added community submitted kill icons. - Fixed enemies seeing death notices when you backstab their team mates with Your Eternal Reward. - Fixed the attack animation not always playing correctly for Your Eternal Reward. - Fixed the critboost sound not playing when the Kritzkrieg charge is deployed. - Fixed a broken texture on the Flipped Trilby. - Updated the material for the Jag. - Community Request - Fixed spawn points associated with a control point not being enabled/disabled correctly when the control point owner is set using the SetOwner input. - Added the Server can execute flag to the firstperson and thirdperson commands. Jason ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Team Fortress 2 Update Released
Not just for those using nemrum. It's confusing players who updated. All the old servers are showing up on the master and giving people errors when they try to join. On Fri, Jan 7, 2011 at 7:51 PM, bottige...@gmail.com bottige...@gmail.comwrote: Can you please update the version on the master server for those of us using nemrun? Thank you. On Fri, Jan 7, 2011 at 4:05 PM, Jason Ruymen jas...@valvesoftware.com wrote: A required update for Team Fortress 2 is now available. The specific changes include: Source Engine Changes (CS:S, DoD:S, TF2, HL2:DM) - Added the Server can execute flag to the r_cleardecals command. - Fixed a problem where the microphone transmit volume sometimes had no associated control and was disabled in the Audio options dialog. - Fixed a crash on exit for Mac clients. Team Fortress 2 - Added community submitted kill icons. - Fixed enemies seeing death notices when you backstab their team mates with Your Eternal Reward. - Fixed the attack animation not always playing correctly for Your Eternal Reward. - Fixed the critboost sound not playing when the Kritzkrieg charge is deployed. - Fixed a broken texture on the Flipped Trilby. - Updated the material for the Jag. - Community Request - Fixed spawn points associated with a control point not being enabled/disabled correctly when the control point owner is set using the SetOwner input. - Added the Server can execute flag to the firstperson and thirdperson commands. Jason ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] tf2 denial of service - please do something!
Il 08/01/2011 01:01, frostschutz ha scritto: On Fri, Jan 07, 2011 at 11:50:56PM +0100, Marco Padovan wrote: I suppose those are all spoofed udp packets as they were the last time I checked them :( Only you can tell. (We can't look at the packets you're getting:) Didn't took the time because they were very short spikes... will arrange something in the next days if the thing will continue with this frequency... The problem is that it will take days to analyze the output of half an hour worth of log :D it's difficult to justify these spikes as legit traffic.. 10k spikes are not legit, I was thinking more along the lines of randomly getting 40 instead of just 10-20 packets in one particular second. A spike of 40 could be allowed, a spike of 1 certainly not. ;) check from 23:21 onward http://pastebin.com/jUjzyKY6 Since the DROP stays at 0 for several minutes that looks fine. If it increased like 1-5 packets every other second that would point to a too low limit. You had 3 unlucky queries between 23:00 and 23:01 (legit spike that got dropped), then again nothing for minutes, and then comes the DoS that gets dropped correctly. yeah, I'm sorry for those 3... hope they got lucky retrying a second later ;) I think that's okay. I hope that too... thanks for your precious suggestions :) Regards frostschutz ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
