/var/log/syslog has:
Oct 7 15:42:33 laptop kernel: [21375.839338] [UFW BLOCK] IN=lxdbr0 OUT= PHYSIN=vethdfc21f4f MAC=00:16:3e:38:26:a2:00:16:3e:4d:c5:95:86:dd SRC=fe80:0000:0000:0000:0216:3eff:fe4d:c595 DST=fe80:0000:0000:0000:0216:3eff:fe38:26a2 LEN=78 TC=0 HOPLIMIT=64 FLOWLBL=740385 PROTO=UDP SPT=32931 DPT=53 LEN=38
So DNS is blocked.
$ sudo ufw status verbose Status: active Logging: on (low) Default: deny (incoming), allow (outgoing), deny (routed) New profiles: skip
Disabling ufw is a usable workaround.
BUT disabling ufw is not recommendable security-wise. snapcraft should come with the necessary ruleset for running behind ufw.
/var/log/syslog has:
Oct 7 15:42:33 laptop kernel: [21375.839338] [UFW BLOCK] IN=lxdbr0 OUT= PHYSIN=vethdfc21f4f MAC=00: 16:3e:38: 26:a2:00: 16:3e:4d: c5:95:86: dd SRC=fe80: 0000:0000: 0000:0216: 3eff:fe4d: c595 DST=fe80: 0000:0000: 0000:0216: 3eff:fe38: 26a2 LEN=78 TC=0 HOPLIMIT=64 FLOWLBL=740385 PROTO=UDP SPT=32931 DPT=53 LEN=38
So DNS is blocked.
$ sudo ufw status verbose
Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), deny (routed)
New profiles: skip
Disabling ufw is a usable workaround.
BUT disabling ufw is not recommendable security-wise. snapcraft should come with the necessary ruleset for running behind ufw.