Security Gateway Manual
SG-3100
The lack of a selected gateway in the interface configuration causes the firewall to treat the interface as a LAN type
interface.
The firewall uses LAN type interfaces as sources of outbound NAT traffic but does not apply outbound NAT on traffic
exiting a LAN. The firewall does not add any extra properties on firewall rules to influence traffic behavior. The DNS
Resolver will accept queries from clients on LAN type interfaces.
See also:
2.6.4 DHCP Server
Next, configure DHCP service for this local interface. This is a convenient and easy way assign addresses for clients
on the interface, but is optional if clients will be statically addressed instead.
• Navigate to
Services > DHCP Server
,
OPTx
tab (Or the custom name)
• Check
Enable
• Configure the
Range
, e.g. from
192.168.2.100
to
192.168.2.199
This sets the lower (
From
) and upper (
To
) bound of automatic addresses assigned to clients.
• The rest can be left at defaults
• Click
Save
See also:
2.6.5 Outbound NAT
For clients on this interface to get to the Internet from private addresses, the firewall must apply Outbound NAT for
the new subnet.
• Navigate to
Firewall > NAT
,
Outbound
tab
• Check the current outbound NAT mode
If the mode is set to
Automatic
or
Hybrid
, then this may not need further configuration. Ensure the new LAN subnet
is listed as a
Source
in the
Automatic Rules
at the bottom of the page. If so, skip ahead to the next section to configure
Firewall Rules.
If the mode is set to
Manual
, create a new rule or set of rules to cover the new subnet.
• Click
to add a new rule at the top of the list
• Configure the rule as follows:
Interface
Choose the WAN interface. If there is more than one WAN interface, add separate rules
for each WAN interface.
Address Family
IPv4
Protocol
Any
Source
Network
, and fill in the new LAN subnet, e.g.
192.168.2.0/24
.
Destination
Any
Translation Address
Interface Address
© Copyright 2022 Rubicon Communications LLC
55
