They may get the DNS server to use from Nethserver DHCP. The clients use the DNS server of a webfilter. This way all clients should be able to access it. You may use a static route on the internet gateway for the aqua network to go to the docker machine. Now you can manage the containers via web UI.Ĭheck the IPs of your machines, if you installed in a different order they may differ. Install nxfilter and/or pihole to test them.Įdit TZ=Europe/Vienna to match your timezone: Nxfilterĭocker run -d -name nxfilter -v nxfilter-conf:/nxfilter/conf -v nxfilter-log:/nxfilter/log -v nxfilter-db:/nxfilter/db -e TZ=Europe/Vienna -net=aqua -restart=unless-stopped packetworks/nxfilter-base:latest Piholeĭocker run -d -name pihole -e TZ="Europe/Vienna" -e WEBPASSWORD="admin" -v "$(pwd)/etc-pihole/:/etc/pihole/" -v "$(pwd)/etc-dnsmasq.d/:/etc/dnsmasq.d/" -cap-add NET_ADMIN -net=aqua -restart=unless-stopped pihole/pihole:latest Portainerīrowse to setup admin username/password and select Local. mkdir -p /etc/e-smith/templates-custom/etc/shorewall/policyĬp /etc/e-smith/templates/etc/shorewall/policy/35aqua /etc/e-smith/templates-custom/etc/shorewall/policy/Ĭat /etc/e-smith/templates-custom/etc/shorewall/policy/35aqua In a production environment you should leave this step and set firewall rules. Get docker repo and install and enable nethserver-docker: cd ~įor testing purposes I decided to open the docker network by policy. Please test and give feedback… Installation This howto is for testing the DNS webfilters.
0 kommentar(er)
