After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 517468 - failure to connect if tunnel got interface != ppp0
failure to connect if tunnel got interface != ppp0
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: VPN: pptp
0.6.5
Other All
: Normal blocker
: ---
Assigned To: Antony Mee
Antony Mee
Depends on:
Blocks:
 
 
Reported: 2008-02-19 15:47 UTC by Aldrin Martoq
Modified: 2008-08-08 03:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Fix if connection is not ppp0 (1.85 KB, patch)
2008-02-19 15:49 UTC, Aldrin Martoq
none Details | Review

Description Aldrin Martoq 2008-02-19 15:47:49 UTC
Please describe the problem:
If there is a previous ppp0 connection, the tunnel is correctly created as ppp1 but network-manager-pptp incorrectly closes the connection. So, the user cannot connect if there is a previous ppp0 connection. This means, many ADSL users can't connect to a vpn.

If the tunnel is created as ppp0, the VPN connection works fine.


Steps to reproduce:
1. Make sure to create a ppp0 connection (example: an ADSL connection "pon dsl-provider")
2. Activate the pptp VPN connection through network-manager applet



Actual results:
The ADSL connection (ppp0) works fine. Then, when trying to activate the pptp VPN,  the connection is successfuly created (as said by logs), but then it's disconnected and the following message appears:
VPN Connect Failure

Could not start the VPN connection 'test' because the VPN server did not return an adequate network configuration.

VPN Connection failed




Expected results:
The VPN connection should work.

Does this happen every time?
Yes

Other information:
Maybe the other Network Manager VPN plugins have the same bug. A Patch is attached below.
Comment 1 Aldrin Martoq 2008-02-19 15:49:34 UTC
Created attachment 105582 [details] [review]
Fix if connection is not ppp0

Here is the patch that fixes this issue.
Comment 2 Aldrin Martoq 2008-02-19 15:51:38 UTC
This is the message that appears if the connection is made as ppp1 for example:

Feb 19 12:45:44 localhost pppd[25103]: Plugin nm-pppd-plugin.so loaded.
Feb 19 12:45:44 localhost pppd[25103]: nm-pppd-plugin: plugin initialized.
Feb 19 12:45:44 localhost pppd[25105]: pppd 2.4.4 started by root, uid 0
Feb 19 12:45:44 localhost pppd[25105]: Using interface ppp1
Feb 19 12:45:44 localhost pppd[25105]: Connect: ppp1 <--> /dev/pts/12
Feb 19 12:45:45 localhost pppd[25105]: nm-pppd-plugin: CHAP check hook.
Feb 19 12:45:47 localhost pppd[25105]: nm-pppd-plugin: CHAP credentials requested.
Feb 19 12:45:47 localhost pppd[25105]: CHAP authentication succeeded: Access granted
Feb 19 12:45:47 localhost pppd[25105]: CHAP authentication succeeded
Feb 19 12:45:47 localhost pppd[25105]: local  IP address 192.168.1.1
Feb 19 12:45:47 localhost pppd[25105]: remote IP address 192.168.0.1
Feb 19 12:45:47 localhost pppd[25105]: nm-pppd-plugin: didn't receive an Internal IP4 Address from ppp.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 19 12:45:47 localhost pppd[25105]: Terminating on signal 15
Feb 19 12:45:47 localhost pppd[25105]: Child process /usr/sbin/pptp 192.168.9.50 --nolaunchpppd (pid 25106) terminated with signal 15
Feb 19 12:45:47 localhost pppd[25105]: Connect time 0.0 minutes.
Feb 19 12:45:47 localhost pppd[25105]: Sent 0 bytes, received 0 bytes.
Feb 19 12:45:47 localhost pppd[25105]: Modem hangup
Feb 19 12:45:47 localhost pppd[25105]: Connection terminated.
Feb 19 12:45:47 localhost pppd[25105]: Exit.
Comment 3 Dan Williams 2008-08-08 03:30:28 UTC
Thanks! fixed in svn trunk r3910 and stable branch r3911