From owner-freebsd-net@FreeBSD.ORG  Wed Dec  3 16:31:01 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 7013BE48
 for <freebsd-net@freebsd.org>; Wed,  3 Dec 2014 16:31:01 +0000 (UTC)
Received: from forward20.mail.yandex.net (forward20.mail.yandex.net
 [IPv6:2a02:6b8:0:1402::5])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "forwards.mail.yandex.net",
 Issuer "Certum Level IV CA" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 2670B623
 for <freebsd-net@freebsd.org>; Wed,  3 Dec 2014 16:31:01 +0000 (UTC)
Received: from web23g.yandex.ru (web23g.yandex.ru [95.108.253.232])
 by forward20.mail.yandex.net (Yandex) with ESMTP id CCD63104126E
 for <freebsd-net@freebsd.org>; Wed,  3 Dec 2014 19:30:47 +0300 (MSK)
Received: from 127.0.0.1 (localhost [127.0.0.1])
 by web23g.yandex.ru (Yandex) with ESMTP id 5CDB932010C1;
 Wed,  3 Dec 2014 19:30:47 +0300 (MSK)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail;
 t=1417624247; bh=djKmER3z8UTKgf0wMq4EBg3ECaO9Sd9qOkwhD+v8Mk4=;
 h=From:To:Subject:Date;
 b=G/Vg7Pk7zQ1LBXiVJSdAe4ZEhKq+1aYv6STanYWGjCQA9uvA1s6FqWB/Cn6E+rxWF
 ba1AWqkSLtf2d+HO/2NifPStATMWF6fnRHFdldFO8FWjDgDt+O7GG+SbSJLrCR0Uoc
 CmFtVeiKwqbzvUM69SWHhAXceE0IDl7OD60sGM6U=
Received: from 92b91f64.rdns.100tb.com (92b91f64.rdns.100tb.com
 [146.185.31.100]) by web23g.yandex.ru with HTTP; 
 Wed, 03 Dec 2014 19:30:47 +0300
From: Martin Hanson <greencoppermine@yandex.com>
To: freebsd-net@freebsd.org
Subject: NICs devices switches "pshycial" place on each boot
MIME-Version: 1.0
Message-Id: <1511041417624247@web23g.yandex.ru>
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Wed, 03 Dec 2014 17:30:47 +0100
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 16:31:01 -0000

Hi

I got a small Intel Atom N280 box I wanted to use as a PF firewall.

It has one Intel NIC that gets registered as "bge0", then it has three
USB->NIC dongles with the ASIX AX88179 chipset which gets registered
as "ue0", "ue1" and "ue2".

I have set each device to a static IP during boot.

The problem is however that upon boot the devices gets switched.

So first boot:

| USB DONGLE 1 | UE0 | 192.168.1.1 |
| USB DONGLE 2 | UE1 | 192.168.2.1 |
| USB DONGLE 3 | UE2 | 192.168.3.1 |

Next boot:

| USB DONGLE 1 | UE1 | 192.168.2.1 |
| USB DONGLE 2 | UE2 | 192.168.3.1 |
| USB DONGLE 3 | UE0 | 192.168.1.1 |

Upon each boot the order changed, there is no fixed pattern.

This is a major problem as the device *still* has the right name and the
right IP, but it is as though it has been physically removed from the
slot and changed place.

Is it somehow possible to deal with this problem?

pciconf doesn't display those devices.

Kind regards

Martin