Re: [pfSense] OpenVPN client bug? "An IPv4 protocol was selected, but the selected interface has no IPv4 address" error
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 systems more times than I can count. What interface are you trying to bind it to? It actually does have v4 connectivity? I was trying to bind it to a local interface created for OpenVPN itself, to allow pfSense (as an OpenVPN client) to obtain IP itself from the remote OpenVPN server. The interface is assigned to Network port "ovpnc3" Since the port relies upon OpenVPN to obtain an IP, and OpenVPN refuses to allow me to configure anything without the port first having an IP, I'm stuck in a chicken-v-egg scenario. Or maybe I'm setting up my OpenVPN client connections entirely wrong? But I did have it working previously, and have it working again since I commented out this validation in the PHP code, thereby allowing the parameters to be saved and the connection to be updated. -- Dave Warren http://www.hireahit.com/ http://ca.linkedin.com/in/davejwarren Men are from Earth. Women are from Earth. Deal with it. ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] OpenVPN client bug? "An IPv4 protocol was selected, but the selected interface has no IPv4 address" error
On 12/21/2013 10:11 PM, Chris Buechler wrote: > On Thu, Nov 28, 2013 at 4:25 PM, Dave Warren 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 interface has no IPv4 address". The interface >> was properly configured using DHCPv4, and therefore has no IP address. >> > > 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 systems more times than I can > count. What interface are you trying to bind it to? It actually does > have v4 connectivity? I have hit that error when the DHCP interface was unplugged or had not yet obtained an IP. At those points it would fail that check. Jim ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
