On 11/26/2015 09:14 AM, James Valleroy wrote: [...] > I've committed this patch. > > I tested it with Stretch Alpha 4 installer in Virtualbox. After install, > I found that /etc/network/interfaces was empty except for the loopback > device. But there's a different issue: the installer created a network > manager connection "Wired Connection 1".
It is interesting to know that Debian installer is using network manager for connections rather than traditional way. Perhaps it does this when network manager is available (as a result of freedombox-setup). > > I tried testing with 2 network configurations: > - Bridged Adapter: Wired Connection 1 is active, FreedomBox WAN is not > active. Plinth cannot be accessed from host machine. > - Bridged Adapter + Host-only Adapter: FreedomBox WAN is active on > enp0s3, Wired Connection 1 is active on enp0s8, FreedomBox LAN enp0s8 is > not active. Plinth can be access on bridged adapter IP only. > > So it looks like we will need to check for this connection and delete it. There is a connection setting for network manager connections called 'autoconnect-priority'. Perhaps setting this value to a higher value than the automatic connections such as 'Wired Connection 1' created by network manager (or debian-installer) is a good solution. Then again, any connection created by user (or script) should take priority over automatically created default connections. I suspect another thing: VirtualBox does something weird, it uses one kind of network adapter during first boot and another kind after the first boot. Thus the interface name changes after first boot. During first boot, it will be 'eth0' and we will have created a connection for it, then after the reboot, it changes to 'enp0s8' or so which will not be associated with the connection we created. Repeating the process in Qemu/KVM might confirm the suspicion. On the overall, we should: - Increase auto-connection priority to our connections - Change default firewall zone to 'external' so that no matter who created the connection, Plinth will be accessible. > > Some more ideas for further improvements: > - There are still several prompts in the install process, maybe these > can be automated. > - This preseed file appears to be only meant for x86 or amd64. Since > Debian has installers for several armhf boards now, we can look into > making a preseed file that works on armhf. I don't see architecture specific bits in our preseed file. Will the armhf installer have different questions? (I suppose not). Also, I don't know why we have to mess with resolv.conf in our preseed. Perhaps it is a fix we no longer require. Sounds like the Debian installer method is easier than installing Debian and running freedombox-setup. It is also possibly less prone to errors. We should document this thoroughly on the Wiki and encourage new installing users to take up this procedure. -- Sunil
signature.asc
Description: OpenPGP digital signature
