What is my inbound IP address when using SFC?

Hi all, I’ve setup port forwarding to a camera (for RTSP), and I have SFC configured and the Chicago relay selected; where do I find my inbound IP address for that relay so that I can connect to my camera stream? (My carrier is CG-NATed.)

Hi, @vendooradam

Welcome to community…

About SFC Relay…
Have you watch this?

You will configure your camera to some lan ip address at lan side of your peplink devices.

Hi @MarceloBarros , thanks so much.

I should have explained my problem better; my camera and my Peplink are on the same PoE switch. (And nothing else.)

I have setup the Peplink to port forward inbound traffic on port 554 (the default for RTSP) to the static IP of the camera.

In order to view the camera stream, I need to go to something like (this will not be exact because I’m on mobile) username:password@ipaddress:554 where ipaddress is my public facing ip address. Since my carrier is CG-NATed for SIM data, it’s my understanding the whole point of SFC is that I get a “static” IP address from Pep which routes to the relay which then passes traffic to my device. (And the device then port forwards that specific traffic to my LAN device.)

The part I’m missing, I think, is that I don’t know or know how to find the public IP that SFC holds on my behalf.

The video you showed seems to suggest that I can tunnel two Pep devices to each other through the SFC relay.

Hi, @vendooradam

Peplink don’t share the public ip address of the SFC Cloud Server.
Peplink don’t allow users to configure incoming tcp/udp connections to their SFC Cloud Server.

The main idea of SFC Relay it is connect two or more Peplink devices, behind CGNAT, but all devices will be able to have communications using their lan ip address.

To use your mobile or PC, to be access your camera streaming, you will need to be at this Relay Cloud, bettwen your devices… And to do this… you need to have your Peplink with a VPN service with a public ip vpn server (third part vpn service provider) , that allow you to contract and manage what kind of incoming tcp/udp a public ip address dedicated for your needs.

You can use OpenVPN for this, which is built in on your Peplink device. You can configure it on your local device interface > Advanced > Remote User Access and, once configured, you can download the configuration files from the local device interface > Status page. This is a secure and straightforward way to access the camera.

As Marcelo mentioned, Peplink is essentially an ISP while providing the SFC service, and they will not do any 1:1 NAT, port forwarding, or pinning for you; no ISP will.

Lastly, port forwarding from an internet-facing interface to something internal is a terrible idea, please do not do it. There are no security cameras that support RTSP that are hardened to the level where you should feel comfortable exposing them directly to the internet. This is how botnets get nice and big :slight_smile: