WDTV Live Restarting

[MajicM]

Changed my SuperHub settings.... Fingers crossed.

My box is turning itself on as well though, could that be down to the UPNP?

Hope this resolves it

[Perfik]

I had the same problem and I changed the Superhub setting a while ago AND it has never happened since. Good luck to all.

[MajicM]

2 days now and the box hasn't turned itself on... about to watch some TV, let's hope no reboots

[steelrattuses]

Another person here with the so called Super Hub.

I've been happily using my WD TV Live for months. Got the hub a week ago, and been having reboot problems ever since. Luckily a friend found this and pointed me here. I have increased the uPnP value to the maximum, and I suspect that will solve my problem.

The so called Super Hub didn't work for two hours after Virgin installed it. But mysteriously has worked ever since. Speaks volumes!

[noknok]

To WD Technical Support:

I have spent 2 days diganosing this problematic reboot with the WD LIVE.  The bug in the firmware exists on 1.05/and 1.06 branches.

Going back 2 revisions on the firmware to 1.04 resolves the issue.

What the issue is:  UPnP..  In the latest firmware releases, when entering the MEDIA SERVER browsing on the device, you send out 4 consecutive SEARCH UPNP packets for MEDIASERVER devices.  You do this, every 1 second at a minimum and dont stop.  Because of this, you get literally hundreds then thousands of REPLIES from devices.

It seems your UDP buffer is blowing up because of all the fast responses your getting, and can not process.  By scrolling in the MEDIASERVERS you can force the box to reboot 100% of the time.

You need to delay sending your M-SEARCH packets, by at least 5-10 seconds, as devices have up to 3 seconds to respond.  

FIX THIS BUG !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

The device is 100% unusable in any fashion if your using DLNA.

If you would like to contact me, I can provide more specific details.

developer / @ / noknok / .net

[noknok]

Also - if your listening......

Would be nice if you accepted a LOCATION: [Deleted]

Which was NOT on the local subnet.  I have remote DLNA servers in the cloud, which a utility broadcasts them in my local network.  GoogleTV, PlugPlayer, Boxee, WMS, XBOX, PS3 all accept them and work perfectly, but the WD LIVE requires the LOCATION header in the SSDP message to be a LOCAL IP on the same subnet.....

Just saying would open a lot of useful stuff

[TonyPh12345]

How many devices do you have that would cause THOUSANDS of responses?   I have 6 DLNA servers on my network and never had this happen...

[noknok]

Do a wireahark capture if you can...

Simple, I have about 10 DLNA devices, then in my office I have over 50 computers all responding to DLNA requests.

But at home, the WD NAS sends out 4 consecutive M-SEARCH Requests every secondt.  Each DLNA Device receiving a request must respond to that request 3 times, gapped by 200ms.  So the first series sent out by WD, gets back 10 devices x 3 responses x 4 requests from the WD = 120 responses in the first round.  then every second thereafter same thing.  So the WD is getting inandated, or something has changed in how they are handling these messages, because with 4 different WD's I can reproduce this EVERY time.

Again, reverting to 1.04 branch, this does not happen.