Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1527934

Summary: GSM connection doesn't get a default device route
Product: Red Hat Enterprise Linux 7 Reporter: Beniamino Galvani <bgalvani>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: atragler, bgalvani, fgiudici, lmiksik, lrintel, rkhan, sukulkar, thaller, vbenes
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.10.2-5.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 13:35:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Beniamino Galvani 2017-12-20 13:53:24 UTC
Description of problem:

When a GSM connection is activated and the modem returns no gateway, NM doesn't add a default device route.


Version-Release number of selected component (if applicable):
1.10


How reproducible:
Always


Steps to Reproduce:
1. Activate a GSM connection
2. Check routes


Actual results:
 $ ip r
 x.x.x.x dev hso0 proto kernel scope link src x.x.x.y metric 700


Expected results:
 $ ip r
 default dev hso0 proto static scope link metric 700
 x.x.x.x dev hso0 proto kernel scope link src x.x.x.y metric 700

Comment 2 Beniamino Galvani 2017-12-20 13:57:35 UTC
Please review branch bg/modem-default-route-rh1527934.

Comment 3 Thomas Haller 2017-12-20 17:39:19 UTC
(In reply to Beniamino Galvani from comment #2)
> Please review branch bg/modem-default-route-rh1527934.

lgtm

Comment 8 Beniamino Galvani 2018-02-13 08:02:39 UTC
I confirm the issue is fixed:

 # rpm -q NetworkManager
 NetworkManager-1.10.2-11.el7.x86_64

 # nmcli connection up 3\ Ricaricabile 
 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/7)

 # ip r
 default dev hso0 proto static scope link metric 700      <----------------
 x.x.x.x dev hso0 proto kernel scope link src x.x.x.x metric 700

Comment 9 Vladimir Benes 2018-02-14 09:26:16 UTC
as for above comment, moving to verified (sanity only)

Comment 12 errata-xmlrpc 2018-04-10 13:35:58 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, 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-2018:0778