| { | |
| "$schema": "https://raw.githubusercontent.com/JanDeDobbeleer/oh-my-posh/main/themes/schema.json", | |
| "blocks": [ | |
| { | |
| "alignment": "left", | |
| "segments": [ | |
| { | |
| "background": "#ffffff", | |
| "foreground": "#000000", | |
| "leading_diamond": "", |
| EMAIL= | |
| DOMAIN0= | |
| DOMAIN1= | |
| API_EMAIL= | |
| API_TOKEN= |
Few months ago, I've made a similar work but I wanted something a little more easier to manage. Please have a look at here for my previous work.
This time, I'm gonna do pretty much the same thing but using Pi-hole as base then modify it to include unbound and stubby.
This way, I can use the power of Pi-hole with some additional security layers:
unbound)stubby)
| // ID of the config, e.g. A1234BCD. | |
| const configID = "A1234BCD"; | |
| // API key, found at the bottom of your account page in https://my.nextdns.io/account | |
| const APIKey = "xxxxxxxxxxxxxxxxxxxxxxxxxx"; | |
| // Mark true or false. If true, failed links will be retried 3 times at progressively increasing intervals. | |
| // If false, failed links will not be retried. | |
| const retryFailedLinks = true; | |
| // Time delay between requests in milliseconds. | |
| // 800 seems to not give any errors but is rather slow while anything faster will give errors (in limited testing). | |
| // If you want to go lower, it is recommended that "retryFailedLinks" is true |
All packages, except for Tini have been added to termux-root. To install them, simply pkg install root-repo && pkg install docker. This will install the whole docker suite, left only Tini to be compiled manually.
This is my personal guide for installing pfSense. Hope you find it useful. I made these notes to capture the details of my "install from scratch" to ensure I didn't miss important details. Also, I'm trying build my network with discrete "disposable" components that make the system mutable and less rigid. It does not cover installing any packages like Squid or Suricata as that's way beyond the scope of a basic, functional install.
I migrated from an environment that was at various times running Tomato Toastman 1.28 or Asuswrt-Merlin on Netgear and ASUS routers across four "access points" (one always acting as the firewall/gateway, the rest as APs). It was OK pre-gigabit, but had roaming problems, and I was using large Wifi routers with most of the features disabled. Also, I found that I could easily swamp the network and tank VOIP and Wifi Calling without even trying. The only fix was to throttle everything by using Bandwidth Limit
| server: | |
| ########################################################################### | |
| # BASIC SETTINGS | |
| ########################################################################### | |
| # Time to live maximum for RRsets and messages in the cache. If the maximum | |
| # kicks in, responses to clients still get decrementing TTLs based on the | |
| # original (larger) values. When the internal TTL expires, the cache item | |
| # has expired. Can be set lower to force the resolver to query for data | |
| # often, and not trust (very large) TTL values. | |
| cache-max-ttl: 86400 |
Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.
| udp://p4p.arenabg.ch:1337 | |
| udp://p4p.arenabg.com:1337 | |
| http://bttracker.crunchbanglinux.org:6969/announce | |
| http://tracker.aletorrenty.pl:2710/announce | |
| udp://torrent.gresille.org:80/announce | |
| udp://glotorrents.pw:6969/announce | |
| udp://tracker.trackerfix.com:80/announce | |
| udp://www.eddie4.nl:6969/announce | |
| udp://tracker.leechers-paradise.org:6969 | |
| http://retracker.kld.ru:2710/announce |