Network won't connect in custom live disk

[klassiek]

I created a custom Mint 19 live disk using a tool called "refractasnapshot". The new live disk seems to work fine, except it won't connect to the wired network like I it does normally with a vanilla Mint 19 live disk, or a fully installed version of Mint. Any idea what might be going wrong? Manually executing "dhclient ens33" does cause the network to connect, but I don't wan't to have to do this every time I boot. Thanks.

[kukamuumuka]

What the next commands are telling?

Code: Select all

inxi -Nn

Code: Select all

nmcli dev status

Code: Select all

rfkill list all

[klassiek]

Thanks for taking a look.

What the next commands are telling?

Code: Select all

inxi -Nn

Code: Select all

Network:   Card: Intel 82545EM Gigabit Ethernet Controller (Copper)
           driver: e1000
           IF: ens33 state: up speed: 1000 Mbps duplex: full
           mac: 00:0c:29:b6:28:29

Code: Select all

nmcli dev status

Code: Select all

DEVICE  TYPE      STATE                                  CONNECTION         
ens33   ethernet  connecting (getting IP configuration)  Wired connection 1 
lo      loopback  unmanaged                              --                 

Code: Select all

rfkill list all

This does nothing.

[kukamuumuka]

Is DNS-servers ok?

Code: Select all

cat /etc/resolv.conf

Is IPV6 enabled?

Code: Select all

test -f /proc/net/if_inet6 && echo "IPv6 supported" || echo "IPv6 not supported"

[klassiek]

Thanks.

Is DNS-servers ok?

Code: Select all

cat /etc/resolv.conf

Code: Select all

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53

Is IPV6 enabled?

Code: Select all

test -f /proc/net/if_inet6 && echo "IPv6 supported" || echo "IPv6 not supported"

Code: Select all

IPv6 supported

[kukamuumuka]

Code: Select all

nameserver 127.0.0.53

It seems that there is a systemd-bug.
https://bugs.launchpad.net/ubuntu/+sour ... ug/1624320
To solve that bug:
https://www.hiroom2.com/2017/08/24/ubun ... 0-0-53-en/

2 Disable systemd-resolved
Disable systemd-resolved and reboot. nameserver 127.0.0.53 is not written to /etc/resolv.conf.

Code: Select all

sudo systemctl disable systemd-resolved
sudo reboot

[klassiek]

Since I am using a live disk, I cannot reboot after following your instructions.

But on my fully installed instance (which has a working wired connection), I disabled systemd-resolved as you said. Now I can't resolve any addresses. For instance:

Code: Select all

Could not resolve 'archive.ubuntu.com'

Firefox also can't get to websites.

[kukamuumuka]

Since I am using a live disk, I cannot reboot after following your instructions.

But on my fully installed instance (which has a working wired connection), I disabled systemd-resolved as you said. Now I can't resolve any addresses. For instance:

Code: Select all

Could not resolve 'archive.ubuntu.com'

Firefox also can't get to websites.

Code: Select all

sudo systemctl enable systemd-resolved
sudo reboot

[klassiek]

Is there a way to disable systemd-resolved without needing to reboot? Thanks.

[edit]

I tried disabling systemd-resolved in the OS instance that I use to create the live disk. It can't tell what difference it made, since the (newly generated) live disk *still* cannot connect to Ethernet *at all*.