• Version
  • Language
  • Product
  • Knowledge base
  • Camera
  • Motion
  • Zivid.com ↗
  • Downloads ↗
  • Webshop ↗
Logo

Getting Started

  • User Guide
  • Software Installation
    • Install Zivid on Windows
    • Install Zivid on Ubuntu
    • Install Zivid on Jetson Linux
    • Network Configuration
      • Default configuration
      • Custom configuration
        • Static IP
        • Dynamic IP (DHCP or link-local)
          • DHCP Network Configuration
          • Link Local Network Configuration
            • Camera
            • PC
      • Connecting to the camera
      • Performance
      • Restricting discoverable cameras
    • About GPU
  • Studio Guide
  • Quick Capture Tutorial

Academy

  • Camera
  • Applications

Software

  • Integrations
  • Samples
  • Docker
  • API Reference
  • Capture Speed
  • Supporting Reference

Reference Articles

  • Camera Settings
  • Calculators
  • Hardware
  • General Camera Topics
  • General 3D Topics

Support

  • FAQ
  • Troubleshooting
  • Erratas
  • Contact Us
  • KB Version History
ZIVID KNOWLEDGE BASE
  • Zivid Camera
  • User Guide
  • Software Installation
  • Network Configuration
  • Link Local Network Configuration

  • Link Local Network Configuration
    • Camera
    • PC

Link Local Network Configuration

To configure link-local, set the camera to DHCP mode with no DHCP server active, then connect the camera and configure the PC’s network interface to link-local.

Caution

The correct instructions for network configuration will depend on your SDK version. Choose your SDK version in the top left drop-down.

  • Camera

  • PC

Camera

The camera automatically falls back to a link-local IP address when no DHCP server responds, so set the camera to DHCP mode using Zivid Studio, the CLI Tool, or the API.

Zivid Studio

Open Zivid Studio and click Cameras → All Cameras to open the camera menu.

../../../../_images/studio-cameras-menu.png

Click Configure on the camera that you want to configure.

../../../../_images/studio-cameras-configure-dhcp.png

Select the automatic (DHCP) configuration mode. Click Apply to apply the configuration to the camera.

../../../../_images/studio-cameras-configure-dhcp-applying.png
CLI Tool

You can use the CLI tool ZividNetworkCameraConfigurator to change the camera network configuration of one camera at a time. This tool is installed alongside the Zivid SDK on Windows, and with the Zivid Tools package on Ubuntu.

  1. Open a terminal/Command Prompt.

  2. Connect the camera.

  3. Verify that your camera is found by running:

    Windows
    ZividListCameras.exe
    
    Ubuntu
    ZividListCameras
    
  4. Set the camera with current IP <host> in DHCP mode by:

    Windows
    ZividNetworkCameraConfigurator.exe set-config <host> --dhcp
    

    For example, changing the mode from static to DHCP for a camera with IP 172.28.60.5:

    ZividNetworkCameraConfigurator.exe set-config 172.28.60.5 --dhcp
    
    Ubuntu
    ZividNetworkCameraConfigurator set-config <host> --dhcp
    

    For example, changing the mode from static to DHCP for a camera with IP 172.28.60.5:

    ZividNetworkCameraConfigurator set-config 172.28.60.5 --dhcp
    

    You can also set a hostname by using the optional argument [--hostname <hostname>]. All ethernet-based Zivid cameras come with a pre-defined hostname with the following format zivid-serialnumber, e.g., zivid-2234AB12.

API

The SDK provides the functions to configure the camera network configuration.

  1. Connect to your camera.

    Go to source

    source

    auto camera = zivid.connectCamera();
    
    Go to source

    source

    var camera = zivid.ConnectCamera();
    
    Go to source

    source

    camera = app.connect_camera()
    
  2. Set the mode to DHCP.

    Go to source

    source

    mode = Zivid::NetworkConfiguration::IPV4::Mode::dhcp;
    
    Go to source

    source

    mode = Zivid.NET.NetworkConfiguration.IPV4Group.ModeOption.Dhcp;
    
    Go to source

    source

    mode = zivid.NetworkConfiguration.IPV4.Mode.dhcp
    
  3. Create a network configuration object.

    Go to source

    source

    Zivid::NetworkConfiguration newConfig(Zivid::NetworkConfiguration::IPV4(mode, address, subnetMask));
    
    Go to source

    source

    var newConfig = new Zivid.NET.NetworkConfiguration()
    {
        IPV4 = {
            Mode = mode,
            Address = address,
            SubnetMask = subnetMask,
        }
    };
    
    Go to source

    source

    new_config = zivid.NetworkConfiguration(
        ipv4=zivid.NetworkConfiguration.IPV4(
            mode=mode,
            address=address,
            subnet_mask=subnet_mask,
        )
    )
    
  4. Apply the new network configuration to the camera.

    Go to source

    source

    camera.applyNetworkConfiguration(newConfig);
    
    Go to source

    source

    camera.ApplyNetworkConfiguration(newConfig);
    
    Go to source

    source

    camera.apply_network_configuration(new_config)
    
  1. Make sure a DHCP server is not active on the network.

  2. Connect your camera(s), and then wait more than 45 seconds.

PC

This guides you through how to configure the network interface that interfaces your camera to link-local, on Windows or Ubuntu.

Windows
  1. Identify the network interface name.

    netsh interface ip show config
    Configuration for interface "Ethernet 2"
       DHCP enabled:                         Yes
       InterfaceMetric:                      5
       DNS servers configured through DHCP:  None
       Register with which suffix:           Primary only
       WINS servers configured through DHCP: None
    
    Configuration for interface "WiFi"
       DHCP enabled:                         Yes
       IP Address:                           192.168.0.4
       Subnet Prefix:                        192.168.0.0/24 (mask 255.255.255.0)
       Default Gateway:                      192.168.0.1
       Gateway Metric:                       0
       InterfaceMetric:                      35
       DNS servers configured through DHCP:  192.168.0.1
       Register with which suffix:           Primary only
       WINS servers configured through DHCP: None
    
  2. Obtain link-local IP address.

    Windows has an Automatic Private IP Addressing (APIPA) feature. This feature is enabled by default, and includes an implementation of NetBIOS Naming Service (WINS). To trigger this feature the network interface must be configured for DHCP.

    netsh interface ip set address "<name>" dhcp
    

    In this example it is:

    netsh interface ip set address "Ethernet 2" dhcp
    

    Then make sure that you release any assigned IP addresses, just in case a DHCP server was available at one point.

    ipconfig /release
    
  3. Once the network settings are configured, connect the camera and wait more than 45 seconds. Then check if a link-local IP address has been assigned.

    netsh interface ipv4 show ipaddresses "<name>"
    

    In this example it is:

    netsh interface ipv4 show ipaddresses "Ethernet 2"
    
    Address 169.254.208.207 Parameters
    ---------------------------------------------------------
    Interface Luid     : Ethernet 2
    
Ubuntu
  1. Identify the network interface name.

    ip addr
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
       link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
       inet 127.0.0.1/8 scope host lo
          valid_lft forever preferred_lft forever
       inet6 ::1/128 scope host
          valid_lft forever preferred_lft forever
    2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
       link/ether e8:6a:64:d3:52:51 brd ff:ff:ff:ff:ff:ff
       altname enp0s31f6
    3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
       link/ether 98:2c:bc:af:a5:19 brd ff:ff:ff:ff:ff:ff
       inet 192.168.2.165/20 brd 192.168.15.255 scope global dynamic noprefixroute wlp2s0
          valid_lft 85346sec preferred_lft 85346sec
       inet6 fe80::e2b2:f4ff:e2f:b629/64 scope link noprefixroute
          valid_lft forever preferred_lft forever
    
  2. Obtain link-local IP address.

    It is possible to configure Link-Local via netplan. First we verify existing configurations.

    ls /etc/netplan/
    01-network-manager-all.yaml
    

    In our case we add a new configuration for our interface.

    sudo nano /etc/netplan/99_config.yaml
    
    network:
    version: 2
    renderer: networkd
    ethernets:
       eno1:
          link-local: [ipv4]
    
    sudo netplan apply
    
  3. Once the network settings are configured, connect the camera and wait more than 45 seconds. Then check if a link-local IP address has been assigned.

    ip addr
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
       link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
       inet 127.0.0.1/8 scope host lo
          valid_lft forever preferred_lft forever
       inet6 ::1/128 scope host
          valid_lft forever preferred_lft forever
    2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
       link/ether e8:6a:64:d3:52:51 brd ff:ff:ff:ff:ff:ff
       altname enp0s31f6
       inet 169.254.242.125/16 brd 169.254.255.255 scope link eno1
          valid_lft forever preferred_lft forever
    3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
       link/ether 98:2c:bc:af:a5:19 brd ff:ff:ff:ff:ff:ff
       inet 192.168.2.165/20 brd 192.168.15.255 scope global dynamic noprefixroute wlp2s0
          valid_lft 80799sec preferred_lft 80799sec
       inet6 fe80::e2b2:f4ff:e2f:b629/64 scope link noprefixroute
          valid_lft forever preferred_lft forever
    

Next Steps

You have now configured the camera and PC to link-local. Go to Connecting to the camera.

Previous Next

© Copyright 2015-2026 Zivid AS, last updated: 14 Sep 2026, 15:36 CET.

Built with Sphinx using a theme provided by Read the Docs.

Links

  • Knowledge base
  • Products
  • Downloads
  • Webshop

Follow Us

  • Twitter
  • Facebook
  • LinkedIn
  • YouTube

Contact us

  • Zivid.com
  • Gjerdrums vei 10A
  • NO0484 Oslo, Norway
  • +47 21 02 24 72