[3760] in linux-net channel archive

home help back first fref pref prev next nref lref last post

Re: bsd_comp errors

daemon@ATHENA.MIT.EDU (John Saunders)
Fri Jul 19 20:50:51 1996

To: linux-net@vger.rutgers.edu
From: john@nlc.net.au (John Saunders)
Date: 	17 Jul 1996 15:52:06 GMT

I had problems with bsd_comp on 2 Linux boxes running kernel 1.3.57 and
pppd 2.2.0e. Both machines were almost the same hardware wise, same modems,
and running exactly the same RedHat install. Go figure. I just disabled
bsd_compe in my /etc/ppp/options file and let the modem compress.

Graham Mitchell (gmitch@woodlea.wintermute.co.uk) wrote:
> On 12 Jul 96 at 12:15, Jon Lewis wrote:
> 
> > I've just recently started using bsd_comp.o.  Are these errors just 
> > likely line noise garbling some BSD compressed data?
> > 
> > bsd_decomp27: bad sequence # 2, expected 0
> > bsd_decomp27: bad CLEAR
> 
> Hmmm..... Ive recently started getting errors with this too. Mine 
> started to happen when my ISP upgraded from 1.3.68 to 2.0.0
> 
> Jul  3 22:26:45 woodlea linux: bsd_decomp0: bad sequence # 1, expected -1  
> Jul  3 23:32:42 woodlea linux: bsd_decomp0: peer should have cleared dictionary on 17363 
> Jul  3 23:32:42 woodlea linux: bsd_decomp0: bad sequence # 17369, expected 17363 
> 
> Jul  5 03:53:20 woodlea linux: bsd_decomp0: bad sequence # 4435, expected 4430 
> Jul  5 19:02:50 woodlea linux: bsd_decomp0: peer should have cleared dictionary on 5905 
> Jul  5 19:02:50 woodlea linux: bsd_decomp0: bad code 0x180 oldcode=0x4e max_ent=0x100 explen=4 seqno=5907 
> Jul  5 19:02:51 woodlea pppd[3822]: Lost compression sync: disabling compression
> 
> Jul  5 20:54:36 woodlea linux: bsd_decomp0: bad sequence #1, expected -1 
> Jul  5 20:52:08 woodlea pppd[5904]: demuxprotrej: Unrecognized Protocol-Reject for protocol 0x6d 
> Jul  5 20:52:08 woodlea pppd[5904]: demuxprotrej: Unrecognized Protocol-Reject for protocol 0x10 
> Jul  5 20:52:08 woodlea pppd[5904]: demuxprotrej: Unrecognized Protocol-Reject for protocol 0x32 
> 
> 
> Does anyone have any ideas what causes this? I'm running 2.0.4, and 
> ppp2.2.0f. MY ISP is running 2.0.0 and 2.2.0f. There has been silence 
> from them about this problem, despite a couple of emails, so any help 
> would be gratefully accepted.
> 
> 
> 
> Graham
> ---------------------------------------------
> There's a war out there
> A world war
> And it's not about who's got the most bullets
> It's about who controls the information
> What we see and hear
> How we work
> What we think
> It's all about the information
> ---------------------------------------------
> 

-- 
--            +------------------------------------------------------------+
        .     | John Saunders  - john@nlc.net.au                   (EMail) |
    ,--_|\    |                - http://www.nlc.net.au/              (WWW) |
   /  Oz  \   |                - 018-223-814 or 02-477-2881        (Phone) |
   \_,--\_/   | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional,   |
         v    | and above all friendly, internet connection service.       |
              +------------------------------------------------------------+


home help back first fref pref prev next nref lref last post