summaryrefslogtreecommitdiffstats
path: root/lib/libutil
diff options
context:
space:
mode:
authorbrian <brian@FreeBSD.org>1999-03-11 01:49:15 +0000
committerbrian <brian@FreeBSD.org>1999-03-11 01:49:15 +0000
commite1bfa8246d0e06905f031d831a39c068717a807f (patch)
tree924dca68ca4d843b359e2face7811a7fa509a6f6 /lib/libutil
parent2adbdf81a7b8649a7dd26bade0f7633556308866 (diff)
downloadFreeBSD-src-e1bfa8246d0e06905f031d831a39c068717a807f.zip
FreeBSD-src-e1bfa8246d0e06905f031d831a39c068717a807f.tar.gz
Tone down the log levels (Log{ERROR,WARN} -> LogCCP)
when we've simply missed a packet. When our Predictor1 CRC is wrong (implying we've dropped a packet), don't send a ResetReq(). Instead, send another CCP ConfigReq(). *shrug* My tests show this as being far worse than the ResetReq as we may have further Nak/Rejs etc and we're basically resetting both our incoming and outgoing compression dictionaries, but rfc1978 says the ConfigReq is correct, so we'd better go along...
Diffstat (limited to 'lib/libutil')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud