I was playing with ppp-2.3.5 and its compression features. At one point I tested how one-sided compression works and seemed to run into a bug. Here's the relevant log snippit: pppd[434]: rcvd [CCP ConfReq id=0x2 <SuperZ 0x0001>] pppd[434]: sent [CCP ConfReq id=0x1] pppd[434]: sent [CCP ConfAck id=0x2 <SuperZ 0x0001>] pppd[434]: rcvd [CCP ConfAck id=0x1] pppd[434]: SuperZ transmit compression enabled According to the above, I request no compression but accepted the peer (server)'s request for SuperZ - which is what I wanted. According to the CCP RFC, peers ask each other if it is alright to send compressed data. Since I accepted the server's CCP request, I should then start the DEcompression engine and prepare to receive compressed data, right? What happens is ppp says xmit compression enabled, then proceeds to compress outgoing data... and does not decompress incomeing data either. Is this a known bug in ppp 2.3.5? TIA, -J - To unsubscribe from this list: send the line "unsubscribe linux-ppp" in the body of a message to [EMAIL PROTECTED]
