Matrix Vision mvBlueGEMINI, Техническое руководство

Страница: 37 / 52

mvBlueGEMINI Technical Manual (EN) v 1.2.2
APPENDIX - NOTES ON NETWORK CONNECTIONS
36
Error Cause Action
10.3 Notes on network connections
10.3.1 Background information
The user would like to connect to the smart camera with their client via web browser. For this to
work,
1. the smart camera's IP address or host name must be known or found, and
2. a data packet route to this IP address or host name must exist.
Point 2 is relatively simple, as only a single route has to exist between the client and the server.
Routers (and routing tables) as well as port forwarding are available for this purpose. However, for
point 1, conveniently locating the smart camera, the mDNS broadcasts must be available, which is
normally suppressed by routers. The server essentially publishes its settings via Avahi and mDNS.
The client can initially use the host name printed on the smart camera.
Different problems need to be overcome with different solutions depending on the network
topology. These are discussed below.
10.3.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.
10.3.3 Server and client not separated by a firewall
10.3.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.