From owner-freebsd-hackers  Wed Dec 10 14:57:53 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA28446
          for hackers-outgoing; Wed, 10 Dec 1997 14:57:53 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from webserver.smginc.com (webserver.smginc.com [204.170.176.2])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA28424
          for <hackers@FreeBSD.ORG>; Wed, 10 Dec 1997 14:57:43 -0800 (PST)
          (envelope-from AdamT@smginc.com)
Received: from smginc.com ([204.170.177.4]) by webserver.smginc.com
          (post.office MTA v2.0 0813 ID# 0-13723) with SMTP id AAA284
          for <hackers@FreeBSD.ORG>; Wed, 10 Dec 1997 17:59:44 -0500
Received: by smginc.com with Microsoft Mail
	id <348F48CE@smginc.com>; Wed, 10 Dec 97 17:58:38 PST
From: Adam Turoff <AdamT@smginc.com>
To: hackers <hackers@FreeBSD.ORG>
Subject: RE: I seriously need some networking help
Date: Wed, 10 Dec 97 17:57:00 PST
Message-ID: <348F48CE@smginc.com>
Encoding: 68 TEXT
X-Mailer: Microsoft Mail V3.0
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


>Eivind Eklund wrote:
> >
> > "Jamil J. Weatherbee" <jamil@trojanhorse.ml.org> writes:
> >
> > > Here is a diagram of what I want to do (if this is possible):
> > > I have not been able to get this configured:
> > >
> > > The ip addresses have been altered to protect innocent networks of
> > > unprotected wincrap 95 machines.
> > >
> > >
> > > service provider ------\
> > >                       |
> > >                       |
> > >                 Ascend Pipeline 50
> > >                  123.123.62.161/27 (router0)
> > >                         |
> > >                         |  <----- crossover cable
> > >                       (ed1)
> > >                 FreeBSD Firewall
> > >                  123.123.62.162/27 (core)--(ppp0-modem(remote user)
> > >                       (ed0)                            proxied to
> > >                         |                               ethernet
> > >                         |
> > >                         |
> > >                 Windoze ethernet 123.123.62.161-190/27
> >
> > This one seems to be possible, but it will be somewest, though)
> >
> > Eivind.
>
> better answer..
> use address translation between the ascend and the FBSD machine
> (using natd)
>
> allloceate 192.168.1.x to the mahines that dial in
> let the FBSD machien use normal routing..

Just another datapoint.  I have a similar network setup:
 FBSD box with two identical PCI Ethernet cards,
 Crossover cable to a Cicso router
 std. cable into an ethernet hub

The box works fine on both networks.  The only problem
is that whenever the T1 goes down, the ethernet port
on the router goes down.  Apparently, when FBSD detects
a dead network interface, it removes all the routes associated
with that interface.

Therefore, everytime I get a hiccup on the T1, I need to
telnet in on the other interface and reboot the box in order for
the box to straighten itself out.

I looked into some docs and found a mention of RIP doing this
and routed working with RIP to discover and fix problems like
this.  (I took the recommendation from the man page and reset
the timeout to 45 seconds.)

This has been happening a lot recently, and it caused the
"stupid fast webserver" to be offline for a weekend.

Any thoughts?

Thanks in advance,

 -- Adam.
adamt@smginc.com