Comment 107 for bug 259168

Regarding refuse-eap: As I stated 2008-11-04 , the manual workaround of using your favorite text editor to add "refuse-eap" to the file ~/.gconf/system/networking/connections/n/vpn/%gconf.xml works for me (makes me able to establish the vpn). (As an aside, gconf-editor can be used, instead of a text editor, to add the refuse-eap.) I am very grateful to the author of the patch which adds refuse-eap as a configurable item in the gui (but then again, the manual workaround works fine too). But this is like nibbling at the edges of a much larger problem, for example:

1. In 0.7, if you use the gui again, it overwrites your manual workarounds, like refuse-eap.

2. I still cannot modify routes so that only some traffic goes through the vpn while all other traffic goes through my internet gateway.

3. There are still dozens of other parameters which were configurable in 0.6.5 but which are not in 0.7. I don't know how many people here have ever used 0.6.5 under Hardy, but that is why, in my previous post, I showed a text equivalent of the gui for 0.6.5.

Does anyone know where 0.7 came from, and why it was the version which was put in Intrepid, given the fairly large amount of bugs in 0.7, and given the fact (please correct me if I'm wrong) that, according to my understanding, each new release of Ubuntu starts with the latest Debian "unstable", and if I search within Unstable at debian.org ( http://packages.debian.org/search?keywords=network-manager&searchon=names&suite=unstable&section=all ) I get the following versions:

network-manager: 0.6.6-2
network-manager-gnome: 0.6.6-2
network-manager-pptp: 0.6.5+svnhead2574+dfsg-2
network-manager-pptp-gnome: 0.6.5+svnhead2574+dfsg-2

and if I search within Experimental (http://packages.debian.org/search?keywords=network-manager&searchon=names&suite=experimental&section=all ) I get the following versions:

network-manager: 0.7.0~svn4191-1
network-manager-gnome: 0.7.0~svn953-1
network-manager-pptp: 0.6.6+dfsg-2
network-manager-pptp-gnome: 0.6.6+dfsg-2

I'm wondering if network-manager-pptp 0.7 in Intrepid was simply a mistake (a rather large one, if so), I also wonder if what Anthony Mercatante said has any bearing: see https://launchpad.net/ubuntu/intrepid/+source/network-manager-pptp/0.6.5+svnhead2574-0ubuntu1 . I quote Anthony as follows:

"* Due to misscomprehension with original maintainer, my previous svn sync was a regression, as I synched with 0.6.5 branch while he did with 0.7 beta and backported the sources for 0.6.x.
Reverting the packaging for the moment as we are late in the dev cycle to resync from svn and get potentially something unstable.
* Applyed patch 01_no_icon.dpatch
* Removed network-manager-gnome dependancy
* Added missing build-dep libnm-util-dev"

Final note: I used aptitude, in Intrepid, to downgrade the five related packages (network-manager, network-manager-gnome, network-manager-pptp, libnm-glib0, libnm-util0) to what they were in Hardy, and mark them as held at the older 0.6.6/0.6.5 version, and it works fine, just like the good old days in Hardy. But I would not recommend the downgrade to anyone unless you are willing to put up with the fact that the gui update-manager and synaptic do not recognize the Held state of the five packages, so they will both will keep telling you that upgrades are available for the five.