HDHR-prime can't get IP after firmware update

Reception, channel detection, network issues, CableCARD setup, etc.
Post Reply
averyfreeman
Posts: 254
Joined: Sun Apr 09, 2017 11:12 am
Device ID: 1326E235 1313788A
Location: Olympia, WA
Contact:

HDHR-prime can't get IP after firmware update

Post by averyfreeman »

Hey,

I've had two HDHRPs on my network for the past ... I dunno, 5 years? They've both been working fine basically the entire time. In fact, when I went to go troubleshoot the one that's not responding, the whole area I noticed is coated in a thick matte of dust due to lack of intervention necessity for so long (I will have to take care of that once I get it working).

But I digress. The HDHRP in question was complaining about a firmware update at my.hdhomerun.com, so I hit the unassuming-looking "download firmware and reboot" button (or something to that effect). It went down for a bit, but then I noticed it never came back up on the my.hdhomerun.com local site.

I went and hard-reset the HDHRP which I believe is 1313788A. Blinking left led after it booted back up. Removed ethernet, re-plugged in, blinking left light.

I am about to do a wireshark capture when I get back from an errand to see if that doesn't help diagnose the issue, but I thought I'd write a quick, rambling post to let others know in case someone can chime in with some recommendations.

BTW, nothing on my network is disabling LAN mdns, but I never set UPnP on my firewall since I'm not a huge fan of opening ports to the outside inexplicitly. It's never been an issue w/ the primes before.

Re: latest firmware, buyer beware (for now).

NedS
Silicondust
Posts: 1702
Joined: Mon Dec 10, 2018 12:38 pm
x 76

Re: HDHR-prime can't get IP after firmware update

Post by NedS »

It might be the power supply. Try swapping them.

averyfreeman
Posts: 254
Joined: Sun Apr 09, 2017 11:12 am
Device ID: 1326E235 1313788A
Location: Olympia, WA
Contact:

Re: HDHR-prime can't get IP after firmware update

Post by averyfreeman »

Thanks for getting back to me. The weirdest thing happened, last night the prime just started working again. I was looking at the log, and there's no particular reason why I can discern, but I was fine-tuning my IPV6 config on the domain controllers (the HDHRPs don't pay attention to IPV6, though, do they?)

I'm assuming these use UTC, so around 5pm PST?

Could a dying power supply be related to this behavior?

Log:

Code: Select all

