ddclient 3.8.2-2ubuntu2 causes networking to fail on GCE

[Dwight Lyle]

Release info:
Description: Ubuntu 16.04.2 LTS
Release: 16.04

Regardless of the /etc/ddclient.conf settings, simply installing the ddclient 3.8.2-2ubuntu2 package causes networking to completely fail after restarting an instance on Google Compute Engine (GCE). The serial console outputs the following errors repeatedly:

May 2 22:36:37 ubuntu-test kernel: [ 139.218755] ll header: 00000000: 42 01 0a f0 00 17 42 01 0a f0 00 01 08 00 B.....B.......
May 2 22:36:37 ubuntu-test kernel: [ 139.292581] IPv4: martian source x.x.x.x from x.x.x.x, on dev ens4

I tested this on two GCE images.

ubuntu-1604-xenial-v20170330
ubuntu-1604-xenial-v20160429

This does not seem to be a GCE bug because other Ubuntu images work fine with ddclient and function as expected.

ubuntu-1704-zesty-v20170413 with ddclient 3.8.3-1.1ubuntu1
ubuntu-1404-trusty-v20170424 with ddclient 3.8.1-1ubuntu2

Steps to reproduce:
1. Create a new network (not a legacy network) with default ports (22 for SSH etc).
2. Create a new Ubuntu instance using a 1604 image from GCE.
3. SSH into the instance and install ddclient. Set the config file with any contents.
4. Restart the instance.
5. Try to SSH to the instance or look at the serial console output to see the errors.

I recovered my instance by attaching the boot disk to another instance and deleting the files in the package file list: http://packages.ubuntu.com/xenial/all/ddclient/filelist The instance started up with functional networking like normal and I was able to complete the uninstall process with apt-get.

After recovering my instance, I installed ddclient 3.8.3-1.1ubuntu1 from the Zesty universe repository. That package works fine on Xenial and operates as expected.

[Zach Marano (zmarano)]

This is probably the same issue as Debian, which is this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807707

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Philipp Nagel (najel)]

I am also affected by this, and I found the same issue with the Azure Ubuntu Server 16.04 image. This issue did not affect the Ubuntu Server 16.04 image in AWS.