![]() I have same problem as you, opevpn client not running and refused to cat some debugging, haven't really had any impact since the vpn connection has worked even though the gui states not running.Ĭould you elaborate on how you killed the client manually over ssh. I think the gui should report failure to shut down the openvpn client if the management socket isn't reachable.ĭo you have command for killing client manually over ssh? Seems like openvpn sometimes failes to create the management socket? I killed the client manually over ssh and after restarting it everything worked as intended. I tried stopping openvpn using the gui but since it seems to be using the management socket for shutting down the client as well this wasn't working. ![]() INFO:OpenVPN Management Interface Version 1 – type 'help' for more info It is apparantly the management socket for openvpn (client 5 for me) that refuses cat client5.sockĬat: client5.sock: Connection cat client6.sock Jan 2 13:09:41 openvpn: Initialization Sequence some debugging, haven't really had any impact since the vpn connection has worked even though the gui states not running. Jan 2 13:09:44 openvpn: TUN/TAP device ovpnc1 exists previously, keep at program end Jan 2 13:09:44 openvpn: Cannot open TUN/TAP dev /dev/tun1: Device busy (errno=16) Jan 2 13:09:44 openvpn: TUN/TAP device ovpnc2 exists previously, keep at program end Jan 2 13:09:44 openvpn: Cannot open TUN/TAP dev /dev/tun2: Device busy (errno=16) Jan 2 13:09:44 openvpn: Exiting due to fatal error Jan 2 13:09:46 openvpn: Peer Connection Initiated with ip:port ![]() Jan 2 13:09:46 openvpn: Initialization Sequence Completed Log after successful establishing tunnels after reboot: Usually the problem resolved in the past after rebooting, but this time the problem survived…Īlthough the issues is only annoying rather than problematic in any way (except for not letting me know when the tunnels are really down.), it would be nice if there was a persistent fix to this. After adjusting the interfaces, installing packages and moving /var and /tmp to RAM disks, I recognized that the GUI presents the error mentioned above. Just to follow a suggestion I did a fresh full-install of pfsense 2.1.5 i386 on a notebook with SSD and copied my config file to this installation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |