From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] shaping domain names(www.xyz.com)
Date: Fri, 07 May 2004 18:14:53 +0000 [thread overview]
Message-ID: <200405072014.53623.stef.coene@docum.org> (raw)
In-Reply-To: <1083934416.409b86d04f7df@smwp01.maa.sify.net>
On Friday 07 May 2004 15:37, Michael Renzmann wrote:
> Hi.
>
> jayesh rathod wrote:
> > Is there any way by which we can shape domain name(not by IP address)
> > Eg : suppose i want to shape tarrif to a particular domain www.xyz.com
> >
> > which has multiple ips and i am not aware of there ips
>
> You could achieve this by using different firewall marks for the
> different traffic classes, and shape upon that marks. IIRC there is an
> iptables-extension available that allows to match strings, so you could
> try to match "Host: <domain>" in order to distinguish the different
> domains. But I have no idea if this would work in real world, nor what
> performance impact that may have.
Only one problem. Tc sees ip packets and ip packets contains ip addresses,
not hostnames. So you can't do this.
But I suppose you want to shape http / ftp? You can try to setup a squid
transparant proxy server and if I'm not mistaken, you can patch squid so you
can use tc to shape the squid traffic.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-05-07 18:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 12:23 [LARTC] shaping domain names(www.xyz.com) jayesh rathod
2004-05-07 13:37 ` Michael Renzmann
2004-05-07 18:14 ` Stef Coene [this message]
2004-05-08 7:08 ` Michael Renzmann
2004-05-08 18:45 ` Stef Coene
2004-05-10 5:19 ` Michael Renzmann
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=200405072014.53623.stef.coene@docum.org \
--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.