19700101-00:00:00 System: reset reason = power on
19700101-00:00:01 CableCARD: M-CARD inserted
19700101-00:00:03 System: network link 1000f
19700101-00:00:05 CableCARD: Arris/Motorola card (0000:0717)
19700101-00:00:05 CableCARD: authentication status: authentication in progress
19700101-00:00:05 CableCARD: authentication status: authentication success, validation success
19700101-00:00:28 System: network link down
19700101-00:00:34 System: network link 1000f
20201023-17:19:02 CableCARD: time changed from Thu Jan 01 00:01:01 1970 to Fri Oct 23 17:19:02 2020
20201023-17:19:19 System: myhdhomerun_sync: webclient error (dns failed)
20201023-17:29:52 System: myhdhomerun_sync: webclient error (dns failed)
20201023-17:40:25 System: myhdhomerun_sync: webclient error (dns failed)
20201023-17:49:34 System: myhdhomerun_sync: webclient error (dns failed)
20201023-17:59:56 System: myhdhomerun_sync: webclient error (dns failed)
20201023-18:08:57 System: myhdhomerun_sync: webclient error (dns failed)
20201023-18:19:25 System: myhdhomerun_sync: webclient error (dns failed)
20201023-18:29:20 System: myhdhomerun_sync: webclient error (dns failed)
20201023-18:40:17 System: myhdhomerun_sync: webclient error (dns failed)
20201023-18:49:34 System: myhdhomerun_sync: webclient error (dns failed)
20201023-18:58:42 System: myhdhomerun_sync: webclient error (dns failed)
20201023-19:07:49 System: myhdhomerun_sync: webclient error (dns failed)
20201023-19:17:51 System: myhdhomerun_sync: webclient error (dns failed)
20201023-19:27:47 System: myhdhomerun_sync: webclient error (dns failed)
20201023-19:37:44 System: myhdhomerun_sync: webclient error (dns failed)
20201023-19:48:06 System: myhdhomerun_sync: webclient error (dns failed)
20201023-19:58:27 System: myhdhomerun_sync: webclient error (dns failed)
20201023-20:08:57 System: myhdhomerun_sync: webclient error (dns failed)
20201023-20:19:38 System: myhdhomerun_sync: webclient error (dns failed)
20201023-20:29:21 System: myhdhomerun_sync: webclient error (dns failed)
20201023-20:40:03 System: myhdhomerun_sync: webclient error (dns failed)
20201023-20:50:46 System: myhdhomerun_sync: webclient error (dns failed)
20201023-21:01:28 System: myhdhomerun_sync: webclient error (dns failed)
20201023-21:11:42 System: myhdhomerun_sync: webclient error (dns failed)
20201023-21:18:24 System: myhdhomerun_sync: webclient error (dns failed)
20201023-21:28:33 System: myhdhomerun_sync: webclient error (dns failed)
20201023-21:38:55 System: myhdhomerun_sync: webclient error (dns failed)
20201023-21:49:50 System: myhdhomerun_sync: webclient error (dns failed)
20201023-21:59:02 System: myhdhomerun_sync: webclient error (dns failed)
20201023-22:08:27 System: myhdhomerun_sync: webclient error (dns failed)
20201023-22:18:18 System: myhdhomerun_sync: webclient error (dns failed)
20201023-22:28:34 System: myhdhomerun_sync: webclient error (dns failed)
20201023-22:39:32 System: myhdhomerun_sync: webclient error (dns failed)
20201023-22:50:00 System: myhdhomerun_sync: webclient error (dns failed)
20201023-23:00:05 System: myhdhomerun_sync: webclient error (dns failed)
20201023-23:09:13 System: myhdhomerun_sync: webclient error (dns failed)
20201023-23:19:08 System: myhdhomerun_sync: webclient error (dns failed)
20201023-23:30:00 System: myhdhomerun_sync: webclient error (dns failed)
20201023-23:39:05 System: myhdhomerun_sync: webclient error (dns failed)
20201023-23:49:53 System: myhdhomerun_sync: webclient error (dns failed)
20201023-23:59:29 System: myhdhomerun_sync: webclient error (dns failed)
20201024-00:08:34 System: myhdhomerun_sync: webclient error (dns failed)
20201024-00:11:35 System: ip address obtained: 192.168.1.127 / 255.255.255.0
20201024-00:59:31 Tuner: tuner0 tuning 109 KCTSDT (auto:117MHz-11096)
20201024-00:59:31 Tuner: tuner0 streaming http to 192.168.1.32:34902
20201024-00:59:31 CableCARD: tuner0 109 KCTSDT (auto:117MHz-11096) access = subscribed
20201024-01:59:32 Tuner: tuner1 tuning 336 KCTSDT3 (auto:159MHz-3)
20201024-01:59:32 Tuner: tuner1 streaming http to 192.168.1.32:34912
20201024-01:59:32 CableCARD: tuner1 336 KCTSDT3 (auto:159MHz-3) access = subscribed
20201024-02:30:29 Tuner: tuner0 http stream ended (remote closed)
20201024-03:00:31 Tuner: tuner1 http stream ended (remote closed)
20201024-07:59:29 Tuner: tuner0 tuning 657 CNNHD (auto:345MHz-2)
20201024-07:59:30 Tuner: tuner0 streaming http to 192.168.1.32:34994
20201024-07:59:30 CableCARD: tuner0 657 CNNHD (auto:345MHz-2) access = subscribed
20201024-09:59:30 Tuner: tuner1 tuning 661 MNBCHD (auto:231MHz-4)
20201024-09:59:30 Tuner: tuner1 streaming http to 192.168.1.32:35014
20201024-09:59:31 CableCARD: tuner1 661 MNBCHD (auto:231MHz-4) access = subscribed
20201024-10:00:30 Tuner: tuner0 http stream ended (remote closed)
20201024-12:59:30 Tuner: tuner0 tuning 657 CNNHD (auto:345MHz-2)
20201024-12:59:31 Tuner: tuner0 streaming http to 192.168.1.32:35042
20201024-12:59:31 CableCARD: tuner0 657 CNNHD (auto:345MHz-2) access = subscribed
20201024-17:39:30 Tuner: tuner2 tuning 645 CSPANHD (auto:291MHz-6)
20201024-17:39:31 Tuner: tuner2 streaming http to 192.168.1.32:35092
20201024-17:39:31 CableCARD: tuner2 645 CSPANHD (auto:291MHz-6) access = subscribed
20201024-19:11:29 Tuner: tuner2 http stream ended (remote closed)

NedS
Silicondust
Posts: 1702
Joined: Mon Dec 10, 2018 12:38 pm
x 76

Re: HDHR-prime can't get IP after firmware update

Post by NedS »

Huh, probably not a dying power supply, then. That's weird.

signcarver
Expert
Posts: 9322
Joined: Wed Jan 24, 2007 1:04 am
Device ID: 10802091 131B34B7 13231F92 1070A18E 1073ED6F 15300C36
x 24

Re: HDHR-prime can't get IP after firmware update

Post by signcarver »

For some reason it looks like it took around 18 hours to get an ip address. I have seen this before on some networks (but not with a prime) where a lease isn't expired and tries to renew with a different name than the the reservation table has. The particular case i remember seeing such as it was my equipment was with a moca adapter that had an illegal character (at least for my router) in it's name since I wanted a reservation I changed the name in the reservation table to something like mocaupstairs to not have the foreign characters provided by the device. A brand new lease (after expiration) would be issued with the reserved ip address but any request/renewal would fail if there was an unexpired lease out. I found a few other devices that behaved the same if I gave it a new name in the reservation table. Eventually an update allowed the foreign character and then I edited the reservation table to the name of the device and it worked. As a result of that I haven't changed any names with registration and accept the name when making the reservation.

In your case though it may have been your tweaking that brought down dhcp for awhile.

Post Reply