Describe the Windows Hardware Discovery Process New Network Card

Case 1: Connecting to I Public and One Individual Network

In this scenario, a host PC is connected to both a corporate network (via NIC #1) which allows internet access too as a private network (via NIC #2) with several LabVIEW Real-Time targets. The corporate network is setup to assign a DHCP address in the range of 10.0.x.x with subnet mask 255.255.0.0 to NIC #one. The default gateway (router) accost is 10.0.0.1.

Figure five. In this scenario, a multi-NIC controller is connected to both a corporate network (with internet access) and a local private network.

Following the guidelines higher up, we tin configure NIC #ii, attached to the private network, with a static IP outside of the 10.0.x.ten subnet range. While it might be acceptable to use an address in the 10.1.x.x range, as information technology is in a different subnet, it is possible that other ten.x.ten.ten IP addresses are used for boosted corporate servers, etc. Therefore, it is safer to use the 192.168.ten.ten range for the individual network.

Since we are working with a small number of LabVIEW Real-Time targets in the private network, we can use a subnet mask of 255.255.255.0 and assign each a static IP address in the range 192.168.0.10; this will permit for up to 255 connected interfaces in the subnet. For simplicity, the IP address of the host computer (NIC #ii) will exist set to 192.168.0.ane.

It is of import to get out the default gateway blank on the NIC #ii settings for the host auto. In this mode, just the NIC #1 default gateway will be used, which is what we desire in order to access the internet from the host. In addition, the default gateway can be left blank on the LabVIEW Real-Time devices, as they should only be communicating within the local subnet (there are no gateways connected).

NIC ane Connected to Corporate Network and Internet	NIC 2 Connected to Local Private Network
IP Address: (DHCP) x.0.ten.x	IP Accost: 192.168.0.i
Subnet Mask: (DHCP) 255.255.0.0	Subnet Mask: 255.255.255.0
Default Gateway: (DHCP) ten.0.0.1	Default Gateway: 0.0.0.0 (unspecified)

Tabular array 3. This table shows one possible IP address configuration for the system shown in Effigy 5 to a higher place. Notice that the two NICs connect to different subnets, and that only one Default Gateway accost is specified.

Instance 2: Configuring an NI Existent-Time Hypervisor System with Virtual Ethernet Connection (local evolution)

NI Real-Time Hypervisor systems run a host OS (Windows or Linux) alongside LabVIEW Real-Time simultaneously. Each concrete NIC in these systems tin can be assigned to either the host OS or LabVIEW Real-Time, and a virtual NIC (emulated in software) is also presented to each Os to simplify inter-Os communication.

Figure 6. In this scenario, a Real-Time Hypervisor controller is running both Windows XP and LabVIEW Existent-Time in parallel. Both OSs are connected to each other through a fix of virtual NICs, and each OS has a physical NIC to connect to the corporate network & net also.

In this scenario nosotros will work with a Existent-Fourth dimension Hypervisor organisation that has two physical NICs, and has the internal Virtual Ethernet connection enabled. One concrete interface volition be assigned to Windows XP, and the other to LabVIEW Real-Fourth dimension. Therefore, each Bone will have access to two NICs (the Virtual Ethernet connection and one physical connection). The Windows XP side of the hypervisor system will be used for LabVIEW Real-Time application development and deployment.

Assume that the concrete connections are used to enable communication to the internet from either Bone via a corporate network. The virtual interface volition be used only for communication betwixt LabVIEW Real-Time and Windows XP. The IP address of both physical adapters connected to the corporate network will be dictated via DHCP, and will be in the range 10.0.0.x with subnet mask 255.255.255.0. The gateway accost is gear up to 10.0.0.1.

Post-obit the guidelines above, nosotros should set a static IP for each of the Virtual Ethernet adapters using a unlike subnet than is used with the concrete adapter on each OS. Although other addresses in the 10.x.x.10 range could exist used, to be conservative we will fix the IP addresses of the Windows XP and LabVIEW Real-Time adapters to 192.168.0.1 and 192.168.0.two respectively. The subnet mask of each is set to 255.255.255.0.

Because we desire both Windows XP and LabVIEW Real-Time to access the internet via the concrete NICs, they should exist the simply adapters that have a default gateway set. Therefore, we will go out the default gateway entry for both Virtual Ethernet NICs empty. Note that each OS ultimately has only one default gateway specified.

LV RT Physical NIC	LV RT Virtual NIC	Win XP Virtual NIC	Win XP Physical NIC
IP Address: (DHCP) 10.0.0.10	IP Address: 192.168.0.ii	IP Address: 192.168.0.1	IP Address: (DHCP) 10.0.0.x
Subnet Mask: (DHCP) 255.255.255.0	Subnet Mask: 255.255.255.0	Subnet Mask: 255.255.255.0	Subnet Mask: (DHCP) 255.255.255.0
Default Gateway: (DHCP) 10.0.0.1	Default Gateway: 0.0.0.0 (unspecified)	Default Gateway: 0.0.0.0 (unspecified)	Default Gateway: (DHCP) 10.0.0.1

Table 4. This table shows one possible IP address configuration for the system shown in Figure 6 above. Since there are two OSs running on a single hypervisor controller in this instance, the important thing to note is that each OS connects to separate subnets with each NIC, and a maximum of ane default gateway.

Case three: Configuring an NI Real-Fourth dimension Hypervisor Organisation with Virtual Ethernet (remote development)

In this scenario, two physical NICs are also used in a Existent-Time Hypervisor system with the Virtual Ethernet connection enabled as in Instance 2 above. However, the physical NIC assigned to LabVIEW Real-Fourth dimension will be used for deployment from a networked host PC rather than for internet access.

Figure vii. In this scenario, the LabVIEW Existent-Time side of an NI Real-Time Hypervisor organization is connected to a remote Windows PC for LabVIEW Real-Time awarding development.

The Windows concrete adapter will nonetheless exist assigned a DHCP accost in the range ten.0.0.x with subnet mask 255.255.255.0. The Virtual Ethernet adapters on Windows XP and LabVIEW Real-Fourth dimension volition once again use static IP addresses of 192.168.0.i and 192.168.0.2 respectively, with subnet masks of 255.255.255.0 and no default gateway.

To ensure that the physical NIC used with LabVIEW Real-Fourth dimension is on a different subnet than the Virtual Ethernet NIC, nosotros can use an IP accost of the form 192.168.1.x with subnet mask 255.255.255.0. Therefore, the remote PC adapter and LabVIEW Existent-Time adapter connected together can use static IP addresses of 192.168.one.1 and 192.168.ane.2 respectively with subnet masks of 255.255.255.0. Once again, no default gateway is needed since neither adapter needs to access an outside network (no gateways are nowadays on this subnet).

Win Host NIC	LV RT Physical NIC	LV RT Virtual NIC	Win XP Virtual NIC	Win XP Physical NIC
IP Address: 192.168.one.1	IP Address: 192.168.ane.ii	IP Address: 192.168.0.2	IP Address: 192.168.0.1	IP Address: (DHCP) 10.0.0.x
Subnet Mask: 255.255.255.0	Subnet Mask: 255.255.255.0	Subnet Mask: 255.255.255.0	Subnet Mask: 255.255.255.0	Subnet Mask: (DHCP) 255.255.255.0
Default Gateway: 0.0.0.0 (unspecified)	Default Gateway: 0.0.0.0 (unspecified)	Default Gateway: 0.0.0.0 (unspecified)	Default Gateway: 0.0.0.0 (unspecified)	Default Gateway: (DHCP) 10.0.0.ane

Table 5. With a remote LabVIEW Real-Time development automobile added to this scenario, IP accost settings must be chosen such that the remote PC can connect with the LabVIEW Real-Fourth dimension side of the hypervisor organization.

Many other configurations are also possible, including using DHCP with the remote development PC and LabVIEW Real-Fourth dimension target (to allow connection with the internet), or using additional NICs in the LabVIEW Existent-Fourth dimension target or remote host computer to connect to the internet.

Case 4: Connecting to Ii Routed Networks (advanced)

One more advanced scenario involves configuring a calculator (running just i OS this time) with two NICs that communicate with two local networks. Each network features a gateway that can be used to relay packets to boosted outside networks.

Effigy viii. In this advanced scenario, a multi-NIC calculator connects to two routed networks. This TCP/IP configuration is more than difficult to ready, peculiarly if the exterior networks are non supersets of the local network subnets.

Imagine that local network A uses IP addresses of the course 10.0.0.ten with subnet mask 255.255.255.0, and local network B uses IP addresses of the form 10.0.1.x with subnet mask 255.255.255.0. Local network A is connected via a gateway to outside network C, which uses IP addresses of the form 192.168.0.x with subnet mask 255.255.255.0. Likewise, local network B is connected to outside network D via a gateway, which uses IP addresses of the class 192.168.1.ten with subnet mask 255.255.255.0.

The goal is for our multi-NIC PC to exist able to access any of the networks. We can connect ane NIC to local network A and assign the IP accost 10.0.0.5 with subnet mask 255.255.255.0, and we tin connect the 2nd NIC to local network B and assign the IP address 10.0.1.5 with subnet mask 255.255.255.0. If any default gateway were assigned, then packets destined for the outside networks may be sent through the wrong gateway, and so this is undesirable.

To solve this problem, we tin can get out the default gateway entries blank for the two NICs and configure bundle routing more than manually in the OS. While all OSs are configured differently, nigh enable the manual addition of routes by the user, and these routes can be configured to persist across reboots of the arrangement. Specifically, we need to add a route with IP accost 192.168.0.x and subnet mask 255.255.255.0 to apply the IP accost of the gateway betwixt networks A and C (eastward.g. ten.0.0.one). The same needs to exist done with IP address 192.168.ane.x and subnet mask 255.255.255.0 for the gateway between networks B and D (e.g. address 10.0.i.ane).

NIC one	NIC two
IP Address: 10.0.0.5	IP Address: 10.0.1.v
Subnet Mask: 255.255.255.0	Subnet Mask:255.255.255.0
Default Gateway: 0.0.0.0 (unspecified)	Default Gateway: 0.0.0.0 (unspecified)
Special Route: Use NIC ane and gateway 10.0.0.one to road to 192.168.0.ten	Special Road: Use NIC 2 and gateway 10.0.1.1 to road to 192.168.1.10

Tabular array vi. While typically only one NIC in a controller volition connect with a gateway (to a corporate network or the internet), more than advanced configurations such as the 1 pictured in Figure 8 above may crave special OS routing entries to part properly.

Additional routes may need to be added equally the number of distinct subnets increases. In practice, about networks are set upwards to avoid the demand for this complex configuration by ensuring that each computer is connected to only one gateway.

Share this post