At home, nagios, at work colleagues. (I finally escaped the admin rat race)
At home, nagios, at work colleagues. (I finally escaped the admin rat race)
Duh
Not watching at all.
Sorry, totally forgot apparmor. On debian that thing can be nasty, I had to fix those rules as well for bind That was years ago and was added to my Puppet module, so I forgot.
Nop, I don’t have a 4k library. To be honest, my TV doesn’t even know what HD ready is. It can handle 1080i, but full HD, nop. (And I already have a hard time seeing the difference between 720p and 1080p)
Second that. I’m glad RPis are finally supported.
You need to include the files in the zone file. Bind 9.18.18 is a mess with the changed DNSSEC setup, it broke my domains as well. I’t isn the bind documentation, so I have to refer you there. I have no access to my setup now (or my browser history) as I’m not at my computer.
Edit: managed to get in dns.
named.conf.local: zonefile needa to be the .signed file the unsigned zone file must have both keys included, best is via absolute path:
$INCLUDE "/etc/bind/keys/example.com.123456.key"
for both the ZSK and KSK keys. The include is to get the RRSIG entries.
I haven’t bought new media in years. Last time I bougth new they were LP records, new pressings. For movies I just download or buy used, for music I almost always buy used and from time to time new when I really want to support the artist.
Yhe problem with limiting yourself to either pirate or just 1 type of medium is that you miss out on good stuff. At this moment I have music from every decade between 1890 and 2020 on LP, of which most will never be available digitally.
I’m running domoticz with an rflink interface for my rf433 devices. No clue if they support ESPHome, but you can check. It runs confined to my network.
Then I’ll limit myself to the situation at work. ifupdown2 works great and doesn’t need replacing at home.
Thanks, it was already a mess to figure out without systemd ‘defaults’ barging trough my settings. Maybe I;ll keep my personal setup as it is and only let systemd dat the interface names of the 2 physical interfaces and have the dependencies of services linked to the virtual device states. As long as I can ditch NetworkManager at work I’m totally happy.
I’ll see what I can manage. Thanks for the pointers.
When I can manage simple ipv4 networking via networkd I’m already happy, as it means I can ditch NM again at work, that’s giving me a lot more headaches then a flapping SLAAC that I’m not dependent on. (already switched back to my super stable tunnel) The situation here is a setup with 2 ipv6 tunnels, 1 ipv6 SLAAC, source based routing and no default gateway in main routing table for ipv6. Everything runs via the ipv4 pppoe connection. (and a load of vlans both sides of my router to internet)
Replace a bunch of poorly integrated tools such as NetworkManager
You got me here… I’m now battling NetworkManager in scripting (alas, still no Ansible in place there, I doubt it’ll be long before I have implemented it), the thing just refuses any configuration via files. Time to dive into the networkd setup. I also hope I can get rid of the very unstable ppoe and wide-dhcpv6-client setup I have here now via ifupdown2 on Debian. The restart I like as well. Time for a deep dive I guess. On Debian NM never caught on, thank $preferredDdiety, but at work it’s a disaster.
If you apply what is written at https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/#cutthecraphowdoimakesurethatmyservicestartsafterthenetworkisreallyonline it will work.
Then I’ll need to do a global rewrite of all distrubution delivered service files and replace network.target with network-online.target. Then I don’t understand why maintainers all keep using network.target. For every service that needs some kund of netwirj active I alkready have iverrides to link then to the virtual or physical interfaces they actually use.
Systemd-networkd has a learning curve, once you learn it you’ll find it superior and more flexible than anything else.
I still find it a solution desperately looking for a problem to solve. Yes, you can control loads of dependencies, but you could already do that with the init scripts. The main selling point on introduction was ‘it is faster’. Why would you want something faster when you use it once every kernel update? When you design your solutions correctly (redundant), you won’t even notice a reboot of 1 system in the setup.
I’d say they made the image, started it, did minor adjustments and didn’t delete the command history before stopping it and starting to deploy the image.
Looks harmless, although a tad sloppy.
I highly advice against nfs mounts between a vps and home network, even with a static ip and over a vpn.
When you need data that’s on the nas at home on the vps, it’s best to place a copy of that data on the vps local storage. It can act as a backup as well and the original data can be kept safely at home.
What are you trying to do with this setup? Maybe we can find another solution for you.
I think I’d bring it a thriftstore. (Or donate it to somebody that could use it ;) )
I’m having the same issue with and RPi 1, 2 and 2 bananapies. (R1 and R2) I’m not sure if the BPi R2 is good enough for a kodi setup, the rest is to light.
I’m using ifupdown2 and have services depending on the state of virtual network devices (BindsTo=sys-devices-virtual-net-.device).
I hate systemd with a passion, as the refuses to wait for networking when you haven some service specified to be started After networking, but it start when the start of networking actions has sbeen tarted (not after networking is finished bringing up everything)
The only think I let systemd do is monitor the state of the devices and set the interface name, as udev seems to mess these names up in combination with systemd (and there is to much depending on systemd now in Debian to get rid of the junk)
open gmail and see ublock report >1k trackers blocked What tracker bust?
Oh wait, torrents and stuff… never mind.