You are here

Planet Ubuntu

Subscribe to Feed Planet Ubuntu
Planet Ubuntu -
Përditësimi: 1 month 3 javë më parë

Stephen Michael Kellat: Social Media Presences Terminated So Far Today

Mar, 24/07/2018 - 3:38pd

Some people have been wondering where I've been online. In conformance to some "employee protection" orders at work, I've had to begin terminating various & sundry bits of online presence. These sorts of orders are such that I do eventually have to obey them.

My Twitter account is gone. I currently have no active presence there.

My Flickr account is gone. I currently have no active presence there.

My account on the Mastodon network via has been gone for some time. If you've been looking for me there that account isn't being restored any time soon.

My account on is as good as gone considering I can't even get a ping response back from that system. After all, this is what I get from attempting a ping:

$ ping PING ( 56(84) bytes of data. ^C --- ping statistics --- 811 packets transmitted, 0 received, 100% packet loss, time 829416ms

My account on Identica is locked in "Hotel California" mode and cannot be terminated by me at this time. That's probably a good thing. The network still exists, ya know.

Additionally, I've been getting tired of seeing things spill over on various social networks about how the current President of the United States (my 11th-line supervisor) is the embodiment of evil walking this planet. It is bad enough spending eight hours per day being paid by the federal government to hear that garbage while protecting the nation's financial interests. Coming home to hear that too is just a step too far. There just comes a point where I can't handle it anymore & have to cut something back.

This blog remains. I'm not going totally dark. Trying to be a light and to spread light is just not as easy as it sounds in this crazy world. Thankfully there is F/LOSS like the many flavours of Ubuntu to at least ensure that I don't have to include computer issues among my many worries right now. Worst comes to worst, you can give me a call on Telegram perhaps if you are so moved.

Simos Xenitellis: Configuring public IP addresses on cloud servers for LXD containers

Hën, 23/07/2018 - 6:30md

You have a cloud server and you got more than one public IP addresses.

How do you get those additional IP addresses to associate to specific LXD containers?

That is, how do you get your LXD container to use a public IP address?

This post has been tested with a baremetal server.


You have configured a cloud server and you arranged to have at least one additional public IP address.

In the following, we assume that

  • the gateway of your cloud server is
  • the unused public IP address is
  • the network is
  • the default network interface on the host is enp0s100 (if you have a bonded interface, the name would be something like bond0)
Creating a macvlan LXD profile

Create a new LXD profile and set up a macvlan interface. The name of the interface in the container will be eth0, the nictype is macvlan and the parent points to the default network interface on the host.

$ lxc profile create macvlan$ lxc profile device add macvlan eth0 nic nictype=macvlan parent=enp0s100

Here is how the profile macvlan looks like.

ubuntu@myserver:~$ lxc profile show macvlan config: {} description: "" devices: eth0: nictype: macvlan parent: enp0s100 type: nic name: macvlan used_by: Launching the container

Launch the container by specifying the macvlan profile on top (stacked) of the default profile. The container is called c1public.

$ lxc launch --profile default --profile macvlan ubuntu:18.04 c1public

Get a shell into the container and view the network interfaces

ubuntu@myserver:~$ lxc exec c1public bash root@c1public:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::216:3eff:fe55:1930 prefixlen 64 scopeid 0x20<link> ether 00:16:3e:55:19:30 txqueuelen 1000 (Ethernet) RX packets 82 bytes 5200 (5.2 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 16 bytes 2788 (2.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 .... root@c1public:~# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 8: eth0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:55:19:30 brd ff:ff:ff:ff:ff:ff link-netnsid 0

At this stage, we can configure manually the appropriate public IP address for the network interface eth0 of the container and it will work. If you are familiar with /etc/network/interfaces, you can go ahead and make the static network configuration. In the next section we are going to see how to use netplan to configure the network.

Configuring the public IP with netplan

In the container, create a file /etc/netplan/50-static-public-ip.yaml so that it as follows. There are two options for the renderer, networkd (systemd-networkd which is available on Ubuntu 18.04) and NetworkManager. We then specify the public IP address, the gateway and finally the DNS server IP addresses. You may want to replace the DNS server with that of your cloud provider.

root@c1public:~# cat /etc/netplan/50-static-public-ip.yaml network: version: 2 renderer: networkd ethernets: eth0: dhcp4: no dhcp6: no addresses: - gateway4: nameservers: addresses: - Applying the netplan network configuration

Run the following command to apply the netplan network configuration. Alternatively, you can restart the container.

root@c1public:~# netplan --debug apply ** (generate:294): DEBUG: 15:46:19.174: Processing input file //etc/netplan/50-cloud-init.yaml.. ** (generate:294): DEBUG: 15:46:19.174: starting new processing pass ** (generate:294): DEBUG: 15:46:19.174: Processing input file //etc/netplan/50-static-public-ip.yaml.. ** (generate:294): DEBUG: 15:46:19.174: starting new processing pass ** (generate:294): DEBUG: 15:46:19.174: eth0: setting default backend to 1 ** (generate:294): DEBUG: 15:46:19.175: Generating output files.. ** (generate:294): DEBUG: 15:46:19.175: NetworkManager: definition eth0 is not for us (backend 1) DEBUG:netplan generated networkd configuration exists, restarting networkd DEBUG:no netplan generated NM configuration exists DEBUG:device lo operstate is unknown, not replugging DEBUG:netplan triggering .link rules for lo DEBUG:device eth0 operstate is up, not replugging DEBUG:netplan triggering .link rules for eth0 root@c1public:~#

Here is the network interface with the new IP address,

root@c1public:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet netmask broadcast inet6 fe80::216:3eff:fe55:1930 prefixlen 64 scopeid 0x20<link> ether 00:16:3e:55:19:30 txqueuelen 1000 (Ethernet) RX packets 489 bytes 30168 (30.1 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 18 bytes 1356 (1.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ... root@c1public:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default _gateway UG 0 0 0 eth0 U 0 0 0 eth0 root@c1public:~# ping -c 3 PING ( 56(84) bytes of data. 64 bytes from ( icmp_seq=1 ttl=53 time=8.10 ms 64 bytes from ( icmp_seq=2 ttl=53 time=8.77 ms 64 bytes from ( icmp_seq=3 ttl=53 time=9.81 ms --- ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 8.106/8.896/9.810/0.701 ms root@c1public:~# Testing the public IP address

Let’s test that the public IP address of the LXD container works. We install nginx and modify a bit the default HTML page.

ubuntu@c1public:~$ sudo apt update ... ubuntu@c1public:~$ sudo apt install nginx ... ubuntu@c1public:~$ cat /var/www/html/index.nginx-debian.html <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> <style> body { width: 35em; margin: 0 auto; font-family: Tahoma, Verdana, Arial, sans-serif; } </style> </head> <body> <h1>Welcome to nginx!</h1> <p>If you see this page, the nginx web server is successfully installed and working. Further configuration is required.</p> <p>For online documentation and support please refer to <a href=""></a>.<br/> Commercial support is available at <a href=""></a>.</p> <p><em>Thank you for using nginx.</em></p> </body> </html> ubuntu@c1public:~$ sudo sed -i 's/to nginx/to nginx running in a LXD container with public IP address/g' /var/www/html/index.nginx-debian.html ubuntu@c1public:~$

Let’s visit the public IP address with our browser!

It worked!

Troubleshooting Help! I can see the IP address but there is no route?!?

Most likely you misconfigured the network prefix in the netplan configuration file. Find the details at

ubuntu@myserver:~$ sudo apt install ipcalc ubuntu@myserver:~$ ipcalc Address: 01100100.01100100.01100100.01100 000 Netmask: = 29 11111111.11111111.11111111.11111 000 Wildcard: 00000000.00000000.00000000.00000 111 => Network: 01100100.01100100.01100100.01100 000 HostMin: 01100100.01100100.01100100.01100 001 HostMax: 01100100.01100100.01100100.01100 110 Broadcast: 01100100.01100100.01100100.01100 111 Hosts/Net: 6 Class A

The public IP addresses have the range 100.100.100.[97-102]. Both the gateway ( and the LXD container public IP address ( are in this range, therefore all are fine.

Simos Xenitellis

Nobuto Murata: Minimal Dynamic DNS configuration for with ddclient

Sht, 21/07/2018 - 8:56pd

When I searched for a way to configure ddclient for, some pages mention protocol=dyndns2 with a custom URL. But actually, ddclient supports protocol=noip out of the box, so minimal steps would be something like:

$ sudo apt install ddclient$ cat <<EOF | sudo tee /etc/ddclient.conf

And here we go.

$ echo 'run_daemon="true"' | sudo tee -a /etc/default/ddclient$ sudo service ddclient restart$ journalctl -u ddclient.service
systemd[1]: Started LSB: Update dynamic domain name service entries.
ddclient[24631]: SUCCESS: updating good: IP address set to 118.X.Y.Z

For more details, refer to ddclient -help.

Xubuntu: Xubuntu 17.10 EOL

Sht, 21/07/2018 - 7:20pd

On Thursday 19th July 2018, Xubuntu 17.10 goes End of Life (EOL). For more information please see the Ubuntu 17.10 EOL Notice.

We strongly recommend upgrading to the current release, Xubuntu 18.04, as soon as practical. Alternatively you can download the current Xubuntu release and install fresh.

Raphaël Hertzog: Freexian’s report about Debian Long Term Support, June 2018

Pre, 20/07/2018 - 4:28md

Like each month, here comes a report about the work of paid contributors to Debian LTS.

Individual reports

In June, about 202 work hours have been dispatched among 13 paid contributors. Their reports are available:

  • Abhijith PA did 8 hours (out of 10 hours allocated, thus keeping 2 extra hours for July).
  • Antoine Beaupré did 24 hours (out of 12 hours allocated + 12 extra hours).
  • Ben Hutchings did 12 hours (out of 15 hours allocated, thus keeping 3 extra hours for July).
  • Brian May did 10 hours.
  • Chris Lamb did 18 hours.
  • Emilio Pozuelo Monfort did 17 hours (out of 23.75 hours allocated, thus keeping 6.75 extra hours for July).
  • Holger Levsen did nothing (out of 8 hours allocated, thus keeping 8 extra hours for July).
  • Hugo Lefeuvre did 4.25 hours (out of 23.75 hours allocated, but gave back 10 hours, thus keeping 9.5 hours for July).
  • Markus Koschany did 23.75 hours.
  • Ola Lundqvist did 6 hours (out of 8 hours allocated + 17.5 remaining hours, but gave back 15.5 unused hours, thus keeping 4 extra hours for July).
  • Roberto C. Sanchez did 29.5 hours (out of 18 hours allocated + 11.5 extra hours).
  • Santiago Ruano Rincón did 5.5 hours (out of 8 hours allocated + 7 extra hours, thus keeping 9.5 extra hours for July).
  • Thorsten Alteholz did 23.75 hours.
Evolution of the situation

The number of sponsored hours increased to 210 hours per month. We lost a silver sponsor but gained a new platinum sponsor with the Civil Infrastructure Platform project (hosted by the Linux Foundation, see their announce).

We are very happy to see the CIP project engage directly with the Debian project and try to work together to build the software stack for tomorrow’s world’s infrastructure.

The security tracker currently lists 57 packages with a known CVE and the dla-needed.txt file 52.

Thanks to our sponsors

New sponsors are in bold.

No comment | Liked this article? Click here. | My blog is Flattr-enabled.

Kubuntu General News: Kubuntu 18.04 Reviewed in Linux ( Pro ) Magazine

Pre, 20/07/2018 - 3:39md

Kubuntu Linux has been my preferred Linux distribution for more than 10 years. My attraction to the KDE desktop and associated application set, has drawn from Kubuntu user, to a tester, teacher, developer, community manager and councilor. I feel really privileged to be part of, what can only be described as, a remarkable example of the free software, and community development of an exceptional product.

This latest release 18.04, effectively the April 2018 release, is a major milestone. It is the first LTS Long Term Support release of Kubuntu running the “Plasma 5” desktop.
The improvements are so considerable, in both performance and modern user interface ( UI ) design, that I was really excited about wanting to tell the world about it.

Which is why I was completely ecstatic when I was commissioned by Linux Magazine to write a 2000 word article, spanning some 4 pages, as a major review center piece in their magazine.

Published as “Linux Pro Magazine” in the US and “Linux Magazine” in Europe.

In the article I dive into one of the greatest and most unsung features of KDE Plasma 5; “Activities”. The introduction of activities in KDE has been a revelation to me, and completely changed the way that I work on a day to day basis. I encourage you whole heartedly to explore them, if you haven’t done so already.

Published in the August 2018 edition, and from which the introduction is available online at or of course you can buy the August issue from

It is fantastic to see Kubuntu hitting the main stream publishing and to have an in-depth review article in one of the global leading Linux magazines is wonderful.

by Rick Timmis