woof
Remote
MOVED TO @julia@eepy.moe (Julia 
)
@julia@snug.moe
iceshrimp 2026.5.1
Unfunny linux user. Code gremlin. Container addict.
Before you try to follow me, PLEASE HAVE A BIO AND AT LEAST A FEW POSTS! Thank you in advance.
I try to add alt text to all the images and videos that I post, but I may boost content without alt text.
alert("You should sanitize YOUR html NOW *lowtiergod.jpg*")
830 Followers
544 Following
10 Posts
EDIT: Apparently, systemd-networkd was being a fuck
PLEASE BOOST THIS
What is wrong with this config on wireguard (wireguard-tools version v1.0.20210914)? The intent is to allow the clients to connect and access internyal nodes, while also being able to access the internet, with all of their traffic proxied through the VPN. This used to work on prior versions of WireGuard. I don't understand why it doesn't work now.
Server config:
[Interface]
Address = 10.0.0.1/24
ListenPort =
PrivateKey =
PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
[Peer]
PublicKey =
AllowedIPs = 10.0.0.2/32Client config:
[Interface]
PrivateKey =
Address = 10.0.0.2/24
DNS = 8.8.8.8
[Peer]
PublicKey =
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint =
PersistentKeepalive = 30flossing in front of my boyfriend while my server is just positively fucked as a coping mechanism
I don't fucking know what Intel VT-D is but fuck that
routers shouldn't be able to tell me what DNS sever to use
that's fucking dunb
looks like a known kernel regression, fuck my life
I hate everything
chat how do I:
- proxy all ipv4 & ipv6 traffic through a wireguard connection
- while also allowing domain names from the outside world to resolve, including a DNS server
aaaaaaaaaaaaaaaaaaaaaaaaand wireguard is fucked
where were you in the great eepy moe outage of November 2024