web frontend shows wrong stream link

[jyrts]

My minisatip running on 192.168.2.65 with startup command line: /usr/bin/minisatip -R /usr/share/minisatip/html -o 127.0.0.1:9000,10 --disable-dvb --disable-ssdp -s 192.168.2.16 -s 192.168.2.17 -s 192.168.2.22 -s 192.168.2.20 -s 192.168.2.18 -s 192.168.2.24 -s 192.168.2.23 -s 192.168.2.32 -s 192.168.2.19 -s 192.168.2.25 -s *dvbs2:192.168.2.128 -s dvbt2:192.168.2.34 -s dvbt2:192.168.2.34 -A 0:0:0,1:1:0,2:2:0,3:3:0,4:4:0,5:5:0,6:6:0,7:7:0,8:8:0,9:9:0,10:10:0

My client is using url: http://192.168.2.65:8080/?freq=11919&src=3&sr=30000&pol=V&msys=DVBS2&mtype=qpsk&pids=6411,6422,6451,6409,0,20

All woking good. BUT. When I look the minisatip web frontend at http://192.168.2.65:8080 then is shows the client is using url
http://192.168.2.65:8080/?freq=11919&src=1&sr=30000&pol=V&msys=DVBS2&mtype=qpsk&pids=6411,6422,6451,6409,0,20

src=1 not src=3. It should show src=3 in stream url

seem like minisatip web frontend can't show correct "src" values. bug

[catalinii]

Can you upload a log with -l http?

[jyrts]

Are the logs really necessary. It is pure front-end visual problem?
As you can see from the startup command I am using minisatip as "virtual diseqc" but it looks like the minisatip web frontend is not used to that...

[jyrts]

the wrong SRC number is also in the RTSP link:
rtsp://@:554/?freq=11919&src=1&sr=30000&pol=V&msys=DVBS2&mtype=qpsk&pids=6411,6422,6451,6409,0,20

I am using the -A 0:0:0,1:1:0,2:2:0,3:3:0,4:4:0,5:5:0,6:6:0,7:7:0,8:8:0,9:9:0,10:10:0 command on startup (for virtual disqc)

Seems like whatever the real SRC value in the request URL is... The minisatip webfrontend shows always SRC=1 in stream link

[jyrts]

Ok ok. I will upload the logs. maybe web frontend stream link is show'ing src=1 in the url because src=1 is used by the upper level incoming satip server. But it is worng, because the link is showing clients who connect to minisatip, not where minisatip is connecting to...

[Jalle19]

IIRC this has been brought up before, maybe @lars18th remembers? I couldn't find any previously created issues about it though, it was probably a discussion in an unrelated issue.