© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Specification updated. <https:/
> 1. Each APN has a defined "Name", which would be helpful to display to the user.
What is the use case? I could understand showing the name if we let you select an APN from a list, or import/export APN settings on external storage, or set up an APN separately from choosing which Types it should be used for. Currently we're doing none of those things, so I'm leaving it out for now. I wouldn't want to mislead people into thinking that all they need to do to make their Orange phone work is to delete "T-Mobile US" and type "Orange" in its place, leaving all the actual settings unchanged.
> Also, it might be helpful to include the MCC ( mobile country code ) and MNC ( mobile network code ).
What is the use case? Are those data editable? If so, what would an APN do differently if you changed them? And if not, what do you need to see them for?
> 2. Currently the only protocol that's supported for Mobile data connections is IPv4.
Explained: "The 'Protocol' menu should be present when IPv6 has been implemented."
> 3. The MMS fields are close, but not quite accurate.
Fixed: each APN now has fields for "APN", "Proxy", and "Proxy port".
> 4. We're still trying to determine how we rectify the difference between ofono contexts and Android's APN db.
What is the use case for an APN that isn't default/internet or mms? For example, what does a supl APN do?
> 5. Turns out that there are ~100 or so APNs defined with "proxy" and "port" attributes that are used to configure what I'm guessing is a required HTTP proxy.
Fixed as for #3.
> 6. Some APNs also expose an "authentication
Added: "The 'Authentication' menu should contain 'None' (the default), 'PAP or CHAP', 'PAP only', and 'CHAP only'." Since "PAP or CHAP" is an option, I'm assuming that the rationale for the more restrictive options is to prevent MITM attacks? If we can auto-detect authentication methods altogether, then we can get rid of the menu altogether.
> 7... we've decided that it'd be best to provision all of the possible APNs for the given SPN/MNC/MCC combination, pick a default ( which is the first that supports Internet in the list ), and then allow the user to select any of the APNs that have been provisioned
If I understand you correctly, that would make the UI much more complex: first you'd set up one or two APNs, and then you'd say "I want to use that one for Internet", rather than having dedicated "Internet APN" fields. That would be a reason to show the "Name" field (#1 above), but I'd rather avoid it (see #4 above).
> 8. AOSP allows a user to manually create a new APN.
As for #7 above.
> 9. AOSP also allows a user to reset their APN configuration to it's default ( ie. undo any changes made ).
How does Ubuntu know what the default is?