From owner-freebsd-current@FreeBSD.ORG Tue Apr 16 15:44:20 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DDF59EC0; Tue, 16 Apr 2013 15:44:20 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) by mx1.freebsd.org (Postfix) with ESMTP id 8767126E; Tue, 16 Apr 2013 15:44:19 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.5/8.14.5) with ESMTP id r3GFiNL6014246; Tue, 16 Apr 2013 10:44:24 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.5/8.14.5/Submit) id r3GFiNaa014245; Tue, 16 Apr 2013 10:44:23 -0500 (CDT) (envelope-from brooks) Date: Tue, 16 Apr 2013 10:44:23 -0500 From: Brooks Davis To: Willy Offermans Subject: Re: control of order of inet devices Message-ID: <20130416154423.GD98205@lor.one-eyed-alien.net> References: <20130416135621.GE3286@vpn.offrom.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZJcv+A0YCCLh2VIg" Content-Disposition: inline In-Reply-To: <20130416135621.GE3286@vpn.offrom.nl> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Apr 2013 15:44:20 -0000 --ZJcv+A0YCCLh2VIg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 16, 2013 at 03:56:21PM +0200, Willy Offermans wrote: > Dear FreeBSD friends, >=20 > How can I control the order of the network devices in FreeBSD. >=20 > For example, the command ifconfig lists the network devices: >=20 > pcn0: flags=3D8802 metric 0 mtu 1500 > options=3D80000 > ether 00:0c:46:ea:2b:32 > nd6 options=3D29 > media: Ethernet 100baseFX > status: no carrier > rl0: flags=3D8843 metric 0 mtu 15= 00 > options=3D2008 > ether 00:11:6b:99:7c:5a > inet XXX.XXX.24.4 netmask 0xffffff80 broadcast 137.226.24.127 > inet6 fe80::211:6bff:fe99:7c5a%rl0 prefixlen 64 scopeid 0x4=20 > nd6 options=3D29 > media: Ethernet autoselect (100baseTX ) > status: active > nfe0: flags=3D8802 metric 0 mtu 1500 > options=3D82008 > ether 00:1b:fc:df:a1:33 > nd6 options=3D29 > media: Ethernet autoselect (none) > status: no carrier > plip0: flags=3D8810 metric 0 mtu 1500 > nd6 options=3D29 > lo0: flags=3D8049 metric 0 mtu 16384 > options=3D600003 > inet6 ::1 prefixlen 128=20 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7=20 > inet 127.0.0.1 netmask 0xff000000=20 > nd6 options=3D21 > tap0: flags=3D8843 metric 0 mtu 1= 500 > options=3D80000 > ether 00:22:19:10:8d:bb > inet XXX.XXX.24.19 netmask 0xffffffff broadcast 137.226.24.19 > inet6 fe80::2bd:83ff:fe68:7200%tap0 prefixlen 64 scopeid 0x8=20 > nd6 options=3D21 > media: Ethernet autoselect > status: no carrier >=20 > pcn0 being first. However, I would like tap0 being first and of course > without any output ordering trick. The order is dictated by the order the drivers are probed by the kernel. When the devices are created they are added to a linked list. There is no practical way to control the order and it has little or no effect. -- Brooks --ZJcv+A0YCCLh2VIg Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFRbXHWXY6L6fI4GtQRAnu9AKCAx1z0Ns3LdGZb+OEthXHUXoubAQCgr0YG ba2xOdoX8hi1TH33bqevAFE= =vPsr -----END PGP SIGNATURE----- --ZJcv+A0YCCLh2VIg--