Technical Frequently Asked Questions: Terms and Definitions

Reverse NAT refers to Port forward/DMZ host support.

The item list in 'About' is derived directly from our build configuration, hence are supported in the version you are using.

The list of 'Services' was shortened due to user interface constraints.
Services are name definitions for well-known protocols/ports, and they are used when defining firewall rules. ALGs are not related to the Services list.
They are triggered automatically on well-known application ports, and are not controlled by the user in any way.

OpenSMB 4.0 is using CSR version 1.4, and DSR version 2.6.

Up to OpenRG version 4.1, the NAT table was defined during compilation time. In OpenRG version 4.0 it was 5000 entries, in older versions it was 1000.
From OpenRG version 4.1, the maximum connections number is allowed to increase dynamically:

• A quota of 1000 connections is reserved by default (that number is configurable at compilation).
• Above 1000 connections, connections are allowed to be created until the amount of free memory falls below 1.2MB (also configurable).
  Subsequent connections will be denied.
• Each NAT entry takes about 160 bytes of RAM.

When OpenRG's NAT table is full, the policy is to deny the new connection.

Assuming that you know how to identify the different groups, it will not be difficult to implement this behavior.

OpenRG will support SSH protocol from version 4.2.
The usage is by executing the following:
and then providing the password.

In the Web-based Management (WBM), select the 'Security' section (on the left sidebar) and add a new entry in the 'Port Forwarding' tab.
Another option is to use the 'DMZ Host' tab to forward all the packets from the WAN to a specific IP on the LAN. You can find full documentation on the usage in our 'User Manual'.

In order to view the NAT table association, perform the following: In OpenRG's Command Line Interface (CLI) type 'shell'