Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

AppleTV 4k - Ethernet IP Auto-Addressing Problem

I have had a new AppleTV 4k (64gb) for three days running tvOS 11. It has been running for two days just fine, hardwired to my gigabit ethernet. Streamed a bunch of shows and 4k movies. Most of the ATV settings are in the default mode, including the option to automatically select an IP address. Today, the ATV is forcing itself to IP address 169.254.226.187. My entire network is 192.xxx.x.xxx, the default for the router/gateway. I have tried rebooting the ATV, resetting the ATV, and rebooting/resetting my entire home network. Each time the systems come back up, the ATV immediately moves back over to 169.254.226.187. This only started happening today. And interesting side effect, when the ATV moves to the bad IP address, it knocks out my router/gateway, and my whole home internet goes down and requires a hard reboot to recover. I can get around the problem by switching the ATV to wireless only, but that slows down my internet speeds quite a bit, so I would like to know if anyone else has identified this bad IP addressing issue on ethernet connections, and if so is there a fix for it?

Apple TV 4K, tvOS 11

Posted on Oct 19, 2017 9:14 PM

Reply
Question marked as Best reply

Posted on Oct 20, 2017 1:54 PM

Hi. That 169.* address is a dummy value used by devices when they have not received a value from DHCP.

Have you made any changes to your router, such as MAC address filtering?

Is Apple TV connected directly to the router, with no intervening switches?

Could you check the router logs for any unusual activity from Apple TV prior to the failure you describe? In particular, do you see multiple DHCP requests, only a few minutes apart?

8 replies
Question marked as Best reply

Oct 20, 2017 1:54 PM in response to Astro_Not

Hi. That 169.* address is a dummy value used by devices when they have not received a value from DHCP.

Have you made any changes to your router, such as MAC address filtering?

Is Apple TV connected directly to the router, with no intervening switches?

Could you check the router logs for any unusual activity from Apple TV prior to the failure you describe? In particular, do you see multiple DHCP requests, only a few minutes apart?

Oct 20, 2017 1:57 PM in response to Diana.McCall

I did not make any changes to my home components. Yes, I did see multiple DHCP requests, here is what it looked like:


INF2017-10-16T08:17:55-05:00acsconnreq: all done, close connection...
INFP0000-00-00T00:04:23hurlhost=ps-928.pubnub.com uri=/time/0 hijacked
INFP0000-00-00T00:04:22hurlhost=www.apple.com uri=/xslt hijacked
INFP0000-00-00T00:04:21hurlerr=4 name=NO_DHCP_SERVICE clear
INFP0000-00-00T00:04:20hurlhost=www.apple.com uri=/xslt hijacked
INFP0000-00-00T00:04:20hurlerr=4 name=NO_DHCP_SERVICE redirect
INFP0000-00-00T00:04:20hurlhost=ps-914.pubnub.com uri=/time/0 hijacked
INFP0000-00-00T00:04:20hurlerr=4 name=NO_DHCP_SERVICE redirect
INFP0000-00-00T00:04:19hurlhost=ps-928.pubnub.com uri=/time/0 hijacked
INFP0000-00-00T00:04:19hurlerr=4 name=NO_DHCP_SERVICE redirect
INFP0000-00-00T00:04:19hurlhost=ps-451.pubnub.com uri=/time/0 hijacked
INFP0000-00-00T00:04:19hurlerr=4 name=NO_DHCP_SERVICE redirect
INFP0000-00-00T00:04:19hurlerr=4 name=NO_DHCP_SERVICE redirect
INFP0000-00-00T00:04:19hurlhost=ps-928.pubnub.com uri=/time/0 hijacked
INFP0000-00-00T00:04:19hurlerr=4 name=NO_DHCP_SERVICE redirect

Oct 20, 2017 3:33 PM in response to Diana.McCall

And I just turned on the ATV 4k again for the first time today, and I lost internet to the whole house within seconds after turning it on. I'm convinced the ATV 4k is knocking my home router offline each time I power on the ATV. Logs from the most recent time I turned on the ATV:


