From owner-freebsd-hackers Sun Jan 11 18:14:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA07159 for hackers-outgoing; Sun, 11 Jan 1998 18:14:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.scsn.net (scsn.net [206.25.246.12]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA07132 for ; Sun, 11 Jan 1998 18:14:02 -0800 (PST) (envelope-from dmaddox@scsn.net) Received: from rhiannon.scsn.net ([208.133.153.130]) by mail.scsn.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-41950U6000L1100S0) with ESMTP id AAA205; Sun, 11 Jan 1998 21:12:26 -0500 Received: (from root@localhost) by rhiannon.scsn.net (8.8.8/8.8.7) id VAA00904; Sun, 11 Jan 1998 21:13:29 -0500 (EST) (envelope-from root) Message-ID: <19980111211328.42326@scsn.net> Date: Sun, 11 Jan 1998 21:13:28 -0500 From: dmaddox@scsn.net (Donald J. Maddox) To: John Kelly Cc: hackers@FreeBSD.ORG Subject: Re: 16650 Support(?) Reply-To: dmaddox@scsn.net References: <19980111150619.48677@scsn.net> <34b95e60.140553@mail.cetlink.net> <34B957B6.AEC4CDAF@scsn.net> <34bf6bef.3609890@mail.cetlink.net> <19980111194120.34679@scsn.net> <34c17b19.7493033@mail.cetlink.net> <19980111203118.15860@scsn.net> <34c48361.9613962@mail.cetlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <34c48361.9613962@mail.cetlink.net>; from John Kelly on Mon, Jan 12, 1998 at 02:53:14AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Mon, Jan 12, 1998 at 02:53:14AM +0000, John Kelly wrote: > On Sun, 11 Jan 1998 20:31:18 -0500, dmaddox@scsn.net (Donald J. > Maddox) wrote: > > >> It all makes sense when you see the baud rate table for 4x vs. 1x. > > > > Yeah, that's exactly it. I finally figured this out just moments > >before I got this message. My ISDN modem is a Motorola BitSURFR Pro EZ, > >and it works pretty much exactly like your description of the 3COM... > >Have you figured out a way to use both B channels under BSD? > > That's easy because it's transparent to FreeBSD. > > An AT command of S80=1 to the 3Com tells it to make a bonded PPP > Multilink call. The 3Com and the ISP's Portmaster do the rest. Once > both channels are up, the 3Com logically bonds them and sends a single > PPP data stream to FreeBSD. > > I expect the Bitsurfer has an AT command which does the same. Yeah, it would seem that way :-) Actually, the BitSURFR does have such an AT command... But... The AT command to use both B channels is 'AT@B0=2' on the BitSURFR; however, it has 3 different rate adaption protocols: V.120, AIMux, and PPP. If I use V.120, everything works great, but, unfortunately, V.120 does not support channel bonding. If I use PPP (which _does_ support channel bonding, and which works great under W95 dial-up networking), the modem connects fine, but instead of a login prompt, I just get garbage characters from the modem. I know the problem is something simple that I am just not quite grasping, since W95 dial-up networking seems to be able to log me into my ISP just fine with PPP rate adaption protocol. In short, I cannot get a working chat script to log me into my ISP if I select PPP protocol on the modem. Does any of this make any sense to you? (I hope so)