From owner-freebsd-isdn  Mon Jun 15 09:48:09 1998
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA12733
          for freebsd-isdn-outgoing; Mon, 15 Jun 1998 09:48:09 -0700 (PDT)
          (envelope-from owner-freebsd-isdn@FreeBSD.ORG)
Received: from ns1.yes.no (ns1.yes.no [195.119.24.10])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12652
          for <freebsd-isdn@FreeBSD.ORG>; Mon, 15 Jun 1998 09:48:00 -0700 (PDT)
          (envelope-from eivind@bitbox.follo.net)
Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218])
	by ns1.yes.no (8.8.7/8.8.7) with ESMTP id QAA28399;
	Mon, 15 Jun 1998 16:47:33 GMT
Received: (from eivind@localhost)
	by bitbox.follo.net (8.8.8/8.8.6) id SAA28759;
	Mon, 15 Jun 1998 18:47:33 +0200 (MET DST)
Message-ID: <19980615184732.03805@follo.net>
Date: Mon, 15 Jun 1998 18:47:32 +0200
From: Eivind Eklund <eivind@yes.no>
To: hm@hcs.de, jhs@muc.de
Cc: freebsd-isdn@FreeBSD.ORG
Subject: Re: Success report for isdnd 00.62 + FreeBSD 2.2.6-RELEASE + Creatix S0-16
References: <199806141549.RAA00687@jhs.muc.de> <m0ylUM4-0000dfC@hcswork.hcs.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <m0ylUM4-0000dfC@hcswork.hcs.de>; from Hellmuth Michaelis on Mon, Jun 15, 1998 at 10:11:04AM +0200
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Mon, Jun 15, 1998 at 10:11:04AM +0200, Hellmuth Michaelis wrote:
> >From the keyboard of Julian Stacey:
> 
> > Just a success report for isdnd 00.62 + FreeBSD 2.2.6-RELEASE + Creatix S0-16.
> 
> Thanks a lot, Julian!

Just to give a status report for the multilink support: After having
done a number of extensions to i4brbch, I'm getting packets through to
my portmaster, but I'm not getting any data bak (the rx queue in the
rbch linktab remains empty).

Right now (in another window) I'm investigating where the data is lost
- I know the userland mppp code I'm using work with a slightly hacked
bisdn, so the problem is somewhere in the interactions with i4b or in
i4b.  I hope to have it licked shortly.

Eivind.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message