From owner-freebsd-questions@FreeBSD.ORG  Fri Jul 25 03:34:27 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EBA5637B401
	for <freebsd-questions@freebsd.org>;
	Fri, 25 Jul 2003 03:34:27 -0700 (PDT)
Received: from wrongcrowd.com (dsl231-036-178.sea1.dsl.speakeasy.net
	[216.231.36.178])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 87DDA43F93
	for <freebsd-questions@freebsd.org>;
	Fri, 25 Jul 2003 03:34:27 -0700 (PDT)
	(envelope-from matt@wrongcrowd.com)
Received: from [192.168.1.99] (helo=thunderbird.wrongcrowd.com)
	by wrongcrowd.com with esmtp (Exim 3.34 #1)
	id 19fzu7-0003gb-00
	for freebsd-questions@freebsd.org; Fri, 25 Jul 2003 03:34:27 -0700
Message-Id: <5.2.0.9.2.20030725032137.02a3fcf8@mail.speakeasy.net>
X-Sender: matt@192.168.1.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 25 Jul 2003 03:34:34 -0700
To: freebsd-questions@freebsd.org
From: Matt Staroscik <matt@wrongcrowd.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: Can't assign IP to network interface vr0
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
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, 25 Jul 2003 10:34:28 -0000


Solved it: after more searching, the great Google hath taught me that you 
can't have 2 IP addresses on the same subnet on one machine... and I was 
trying to set the NICs to 192.168.1.n and .n+1. Too bad this doesn't drop a 
message in a logfile though. Or if it did, I wasn't looking in the right place.

You learn something new every day!