I can not find any power adapter recomended from Asrock...
Is DTK ok brand?
I can not find any power adapter recomended from Asrock...
Is DTK ok brand?
I'm currently building a second NAS based on an Asrock N100DC mbo.
I found an old power supply that, according to the label, meets the required specifications, but I would like to measure it just in case if it's correct, so I'm wondering what values it should have?
I'd also need a recommendation for a quality power supply that is available on amazon.de or aliexpress
A Leicke power supply was purchased for the first NAS, but given the many negative experiences I'd like something of a higher quality just in case. Unfortunately, I can't find the ones that Asrock recommends.
Maybe I worry too much, but that's me.
Everything is up but response time on Adguard home is slow for unboud... 103ms
Adguard home and Unbound are in docker containers on macval network and they have its own IPs.
I need help with best settings for this combination.
Adguard home is working ok but advice for best settings is very welcom.
With this settings Unbound i restarting...
# Unbound Configuration with DoT and DoH - proba
server:
# Listen on all interfaces (IPv4 and IPv6)
interface: 0.0.0.0
interface: ::0
port: 53
# Access Control (Restrict to Local Network)
access-control: 127.0.0.0/8 allow
access-control: 192.168.0.0/16 allow
access-control: 10.0.0.0/8 allow
access-control: ::1 allow
access-control: fe80::/10 allow
# Enable IPv4 and IPv6
do-ip4: yes
do-ip6: yes
# Enable UDP and TCP
do-udp: yes
do-tcp: yes
# Enable DNS-over-TLS (DoT)
tls-service-key: "/etc/unbound/unbound_server.key"
tls-service-pem: "/etc/unbound/unbound_server.pem"
tls-port: 853
tls-cert-bundle: "/etc/ssl/certs/ca-certificates.crt"
tls-ciphers: "TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384"
tls-ciphersuites: "TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384"
# Enable DNS-over-HTTPS (DoH)
https-port: 443
http-endpoint: "/dns-query"
http-service-key: "/etc/unbound/unbound_server.key"
http-service-pem: "/etc/unbound/unbound_server.pem"
http-query-buffer-size: 4k
http-response-buffer-size: 8k
# Enable DNSSEC validation
auto-trust-anchor-file: "/etc/unbound/root.key"
harden-dnssec-stripped: yes
# Enable caching
cache-min-ttl: 3600
cache-max-ttl: 86400
msg-cache-size: 100m
rrset-cache-size: 100m
# Prefetch popular domains
prefetch: yes
prefetch-key: yes
# Harden DNS responses for privacy and security
hide-identity: yes
hide-version: yes
harden-short-bufsize: yes
harden-large-queries: yes
harden-glue: yes
harden-below-nxdomain: yes
harden-referral-path: yes
qname-minimisation: yes
# Limit resource usage
num-threads: 2
so-rcvbuf: 4m
so-sndbuf: 4m
# Root Hints (Optional for better performance)
root-hints: "/etc/unbound/root.hints"
# Serve Expired (Optional for reliability)
serve-expired: yes
serve-expired-ttl: 3600
serve-expired-reply-ttl: 30
Display More
I'm not sure what I'm doing wrong, because after doing everything according to the instructions, I can access adguard in the LAN and ping from the host, but I can't see adguard outside the LAN through the wireguard vpn, which is also on the host.
Is it possible that iptables should also be set to forward to macvlan network in the wireguard settings?
Now I have it like this:
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o enp1s0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o enp1s0 -j MASQUERADE
Could this be a solution?
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -A FORWARD -i %i -o macvlan0 -j ACCEPT; iptables -A FORWARD -i macvlan0 -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o enp1s0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -D FORWARD -i %i -o macvlan0 -j ACCEPT; iptables -D FORWARD -i macvlan0 -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o enp1s0 -j MASQUERADE
Or maybe this?
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -A FORWARD -i %i -o macvlan0 -j ACCEPT; iptables -A FORWARD -i macvlan0 -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o enp1s0 -j MASQUERADE; iptables -t nat -A POSTROUTING -s 10.10.10.0/24 -d 192.168.1.0/24 -j ACCEPT
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -D FORWARD -i %i -o macvlan0 -j ACCEPT; iptables -D FORWARD -i macvlan0 -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o enp1s0 -j MASQUERADE; iptables -t nat -D POSTROUTING -s 10.10.10.0/24 -d 192.168.1.0/24 -j ACCEPT
EDIT:
Just to note that I am not using wireguard as an omv plugin but as an application installed on the host machine
Display MoreOh is possible!
Read here:
EXAMPLE:
Your network is 192.168.1.0/24
Your OMV's network adapter is "eno1"Pihole via MACVLAN is 192.168.1.200
You need to create a script like "macvlan_dummy.sh" or other (the name isn't important) like this:
#! /bin/bash
ip link add macvlan_dummy link eno1 type macvlan mode bridge
ip addr add 192.168.1.99/24 dev macvlan_dummy
ip link set macvlan_dummy up
ip route add 192.168.1.200/255.255.255.255 dev macvlan_dummy
Save the file inside the /root/
Launch: crontab -e
Add this line and save: @reboot /root/macvlan_dummy.sh
Launch: chmod +x macvlan_dummy.sh
Reboot.
Done.
If you want to try this script before, simply copy&paste in the prompt this, without #! /bin/bash:
ip link add macvlan_dummy link eno1 type macvlan mode bridgeip addr add 192.168.1.99/24 dev macvlan_dummy
ip link set macvlan_dummy up
ip route add 192.168.1.200/255.255.255.255 dev macvlan_dummy
Unfortunately, this script doesn't work for me. I have AdGuard Home on macvlan and this script does not connect me to it via VPN but to the openmediavault login
Unfortunately, I don't really manage with the settings in this Asrock bios for n100dc itx.
If anyone is willing to share their settings with me, I would be grateful.
Especially how to adjust pl1 and pl2.
I have one nvme ssd, one sata3 ssd, one 3.5" HDD, one 12cm fan connected to the mbo.
I use 19V 4.74A 90W power supply.
What CPU temperatures are normal for this CPU/MBO ?
Currently I have 55-60 °C on idle with one fan bellow CPU/MBO.
I found this on that forum.
Is this ok or I need some more adjusment?
I read what you linked and I have to admit that I didn't really understand it.
Can you explain to me, as in the instructions for idiots, how to set it in the bios to get 6W?
Thanks for the link.
I found some useful stuff there...
I also read there how someone's Leica power supply failed quickly 😱
I also ordered that power supply and I hope I won't have those problems.
I need a stable NAS to work 24/7
EDIT:
I was a little scared about that.
Do you have a better quality power supply that you would recommend?
Someone mentioned earlier that Asrock has boosted this mbo with N100 cpu a bit.
How do I adjust the settings so that they are not boosted to reduce heating?
Here's what Asrock customer support says:
...the chassis fan headers on N100DC-ITX provide 12V/2A.
Therefore, connecting two chassis fans (12V/0.2~0.5A) to each fan header should be no problem.
I see that the mbo has connections for only two fans.
I am wondering if I can install four fans?
I can solve this with PWM PST fans, but I don't know if I can do it because of the mbo itself and the 19V 4.74A power supply?
I'm going to buy an Asrock mbo, so please recommend a quality 19V power supply.
If possible, something that can be bought on amazon.de
Are there any significant differences between the mbos other than the power supply they use? I am concerned that some users who have an Asrock mbo are complaining about the appearance of strange noises such as buzzing and crackling.
In your opinion, which is better to buy Asrock N100DC or Asus Prime N100i-d d4?
I see that there is also an Asus Prime n100i-d d4-csm, but I don't know the difference between those Asus mbo
I did, but I still have the same problem.
I decided to go with fresh install of openmwdiavault 7
I would like to know if there is a 64-bit board that would replace the OdroidXU4 in the Cloudshell2 case.
I tried to upgrade from omv6 to omv7 twice, both times at the end there was a message that the upgrade was successful, but after the reboot I'm still on omv6 and bullseye.
I rum OMV on OdroidXU4 with armbian.
The sudo omv-salt stage run deploy command passed without error the first time, but now it throws a bunch of incomprehensible characters. After the omv-upgrade command I get a warning:
The following packages have been kept back: armbian-bsp-cli-odroidxu4 samba-common sources.list is like this:
# deb http://deb.debian.org/debian bookworm main contrib non-free
# deb-src http://deb.debian.org/debian bookworm main contrib non-free
deb http://deb.debian.org/debian bookworm-updates main contrib non-free
# deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free
#deb http://security.debian.org/ bookworm/updates main contrib non-free
## deb-src http://security.debian.org/ bookworm/updates main contrib non-free