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.Īs a workaround, you might consider changing the metric of the interface you desire to have displayed in SecureCRT's status bar.
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).
Get-NetIPAddress |Sort-Object -Property InterfaceIndex | format-table These commands run from within a PowerShell CLI will provide some details as to which interface has which metric: 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. SecureCRT asks the OS for a list of IP addresses, and chooses the first one returned in the list. If you prefer direct e-mail notification, contact and include "Feature Request - Forum Thread #14124" in the subject line. I've added this thread to the feature request mentioned below. 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).
0 kommentar(er)
