Created attachment 316953 [details] Entry relative to nm-pptp connecting in /var/log/messages Description of problem: Summary says it all. See attache file. Version-Release number of selected component (if applicable): NetworkManager-pptp-0.7.0-0.10.svn4027.fc9.x86_64 NetworkManager-pptp-debuginfo-0.7.0-0.10.svn4027.fc9.x86_64 How reproducible: Always. Steps to Reproduce: 1. Create an vpn-connection 2. Manually set the route or 3. use the route received from server ( default ) 4. Run route -n to see if routes get added/updated. Actual results: Routes dont get update with new routes Expected results: Routes getting updated Additional info:
I got this problem too！ on rawhide ，version list below： NetworkManager-gnome-0.7.0-0.11.svn4229.fc10.i386 NetworkManager-0.7.0-0.11.svn4229.fc10.i386 NetworkManager-pptp-0.7.0-0.12.svn4229.fc10.i386 NetworkManager-glib-0.7.0-0.11.svn4229.fc10.i386
afaik, PPP servers do not send routes from the server to the client; what exact routes are you looking for here? What should 'route -n' show, and what does it show instead?
[xelnaga@ASUS6 ~]$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 220.169.80.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 0.0.0.0 220.169.80.1 0.0.0.0 UG 0 0 0 ppp0 [xelnaga@ASUS6 ~]$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.10.0.1 220.169.80.1 255.255.255.255 UGH 0 0 0 ppp0 220.169.80.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 69.89.31.238 124.116.176.67 255.255.255.255 UGH 0 0 0 ppp1 124.116.176.67 0.0.0.0 255.255.255.255 UH 0 0 0 ppp1 124.116.176.67 220.169.80.1 255.255.255.255 UGH 0 0 0 ppp0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp1 [xelnaga@ASUS6 ~]$ It seems OK now，that's weird！
# Routing table on client connected with pptpconfig [root@localhost ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 130.208.165.95 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 130.208.179.1 130.208.69.254 255.255.255.255 UGH 0 0 0 eth0 130.208.69.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 130.208.69.254 0.0.0.0 UG 0 0 0 eth0 # Routing table on client connected with NM-PPTP [root@localhost ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 130.208.69.254 255.255.255.255 UGH 0 0 0 eth0 130.208.69.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
Created attachment 322108 [details] Client-Server.log
Have you added any custom routes in the pptpconfig GUI?
No all have told pptp is to route all packages through the pptp vpn connection. One curios question I noticed that NM-pptp while connecting marked the vpn gateway 0.0.0.0 is that expected behaviour?
I would have thought it was supposed to be 130.208.179.1 since I get assigned 130.208.179.x ?
Could this be a 64bit or a driver issue? I just installed F10Preview on my Dell Inspirion 6000 which is an i686 same nm-pptp settings as on my T61p 64bit machine NM-PPTP works like a charm.. [root@localhost ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 130.208.165.95 130.208.69.254 255.255.255.255 UGH 0 0 0 eth0 130.208.179.1 130.208.69.254 255.255.255.255 UGH 0 0 0 eth0 130.208.71.0 0.0.0.0 255.255.255.0 U 2 0 0 eth1 130.208.69.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
uhum noticed I had been testing this on my workstation ( F9 64bit ) Will test this on my t61p when I get home from work.. which is an F10 64 bit...
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.