So, I've looked everwhere and gotten really frustrated... so i came here... and the search feature showed me a bunch of spam...
so
how do i throttle bandwith in server 2009?
i have a 100mbps connection and i dont want someone coming along and dossing me/ getting files from my server and eating up my connection... I know 100mbps is a lot, but i have enemies with more... so how can i throttle downloads/connections (im also running a game server) to prevent "legal DoSing"
i am running server 2009 apache 2.2
tanks
matt

Dani AI

Generated

If a small number of legitimate downloads can saturate the server link, the most reliable fix is to shape or police traffic before it reaches your NIC. That keeps other services responsive and avoids trying to “fix” ingress bandwidth from inside the VM. If you cannot modify the upstream router, use layered controls: network-side shaping (provider), web-server throttles, and connection limits at the application level.

Options that work in practice:

  • Ask the datacenter to apply per-IP or per-port rate limits, or enable per-tenant traffic policing. This is the simplest and most effective place to cap inbound throughput.
  • Add server-side request/connection controls in Apache: use an official rate-limiting module if available, and pair it with modules that limit concurrent connections or requests per IP. Also consider modules that block or slow abusive clients rather than outright banning. Test any module carefully on Windows builds — some third-party modules need compilation or specific builds.
  • Use OS-level QoS only as a last resort for outbound shaping; it cannot truly stop inbound traffic arriving at full speed (ingress policing requires upstream support).
  • For file distribution, use a CDN, alternative hosts, or a download server that supports chunked/resumable downloads to reduce peak load on a single origin.

Practical checklist:

  1. Open a ticket with the host asking for “ingress/egress policing” or a per-port cap and request metrics while they test it.
  2. If the host won’t, install and test Apache rate/connection-limiting modules in a staging environment and gradually enable them for the download paths only.
  3. Monitor with real traffic (netstat, performance monitor, Apache status) and tune limits so normal users aren’t penalized.

As pointed out, edge shaping is ideal; since is on a rented server, start with the provider. Ignore unrelated speed-test commentary from for the immediate throttling task. Test carefully to avoid false positives that block legitimate players or downloads.

Recommended Answers

All 5 Replies

You will want to do all traffic throttling in front of the network or machine. So if you want to throttle you webserver then use the router in front of it. What type of router do you have?

I dont have a router. Its a rented off site server

Don't worry about it then. The datacenter should have preventative measures in place for DDoS ;)

but its not dosing... its 10 people downloading a file at 10mbps

He did this by creating a speed test that measured the throughput of continuous access to popular Web sites like Google, Expedia, and many others. Until this report was published, the common metric for comparing ISPs was through the use of the numerous Internet speed test sites available online.

The problem with this validation method was that it could not simulate real speeds encountered when doing typical Web surfing and downloading operations. Plus, ISPs can tamper with the results of speed tests — more on this later.
SNIP

commented: irrelevant post. probably spamming sig links -1
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.