[#CM-541] No default route after disconnecting pptp connection

advertisement
[CM-541] No default route after disconnecting pptp connection Created: 25/Aug/12
Updated:
16/Jul/13 Resolved: 26/Nov/12
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Closed
Connection Manager
ConnMan Core
unspecified
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Environment:
Bug
Jeff Zheng
Duplicate
None
Not Specified
Issue Links:
Duplicate
duplicates CM-538 routing table incorrect after PPTP tu...
External issue
URL:
None
Assignee:
Votes:
Flykt Patrik
0
Not Specified
Not Specified
Operating System: —
Platform: Common
http://mehestexdesktop.jf.intel.com/bugzilla/index.cgi/show_bug.cgi?id=25701
Description
Connman 1.6 + recent VPN patches (to git head - typo fix)
System has two active interfaces; eth0 and wlan0
Routing table before PPTP connection is made:
root ~/.config # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 172.16.20.1 0.0.0.0 UG 0 0 0 eth0
172.16.20.0 * 255.255.255.0 U 0 0 0 eth0
172.16.20.0 * 255.255.255.0 U 0 0 0 wlan0
Closed
172.16.20.1 * 255.255.255.255 UH 0 0 0 wlan0
172.16.20.1 * 255.255.255.255 UH 0 0 0 eth0
Then we establish the PPTP connection:
root ~/.config # ./vpn-connect-test
root ~/.config # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default * 0.0.0.0 U 0 0 0 ppp0
91.135.9.67 172.16.20.1 255.255.255.255 UGH 0 0 0 eth0
91.135.9.67 172.16.20.1 255.255.255.255 UGH 0 0 0 eth0
172.16.20.0 * 255.255.255.0 U 0 0 0 eth0
172.16.20.0 * 255.255.255.0 U 0 0 0 wlan0
172.16.20.1 * 255.255.255.255 UH 0 0 0 wlan0
172.16.20.1 * 255.255.255.255 UH 0 0 0 eth0
172.16.30.200 * 255.255.255.255 UH 0 0 0 ppp0
208.67.220.220 * 255.255.255.255 UH 0 0 0 ppp0
208.67.222.222 * 255.255.255.255 UH 0 0 0 ppp0
Note this is shown twice
91.135.9.67 172.16.20.1 255.255.255.255 UGH 0 0 0 eth0
Then we disconnect the PPTP tunnel:
root ~/.config # ./vpn-disconnect-test
root ~/.config # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
91.135.9.67 172.16.20.1 255.255.255.255 UGH 0 0 0 eth0
91.135.9.67 172.16.20.1 255.255.255.255 UGH 0 0 0 eth0
172.16.20.0 * 255.255.255.0 U 0 0 0 eth0
172.16.20.0 * 255.255.255.0 U 0 0 0 wlan0
172.16.20.1 * 255.255.255.255 UH 0 0 0 wlan0
172.16.20.1 * 255.255.255.255 UH 0 0 0 eth0
routing table still has a duplicate entry for:
91.135.9.67 172.16.20.1 255.255.255.255 UGH 0 0 0 eth0
this doesn't appear to cause any functional issues, but we should only have 1x each entry in the
table, not 2x
Comments
Comment by jukka.rissanen@gmail.com [ 27/Aug/12 ]
Looks like you are missing the pptp-client patch that I attached in
https://bugs.meego.com/attachment.cgi?id=9971
Can you verify that you are not using the patched pptp-client?
Comment by meego@chrishewitt.net [ 27/Aug/12 ]
mm.. okay, my bad for not having the patch, but once it's applied things go wrong
when I create the pptp connection, table shows:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default * 0.0.0.0 U 0 0 0 ppp0
82.0.199.129 172.16.20.1 255.255.255.255 UGH 0 0 0 eth0
172.16.20.0 * 255.255.255.0 U 0 0 0 eth0
172.16.20.1 * 255.255.255.255 UH 0 0 0 eth0
192.168.100.1 * 255.255.255.255 UH 0 0 0 ppp0
everything is working, no issues.
once I disconnect:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
82.0.199.129 172.16.20.1 255.255.255.255 UGH 0 0 0 eth0
172.16.20.0 * 255.255.255.0 U 0 0 0 eth0
172.16.20.1 * 255.255.255.255 UH 0 0 0 eth0
the default route is gone so the system is effectively offline from the net now..
it's better off without the pptp-client patch, that at least leaves the system in a working state
Comment by jukka.rissanen@gmail.com [ 28/Aug/12 ]
(In reply to comment #2)
> mm.. okay, my bad for not having the patch, but once it's applied things go
> wrong
>
> when I create the pptp connection, table shows:
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> default * 0.0.0.0 U 0 0 0 ppp0
> 82.0.199.129 172.16.20.1 255.255.255.255 UGH 0 0 0 eth0
> 172.16.20.0 * 255.255.255.0 U 0 0 0 eth0
> 172.16.20.1 * 255.255.255.255 UH 0 0 0 eth0
> 192.168.100.1 * 255.255.255.255 UH 0 0 0 ppp0
>
> everything is working, no issues.
>
> once I disconnect:
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 82.0.199.129 172.16.20.1 255.255.255.255 UGH 0 0 0 eth0
> 172.16.20.0 * 255.255.255.0 U 0 0 0 eth0
> 172.16.20.1 * 255.255.255.255 UH 0 0 0 eth0
>
> the default route is gone so the system is effectively offline from the net
> now..
This is the real bug here. You definitely should have default route on eth0 at this point. I will
investigate this (and also change the bug title).
Comment by jukka.rissanen@gmail.com [ 28/Aug/12 ]
(In reply to comment #3)
> > the default route is gone so the system is effectively offline from the net
> > now..
>
> This is the real bug here. You definitely should have default route on eth0 at
> this point. I will investigate this (and also change the bug title).
I could not reproduce this problem in my test system, I get always default route after vpn
disconnection.
I would need syslog with connman debugging activated and with pptp-client patches for further
investigation.
Comment by jukka.rissanen@gmail.com [ 15/Nov/12 ]
This is basically the same issue as in so handling the issue in that bug and marking this one as
duplicate.
Comment by jeff.zheng@intel.com [ 26/Nov/12 ]
Mark as verified. Feel free to reopen if you disagree.
Generated at Sat Mar 05 19:50:43 PST 2016 using JIRA 6.3.14#6345sha1:47b2bb0a76c6e60bffb16fa45719b26a7e5e0c78.
Download