Event logs:

TypeDate/TimeEvent Description
INF2017-10-20T17:27:10-05:00Previous log entry repeated 1 times
INF2017-10-20T17:26:59-05:00sysNode 192.X is up
INF2017-10-20T17:26:32-05:00sysNode 192.X is up
INF2017-10-20T17:25:38-05:00hurlhost=ps-928.pubnub.com uri=/time/0 hijacked
INF2017-10-20T17:25:08-05:00hurlhost=ps-928.pubnub.com uri=/time/0 hijacked
INF2017-10-20T17:25:05-05:00acsbdc started.
INF2017-10-20T17:25:02-05:00sysNode 192.X is up
INF2017-10-20T17:24:57-05:00Previous log entry repeated 1 times
INF2017-10-20T17:24:57-05:00sysNode 192.X is up
INF2017-10-20T17:24:56-05:00sysNode 192.X is up


and system logs during the ATV power on:

TypeDate/TimeEvent Description
warnOct 20 17:31:52

daemon: httpd[1337]: dsl_get_bondstats failed: Invalid argument

errOct 20 17:31:52

daemon: httpd[1337]: dsld_gbondstats_1 failure: 22, Invalid argument

errOct 20 17:31:52

daemon: dsld[1326]: DSLD_CMD_GBONDSTATS: DSL device not up

errOct 20 17:31:52

daemon: dsld[1326]: bcmdsl_get_priv_info fail: device:/dev/dsl0

errOct 20 17:31:52

daemon: dsld[1326]: bcmdsl_get_mib() failed: rc: 9002, size: 30740, sizeof(adslMibInfo): 30740

errOct 20 17:31:52

daemon: dsld[1326]: bcmdsl_get_priv_info fail: device:/dev/dsl0

errOct 20 17:31:52

daemon: dsld[1326]: bcmdsl_get_mib() failed: rc: 9002, size: 30740, sizeof(adslMibInfo): 30740

warnOct 20 17:25:50

daemon: httpd[1337]: dsl_get_bondstats failed: Invalid argument

errOct 20 17:25:50

daemon: httpd[1337]: dsld_gbondstats_1 failure: 22, Invalid argument

errOct 20 17:25:50

daemon: dsld[1326]: DSLD_CMD_GBONDSTATS: DSL device not up

errOct 20 17:25:50

daemon: dsld[1326]: bcmdsl_get_priv_info fail: device:/dev/dsl0

errOct 20 17:25:50

daemon: dsld[1326]: bcmdsl_get_mib() failed: rc: 9002, size: 30740, sizeof(adslMibInfo): 30740

errOct 20 17:25:50

daemon: dsld[1326]: bcmdsl_get_priv_info fail: device:/dev/dsl0

errOct 20 17:25:50

daemon: dsld[1326]: bcmdsl_get_mib() failed: rc: 9002, size: 30740, sizeof(adslMibInfo): 30740

infoOct 20 17:25:22

daemon: httpd[1337]: DNS server name: attlocal.net

infoOct 20 17:25:22

daemon: httpd[1337]: bind(fd=16) family 10, port 443 to fe80::16ed:bbff:fe44:dab1 scope 17

infoOct 20 17:25:22

daemon: httpd[1337]: DNS server name: attlocal.net

infoOct 20 17:25:22

daemon: httpd[1337]: bind(fd=15) family 10, port 80 to fe80::16ed:bbff:fe44:dab1 scope 17

infoOct 20 17:25:19

daemon: rulemgrd[1380]: CMD_RET: 256

infoOct 20 17:25:19

daemon: rulemgrd[1380]: CMD_EXEC: "/bin/ip6tables -X telco_epilogue_A"

infoOct 20 17:25:19

daemon: rulemgrd[1380]: CMD_RET: 256

infoOct 20 17:25:19

daemon: rulemgrd[1380]: CMD_EXEC: "/bin/ip6tables -X user_interface_A"

infoOct 20 17:25:19

