Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc,comp.dcom.isdn
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!spool.mu.edu!sol.ctr.columbia.edu!news.uoregon.edu!news.bc.net!rover.ucs.ualberta.ca!atha!sgiblab!sgigate.sgi.com!swrinde!howland.reston.ans.net!nntp.crl.com!pacbell.com!amdahl.com!netcomsv!uu4news.netcom.com!calcite!vjs
From: vjs@calcite.rhyolite.com (Vernon Schryver)
Subject: Re: Motorola Bitsurfer Pro + FreeBSD
Message-ID: <DJn6IA.7oJ@calcite.rhyolite.com>
Organization: Rhyolite Software
Date: Fri, 15 Dec 1995 19:08:33 GMT
References: <DJKC80.Aqu@rci.ripco.com> <DJL3r9.MCC@calcite.rhyolite.com> <4are91$h5a@agate.berkeley.edu>
Lines: 68
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:10501 comp.dcom.isdn:23242
In article <4are91$h5a@agate.berkeley.edu> jkh@violet.berkeley.edu (Jordan K. Hubbard) writes:
> .... The bonding schemes used
>internally by the various TAs ARE NOT GENERALLY COMPATIBLE and if you
>try to put a BitSurfer on one end of a connection and an ADTRAN on the
>other, it WILL NOT WORK! Use TAs from the same manufacturer on each end
>if you want to do this.
> ...
Or use TA's that do use generally compatible "internal" protocols on their
B channels. There are at least 3 common protocols that have plenty
of inter-vendor interoperability:
1. RFC 1717 MP. In this case the, the TA converts between a single
PPP stream, usually async, on the "external" or computer side
and two B channels running RFC 1618 sync PPP bundled together
with RFC 1717 MP.
I understand that the BitSurFR Pro does this. Am I wrong?
Isn't this how PSI expects its customers to call its zillions
of Ascend ISDN servers and get more than 64 kbps?
2. BONDING, which stands for something or other, has a big industry
consortium, and a lot of inter-vendor compatibility.
3. "round robin" or "BF&I" for IP packets.
(I think the #2 and #3 are dead issues, although they are still being
sold and I continue to receive reports concerning my code doing BF&I
with other vendor's systems.)
Those following this thrread in to comp.unix.bsd.freebsd.misc should
note that it was cross-posted to comp.dcom.isdn. Readers of comp.dcom.isdn
have noticed that many reports from operators of Internet Service
Providers using BONDING or RFC 1717 MP with various ISDN servers, as
well as a bazillion users of PC's running Windows, DOS, and NT using
various ISDN TA's and connecting to those ISP's. Readers of comp.dcom.isdn
have seen plenty of reports of multi-vendor interoperability.
Readers of comp.dcom.isdn will also recall the public reports of the
MP ISDN interoperability meeting last March at PacBell's San Ramon
facility. See http://www.ciug.org/ciug/ciug.html and notice that
among the particpants were TA vendors. (Those who continue to ask
about Microsoft's MP software plans might ponder the 15th company
listed in http://www.ciug.org/ciug/mpptest.html)
Readers of comp.unix.bsd.freebsd.misc should also note that the
BitSurfer (or however Motorola spells "surfer") and the BitSurfer Pro
are different boxes.
Readers of comp.unix.bsd.freebsd.misc who have argued with me about
whether the BitSurFR does RFC 1717 MP might want to argue with the
author of the following first hand report:
] From: daleg@fred.net (Dale Ghent)
] Newsgroups: comp.dcom.isdn
] Subject: Re: Bitsurfr pro and ISDN questions
] Date: 15 Dec 1995 17:18:22 GMT
] Message-ID: <4asaku$bj5@zippy.cais.net>
] References: <30cf06f3.7191559@news.frontiernet.net>
] ...
] The BSP will do MultiLink PPP (MP), which is 2B running at 112k. You
] can't do 128 because of your UART's limitations. It can do only 115.2k.
] ...
Vernon Schryver vjs@rhyolite.com