Issues with Configuring Multiple Streaming Bridges on Differ

Hi.

I have 10 streaming bridges, but when I try to configure each one with different ports it doesn’t work;

the only port that works is 1935! I also tried to set 1935 on the device and another port on the WAN IP with forwarding to have the G2 camera stream to wan-ip:8888 -> lan-ip:1935, but the stream doesn’t start from the camera. It only works if I set 1935 on both the G2 and the streaming bridge.

Details,
all TCP/UDP ports are open on the public IP firewall. I take one streaming bridge, set it to 1935, and generate the XML file, which includes IP:1935 for both RTMP and SRT. I load it onto the G2 camera and it works correctly.

I take another streaming bridge and set it to a random port, for example, 18397. I open the randomly generated port 18397 on the firewall using Atem setup, save the XML file which reports IP:18397 for RTMP and SRT, load the file onto the G2, and it doesn’t work. I replicate the same procedure with other random and manual ports like 1936, and it doesn’t work.

At this point, I run a port scan on the firewall, and the ports appear to be open correctly. I enter the firewall and intercept UDP and TCP packets on the listening port (not 1935, which always works), and see no traffic, literally 0, as if the camera isn’t even sending a packet for the stream. I replicate this for any port other than 1935 and always get the same result.

Reaching the paranoid phase, I take the second streaming bridge that doesn’t work on the WAN and set it to another random port using Atem Setup. This time, I set the LAN IP of the streaming bridge directly, so both the camera and streaming bridge are on the same LAN and subnet. I load the streaming profile onto the camera, and it doesn’t work! Then I reset the configuration in the LAN, set port 1935 on the camera and streaming bridge within the same LAN, and it works… crazy.

1935 is default RTMP port .. But If u change it on both devices , it must work .. I dont have stream bridge , so I cannot test it .. SRT have not default ports .. U can use what do U want ..

But If u change it on both devices , it must work ..

Exactly, it must work.
Can I have a feedback from black magic staff?
Thank you.

It would be helpful to me if someone did the same test of setting the streaming bridge on a random port other than 1935 and making a direct stream on the LAN, and finding out if it works or not.

I set the LAN IP of the streaming bridge directly, so both the camera and streaming bridge are on the same LAN and subnet. [/i][/b]

If you are testing your camera and Streaming Bridge are on the same local network you do not need to configure the Port XXXX element, as you are not sending and receiving via the internet - just select Local with or without a streamkey.

Also, you have not mentioned Port Forwarding. Port 1935 sounds already configured as you've had it working, but when you allocate a Port 1936 connection, it doesn't work. So, when streaming the camera to the SB via the internet, have you configured a TCP or UDP Port Forward Service on your router to Port Forward 1936 to the local static IP of the Streaming Bridge? RTMP uses TCP, SRT uses UDP.

I set the LAN IP of the streaming bridge directly, so both the camera and streaming bridge are on the same LAN and subnet. [/i][/b]

If you are testing your camera and Streaming Bridge are on the same local network you do not need to configure the Port XXXX element, as you are not sending and receiving via the internet - just select Local with or without a streamkey.

Also, you have not mentioned Port Forwarding. Port 1935 sounds already configured as you've had it working, but when you allocate a Port 1936 connection, it doesn't work. So, when streaming the camera to the SB via the internet, have you configured a TCP or UDP Port Service on your router to Port Forward 1936 to the local static IP of the Streaming Bridge? RTMP uses TCP, SRT uses UDP.

Obviously I didn't explain myself well in the first post

That is, what comes to my mind is that the streaming bridge listens exclusively on the 1935. Which... It wouldn't be a problem at this point. However, the problem becomes more complicated when, By loading the stream profile on the G2 camera on a customized port, for example 1936, and on the router you set the forward towards the 1935 LAN of the SB locale ip, from the camera, no stream start on the custom port . I have verified this putting my server listening incoming packets like the streaming bridge on the 1935 and also sniffing the Wan 1936 and no one packet arrive..

