Replying to Avatar jb55

thanks to an idea from nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h i was able to get my node up again.

basic idea is to have `persistentKeepalive = 25;` wireguard option from my home node to my VPS. then I ip forward the lightning port from my VPS to my home node over wireguard.

my zaps and lightning node should be working again. please test!

03f3c108ccd536b8526841f0a5c58212bb9e6584a1eb493080e7c1cc34f82dad71@ln.damus.io:9735

nostr:note1f0a9h0jcl6up920pllda6qvtmesaapuxlq80mw9cdvdmt9d39kasq3xj4t

I love this setup:

systemd-networkd: routing all traffic over WireGuard (section)

https://wiki.archlinux.org/title/WireGuard

(this knowledge is cross-linux, not just archlinux, btw ^^)

By leveraging it's built in routing, you don't have to set up nearly as many iptables to open up ports.

Reply to this note

Please Login to reply.

Discussion

I do something like that but only for some traffic (like torrents) using fwmarks and cgroups