Searched hist:44650 (Results 1 - 3 of 3) sorted by relevance
| /freebsd-10.0-release/usr.sbin/ppp/ | ||
| H A D | deflate.c | diff 44650 Wed Mar 10 23:49:15 MST 1999 brian 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... |
| H A D | pred.c | diff 44650 Wed Mar 10 23:49:15 MST 1999 brian 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... |
| H A D | ccp.c | diff 44650 Wed Mar 10 23:49:15 MST 1999 brian 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... |
Completed in 87 milliseconds