From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Configuration help
Date: Tue, 08 Apr 2003 21:06:48 +0000 [thread overview]
Message-ID: <marc-lartc-104983605808642@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104983106502106@msgid-missing>
On Tuesday 08 April 2003 21:42, Micah Anderson wrote:
> I have been reading lartc.org for the past few days and am a bit
> overwhelemed by the possibilities and configurations that are
> possible. I am still trying to process all of this to try and
> understand what I need to do in my configuration, and have tried a few
> things to no avail. I currently have a webserver that is completely
> flooding our link, so I need to find a way to deal with this quickly.
> Can someone offer me some guidance in figuring out what I need to do?
>
> My configuration is as follows:
>
> 2.2.20 kernel (with QOS enabled and all shaping stuff on), this
> machine acts as a webserver and is also doing IPFW/MASQ for a small
> network behind it. Interface eth0 is on the internet, eth1 is
> connected to the private network. I would like to limit any traffic
> that originates from the webserver itself so that the masquaraded
> hosts behind it can still function with a certain amount of assured
> bandwidth. The problem of course is that all the masqueraded traffice
> comes through the webserver, so I am not sure how I can shape traffic
> that comes from eth1 to be of higher priority over traffic that doesn't.
First of all, upgrade your kernel. The network (and especially the shaping
part of it) is updated a lot in the 2.4.x kernels.
Or was it a typo and are you running 2.4.20 ?
Web-server can be matched based on ports.
Or you can mark the LAN packets entering your box and use that mark after the
natting to shape the traffic.
> I have played with the shaper utility, the wondershaper, and have
> tried my own recipies, all so far with no success. :(
>
> Thanks for any pointers you can offer!
www.docum.org ?
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-04-08 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 19:42 [LARTC] Configuration help Micah Anderson
2003-04-08 21:06 ` Stef Coene [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-104983605808642@msgid-missing \
--to=stef.coene@docum.org \
--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.