OPNsense Forum
Archive => 18.1 Legacy Series => Topic started by: Lumpy on February 14, 2018, 01:22:48 pm
-
Since the Upgrade to 18.1 I've got a strange issue with my openvpn server configuration. The GUI has issues to connect to the daemon, see screenshot and logfile
Feb 10 10:27:59 OPNsense openvpn[25551]: OpenVPN 2.4.4 amd64-portbld-freebsd11.1 [SSL (OpenSSL)] [LZO] [LZ4] [MH/RECVDA] [AEAD] built on Jan 22 2018
Feb 10 10:27:59 OPNsense openvpn[25551]: library versions: OpenSSL 1.0.2n 7 Dec 2017, LZO 2.10
Feb 10 10:27:59 OPNsense openvpn[26175]: MANAGEMENT: unix domain socket listening on /var/etc/openvpn/server1.sock
Feb 10 10:27:59 OPNsense openvpn[26175]: WARNING: using --duplicate-cn and --client-config-dir together is probably not what you want
Feb 10 10:27:59 OPNsense openvpn[26175]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Feb 10 10:27:59 OPNsense openvpn[26175]: Diffie-Hellman initialized with 2048 bit key
Feb 10 10:27:59 OPNsense openvpn[26175]: Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Feb 10 10:27:59 OPNsense openvpn[26175]: Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Feb 10 10:27:59 OPNsense openvpn[26175]: ROUTE_GATEWAY x.y.z/255.255.255.255 IFACE=pppoe0 HWADDR=00:00:00:00:00:00
Feb 10 10:27:59 OPNsense openvpn[26175]: TUN/TAP device ovpns1 exists previously, keep at program end
Feb 10 10:27:59 OPNsense openvpn[26175]: Cannot open TUN/TAP dev /dev/tun1: Device busy (errno=16)
Feb 10 10:27:59 OPNsense openvpn[26175]: Exiting due to fatal error
Feb 10 10:29:25 OPNsense openvpn[79034]: OpenVPN 2.4.4 amd64-portbld-freebsd11.1 [SSL (OpenSSL)] [LZO] [LZ4] [MH/RECVDA] [AEAD] built on Jan 22 2018
Feb 10 10:29:25 OPNsense openvpn[79034]: library versions: OpenSSL 1.0.2n 7 Dec 2017, LZO 2.10
Feb 10 10:29:25 OPNsense openvpn[79210]: MANAGEMENT: unix domain socket listening on /var/etc/openvpn/server1.sock
Feb 10 10:29:25 OPNsense openvpn[79210]: WARNING: using --duplicate-cn and --client-config-dir together is probably not what you want
Feb 10 10:29:25 OPNsense openvpn[79210]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Feb 10 10:29:25 OPNsense openvpn[79210]: Diffie-Hellman initialized with 2048 bit key
Feb 10 10:29:25 OPNsense openvpn[79210]: Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Feb 10 10:29:25 OPNsense openvpn[79210]: Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Feb 10 10:29:25 OPNsense openvpn[79210]: ROUTE_GATEWAY x.y.z/255.255.255.255 IFACE=pppoe0 HWADDR=00:00:00:00:00:00
Feb 10 10:29:25 OPNsense openvpn[79210]: TUN/TAP device ovpns1 exists previously, keep at program end
Feb 10 10:29:25 OPNsense openvpn[79210]: Cannot open TUN/TAP dev /dev/tun1: No such file or directory (errno=2)
Feb 10 10:29:25 OPNsense openvpn[79210]: Exiting due to fatal error
Feb 10 10:34:31 OPNsense openvpn[40849]: OpenVPN 2.4.4 amd64-portbld-freebsd11.1 [SSL (OpenSSL)] [LZO] [LZ4] [MH/RECVDA] [AEAD] built on Jan 22 2018
Feb 10 10:34:31 OPNsense openvpn[40849]: library versions: OpenSSL 1.0.2n 7 Dec 2017, LZO 2.10
Feb 10 10:34:31 OPNsense openvpn[40991]: MANAGEMENT: unix domain socket listening on /var/etc/openvpn/server1.sock
Feb 10 10:34:31 OPNsense openvpn[40991]: WARNING: using --duplicate-cn and --client-config-dir together is probably not what you want
Feb 10 10:34:31 OPNsense openvpn[40991]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Feb 10 10:34:31 OPNsense openvpn[40991]: Diffie-Hellman initialized with 2048 bit key
Feb 10 10:34:31 OPNsense openvpn[40991]: Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Feb 10 10:34:31 OPNsense openvpn[40991]: Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Feb 10 10:34:31 OPNsense openvpn[40991]: ROUTE_GATEWAY x.y.z/255.255.255.255 IFACE=pppoe0 HWADDR=00:00:00:00:00:00
Feb 10 10:34:31 OPNsense openvpn[40991]: TUN/TAP device ovpns1 exists previously, keep at program end
Feb 10 10:34:31 OPNsense openvpn[40991]: TUN/TAP device /dev/tun1 opened
Feb 10 10:34:31 OPNsense openvpn[40991]: do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Feb 10 10:34:31 OPNsense openvpn[40991]: /sbin/ifconfig ovpns1 10.0.8.1 10.0.8.2 mtu 1500 netmask 255.255.255.255 up
Feb 10 10:34:32 OPNsense openvpn[40991]: /usr/local/etc/inc/plugins.inc.d/openvpn/ovpn-linkup ovpns1 1500 1622 10.0.8.1 10.0.8.2 init
Feb 10 10:34:32 OPNsense openvpn[40991]: /sbin/route add -net 10.0.8.0 10.0.8.2 255.255.255.0
Feb 10 10:34:32 OPNsense openvpn[40991]: Could not determine IPv4/IPv6 protocol. Using AF_INET
Feb 10 10:34:32 OPNsense openvpn[40991]: Socket Buffers: R=[42080->42080] S=[57344->57344]
Feb 10 10:34:32 OPNsense openvpn[40991]: UDPv4 link local (bound): [AF_INET]x.y.z
Feb 10 10:34:32 OPNsense openvpn[40991]: UDPv4 link remote: [AF_UNSPEC]
Feb 10 10:34:32 OPNsense openvpn[40991]: MULTI: multi_init called, r=256 v=256
Feb 10 10:34:32 OPNsense openvpn[40991]: IFCONFIG POOL: base=10.0.8.4 size=62, ipv6=0
Feb 10 10:34:32 OPNsense openvpn[40991]: Initialization Sequence Completed
The connection itself from my client to the server works fine, no errors etc. I'm not sure how to fix that. Any suggestions? Thanks in advance.
-
See https://github.com/opnsense/core/issues/1931
Cheers,
Franco
-
So bug is acknowledged but will be fixed at a later date?
-
As it does not affect operation it's low on priority, yes. All coding help to move this along quicker is welcome.
Cheers,
Franco