271
Intrusion Detection and Prevention / Re: Error with abuse.ch/ThreatFox rules
« on: March 22, 2021, 11:42:47 am »
Yep, same problems.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
So do most of you guys just use Unbound to upstream to DoT servers with DNSSEC or use DNSCrypt?The former and never had problems so far... but I started to study if/how DNSCrypt can be used to add an additional layer of security: do you know any online documentation for beginners on this?
To reconfigure AdGuard's listening address you need to edit its config file, no UI for that yet. It's /usr/local/AdGuardHome/AdGuardHome.yaml:It seems to me with Unbound you cannot select a 'custom' IP address...Code: [Select]dns:
bind_host: 0.0.0.0
port: 53
[...]
upstream_dns:
- 127.0.0.1:53530
127.0.0.1:53530 is my BIND. You can configure Unbound to do the same.
# fsck -y
** /dev/gpt/rootfs
** Last Mounted on /mnt
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
71646 files, 1018270 used, 26970326 free (5014 frags, 3370664 blocks, 0.0% frag)
***** FILE SYSTEM IS CLEAN *****
#
root@hush:~ # fsck
** /dev/gpt/rootfs (NO WRITE)
** Last Mounted on /mnt
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
LINK COUNT FILE I=2006450 OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 16:44 2021 COUNT 2 SHOULD BE 1
ADJUST? no
LINK COUNT FILE I=2006476 OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 17:00 2021 COUNT 2 SHOULD BE 1
ADJUST? no
LINK COUNT FILE I=2006506 OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 17:11 2021 COUNT 2 SHOULD BE 1
ADJUST? no
LINK COUNT FILE I=2006509 OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 17:33 2021 COUNT 2 SHOULD BE 1
ADJUST? no
UNREF FILE I=2006510 OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 17:44 2021
RECONNECT? no
CLEAR? no
UNREF FILE I=2006524 OWNER=operator MODE=100400
SIZE=0 MTIME=Mar 20 17:44 2021
RECONNECT? no
CLEAR? no
LINK COUNT FILE I=2006565 OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 16:33 2021 COUNT 2 SHOULD BE 1
ADJUST? no
LINK COUNT FILE I=2006585 OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 16:55 2021 COUNT 2 SHOULD BE 1
ADJUST? no
LINK COUNT FILE I=2006595 OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 17:22 2021 COUNT 2 SHOULD BE 1
ADJUST? no
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no
SUMMARY INFORMATION BAD
SALVAGE? no
BLK(S) MISSING IN BIT MAPS
SALVAGE? no
71667 files, 1002761 used, 26985631 free (5047 frags, 3372573 blocks, 0.0% fragmentation)
root@hush:~ #
root@hush:/ # fsck
** /dev/gpt/rootfs (NO WRITE)
** Last Mounted on /mnt
** Root file system
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=2006612 (20672 should be 20608)
CORRECT? no
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=2007178 OWNER=root MODE=100644
SIZE=197 MTIME=Mar 20 12:22 2021
RECONNECT? no
CLEAR? no
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no
SUMMARY INFORMATION BAD
SALVAGE? no
BLK(S) MISSING IN BIT MAPS
SALVAGE? no
71680 files, 1015643 used, 26972945 free (4945 frags, 3371000 blocks, 0.0% fragmentation)
root@hush:/ #
Is there anything to worry about? How to correct the block count error?