NM does not honour manual IP4Settings for ppp connections [(3G/pppoe) NM doesn't overwrite the bogus values it received from ppp even if you set Automatic (addresses only) in the ip4setting tab in connection editor]

Bug #303165 reported by Alexander Sack on 2008-11-28
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
High
Unassigned
Intrepid
High
Alexander Sack

Bug Description

Binary package hint: network-manager

For ppp connections (serial+pppoe), NM doesnt consider your IP settings, but uses what you get through PPP (e.g. for 3G).

This issue was found and a patch suggested in the "ppp bogus dns" bug: https://bugs.edge.launchpad.net/ubuntu/+source/ppp/+bug/258801/comments/33.

To verify:
1. connect to 3G provider (or through DSL/pppoe) with "addresses only" and some custom DNS setting.
2. see that the dns provided by ppp is used and not your custom DNS settings.
3. verify that new package uses your custom DNS setting.

Alexander Sack (asac) wrote :
Changed in network-manager:
importance: Undecided → Medium
status: New → Triaged
Alexander Sack (asac) wrote :

since we have a patch we should SRU it with next NM round.

Changed in network-manager:
assignee: nobody → asac
importance: Undecided → High
milestone: none → intrepid-updates
status: New → Triaged
importance: Medium → High
description: updated

Is this happening any time soon? I still can't use PPTP VPNs in intrepid:

Feb 2 17:07:25 rantipole pptp[17173]: nm-pptp-service-17163 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply
Feb 2 17:07:25 rantipole pptp[17173]: nm-pptp-service-17163 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established.
Feb 2 17:07:26 rantipole pptp[17173]: nm-pptp-service-17163 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request'
Feb 2 17:07:26 rantipole pptp[17173]: nm-pptp-service-17163 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply.
Feb 2 17:07:26 rantipole pptp[17173]: nm-pptp-service-17163 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 27393).
Feb 2 17:07:26 rantipole pptp[17173]: nm-pptp-service-17163 log[ctrlp_disp:pptp_ctrl.c:912]: Received Call Clear Request.
Feb 2 17:07:57 rantipole pptp[17173]: nm-pptp-service-17163 log[pptp_read_some:pptp_ctrl.c:544]: read returned zero, peer has closed
Feb 2 17:07:57 rantipole pptp[17173]: nm-pptp-service-17163 log[callmgr_main:pptp_callmgr.c:258]: Closing connection (shutdown)
Feb 2 17:07:57 rantipole pptp[17173]: nm-pptp-service-17163 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request'
Feb 2 17:07:57 rantipole pppd[17164]: Modem hangup
Feb 2 17:07:57 rantipole NetworkManager: <info> VPN plugin failed: 1
Feb 2 17:07:57 rantipole pppd[17164]: Connection terminated.
Feb 2 17:07:57 rantipole pptp[17173]: nm-pptp-service-17163 log[pptp_read_some:pptp_ctrl.c:544]: read returned zero, peer has closed
Feb 2 17:07:57 rantipole pptp[17173]: nm-pptp-service-17163 log[call_callback:pptp_callmgr.c:79]: Closing connection (call state)
Feb 2 17:07:57 rantipole NetworkManager: <info> VPN plugin failed: 1
Feb 2 17:07:57 rantipole pppd[17164]: Exit.
Feb 2 17:07:57 rantipole NetworkManager: <info> VPN plugin failed: 1
Feb 2 17:07:57 rantipole NetworkManager: <info> VPN plugin state changed: 6
Feb 2 17:07:57 rantipole NetworkManager: <info> VPN plugin state change reason: 0
Feb 2 17:07:57 rantipole NetworkManager: <WARN> connection_state_changed(): Could not process the request because no VPN connection was active.
Feb 2 17:07:57 rantipole NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
Feb 2 17:08:09 rantipole NetworkManager: <debug> [1233547689.829289] ensure_killed(): waiting for vpn service pid 17163 to exit
Feb 2 17:08:09 rantipole NetworkManager: <debug> [1233547689.829542] ensure_killed(): vpn service pid 17163 cleaned up

Alexander Sack (asac) wrote :

this was fixed in jaunty.

Changed in network-manager (Ubuntu):
status: Triaged → Fix Released
Alexander Sack (asac) wrote :

wont fix in intrepid. if you really need this, talk to me on IRC.

Changed in network-manager (Ubuntu Intrepid):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers