A problem with how Serviio advertises itself to the TV?

Hi.

I have a Sony Bravia KDL-52W55000, and I am experiencing some problems with how Serviio (1.4.1.2) advertises itself to it.

The situation is that I have 2 NICs active on the server. I currently don't have a router, so one of the NICs is connected to the internet (and has an external IP) and the other NIC is connected straight to the TV (and has an internal IP).

I have set up in the Serviio console that it should use the NIC with the internal IP. This works fine. No problems. The TV picks up the sever and vice versa. Streaming works too. There is nothing wrong with my configuration.

But the problem is this: When I turn off the TV, Windows (XP) sees the cable as "unplugged". This in turn causes Serviio to fall back to the other NIC and advertise itself on the external IP, instead. For me, that's not much of a problem. But the real issue is when the TV comes back on. Windows notices that the cable is now "connected" but it seems like Serviio doesn't. As such, it keeps advertising itself on the external IP, without switching back to the NIC I have actually selected.

In the console, the correct NIC is always shown as the selected one. It was only in the log I could determine that Serviio was changing to the external IP, and not switching back. Naturally, as long as the TV is on, just pressing "stop", then "start" in the console fixes this and the TV instantly picks up Serviio again, because Serviio restarts the advertising process and begins with the NIC I have selected. But this is a hassle, as I need to do it *every* time I turn on the TV.

I understand there are Android apps and such that can remote this, but in truth Serviio should simply understand that the cable is now connected and start advertising to the selected NIC again. Or I should be able to force an NIC/IP to always be used, despite connections status.

I have seen the system variable "serviio.boundAddr" but I don't think this actually forces the IP despite connection status? Or does it?

Any help is appreciated.

Log from when the TV is turned off:

  Code:

2014-09-13 19:57:02,265 WARN  [MultiCastUtils] Host IP address 192.168.1.1 is not available, will try again 9 times
2014-09-13 19:57:07,265 WARN  [MultiCastUtils] Host IP address 192.168.1.1 is not available, will try again 8 times
2014-09-13 19:57:12,281 WARN  [MultiCastUtils] Host IP address 192.168.1.1 is not available, will try again 7 times
2014-09-13 19:57:17,281 WARN  [MultiCastUtils] Host IP address 192.168.1.1 is not available, will try again 6 times
2014-09-13 19:57:22,281 WARN  [MultiCastUtils] Host IP address 192.168.1.1 is not available, will try again 5 times
2014-09-13 19:57:27,281 WARN  [MultiCastUtils] Host IP address 192.168.1.1 is not available, will try again 4 times
2014-09-13 19:57:32,281 WARN  [MultiCastUtils] Host IP address 192.168.1.1 is not available, will try again 3 times
2014-09-13 19:57:37,281 WARN  [MultiCastUtils] Host IP address 192.168.1.1 is not available, will try again 2 times
2014-09-13 19:57:42,281 WARN  [MultiCastUtils] Host IP address 192.168.1.1 is not available, will try again 1 times
2014-09-13 19:57:47,281 WARN  [DiscoveryAdvertisementNotifier] Cannot acquire NIC for current bound IP address 192.168.1.1, will re-acquire new IP
2014-09-13 19:57:47,281 INFO  [DiscoverySSDPMessageListener] Leaving DiscoverySSDPMessageListener
2014-09-13 19:57:47,281 INFO  [EventDispatcher] Leaving EventDispatcher
2014-09-13 19:57:47,281 INFO  [EventSubscriptionExpirationChecker] Leaving EventSubscriptionExpirationChecker, removing all event subscriptions
2014-09-13 19:57:47,281 WARN  [MultiCastUtils] Could not find NIC with name 'eth1-0'
2014-09-13 19:57:47,281 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth1-0, will try again 9 times
2014-09-13 19:57:47,281 WARN  [MultiCastUtils] Could not find NIC with name 'eth1-0'
2014-09-13 19:57:47,281 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth1-0, will try again 8 times
2014-09-13 19:57:47,500 INFO  [RendererExpirationChecker] Leaving RendererExpirationChecker
2014-09-13 19:57:52,281 WARN  [MultiCastUtils] Could not find NIC with name 'eth1-0'
2014-09-13 19:57:52,281 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth1-0, will try again 7 times
2014-09-13 19:57:57,281 WARN  [MultiCastUtils] Could not find NIC with name 'eth1-0'
2014-09-13 19:57:57,281 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth1-0, will try again 6 times
2014-09-13 19:58:02,281 WARN  [MultiCastUtils] Could not find NIC with name 'eth1-0'
2014-09-13 19:58:02,281 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth1-0, will try again 5 times
2014-09-13 19:58:07,281 WARN  [MultiCastUtils] Could not find NIC with name 'eth1-0'
2014-09-13 19:58:07,281 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth1-0, will try again 4 times
2014-09-13 19:58:12,281 WARN  [MultiCastUtils] Could not find NIC with name 'eth1-0'
2014-09-13 19:58:12,281 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth1-0, will try again 3 times
2014-09-13 19:58:17,296 WARN  [MultiCastUtils] Could not find NIC with name 'eth1-0'
2014-09-13 19:58:17,296 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth1-0, will try again 2 times
2014-09-13 19:58:22,296 WARN  [MultiCastUtils] Could not find NIC with name 'eth1-0'
2014-09-13 19:58:22,296 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth1-0, will try again 1 times
2014-09-13 19:58:27,296 WARN  [MultiCastUtils] Could not find NIC with name 'eth1-0'
2014-09-13 19:58:27,296 INFO  [Device] Updated bound IP address of Device with UUID: 232e919c-d3d9-3eeb-ac51-8e4209d980af, bound address: 109.228.163.58
2014-09-13 19:58:27,296 INFO  [EventSubscriptionExpirationChecker] Starting EventSubscriptionExpirationChecker
2014-09-13 19:58:27,296 INFO  [DiscoveryAdvertisementNotifier] Starting DiscoveryAdvertisementNotifier
2014-09-13 19:58:27,296 INFO  [EventDispatcher] Starting EventDispatcher
2014-09-13 19:58:27,296 INFO  [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface eth0 (D-Link DGE-528T Gigabit Ethernet Adapter - Packet Scheduler Miniport) and address 109.228.163.58, timeout = 0

If I turn on the TV after this, Serviio does not revert (it does not do anything).

[atc98092]

What you need is something that tells your computer that it still has an active internal LAN connection. The least expensive option I can think of is putting a small Ethernet switch between the computer and TV. Also, this way you don't need to use a crossover cable, and has the benefit of providing a connection for another computer or other network device.

http://www.newegg.com/Product/Product.aspx?Item=N82E16833704042 This is likely the least expensive way to go. It gives you a gigabit network (way overkill for your existing two devices, but plenty of room for future use). It's $19 with free shipping. For the absolute cheapest way, they have a 100BaseT 5 port switch for $10. Don't use an old cast off 10BaseT switch. That's too slow for anything nowadays.