On Sun, Dec 22, 2013 at 11:27 PM, Dave Warren <[email protected]> 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 [email protected] http://lists.pfsense.org/mailman/listinfo/list
