Hello, the silo 2162 installed nicely, but the update to aethercast did not install. What has been changed is: The following packages will be upgraded: isc-dhcp-client isc-dhcp-common isc-dhcp-server I see the changed /etc/apparmor.d/sbin.dhclient, so that landed. But I still see /etc/dhcp/dhclient-enter-hooks.d/aethercast-p2p/dhclient-hook-p2p and I assume this will only work when pushed a directory higher, as explored below. In the current state, I can connect once to the Wireless Display Adapter while conserving internet access. By the second time, internet access is dropped. The behavior I'm seeing is that at the first time, a new network is added, albeit without a default route. By the second connection, a new network is added, this time with a default route. === network routes with silo 2162 installed: $ dpkg -l | egrep '(aethercast|isc-dhcp)' # lines are shortened manually ii aethercast 0.1+15.04.20160808-0ubuntu1 ii aethercast-tools 0.1+15.04.20160808-0ubuntu1 ii isc-dhcp-client 4.3.1-5ubuntu2.4~overlay2 ii isc-dhcp-common 4.3.1-5ubuntu2.4~overlay2 ii isc-dhcp-server 4.3.1-5ubuntu2.4~overlay2 before aethercast: $ ip r l default via 192.168.1.254 dev wlan0 proto static metric 600 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.33 metric 600 after first aethercast connection, it being active: $ ip r l default via 192.168.1.254 dev wlan0 proto static metric 600 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.33 metric 600 192.168.7.0/24 dev p2p0 proto kernel scope link src 192.168.7.1 after second aethercast connection, it being active: default via 192.168.157.1 dev p2p0 default via 192.168.1.254 dev wlan0 proto static metric 600 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.33 metric 600 192.168.7.0/24 dev p2p0 proto kernel scope link src 192.168.7.1 192.168.157.0/24 dev p2p0 proto kernel scope link src 192.168.157.100 This stays the same from here on, even after disabling external display via menu. Disabling and reenabling wireless network completely re-empties the routes, eliminating the default route via the p2p0 device, thus restoring internet connectivity. Until aethercast is activated again. It seems that p2p0 connections are not torn down on terminating aethercast connection, at least after the first time - when using it multiple times, I always end up with two networks routed via p2p0, at the second time coming with a default route. I do not know what is the desired behavior, if networks are supposed to be torn down after ending an aethercast connection. ==== network state after moving the aethercast dhclient-enter-hook up by one directory and rebooting: $ sudo mount -o rw,remount / $ sudo mv /etc/dhcp/dhclient-enter-hooks.d/aethercast-p2p/dhclient-hook-p2p /etc/dhcp/dhclient-enter-hooks.d/ $ sudo shutdown -r now before first connection: $ ip r l default via 192.168.1.254 dev wlan0 proto static metric 600 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.33 metric 600 after first aethercast connection, it being active: $ ip r l default via 192.168.1.254 dev wlan0 proto static metric 600 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.33 metric 600 192.168.7.0/24 dev p2p0 proto kernel scope link src 192.168.7.1 after second and third aethercast connection, it being active: $ ip r l default via 192.168.1.254 dev wlan0 proto static metric 600 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.33 metric 600 192.168.7.0/24 dev p2p0 proto kernel scope link src 192.168.7.1 192.168.157.0/24 dev p2p0 proto kernel scope link src 192.168.157.100 The two p2p0 networks created remain, but the default route via p2p0 is not not added, allowing undisturbed internet access to the device. If there has been a change to the aethercast package in silo 2162, it is not appearing when deploying the silo. What is missing from my point of view is to move the dhcpclient-enter-hook one directory up, I assume the enter-hook.d-directory is not recursed into by the dhcp client. @Simon: Could you please revisit that and tell me when I can test that again? I am now familiar with where to install bileto :-)