All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to realize "MLPPP LFI"
Date: Sun, 30 May 2004 07:29:20 +0000	[thread overview]
Message-ID: <40B98D50.30003@dsl.pipex.com> (raw)
In-Reply-To: <20040526020533.5B3C54029@outpost.ds9a.nl>

swcims wrote:
> Hi,Andy
> 	I don't understand what you mean.I have a adsl router based on mips linux2.4.17.In this adsl router,one side is 100Mbit ethernet card,another side is adsl line,as following:
> 	LAN------(ethernet)--------ADSL Router------(ADSL line)-------------WAN
> 	On this adsl line,it can configue rfc1483bridge or router,or pppoe to get wan ip from ISP. I think this side(upstream) is the bottleneck link. I ported iproute2/tc on this router and i can control traffice on the upstream line.
> 	But I got completely no idea for doing these: (from TR059 Technical Report DSL Forum)
> 	1.The device MUST support the capability to fragment AF and BE traffic in order to constrain the perturbing impact of AF and BE packets on EF traffic delay, for example using a mechanism such as MLPPP LFI.(RFC1990)
>  	2. The packet size threshold before fragmenting AF and BE packets MUST be configurable. 
> 	Thank you very much!

What I mean is that if you want to mess around with packets below ip
level, the other end  - your ISP/teleco , will need to be running
software that knows what you are doing so that it can  reconstruct the
packets before routing.

If you have a specific need for your upstream not to be delayed more
than X ms you could adjust your MTUs/MSS clamp - the size will depend on
your bitrate and max delay required.

Andy.


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

      parent reply	other threads:[~2004-05-30  7:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26  1:51 [LARTC] how to realize "MLPPP LFI" swcims
2004-05-27  1:30 ` swcims
2004-05-28 18:57 ` Andy Furniss
2004-05-29  6:23 ` swcims
2004-05-30  7:29 ` Andy Furniss [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=40B98D50.30003@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.