• Version
  • Language
  • Knowledge base
  • Products
  • Downloads
  • Webshop
  • Zivid.com
Logo

Getting Started

  • User Guide
  • Software Installation
    • Network Configuration
      • Default configuration
      • Custom configuration
        • Static IP Network Configuration - Camera
        • Static IP Network Configuration - PC
        • DHCP or Link Local IP Network Configuration - Camera
        • Link Local IP Network Configuration - PC
        • DHCP Network Configuration - PC
      • Connecting to the camera
      • Performance
      • Cameras.yml and how to restrict discoverable cameras
      • Version History
    • About GPU
  • Studio Guide
  • Quick Capture Tutorial

Academy

  • Camera
  • Applications

Software

  • Wrappers
  • Samples
  • Docker
  • API Reference
  • Capture Speed
  • SDK Lifecycle
  • SDK Changelog

Reference Articles

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

Support

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

Link Local IP Network Configuration - PC

Caution

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

This guides you through how to set the PC to link-local. Make sure you first have configured the camera to link-local before going onward. Go to DHCP or Link Local IP Network Configuration - Camera in order to do this.

  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
    
    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.

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

    netsh interface ip set address "<name>" dhcp
    

    In this example it would be:

    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
    

    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.

    netsh interface ipv4 show ipaddresses "<name>"
    

    In this example it would be:

    netsh interface ipv4 show ipaddresses "Ethernet 2"
    
    Address 169.254.208.207 Parameters
    ---------------------------------------------------------
    Interface Luid     : Ethernet 2
    
    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
    

Once you have configured the camera and PC to link-local, go back to Connecting to the camera.

Previous Next

© Copyright 2015-2025 Zivid AS, last updated: 02 May 2025, 09:49 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