On Sun, 2019-02-03 at 17:28 +0800, Ed Greshko wrote:
> On 2/3/19 5:15 PM, Patrick O'Callaghan wrote:
> > I may ask them about the current issue but am not very hopeful of a
> > solution. In any case I can work around it.
>
> In reading their web site, it seems the underlying technology is OpenVPN.
On Sat, 2019-02-02 at 14:43 -0800, Mike Wright wrote:
> On 2/2/19 4:22 AM, Patrick O'Callaghan wrote:
> > Last ditch left-field idea: I have a (commercial) VPN service which is
> > not normally turned on but does have a systemd daemon running. I turned
> > it off and everything started working.
> >
On 2/3/19 5:15 PM, Patrick O'Callaghan wrote:
> I may ask them about the current issue but am not very hopeful of a
> solution. In any case I can work around it.
In reading their web site, it seems the underlying technology is OpenVPN. So,
it isn't
clear to me why they would need specialized pro
On Sun, 2019-02-03 at 07:22 +0800, Ed Greshko wrote:
> On 2/3/19 1:55 AM, Patrick O'Callaghan wrote:
> > On Sat, 2019-02-02 at 09:02 -0500, Sam Varshavchik wrote:
> > > Ed Greshko writes:
> > >
> > > > Well, it would be good to
> > > >
> > > > Stop firewalld, dump the IPTables, start the VPN
