Cipafilter Support:
309 517 2022 option 2
Mon - Fri 7 AM - 6 PM CT
Cipafilter Documentation - IP Settings
Posted by Jim Giseburt, Last modified by Jim Giseburt on 06 April 2017 11:53 AM

Each interface has a primary IP address as well as one or more optional secondary IP addresses. An IP address of indicates that the interface is to be left unconfigured. Secondary IP addresses can be assigned to an interface by clicking Add IP near the bottom of each interface section.

IP addresses are specified using CIDR notation, which uses an address/subnet bits format. The subnet bits refer to the number of bits that are set in binary in the subnet mask from the left hand side. For example, a subnet mask of in binary has 8 bits set from the left hand side. So, with a subnet mask of translates to in CIDR notation. See the table in Appendix I for a list of common dot-notation subnet masks and their CIDR-notation equivalents.

Settings like the host name and time zone can also be changed on this page. If you are using the anti-spam features of Cipafilter, make sure that the host name and domain are correct. Ensure that the hostname.domain combination resolves to an IP address on the Cipafilter and that the IP address reverses properly back to hostname.domain. This is important because many mail servers will refuse to trade e-mail with your Cipafilter if this is not done.

Logging Database Connect String

Cipafilter can use a remote filter as a logging database server for the purposes of scaling performance. This value is a PostgreSQL connect string that instructs the filter to log to a remote database server; it should be configured by tech support.

Enterprise Database Connect String

This PostgreSQL connect string describes how the filter connects to the Cipafilter Enterprise monitoring product (if it has been purchased by your organization); it should also be configured by tech support.

Primary and Secondary DNS

Enter external DNS servers here. We recommend leaving these blank to use the Cipafilter's internal DNS server.

Interface Bridging

Clicking this check box will cause the Cipafilter to become a bridge, bridging all of its Ethernet interfaces together into one logical interface. In this configuration the Cipafilter acts like a switch. Installing the Cipafilter this way may require the restarting of any Cisco routers on the subnet to clear their ARP caches. Any IP addresses you wish to configure on Cipafilter for management can be applied to any interface if this box is checked.

Note: The filter should always be rebooted after disabling bridging to allow for the proper re-configuration of network interfaces.

Primary Internet Connection

The interface closest to the Internet should be chosen as your Primary Internet connection. This is used primarily if you enable NAT on any of your other subnets. If a subnet is being NATed, all packets coming from it through the router are translated to appear as if they are coming from the IP you designate with this setting.


NAT is used to allow a group of machines with private IP addresses like or to access the Internet. Packets flowing from any subnet with NAT This Subnet checked will have their source address modified to reflect the IP address of your Primary Internet Connection. Packets coming back to the Primary Internet Connection will then be sorted and passed passed to their real destinations. You only have to enable NAT This Subnet on a single IP from each subnet. For example, if you have five IPs on the subnet, you only need to turn NAT on on any one of them to NAT all traffic from the

(1 vote(s))
Not helpful

Comments (0)
©Cipafilter 2017. All Rights Reserved.