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: Mon, 11 Nov 2002 15:14:24 +0000	[thread overview]
Message-ID: <marc-lartc-103702768009435@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103688783525085@msgid-missing>

I apologize if I offended you, my intention was not to offend anyone, 
sorry(I was just kidding, I already know of the great advantages on 
Layer 3 squid offers, but is not the solution that I'm looking for).

What u say is what I'm actually doing, using acl in order to put a DSCP 
mark on each packet leaving the maching according to the IP src, is 
something like this

    acl higgs src 192.168.1.2
    tcp_outgoing_dscp 0x01 higgs

But tc seems to have no support on dscp or I haven't found it yet; so I 
must "remark" the packet with a fwmark that tc can handle. Thats where 
the problem becomes a netfilter problem, but if you thinks it deeply is 
a routering problem since the packets are being routered(anyway the 
problem concercs with iptables or something so).

-- 
It will be advantageous to cross the great stream ... the Dragon is on
the wing in the Sky ... the Great Man rouses himself to his Work.


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

  parent reply	other threads:[~2002-11-11 15:14 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 [this message]
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-103702768009435@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.