To be clear: G2 on 4g network stream to my public network on 1936, with firewall forwarding traffic from 1936 TCP UDP to streaming bridge lan IP 192.168.10.200 on 1935

Camera 3: to pub net on port 1937 with forward to Lan SB 192.168.10.201 on 1935.

Etc.. to camera 10..
----------------

Therefore the custom port that set the Atem setup, it's not real custom port for the streaming bridge server, but it's a mechanism trying to set forward traffic on the wan router probably using upnp (poor) technology
--------
Obviously by setting the G2 camera to 1935 everything works..
--------
I'm sure that if I get a pool of 10 public ip's from isp and setting each stream to 1935 for each ip on the firewall all will works

I'm sure that if I get a pool of 10 public ip's from isp and setting each stream to 1935 for each ip on the firewall all will works

Test Results:
As expected, I added a second public IP to my firewall server (without UPnP and similar) with static NAT for port 1935. The G2 camera stream is coming through correctly (using a different port with the G2, no traffic was sent out, verified sniffing the incoming traffic), and the streaming bridge is receiving it as expected, even when set to local network only while receiving from the internet.

With two public IPs, both using NAT with port 1935 open, everything works consistently.

Works correctly without issues even through the G2 on 5G smartphone to a datacenter server with multiple ip's and server forwarding over virtual network device to remote LAN IPs via udp VPN

I have this exact issue and can confirm everything josephjj has already written above. My only idea on solution is to go back a few generations in firmware on either the Streaming Bridge or the encoder (Web presenter for me). But how long back, and is it really reasonable when this is obviously a simple bug for Blackmagic to solve?

Ok, after spending the whole day with this I finally found a solution. Back up to ATEM Switchers 8.10.1 Update and it will all work fine.

Ok, after spending the whole day with this I finally found a solution. Back up to ATEM Switchers 8.10.1 Update and it will all work fine.

You mean firmware downgrade? The old one use the old rtmp instead of the srt?

I'm working now with 10 dedicated public ip's, one for each camera..total 250mbps stable..from 0,5 to 1,2sec delay... and complex forwards rules per ip on the firewall to remote vpn lan ip's.

All works perfectly..., except for those delightful monthly IP costs

I'm rather late to the party with this one! But the issue with the Port setting on a streaming bridge is that since the software update arround 8.6 it's for decoration purposes only! You change the port to say e.g. 1936 and the software will say 1936. IT'S LYING!!!!! The port is still at 1935 and won't change. If you want to confirm this for yourselves, Do a scan with something like Angry IP for the address and port. For two years, Blackmagic is fully aware of this BUG and have accepted that it is one and DON'T CARE! The answer I got was "Don't expect anything to be done about it any time soon!
I was using three to send back feeds for remote loggers at base for 60 hours of live broadcast over a week covering the largest youth festival in Europe. I've got no hair left and only use one streaming bridge now and switched to another decoder for the other two feeds. The other Streaming bridges are paper waits unless Blackmagick gets it's finger out!

Strong language, but you can get a feel for my frustration!

It's a very customized solution with iptables and central server, but it works well, certainly not a plug and play setup. For the future, if you need it, I can replicate it for you but it will require a few hours of configuration and testing of VPN, firewall, cameras and devices. In the meantime I've built a centralized server for multi unicast out srt distribution that rocks! If so, I can show you my solution.You can make a mega srt distribution at any frame rate and resolution and mbps of your choice

The part of the input to the setup program is only for creating XML to be imported into ATEM. I have not changed any of the settings on the unit. The router has to convert its port to the default 1935 or communication is impossible.

Sure.. In fact there is only one port 1935 per public IP and more 1935 ports, one for each camera
But the destination point .. the single public IP, is the same for all' the 1935 cameras good luck ..

The part of the input to the setup program is only for creating XML to be imported into ATEM. I have not changed any of the settings on the unit. The router has to convert its port to the default 1935 or communication is impossible.