How do the DNS servers resolve local hostnames then? The pihole DHCP integration adds local hostnames to DNS when they are assigned an address. If there’s two DHCP servers handing out leases, presumable only one would be accepted, how then would the DNS servers sync those names?
I think I had my secondary pihole resolve local names from the primary, and leases were copied over on a cronjob in case the secondary DHCP server had to be enabled.
Not that it particularly matters for just queries. The problem is that DHCP can only be enabled on one host. If that one fails then devices can’t get on to the network themselves. I’d like to know a good way to have a failover DHCP server - my janky cronjob isn’t great.
Where do you do DHCP? I had a primary pihole with DHCP enabled and a secondary with a cron job that enabled DHCP if the primary was down or disabled it if the primary was working. The cron job did sync DHCP leases from one to the other but it was a bit janky. I tried to update the secondary to pihole v6 and hosed it so I have no backup for now. I’d like to re-image the secondary and get a better setup - when I have time.
Edit to say I really wanted to try keepalived - that’s really cool to fail over without clients noticing.
I think this wiki cheetsheet will explain some of the defaults. Pretty much everything is controlled with a keybind using the meta/super (windows) key. Mod + d should open the launcher, I only used dmenu but yours might be something else. The launcher will let you launch applications by name. If you just want a terminal, Mod + Enter will open one.
You will want to look at your config. It should live in ~/.config/sway/config. If it’s not there then mkdir ~/.config/sway/ && cp /etc/sway/config ~/.config/sway/. That should list the keybinds you have set. You can look up the options in the man page for sway.
Once you can do some basic window control, you might want to customise the status bar. The config should tell you what bar is being used, but there are a huge array of statusbars to choose from - I used i3status-rust but try searching for i3/sway statusbars to see what’s out there.
Ah, I saw another comment about this. The free plan is 300,000 queries a month. That’d last me almost a week before it stops working.
That says it will only function for 300,000 queries per month. Based on my last 24 hours from pi-hole, that wouldn’t even last a week. Are you using a paid plan?
Yeah, I really dislike snap and have puppet clean it out and add in the real mozilla repo for me. If I wanted sandboxed apps I’d probably look at flatpak but I think there’s still work to be done there also.
Canonical added an epoch prefix to the firefox version number. Because that epoch (1) is higher than the implicit default (0), the official ubuntu dummy package is always considered to be a higher version than the official Mozilla package. apt doesn’t look at snap packages, it installs the deb, but the ubuntu deb just runs snap install firefox and basically nothing else.
w3m is a proper deb 😛
Looks like only firefox, chromium-browser and thunderbird are these dummy transitional packages. There’s a fwupd-snap, but the default fwupd is a full deb.
So both commands do the same thing… right? I’m not saying snap and apt are the same in general.
In Ubuntu they are the same. firefox version 1:1snap1-0ubuntu5 is a deb that literally runs the command snap install firefox in the preinst script. Check line 77 in firefox-1snap1/debian/firefox.preinst in the source tarball: https://launchpad.net/ubuntu/+source/firefox/1:1snap1-0ubuntu5
There’s no magic there.
If you have the
docker-compose.ymllocally, you cannix run github:aksiksi/compose2nixto translate it into a nix file for inclusion in your nixos system config. I think that could be done in the config itself with a git url but I’m not that great at nix. You will surely still need some manual config to e.g. set environment variables for paths and secrets.