Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Mac shows a 169.254 address: there is no usable DHCP lease

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

The Mac's IPv4 address starts with 169.254. Office servers, printers, and the internet do not work. That address is not an office DHCP lease. RFC 3927 defines it as an IPv4 link-local address, used when ordinary configuration is missing. Ask for DHCP again. If the prefix returns, no lease reached the Mac. The fault may then be on the network side, for example the DHCP service, the VLAN for that network, or a scope with no free addresses, and further changes on the Mac will not invent a lease.

People call this a self-assigned IP. Apple's pages "Use DHCP or a manual IP address on Mac" and "Renew your IP address from the DHCP server on Mac" do not use that phrase: they say how to choose Using DHCP and how to renew a lease. The meaning of the prefix is in RFC 3927.

What the prefix means

A host needs an address "either manually by the user or automatically from a source on the network such as a Dynamic Host Configuration Protocol (DHCP) server." When that is missing, it may "automatically configure an interface with an IPv4 address within the 169.254/16 prefix that is valid for communication with other devices connected to the same physical (or logical) link."

"IPv4 Link-Local addresses are not suitable for communication with devices not directly connected to the same physical (or logical) link, and are only used where stable, routable addresses are not available" (the sentence goes on: "such as on ad hoc or isolated networks"). Section 2.1 selects from "169.254.1.0 to 169.254.254.255 inclusive." The rest of the prefix "MUST NOT be selected."

Section 2.7: a packet whose source or destination is in 169.254/16 "MUST NOT be sent to any router for forwarding," and a device that receives it "MUST NOT forward it." The Mac can talk only to other link-local hosts on that link.

Section 1.6: addresses in 169.254/16 "SHOULD NOT be configured manually or by a DHCP server." Do not type one in, and do not put the prefix in a DHCP pool.

Apple's step, when the address should be automatic, is "choose Using DHCP." Renewing applies when you already use DHCP. A restart "automatically renews the internet address it was assigned when joining the Wi-Fi network."

Likely causes

Cause What you see How to confirm
No DHCP offer The address stays in 169.254.1.0–169.254.254.255 after a renew The prefix returns
Configure IPv4 is not Using DHCP Manually, with an address the server does not know The TCP/IP pop-up
A 169.254 address was typed in It survives a renew Section 1.6 says not to configure it manually

Prove the cause before changing anything

1. Write down TCP/IP. System Settings, Network, the service, Details, TCP/IP. Record Configure IPv4, the address, the mask, and the router if it is filled in. Record DNS servers too in a note.

2. Check the prefix. 169.254.1.0 through 169.254.254.255 matches section 2.1. Any other 169.254 address is in the reserved range a host must not select. An address outside 169.254/16 is not this fault.

3. See whether renew applies. Apple's renew page is for an address you receive using DHCP. If Configure IPv4 is Manually, renew is the wrong first step.

Fix

If Configure IPv4 says Manually

List the service names first. This command only prints a list. Use the exact name of your connection, in quotes, in the commands below.

networksetup -listallnetworkservices

To save the current settings first, run the two commands below. SS64's networksetup reference says -getinfo displays "the IP address, subnet mask, router, and hardware address" and -getdnsservers displays "DNS info" for the service.

networksetup -getinfo "<service name>" > mac-tcpip-before.txt
networksetup -getdnsservers "<service name>" >> mac-tcpip-before.txt

Risk: the next step switches Configure IPv4 from Manually to Using DHCP and drops the address you typed. If the server still does not answer, the Mac returns to 169.254 and the manual address is gone until you type it back from mac-tcpip-before.txt.

Set Configure IPv4 to Using DHCP: Apple menu, System Settings, Network, the connection, Details, TCP/IP, Using DHCP. From Terminal, -setdhcp "Sets the TCP/IP configuration for the specified network service to use DHCP."

networksetup -setdhcp "<service name>"

To undo it: restore a manual configuration only from mac-tcpip-before.txt, and never with a 169.254 address. If the saved manual value was a 169.254 address, do not restore it; leave the Mac on DHCP. Otherwise use the saved address, mask and router, then set the DNS servers the file lists. If the file shows none, SS64's reference says to clear them by typing "empty" in place of the DNS server names:

networksetup -setmanual "<service name>" <saved address> <saved mask> <saved router>
networksetup -setdnsservers "<service name>" <saved DNS servers, or empty>

Or choose Manually in System Settings and enter those fields. Apple's DHCP page says to enter the mask and router when an administrator gave them.

If Configure IPv4 already says Using DHCP

Apple's renew page says: "Check with your ISP or network administrator to find out whether you need to renew your DHCP address." To show the exact lease you are about to replace, run the command below and keep the output.

networksetup -getinfo "<service name>" > mac-lease-before.txt

Disruptive step: the next step renews the DHCP lease for that connection, and the Mac may receive a different address from the one it has now. Apple's Wi-Fi help says: "If the lease expired and the address is already in use by another device, your Mac is assigned a new address."

Use Renew DHCP Lease on the TCP/IP screen, then OK.

To undo it: a renewed lease cannot be put back, and nothing needs restoring, because the service was already Using DHCP. mac-lease-before.txt only records the address you had, which in this fault is the 169.254 address and is never to be restored.

When the prefix comes back

Stop changing the laptop. A second renew that returns 169.254 means no lease reached the Mac. The fault may be on the network side, for example the DHCP service, the VLAN for that SSID, or a scope with no free addresses, and none of these is repaired on the Mac.

Example (illustrative): 169.254.86.12, Configure IPv4 already Using DHCP. Renew DHCP Lease runs and the address becomes 192.0.2.40. A second laptop stays on 169.254 after two renews. That one is evidence about the server or the VLAN.

Confirm the fix

  1. The address is outside 169.254/16.
  2. Configure IPv4 is Using DHCP, unless an administrator issued a manual office address and you entered it from their note.
  3. A host that is not on the local link opens. Link-local never could.
  4. You did not leave a handmade 169.254 address in place.

What to watch afterwards

  • Check that no 169.254 address was ever typed into the office DNS zone: RFC 3927 says "IPv4 Link-Local addresses MUST NOT be stored in the DNS."
  • If several laptops fail together, compare their TCP/IP screens before changing any one Mac.

Risks and limits

  • None of the four Apple pages listed under Sources uses the words Self-Assigned IP. The prefix test is the RFC range.
  • Renewing cannot restore the previous address. Apple says that if the lease expired and the address is in use by another device, the Mac is assigned a new one.
  • A full scope is not fixed on the Mac.

Sources