Bug 1439360 - NetworkManager-ppp ignoring ipv4.method when set to disable
Summary: NetworkManager-ppp ignoring ipv4.method when set to disable
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 27
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-04-05 19:30 UTC by Eric Lajoie
Modified: 2018-11-30 17:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-11-30 17:46:06 UTC
Type: Bug

Attachments (Terms of Use)
tcpdump and config (2.20 KB, application/x-xz)
2017-04-05 19:30 UTC, Eric Lajoie
no flags Details
0001-ppp-allow-disabling-IPv4-too-rhbz-1439360.patch (3.26 KB, patch)
2017-04-05 21:21 UTC, Dan Williams
no flags Details | Diff

Description Eric Lajoie 2017-04-05 19:30:51 UTC
Created attachment 1269067 [details]
tcpdump and config

Description of problem:
PPPoE connection in NetworkManager fails to ignore IPv4 assignment when ipv4.method is set to disable.

Version-Release number of selected component (if applicable):
nmcli tool, version 1.8.0-0.1.fc27

How reproducible:
Always, wireshark shows IPCP request before IPV6CP request.

Steps to Reproduce:
1. Create connection (type pppoe) via nmcli for "ipv6.method auto" and "ipv4.method disable"
2. nmcli connection up pppoe-enp7s0
3. observer ipv4 address

Actual results:
10: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc fq_codel state UNKNOWN group default qlen 3
    inet peer scope global ppp0
       valid_lft forever preferred_lft forever
    inet6 2003:63:237f:d6f2:a942:b189:27c9:46de/64 scope global mngtmpaddr dynamic 
       valid_lft 14356sec preferred_lft 1756sec
    inet6 fe80::a942:b189:27c9:46de/10 scope link 
       valid_lft forever preferred_lft forever

Expected results:
Only IPv6 address and only IPV6CP messages, not IPCP

Additional info:
tcpdump may indicate an error as I removed the DSL password from the dump.

Comment 1 Dan Williams 2017-04-05 21:21:56 UTC
Created attachment 1269087 [details]

Probably fix; unfortunately my Nokia 21m-02 (the thing I can test IPv6 PPP with) died before I could fully test the fix, but this is likely what needs to be done.

Comment 3 Beniamino Galvani 2017-04-14 09:35:21 UTC
Scratch build with the patch: 


Comment 4 Eric Lajoie 2017-04-15 13:40:22 UTC
Looks like its working now.  Thanks!!!

I'll open another bug related to bringing the connection down and it not activating again with the up command.

Comment 6 Jan Kurik 2017-08-15 08:07:00 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 7 Ben Cotton 2018-11-27 18:34:03 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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
EOL if it remains open with a Fedora  'version' of '27'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 8 Ben Cotton 2018-11-30 17:46:06 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.