DNS resolution broken after DHCP in 20191016-eoan?

A partition and disk imaging/cloning program

Brought to you by: steven_shiau

DNS resolution broken after DHCP in 20191016-eoan?

Forum: Clonezilla live

Creator: Ian Bell

Created: 2019-10-22

Updated: 2019-10-24

Ian Bell - 2019-10-22

In 20191016-eoan, when running sudo dhclient -v, I get some garbage from md5sum in the output, and then DNS resolution doesn't work.

In 20191016-disco, this doesn't appear to occur.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2019-10-23

Yes, I confirmed this issue. However, so far I can not find any clue why this happens...

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2019-10-23

Somehow by running "service systemd-resolved restart" after "dhclient -v eth0", then the DNS setting works. No idea why...

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ian Bell - 2019-10-23

/etc/dhcp/dhclient-enter-hooks.d/resolved is different in 20191016-eoan than in 20191016-disco and is referenced by /usr/sbin/dhclient-script.

Line 58 of /etc/dhcp/dhclient-enter-hooks.d/resolved uses md5sum. There's probably something wrong there.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ian Bell - 2019-10-23

Line 29 + 33 references /run/systemd/resolved.conf.d/isc-dhcp-v4-$interface.conf which doesn't exist, so that explains the error.

I guess they changed the way they set DNS resolvers with dhclient.

You could probably replace \live\filesystem.squashfs\etc\dhcp\dhclient-enter-hooks.d\resolved with the version from 20191016-disco and it will fix it.

Edit: Confirmed that replacing this file fixes the issue.

I attached the 20191016-disco version for reference.

-- Ian Bell

Last edit: Ian Bell 2019-10-23

resolved

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ian Bell - 2019-10-23

Made a bunch of edits to the last post, making a new reply to make sure an email notification gets sent:

Line 29 + 33 references /run/systemd/resolved.conf.d/isc-dhcp-v4-$interface.conf which doesn't exist, so that explains the error.

I guess they changed the way they set DNS resolvers with dhclient.

You could probably replace \live\filesystem.squashfs\etc\dhcp\dhclient-enter-hooks.d\resolved with the version from 20191016-disco and it will fix it.

Edit: Confirmed that replacing this file fixes the issue.

I attached the 20191016-disco version for reference.

-- Ian Bell

resolved

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2019-10-23

Thank you very much.
It's better that the upstream fixes this issue, so that we won't have to patched it time to time. Could you please help to file a bug about this regression:
https://bugs.launchpad.net/ubuntu
Appreciate.

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2019-10-24

OK, I have filed a bug report and attach a patch file for this issue:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1849608
Hope the upstream can apply it ASAP. If you can, please also tag it also affects you so the important level can be raised.
Thanks.

Steven

👍
1

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Ian Bell - 2019-10-24
  
  That patch is better than my suggestion! Didn't realize that the issue was only happening because of the error output.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2019-10-24

It's because you gave the hints so that I could identify and fix this issue. Thank you very much.
I have uploaded a patched systemd version of Clonezilla live: 2.6.4-10 or 20191024-*:
https://clonezilla.org/downloads.php

Please give it a try and let us know the results.

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2019-10-24

Oh, this issue is nothing to do with Debian-based Clonezilla live and 20191024-disco, so please just give Clonezilla live 20191024-eoan a try.
If it's tested good, I plan to release it as stable one.

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Ian Bell - 2019-10-24
  
  Tried 20191024-eoan on the same box that I initially had the problem. Confirmed that DNS resolution now works after DHCP. Seems to be fixed!
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2019-10-24

Great! Thanks for your confirmation.

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.