Public bug reported:
Binary package hint: network-manager
Hello,
I'm suing VPN support on edgy/feisty and have some quite important
whishlisst items. I know some of these have already been reported but it
seems no progress has been made, or the issue is stalled. I think these
are absolutely necessary ASAP in order to make NM useable at all.
1) It would be great to have OpenVPN/VPNC/PPTP support in the official
packages.
2) NM should update resolv.conf. Without this VPN support is useless
since DNS servers pushed by the VPN server (e.g. OpenVPN) are not
applied. This is a real pain for resolv.conf in particular since manual
changes to it are preserved only until NM rewrites it (few minutes).
3) NM should update the routing table. Without this VPN support is
useless since routes pushed by the VPN server (e.g. OpenVPN) are not
applied. This is slightly less painful because you can manually specify
which networks should go to the VPN, but still should really be
automatic/configurable.
4) Upon link failure NM should autoreconnect VPN networks which were
connected before link failure.
5) You should be able to connect to more than one VPN concurrently. This
is a major pain. Now you have to disconnect vpn1 and connect vpn2, then
disconnect vpn2 and connect vpn1 and so on.
6) You should be able to connect to more than one network concurrently.
Maybe with the option to specify a "primary" connection used for default
gateway, DNS configuration and the like. Not sure how simple/desireable
this really is.
Quite long list, I know, bu this is badly needed for NM to be of any
use, IMHO. Now show me I am wrong, please.
Luca
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
VPN support status
https://launchpad.net/bugs/71977
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
