Self-Assigned IP

a few minor edits:

It means that for some reason, your mac could not find a dchp server to get an ip address. not sure when the mac may need to get a new ip address after it already has an an ip address. The mac needs to renew it's ip address ever so often. The only thing I can think of is the renew ip address failed. The mac "helpfully" dreams up it's own ip address. You may be able to set the renew time from you router.

I don't now why this is happening. have you tried powering, off waiting, then powering on your router? What type of router do you have ... make and model?

could you try login onto your router? The address is often the network address of your router ... like 192.168.0.1 or 192.168.0.0

Instead of re-booting, as a work-a-round you might try

A) renew your DHCP address.

1. Choose Apple menu > System Preferences, then click Network.
2. In the list at the left, select the network service that needs a renewed IP address.
3. Click Advanced, click TCP/IP, then click Renew DHCP Lease.

macOS Sierra: Renew an IP address from the DHCP server

mac $ networksetup -listallhardwareports

Hardware Port: Bluetooth DUN
Device: Bluetooth-Modem
Ethernet Address: N/A

Hardware Port: FT232R USB UART
Device: usbserial-A700fcUV
Ethernet Address: N/A

Hardware Port: Ethernet
Device: en0
Ethernet Address: 98:5a:eb:cf:65:eb

Hardware Port: Wi-Fi
Device: en1
Ethernet Address: 78:9f:70:7a:fe:12

Hardware Port: Bluetooth PAN
Device: en4
Ethernet Address: 78:9f:70:7a:fe:13

Hardware Port: Thunderbolt 1
Device: en2
Ethernet Address: 2a:00:00:bf:26:70

Hardware Port: Thunderbolt 2
Device: en3
Ethernet Address: 2a:00:00:bf:26:71

Hardware Port: Thunderbolt Bridge
Device: bridge0
Ethernet Address: N/A

VLAN Configurations
===================
mac $

http://dr-palaniraja.blogspot.com/2013/04/disable-networkinginternet-from-comman d.html

You could self assign an ip address. just take a guess. 192.168.0.200 at least it should not need to be renewed i don't think.

R

Make sure you are getting the IP address by DHCP. Make sure no other device on your network has a manually assigned IP address that is within the scope of the DHCP assigned IP address range. Power cycle your router.

It means that for some reason, you mac could not find a dchp server to get an ip address. not sure when the mac may need to get a new ip address. maybe the renew ip address failed. The mac "helpfully" dreams up it's own ip address.

I don't now why this is happening. have you tried powering, off waiting, then powering on your router? What type of router do you have ... make and model?

could you try login onto your router? The address is often the network address of your router ... like 192.168.0.1 or 192.168.0.0

as a work-a-round you might try

renew your DHCP address.

mac $ networksetup -listallhardwareports

Hardware Port: Bluetooth DUN
Device: Bluetooth-Modem
Ethernet Address: N/A

Hardware Port: FT232R USB UART
Device: usbserial-A700fcUV
Ethernet Address: N/A

Hardware Port: Ethernet
Device: en0
Ethernet Address: 98:5a:eb:cf:65:eb

Hardware Port: Wi-Fi
Device: en1
Ethernet Address: 78:9f:70:7a:fe:12

Hardware Port: Bluetooth PAN
Device: en4
Ethernet Address: 78:9f:70:7a:fe:13

Hardware Port: Thunderbolt 1
Device: en2
Ethernet Address: 2a:00:00:bf:26:70

Hardware Port: Thunderbolt 2
Device: en3
Ethernet Address: 2a:00:00:bf:26:71

Hardware Port: Thunderbolt Bridge
Device: bridge0
Ethernet Address: N/A

VLAN Configurations
===================
mac $

http://dr-palaniraja.blogspot.com/2013/04/disable-networkinginternet-from-comman d.html

You could self assign an ip address. just take a guess. 192.168.0.200 at least it should not need to be renewed i don't thing.

