This also triggered my PTSD from absolute cluster fuck that is the official Miku PC build
Smash
joined 2 years ago
Just do Teto x Miku instead
Looks lile crap (tbf all of ASUS "gaming" products look terrible)
Modding your hardware yourself is always the best option to not make it look tacky
Some are very easy to get, but you don't want those
Monogatari Series and Railgun
Her oldest videos don't ^^ I have nothing against suggest content on YT, but Google always tries to babysit and degrades everything to YT kids level
Pack den RPI am besten in ein eigenes Netzwerk (DMZ). Die Sicherheit hängt dann maßgeblich von deinem Webfrontend ab, du solltest eine sichere Authentisierung nutzen (etwa mit MFA oder Zertifikat). Ansonsten noch das übliche, immer sofort die neusten updates installieren und hardening wie strike firewall Regeln, geo restriction und fail2ban nutzen.
Basically all programs which enable file sharing via your Internet connection. Germany is notorious for having a huge amount of lawyers which are only dedicated to tracking down and file a copy right infringement (or worse) case against people, who had unlawful actions done over their IP. And if you can't pay your fines, jail time is waiting.
Going to Jail in Germany speedrun any%
Then let it be 1:1,002 but not 1:35 or what ever the fuck translators sometime fantasize together
Properly not as bad as the shit their human translator pull all the time -completely altering sentences and words instead of a faithful 1:1 translation
I tried debugging this issue for hours now but I'm out of ideas. I'm running WireGuard on my OPNsense firewall. It worked flawlessly for about a year but now I've gotten a really strange issue.
Here is the Client config:
As you can see, the Client got assigned the IP 10.10.10.11/32
I can ping this IP and the Client can access all Server in the network when connected with the VPN.
BUT when it connects to hosts in the LAN, it doesn't use it's assigned 10.10.10.11 IP but the public IP of the OPNsense firewall instead.
This also doesn't happen every time, but most of the time. I assume that it's perhaps a ARP issue, but I don't know why the OPNsense firewall sends its public IP (WireGuard Endpoint IP) instead of the Clients assigned IP at all.
The IP the Client should use in the LAN (virtual VPN IP):
The IP which the Client actually uses (Endpoint IP):
Every help would be greatly appreciated!
EDIT: I removed and re-added the peers in OPNsense and it works again, at least for now. Maybe something broke during an update(?). I will report back if this already fixed the issue (the problem can sometimes be hard to replicate)
EDIT 2: The issue reappeared. But I noticed, that I now have the problem only with Gecko based browsers, chromium works fine (tested on Android).
EDIT 3: The issue only appeared with Gecko based browsers because mine are configured to use some public DOH DNS, which resolved my internal host FQDNs to public IPs, not private ones from the LAN
view more: next ›
Fucking censorship for the China/US