Bri PS The lower two entries puzzled me, but it would appear that they are related to the Qnap virtual switch feature (which I have yet to read up on). When I get some time, I'll also have a deeper dive through it and look for any references to 'interface', or the likes. On my TS-453Pro, I see the below result returned: 127.0.0.1:9000 10.11.11.22:9000, 10.0.5.1:9000, 10.0.3.1:9000, The above is from a 190 page confidential document relating to Twonky 5.1 (and I was under strict instructions to seek permission before letting anyone else have it) so if you want to look at it, I'd first have to ask permission then figure out a way for us to exchange e-mail addresses (darned pest about the PM feature being disabled). This may provide some help by configuring the server or for troubleshooting' though unfortunately, it isn't followed by a section explaining what to do when there's interface-related trouble to shoot. The main problems I had with Twonky was that it occasionally advertised itself on the local loopback address and back in the day, that caused discovery problems on some control points, so I discovered that I could lock it onto the interface that I wanted by using the below command (obviously, that example shows how to lock it onto 192.168.1.20):Ĭode: Select all Which is there to 'Return the list of network interfaces (NICs), which the server has detected. My Twonky knowledge is based on the Twonky 5 and Twonky 6 days as from Twonky 7 onwards, they limited the ability to build custom trees (though you can still tweak the existing containers). I do still pop in and read, but I haven't typed much for a while (Qnap told me to stop posting Twonky tedium as I was scaring potential customers away ). do you know the command to allow ALL interfaces access to Twonky? Oh yes it is also 64bit too! not sure if that make much difference howvever Hi Simon. I noticed also Twonky installed on my LAN1 interface (default gateway) but not on my LAN2 port which i use for management. Toxic17 wrote:Briain, welcome, havent seen you for here for a while. Bri PS You can enter the key via the Twonky web interface ( ) or if you are as lazy as I am, you can RPC your new key into Twonky via entering the below command (though with a valid key) into your browser, then hitting the enter key: I also updated my TS-219P and as expected, the Qnap supplied (ARM) version of Twonky was not disabled by the 4.3.3 update (though curiously, it didn't show as being running on the 'my apps' page, but it was all working okay I've just shut down the 219, so next time it's up, I'll see if that status has changed on the 'my apps' page). ![]() ![]() ![]() Curiously, when installing the tree I noticed the installation directory is now called 'TwonkyServerEU', but everything else appears to be just as before (other than it now requiring a key). It all seems to behave itself (no high CPU issues, or the likes) and I already had a few Twonky 5 keys from the olden days (when I used to discuss issues directly with the Twonky engineers) so I applied one and it all worked as expected (and I installed a slightly tweaked music tree changing the artist container to an albumArtist container). Hi I have just updated my TS-453 Pro and yes, Twonky didn't work, so I did a search and found the Twonky NAS build pages are still on the go, and indeed, the later ones seem to include various Qnap builds, so I removed the Qnap Twonky package and installed Twonky 8.3 (for my Qnap, it was the 'Qnap x86-64 package') from their site.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |