Inhaltsverzeichnis   MOBOTIX Online-Hilfe


Open the Routing dialog to define the routes to be used by the camera for connecting to different networks. Connections via the Ethernet interface can be used as well as ISDN data connections.

In general, the camera can only send network data using a connection previously configured in the Ethernet Interface and ISDN Data Connections (Dial-In Connection or Dial-Out Connections tabs) dialogs.

Note: Make sure that you create a route for every ISDN dial-out connection; otherwise the camera does not dial out.


A network is defined by the network address and the network mask. For example, by factory default the camera is configured to an IP address within the network (network address/network mask).

Networks are connected through gateways. This may be an ISDN router or a special computer within the network.

In order for each computer within the network to know if and how it can connect to computers in other networks, you need to configure routes. A route consists of the following information:

If a network package is to be sent to a specific target IP address, the camera checks if a route exists for this address. If no specific route exists, or no routes have been defined, the so-called Default Route is used.

The Default Route

Select the connection to be used by default. In general, this is the connection to your Internet Service Provider or to the closest gateway.

If you select the Ethernet Interface connection, you need to enter the IP address of the Gateway. Valid gateway IP addresses need to be accessible within the camera's local network (as defined in the Ethernet Interface dialog).

Note: If you have activated the BOOTP/DHCP option in the Ethernet Interface dialog, the Default Route is always set to the Ethernet Interface with the Gateway IP Address being determined automatically.

If you select an ISDN Dial-Out Connection, the camera accepts the DNS server's IP address proposed by the service provider.

Network Routes

Enter the routes to other networks.

For additional information on the topic, see the Routing - Example help page.

Using the Camera as a Router

Backup Internet Gateway

Note: This functionality is only available if the camera has been configured as DHCP server in the Ethernet Interface dialog.

After activating the Backup Internet Gateway option, the camera can use an additional Internet connection. In case the camera's default Internet connection fails, the local network traffic is re-routed via the additional backup Internet gateway. Enter the IP address of the backup Internet gateway in the Backup Internet Gateway IP field.

To be able to detect the failure of the default Internet connection, you need to enter the Test Server IP. When running, the camera is sending ping signals at regular intervals to the specified IP address. If the camera cannot reach the test server, the camera changes the default route to use the backup Internet gateway.

The IP address of the test server needs to be a publicly accessible IP address that is usually not contacted from the camera network.

Note: It is highly recommended to configure an additional public DNS server in the Ethernet Interface dialog. This DNS server should be accessible via the backup Internet gateway.

IP Forwarding

If the IP Forwarding parameter is activated, the camera acts as a router for other network devices. The camera then routes IP packets between its own network interfaces based on the routing table. This feature only provides the basic forwarding of IP packets without applying any NAT functionalities (Network Address Translation).

NAT for Outbound Traffic

The NAT for Outbound Traffic parameter activates NAT for all outbound packets on the external side of the camera's network interface (WAN - Wide Area Network). These are the network connections of the camera that are established using ISDN, modem PPP, GPRS/2G, UMTS/3G WiFi, etc.

Other network devices connected to the camera on the local network can use the forwarding camera as a default gateway in order to establish their own connections to external IP addresses. The external data traffic of the other network devices is visible on the WAN as if it originated from the camera. (The sender's IP of the packets is rewritten to the IP address of the forwarding camera.) This functionality thus prevents anyone from accessing devices on the local network via the external network interface of the camera.

Note: Since this function always requires IP Forwarding, the camera automatically activates this parameter as soon as you activate the Nat for Outbound Traffic.

NAT for Inbound Traffic

Activating the NAT for Inbound Traffic parameter prompts the camera to forward requests from outside of the local network (external network interface) to cameras within the local network. If you would like to access a camera within the local network, you need to activate this parameter. To access an internal camera, you thus need the external IP address of the forwarding camera or its host name (see dynamic DNS) and a port.

The forwarding camera automatically searches the local network using Zeroconf (Bonjour). Access from the outside is granted automatically for all cameras on the local network that have activated Zeroconf. Access from the outside is handled by NAT and port mapping (using a map of external port numbers to internal IP addresses). If the forwarding camera detects traffic on a specific port on its external (WAN) network interface, it forwards the request to the corresponding camera on the local network.

Note: NAT port mapping is only activated for MOBOTIX cameras. Other network devices are ignored even if they support Zeroconf.

The mapping of external ports to internal IP addresses follows this scheme:

External IP address of forwarding camera:
Internal IP address of a camera on the local network:
You can thus access the internal camera from anywhere in the world using this address:
(If HTTPS has been activated in the Web Server dialog of the internal camera.)

Caution: Make sure that you are only using HTTPS connections when accessing an internal camera. This prevents unwanted eavesdropping on the connection.

Note: Since this function always requires IP Forwarding, the camera automatically activates this parameter as soon as you activate the Nat for Outbound Traffic.

Additional Information

Note: Activate the Enable HTTPS parameter in the Web Server dialog of the internal camera to be able to use HTTPS encryption when accessing the camera.

Note: As soon as you are using one camera as router, you should also configure this camera as DHCP server and the remaining devices on the local network as DHCP clients (see the Ethernet Interface dialog and the BOOTP/DHCP parameter).
In order to get a list of the devices managed by the DHCP server (including their IP addresses, host names and MAC addresses), open the DHCP Leases dialog of the camera that serves as DHCP server.

Note: In order to use Zeroconf (Bonjour), open the Ethernet Interface dialog, activate the Zeroconf parameter and reboot the camera.

Note: You should also consider activating DynDNS on the forwarding camera, so that you can access this camera from the outside using a host name (e.g. instead of an IP address that changes every time the camera establishes an Internet connection. For additional information on this topic, see the Dynamic DNS help page.

Konfiguration sichern

Klicken Sie auf Setzen, um die Einstellungen zu aktivieren und bis zum nächsten Neustart der Kamera zu sichern.

Klicken Sie auf Voreinstellung, um diesen Dialog auf die werkseitigen Voreinstellungen zurückzusetzen (dieser Button wird nicht in allen Dialogen angezeigt).

Klicken Sie auf Wiederherstellen, um alle Änderungen seit dem letzten permanenten Speichern der Konfiguration zu verwerfen.

Beenden Sie den Dialog durch Klick auf Schließen. Hierbei wird geprüft, ob Änderungen der Gesamtkonfiguration vorliegen. Ist dies der Fall, werden Sie gefragt, ob die Gesamtkonfiguration dauerhaft gesichert werden soll.

 Zum Aktivieren der neuen Einstellungen speichern Sie die Konfiguration und führen einen Neustart der Kamera durch!

de, en

© 2001-2024 MOBOTIX AG, Germany ·