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.
2 Likes
Just another comment…
Starlink don’t provide public ip address to be used for this kind of " server " side solution.
2 Likes
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.
3 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.
1 Like
Hi, I have a similar situation and I really would appreciate if someone could guide me through all the steps on how to make this:
Alternatively, if you could direct me to an existing guide, that would be very much appreciated.
I followed this guide from the great Martin Langmaid for making the FH https://www.youtube.com/watch?v=ZxZBWloVizM
Also, do I need to add a firewall rule also on Vultr?
Thanks in advance.
Lorenzo.
How far have you got so far?
If you can get the FusionHub built, the SpeedFusion tunnels configured (suggest you use Ic2 to manage all of this as it makes things a bit easier) then for the port forwarding try these steps:
-
Build SpeedFusion tunnels, make sure there is no NAT enabled on the profile as that just complicates things.
-
On the FusionHub go to Advanced > Port Forwarding and create a rule like this:
By default, in Peplink the firewalls are wide open, the same on Vultr unless you have configured something else - I would normally suggest you get everything working without the firewall configured, and then once you are happy you can begin to lock down what is accepted / dropped.
The port 20001 I chose randomly, use whatever matches your setup but that is the “SRT Listener” that you would have on your vMIX PC or whatever is the receiving side of the SRT link.
The “Server IP Address” is the IP of your vMIX PC or whatever is the RX side of the SRT link.
If you need multiple SRT streams then repeat the steps to make more rules with different ports used.
On your SRT caller, i.e. the TX side you would configure it to connect to the public IP of the FusionHub and the port you configured there.
Traffic will arrive at the WAN IP of the FusionHub and be forwarded to the Server IP/port combo you define in the rule.
3 Likes
I just tried it and it works perfectly.
Thank you so much for your help!
2 Likes
Hi Mark,
As Marcelo suggested, your WAN’s IP is a private one, which means you’ll have to open ports on both routers (your WANs router and the Peplink one). I have been able to send and receive SRT succesfully doing that.
If that is not possible, I have also been able to receive SRT in vMix using a cellular WAN by doing both port forwarding and NAT mapping.
I hope this helps,
Ignacio
2 Likes