All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Geiger <tobias.geiger@web.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Where does the Bandwidth Management taking place after/before
Date: Wed, 08 Jan 2003 10:19:09 +0000	[thread overview]
Message-ID: <marc-lartc-104202202904792@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104202046703231@msgid-missing>

AFAIK:
local stuff: Application -> IPTABLES (OUTPUT) -> ROUTING -> QDISC
	routing stuff: IPTABLES (PREROUTING/FORWARD) -> ROUTING -> 
IPTABLES-POSTROUTING -> QDISC

these iptables-chains do sometimes a little wired stuff, depending on 
the jump-target/Chain (especially PREROUTING/NAT/...) sometimes 
routing-code is called to determine the route for iptables, but AFAIK 
ALL packets pass after the iptables-code the routing-code and ALWAYS as 
a LAST station the qdisc.
off course only outgoing stuff. incoming is more or less :) other way round.

Greetings

Tobias

Srikanth W wrote:
> Hi!
>  
> I want to know exactly how the packet flow is occuring in BW management?
> 
> and 
> 
> Where does the Bandwidth Management taking place after/before routing?
> 
> Kindly let me know asap.
> 
> tnr,
> Srikanth
> 
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> 
> 


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-01-08 10:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 10:07 [LARTC] Where does the Bandwidth Management taking place after/before Srikanth W
2003-01-08 10:19 ` Tobias Geiger [this message]
2003-01-08 14:01 ` [LARTC] Where does the Bandwidth Management taking place 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-104202202904792@msgid-missing \
    --to=tobias.geiger@web.de \
    --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.