From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] problem with htb restriction
Date: Wed, 17 Sep 2003 23:33:50 +0000 [thread overview]
Message-ID: <marc-lartc-106384175927270@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106383054210484@msgid-missing>
Omar Armas wrote:
> [router]
> |
> [Firewall]
> eth0: 200.x.x.x (public address)
> eth1: 192.168.44.1 (private address)
> |
> [LAN] (192.168.44.0/24)
> tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip src \
> 192.168.44.0/24 match ip dport 25 0xffff flowid 1:10
> tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip src \
> 192.168.44.0/24 match ip dport 80 0xffff flowid 1:11
>
>
> But from a machine of the class 192.168.44 (fw as gateway) I made a test
> to an external http server and had no limit on port 80 traffic.
The htb qdisc is going to rate limit the traffic _leaving_ the interface.
so the rules you've created above will only slow down the HTTP requests to the
internet, not the HTTP data downloaded from the external servers.
> Is it necessary to add the same rules with eth1?
I think you should be able to move them all to eth1, and remove them from eth0.
You'll also want to change the 'src' to 'dst'.
regards.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer email: damion@snapgear.com
SnapGear --- ph: +61 7 3435 2809
| Custom Embedded Solutions fax: +61 7 3891 3630
| and Security Appliances web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--- Free Embedded Linux Distro at http://www.snapgear.org ---
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-09-17 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 20:28 [LARTC] problem with htb restriction Omar Armas
2003-09-17 23:33 ` Damion de Soto [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-106384175927270@msgid-missing \
--to=damion@snapgear.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox