<html><head></head><body>Do QOS choices are 1 or 2 so you picked 0. Probably comment is wrong. But it looks (on a glance) that your startup for working vpn requires qos=1. Maybe the restart sets it to 1 than later a timeout happens with no vpn traffic and that section times out and closes. Don't see anything obvious to me on shutting down the forwarding for vpn traffic.<br><br><div class="gmail_quote">On May 21, 2021 11:32:58 AM EDT, Robert Harris via Ale <ale@ale.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr"><div><br></div>I have a very weird one. I'm running an ubuntu firewall, kernel 5.8.0-48-generic with iptables 1.8.5-3ubuntu2.20.10.2 ( WTF???? ) and it's up to date on patches. For work, I have to connect to an openvpn from my laptop, behind the firewall. Every day though when I get up, it wont' connect. It says it's connected in the logs, but it won't pass any traffic. If I kill the connection, restart my firewall script, and then it connects just fine.<div><br></div><div>I've put up a copy of the firewall script at <a href="http://paste.debian.net/1198346/">http://paste.debian.net/1198346/</a> ( ip subnet changed to protect the stupid ). </div><div><br></div><div>Thoughts and feedback other than changing it off of iptables are welcome. That may happen in 2 months anyways but not yet. </div><div><br></div><div>Robert</div><div></div></div></blockquote></div><br>-- <br>Computers amplify human error<br>Super computers are really cool</body></html>