AWS uses as a link local address, which you can use to pull meta data about the instance, ie:


How/where is this IP configured on the instance? I can see a route for it if I do an "ip route". And if I "netcat -Cvz 80", I can get a connection. However, I don't actually see the instance listening anywhere if I do a "netstat -ntlp". If I attempt to connect to another port, "netcat -Cvz 22", it fails. In fact, I have what would seem to be a conflicting Apache service running on So it seems like this address is referring to an outside host. Would it be pointing to the hypervisor?

  • 6
    It's not configured on the instance. The instance isn't providing that data at all, so of course nothing on the instance is listening for requests to it. "Link-local" doesn't mean localhost. It means they're in the same network segment. en.wikipedia.org/wiki/Link-local_address – ceejayoz Jun 8 '16 at 0:49

Most linux distributions will already create a Zeroconf route, which is probably why Amazon figured they would "borrow" that particular IP address. For example, if you install CentOS 7 then "out of the box" your primary Ethernet will get a route added:


# Add Zeroconf route.
if [ -z "${NOZEROCONF}" -a "${ISALIAS}" = "no" -a "${REALDEVICE}" != "lo" ]; then
    ip route add dev ${REALDEVICE} metric $((1000 + $(cat /sys/class/net/${REALDEVICE}/ifindex))) scope link

No doubt similar stuff exists in debian, ubuntu, etc...

You may wonder how it works when none of your local interface addresses are even in the correct subnet, but actually Linux doesn't care too much about that. Some servers generate a local Zeroconf address just using random numbers as per RFC3927, in which case they will use the generated address. Either way shouldn't make much difference, provided the thing at is happy to answer.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.