Search results for tag #wireguard
![[?]](https://media.norden.social/accounts/avatars/109/284/385/405/764/038/original/732419492b6f8c10.jpg)
Ein eigener Backupserver mit Debian, ZFS und BorgBackup
https://www.moellnitz.de/ein-eigener-backupserver-mit-debian-zfs-und-borgbackup/
#BorgBackup #Backupserver #Debian13 #Linux #ZFS #ZFSMirror #Datensicherung #Backupstrategie #Georedundanz #Datensouveränität #HetznerStoragebox #NAS #WireGuard #RTCWakeup #BackupAutomatisierung #SMARTMonitoring #Selfhosting
![[?]](https://media.burningboard.net/accounts/avatars/109/892/491/632/731/847/original/22ff3e71df4e5854.jpeg)
My YouTube kept stuttering and loading poorly on #Telekom in the evenings. Fix: selective policy routing on a #MikroTik running #RouterOS.
DNS FWD entries (youtube.com, googlevideo.com, ytimg.com …) dynamically populate an IPv6 address list. Mangle marks new connections; a dedicated routing table sends them through a WireGuard tunnel to route64.org (AS212895) instead of the Telekom default route. Plus NAT masquerade into the tunnel, TCP MSS clamping and a FastTrack exception. IPv4 to YouTube targets is rejected → true IPv6-only.
Mein #YouTube ruckelte abends bei der #Telekom. Lösung: selektives Policy-Routing auf einem #MikroTik mit #RouterOS
DNS-FWD-Einträge (youtube.com, googlevideo.com, ytimg.com …) füllen dynamisch eine #IPv6 Adressliste. #Mangle markiert neue Verbindungen; eine eigene Routing-Tabelle leitet sie über einen WireGuard-Tunnel zu route64.org (AS212895) statt über die Telekom-Defaultroute. Dazu NAT-Masquerade in den Tunnel, TCP-MSS-Clamping und FastTrack-Ausnahme. IPv4 zu YouTube per reject gesperrt → IPv6-Only.
Mein YouTube ruckelte abends bei der #Telekom. Lösung: selektives Policy-Routing auf einem #MikroTik mit #RouterOS.
DNS-FWD-Einträge (youtube.com, googlevideo.com, ytimg.com …) füllen dynamisch eine IPv6-Adressliste. Mangle markiert neue Verbindungen; eine eigene Routing-Tabelle leitet sie über einen WireGuard-Tunnel zu route64.org (AS212895) statt über die Telekom-Defaultroute. Dazu NAT-Masquerade in den Tunnel, TCP-MSS-Clamping und FastTrack-Ausnahme. IPv4 zu YouTube per reject gesperrt → IPv6-Only.
My YouTube kept stuttering and loading poorly on #Telekom in the evenings. Fix: selective policy routing on a MikroTik running #RouterOS.
DNS FWD entries (youtube.com, googlevideo.com, ytimg.com …) dynamically populate an IPv6 address list. Mangle marks new connections; a dedicated routing table sends them through a WireGuard tunnel to route64.org (AS212895) instead of the Telekom default route. Plus NAT masquerade into the tunnel, TCP MSS clamping and a FastTrack exception. IPv4 to YouTube targets is rejected → true IPv6-only.
Mein YouTube ruckelte abends bei der #Telekom. Lösung: selektives Policy-Routing auf einem MikroTik mit #RouterOS.
DNS-FWD-Einträge (youtube.com, googlevideo.com, ytimg.com …) füllen dynamisch eine IPv6-Adressliste. Mangle markiert neue Verbindungen; eine eigene Routing-Tabelle leitet sie über einen WireGuard-Tunnel zu route64.org (AS212895) statt über die Telekom-Defaultroute. Dazu NAT-Masquerade in den Tunnel, TCP-MSS-Clamping und FastTrack-Ausnahme. IPv4 zu YouTube per reject gesperrt → IPv6-Only.
![[?]](https://files.mastodon.social/accounts/avatars/108/288/607/816/054/957/original/44ef33fd13454e94.png)
WireGuard Easy 15.5 adds AmneziaWG 3.1 support, security fixes, configurable WireGuard interfaces, and improved proxy handling.
https://linuxiac.com/wireguard-easy-15-5-adds-amneziawg-3-1-support-security-fixes/
Alt...
WireGuard Easy 15.5 adds AmneziaWG 3.1 support, security fixes, configurable WireGuard interfaces, and improved proxy handling.
![[?]](https://polymaths.social/fileserver/01HCMX6M1CZNEVJ4F5H58TT5XJ/attachment/original/01M5TMWZCPKPS22X34CSPX7W4G.webp)
🍵 
[Hey #NetBSD guys,
How do you set up #WireGuard? wg-quick isn't available for NetBSD from what I can tell. I got wireguard-go to create the tun0 interface, but when I try to feed the config file to it, I get a parsing error:
rld@discovery:~$ doas wg setconf tun0 /etc/wireguard/protonvpn.conf
Line unrecognized: `Address=10.~~~.~~~.~~~/32,2a07:~~~~::2:2/128'
Configuration parsing error
rld@discovery:~$
(~~~=redacted)
![[?]](https://files.mastodon.social/accounts/avatars/000/033/565/original/48537eb7c14b6502.png)
🟠 Nouvel article sur le blog !
Aujourd'hui petit article rapide AppArmor qui cause quelques petits soucis à wg-quick sous Ubuntu 26.04.
Bonne lecture ! 😃
#WireGuard #AppArmor #Ubuntu #SysAdmin
Alt...
Couverture de l'article : Logos des WireGuard et de AppArmor en blanc sur fond rouge
![[?]](https://files.mastodon.online/accounts/avatars/000/083/568/original/0c48ac7d28dba767.jpg)
Finally got around to playing with #headscale and it's pretty great! I hadn't used #TailScale before, though I've done #wireguard stuff in some way for years.
![[?]](https://social.patpro.net/fileserver/01CGJ0J327W2AD6G9YJK2G8HQ7/attachment/original/01JPQFGGTA0ZRR71JD8BS0XPP4.jpeg)
Is there a way to debug the (non) connection between a wireguard client inside a FreeBSD Jail, and a remote wireguard server (on a FreeBSD host)?
It looks like nothing gets out of the Jail, so tcpdump is probably not the tool I need right now.
I wish I could get debug logs from the client, but I got nothing.
![[?]](https://assets.chaos.social/accounts/avatars/108/130/304/763/556/365/original/99f7d524529dce65.jpg)
So, the onboard SBC in my van wasn't reachable from via #Wireguard today.
I first suspected that the wg-quick service hadn't been started correctly, but it had.
However, `sudo wg` listed 172.31.255.254 as the IP address of my VPN server (I run Wireguard mostly in a star topology).
My guess is that the LTE modem that provides the uplink had some kind of connection problem and turned into a captive portal, responding to every DNS query with its own IP. And Wireguard only looks up the host once.