From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Prioritizing on a Bridge doesn't seen to work correct,
Date: Mon, 19 Apr 2004 23:32:55 +0000 [thread overview]
Message-ID: <408461A7.9040104@snapgear.com> (raw)
In-Reply-To: <s083e92d.047@tkh-master2.tkh.theresienkh-nbg.de>
Thomas Reiß wrote:
> i tried to setup up a Linuxbridge for prioritize some interactive (Citrix / https) Traffic to 1.2.3.4 on my ADSL Link, but i think it work not correct.
---snip----
> 1) a big Download becomes never more than ~ 100kbit (the most times it will be much lower). Why that ?
> - Should it not have the speed of the Download Rate from the ingress qdisq ?
> - The ingress qdisq counter show 0 Packets send. Why isn't this work ?
---snip---
> I think i do something wrong, but can please anybody point my to the right direction ?
I couldn't make ingress policing work with bridges either.
I just changed to egress shaping on both interfaces (since it's a gateway router).
I vaguely recall someone else discussing this on the list recently - can't remember
what the result was though.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer email: damion@snapgear.com
SnapGear - A CyberGuard Company --- 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:[~2004-04-19 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 12:58 [LARTC] Prioritizing on a Bridge doesn't seen to work correct, ingress Thomas Reiß
2004-04-19 23:32 ` 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=408461A7.9040104@snapgear.com \
--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 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.