Too many NAT TCP connections

[sighck]

I'm using WinGate 6.2.1 as a NAT server on a dedicated PC (Win2k) and there are four clients that connect to Internet through this 'server'. The problem I have is when one of the clients gets a lot of TCP connections ~200 (all together ~225-250) the other clients get problems with there Internet access. The reason for the huge amount of TCP connections for that client is that it has a bittorrent client running. Is there a limit in WinGate how many TCP/UDP connection it can handle?

In a thread from Nov 2006 (Limit amount of NAT TCP connections) I read that in next major release it should be possible to limit number off TCP connection for a client. When will this 'new major release' be released?

If I limit the upload bandwidth for that client the amount off connections increase faster and if I don’t it takes all upload bandwidth and makes the Internet access slow for the others.

Any work around?

[deftech]

I don't know about a patch coming out like that, but I can tell you anyone running bittorrent, even one machine will slow your net down a ton. I can't play online games with decent latency at all when I'm dling from a torrent site.

I also know that Microsoft implemented a security patch that limits Windows from allowing too many tcp connections, because many viruses act the same way dling torrents does.

[sighck]

I don't think we can blaim Microsoft for this 'feature', I'm using Win 2000 and the limit you mention is for XP. It would be nice if somebody from Qbik could reply to this topic. I have made a workaround with the client that use uTorrent I have limit the number of TCP connections that this machine can have (100) and know it works again but it would be nicer if I could limit the number of TCP connection in WinGate instead.

[script]

You can see this topic.

I think that it will have your answer.

http://forums.qbik.com/viewtopic.php?t=5392

[adrien]

Hi

There's currently no way to specify per-user connection limits in WinGate sorry. That post only applies if WinGate (or a client) is running on XP SP2.

We're currently previewing the next WinGate to a few people for initial feedback on the new policy system (its very different), and expect to have a release available around end October. That's the plan anyway.

As for limiting number of connections, I'll have to discuss that with the ENS lead dev, we've discussed limits in the past, but mainly rate limiting data. Limiting concurrent connections per client IP is tricky to do efficiently, and it's impossible to tell which connections one should drop or what. E.g someone runs bittorrent and then they can't check email.