Hi Egor,
Apologies, my examples were taken from a RUTX50 on firmware 07.06.6, so now I see the dialogue is different to your firmware version.
So, to populate your example …
Name = Nest 11095
Protocol = TCP + UDP (don’t know if Nest relies on ICMP but could add it in aswell, if these 2 don’t work)
Source = wan
Source MAC address = Any
Source IP address = Any
Source Port = Any
External IP Address = Any
External Port = 11095
Internal zone = lan
Internal IP address = [insert the camera IP that you set up as a static IP in DHCP]
Internal port = 11095 (I assume your camera requires the same port number)
Send screen shot if struggling to complete the above.
As an explanation of the boxes, the following can be considered ‘advanced’ options and the first 3 are used to lock down the port to match traffic only from a particular ‘device’ on the wan (internet). As we don’t know these details of the Nest infrastructure, we will accept input from anything that ‘talks’ to us on port 11095 - hence the ‘Any’ setting …
Source MAC address = Any
Source IP address = Any
Source Port = Any
External IP Address = Any
I’m assuming you have the ‘Any’ option for all of the above.
The key ones for you are …
Protocol = TCP + UDP (The ‘usual suspects’ for protocols over the internet)
Source = wan (we are ‘listening’ for traffic coming from the internet)
External Port = 11095 (we are only interested in external internet traffic, with the above protocols, hitting this port)
Internal zone = lan (we are going to forward this traffic to the lan)
Internal IP address = [insert camera IP] (and this is the camera on the lan that we want to forward this traffic to)
Internal port = 11095 (and the camera is ‘listening’ for this forwarded traffic on its own port of 11095)
Good luck
P.S. According to Teltonika there are later firmware versions for the RUT240. I’m assuming they’re also applicable to USA models but may be worth checking first.