• Local Port(s): The port number(s) that corresponds to the service (Web server, FTP, etc.) on a local computer or device. For
example, you might input “80” in the Local Port(s) field to open a port for a Web server on a computer within your network.
The Internet Port(s) field could then also be 80, or you could choose another port number that will be used across the
Internet to access your Web server. If you choose a number other than 80 for the Internet Port, connections to that number
will be mapped to 80—and therefore the Web server—within your network.
• Protocol: Select from the following options in the dropdown menu:
o TCP
o UDP
o TCP & UDP
• Click Submit to save your completed port forwarding rule.
6.4.2 Network Prefix Translation (Advanced)
Network Prefix Translation is used in IPv6 networks to translate one IPv6 prefix to another. IPv6 prefix translation is an experimental
specification (RFC 6296) trying to achieve address independence similar to NAT in IPv4. Unlike NAT, however, NPT is stateless and
preserves the IPv6 principle that each device has a routable public address. However, it still breaks any protocol embedding IPv6
addresses (e.g. IPsec) and is generally not recommended for use by the IETF. NPT can help to keep internal network ranges
consistent across various IPv6 providers, but it cannot be used effectively in all situations.
The primary purpose for Cradlepoint’s NPT implementation is for failover/failback and load balancing setups. LAN clients can
potentially retain the original IPv6 lease information and may experience a more seamless transition when WAN connectivity
changes than if not utilizing NPT.
Mode:
• None – No translation is
performed
• Load Balance Only –
(Default) Only translate
networks when actively load
balancing
• First – Use the first IPv6 prefix found
To Next Page
Loading...
