From owner-freebsd-isp  Fri Apr 25 09:58:49 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA27030
          for isp-outgoing; Fri, 25 Apr 1997 09:58:49 -0700 (PDT)
Received: from super-g.inch.com (super-g.com [204.178.32.161])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA27023
          for <freebsd-isp@FreeBSD.org>; Fri, 25 Apr 1997 09:58:46 -0700 (PDT)
Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.6.9) with SMTP id NAA12739; Fri, 25 Apr 1997 13:14:01 -0400 (EDT)
Date: Fri, 25 Apr 1997 13:14:01 -0400 (EDT)
From: spork <spork@super-g.com>
X-Sender: spork@super-g.inch.com
To: Steve <shovey@buffnet.net>
cc: Damian Hamill <damian@cablenet.net>, freebsd-isp@FreeBSD.org
Subject: Re: SMTP gateway clients
In-Reply-To: <Pine.BSI.3.95.970425111858.4465A-100000@buffnet11.buffnet.net>
Message-ID: <Pine.BSF.3.95.970425131204.12617B-100000@super-g.inch.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> I have annex4000 term servers.  I can set a dedicated IP to a user, but if
> they connect on a term server in a different class C they get the IP but
> there is no route to it.

The best answer I get get from Xylogics on this was to turn on RIP so that
when the user dialed in, the Annex would let everything on the network see
the new route.  The problem is that it only updates every 30 seconds, so
an impatient user would hang up thinking the link was dead.  We opted to
only give out static IPs on a small hunt that resides on one annex...

Charles