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 1459529 - cannot connect gsm modem
Summary: cannot connect gsm modem
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-07 12:03 UTC by Vladimir Benes
Modified: 2018-10-30 11:12 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.12.0-0.1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 11:11:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
debug logs from NM and MM (81.77 KB, application/octet-stream)
2017-06-07 12:04 UTC, Vladimir Benes 		no flags Details
[PATCH] all: add more meaningful error code for unsupported IP method (3.76 KB, patch)
2017-12-20 15:29 UTC, Beniamino Galvani 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3207 0 None None None 2018-10-30 11:12:20 UTC

Description Vladimir Benes 2017-06-07 12:03:30 UTC 
Description of problem:
cannot connect Huawei modem that worked in 7.2 with these errors:
[root@gsm-r5s8-01 ~]# nmcli  connection up id gsm 
Error: Connection activation failed: Unknown error
[root@gsm-r5s8-01 ~]# nmcli  connection up id gsm 
Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)

ipv6 is ignored and ipv4 method set to manual and ipv4.address to 10.0.0.1/24. 


Version-Release number of selected component (if applicable):
Bus 003 Device 004: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E230/E270/E870 HSDPA/HSUPA Modem

NetworkManager-1.8.0-5.el7.x86_64
kernel-3.10.0-675.el7.x86_64
usb_modeswitch-data-20160612-2.el7.noarch
usb_modeswitch-2.4.0-5.el7.x86_64
ModemManager-1.6.0-2.el7.x86_64

How reproducible:
always
Comment 1 Vladimir Benes 2017-06-07 12:04:05 UTC 
it worked in 7.3 not 7.2 as stated above
Comment 2 Vladimir Benes 2017-06-07 12:04:33 UTC 
Created attachment 1285773 [details]
debug logs from NM and MM
Comment 3 Vladimir Benes 2017-06-07 12:21:15 UTC 
Bus 003 Device 005: ID 1c9e:9603 OMEGA TECHNOLOGY 

the same issue
Comment 4 Beniamino Galvani 2017-06-09 16:37:47 UTC 
Hi,

I tried the same on RHEL 7.3:

# nmcli connection show Vodafone\ Mobile\ Internet | grep "ipv4.method\|ipv4.addresses\|ipv6.method"
ipv4.method:                            manual
ipv4.addresses:                         10.0.0.1/24
ipv6.method:                            ignore

# nmcli connection up Vodafone\ Mobile\ Internet
 Error: Connection activation failed.

# rpm -q NetworkManager NetworkManager-wwan ModemManager
 NetworkManager-1.4.0-20.el7_3.x86_64
 NetworkManager-wwan-1.4.0-20.el7_3.x86_64
 ModemManager-1.6.0-2.el7.x86_64

From the journal:
 (ttyHS2): unhandled WWAN IPv4 method 'manual'; will fail
 device (ttyHS2): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
 active-connection[0x7fd7e1574b20]: set state deactivated (was activating)
 active-connection[0x7fd7e1574b20]: check-master-ready: not signalling (state deactivated, no master)
 device[0x7fd7e15f1760] (ttyHS2): remove_pending_action (0): 'activation::0x7fd7e1574b20'
 modem-broadband[ttyHS2]: notifying ModemManager about the modem disconnection
 policy: connection 'Vodafone Mobile Internet' failed to autoconnect; 3 tries left
 device (ttyHS2): Activation: failed for connection 'Vodafone Mobile Internet'

Do you confirm it is working on RHEL 7.3 for you?
Comment 5 Vladimir Benes 2017-06-12 09:43:09 UTC 
(In reply to Beniamino Galvani from comment #4)
> Hi,
> 
> I tried the same on RHEL 7.3:
> 
> # nmcli connection show Vodafone\ Mobile\ Internet | grep
> "ipv4.method\|ipv4.addresses\|ipv6.method"
> ipv4.method:                            manual
> ipv4.addresses:                         10.0.0.1/24
> ipv6.method:                            ignore
> 
> # nmcli connection up Vodafone\ Mobile\ Internet
>  Error: Connection activation failed.
> 

as Lubo told me, manual method is not supported. We have to use auto to be able to connect. Not sure if this shouldn't be at least announced in the error message.
Comment 8 Beniamino Galvani 2017-07-13 15:54:21 UTC 
Vlad, can you confirm that a supported configuration works?
Comment 9 Vladimir Benes 2017-09-12 10:11:34 UTC 
(In reply to Beniamino Galvani from comment #8)
> Vlad, can you confirm that a supported configuration works?

yeah, connecting via modem works with auto method
Comment 10 Beniamino Galvani 2017-11-27 17:14:10 UTC 
Manual method for gsm connections is not supported.

Quoting dcbw on IRC:

"you cannot really control the IP, if you do get a static IP from the provider, they will just assign it to you on the network side and you get it the same way you get dynamic addresses".

So, the current limitation on the method=manual is intentional and it is not going to be changed.
Comment 11 Beniamino Galvani 2017-12-20 15:29:34 UTC 
Created attachment 1370512 [details]
[PATCH] all: add more meaningful error code for unsupported IP method

I think we should return a specific code for this error.
Comment 12 Beniamino Galvani 2017-12-20 15:31:52 UTC 
# nmcli connection mod "3 Ricaricabile" ipv4.method manual ipv4.address 1.2.3.4/32
# nmcli connection up  "3 Ricaricabile"
Error: Connection activation failed: The selected IP method is not supported

vs

Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)
Comment 13 Thomas Haller 2017-12-20 16:32:40 UTC 
(In reply to Beniamino Galvani from comment #11)
> Created attachment 1370512 [details]
> [PATCH] all: add more meaningful error code for unsupported IP method
> 
> I think we should return a specific code for this error.

lgtm
Comment 14 Beniamino Galvani 2017-12-21 09:12:03 UTC 
Applied to master:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=aa820e93864a452ec5089381a332be106f4d2c69

and nm-1-10.
Comment 16 Vladimir Benes 2018-08-31 15:01:30 UTC 
We are now seeing an error of wrong IPv4 method. This is sufficient and should be saying enough about just auto being supported.
Comment 18 errata-xmlrpc 2018-10-30 11:11:02 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:3207
Note You need to log in before you can comment on or make changes to this bug.