Yes, it was the EPG updating during the OTA window.
Yes, this fix will block all traffic between the Humax and any IP address which is rejected. So, if you create a route reject for the IP of your NAS, the Humax will not be able to play files from it, whether direct or through any media server (twonky or otherwise) that is hosted on the NAS.Does this work around block ALL traffic from the NAS so that the humax cannot even see the NAS to play media?
In other words, with this fix the humax cannot play content from twonky and have to use other clients to play media?
Is that correct?
I tell a lie... the reason I am running the old Zyxel 4.22 firmware is so that I can leave the media server enabled (when I updated to 4.50 I found that I had to disable it, so I reverted).Personally, I use automount to allow my HDR-Fox-T2 to access the files on my Zyxel NAS direct, and Twonky is disabled.
No a properly written IPTables rule will allow a great deal of control of what is allowed through and dropped by address, protocol, ports etc.As far as I know, anything port or IP related will block access between the 2 devices completely, not allowing them to talk to each other, but will allow them to exist on the same network with content sharing turned on.
You're right, but I wasn't able to reproduce the problem on my network, even by running various versions of Twonky on a Linux box. Haven't picked it up again. The idea is to create a 'twonky-protect' package or similar which stops the crashing but still allows other communication between the devices - potentially even preserving DLNA functionality. The custom kernel IP tables only has very basic features compiled in at present but can easily be extended to even include packet text matching if that's necessary.I vaguely recollect af123 was doing something along these lines.
So why not just reverse the QNAP update?My QNAP has just had a firmware update and that has moved it onto Twonky 7 causing the Humax crashing problems. I have done the blocking fix for now to stop it rebooting (I hope).
Has anyone found any other ways to work round this so that the Humax can still connect to the NAS?
So why not just reverse the QNAP update?
I am quite happy with command line stuff, so I think it is worth me spending a bit of time to have a deeper look into this. I'm not overly familiar with the syntax for ipTables, though I have used it in the dim and distant past on some router or other. I presume I need to upgrade to CFW v3 first as I am still on 2.22. Any more pointers people can give would be appreciated. I will then investigate and see what I can come up with.It would be good to get to the bottom of this and work out what's required to make the two coexist. The fault is definitely with the Humax, but there is a way to achieve what the OP wants, namely to stop the Humax crashing whilst still being able to use the NAS features of the QNAP.
@rowanmoor - how familiar are you with the command line? Even if you aren't, if you're willing we should be able to talk you through gathering the information needed.
My QNAP has just had a firmware update and that has moved it onto Twonky 7 causing the Humax crashing problems.
A workaround on the QNAP side is to disable Twonkymedia DLNA Server in the QNAP Control Panel, then separately install an earlier version of Twonky as a QPKG. Personally I still use Twonky 6.0.34, which I downloaded from here, and it coexists happily with the HDR.So why not just reverse the QNAP update?