From: "Leigh Waldie" <lartc@thisisnota.co.uk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Proxy question
Date: Wed, 02 Jul 2003 15:16:20 +0000 [thread overview]
Message-ID: <marc-lartc-105715907812150@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105713412720634@msgid-missing>
> Heloooo :-)
> Well this is a good oppinion but, what does it happen when somebody make
> a big request, the proxy will be unshaped thus it will allocate whole
> the line.
Perhaps you need to put the shaping on the same machine as the proxy, this should allow
you to mark the packets (i think squid can do this) and shape them accordingly?
> A good option is to place another shaper between the proxy and the
> internet.
> To make it simpler to place the proxy in our DMZ, and place another
> shaper for the dmz.
> Thanks for the advice my friend
> Best regards
> Stamatis
> Leigh Waldie wrote:
>
>>Why not change your topology so that you have
>>
>>Firewall----------------->Shaper-------------->Proxy------------->Internet
>>
>>This way you have more control over the traffic. Admittedly, you are not truly shaping
>>the total bandwidth available to you (some of the traffic will be returning to your
>>clients from the proxy without ever going out to the internet) but maybe with some
>>tweaking of the traffic shaping you can allow for this ?
>>
>>Leigh
>>
>>
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-07-02 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 8:18 [LARTC] Proxy question Σταμάτης Κεκές
2003-07-02 11:41 ` Radu-Mihail Obada
2003-07-02 11:58 ` ???????? ?????
2003-07-02 12:43 ` Chijioke Kalu
2003-07-02 13:42 ` Leigh Waldie
2003-07-02 14:19 ` ???????? ?????
2003-07-02 15:16 ` Leigh Waldie [this message]
2003-07-02 15:28 ` ???????? ?????
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-105715907812150@msgid-missing \
--to=lartc@thisisnota.co.uk \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.