RuneAudio Forum

While I was initially trying out Rune, via a wired connection I was able to resolve other machines in my network by name, including the server that holds all my music.

After switching to a Wi-Fi connection, the mount for my music failed. Eventually traced it down to a /etc/resolv.conf that only contained the default Google nameservers. Although in one of the many attempts, I thought I did see my own nameserver once, but could be mistaken as I was switching between wired and wireless lots of times.

Could this solely due to no configuration file for wlan0 network file being created under /etc/systemd/network/, because after manually creating one, I now get a correctly configured /etc/resolv.conf for my local network. Or could it be a timing issue and I've just been lucky on the last few attempts.

BTW the DHCP setting in /etc/systemd/network/eth0.network is set to: both. According to the man page, this shoul be "yes", "no", "ipv4", or "ipv6".

Cheers.

Hi EddieA,

please tell us what image you are working on (see your debug data).

Newer images do not use networkd!

Frank.

Hi EddieA,

your image is OK.

Rune doesn't use networkd.
We use netctl-auto for WiFi and netctl-ifplugd for ethernet.

Frank

Frank. Even though this is using netctl-auto for WiFi it sure looks like the assignment of the nameservers still depends on a file in the /etc/systemd/network/ directory.

I just ran some tests where I re-booted the C1+ 10 times. 5 of the times I had a /etc/systemd/network/wlan0.network file in place and every time /etc/resolv.conf was configured with my local nameserver. For the other 5 re-boots, this file was not present. On every one of those, /etc/resolv.conf was configured to use the Google nameservers.

Cheers.

And to add to the confusion, even though /etc/resolv.conf was correctly set at boot time to point to my local nameserver, at some point when it renewed the lease, it then switched over to the Google ones again.

Cheers.