OK, let me try to make some observations..
You have 2 NICs and Serviio uses both to search for renderers:
- Code:
2013-01-06 01:41:56,920 DEBUG [RendererSearchSender] Multicasting SSDP M-SEARCH using interface eth3 (Realtek PCIe GBE Family Controller) and address 192.168.1.46, timeout = 0
2013-01-06 01:41:56,920 DEBUG [RendererSearchSender] Multicasting SSDP M-SEARCH using interface net3 (Intel(R) WiFi Link 5300 AGN) and address 192.168.2.17, timeout = 0
You have 2 subnets, .1.x and .2.xx, with the TV on .2.20 IP.
The TV responds to the search correctly:
- Code:
2013-01-06 02:15:22,021 DEBUG [RendererSearchSender] Received a valid M-SEARCH response from Renderer 420b3337-bcc4-a2aa-13a2-9ec471b5ec19 from address /192.168.2.20:57360
This is what you see in the console as Samsung DVR.
When Serviio advertises itself it also uses both NICs, and the TV responds like this:
- Code:
2013-01-06 02:15:24,177 DEBUG [WebServer] Incoming connection from /192.168.1.3:42144
2013-01-06 02:15:24,178 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.3
2013-01-06 02:15:24,178 DEBUG [DeviceDescriptionRequestHandler] DeviceDescription request received for device c48120f2-ff22-3b77-88f3-f16bdd0d2e60 from 192.168.1.3 (headers = [HOST: 192.168.1.46:8895,USER-AGENT: SEC_HHP_Hjemme-TV/1.0,ACCEPT-LANGUAGE: en-us])
From there on it uses the .1.3 IP address to talk to Serviio. What is the .1.3 IP? Any idea what device it belongs to?