From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] "Transparent" shapping
Date: Mon, 02 Sep 2002 18:41:15 +0000 [thread overview]
Message-ID: <marc-lartc-103099216631315@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103097944720037@msgid-missing>
On Monday 02 September 2002 17:08, Esteban Maringolo wrote:
> Hello,
>
> I want to do some traffic shapping with a PC in the same IP subnet that
> the "shaped" PC's.
> Graphically:
>
> ________ __________
>
> Internet-eth0| NAT/GW |eth1----eth0| TC BOX |eth1 --- SUBNET PC's...
>
> |________| |__________|
>
> NAT GW (Nat Gateway) Specs:
> eth0 IP: AAA.BBB.CCC.DDD Public Address
> eth1 IP: 192.168.0.1/24
>
> TC BOX (Traffic Shaper):
> eth0 IP: 192.168.0.2/24
> eth1 IP: 192.168.0.3/24
>
> SUBNET PCs:
> Netblock: 192.168.0.10/24 - 192.168.0.254/24
> Default GW IP: 192.168.0.1
>
> Is possible to make that my TC BOX acts transparently for the subnet PCs
> without redefine the default GW to 192.168.0.3 (the TC inner interface).
>
> The intention is not add another Hop to the network, and lower the CPU
> usage of the TC BOX (i don't want to do NAT on it).
You can put the box in bridge mode and use the u23 filter. There is a patch
floating around to enable iptables on the bridged box. You can asign the box
an ip-address so you can reach it, but all traffic passes thru and is shaped.
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/
next prev parent reply other threads:[~2002-09-02 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 15:08 [LARTC] "Transparent" shapping Esteban Maringolo
2002-09-02 15:50 ` Rohan Almeida
2002-09-02 18:41 ` Stef Coene [this message]
2002-09-03 12:46 ` Esteban Maringolo
2002-09-03 13:54 ` Stef Coene
2002-09-05 16:41 ` Esteban Maringolo
2002-09-05 16:52 ` Martin A. Brown
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-103099216631315@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.