R

In your router you reserve a range of IP addresses to be used for DHCP assignments. If you use one of these IP addresses manually on another device DHCP does not know about the manually used address so could assign that same address to another device. This would cause the device to use a self assigned ip address since the same address is trying to be used twice.

How many IP addresses are in the DHCP scope? If you have 2 addresses in the scope and 2 devices connect there is no problem. If a third device tries to connect using DHCP then there is a problem and a self assigned IP address will be used.

I'm experiencing the exact same problem you're describing. It began about 3 days ago when I upgraded to 10.13.5.

I have a MacBook I purchased new 5 months ago. I'm traveling on business and have been living in an apartment with only wired ethernet for the past 4 months. About 3 months ago I purchased a new DrayTek Vigor 902 AP wireless access point for my apartment. This AP provides both wired and wireless connectivity. I installed it so I could use my smart phone in my apartment because the cell coverage indoors is terrible. The MacBook is always connected to the wired ethernet. Once a week when I have maid service in the apartment I shut down the MacBook otherwise it's always on and usually streaming music when I'm home from work. I have a different laptop I use at work.

I've had absolutely no network connectivity issues prior to upgrading to 10.13.5. My network couldn't be simpler, 2 devices, a phone and a laptop, one on wireless the other on wired ethernet. Just as you describe, after several hours, or after waking from sleep, the Internet connection stops working. The MacBook shows the physical ethernet connection as up but the IP address is self-assigned and not correct. The only thing that fixes it every time is restarting the MacBook. Rebooting the AP or attempting to renew the DHCP lease on the MacBook does not resolve the issue.

Clearly Apple broke something in the network stack with 10.13.5. I was thinking about upgrading to 10.13.6 but you are seeing the same issue with 10.13.6 so I don't think upgrading will help me. I may try switching the MacBook to wireless and see if the issue goes away. Have you tried wireless?

John Wills wrote:

<snip>

Clearly Apple broke something in the network stack with 10.13.5. I was thinking about upgrading to 10.13.6 but you are seeing the same issue with 10.13.6 so I don't think upgrading will help me. I may try switching the MacBook to wireless and see if the issue goes away. Have you tried wireless?

No. Millions of users are using High Sierra without network issues. You have a configuration or other local issue. Start your own thread detailing your network and system connections. You will get dedicated focused help for your issue in your own thread.

Nothing in my environment or configuration has changed in the last 3 months except for an update from 10.13.4 to 10.13.5. Generally the best way to root cause an issue is to control the variables and change only one thing at a time. This is exactly what I have done. As soon I performed the update the issue appeared.

When I searched the forum I found another user who hit an issue with the very same symptoms I encountered. A different problem with the same symptoms? Or the same issue I'm hitting? I don't know, but it sounds suspiciously the same.

Do you have any helpful advice besides suggesting I make the same post in another thread? You didn't have any problem finding my post so it's not clear to me why I should re-post.

It's the custom of this place to start your own thread. Problems that may appear the same may not be. You should state your issue. Describe what you have done to solve the issue. Don't make a conclusions. Don't argue with us helpers. Reference this thread if you wish.

How to create a new Discussion

R

PS. Play by the rules and you increase your success.

You can click on the triangle below the title when you create a new thread.

How to write a good question

To help other members answer your question, give as many details as you can.

• Include your product name and specs such as processor speed, memory, and storage capacity. Please do not include your Serial Number, IMEI, MEID, or other personal information.
• Provide the version numbers of your operating system and relevant applications, for example "iOS 6.0.3" or "iPhoto 9.1.2".
• Describe the problem, and include any details about what seems to cause it.
• List any troubleshooting steps you've already tried, or temporary fixes you've discovered.

"Be polite, constructive and stay on topic." Could be interpreted as don't hijack a thread.

Community etiquette

Apple Support Communities Use Agreement

Can you point me to a list of the rules and/or customs?

Thanks,

John