OpenVPN connects but doesn't pass traffic

Binary package hint: network-manager-openvpn

Using Maverick I have found that it is impossible to connect to an OpenVPN server using network manager. I have a working client.conf using which I can connect at the terminal using openvpn client.conf. 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. 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.

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. Have also checked bug #610361 but this appears to be a different issue.

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:

[code]
Feb 23 21:46:00 laptop NetworkManager[17366]: <info> Starting VPN service 'org.freedesktop.NetworkManager.openvpn'...
Feb 23 21:46:00 laptop NetworkManager[17366]: <info> VPN service 'org.freedesktop.NetworkManager.openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 18245
Feb 23 21:46:00 laptop NetworkManager[17366]: <info> VPN service 'org.freedesktop.NetworkManager.openvpn' appeared, activating connections
Feb 23 21:46:00 laptop NetworkManager[17366]: <info> VPN plugin state changed: 1
Feb 23 21:46:00 laptop NetworkManager[17366]: <info> VPN plugin state changed: 3
Feb 23 21:46:00 laptop NetworkManager[17366]: <info> VPN connection 'client' (Connect) reply received.
Feb 23 21:46:15 laptop NetworkManager[17366]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/tun0, iface: tun0)
Feb 23 21:46:15 laptop NetworkManager[17366]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found.
Feb 23 21:46:15 laptop NetworkManager[17366]: <info> VPN connection 'client' (IP Config Get) reply received.
Feb 23 21:46:15 laptop NetworkManager[17366]: <info> VPN Gateway: 2.2.2.2
Feb 23 21:46:15 laptop NetworkManager[17366]: <info> Internal Gateway: 10.8.0.5
Feb 23 21:46:15 laptop NetworkManager[17366]: <info> Tunnel Device: tun0
Feb 23 21:46:15 laptop NetworkManager[17366]: <info> Internal IP4 Address: 10.8.0.6
Feb 23 21:46:15 laptop NetworkManager[17366]: <info> Internal IP4 Prefix: 32
Feb 23 21:46:15 laptop NetworkManager[17366]: <info> Internal IP4 Point-to-Point Address: 10.8.0.5
Feb 23 21:46:15 laptop NetworkManager[17366]: <info> Maximum Segment Size (MSS): 0
Feb 23 21:46:15 laptop NetworkManager[17366]: <info> Static Route: 192.168.10.0/24 Next Hop: 192.168.10.0
Feb 23 21:46:15 laptop NetworkManager[17366]: <info> Static Route: 10.8.0.1/32 Next Hop: 10.8.0.1
Feb 23 21:46:15 laptop NetworkManager[17366]: <info> DNS Domain: '(none)'
Feb 23 21:46:16 laptop NetworkManager[17366]: <info> VPN connection 'client' (IP Config Get) complete.
Feb 23 21:46:16 laptop NetworkManager[17366]: <info> Policy set 'Auto wireless' (wlan0) as default for IPv4 routing and DNS.
Feb 23 21:46:16 laptop NetworkManager[17366]: <info> VPN plugin state changed: 4
Feb 23 21:46:16 laptop nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.
[/code]