daemon: rulemgrd[1380]: CMD_RET: 256

infoOct 20 17:25:19

daemon: rulemgrd[1380]: CMD_EXEC: "/bin/ip6tables -X telco_prologue_A"

infoOct 20 17:25:16

daemon: httpd[1337]: DNS server name: attlocal.net

infoOct 20 17:25:16

daemon: httpd[1337]: bind(fd=14) family 10, port 443 to 2602:30a:c09a:8050::1 scope 17

infoOct 20 17:25:16

daemon: httpd[1337]: DNS server name: attlocal.net

infoOct 20 17:25:16

daemon: httpd[1337]: bind(fd=12) family 10, port 80 to 2602:30a:c09a:8050::1 scope 17

infoOct 20 17:25:08

daemon: ntpd[4386]: Listening on routing socket on fd #21 for interface updates

infoOct 20 17:25:08

daemon: ntpd[4386]: peers refreshed

infoOct 20 17:25:08

daemon: ntpd[4386]: Listen normally on 4 lo ::1 UDP 123

infoOct 20 17:25:08

daemon: ntpd[4386]: Listen normally on 3 br1 172.9.168.5 UDP 123

infoOct 20 17:25:08

daemon: ntpd[4386]: Listen normally on 2 lo 127.0.0.1 UDP 123

infoOct 20 17:25:08

daemon: ntpd[4386]: Listen and drop on 1 v6wildcard :: UDP 123

infoOct 20 17:25:08

daemon: ntpd[4386]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123

noticeOct 20 17:25:08

daemon: ntpd[4386]: proto: precision = 9.865 usec

noticeOct 20 17:25:07

daemon: ntpd[4386]: ntpd 4.2.6p5@1.2349 Thu Jan 21 22:39:53 UTC 2016 (1)

infoOct 20 17:25:06

daemon: cwmd[1306]: inited ca label 'root'

Oct 20, 2017 4:27 PM in response to Astro_Not

That's very detailed output. What make of router is that? And what software is it running?

I could not actually see any DHCP requests identifying Apple TV. They should show its MAC address. There seem to be a lot of errors reporting NO_DHCP_SERVICE.

The second set of logs don't seem to show anything related to Apple TV, or to any specific IP address.

Are you sure DHCP is enabled for ethernet connections?

Do you know what the DHCP lease duration is?

Oct 20, 2017 6:02 PM in response to Diana.McCall

It's an AT&T Uverse router, so a PACE 5268AC. It's running software version 10.5.3.527171-att. I have gigabit service. I was just data dumping the logs to you in case there was some nugget of info you could glean from them. I can pull up the MAC address, etc for the ATV if that helps. I spent a while on the phone with AT&T checking out the router and all connecting lines to the home to make sure it is working okay, and it all checked out good. This was the info that the router logs recorded when I powered up my ATV. The DHCP is working for every other device in my home, including my other two Apple TVs. The ATVs are Gen 3 and one is Gen 4. The DHCP lease is for 24 hrs. I believe the router starts showing the NO_DHCP_Service immediately after the ATV is powered on, and the whole home internet gets kicked offline. I can't recover the internet until I reboot the router. And the router keeps working fine until I turn on that ATV 4k. It worked fine for the first day, but now it just keeps crashing the router somehow. So the ATV is creating some kind of IP or other conflict that knocks my whole home internet unavailable.

Oct 20, 2017 9:05 PM in response to Astro_Not

I didn't want to know the Apple TV MAC address. I'm just surprised it didn't appear in the log for a DHCP request.


Are you sure the Apple TV network settings are Automatic for both IP address and DNS? Because what you describe is a typical symptom of trying to use a manual IP value which conflicts with something important. Like maybe the router itself.


Also, I asked about MAC address filtering, and you haven't mentioned whether you're using it.


You could try taking Apple TV to an Apple store for a checkout. If it works normally there, then at least you'd know the device is working correctly. Be sure to make an appointment.

AppleTV 4k - Ethernet IP Auto-Addressing Problem

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