Bug 807430

Summary:	NetworkManager does not provide the setting for movistar carrier in Guatemala
Product:	[Fedora] Fedora	Reporter:	Edwind Richzendy Contreras Soto <richzendy>
Component:	mobile-broadband-provider-info	Assignee:	Dan Williams <dcbw>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	16	CC:	dcbw, jklimes, sanjay.ankur
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-14 02:51:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Edwind Richzendy Contreras Soto 2012-03-27 18:48:08 UTC

Description of problem:

Network manager does not provide the setting for movistar carrier in Guatemala, in the setup wizard for Internet connection GSM / usb modem

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

Version     : 0.9.2
Release     : 1.fc16
Architecture: x86_64


Additional info:

See:

http://www.unlockit.co.nz/mobilesettings/settings.php?id=111

This config work fine:

# /etc/NetworkManager/system-connections/Movistar\ Predeterminado
[connection]
id=Movistar Predeterminado
uuid=b3d8a116-a2fc-4af9-5a5a-7d1f099c2847
type=gsm
autoconnect=false

[gsm]
number=*99#
apn=internet.movistar.gt
username=movistargt
password=movistargt

[ipv4]
method=auto

[serial]
baud=115200

Comment 1 Jirka Klimes 2012-07-12 12:57:16 UTC

Thanks for reporting and providing the data!

Added to mobile-broadband-provider-info database upstream:
5af4de9553c197592ac089c4f47e7f3a319ffe7d

Comment 2 Fedora End Of Life 2013-02-14 02:51:09 UTC

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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