RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1854892 - pppoe connection terminated immediately after a successful start; assertion error
Summary: pppoe connection terminated immediately after a successful start; assertion e...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: NetworkManager Development Team
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1849386
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-08 12:19 UTC by Beniamino Galvani
Modified: 2020-11-04 01:48 UTC (History)
20 users (show)

Fixed In Version: NetworkManager-1.26.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1849386
Environment:
Last Closed: 2020-11-04 01:47:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Beniamino Galvani 2020-07-08 12:19:28 UTC
+++ This bug was initially created as a clone of Bug #1849386 +++

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.

--- Additional comment from Beniamino Galvani on 2020-07-03 21:47:53 CEST ---

Upstream merge request:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/564

--- Additional comment from Vlado Potisk on 2020-07-04 08:45:57 CEST ---

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.

Comment 1 Beniamino Galvani 2020-07-08 12:29:43 UTC
Reproducible on RHEL 8.3. Set debug=fatal-warnings in the [main] section of NetworkManager.conf and create a pppoe connection with 'ifname ppp0 pppoe.parent=$parent_eth'. Upon activation, NM crashes with:

 NetworkManager[2715]: ((src/devices/nm-device.c:1758)): assertion '<dropped>' failed

Comment 2 Thomas Haller 2020-07-13 21:00:00 UTC
Vladimir, please give QA_ACK for 8.3. Thank you.

Comment 9 errata-xmlrpc 2020-11-04 01:47:57 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4499


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