Re: [pfSense] OpenVPN client bug? An IPv4 protocol was selected, but the selected interface has no IPv4 address error
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 OpenVPN tunnel to the inside. You'd be telling it to use the VPN to connect to the VPN. It has to be on the proper WAN. Interesting, when I had it set to a WAN in the past it gave me an error about the interface already being assigned or something to that extent, so I read up and found some directions that suggested setting it to the OpenVPN tunnel itself. I'll experiment once I'm back in the office and see what happens if I change it to a WAN. Thanks. -- Dave Warren http://www.hireahit.com/ http://ca.linkedin.com/in/davejwarren Light travels faster than sound. This is why some people appear bright until you hear them speak... ___ 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 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 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 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 OpenVPN tunnel to the inside. You'd be telling it to use the VPN to connect to the VPN. It has to be on the proper WAN. ___ 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 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 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
Re: [pfSense] OpenVPN client bug? An IPv4 protocol was selected, but the selected interface has no IPv4 address error
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 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? ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
[pfSense] OpenVPN client bug? An IPv4 protocol was selected, but the selected interface has no IPv4 address error
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.
After banging my head comparing this VPN with other established/working
VPNs and getting no-where, I started getting through the code to find
this gem:
pfsense /usr/local/www/vpn_openvpn_client.php
} elseif ((stristr($pconfig['protocol'], 6) === false)
!get_interface_ip($iv_iface) ($pconfig['interface'] != any)) {
$input_errors[] = gettext(An IPv4 protocol was
selected, but the selected interface has no IPv4 address.);
So basically it is currently impossible to create or modify any OpenVPN
client pipe that uses DHCP, as the IP (which isn't known until the
OpenVPN client connects, and is dynamic) must be hard-coded into the
interface before the connection is created.
Commenting out the offending PHP allowed me to save changes and
successfully connect to the VPN.
While this code likely makes sense when setting up and OpenVPN server,
it should not apply when setting up an OpenVPN client.
Am I missing something or is this a bug?
--
Dave Warren
http://www.hireahit.com/
http://ca.linkedin.com/in/davejwarren
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
