Tag: IP Address

Categories
Knowledge Support Cloudvue Cloudvue Gateway Support Categories Products

Configuring IP Addresses on a Cloudvue Gateway

Description 

This article describes how to set IP addresses as either static or DHCP for a Cloudvue Gateways onboard NICs.

Product 

  • Cloudvue Gateway

Prerequisites

  • Port #1 “NET” is connected to a network with internet access
  • The Cloudvue Gateway has be registered

Solutions

NOTE: Network Settings can only be viewed, not changed from cloudvue.com

Local Cloudvue

  • Open a web browser from a machine connected to the same network as the Cloudvue Gateway
  • Go to the LAN IP address of the Cloudvue Gateway for example http://192.168.1.180
    • Note: See Knowledge Base Article #15509 “Finding Cloudvue Gateway IP Addresses” for more details about finding IP Addresses
  • Login to the Local Cloudvue instance 
  • From the Navigation bar select Live
  • Expand Video Devices
  • Select the Cloudvue Gateway
  • From the Navigation bar select Settings
  • Select the Settings tab
  • Under Network Settings
    • PORT 1 “LAN”
      • This is the NIC labeled “NET” on the gateway and should be connected to the customers local area network
      • It can be configured to either obtain an IP address dynamically “DHCP” or be assigned a Static IP
      • DHCP (Default)
        • Tick DHCP
      • STATIC
        • Tick Static
        • Enter the desired IP address
        • Enter a Subnet Mask
        • Enter the IP address for DNS Server 1
        • Enter the IP address for DNS Server 2
      • Save the Changes
    • PORT 2  “Cameras”
      • This NIC is labeled POE on the gateway and should be connected to the Camera Network
      • It is intended to function as a DHCP server and assign a dynamic IP address to connected cameras
      • However, you can choose to set to static and manually IP connected cameras
      • DHCP Server (Default)
        • Tick DHCP Server
      • Static
        • To change the networking number scheme from the default 192.168.20.1
        • Enter a new IP address
        • Enter a Subnet Mask
      • NOTE: After changing PORT 2, all devices plugged into this port will need to be rebooted.
    • Once satisfied click SAVE to apply changes

Command Line

  • The overall process is
  • Establish an SSH connection to the Cloudvue Gateway
    • Enter your machines sudo password
    • Enter the smartvue SSH password  found in the SSH Section for the device in Cloudvue Manager.
  • Using either nano or vi edit the file /etc/network/interfaces
  • Make the desired changes to any NIC to set for either static or dhcp
  • Save the changes and exit the editor
  • Down and up the NICs which were changed to apply the changes or alternatively restart the Gateway

In this example both NICs em2 (LAN) and em1 (Cameras) are being set to a static IP address

Additional /etc/network/interfaces Examples

In this example NIC em2 (LAN) is set to static and em1 (Cameras) is set to DHCP

In this example NIC em2 (LAN) is set to DHCP and em1 (Cameras) is set to Static

Categories
Knowledge Support Support exacqVision Server Categories

How multiple adapters on the same network are expected to behave

Summary

If you configure a Windows-based computer that has more than one network adapter on the same physical network and protocol subnet, you may experience unexpected results. This article describes the expected behavior of this kind of nonstandard configuration. 

More Information

Consider the following scenario:

  • You have a working computer that has Windows installed.
  • Two network adapters are connected to the same physical network or hub.
  • TCP/IP is installed as the network protocol.
  • The adapter addresses on the same subnet are 192.168.0.1 and 192.168.0.2.
  • A client on the network uses the address 192.168.0.119.

In this scenario, you may expect the two adapters on the same physical network and protocol subnet to perform load balancing. However, by definition, only one adapter may communicate on the network at a time in the Ethernet network topology. Therefore, both adapters cannot be transmitting at the same time and must wait if another device on the network is transmitting. Additionally, broadcast messages must be handled by each adapter because both are listening on the same network. This configuration requires significant overhead, excluding any protocol-related issues. This configuration does not offer a good method for providing a redundant network adapter for the same network. 

Note Windows Server 2012 includes a new feature call SMB Multichannel. SMB Multichannel is part of the SMB 3.0 protocol and lets servers use multiple network connections at the same time. For more information about SMB Multichannel, visit The basics of SMB Multichannel, a feature of Windows Server 2012 and SMB 3.0.

Note Windows Server 2012 servers cannot use multiple network connections at the same time if the network is configured by using CSMA/CD.

Assume that the server has to send a packet by using the TCP/IP protocol to a client whose address is 192.168.0.119. This address is located on the local subnet. Therefore, a gateway does not have to be used to reach the client. The protocol stack uses the first route that it finds in the local routing table. Typically, this is the first adapter that was installed. In this case, that adapter is 192.168.0.1. If the transmission fails, later retries may use the same adapter according to the entry that is found in the routing table. 

If the network cable for the 192.168.0.1 adapter fails, this does not necessarily cause the route to be removed from the routing table. Therefore, the second adapter still may not be used. 

Another thing to consider is that some network applications bind to specific adapters in the system. If a network application were to bind to the second adapter specifically, application-related traffic that was received from clients on the first adapter might be ignored by the application. This might be caused by NetBIOS name registration on the network. Additionally, if the adapter to which the application is bound fails, the application may fail if it does not use the other adapter.  

Usually, unless applications specifically demand it, this kind of configuration is not helpful. Some manufacturers make fault-tolerant network adapters to guard against a single point of failure. These adapters enable two adapters to be included on the same server but enable only one adapter to be used at a time. If the primary adapter fails, the driver deactivates the first card and enables the second by using the same address configuration. The result is a fairly seamless transition to the alternative adapter. This is the preferred method to guard against a single network adapter as a single point of failure.

Microsoft article link

https://support.microsoft.com/en-us/topic/how-multiple-adapters-on-the-same-network-are-expected-to-behave-e21cb201-2ae1-462a-1f47-1f2307a4d47a

Categories
Knowledge Support Support exacqVision Client Categories Products

Why do I see the 127.0.0.1 IP address in my Add Systems list?

Modern computer networks require each device on the network to have a unique IP address. These addresses are used so that computers know how to communicate with each other and so that network equipment knows where to route the traffic crossing its path.

When using the ExacqVision Desktop Client application from a client workstation to connect to your ExacqVision Server application on another machine, perhaps on the other side of your office, you will need to enter the server’s IP address so the two machines can communicate.

However, TCP/IP includes some “shortcuts” that make routing communication more efficient when two applications running on the same machine need to communicate. These “shortcuts” are called loopback addresses and tell the machine not to bother sending the message out onto the network only to have the network send it right back.

127.0.0.1 is an IP address that always refers to “this machine”; the local computer. An ExacqVision Client can always connect to a server running on the same computer using the 127.0.0.1 IP address, regardless of the actual IP address being used by the NIC in the computer. The same can be said for “localhost,” which may be used in place of the address 127.0.0.1 in many applications. Both “localhost” and the address 127.0.0.1 refer to “this machine.”

Do not delete 127.0.0.1 or ‘localhost’ from your systems list. Using 127.0.0.1 instead of the actual IP address of the NIC ensures the fastest and least troublesome connection to the ExacqVision Server running on the same computer.

<br>

The 127.0.0.1 loopback address is an IPv4 address. While IPv6 has been a growing protocol for several years, it is still primarily used by service providers and external routing. Within private networks such as offices and homes, the older IPv4 protocol is still standard.

In case you’re wondering, the loopback address in IPv6 can be written as:
0:0:0:0:0:0:0:1 or as ::1

At the time of this writing, ExacqVision Server does not support IPv6 addressing.
<br>