View Single Post
Old 03-25-2020, 10:32 AM
bgagnon bgagnon is offline
VanDyke Technical Support
Join Date: Oct 2008
Posts: 4,322
Hi jumpinjack,

Thanks, I just wanted to verify it was not a valid IP address (and thanks to a colleague now I know that 169.254 is Microsoft's Automatic Private IP address -- APIPA).

I've added this thread to the feature request mentioned below. If you prefer direct e-mail notification, contact and include "Feature Request - Forum Thread #14124" in the subject line.

Here's info on why it happens:

SecureCRT asks the OS for a list of IP addresses, and chooses the first one returned in the list.

Typically the list is ordered by "metric", so an individual may modify their networking configuration to make sure the interface they desire to be shown has the lowest metric.

These commands run from within a PowerShell CLI will provide some details as to which interface has which metric:

route print -4
Get-NetIPInterface -AddressFamily IPv4
Get-NetIPAddress |Sort-Object -Property InterfaceIndex | format-table

This information will likely reveal that the address SecureCRT is displaying in the status bar is the interface that has either the lowest metric or the lowest ifIndex value (in the case of the Get-Net* cmd output).

I've added a feature request on your behalf for the ability to tell SecureCRT to ignore loopback interfaces or otherwise make a heuristically better choice as to which IP address to display instead of trusting the first one reported by the OS.

As a workaround, you might consider changing the metric of the interface you desire to have displayed in SecureCRT's status bar.

This MS article describes how metrics are calculated automatically by default, and at the end tells how to change the metric for a network interface:
Note that the lower the metric, the higher Windows gives to that interface in terms of priority for performing networking related activity. So, if you had both a Wi-Fi connection and an Ethernet LAN connection active on the same machine, the Ethernet LAN connection will typically have a lower automatic metric (25, for example) than would the Wi-Fi interface (35, for example). This stands to reason, since LAN connections are typically faster than Wi-Fi connections, so the LAN should be the "chosen" interface. Loopback adapters (127.*, 169.254.*, for example) typically have a pretty low metric because they're loopback (nothing ever goes on the physical wire (or radio wave in the case of wireless)). The article above tries to explain Windows' reasoning for automatically-applied metrics to interfaces based on their detected capability.

VanDyke Software
Technical Support
(505) 332-5730

Last edited by jdev; 03-25-2020 at 11:00 AM.
Reply With Quote