I'm currently working on a project with Ubuntu Core with a RPi3. We are planning on installing the device on-site for experimental purposes, using the Wi-Fi interface for communication to the internet, on networks that use security PEAP+MSCHAPV2 authentification. To achieve connecting to this network, I've used Network Manager, mostly with success (it is connected, gets an address, receives DNS servers, etc.).
For developpement purposes, it was connected to my laptop, through ethernet, where I was sharing the internet (for initial updates, installing Network Manager, setting up the wireless network). To do so, I had configured the eth0 device to use a static config, setting my laptops IP address as the gateway and adding specific dns addresses.
As I approached my goal, I removed the gateway address and DNS settings from the ethernet to let the Pi talk to the internet through wi-fi. This failed with a nice "temporary failure in name resolution". A direct ping to the dns server addresses works, but with the domain name, it doesn't.
After tinkering, I added the DNS addresses back to the ethernet configuration through
console-conf, and weirdly enough, wifi would work. I've checked out wireshark from my laptop to confirm the ping wasn't coming through it and no trace of it.
It seems like DNS through Network Manager is broken, and that it will fallback to the ones configured for another interface to work. This seems wrong.
Anyone encounter anything similar? Is there a way to manage this properly ?
TL;DR : Network Manager configured WiFi with specific set DNS address fails to resolve names, unless the ethernet configuration in
console-conf sets the proper DNS address.
ls -al /etc/resolv.conf:
lrwxrwxrwx 1 root root 39 Mar 12 20:44 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
Sorry for bad formatting, responded from my phone