Multiple Public Interface Support (Windows Embedded CE 6.0)
1/6/2010
Internet connection sharing supports multiple interfaces. For example, when the same protocol and port is used for port mapping public address A to private address B, and port mapping public address C to private address D, simultaneous traffic can occur.
On a local system, a virtual connection (VC) is an endpoint (or association) that can host a single call between a client, call manager or MCM driver, and a miniport driver. On the network, a VC refers to a connection between two communicating endpoints, such as two connection-oriented clients.
Many VCs can be active on a NIC at the same time, allowing the NIC to simultaneously service many calls. Each connection can be to different endpoints on different computers. A permanent VC (PVC) is a VC that is manually created and eventually deleted by an operator using a configuration utility that is not supplied in NDIS.
Some DSL carriers require support for multiple asynchronous transfer mode (ATM) permanent virtual connections (PVCs) on the WAN. Because ATM is not supported in Windows Embedded CE, each PVC appears as a separate network interface with a unique IP address. For each PVC, Windows Embedded CE performs standard network configuration, such as port mapping.
The following list shows how Windows Embedded CE supports multiple public interfaces.
- NAT supports configuration of port mappings on multiple public interfaces.
- The DNS proxy can handle multiple DNS servers that resolve addresses on multiple public interfaces.
- The UPnP Internet Gateway Device (IGD) implementation does not support multiple public interfaces. It creates port mappings only on one primary public interface.
- The Internal exposed host setting functions only for the primary public interface.