Live u setup over Starlink/Peplink

I need help setting up port forwarding to send LIVE U (caller) Srt to Vmix (listener) remotely to my OB, which uses Peplink Transit Duo Wan 1, Starlink and 2 x LTE.

I set up Port forwarding to Vmix PC

Access rules

Wans

Looks like you have it setup correctly…

What’s the issue you are having?

Post a screenshot of your vmix settings for the SRT input.

1 Like

So no picture coming thru into vmix!

So my vmix side is simple “listener” port 10254 its the srt settings in the live u solo pro and what address to input. Its needs the correct static ip.

I think the SL doesn’t allow static ip on their consumer subscription only business.

Im thinking Live u needs the peplink static ip in SFC. I dont know lol i tried for hours.

I can send a srt to vmix in my studio pc from the live u no problem. Its trying to create a static ip remotely while using the OB

Hi… Look at your WAN IP address.
here (Brazil) we call it a private ip address (RFC-1918) 192.168.x.x/16 … It is not a public ip address.
Because this, it not working.
When using Live-U solution… your " listening side " should have a public IP address at WAN port.
Also… ip network address 100.64.x.x to 100.127.x.x are private ip address (CGNAT).
The only address that have a public ip address it is CELL2 (NZ?) but… LTE-A maybe it is not be enough to be the " listening side " for LIVE-u.

1 Like

Just another comment…
Starlink don’t provide public ip address to be used for this kind of " server " side solution.

1 Like

That won’t work either, there is no inbound connectivity provided by SFC.

Well that is not true, they can provide a public IP as long as you are on the correct tariff and put the dish into bypass / bridge mode.

Regardless, @markhepi what would probably be the easiest and relatively low cost solution would be to host a FusionHub Solo somewhere (Vultr, Digital Ocean, AWS, GCP, Azure etc. pick whatever works for you and your budget but there are plenty of minimal cost options).

You would have a public IP on the FusionHub WAN.

Your TST Duo in the OB would create SFVPN to the FusionHub and your remote SRT caller would connect to the public IP of the FusionHub.

Port forwarding would be done on the FH towards the LAN IP of your vmix PC.

SRT Caller > FusionHub WAN IP > SFVPN > TST Duo > vmix PC

This also gives you the advantages of SFVPN such as bonding, WAN Smoothing, better failover between various WAN connections etc. all of which are probably highly desirably in your environment.

2 Likes

Hey… When I wrote about Starlink… I comment about what happening here at Brazil. They don’t provide public ip address associate to a unique dish.