Make sure dhcpcd does not interfere with resolv.conf. For the router
product we have a dnsmasq running that forwards to a local root
resolver (i.e. unbound).
For the ALIX board, we want to run a DHCP client on one port and a
DHCP server on the other two.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
- Move root.key into /etc/unbound directory
- Remove pid file from config, it is baked into the configure options
- Make sure unbound does not try to chroot anywhere
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
The simplification of the overide behaviour may be worth the slight
duplication overhead.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
- board configuration does not configure network interfaces,
only handles renaming
- router product for Raspberry Pi 3 configures DHCP for ethernet port
- router product for Alix board configures DHCP for third ethernet port,
static addresses for the other two
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
- Service file for dhcpcd master service
- Service template file for interfaces
- Service symlink for each configured interface
- Get DHCP address on raspberry pi 3 for ethernet port
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
- build needs a pair of product and board name
- some products can only be built for some boards
- Config files in product/<name> directory override those in board/<name>
- For some config files, like LDPATH or ROOTFS, the files are merged
- product/common provides defaults
Add default config for various services:
- Add default config for unbound
- Add default config for dnsmasq
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
