From owner-freebsd-questions@FreeBSD.ORG  Fri Jun 17 19:15:34 2011
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 9BD691065675
	for <freebsd-questions@freebsd.org>;
	Fri, 17 Jun 2011 19:15:34 +0000 (UTC)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from x.it.okstate.edu (x.it.okstate.edu [139.78.2.13])
	by mx1.freebsd.org (Postfix) with ESMTP id 4F22C8FC18
	for <freebsd-questions@freebsd.org>;
	Fri, 17 Jun 2011 19:15:34 +0000 (UTC)
Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1])
	by x.it.okstate.edu (8.14.4/8.14.4) with ESMTP id p5HIrn6N073196
	for <freebsd-questions@freebsd.org>;
	Fri, 17 Jun 2011 13:53:49 -0500 (CDT)
	(envelope-from martin@dc.cis.okstate.edu)
Message-Id: <201106171853.p5HIrn6N073196@x.it.okstate.edu>
To: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <73182.1308336776.1@x.it.okstate.edu>
Date: Fri, 17 Jun 2011 13:53:48 -0500
From: Martin McCormick <martin@dc.cis.okstate.edu>
Subject: Second Network Almost but Not Quite Works.
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 19:15:34 -0000

The system in question has its primary NIC on one particular
network and a default route to the gateway on that network and
all of that works fine.

	I needed the system to communicate fully on two
different networks so we enabled the second interface card and
it works on that second subnet. You can connect to hosts there
and hosts on that network see the new interface. The problem is
that  it doesn't know anything about the router on that second
network.

	I don't want it to loose the default router but it needs
to be fully connected from the second interface as it is a name
server and it is about to move from one network to the other.

	I enabled the second interface as follows:

ifconfig fxp1 inet 192.168.1.13  netmask 255.255.255.0

	Is the route add command what I need to cause that
interface to speak to the router and to hear packets addressed
to it from that router?

	The routing issue seems to be the only connectivity
problem that the second interface has.

	Thank you.