IPv6 disabled by default on new mobile broadband connection
After creating a new mobile broadband connection using the GUI wizard (can be started from the GNOME Settings application, or from the tray menu in the GNOME Shell top bar), the new connection profile has inappropriately set the
ipv6.method property set to
This prevents the provider's IPv6 connectivity from being used, which is a violation of RFC 6540. Furthermore, several large content providers (Akamai and Facebook, for example) have reported that according to their performance data, mobile clients perform better over IPv6 than over IPv4. Therefore, disabling IPv6 is doing the end user a disservice, since it prevents the use of the better-performing network protocol. It is also going against the mobile provider's wishes - by offering IPv6 connectivity in the first place, they clearly intend for it to be used.
The issue in screenshots
Final confirmation step of GUI wizard
Note that the wizard at no point mentioned or asked about IPv4 or IPv6.
Connection status after completing the wizard
Note how there is no IPv6 addresses reported.
Connection profile details, IPv6 tab
Opened from the cogwheel button in the previous screenshot. Note how «Method» is set to
When creating a connection profile using
nmcli, the issue does not manifest itself. IPv6 is enabled by default. Therefore, we can conclude that the issue is in the GNOME NetworkManager applet, not in NetworkManager itself:
[:~] $ nmcli con add con-name Telenor type gsm gsm.apn telenor.smart Connection 'Telenor' (d70f7c52-d73f-4a5b-b9a8-9717c71a192b) successfully added. [:~] $ nmcli con show Telenor | grep ipv6.method ipv6.method: auto
After having created the connection in the above fashion, we can confirm that the GNOME Settings application depicted in the second screenshot above does support displaying IPv6 configuration:
Fedora 32 NetworkManager-1.22.12-1.fc32.x86_64 network-manager-applet-1.16.0-1.fc32.x86_64