I took a look at it. From what I understand, some of those lines in your setup is redundant. And the final product seems to do the exact same job as mine. In any case, if it works, it works.
Comment on Ditching the VPN and port forwarding the selfhosted way
ntn888@lemmy.ml 2 weeks agoThanks for the feed back. I started out with that post I referenced in my article, which had fewer entries. It didn’t work. Caveat was although the online port checkers were reporting the port as open, it was not actually making through the tunnel!
I actually solved it by asking chatgpt!! I put in the suggestions and it worked. I’m also no expert on creating iptables, but once it was in place it seemed self explanatory.
I ran netcat as client-server to test it actually worked.
SexualPolytope@lemmy.sdf.org 2 weeks ago
andscape@feddit.it 2 weeks ago
Idk man, it seems pretty irresponsible to me to write a blogpost with stuff that you got from ChatGPT without understanding it. People will assume that if you wrote a blogpost on this then you know what you’re doing. ChatGPT gets stuff wrong all the time, and we’re talking about firewall configuration here. If it misconfigured some stuff it could leave you and your readers vulnerable to all kinds of shit.
In this case it seems to me that (luckily) there’s just a bunch of redundant routing, but the next time it could be leaking your and your readers’ torrent traffic out of the VPN tunnel, leaving you vulnerable to legal repercussions for piracy.
Please don’t authoritatively post stuff that you got from the automatic bullshit generator without understanding it.
ntn888@lemmy.ml 2 weeks ago
I understand what you mean. It’s become a habit of mine lately, and I learn lots in the discussion to.
In my defence I did run some tests and confirm it’s functioning.