Apipa Address vs the PC name

[BlackManINC]

 So I have another question for you ultra nerds out there. I was fooling around in my Oracle VM. I turned off the pfsense router, and disabled the ethernet in my Windows 10 VM. I pinged the Apipa address, and didn't get a response, as I expected. But when I ping the name of the PC itself, I get a response via the loopback address. I was not expecting that at all. Why is the loopback address responding? How would that help me troubleshoot a connection issue in this instance? With Ethernet on, pfsense still turned off, the Apipa address showed up when pinging the PC name before.

 

[Eigenvektor]

It's not quite clear from the post what the actual issue is you're trying to solve here. Since the machine has an 169.254.x.x address it means it hasn't gotten an IP from a DHCP and has assigned itself an IP.

 

When you ping a host name, that name is first resolved to an IP address, typically using a DNS server. Since the machine has no proper network connection it probably recognized its own name, and resolved it to 127.0.0.1/localhost.

[BlackManINC]

7 hours ago, Eigenvektor said:

It's not quite clear from the post what the actual issue is you're trying to solve here. Since the machine has an 169.254.x.x address it means it hasn't gotten an IP from a DHCP and has assigned itself an IP.

 

When you ping a host name, that name is first resolved to an IP address, typically using a DNS server. Since the machine has no proper network connection it probably recognized its own name, and resolved it to 127.0.0.1/localhost.

Right, I mean I know the loopback just pings the machines TCP/IP stack software according to various nerds. Has nothing to do with the hardware. So, not even getting an apipa address just indicates that there is a hardware issue. The wifi adapter and/or NIC has either been disabled, or they gave up the ghost. I still wasn't expecting the loopback to respond, but I guess I should have. Got it.