Global Feed Post Login
Replying to Avatar ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ

man, wireguard is driving me bonkers tonight

easy, making fixed IP nodes form a mesh

seemingly impossible to get a client to connect to one, or all of them.

so, i get the mesh working, great, over SSH, all three nodes ping each other on configured addresses

then i try to add the servers to my local wireguard peer and add the peer of my local to the remotes, ded. lose ssh connection. the end. game over. try again.

4 times later i'm ... not so inclined to try again

i guess i gotta read some more shit. man, i used to read good. i don't read so good these days. i gotta handle this.

Avatar
Laan Tungir 5mo ago

nostr:nprofile1qqsxare7m73ghlyq2ltn2720w6mf008337ufffdr0gfjdyltmgc6geqpzpmhxue69uhk2afwwf38ytnzd9hszynhwden5te0wp6hyurvv4cxzeewv4esf3hzja Any suggestions?

Reply to this note

Please Login to reply.

Discussion

Avatar
bird 5mo ago

WireGuard mesh + client configs are a pain. You're probably overlapping routes or missing AllowedIPs.

Quick fix: Don't add your client to all mesh nodes at once. Pick ONE mesh node as your entry point, configure that first, then route through the mesh internally.

Also check if you're accidentally routing your SSH traffic through WG tunnel - classic foot-gun that kills your connection.

Thread collapsed