Release Note Microsite White Papers Cloud License

Configuring Firewall

This section describes the various firewall configuration options and capabilities of the EnGenius Security Gateway. You can access this page from Configure > Gateway > Firewall

Outbound rules

Here you can configure permit or deny Access Control List (ACL) statements to determine what traffic is allowed between VLANs or out from the LAN to the Internet. These ACL statements can be based on protocol, source IP address and port, and destination IP address and port. These rules do not apply to VPN traffic. To configure firewall rules that affect traffic between VPN peers, please refer to Site-to-site VPN Settings

Click Add a rule to add a new outbound firewall rule.

  • The Protocol field allows you to specify TCP traffic, UDP traffic, ICMP traffic, or Any.

  • The Policy field determines whether the ACL statement permits or blocks traffic that matches the criteria specified in the statement.

  • The Src.IP and Dest.IP fields support IPs or CIDR subnets. Multiple IPs or subnets can be entered comma-separated.

  • The Src. Port and Dest.Port fields support port numbers. Multiple ports can be entered comma-separated. You can enter additional information in the Description field

  • Apply to all ESG in the org: It is used when you want to have the same firewall rules in all gateways in one organization. so the outbound rules will be replicated to all EnGenius Gateway in the same Organization.

Export CSV

This allows you to generate a documented record of your outbound firewall rules in a CSV format. This documentation serves various purposes, including backup, future reference, and troubleshooting.

You can click on the Export button located at the top right corner to export current Outbound rules in a CSV format.

Port Forwarding

Use this option to forward traffic destined for the WAN IP of the EnGenius Gateway on a specific port to any IP address within a local subnet or VLAN. Click Add rule to create a new port forward. You need to provide the following:

  • Protocol: TCP or UDP.

  • Public IP: Listen on the Public IP of WAN 1, WAN 2, or WAN1 & WAN2.

  • Public port: Destination port of the traffic that is arriving on the WAN.

  • LAN IP: Local IP address to which traffic will be forwarded.

  • Local port: Destination port of the forwarded traffic that will be sent from the EnGenius Gateway to the specified host on the LAN. If you simply wish to forward the traffic without translating the port, this should be the same as the Public port.

  • Allowed remote IPs: Remote IP addresses or ranges that are permitted to access the internal resource via this port forwarding rule.

  • Description: A description of the rule.

Export CSV

This allows you to generate a documented record of your port forwarding rules in a CSV format. This documentation serves various purposes, including backup, future reference, and troubleshooting.

You can click on the Export button located at the top right corner to export current Port forwarding rules in a CSV format.

1:1 NAT

Use this option to map an IP address on the WAN side of the EnGenius gateway (other than the WAN IP of the EnGenius Gateway itself) to a local IP address on your network. Click Add a 1:1 NAT mapping to create a new mapping. You need to provide the following:

  • Uplink: The physical WAN interface on which the traffic will arrive.

  • Public IP: The inbound destination public IP address that will be matched to access the internal resource from the WAN.

  • LAN IP: The IP address of the server or device that hosts the internal resource that you wish to make available on the WAN.

  • Rules: You can add rules to specify the matching conditions that only incoming connections matching the following conditions are accepted for 1:1 NAT service to access internal LAN resources.

  • Allowed Remote IPs: Enter the source IP addresses/ranges that will be matched. You can specify multiple WAN IP addresses/ranges separated by commas.

  • Protocol: Choose from TCP, UDP, ICMP, or any.

  • Public Ports: Enter the destination port that will be matched. You can specify multiple ports separated by commas.

Creating a 1:1 NAT rule does not automatically allow inbound traffic to the public IP listed in the 1:1 NAT mapping. By default, all inbound connections are denied. You have to configure matching Rules as described above in order to allow the inbound 1:1 NAT traffic.

Allowed Services

This allows you to configure the allowed services to access EnGenius Gateway

  • ICMP Ping: Use this setting to allow the EnGenius Gateway to reply to inbound ICMP ping requests coming from the specified address(es). Supported values for the remote IP address field include None, Any, or a specific IP range (using CIDR notation). You can also enter multiple IP ranges separated by commas.

  • Web (local status & configuration): Use this setting to allow or disable access to the local management page via the WAN IP of the EnGenius Gateway. Supported values for the remote IPs field are the same as for ICMP Ping.

Last updated