Bug 446663
| Summary: | NetworkManager can't establish GPRS/3G connection | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dawid Lorenz <adlorenz> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 9 | CC: | dcbw, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-11-04 22:45:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dawid Lorenz
2008-05-15 15:56:35 UTC
Is this still an issue with latest NM updates (svn4022 or later)? Yes, I am afraid it is still an issue. Here's the syslog output when I try to connect to the internet via GPRS/UMTS modem: Nov 3 20:24:24 x1 NetworkManager: <info> Activation (ttyUSB0) starting connection 'Era' Nov 3 20:24:24 x1 NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4 Nov 3 20:24:24 x1 NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Nov 3 20:24:24 x1 NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Nov 3 20:24:24 x1 NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Nov 3 20:24:25 x1 NetworkManager: <WARN> manual_registration_done(): Manual registration failed Nov 3 20:24:25 x1 NetworkManager: <info> (ttyUSB0): device state change: 4 -> 9 Nov 3 20:24:25 x1 NetworkManager: <info> Marking connection 'Era' invalid. Nov 3 20:24:25 x1 NetworkManager: <info> Activation (ttyUSB0) failed. Nov 3 20:24:25 x1 NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3 Nov 3 20:24:25 x1 NetworkManager: <info> (ttyUSB0): deactivating device. Nov 3 20:24:25 x1 NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed Nov 3 20:24:25 x1 NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed My NM version is: [root@x1 ~]# rpm -qa | grep Network NetworkManager-openvpn-0.7.0-16.svn4027.fc9.i386 NetworkManager-gnome-0.7.0-0.11.svn4022.4.fc9.i386 NetworkManager-glib-0.7.0-0.11.svn4022.4.fc9.i386 NetworkManager-vpnc-0.7.0-0.10.svn4024.fc9.i386 NetworkManager-0.7.0-0.11.svn4022.4.fc9.i386 Have you manually filled in the "Network:" field in the connection editor? What happens if you let the modem automatically determine which provider to register with? (In reply to comment #3) > Have you manually filled in the "Network:" field in the connection editor? > What happens if you let the modem automatically determine which provider to > register with? Yay! It works! I've left 'Network' field empty, tried to connect, and it worked straight away! I've checked with two different SIM cards, one of which was PIN-protected, and both worked flawlessly. I am really, I mean REALLY impressed. :) What is the purpose of that 'Network' field then? :-o Btw, I'd make password field optional. Not all GSM operators require password to connect. (In reply to comment #4) > (In reply to comment #3) > > Have you manually filled in the "Network:" field in the connection editor? > > What happens if you let the modem automatically determine which provider to > > register with? > > Yay! It works! I've left 'Network' field empty, tried to connect, and it worked > straight away! I've checked with two different SIM cards, one of which was > PIN-protected, and both worked flawlessly. I am really, I mean REALLY > impressed. :) > > What is the purpose of that 'Network' field then? :-o To force the card to register on a specific network and never roam outside your home region if you like. To lock to AT&T, for example, you'd enter 310410 in there, which is the GSM MCC/MNC for much of AT&T (but not all). > Btw, I'd make password field optional. Not all GSM operators require password > to connect. It should be optional; if you don't fill in the username and password, it should be requested. If you fill in the username, the password is expected; but most of the time you can enter anything you like in there and it will still work. (In reply to comment #5) > To force the card to register on a specific network and never roam outside your > home region if you like. To lock to AT&T, for example, you'd enter 310410 in > there, which is the GSM MCC/MNC for much of AT&T (but not all). In that case, I think this field should be described in some different way, to make user think it's not just a place where you put a network name (like 'T-Mobile' or 'Vodafone'). I intuitively did that and I would never suspect it could cause the problem. |