From: Randolph Carter <angelripper@cable.net.co>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Squid + Htb + Nat, problem.
Date: Mon, 11 Nov 2002 15:20:19 +0000 [thread overview]
Message-ID: <marc-lartc-103702804609922@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103688783525085@msgid-missing>
That's true rob, should be in the OUTPUT traffic. But rob, the problem
is I'm trying to limit the upstream which in the case in which is squid
is used, seems always to come from the local machine to the internet, so
TC will not know to whom belongs that packet, it just belong to the
local machine. There is where dscp is needed, in order to know (with
squid's help) to know to whom the "routered" packet belongs.
I have already posted this question on the netfilter maillist, but I
haven't had an answer.
>locally generated traffic should be in the OUTPUT chain, if you specify the
>source port and the destination (device?) then i think you should not
>need -m dscp anymore.
>
>--
>rob
>
>
>
--
Behold the warranty ... the bold print giveth and the fine print taketh
away.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-11 15:20 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
2002-11-11 15:14 ` Randolph Carter
2002-11-11 15:20 ` Randolph Carter [this message]
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-103702804609922@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.