Quote from: krawum on Today at 02:27:05 PMpkg install nanoYou don't need nano because FreeBSD has edit a.k.a. ee by default and it's pretty much the same thing, maybe even easier than nano for some ;)Quote from: keeka on Today at 11:29:49 AMI'm not sure where I got the following impression from, but my understanding of current NAT/Rule linkage is, choosing 'firewall rule' creates a rule for you but the association is not maintained (where it may have been before the overhaul). i.e. now, if you edit the port forward, the generated firewall rule does not get modified. I haven't tested this assumption as I tended to maintain firewall rules, even those associated with NAT, manually.IIRC you could be right, because there were some changes to that "logic" this year.
Quote from: Netlearn on Today at 03:12:23 AMAMEN! :)Quote from: defaultuserfoo on October 09, 2026, 05:21:05 AMIt sucks that we can't automatically store the config on an ftp server or send it by email at least once daily when it has been changed. If that were possible I would have set that up and I'd have the current config now.
Wrong statement: There are several plugins that provide configuration backup service. I personally use 'os-sftp-backup' and works perfectly. You even have 'os-git-backup', so you can trace every single modification in a git server.
[TL:DR] Do no blame others for your own lazyness/lack of knowledge.
Apart from that, you should always make a backup before any upgrade, so your last config would be on the last-1 version. Plus you should also take a snapshot, assuming your system uses zfs, which it's the recommended.
Make a backup before and after you make important changes. It can also help to find which change was wrong by just making a 'diff' between them.
Gonna play with firewall rules? Have a backup before just in case you even get to lose connectivity with the machine. It will take almost no time to go back.
If you follow those well-known basic advices, you won't have any problem recovering from even the total disaster. Of course, everyone is free to not make regular backups, snapshots before upgrades, or any prevention measure at all, but must be conscious of the risk it implies and don't cryif/when sh*it hits the fan.
Last but not least, being polite with the people usually gets best results when asking for help.
Quote from: Patrick M. Hausen on Today at 12:26:52 AMI don't want dynamic DHCP clients polluting my carefully maintained DNS zone.Because in your case you run AdGuard and want to see all Clients listed there and what they are up to ?!
Why would I want "Paddys-Macbook-Pro" in my DNS?
Quote from: (MARLOO) on Today at 12:44:01 AMIt lets me reach laptops, VMs, phones and IoT devices by name without maintaining a static DNS entry for every temporary client.I actually do maintain Local DNS Records in Pi-Hole that match Static DHCP Mappings based on the MAC Address in KEA in OPNsense.
QuoteBeing able to resolve client hostnames is also useful for SSH, SMB, printing, Home Assistant integrations, remote access, and quickly reaching a VM or laptop without looking up its current IP.My favorite is reaching the Printer's webGUI to check errors and statistics :)
QuoteBoth approaches are valid.Ofcourse!