MacBook Air Self Assigned IP Address

I have a Macbook Air, purchased October 2023. It has never had any issue connecting to my home wifi network (or any other wifi network). Software is up to date.


A couple of weeks ago, it performed a system update (I have auto update enabled). It would not reconnect to my home wifi, let's call it WiFi-A. I have a secondary network, WiFi-B connected to WiFi-A for coverage reasons. The Macbook connects to WiFi-B with no problem, but it's slower because of the router connected to another router thing.


[Re-Titled by Moderator]

WiFi-A has 50 other devices connected to it without issue. The Macbook Air is saying "self assigned IP address" and has a non-routable IP address. When I look at the router for WiFI-A, I can see my Macbook Air with an assigned IP address of 192.168.1.37. I tried forcing this in the WiFi settings on the Macbook Air by assigning that address manually but it doesn't work.


This issue is unique to this Macbook Air, and happened after a recent update. I want to connect to WiFi-A because it's much faster (and it bugs me that it refuses to connect while 50 other devices have no issue).


Yes, I've restarted the router (several times). I deleted the Macbook Air from the router's device list. I've told the Macbook to forget the WiFi-A network. Nothing works. The router continues to assign the same IP address to the Macbook, and the Macbook continues to have the "self-assigned", non-routable address of 169.xxx.xxx.xxx.


Ideas?



MacBook Air 15″, macOS 14.6

Posted on Sep 15, 2024 3:36 PM

Reply
Question marked as Top-ranking reply

Posted on Sep 15, 2024 7:22 PM

Try creating a new network location and see if the problem persists. System Settings > Network, click the ... button at the bottom right of the preference pane, then Locations > Edit Locations and click the + button.

Similar questions

12 replies

Sep 17, 2024 6:17 PM in response to turbojimmy68

Have you verified the Mac on a third Wi-Fi network?


That’ll then tend to point to the NETGEAR Orbi, or to the Mac connection into the Orbi, or thr Mac more generally.


What is being reported here so far looks like it’s either an issue with the Mac connecting onto one network — VPN add-on apps or anti-malware add-on apps can sometimes get tangled here, if any of those are present — or it’s potentially an issue with the Orbi network, or interference between the networks.


Check for firmware updates for the Orbi too, and apply the latest available for your particular hardware, and test again if there’s an update:


Longer-term, I’d look to consolidate onto one network with multiple access points with wired backhaul, or onto a common mixed or mesh network.


PS: I’d stay out of 192.168.0.0/24 and 192.168.1.0/24, as those tend to get VPNs tangled, as ~everybody uses those subnets.

Sep 19, 2024 8:15 AM in response to turbojimmy68

If you have a Mac or PC (or if NETGEAR Orbi supports it, (scan the Wi-Fi bands for activity, and also check RSSI and noise for your common client locations.


When configuring mid- or higher-end SOHO Wi-Fi networks, I usually use Ubiquiti mesh-capable Wi-Fi 6 or now 6E gear (which has scanning, mapping, and display capabilities) and WiFi Explorer app on macOS for that, and there are other scanning apps for Mac and PC.


I’ve seen all sorts of local stuff using Wi-Fi, including various appliances, vehicles, neighbors, and Mac Jim ID is exceedingly verily and absolutely correct about congestion causing all sorts of Wi-Fi sadness.


Three separate (and apparently uncoordinated?) Wi-Fi 2.4 GHz networks in close proximity is less that a good idea with 2.4 Ghz gear, as you’ve just used all of the available channels in US-region 2.4 GHz for those networks, and if you also use mesh in 2.4 GHz, that will require yet more (now-conflicting) channels.


A network that is coordinated and is offering multiple SSIDs can use those multiple SSIDs without quite as many 2.4 Ghz channels. Mesh in any band is still going to need channels for backhaul, so either get into 5 GHz or 6 GHz, or get wired backhaul


Check the specs for that particular Orbi gear (can it be encouraged to use 5 Ghz, or 6 Ghz if its new enough?), and also see if the NETGEAR forums have any issues or configuration recommendations.

Sep 19, 2024 7:25 AM in response to turbojimmy68

Is your Orbi operating on the 2.4Ghz band for Wifi? This may be the case since it is an older Orbi and using it with other devices that may operate only on the 2.4Ghz band. This band is very congested and quickly runs out of channels to connect to without interference. With a dual band router, you should be able to force it to use the 5Ghz band, but not sure if that would then be compatible with your other devices. Possibly need to create a seperate SSID for 5Ghz only if your router allows you to do that.


On my router, I have 2 SSID's, one with 2.4Ghz for security cams, printer and older devices, then another SSID on 5Ghz only for TV, computer, and phone WiFi. I was experiencing dropped WiFi connections using just a single SSID on the dual band router.

Sep 17, 2024 4:48 PM in response to MrHoffman

169.254.x.x usually means a network configuration error.


Please describe your Wi-Fi network configuration in a little more detail.


The primary network is an Orbi base and satellite. Many years old, works flawlessly. My Macbook had no issues with it until a few weeks ago. Subnet is 192.168.xxx.xxx.


Same SSID on disparate networks?


No, different SSID on disparate networks.


Same subnet on disparate networks?


No, the network that the Macbook successfully connects to is a 10.x address space.


How many DHCP servers do you have?


2 - one for each network.


Please describe what was meant by “router thing”.


The network with the 10.x address space is connected to the main Orbi network with the 192.168.x space. I've found that this slows things down, but I needed to add the 10.x network to expand coverage.


Bottom line is that this has been working perfectly for years. I've had the Macbook for about a year during which time it also worked fine. Whatever update happened a few weeks ago won't allow it to reliably use the Orbi network. It will work occasionally - like when I added the new location - but drops off again.

Sep 19, 2024 7:00 AM in response to MrHoffman

Thanks for the reply.


I have a third SSID connected to the Orbi - it's a TP-Link outdoor access point for security cameras hardwired to an Orbi satellite. The Mac can connect to that fine (it has the 192.168.1.xxx range which doesn't seem to be an issue with anything else on the network, though I should probably change it).


The Mac will also connect to my Starlink WiFi without a problem (which is completely separate from everything else).


The Orbi firmware is up to date.


All this kind of points to the Orbi itself, but everything else is fine. And the Orbi is issuing an IP address to the Mac, but the Mac isn't using it. Kind of weird.

Sep 24, 2024 7:09 AM in response to Mac Jim ID

The Orbi is dual-band. Unfortunately I need the 2.4 Ghz for other devices, and you can't give different names to the 2.4 and 5 Ghz bands on the Orbi. Actually that's one of the reasons I have a second router on the network - it's also dual band with separate SSIDs for 2.4 and 5 Ghz. I had a remote garage door opener that would only operate on 2.4 Ghz and also refused to connect to the Orbi. At this point I don't even know if I need the second router any longer. It's one of those things that just keeps chugging away and is out of sight, out of mind. I'm glad I kept it around, though, because my Macbook won't connect to the Orbi any longer either.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

MacBook Air Self Assigned IP Address

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.