A way to stop connection overloads?
Posted: Wed Jul 27, 2011 10:44 am
I have been running Gargoyle on my TP Link tl-wr841nd for about a month in my new flat (with about 5 other flatmates) and I get a problem where the router starts to massively slow down (the config page takes ages to load) and so does the throughput to the internet.
I notice that this is perhaps because sometimes people are downloading with p2p and I get in upwards of 500 UDP connections etc.
I was wondering what ways there are to combat this? I have halved the default number of maximum connections and decresed TCP and UDP timeouts to 60sec and 30sec respectively. I have also reduced the UPNP figures to 128kbps up 256kbps down. The QoS is active and I have added capped a couple of users to 10kbps upload. Is there anything more I can do?
I've also noticed the following bugs
1) CPU usage isn't displayed after a while (all numbers are zero)
2) On the bandwidth usage graphs the download graph doesn't show downloading by QoS but upload does
3) The USB thumbdrive isn't detected reliably
4) The router will seize up and stop allowing any network access. I am not sure yet but this may only occur when 40mhz mode is forced to be enabled by entering noscan=1 into the configuration.
I notice that this is perhaps because sometimes people are downloading with p2p and I get in upwards of 500 UDP connections etc.
I was wondering what ways there are to combat this? I have halved the default number of maximum connections and decresed TCP and UDP timeouts to 60sec and 30sec respectively. I have also reduced the UPNP figures to 128kbps up 256kbps down. The QoS is active and I have added capped a couple of users to 10kbps upload. Is there anything more I can do?
I've also noticed the following bugs
1) CPU usage isn't displayed after a while (all numbers are zero)
2) On the bandwidth usage graphs the download graph doesn't show downloading by QoS but upload does
3) The USB thumbdrive isn't detected reliably
4) The router will seize up and stop allowing any network access. I am not sure yet but this may only occur when 40mhz mode is forced to be enabled by entering noscan=1 into the configuration.