Bug #5132
closedOpenVPN error after upgrade to 2.2.4
0%
Description
After upgrading to pfSense 2.2.4, the OpenVPN service doesn't create the neccessary routes:
Sep 14 04:16:51 openvpn88741: Initialization Sequence Completed
Sep 14 04:16:51 openvpn88741: Peer Connection Initiated with [AF_INET]xxx.xxx.xxx.xxx:5097
Sep 14 04:16:47 openvpn88741: UDPv4 link remote: [undef]
Sep 14 04:16:47 openvpn88741: UDPv4 link local (bound): [AF_INET]yyy.yyy.yyy.yyy:1195
Sep 14 04:16:47 openvpn88741: /usr/local/sbin/ovpn-linkup ovpns2 1500 1637 192.168.100.1 255.255.255.0 init
Sep 14 04:16:47 openvpn88741: /sbin/ifconfig ovpns2 192.168.100.1 netmask 255.255.255.0 mtu 1500 up
Sep 14 04:16:47 openvpn88741: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sep 14 04:16:47 openvpn88741: TUN/TAP device /dev/tap2 opened
Sep 14 04:16:47 openvpn88741: TUN/TAP device ovpns2 exists previously, keep at program end
Sep 14 04:16:47 openvpn88741: OpenVPN ROUTE: failed to parse/resolve route for host/network: 10.0.100.0
Sep 14 04:16:47 openvpn88741: OpenVPN ROUTE: OpenVPN needs a gateway parameter for a --route option and no default was specified by either --route-gateway or --ifconfig options
Sep 14 04:16:47 openvpn88741: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Sep 14 04:16:47 openvpn88614: library versions: OpenSSL 1.0.1l-freebsd 15 Jan 2015, LZO 2.09
Sep 14 04:16:47 openvpn88614: OpenVPN 2.3.7 amd64-portbld-freebsd10.1 [SSL (OpenSSL)] [LZO] [MH] [IPv6] built on Jun 19 2015
Sep 14 04:16:47 openvpn46807: SIGTERM[hard,] received, process exiting
Sep 14 04:16:47 openvpn46807: /usr/local/sbin/ovpn-linkdown ovpns2 1500 1637 192.168.100.1 255.255.255.0 init
Sep 14 04:16:47 openvpn46807: event_wait : Interrupted system call (code=4)
Updated by Chris Buechler almost 10 years ago
- Status changed from New to Feedback
- Affected Version deleted (
2.2.4) - Affected Architecture added
- Affected Architecture deleted (
amd64)
Root problem is:
OpenVPN needs a gateway parameter for a --route option and no default was specified by either --route-gateway or --ifconfig options
which usually indicates the config wasn't right to begin with.
what version did you upgrade from? What type of connection is this?
Updated by Zoltan Beck over 9 years ago
I don't know if it is the right behavior but if I use TUN mode then it works finally, but if I set TAP mode then not. I'm not sure if it's a bug or not?
Updated by Chris Buechler over 9 years ago
- Status changed from Feedback to Not a Bug
You're trying to add a route on a tap OpenVPN instance in a way that's not valid. That didn't change after upgrading.