CS:S (Steam) causes router to crash/reboot

yesterday i wanna play a round of counterstrike:source an run in massive troubles :frown: When i start to get the serverlist i recognized that scanning the servers gets very slow. So later on i checked the syslog and see that there was an error message: "ip_conntrack: table full, dropping packet" than i set the value from 2048 to 4096. After getting back to counterstrike i tried to load the serverlist again but after a while i lost internet connectivity. I recheck the syslog and see that the router had rebooted. So after long observations i recognized that every time i load a new serverlist the conntrack connection raises over 4000 connections and the router run out of memory and than cause a reboot. Whats going on here. I dont know if this is the fault of new version 1.06 because i never had this problem before. Later on i will try to flash back and will see if the problem is still there. Anyone an idea ?

I use it all the time no with no problems... I think your problem lies elsewhere.
my connection limit is set to 2048 since I don't really use more than that and
I got 4 computers connected to the router all running bittorrent and emule.

i use Qtracker, a Game-Server-Lister, and had nearly the same problem, except the rebooting, it only disconnects the wan-Con.
Only work around is setting Maximum Connections to ~6000, and lowering the connections used for quering the servers in Qtracker. (I've seen it opening 5000 and more)

The problem is most serverlist software (ingame or 3rd party) is it has to connect to all the servers in a very short space of time to probe them for information. To get that information from so many servers, it will have to open a connection to each and every one of the servers. If your serverlist have a thousand servers then it's gonna request/open a thousand connections. Reason why your p2p programs aren't affected is most of them only default to around 100-200 max connections.

Try increasing the max allowed connections to 4096. Personally I use 8192 without problems, although my max connections have never really reached past 3000. Another tip is to set your serverlist software to only list/refresh servers close to you, as many will allow you to filter by country etc. Not much point in probing servers half way across the globe with pings over 500+ ms, it's not like your gonna play on them are you?

found a solution for the steam problem in their own forum
The problem with crashing the router was of setting the value of conntrack table to high! (>6000) -> router run out of memory. So now i'm back at 2048 (as in the beginning :biggrin: ) and if there is an application (like steam ((without reghack) witch start a lot of sim. connections) dont worry about if there is an "[SIZE=-1]ip_conntrack: table full, dropping packet" in the syslog. For me it doesn't affect performance (after a while of testing:wink.

it was a discussion about the connection limit and GeeTek seems to be buried in his position there is no correlation in the actual problem.
I think only in symptoms eventually since memory will run out...