From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: [LARTC] [ahu@ds9a.nl: Re: tc with iptables]
Date: Wed, 26 Sep 2001 13:07:23 +0000 [thread overview]
Message-ID: <marc-lartc-100150965813793@msgid-missing> (raw)
----- Forwarded message from bert hubert <ahu@ds9a.nl> -----
Date: Wed, 26 Sep 2001 14:45:52 +0200
From: bert hubert <ahu@ds9a.nl>
To: lartc-admin@mailman.ds9a.nl
Subject: Re: tc with iptables
On Wed, Sep 26, 2001 at 10:33:17AM +0530, Mehul Vora wrote:
> Hi,
>
> is it possible to control the bandwidth assigned to a specific interface /
> IP on a linux router using tc with iptables? what i mean to say is, on a
> dual homed linux server, i use iptables to masquerade all the internal
> segment traffic over the interface connected to external segment... can i
> use tc to limit the bandwidth for one of the IP addresses from internal
> segment to say 64Kbps or 128Kbps etc.?
You can only limit what you send and in this case that works in your favor.
On the internal interface, the destination of your packets is the 'real'
internal address, which you can shape on.
If you want to limit *outgoing* traffic, from your internal segment to the
internet, you need to 'mark' your packets when they come into your system,
and then shape on the mark when they go out. This is possible.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
----- End forwarded message -----
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
reply other threads:[~2001-09-26 13:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-100150965813793@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.