All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: how flexible is ingress traffic policing to bandwidth limit?
Date: Wed, 09 Jun 2004 00:52:14 +0000	[thread overview]
Message-ID: <40C65F3E.8020309@snapgear.com> (raw)
In-Reply-To: <87wu2hwp8e.fsf@stark.xeocode.com>

Greg,
> For some reason that hadn't occurred to me. That should work just fine. I
> guess I should mark the packets in iptables to avoid throttling traffic from
> gateway itself, or does match see the external ip?
The only (common) time you need to use iptables to mark traffic, is when you're using 
  egress qdiscs on your outbound (WAN) interface (to shape upload speeds) and want to 
filter based on private (LAN) IP address.

> IMQ does seem like a handy tool, but why is there a distinction at all between
> egress and ingress qdiscs at all? Why not just allow people to attach HTB as
> an ingress qdisc directly?
because you can't shape inbound traffic.  Shaping works by delaying the transmission, and
you can't delay packets that haven't arrived yet. Ingress policing just drops 
packets, and hopes the sender will slow down.

> I suppose in an ideal world the best thing would be to receive the packets,
> hand them to user-space, but not mark them as received, ie, not ack them. That
> avoids introducing any loss from the user point of view but still slows the
> flow down. But that seems fiddly and would only work for TCP I guess.
That's an interesting idea, but yeah... i think it might be a bit hard to implement, 
and violate far too many RFCs...

regards,

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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/

  reply	other threads:[~2004-06-09  0:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09  0:26 [LARTC] Re: how flexible is ingress traffic policing to bandwidth limit? Greg Stark
2004-06-09  0:52 ` Damion de Soto [this message]
2004-06-09  3:33 ` Greg Stark
2004-06-09  4:01 ` Jason Boxman
2004-06-09  8:47 ` Greg Stark
2004-06-09 19:46 ` [LARTC] Re: how flexible is ingress traffic policing to Sanjay Arora
2004-06-09 20:09 ` [LARTC] Re: how flexible is ingress traffic policing to bandwidth limit? Greg Stark
2004-06-09 21:06 ` Jason Boxman
2004-06-11  0:17 ` [LARTC] Re: how flexible is ingress traffic policing to bandwidth Andy Furniss

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=40C65F3E.8020309@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.