Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Angelripper <angelripper@cable.net.co>
To: lartc@vger.kernel.org
Subject: [LARTC] Squid + Htb + Nat, problem.
Date: Sun, 10 Nov 2002 00:22:33 +0000	[thread overview]
Message-ID: <marc-lartc-103688783525085@msgid-missing> (raw)

I'm trying to shape a connection behind a NAT. I have done it already
using tc with htb. Now the problems is that I want to run Squid on the
same
machine, and also control de bandwidth but with htb so it can change
the bandwidth in real time. For the non-squid version of this, I'm using
iptables-mangle to mark packets and tc for the traffic control.

As squid is only for HTTP transactions, I decided to send through it
only the web traffic(excludind FTP and SSL), and limit the downstream with
HTB as in the non-squid version. But the
upstream is always uncontrolled since one only can control the packets
going out of the server and the uploading proccess seem to come from the
NAT-server since is there where squid is installed and squid doesn't make
any NAT at all. Is there a way to mark the packets squid sends
out so tc can control them also? Exists there another solution? Is the
web-cache server a bad solution into the QoS rage?

If something sounds stupid I apologize, since I'm a newbie.


Pity the meek, for they shall inherit the earth.
		-- Don Marquis

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-11-10  0:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-10  0:22 Angelripper [this message]
2002-11-10  0:28 ` [LARTC] Squid + Htb + Nat, problem Joe Cooper
2002-11-10 15:29 ` Stef Coene
2002-11-10 15:55 ` Tomasz Wrona
2002-11-10 16:17 ` Stef Coene
2002-11-10 19:43 ` Randolph Carter
2002-11-11 15:14 ` Randolph Carter
2002-11-11 15:20 ` Randolph Carter
2002-11-11 18:18 ` Randolph Carter

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-103688783525085@msgid-missing \
    --to=angelripper@cable.net.co \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox