summaryrefslogtreecommitdiffstats
path: root/lib/libc
diff options
context:
space:
mode:
authorbrian <brian@openbsd.org>1999-03-11 01:50:04 +0000
committerbrian <brian@openbsd.org>1999-03-11 01:50:04 +0000
commit227c7c4a0642c7c917eea0240bc916aea8295450 (patch)
tree43d799d195c366087e3950a784c97b0f1f45117a /lib/libc
parentfix more comma splices that involve misuse of conjunctive adverbs (diff)
downloadwireguard-openbsd-227c7c4a0642c7c917eea0240bc916aea8295450.tar.xz
wireguard-openbsd-227c7c4a0642c7c917eea0240bc916aea8295450.zip
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/libc')
0 files changed, 0 insertions, 0 deletions