mvBlueGEMINI Technical Manual (EN) v2.6
APPENDIX 28
11.2.2 Terms (simplified description)
• Switch is a simple distributor of network packages in a subnet. Both mDNS packages as well
as packages directly on another computer are permitted.
• Router separates subnets, i.e. a router can forward queries from one subnet to another subnet.
NAT is generally used, i.e. the router replaces the querying IP address with its own. This means
that external access to the computer behind the router is not possible. mDNS broadcasts are
also not transmitted.
• Firewall behaves in a similar manner to a router, but it also filters the content of the network
packages.
11.2.3 Server and client not separated by a firewall
11.2.3.1 Server and client live in the same subnet (e.g. DHCP or fixed IP)
The server now has the problem of having to find the IP address. The possible solutions are:
• In the case of DHCP, the IP address can be read out in the DHCP server, but requires read
rights to the DHCP server.
• Start the delivered script and display an overview of the smart camera. Select a smart camera
and access its URL via web browser.
• Start a local instance of the mvIMPACT-CS server (offline version) and connect with "localhost"
via web browser. Then select the desired smart camera in the browser.
• Call up a central but local instance in the intranet. This is where a small web server is running,
which identifies all smart cameras in the local network via Avahi and makes them available for
selection.
11.2.3.2 Server uses a Zero-Conf address and a fixed IP in an external subnet
The client then also has to use a Zero-Conf address (set "dynamic IP address" under Windows with
no DHCP server in the network). This can be achieved by connecting the camera directly to the
client PC. The second or third solution from "Server and client live in the same subnet (e.g. DHCP
or fixed IP)" can then be used.
To Next Page
Loading...
