From owner-freebsd-bugs  Tue Oct 15 13:47:10 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA07305
          for bugs-outgoing; Tue, 15 Oct 1996 13:47:10 -0700 (PDT)
Received: from typhoon.dial.pipex.net (typhoon.dial.pipex.net [158.43.128.46])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA07300
          for <bugs@freebsd.org>; Tue, 15 Oct 1996 13:47:07 -0700 (PDT)
Received:  from gazebo.candler.demon.co.uk by typhoon.dial.pipex.net (8.7.5/)
	id VAA28609; Tue, 15 Oct 1996 21:46:04 +0100 (BST)
Received: (from brian@localhost) by gazebo.candler.demon.co.uk (8.6.12/8.6.9) id VAA02941; Tue, 15 Oct 1996 21:39:12 +0100
From: Brian Candler <B.Candler@pobox.com>
Message-Id: <199610152039.VAA02941@gazebo.candler.demon.co.uk>
Subject: Re: IP bugs in FreeBSD 2.1.5
To: julian@whistle.com (Julian Elischer)
Date: Tue, 15 Oct 1996 21:39:10 +0100 (BST)
Cc: bugs@freebsd.org, nato-ws@ripe.net, t12@psg.com
In-Reply-To: <3263EBFC.1CFBAE39@whistle.com> from "Julian Elischer" at Oct 15, 96 12:54:36 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > I have just returned from a NATO-sponsored Advanced Networking Course held
> > in St Petersburg, Russia, where I was the chief instructor.
> > 
> > For our PC-based practical sessions we used FreeBSD 2.1.5.
> >
> NEAT!
> 
> I hope each participant got a FreeBSD cdrom as part of the 
> course materials! :)

We thought about it, but the budget didn't stretch far enough for the Walnut
Creek ones, and there wasn't enough time to make our own. We did install
from CD though, which let us get the software running before our Internet
connectivity was up. You'll be pleased to hear that there *are* local
mirrors of FreeBSD in Russia though :-)

> > We uncovered a
> > number of bugs in the TCP/IP code, which I would like to report in the hope
> > they can be fixed in some future release.
> 
> certainly..
> Have you looked at any of these problems with 2.2?

Sorry, no. We stuck with the 2.1.5 release code, as that was what was on the
CD.

Brian.