From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] need help in shaping traffic
Date: Fri, 28 Dec 2001 07:07:39 +0000 [thread overview]
Message-ID: <marc-lartc-100952331805331@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100951048824186@msgid-missing>
On Fri, Dec 28, 2001 at 03:33:58AM +0000, arindam wrote:
> hi all,
> my system with kernel 2.4.16 & 2.4.17( RH-7.2) has
> netfilter-1.2.4, iproute-ss010803, squid, dns with 4
> ether cards.i am trying a simple situation where i
> want to shape traffic all the interfaces. at present
> iam using netfilter to allow a few ips, using
> transparent squid & iproute to limit bandwidth. i feel
> i must give more bandwidth for my local servers for my
> office & customers.
> i need some help from u Gurus in knowing what i did
> wrong here.
> a) y no trafic is passing thru the http handle 101.
> infcat only the 102 handle is working(seen below) ??
'tcp dst' is not working as you think it is. Use 'ip dport'.
> b) whats recomended--marking pkts in iproute or
> iptables ??
AFAIK, ip can't mark packets.
> c) if i mark pkts with iptables, will i be still able
> to use transparent squid as well as shape bandwidth(i
> havnt tried this so far)
An fwmark will not survive a transparent proxy.
You may want to police on ingress.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2001-12-28 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 3:33 [LARTC] need help in shaping traffic arindam
2001-12-28 7:07 ` bert hubert [this message]
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-100952331805331@msgid-missing \
--to=ahu@ds9a.nl \
--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.