TFTP Server IP Address

[jumpinjack]

I am a new user to SecureCRT and have not found the answer anywhere.
Where does SecureCRT 8.7.0 (Windows 7) TFTP server get its ip address from? Currently when I start it, it shows 169.254.144.154:69. I am currently using a laptop and would like it to connect to my lan port at a real ip address. Thank you

[bgagnon]

Hi jumpinjack,

It's supposed to be showing the IP of the computer on which SecureCRT is installed.

So how does the 169.* differ from the "lan port at a real ip address"?

[jumpinjack]

I am not sure where the 169 address came from, that is my issue

I would have thought it would have grabbed my lan at 10.94.185.2 or my wireless at 192.168.1.104...

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : attlocal.net

IPv4 Address. . . . . . . . . . . : 192.168.1.104
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

IPv4 Address. . . . . . . . . . . : 10.94.185.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.94.185.254


Thoughts?

[bgagnon]

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 support@vandyke.com 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:

https://support.microsoft.com/en-us/...or-ipv4-routes

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.

[jumpinjack]

Brenda

I cannot run the programs other than route print -4. The other items are not loaded on my Windows 7 machine. The route print -4 shows the following.

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.104 25
0.0.0.0 0.0.0.0 10.94.185.254 10.94.185.2 266
10.94.185.0 255.255.255.0 On-link 10.94.185.2 266
10.94.185.2 255.255.255.255 On-link 10.94.185.2 266
10.94.185.255 255.255.255.255 On-link 10.94.185.2 266
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.1.0 255.255.255.0 On-link 192.168.1.104 281
192.168.1.104 255.255.255.255 On-link 192.168.1.104 281
192.168.1.255 255.255.255.255 On-link 192.168.1.104 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.104 281
224.0.0.0 240.0.0.0 On-link 10.94.185.2 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.104 281
255.255.255.255 255.255.255.255 On-link 10.94.185.2 266
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 10.94.185.254 Default
===========================================================================

I do not have a device that is getting a windows supplied 169 address.

[bgagnon]

Hi jumpinjack,

I don't think it would be any different for the older OS.

SecureCRT makes a function call asking the system to return the IP addresses it has. This returns a list; SecureCRT picks the first one in the list that isn't 127.* as far as I know.

Perhaps one of these commands will show the interface the system provided to SecureCRT:

netsh interface ipv4 show addresses

or

netsh interface ipv4 show ipaddresses

[jumpinjack]

I am still not seeing a 169 address

netsh>interface ipv4 show addresses

Configuration for interface "ibaFOB-D Network"
DHCP enabled: No
InterfaceMetric: 25

Configuration for interface "Bluetooth Network Connection"
DHCP enabled: Yes
InterfaceMetric: 50

Configuration for interface "Wireless Network Connection"
DHCP enabled: Yes
IP Address: 192.168.1.104
Subnet Prefix: 192.168.1.0/24 (mask 255.255.255.0)
Default Gateway: 192.168.1.254
Gateway Metric: 0
InterfaceMetric: 40

Configuration for interface "Local Area Connection"
DHCP enabled: No
IP Address: 10.94.185.2
Subnet Prefix: 10.94.185.0/24 (mask 255.255.255.0)
Default Gateway: 10.94.185.254
Gateway Metric: 256
InterfaceMetric: 10

Configuration for interface "Loopback Pseudo-Interface 1"
DHCP enabled: No
IP Address: 127.0.0.1
Subnet Prefix: 127.0.0.0/8 (mask 255.0.0.0)
InterfaceMetric: 50


I did do more messing about yesterday. I turned off all interface but the one I want and was able to connect to it...The problem was when I turned another interface back on the address changed in the status bar of SecureCRT. It seems the software does not lock the interface in.

Thanks for the assistance on this.
Jack

[bgagnon]

Hi Jack,

I am trying to get you more info but this is what I have so far:

169.254.x.x: This is what's called an Automatic Private IP address. An IP in this range means that the computer cannot see the network. A computer using DHCP needs to have an external server tell it what IP address to use. Unfortunately, if there's no network connectivity, the computer is unable to talk to the server. In those cases, the computer will actually give itself an IP starting with 169.254, since it must assign itself some sort of number.

Update: Jack, the developers let me know the APIPA does not get listed by the commands.

[bgagnon]

Hi Jack,

To clarify, the TFTP server is still listening on all interfaces, it is just the display that is wrong.

[bgagnon]

Hi Jack,

There is a pre-release build available the developers believe resolves the issue where the wrong IP (for TFTP server) is shown in the status bar.

If you would like to try it, please send an email to support@vandyke.com that includes the email address associated with your download account and reference Forum Thread #14124 in the subject line.