We need to set the new created network and a fixed unique MAC address else the containers get random ones on restart and that breaks DHCP reservations. You need a bridge to connect to (could be created in UI, if you use NSDC you already have one).Ĭreate the docker network testnet with bridge br0:ĭocker network create -d devplayer0/net-dhcp:latest -ipam-driver null -o bridge=br0 testnet
Spiceworks nxfilter install#
Yes, the docker-net-dhcp plugin worked perfectly.īTW, I tested with the nxfilter image first and noticed the latest nxfilter image does not start, there’s an open issue.ĭocker plugin install devplayer0/net-dhcp If docker is bridged to Green, can dhcp server be used for a reservation? I also noted that yum install of results in a failed connection. Loading mirror speeds from cached hostfile Loaded plugins: changelog, fastestmirror, nethserver_events Installng the nethserver-docker via yum install -enablerepo=nethforge-testing nethserver-docker resulted in the following ~]# yum install -enablerepo=nethforge-testing nethserver-docker I was playing around with Guacamole and ran into problems trying to deploy nethserver-docker on a fresh NS demo. Using rootless podman containers - I already tried but no success.The last filter uses Nethserver as upstream DNS. One filter uses the next one as upstream DNS. Now when clients use the proxy the DNS filter is involved. You need to set the Nethserver upstream DNS to one of the filters. In this case the filter only gets the IP of the Nethserver and has no information who is surfing but blocks ads and more.
Nethserver uses webfilter as upstream DNS Nxfilter for instance can map the IP to AD/LDAP users. This way the filter gets the client IP and you can see it in the logs. The Nethserver uses an outside upstream DNS like 8.8.4.4 (google). This webfilter uses the Nethserver as upstream DNS. 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)
