From owner-freebsd-hackers Tue Oct 1 08:13:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA22438 for hackers-outgoing; Tue, 1 Oct 1996 08:13:58 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA22430 for ; Tue, 1 Oct 1996 08:13:51 -0700 (PDT) Received: from ppp-089.etinc.com (ppp-089.etinc.com [204.141.95.148]) by etinc.com (8.6.12/8.6.9) with SMTP id LAA20174; Tue, 1 Oct 1996 11:23:32 -0400 Date: Tue, 1 Oct 1996 11:23:32 -0400 Message-Id: <199610011523.LAA20174@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: "Ulf Zimmermann" From: dennis@etinc.com (dennis) Subject: Re: isdn code Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Oct 1, 11:30am, Michael Hancock wrote: >> Subject: Re: isdn code >> On Mon, 30 Sep 1996, Terry Lambert wrote: >> >> > > >> Unless sufficient many people come out in defense of the current isdn >> > > >> code in the FreeBSD tree, it will be removed because of lack of >support >> > > >> from developers. >> > > > >> > > >What is "unsupported" about it such that it makes you want to remove >> > > >the code? >> > > >> > > Well, nobody seems to use it or support it. >> > >> > I thought many Germans were using it, since their country has a real >> > communications infrastructure, unlike ours. >> >> They have a unified ISDN policy like Japan does. Communications >> monopolies makes this easier I suppose. >> >> Surprisingly, Germany's Internet infrastructure seems pretty weak. >> International ISP's are more likely to access Europe via the UK or Sweden. >> Anyway, that's a different story. >> >> The Teles driver only supports HDLC and does not support PPP, though I >> think they are working on PPP support. I think most FreeBSD Teles Users >> in Germany prefer HDLC because it has less overhead than PPP, so most of >> the effort goes there. This doesn't help for those who need to connect to >> other vendors devices that are most likely use PPP. Oh....I am in such pain right now! PPP is a protocol that runs either async or sync...if its sync then it runs with HDLC framing...the 2 are not mutually exclusive...sync PPP runs over HDLC. So I dont know what this paragraph above means...since HDLC is not a PTP protocol that can be used by itself in most cases..... Dennis