![]() ![]() Please see below for entries logged in the syslog when connecting with NM, there appear to be errors relating to assigning an address to tun0:įeb 23 21:46:00 laptop NetworkManager: Starting VPN service 'org.freedeskto p.NetworkManage r.openvpn'. Have also checked bug #610361 but this appears to be a different issue. This does not seem to be a problem importing OpenVPN configs (have seen this logged elsewhere also) as the issue is also apparent if the connection is created manually within NM. ![]() On examination of the routing table there are some differences (NM adds a route with 32 bit mask to the VPN server via the machine's default gateway) but removal of this route makes no difference, even with the route table identical to when connected to a working VPN in terminal, the NM spawned VPN still will not pass traffic. Importing the same config file into NM creates a working VPN connection in as much as it connects to the VPN server, but no traffic passes. I have a working nf using which I can connect at the terminal using openvpn nf. Using Maverick I have found that it is impossible to connect to an OpenVPN server using network manager. Binary package hint: network- manager- openvpn
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |