All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: Re: [LARTC] how to realize "MLPPP LFI" on linux
@ 2004-05-31  1:32 swcims
  2004-06-02  1:52 ` swcims
  2004-06-02  9:10 ` Ed Wildgoose
  0 siblings, 2 replies; 3+ messages in thread
From: swcims @ 2004-05-31  1:32 UTC (permalink / raw)
  To: lartc

Hi,Andy
	Thank your very much!
	For the MLPPP LFI,I found that in Cisco configuration,it use "ppp multilink;ppp multilink fragmentation;ppp multilink fragment-delay 20;ppp multilink interleave " command to enable MLPPP LFI.So I think just realizing the same function on my linux router would be fine.But I got no idea how to do this on linux.So is there anything with iproute2?Would you please supply some suggestions?
	As for "The packet size threshold before fragmenting AF and BE packets MUST be configurable", I am completely lost.Any advise is highly appreciated!
	Thank you again!


	

==== 2004-05-30 15:29:20 You wrote£º===
>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.
>
>
>

= = = = = = = = = = = = = = = = = = = 			

¡¡¡¡Regards.
 
				 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡swcims
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡swcims@163.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2004-05-31

ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿË\x01\x14™¨¥Šx%ŠË\x7f,\x04S\vùšŠYšŸ÷lõ¯ç–^[m§ÿÿ™¨¥™©ÿvÏZþy\x7f™¨¥™©ÿ–+-ŠwèþV«µÁÎY3ÿ†Ûiÿÿåj»\þŠà

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-06-02  9:10 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-05-31  1:32 Re: [LARTC] how to realize "MLPPP LFI" on linux swcims
2004-06-02  1:52 ` swcims
2004-06-02  9:10 ` Ed Wildgoose

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.