On 2013-12-23 04:31, Chris Buechler wrote:
It shouldn't allow you to pick that, and I'm surprised it worked when
you did in the past (probably we ignored the fact you had it set that
way). It's right to reject it, but for a different reason than it's
telling you. You can't bind the outside of an
On Sun, Dec 22, 2013 at 11:27 PM, Dave Warren da...@hireahit.com wrote:
On 2013-12-21 19:11, Chris Buechler wrote:
DHCP interfaces have an IP, and would not fail that check. I just
configured an OpenVPN client instance on a DHCP interface and it works
fine, and have done it on production 2.1
On 12/21/2013 10:11 PM, Chris Buechler wrote:
On Thu, Nov 28, 2013 at 4:25 PM, Dave Warren da...@hireahit.com wrote:
I have a number of OpenVPN client sessions set up (where my pfSense connects
to a remote OpenVPN server as a client)
Today I needed to switch one from TCP to UDP and received
On Thu, Nov 28, 2013 at 4:25 PM, Dave Warren da...@hireahit.com wrote:
I have a number of OpenVPN client sessions set up (where my pfSense connects
to a remote OpenVPN server as a client)
Today I needed to switch one from TCP to UDP and received An IPv4 protocol
was selected, but the selected
I have a number of OpenVPN client sessions set up (where my pfSense
connects to a remote OpenVPN server as a client)
Today I needed to switch one from TCP to UDP and received An IPv4
protocol was selected, but the selected interface has no IPv4 address.
The interface was properly configured
