From owner-freebsd-questions@FreeBSD.ORG Wed Sep 24 15:30:28 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 48F03601 for ; Wed, 24 Sep 2014 15:30:28 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id E3D82D2D for ; Wed, 24 Sep 2014 15:30:27 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s8OFUQvX012467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 24 Sep 2014 16:30:26 +0100 (BST) Date: Wed, 24 Sep 2014 16:30:26 +0100 From: Karl Pielorz To: freebsd-questions@freebsd.org Subject: Re: Default route (i.e. 'defaultrouter') ignored for VLAN rc.conf setup? Message-ID: <9D720519FAD1B54D1D074FBE@Mail-PC.tdx.co.uk> In-Reply-To: References: X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2014 15:30:28 -0000 --On 24 September 2014 16:15 +0100 Karl Pielorz wrote: > Hi, > > I've got a 10.0-R box setup with: > > cloned_interfaces="bge0.99" > ifconfig_bge0_99="inet 192.168.0.20 netmask 255.255.255.0" > defaultrouter="192.168.0.1" > > This correctly sets up 'bge0.99' at boot time, but doesn't set the > default route. I've managed to fix this - by using: cloned_interfaces="bge0.99" ifconfig_bge0="up" <---- You need this line! ifconfig_bge0_99="inet 192.168.0.20 netmask 255.255.255.0" defaultrouter="192.168.0.1" A little annoying as I'd been bitten by that 'oddity' (i.e. requiring the 'up' line) when working with LAGG interfaces... At least it works now (and it's in the list archives), -Karl