Internal Scanner Static IP Configuration – CODA Intelligence Partner Portal

Footprint Internal scanner uses cloud-init to get it’s IP address configuration.
Reference: https://netplan.io/examples

Option 1: Using Automated Tool (coda-toolkit)

Steps:

Run coda-toolkit --set-ip-config

cd /var/coda
./coda-toolkit --set-ip-config

Choose Static IP option and press ENTER

Enter the static IP
Enter the subnet mask (e.g. for a /24 you would enter only 24)
Enter the IP of the name server
Enter the IP for the gateway
Press y if you want to apply the changes

When using SSH connection, be aware that reloading the networking configuration may cause the connection to disconnect temporarily. After making changes to the network settings,
you'll need to reconnect to the internal scanner using the newly assigned IP address.

Option 2: Manual Editing of Netplan Configuration

The Footprint Internal Scanner appliance uses the: /etc/netplan/60-coda-init.yaml file.
To set the static IP you need to edit it.

Steps:

Edit the /etc/netplan/60-coda-init.yaml file. You can use vi editor or nano editor.

# vi
# to edit in vi you need to press INSERT Key or CTRL + i
# 
sudo vi /etc/netplan/60-cloud-init.yaml

# nano
sudo nano /etc/netplan/60-cloud-init.yaml

Change the existing config to the following structure:

network:
  version: 2
  ethernets:
    eth0:
      addresses:
        - 192.168.159.166/24
      nameservers:
        addresses: [192.168.159.1, 8.8.8.8]
      routes:
        - to: default
          via: 192.168.159.1

If you are using vi save the file by pressing ESC Key + :wq.

Pay attention to using only spaces as indentation, NOT tabs.

Try the new configuration after you have edited the file
```
sudo netplan try
```
Apply the new configuration
```
sudo netplan apply
```

In order to check the current netplan configuration you can run:

sudo netplan get

Default configuration should be using DHCP, if you would like to revert to DHCP then this is the file structure:

network:
  version: 2
  ethernets:
    eth0:
      dhcp4: true

Note: YAML is strict about indentation so if needed you may validate your file using this link: https://yamlchecker.com/

Netplan's configuration files use the YAML format. All /{lib,etc,run}/netplan/*.yaml are considered. Lexicographically later files (regardless of in which directory they are) amend (new mapping keys) or override (same mapping keys) previous ones. A file in /run/netplan completely shadows a file with same name in /etc/netplan, and a file in either of those directories shadows a file with the same name in /lib/netplan.

Option 1: Using Automated Tool (coda-toolkit)

Steps:

Option 2: Manual Editing of Netplan Configuration

Steps:

Related articles