With the windows application DDTV (Digital Devices application like DVBviewer) it works between the two network segments.
I'd need network captures from the DDTV traffic (discovery + streaming) to fully understand your setup.
With the windows application DDTV (Digital Devices application like DVBviewer) it works between the two network segments.
I'd need network captures from the DDTV traffic (discovery + streaming) to fully understand your setup.
I'd need network captures from the DDTV traffic (discovery + streaming) to fully understand your setup.
I will try to get network traces with tcpdump - hope i will get the filter right.
With DDTV i had to set the sat>ip server IP explicitly - there was no discovery.
Thanks!
With DDTV i had to set the sat>ip server IP explicitly - there was no discovery.
So, what was your satip command-line to achieve the same?
So, what was your satip command-line to achieve the same?
I didn't compile satip-plug, i use a ppa package for yavdr (satip v1.0.0). In yavdr the switches/parameters for the plugins are to be set in separate plugin config files. There i set -d 2 (for 2 satip tuners) and -s 192.168.35.62. Nothing more. The network setup is not very compilacted: there are only two collision domains (network segments) - one is routed, the other is "NATed".
192.168.2.0/24 --> there vdr-box is located (192.168.2.100). vdr-box knows (via the router as gateway) how to get to 192.168.35.0/24 (icmp works)
192.168.35.0/24 --> location of sat>ip server (192.168.35.62). vdr-box reaches the sat>ip server with an IP out of 192.168.35.0/24 (NAT address).
I will trace the networktraffic in the next days and will inform you!
Thanks!
here's a network snap with no "-s/--server" parameter set - there are "multicast" udp packets (SSDP/discovery!) at the start of vdr/satip-plug and during runtime:
ZitatAlles anzeigen18:29:26.959505 IP (tos 0x0, ttl 1, id 3216, offset 0, flags [DF], proto UDP (17), length 146)
192.168.2.100.1900 > 239.255.255.250.1900: UDP, length 118
.
.
.
18:57:27.243711 IP (tos 0x0, ttl 1, id 26281, offset 0, flags [DF], proto UDP (17), length 146)
192.168.2.100.1900 > 239.255.255.250.1900: UDP, length 118
With the sat>ip server in netsegment 192.168.2.0/24 everything is working fine.
With option "-s 192.168.35.62" (sat>ip server located in the other net) or option "--server=192.168.35.62|DigitalDevices|OctopusV2" set, there's no packet in direction 192.168.35.0/24 (unicast), no broadcast and no multicast-packet.
In DDTV i set sat-ip server to 192.168.35.62 with port 554 (default) and "RTP Setting: UDP Ports 52000-52100" (that's default as well)
Thanks!
ciax
hmm -
yes! now it's working!
Is there any reference for the settings "-s <ipaddr>|<model>|<desc>" ?
Maybe i missed something - sorry for the noise!!
Thanks!
ciax
You'll have to tweak the model against your configuration: a comma separated list of <system>-<number of tuners>. For example "DVBS2-2,DVBT2-2"
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!