It's currently a bit tricky for me getting into the box physically. If only I had SSH access ha!
I'm almost 100% certain that returning packets are being routed over the tun0 (new default route) interface instead of em0. Thanks > -------- Original Message -------- > Subject: Re: Running OpenVPN as a client breaks SSH access into same box? Is > it a problem with default route being changed? > Local Time: 24 October 2017 10:13 PM > UTC Time: 24 October 2017 20:13 > From: kgo...@gmail.com > To: tec...@protonmail.com <tec...@protonmail.com> > > you are more likely to receive help if you post the output of > "ifconfig -a" and "netstat -nr" commands. > > On Tue, Oct 24, 2017 at 4:06 PM, tec...@protonmail.com > tec...@protonmail.com wrote: > >> Hi, >> I have a very very basic setup. Not using any other pf rules other than what >> comes default with 6.2-Release and almost every other release. Running >> OpenVPN works without a problem - able to connect as a client to a remote >> OpenVPN server. Everything is properly routing, verified by checking my IP. >> Problem is that as soon as OpenVPN is running, I cannot SSH in to my OpenBSD >> machine from any other machine on the Lan. Now, I'm guessing this has >> something to do with the default route being changed automatically by >> OpenVPN but I am still a total newbie with routing and pf so I have not a >> clue how to fix this, especially in any sort of manner which I can safely >> assume it to be the correct way. >> Can someone tell me how to resolve this? Thanks
