Announcement

Collapse
No announcement yet.

BurnInTest order of network interfaces

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • BurnInTest order of network interfaces

    On BurnInTest 7.0, I am testing a machine that has 4 network interfaces on different subnets. In BurnInTest, I set up the Network test to ping a different address for each network interface. On some units of the same model PC, the first two network interfaces switch order according to BurnInTest. If the order switches, the pings fail because the ping is trying to reach an address on the wrong subnet.

    My question: how does BurnInTest decide on the order of the network interfaces, and why would the network interface change order on different units of the same model PC?
    NIC IP Ping Destination in BIT
    1 192.168.8.* (DHCP) 192.168.42.33
    2 192.168.1.106 192.168.1.100
    3 192.168.1.102 192.168.1.100
    4 192.168.1.103 192.168.1.100

    OS: Windows 10, 64-bit
    BurnInTest version: 7.0 Pro, 32-bit

  • #2
    The order that BurnInTest sees adapters is controlled by Windows and the order they are returned by a call to the GetAdaptersAddresses API function. This function states;

    In versions prior to Windows 10, the order in which adapters appear in the list returned by this function can be controlled from the Network Connections folder: select the Advanced Settings menu item from the Advanced menu. Starting with Windows 10, the order in which adapters appear in the list is determined by the IPv4 or IPv6 route metric. This metric is determined by a number of different factors.

    Comment

    Working...
    X