This is a script for installing NextDNS CLI container on Firewalla Gold and Purple series devices. It is based on a script by Brian Curtis and has been tested on Firewalla 1.975 and above running in Router mode.
This script is maintained by me, and is not associated with or supported by Firewalla.
-
NextDNS CLI runs fine on Gold and Purple series Firewalla boxes.
-
The script will automatically grab the latest version of nextDNS CLI.
-
You can run NextDNS CLI and you can have Firewalla Unbound or DoH running, but any given client can only use one of these as they are mutually exclusive. By default, any device that is not in the Unbound or DoH group will use NextDNS CLI for any network segment that is set to use nextDNS and the WAN DNS will be ignored.
-
nextDNS also has support for using it on your mobile devices when away from home. (e.g. see https://apple.nextdns.io/) you can set it to the same profiles you use at home or a different one. So you can have some of the benefits such as ad filtering without the overhead of running a VPN.
-
Pros:
- Running NextDNS CLI as opposed to using Firewalla DoH > NextDNS, you can have DoH betwen FW and NextDNS and it shows individual client devices, not just your firewalla making all the requests. Less anonymous to be sure, but if you want to look at logs by device, that is handy. Note, it seems that is by IP (not mac address of course) so you may end up with the same device entered many times. :( I haven't found a solution to that yet. You can of course, always disable NextDNS logs if you like.
- NextDNS CLI does not require disabling Firewalla DNS Booster any negative side effects.
To install:
-
SSH into your Firewalla (learn how if you don't know how already.)
-
Copy the line below and paste into the Firewalla shell and then hit enter.
curl -s -L -C- https://raw.githubusercontent.com/mbierman/Firewalla-NextDNS-CLI-install/main/install_nextdnscli.sh | cat <(cat <(bash))
-
Next, you must configure two things in
/home/pi/.firewalla/config/post_main.d/install_nextdnscli.sh- IP the IP of your Firealla LAN(s) that you want to use nextDNS CLI
- id your nextDNS id
vi /home/pi/.firewalla/config/post_main.d/install_nextdnscli.shNote you can set up different devices using different NextDNS configurations including VPN connections. For example, I have Apple TVs in a different nextDNS configration so I can tune them. Simply add a line like this:
-config macaddress=nextdnsconfiguration ID \
There are more notes in the installation script about configuratoin choices you can make such as:
- different profiles for VPN connections
- different profiles per device (by mac address) e.g. an Apple TV might use a different profile than a desktop or a different profile for a child's devices. However, Firewalla Groups are not supported by nextDNS so you have to list each device)
- different profiles per network segment (e.g. an IoT segment might be different from a trusted network)
-
After editing, run the script
/home/pi/.firewalla/config/post_main.d/install_nextdnscli.sh
-
If you want to get notifications when nextDNS is not running, edit
/data/nextdnsdata.txtto include your IFTTT API key (optional)vi /data/nextdnsdata.txt
After completing the steps above, you can:
-
Open
https://test.NextDNS.io/
-
Try
dig github.com
; <<>> DiG 9.10.6 <<>> github.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5679
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;github.com. IN A
;; ANSWER SECTION:
github.com. 10 IN A 192.30.255.113
;; Query time: 20 msec
;; SERVER: 192.168.241.1#53(192.168.241.1)
;; WHEN: Thu Sep 08 10:56:06 PDT 2022
;; MSG SIZE rcvd: 55
The SERVER line should match the Firewalla server you set if NextDNS CLI is working. OR
- You can try https://my.NextDNS.io/ to see if it shows that NextDNS is working.
Great resource for all things NextDNS CLI.
Standard disclaimer: I can not be responsible for any issues that may result. Nothing in the script should in any way, affect firewalla as a router or comprimise security. Happy to answer questions though if I can. :)
You can use the following to run a test to make sure nextDNS is running and log to /data/logs/nextdns.log any errors.
If you want to run the monitor automatically, you can add the following line to /home/pi/.firewalla/config/user_crontab and restart Firealla. From then on, every 5 minutes the test will check to see if nextDNS is running on Fireawlla.
*/5 * * * * timeout -s SIGKILL 4m /data/nextdnstest.sh
Make sure the "4m" is < the amount of time between runs. So here we have run every 5 minutes and don't let the script run longer than 4 minutes.
You can also send a notification via IFTT. This requires IFTTT to send the notifiction. Edit /data/nextdnsdata.txt to include your IFTTT API Key.
The monitoring script seems to confict with Firewalla and it will often restart nextdns unnecessarily. As a result, I suggest not using the the testing script for the time being until I can figure this out. in all honesty it doesn't seem to be necessary but I'm leaving it in the repo.
You can temporarily stop nextdns for testing etc. without uninstalltalling it. Simply run this file (or the commands in it).
To Resume nextdns CLI, remove /data/stopnextdns and re-run the install script.
You can run this by copying this line and run it on firewalla to uninstall.
curl -s -L -C- https://raw.githubusercontent.com/mbierman/Firewalla-NextDNS-CLI-install/main/uninstall_nextdns_cli.nosh | cat <(cat <(bash))
This script will also be saved when you install and you can just run it locally:
/home/pi/.firewalla/config/post_main.d/uninstall_NextDNScli.nosh
There are lots of NextDNS communities on Reddit. If you have NextDNS CLI questions, please check there.