From owner-freebsd-questions@FreeBSD.ORG  Fri Jul 25 02:54: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 84DFE37B401
	for <freebsd-questions@freebsd.org>;
	Fri, 25 Jul 2003 02:54: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 E2A4543F75
	for <freebsd-questions@freebsd.org>;
	Fri, 25 Jul 2003 02:54:26 -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 19fzHG-0003Ye-00
	for freebsd-questions@freebsd.org; Fri, 25 Jul 2003 02:54:18 -0700
Message-Id: <5.2.0.9.2.20030725024554.02a305e0@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 02:55: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: 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 09:54:27 -0000


I have a system with a 'vr' driver NIC in it. ifconfig sees the interface 
(and I have miibus and vr in my kernel) yet I cannot assign an IP address 
to it with rc.conf or ifconfig.... it just doesn't "stick."

If I use ifconfig to take it down and bring it back up nothing changes but 
the "RUNNING" text in ifconfig's status report. (It seems to correctly 
sense the media type too.)

dmesg contains the following:

>vr0: <VIA VT6102 Rhine II 10/100BaseTX> port 0xec00-0xecff mem 
>0xe5803000-0xe58030ff irq 11 at device 18.0 on pci0
>vr0: Ethernet address: 00:0a:e6:7d:84:22
>miibus1: <MII bus> on vr0

I am sure there is nothing fundamentally wrong with the system because this 
interface USED to work back in my plain vanilla test-install days... I must 
have done something to break it but I can't imagine what! I have the 
correct devices in my kernel (vr and miibus). I have turned off all 
firewall/nat stuff on this box too.

(I know, vr interfaces stink, but it's what I have to use until I 
decommission the old server and take out the nice Kingston card in there.)

TIA,
Matt