From owner-freebsd-questions  Wed Jan 18 06:16:18 1995
Return-Path: questions-owner
Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id GAA29404 for questions-outgoing; Wed, 18 Jan 1995 06:16:18 -0800
Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id GAA29395; Wed, 18 Jan 1995 06:16:17 -0800
X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol
To: ROBIN@ptnsct.nis.za (Robin Hunt)
cc: questions@FreeBSD.org
Subject: Re: route add problem with 2.1 release? 
In-reply-to: Your message of "Wed, 18 Jan 1995 09:46:41 +0200."
             <950118094641.373d@ptnsct.nis.za> 
Date: Wed, 18 Jan 1995 06:16:16 -0800
Message-ID: <29393.790438576@freefall.cdrom.com>
From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>
Sender: questions-owner@FreeBSD.org
Precedence: bulk

> I was using 2.0-RELEASE FreeBSD (and how well it works, I might add!), then
> upgraded to 2.1. Since then, I can access machines on our local net but
> not beyond our gateway machine, reason being 

Actually, just to avoid confusion in the future: You aren't running
2.1, 2.1 hasn't even been released yet! :-) What you're running is
referred to as 2.0-current (or 2.0C for short).  The fact that uname
identifies the OS as 2.1.0-Development simply means that you're running
2.1-to-be.. :)

> route add <address>
> 
> gives the following error:
> 
> writing to routing socket: Protocol not supported
> add net default: gateway nis03: Protocol not supported

Did you upgrade the route binary when you upgraded the kernel?
Try a make world in /usr/src.

					Jordan