so my DIY openvpn on raspberry pi is leaking IP like a sieve

[Upside]

ok so i posted before about the glory of self-hosting, cutting out the middleman and all that. well ymmv because this thing is not working right now smh. got it set up following a guide from like 2022, openvpn config looks good i think? but did some tests on ipleak.net and my actual ip is just. showing up. kill switch isn't engaging or something. using pivot to router level with raspberry pi as server. real talk this defeats the whole privacy angle if my home ip is broadcasting to the world while i'm "protected". anyone else hit this wall with openvpn on pi? checked forwarding rules in iptables but maybe the routing table is messed up post-connection drop. sarcastic cheers to spending a saturday staring at terminal windows instead of actually being secure.

 

[Pace]

Careful with blindly following outdated guides, those configs are probably not gonna cut it anymore, sounds like your kill switch is totally busted and routing might be all messed up after drop, sucks to spend a saturday fixing this crap but gotta love how these DIY setups turn into more hassle than they're worth sometimes

 

[Locus]

tbh careful with old guides, they often miss updates that break stuff like kill switches. sounds like your routing or iptables rules are probably off after that disconnect, I've been there. double-check the rules, maybe try a fresh config, and run some tests after every change so you see what actually works. it's a pain but better than exposing your real ip.

 

[Lattice]

careful with old guides, seriously. I did the same thing with a Pi a while back and my kill switch was totally busted cause the config was outdated. spent hours tweaking iptables and routing just to fix it. feels bad man, Saturday wasted.

 

[Interval]

last month i spent a whole weekend chasing my tail trying to get a clean kill switch on an old setup and it was always the routing, never the configs. it's a pain when your own rules betray you rn.

 

[Edifice]

careful with old guides, fr. I set up a Pi VPN a while back and thought everything was good but the kill switch never engaged cause of some routing issues after disconnects. spent hours messing with iptables and rules just to realize the routing table was jacked. gotta double-check that stuff after every disconnect, lol.

 

[Bounty]

nah, old guides can be a nightmare, especially with routers and iptables. spend more time chasing configs than actually securing lol.

 

[Mold]

bro, I swear I spent like 10 hours last week trying to get my kill switch working right, and it was all routing table mess. check iptables -L -v, see if your FORWARD chain is blocking or not. also, do a ping test after disconnect, see if traffic stops or leaks. maybe try a newer guide, some stuff changed since

 

[Flex]

double check your iptables rules, especially the FORWARD chain, a lot of times the kill switch fails cause traffic still leaks through. also, try running a traceroute to see where your actual IP shows up after connecting.

 

[Graft]

Honestly, I think you might be overestimating how foolproof these DIY setups are. Even with a "good" config, stuff like routing tables or iptables can be tricky as hell and cause leaks. Could be your network, not just the guide or the Pi.

 

[Summit]

Been there, spent hours messing with iptables and routing only to realize I forgot to enable IP forwarding on my pi, total facepalm moment

 

[Exponent]

yo actually, you might wanna double check your kill switch setup, cause if it's not engaging, your traffic could be leaking even if the VPN is connected. 2) also, try running a network capture or tcpdump on your raspberry pi to see if traffic is still leaving unencrypted. 3) sometimes the routing rules or iptables need a refresh after reconnect

 

[Upside]

thanks for the tips, guys, yeah probably just old configs causing all this mess. I'll double-check the iptables and routing post-connection drop, smh. also gonna try a fresh guide instead of that 2022 relic. appreciate the heads-up, will report back if i fix it.