Well i have run into this problem and netplan did not solve the case. So what i did i assigned the ip address on the interface;
Adjust according to your interface
sudo ip addr add 192.168.99.202/24 dev ens18
That assigns the ip address to the interface. Then state the interface status;
for our case we are setting it to up.
**ip link set dev ens18 up**
ip link set dev ens18 down
now to verify our ip address on the interface;
sudo ip address show dev ens18
configure a default gateway
sudo ip route add default via 192.168.99.2
To verify your default gateway configuration
sudo ip route show
If you require DNS for your network configuration, you can add DNS server IP addresses in the file /etc/resolv.conf .
nameserver 8.8.8.8
nameserver 8.8.4.4
If you no longer need this configuration and wish to purge all IP configuration from an interface, you can use the ip command with the flush option as shown below. Though this does not flush the nameservers. You have to go to the file /etc/resolv.conf
@KagwaiMaina
Netplan is the way to configure the network now on Ubuntu. Using it properly will ensure your configuration will survive a reboot of the server. Your proposition can be used temporarily to test a new config but will not survive a reboot.
i agree it but it was the only thing that could work. It did prove futile later since i couldn’t poll public IPs i dont know if it was a result of that. i just shelved that until i have a better understanding of librenms. I ran into the same with Librenms Centos 7 image. I am starting to think it could be a network issue on my end.