From owner-freebsd-current Fri Apr 9 23:50: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from EventHorizon.STARDreams.org (maccess-01-011.magna.com.au [203.111.85.11]) by hub.freebsd.org (Postfix) with ESMTP id B94AD15048 for ; Fri, 9 Apr 1999 23:49:57 -0700 (PDT) (envelope-from guru@b0rk.looksharp.net) Received: from EventHorizon ([10.144.144.1]) by EventHorizon.STARDreams.org (Netscape Mail Server v2.01) with SMTP id AAA241; Sat, 10 Apr 1999 16:49:03 +1000 Message-Id: <3.0.3.32.19990410164553.00b326f0@b0rk.looksharp.net> X-Sender: guru@b0rk.looksharp.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sat, 10 Apr 1999 16:45:53 +1000 To: Brian Somers From: GuRu Subject: Re: PPP problems in -CURRENT Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199904090824.JAA57701@keep.lan.Awfulhak.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:24 4/9/99 +0100, Brian Somers wrote: >Does anything different happen if you > > set accmap 000a0000 > >in your ppp.conf ? If not, you're going to have to approach your ISP >and ask them why their ppp implementation is ignoring our requests >(which needless to say violates the rfc). It would appear that a few more things are wrong, because the setting doesn't help on my 4.0-CURRENT box, but downgrading to 3.1-RELEASE fixes the problem. With this in mind, I copied and gzipped the 3.1-RELEASE ppp binaries (known to work) to a safe place, upgraded to 4.0-CURRENT once more, and attempted to use the 3.1-REL binaries with 4.0. The strange thing is that it doesn't work. I'm retreating to the relative sanity of 3.1-STABLE, will let you know what happens. -- K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message