From: Daniel Wagner <daniel.wagner@xxxxxxxxxxxx>
Filtering DUN out at BlueZ level reduces the number of CPU cycles and
memory spend just to figure out that PAN is always preferred over DUN.
Doing this could on a the network manager level (e.g. ConnMan) or
at an intermediate daemon such as dundee which handles AT command
parsing and PPP setup is possible just more expensive.
Therefore, just ignore the DUN completely and do not even announce it.
---
src/device.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/src/device.c b/src/device.c
index 928ea2b..c6112fe 100644
--- a/src/device.c
+++ b/src/device.c
@@ -1530,6 +1530,24 @@ static void update_services(struct browse_req *req, sdp_list_t *recs)
sdp_list_free(svcclass, free);
}
+
+ if (!main_opts.prefer_pan)
+ return;
+
+ if (g_slist_find_custom(req->profiles_added, NAP_UUID,
+ (GCompareFunc) strcmp) != NULL) {
+ GSList *l;
+
+ l = g_slist_find_custom(req->profiles_added,
+ DUN_GW_UUID,
+ (GCompareFunc) strcmp);
+ if (l != NULL) {
+ DBG("Skipping DUN entry because PAN was found.");
+ g_free(l->data);
+ req->profiles_added = g_slist_remove_link(
+ req->profiles_added, l);
+ }
+ }
}
static void store_profiles(struct btd_device *device)
--
1.7.10.130.g36e6c
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
