[gutsy] refuses to connect to VPN if ppp0 is already in use

Reported here:

http://bugzilla.gnome.org/show_bug.cgi?id=517468

Workaround:
- Put the following line in your peer file. Example: /etc/ppp/peers/dsl-provider:
unit 9

This will change the adsl connection interface from ppp0 to ppp9

I have the same problem: I launch my ADSL connection at interfase ppp0.
network-manager up VPN at interfase ppp0 too, then everything end.

Added watch for the bugreport mentioned in comment #1

Markus

Is this symptom still reproducible in 8.10?

We are closing this bug report as there hasn't been any activity. Please upgrade to the latest release Karmic 9.10 - If this bug is still reproducible please set Status to New. Thanks

Quoting Neil Perry <email address hidden>:The matter and bug remains unsolved ,as
far as I am concerned the new system is unstable and is unusable on my
computer
until further development has been undertaken. I have reverted to 9.04
which is
working efficiently.Bug 163494 is not the bug I reported bug 484856 refers to my
original report.

> We are closing this bug report as there hasn't been any activity. Please
> upgrade to the latest release Karmic 9.10 - If this bug is still
> reproducible please set Status to New. Thanks
>
> ** Changed in: network-manager-pptp (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> [gutsy] refuses to connect to VPN if ppp0 is already in use
> https://bugs.launchpad.net/bugs/163494
> You received this bug notification because you are subscribed to
> NetworkManager.
>
> Status in NetworkManager: Fix Released
> Status in ?network-manager-pptp? package in Ubuntu: Invalid
>
> Bug description:
> Binary package hint: network-manager-pptp
>
> 1. Connect anything via ppp0 (in my case it was HP iPAQ PDA via
> synce). So, interface ppp0 is used now, and PPTP will use ppp1
> instead.
> 2. Try to connect to any VPN through NetworkManager applet.
>
> It responds with graphic warning message like "server didn't response
> valid configuration" (can't say clearly because in my case there
> appear russian translation of it). And here is the part of my syslog:
>
> Nov 18 11:22:28 lion2002 pppd[7492]: Plugin nm-pppd-plugin.so loaded.
> Nov 18 11:22:28 lion2002 pppd[7492]: nm-pppd-plugin: plugin initialized.
> Nov 18 11:22:28 lion2002 pppd[7494]: pppd 2.4.4 started by root, uid 0
> Nov 18 11:22:28 lion2002 pppd[7494]: Using interface ppp1
> Nov 18 11:22:28 lion2002 pppd[7494]: Connect: ppp1 <--> /dev/pts/0
> Nov 18 11:22:29 lion2002 pppd[7494]: nm-pppd-plugin: CHAP check hook.
> Nov 18 11:22:29 lion2002 pppd[7494]: nm-pppd-plugin: CHAP credentials
> requested.
> Nov 18 11:22:29 lion2002 pppd[7494]: CHAP authentication succeeded
> Nov 18 11:22:29 lion2002 pppd[7494]: MPPE 128-bit stateless
> compression enabled
> Nov 18 11:22:29 lion2002 pppd[7494]: local IP address 172.16.3.33
> Nov 18 11:22:29 lion2002 pppd[7494]: remote IP address 172.16.1.1
> Nov 18 11:22:29 lion2002 pppd[7494]: primary DNS address 192.168.1.10
> Nov 18 11:22:29 lion2002 pppd[7494]: secondary DNS address 192.168.1.10
> Nov 18 11:22:29 lion2002 pppd[7494]: nm-pppd-plugin: didn't receive
> an Internal IP4 Address from ppp.
> Nov 18 11:22:29 lion2002 pppd[7494]: Terminating on signal 15
> Nov 18 11:22:29 lion2002 pppd[7494]: Connect time 0.0 minutes.
> Nov 18 11:22:29 lion2002 pppd[7494]: Sent 0 bytes, received 0 bytes.
> Nov 18 11:22:29 lion2002 pppd[7494]: Child process /usr/sbin/pptp
> 192.168.1.10 --nolaunchpppd (pid 7495) terminated with signal 15
> Nov 18 11:22:29 lion2002 pppd[7494]: Modem hangup
> Nov 18 11:22:29 lion2002 pppd[7494]: Connection terminated.
> Nov 18 11:22:29 lion2002 pppd[7494]: Exit.
>
> As you can see, nm-pppd-plugin "thinks" we don't recieve IP4 Address,
> but it's not true (see log).
> I think it's because nm-pppd-plugin looks for ppp0 IP4 Address or similar.
>
>
>