Use the Interface Binding step of the Edit <Service> wizard to bind the service you plan to create to specific network interfaces. Interface binding can be useful if you want to separate traffic for security reasons. For example, if your organization uses a gateway to separate the internal network (LAN) from external networks (WANs), you can bind the service to an interface that separates the service traffic from other traffic. Binding the service to a WAN, which covers a large geographic area that includes the internet, ensures that the service’s traffic is separated from that of the LAN, which usually covers your organization’s internal network.
Note: Before you can bind the service to network interfaces on the host, ensure that you have properly set up the interfaces on the host. If you do not, you will not be able to bind the service to the interfaces.
To bind your service to network interfaces, specify the following:
All Interface Binding: Select this checkbox to bind the service to all network interfaces. Deselect it if you want to choose either WAN or LAN for binding.
WAN: Select this to bind the service to the WAN.
LAN: Select this to bind the service to the LAN.
NETWORK INTERFACES
This section displays the following information about the network interfaces configured on the host:
HOST NAME: the host’s name as provided
NETWORK INTERFACE: the network interface used by the service instance
INTERFACE TYPE: the type of the network interface used to bind the service instance
NETWORK LABEL: the provided label for the network
IPv4 ADDRESS: the IPv4 address of the network interface
IPv6 ADDRESS: the IPv6 address of the network interface
Ensure that all required information is provided, and click Next to proceed to the next step. If any required information is left empty, an error icon will appear next to the page. To complete missing information, click Back. To exit without saving the configuration, click Cancel. If you have completed all edits and configuration, click Finish.