On Mon, Jan 19, 2015 at 3:56 PM, Jason McClung jason.mccl...@gmail.com wrote:
On 1/19/2015 1:27 PM, Erik Anderson wrote:
On Mon, Jan 19, 2015 at 3:16 PM, Oliver Hansen oliver.han...@gmail.com
wrote:
A bit of a guess but when I've had an issue with the OpenVPN GUI it was
something in my
On Mon, Jan 19, 2015 at 7:46 PM, Chris Buechler c...@pfsense.com wrote:
OP's issue is likely this one that's fixed in 2.2.
https://redmine.pfsense.org/issues/3894
where if an OpenVPN client is delayed trying to do a DNS lookup (or
potentially other causes, that seemed to be the only replicable
On 1/19/2015 1:27 PM, Erik Anderson wrote:
On Mon, Jan 19, 2015 at 3:16 PM, Oliver Hansen oliver.han...@gmail.com wrote:
A bit of a guess but when I've had an issue with the OpenVPN GUI it was
something in my OpenVPN Advanced Configuration section that I had added long
ago and was no longer
On Mon, Jan 19, 2015 at 3:16 PM, Oliver Hansen oliver.han...@gmail.com wrote:
A bit of a guess but when I've had an issue with the OpenVPN GUI it was
something in my OpenVPN Advanced Configuration section that I had added long
ago and was no longer necessary or conflicting in some way.
Thanks,
Hello all -
Running 2.1.5-RELEASE on a Soekris net6501-50.
Since the 2.1.4 release, I've seen this error message appear
incessantly on the dashboard:
http://photos.smugmug.com/photos/i-qwQLZCV/0/O/i-qwQLZCV.png
Despite the web GUI being unable to determine OpenVPN status, clients
continue to
