Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Jun 2004 13:33:28 +0100
From:      Brian Somers <brian@Awfulhak.org>
Cc:        cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/usr.sbin/ppp acf.c async.c hdlc.c hdlc.h link.c link.h lqr.c lqr.h mbuf.h sync.c
Message-ID:  <20040630133328.071bc07b@dev.lan.Awfulhak.org>
In-Reply-To: <200406301224.i5UCOuSc035406@repoman.freebsd.org>
References:  <200406301224.i5UCOuSc035406@repoman.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 30 Jun 2004 12:24:56 +0000 (UTC), Brian Somers <brian@FreeBSD.org> wrote:
> brian       2004-06-30 12:24:56 UTC
> 
>   FreeBSD src repository
> 
>   Modified files:
>     usr.sbin/ppp         acf.c async.c hdlc.c hdlc.h link.c link.h 
>                          lqr.c lqr.h mbuf.h sync.c 
>   Log:
>   Re-implement LQM, this time according to the rfc.
>   
>   PR:             11293
>   MFC after:      4 weeks
[.....]

I'd be interested in peoples comments on the analysis that now
turns up with ``set log +lqm''.  My only real-world testing has
been with my ADSL provider, and with output such as:

LQM: ADSL: Input:
LQM:   Magic:          22264bc4   LastOutLQRs:    00000011
LQM:   LastOutPackets: 0000267d   LastOutOctets:  00ba1202
LQM:   PeerInLQRs:     00000010   PeerInPackets:  02f31620
LQM:   PeerInDiscards: 00000000   PeerInErrors:   00000000
LQM:   PeerInOctets:   bc00380e   PeerOutLQRs:    00000010
LQM:   PeerOutPackets: 4348204d   PeerOutOctets:  4441502f
[.....]
LQM: ADSL: Input:
LQM:   Magic:          22264bc4   LastOutLQRs:    00000012
LQM:   LastOutPackets: 00002a91   LastOutOctets:  00ce7585
LQM:   PeerInLQRs:     00000011   PeerInPackets:  02f31a34
LQM:   PeerInDiscards: 00000000   PeerInErrors:   00000000
LQM:   PeerInOctets:   bc14a3b9   PeerOutLQRs:    00000011
LQM:   PeerOutPackets: 00000000   PeerOutOctets:  00004545
LQM: Analysis:
LQM:   Outbound lossage: 0 LQRs (0 en route), 0 packets, -2088 octets
LQM:   Inbound lossage: -1128801017 packets, -1145157573 octets
LQM:                    Likely due to transport congestion

I can only blame their implementation -- believe me, those
PeerOutPackets/Octets are not for real!!!  Perhaps they're
including some L2TP header info or something with their
PeerInOctets value...

Cheers.

-- 
Brian <brian@Awfulhak.org>                        <brian@[uk.]FreeBSD.org>
      <http://www.Awfulhak.org>;                   <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040630133328.071bc07b>