OxyGEN
mini
Office
Administrator’s Guide
Public IPs
In the majority of installations, each host in the LAN uses a separate private IP address and accesses the
Internet through the automatic transformation by the OxyGEN
mini
Office between the private and one
or more public IP addresses (NAT operation). In some cases, however, it is required to use also public IP
addresses in the LAN (usually for Web servers, FTP servers etc.). In order to realize this, one option is to use
a separate DMZ (DeMilitarized Zone) Interface Group, totally separated from the other LAN hosts (refer
to section
Addresses
on page 71). If it required, however, that the hosts with the public IP addresses
coexist in the same Ethernet segment with the other internal hosts using private IP addresses, a second
available option is to notify the OxyGEN
mini
Office about the existance of public IPs in the LAN. This is
achieved through the
Public IPs
configuration menu. In this configuration page, a subnet of public IP
addresses can be configured for each Interface Group. IP addresses belonging to these subnets will be
routed directly (without NAT), and NAT will only be applied to the private IP addresses.
Figure 7.13: Public IP Addresses
Using the corresponding table entries, for each local LAN Interface Group:
1. Enter the public
IP Address
used for the OxyGEN
mini
Office. This will be used by the device as a
secondary IP and it must be configured on each host in the LAN using a public IP as the default
gateway.
2. Enter the
Netmask
of the public IP subnet.
The value of this parameter together with the
corresponding
IP Address
define the subnet of IPs that will not be treated as public by the OxyGEN
mini
Office and will not be translated via NAT.
3. Select if the subnet of public IPs is going to be protected with firewall or not, using the
Firewalled
checkbox.
4. Check the
Enabled
checkbox in order to activate the relevant operation for the specific Interface
Group.
5. Click
Apply
.
Gennet s.a.
82