How’d you set that up with Opnsense fail over? I have an opnsense VM with input straight from the ISPs FTTP box to the NIC on my server. So I can’t fail over to my second proxmox box without swapping the cable over.
How’d you set that up with Opnsense fail over? I have an opnsense VM with input straight from the ISPs FTTP box to the NIC on my server. So I can’t fail over to my second proxmox box without swapping the cable over.
Run your own DNS server on your network, such as Unbound or pihole. Setup the overrides so that domain.example.lan resolves to a local IP. Set your upstream DNS to something like 1.1.1.1 to resolve everything else. Set your DHCP to give out the IP of the DNS server so clients will use it
You don’t need to add block lists if you don’t want.
You can also run a reverse proxy on your lan and configure your DNS so that service1.example.lan and service2.example.lan both point to the same IP. The reverse proxy then redirects the request based on the requested domain name, whether that’s on a separate server or on the same server on a different port.
I imagine they use it in much the same way as any enterprise. Running servers and workstations, mostly.
F16’s run Kubenetes clusters.
Lots of individual bits of hardware on specialized devices will be running embedded operating systems. QNX is big in automotive for the same reasons it’d work on a rocket.
I don’t understand it either. On one hand people say don’t remember addresses, use DNS and on the other DNS relies on static addresses but then every device is “supposed” to have random addresses via SLAAC or privacy addresses. It just doesn’t seem to tie together very well, but if you use them like IPv4 addresses you’re apparently doing it wrong.
RAID IS NOT BACKUP RAID IS NOT BACKUP RAID IS NOT BACKUP
Don’t use Red drives for a NAS!! You need the Red Plus (or is it red pro) disks as they’re CMR.
I’d go for Ultrastar drives personally. There’s a few really good videos online analyzing the backblaze stats for different drives that are well worth watching.
I received so much spam and abuse of my network from .xyz domains that they are fully blocked in every conceivable way from being accessed or accessing my network.
Just because a DE looks sparse doesn’t means it also uses less resources. In imagine KDE would actually run well as it doesn’t need all the bells it offers and is actually a well written performant DE.
Pretty sure my Seagate usb disks I use for backup are SMR and sustained writes are awfully slow. Luckily I’ve discovered restic for backing up which lowered a 1.5tb weekly incremental backup from 9hrs to 1 min.
I highly recommend watching this guys videos on his analysis of the backblaze data https://www.youtube.com/watch?v=IgJ6YolLxYE&t=1
And a comparison of the difference WD drive colours, which might not be what you expect https://www.youtube.com/watch?v=QDyqNry_mDo&t=2
“It’s never lost data for me. Yet” is what they mean.
I totally agree, the only file system I’ve lost data with as a result of a file system corruption not caused by hardware errors or power problems in 35 years has been btrfs. FAT even served me better.
But pulling the power on a btrfs drive at the wrong time results in you not even being able to mount it as read only. No snapshotting can help you there.
And yet here we are 16 years later with btrfs only just in a position to be usable (perhaps. My experience is that I’ll never use it again)
It cares so much that when it goes wrong you can’t even mount the partitions as readonly to try get your data back. It will stubbornly hold on to it and refuse any access at all. Boy I am so glad it didn’t let me access a potentially corrupted byte somewhere!
And why I no longer run NC. Every time it would fuck itself to death and I’d have to start from scratch again.
Ahh yes, the first time it is defined is in the conclusion after being used 25 times previously in the article.
Thank you! I hate unexplained acronyms
I skimmed through it and have no idea what BBR stands for.
I’ve been using it for a few years. Really handy way if avoiding cooperate firewall rules.