Re: Running OpenVPN as a client breaks SSH access into same box? Is it a problem with default route being changed?

2017-10-24 Thread tec...@protonmail.com
I will have a look into this tonight and see if I can figure it out with that. Thank you > 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:28 PM >

Re: Running OpenVPN as a client breaks SSH access into same box? Is it a problem with default route being changed?

2017-10-24 Thread Daniel Jakots
On Tue, 24 Oct 2017 16:25:08 -0400, "tec...@protonmail.com" wrote: > 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)

Re: Running OpenVPN as a client breaks SSH access into same box? Is it a problem with default route being changed?

2017-10-24 Thread tec...@protonmail.com
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

Running OpenVPN as a client breaks SSH access into same box? Is it a problem with default route being changed?

2017-10-24 Thread tec...@protonmail.com
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