Setting Up Plgd Hub and Plgd DPS in a Dynamic IP Environment (DHCP)

1 minute read
Edit on GitHub

In scenarios where IP addresses can change, such as with DHCP, you’ll need to configure plgd hub and plgd dps (Device Provisioning Service) using both a dynamic and a static IP address.

  1. Configuring the System: To accommodate both dynamic and static IP addresses, follow these steps:

  2. Installing and Configuring DNS Server:

    Install a DNS server, such as dnsmasq, to serve domains to MicroK8s. Make this configuration permanent for reboots. Allow the server to listen on

  3. Configuring MicroK8s to Use Custom DNS:

    Configure MicroK8s to utilize the custom DNS server with IP by following the MicroK8s documentation for adding custom DNS as an add-on.

  4. Updating Helm Values for PLGD Services:

    Adjust the Helm values YAML for PLGD services to utilize the domain and the DHCP assigned IP address. Modify the values.yaml with the following settings:

    SOURCE Copy
          externalAddress: <DHCP_IP:PORT>
        coapGateway: coaps+tcp://<DHCP_IP:PORT>
        - id:
              coapGateway: <DHCP_IP:PORT>

    Replace <DHCP_IP:PORT> with the actual DHCP-assigned IP address and port.

  5. Sustaining IP Address Changes:

    After changing the IP address, you only need to update the values.yaml in Helm for the changes to take effect. Then the coap-gateway, resource-directory, and device-provisioning-service pods will be restarted to load configuration.

  6. Accessing the Services:

    Ensure that any laptop attempting to access has the updated /etc/hosts file pointing to the new DHCP-assigned IP address.

Aug 9, 2023

Get started

plgd makes it simpler to build a successful IoT initiative – to create a proof of concept, evaluate, optimize, and scale.

Get Started Illustration Get Started Illustration