Page 1 of 1
Network binding, responsiveness

Posted:
Tue Jan 08, 2013 5:36 am
by ouroborus
I installed serviio a couple days ago and so far I have two issues with it.
The first is the server's binding strategy. It took me several hours to figure it out, but I did eventually. (Thanks for the logging facilities.) It seems serviio can receive playback requests via all NICs but can only serve them on one, the one its bound to. I have several NICs (Ethernet, Hamachi (LogMeIn), Gbrige, VirtualBox, etc.) and serviio decided Hamachi was the one to use for default. My suggestion on this is to change this strategy so that the default binding is IP 0.0.0.0 and then serve the video via whatever NIC the request came through.
The second issue I've noticed is that the responsiveness while navigating the menus is pretty poor. It takes 1/2 to 1 second to respond to each command and it won't accept further commands until it has responded. (This seems to only happen during folder/file navigation. Video play commands have a snappy response.) In comparison, Samsung's AllShare software appears to have no noticeable delay.
Otherwise, great software. I especially like the trans-coding and the predefined profiles.
My equipment: Windows 7 Ultimate, Samsung 6030 TV (UN40EH6030FXZA), 100BASE-T ethernet in between.
Re: Network binding, responsiveness

Posted:
Tue Jan 08, 2013 9:47 am
by zip
I'm actuall thinking of scrapping the use of multiple NICs and only advertise and accept request on the bound IP. I had some cases where incoming requests from devices on a different subnet come in with the router's IP address (on the same subnet as Serviio) rather than the device's original one. Not quite sure why this is happening, might be some feature of some routers.
I build in some functionality to select the proper NIC by default, but it doesn't work always 100%, especially when you have a lot of active NICs.
Browsing is very fast for me, all the responses are cached. You could check the
detailed log it the delay is on the Serviio side or if it might be the actual network transmit taking some time.
Re: Network binding, responsiveness

Posted:
Wed Jan 09, 2013 5:50 am
by ouroborus
I restarted the service and the console and (after working through some other issues, below) the response time is much better.
It seems that serviio is not really Windows 7 aware.
Launching console without admin privileges and service off: Console hangs. No console and no taskbar icon. Trying to start it again logs something that, with experience, might be interpreted as saying that it's already running but nothing else. Task Manager required to kill process.
Launching console without admin privileges and service on: Console appears to work, but logging seems crippled and responsiveness is poor.
Launching console with admin privileges and service off: Complains about service not running and exits.
Launching console with admin privileges and service on: Console appears to work, logging works, responsiveness is good.
The start and stop service scripts require admin privileges to work, but don't give any obvious indication as whether they were successful or not.
Re: Network binding, responsiveness

Posted:
Thu Jan 17, 2013 9:34 am
by Slinky
Hi,
Not sure if this is the right place or not, try to find an answer.
I'm running serviio on a server which has two ethernet ports. When i search for my samsung tv under the renderer profile it is not there and serviio only shows devices on one port of the ethernet (lets call it port B).
The ports are bridged and the network is fine. I used to have serviio running on the machine hanging off port B just fine, however now i cannot discover any devices hanging off port A.
I'm not sure if this is a problem with network binding or not. Both ports use the one bridge ip. Is there any way to manually add a device or is there something else I may be doing wrong?
Thanks
Re: Network binding, responsiveness

Posted:
Thu Jan 17, 2013 10:33 am
by zip
are they all on the same subnet?
Re: Network binding, responsiveness

Posted:
Fri Jan 18, 2013 1:22 am
by Slinky
are they all on the same subnet?
Yes, did some more playing around, reinstalled serviio onto the computer on port B and same problems. This led me to believe it was a network problem. I went back to a wired connection to isolate one of the routers and it works. (I originally thought it wasn't the network because I had changed to the wireless solution and serviio on computer B still worked. )
Just wondering if it is the discovery of the devices that my wireless network is somehow blocking (just installed dd-wrt on the isolated router so still not sure how to change most of the settings) because it did work over the wireless network when i first changed over and didn't have to discover the device, just send to it.
I know this is definitely not a serviio problem anymore but your help would be appreciated.
Thanks
Re: Network binding, responsiveness

Posted:
Fri Jan 18, 2013 1:35 am
by Slinky
Confirmed.
Switching back to wireless without making any changes, and it still works. Just needed to discover the device first.
Is there any way to manually add a device so that I don't have to run a temporary cable across the house?
Re: Network binding, responsiveness

Posted:
Tue Feb 12, 2013 3:09 pm
by rub
Sorry to intrude on this. But it would be very usefull having serviio only advertise Upnp on a single NIC. I'm using the same machine as a router and it seems to be sending Upnp packets on the LAN and the WAN side. I'm currrently stopping these packets with an outgoing iptables rule so it's not a real issue for me , but i'd love to see this "fixed" in a future release.
Keep up the good work. It's working like a charm with my samsung tv.
Re: Network binding, responsiveness

Posted:
Tue Feb 12, 2013 4:06 pm
by zip
rub wrote:Sorry to intrude on this. But it would be very usefull having serviio only advertise Upnp on a single NIC. I'm using the same machine as a router and it seems to be sending Upnp packets on the LAN and the WAN side. I'm currrently stopping these packets with an outgoing iptables rule so it's not a real issue for me , but i'd love to see this "fixed" in a future release.
Keep up the good work. It's working like a charm with my samsung tv.
I just implement single NIC advertisements only for 1.2, exactly because of these problems. Hopefully it won't break setups of others
