clients: don't default Bluetooth to the PANU profile

No reason to, the other types are no less likely. Quite the contrary, if
the user specifies a GSM APN we're sure to use a DUN profile.

  $ ./clients/cli/nmcli c add type bluetooth ifname '*' bluetooth.bdaddr 1C:E2:CC:56:6C:45 apn internet
  $ nmcli c show bluetooth-1 |grep bluetooth.type
  bluetooth.type:                         panu
                                          ^^^^ not cool
This commit is contained in:
Lubomir Rintel 2017-08-23 14:05:19 +02:00
parent 9b28c9ba91
commit 9481bda939

View file

@ -6613,16 +6613,6 @@ _setting_init_fcn_adsl (ARGS_SETTING_INIT_FCN)
}
}
static void
_setting_init_fcn_bluetooth (ARGS_SETTING_INIT_FCN)
{
if (init_type == NM_META_ACCESSOR_SETTING_INIT_TYPE_CLI) {
g_object_set (NM_SETTING_BLUETOOTH (setting),
NM_SETTING_BLUETOOTH_TYPE, NM_SETTING_BLUETOOTH_TYPE_PANU,
NULL);
}
}
static void
_setting_init_fcn_cdma (ARGS_SETTING_INIT_FCN)
{
@ -6808,7 +6798,6 @@ const NMMetaSettingInfoEditor nm_meta_setting_infos_editor[] = {
NM_META_SETTING_VALID_PART_ITEM (GSM, FALSE),
NM_META_SETTING_VALID_PART_ITEM (CDMA, FALSE),
),
.setting_init_fcn = _setting_init_fcn_bluetooth,
),
SETTING_INFO (BOND,
.valid_parts = NM_META_SETTING_VALID_PARTS (