All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randolph Carter <angelripper@cable.net.co>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Squid + Htb + Nat, problem.
Date: Sun, 10 Nov 2002 19:43:10 +0000	[thread overview]
Message-ID: <marc-lartc-103695742127166@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103688783525085@msgid-missing>

I don't want to use delay pools, since I want squid as a web-cache and TC as a traffic shaper(the way it should be, I think :P). Now I have tried to use DSCP marks(using Squid5Stable1) on packets so TC can handle them, but the fact is they are leaving my machine without being even touched by TC. So now I have a netfilter problem (or I'm not sure if is it still a Lartc problem). I don't know if this is the right place to ask for it, but if the packet is generated locally (as squid generates it) and it is DSCP marked  will TC match it (is the TOS match DSCP compatible or are they different fields???). If I use iptables to mark with "fwmark"(based on the DSCP mark writted by SQUID something like "#iptables -t mangle -D POSTROUTING -m dscp --dscp 0x00 -j MARK --set-mark 5") the packet will TC see this fwmarked packet as with the nated packets? I guess not, because this packet will not fall in mangle, so this should be done in the OUTPUT chain, but iptables doesn't support dscp on this chain. Which solution can I implement then?





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

  parent reply	other threads:[~2002-11-10 19:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-10  0:22 [LARTC] Squid + Htb + Nat, problem Angelripper
2002-11-10  0:28 ` 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 [this message]
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-103695742127166@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 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.