Created attachment 1698221 [details] log (text) Description of problem: There are two ways of specifying interface names for a pppoe connection to be started on an ethernet interface I will hereafter refer to as the old and the new way. The old one was (as saved in a .nmconnection file): [connection] id=adsl-internet type=pppoe interface-name=enp5s0 and the new one is: [connection] id=adsl-internet type=pppoe interface-name=ppp0 [pppoe] parent=enp5s0 The old way is working fine for me, but it has a drawback that it seems to be impossible to have an IP address and running pppoe on the same interface at the same time. AFAIK that was the reason for introducing the new way. When I use the new configuration (not changing anything else, only the connection.interface-name and pppoe.parent as shown above), the pppoe connection is established, but immediately terminated. No other retries are attempted. Bringing the connection up manually with "nmcli conn up ..." succeeds though, but manual connection maintainance is not a viable option. The log contains this error: "assertion '<dropped>' failed": NetworkManager[15807]: PAP authentication succeeded NetworkManager[15807]: peer from calling number 7C:AD:XX:XX:XX:XX authorized pppd[15807]: peer from calling number 7C:AD:XX:XX:XX:XX authorized pppd[15807]: local IP address 212.XX.XX.XX pppd[15807]: nm-ppp-plugin: status 9 / phase 'running' NetworkManager[15807]: local IP address 212.XX.XX.XX NetworkManager[15807]: remote IP address 84.XX.XX.XX NetworkManager[15807]: primary DNS address 195.XX.XX.XX NetworkManager[15807]: secondary DNS address 195.XX.XX.XX NetworkManager[15773]: ((src/devices/nm-device.c:1441)): assertion '<dropped>' failed NetworkManager[15773]: <info> [1592723907.0471] device (ppp0): state change: config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed') NetworkManager[15773]: <info> [1592723907.0477] manager: NetworkManager state is now CONNECTED_LOCAL NetworkManager[15773]: <warn> [1592723907.0577] device (ppp0): Activation: failed for connection 'adsl-internet' More lines of the log are in the attached file. Version-Release number of selected component (if applicable): NetworkManager-1.22.14-1.fc32.x86_64 NetworkManager-ppp-1.22.14-1.fc32.x86_64 How reproducible: always Steps to Reproduce: 1. Configure the NetworkManager with an Ethernet interface and a pppoe interface using the Ethernet as its parent; 2. systemctl restart NetworkManager Actual results: Ethernet up), pppoe down Expected results: Ethernet up, pppoe also up Additional info: I will add my configuration files or other information if needed.
Upstream merge request: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/564
I read the desciption of the linked proposed patch. After changing the interface name from 'ppp0' to other string it works. I think you have found the problem's cause. Thank you.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 '32'. 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 32 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.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.