Currently systemd based wrlinux std/std-sato image cannot set up resolv.conf file correctly. This is because network managers on these images don't set it up correctly. What we need is something like: root@localhost:~# cat /etc/resolv.conf search pek-tuxlab2.wrs.com nameserver 128.224.160.11 nameserver 147.11.100.30 nameserver 147.11.1.11 Both connman and systemd-reolved don't write enough information to resolv.conf. On sysvinit, the resolv.conf file is set up correctly because dhclient is started on eth0. We might need to do the same for systemd based images, making dhclient start on eth0 by default. Please see details below. root@localhost:~# cat /etc/resolv.conf search pek-tuxlab2.wrs.com nameserver 128.224.160.11 nameserver 147.11.100.30 nameserver 147.11.1.11 root@localhost:~# cat /etc/network/interfaces # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # Wireless interfaces iface wlan0 inet dhcp wireless_mode managed wireless_essid any wpa-driver wext wpa-conf /etc/wpa_supplicant.conf iface atml0 inet dhcp # Wired or wireless interfaces auto eth0 iface eth0 inet dhcp iface eth1 inet dhcp # Ethernet/RNDIS gadget (g_ether) # ... or on host side, usbnet and random hwaddr iface usb0 inet static address 192.168.7.2 netmask 255.255.255.0 network 192.168.7.0 gateway 192.168.7.1 # Bluetooth networking iface bnep0 inet dhcp root@localhost:~# ps -ef | grep dhc root 962 1 0 02:26 ? 00:00:00 dhclient -pf /var/run/dhclient.eth0.pid eth0 root 1167 1161 0 02:30 ttyS0 00:00:00 grep dhc root@localhost:~#
