Re: Limit filesharing traffic with PF

> On 11/4/05, Christoph Egger <[EMAIL PROTECTED]> wrote: > > The P2P traffic can be identified this way: > > - The source IP from one client is always the same > > - The client establishes lots of connections to many destination IP > > adresses > > Use synproxy, max-src-states, and overload tabl

Re: Limit filesharing traffic with PF

On 11/4/05, Christoph Egger <[EMAIL PROTECTED]> wrote: > The P2P traffic can be identified this way: > - The source IP from one client is always the same > - The client establishes lots of connections to many destination IP adresses Use synproxy, max-src-states, and overload tables. Automagically

Re: Limit filesharing traffic with PF

Christoph Egger wrote: > Filesharing users eat the whole available bandwidth and they use > lots of connections at the same time. The result is an overloaded > gateway. Locking ports doesn't help, because they do port-hopping. > The rough solution: > The rough answer: Queue everything into you

Limit filesharing traffic with PF

Hello! I have the following problem: Filesharing users eat the whole available bandwidth and they use lots of connections at the same time. The result is an overloaded gateway. Locking ports doesn't help, because they do port-hopping. My goal: I want to create a queue which limits the bandwid