From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 58FBAC4332F for ; Mon, 21 Nov 2022 23:55:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231996AbiKUXzm (ORCPT ); Mon, 21 Nov 2022 18:55:42 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59134 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231322AbiKUXzl (ORCPT ); Mon, 21 Nov 2022 18:55:41 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 69E30DFA5 for ; Mon, 21 Nov 2022 15:54:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1669074885; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Vfi5JoUW4sy0rV+2b6cm9JwJhGIJ1OzKdAPSqEmwZ/s=; b=ICmylPkgpZwfu6WZVhAAR3wOx5bX6E3WK0wiSV/acphMLVy7W7aU2bjANPTSDoLI72wmUV cRZoLhNfb4Uz84TCgJQQbhUPnOl/cm9igTJOASO2UWPj9MuntKYsRtj3UuMj0iK5Gj0hqu k+QRt31J5SSYaffCtS2f4hLz2egGzW0= Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-426-gAYb8BhqNcKV7SoJ1J9VIg-1; Mon, 21 Nov 2022 18:54:44 -0500 X-MC-Unique: gAYb8BhqNcKV7SoJ1J9VIg-1 Received: by mail-ed1-f71.google.com with SMTP id y18-20020a056402359200b004635f8b1bfbso7762420edc.17 for ; Mon, 21 Nov 2022 15:54:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Vfi5JoUW4sy0rV+2b6cm9JwJhGIJ1OzKdAPSqEmwZ/s=; b=pwa0wSTBhsEBypQmbOJ4YtDDUYTmBXPVSIe2VX+fnPICrFTHyAIJb/V3MiUETvE0M9 jpAQjfjoj3AYvlRtPfOfSQOSnnLVLEpgkeUp8ptMYXB0Jyue7H704YLceGb1j3sT90Dm JVc3ogHl89SC0JjeySHJ8oVRWu6Vf4jzKwxH0zsWvi3qMBvpHfXf6UNSICRnLSSsVL9P HjQ5Wikaiq19MOTBCHsTySRVClk3HvvLgb58MvZxAzjqQVDgwmibV6fcZ2+uYOvPNkIJ rbDbHckINLlqnwSjqJoI5jGisYaP7RB8GVzY5fPIfPag3alNZMajxUcPJAmmb0i/3r6K sgCw== X-Gm-Message-State: ANoB5pl84SoTjfL+s7To3aeSPXfL09xy3Td2+MirDPAFmpiY06ozJQ2s T3R1v+1Mu5Vy9845kmilVskfhJUIzpbKzITMQq16Nr8z5VM/exGWCYpEGEjXaNu+cJeP67UenI8 wQEGkC6pBrWp6dH60muFwCF7jdbLYJGRT X-Received: by 2002:a05:6402:2075:b0:457:1323:1b7e with SMTP id bd21-20020a056402207500b0045713231b7emr18096145edb.311.1669074882829; Mon, 21 Nov 2022 15:54:42 -0800 (PST) X-Google-Smtp-Source: AA0mqf4plkbvfUTn37DrpMuiuokQS5FXamM7cr2o73T3mVCgtfVsKKFvQIEszefLXUsr5uMQowhWAfAqhL/yJ1ppcs8= X-Received: by 2002:a05:6402:2075:b0:457:1323:1b7e with SMTP id bd21-20020a056402207500b0045713231b7emr18096132edb.311.1669074882578; Mon, 21 Nov 2022 15:54:42 -0800 (PST) MIME-Version: 1.0 References: <20221102151915.1007815-1-miquel.raynal@bootlin.com> <20221102151915.1007815-2-miquel.raynal@bootlin.com> <20221118230443.2e5ba612@xps-13> <20221121100539.75e13069@xps-13> In-Reply-To: <20221121100539.75e13069@xps-13> From: Alexander Aring Date: Mon, 21 Nov 2022 18:54:31 -0500 Message-ID: Subject: Re: [PATCH wpan-next 1/3] ieee802154: Advertize coordinators discovery To: Miquel Raynal Cc: Alexander Aring , Stefan Schmidt , linux-wpan@vger.kernel.org, David Girault , Romuald Despres , Frederic Blain , Nicolas Schodet , Guilhem Imberton , Thomas Petazzoni , "David S. Miller" , Jakub Kicinski , Paolo Abeni , Eric Dumazet , netdev@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hi, On Mon, Nov 21, 2022 at 4:05 AM Miquel Raynal wrote: > > Hi Alexander, > > aahringo@redhat.com wrote on Sun, 20 Nov 2022 19:57:31 -0500: > > > Hi, > > > > On Fri, Nov 18, 2022 at 5:04 PM Miquel Raynal wrote: > > > > > > Hi Alexander, > > > > > > aahringo@redhat.com wrote on Sun, 6 Nov 2022 21:01:35 -0500: > > > > > > > Hi, > > > > > > > > On Wed, Nov 2, 2022 at 11:20 AM Miquel Raynal wrote: > > > > > > > > > > Let's introduce the basics for advertizing discovered PANs and > > > > > coordinators, which is: > > > > > - A new "scan" netlink message group. > > > > > - A couple of netlink command/attribute. > > > > > - The main netlink helper to send a netlink message with all the > > > > > necessary information to forward the main information to the user. > > > > > > > > > > Two netlink attributes are proactively added to support future UWB > > > > > complex channels, but are not actually used yet. > > > > > > > > > > Co-developed-by: David Girault > > > > > Signed-off-by: David Girault > > > > > Signed-off-by: Miquel Raynal > > > > > --- > > > > > include/net/cfg802154.h | 20 +++++++ > > > > > include/net/nl802154.h | 44 ++++++++++++++ > > > > > net/ieee802154/nl802154.c | 121 ++++++++++++++++++++++++++++++++++++++ > > > > > net/ieee802154/nl802154.h | 6 ++ > > > > > 4 files changed, 191 insertions(+) > > > > > > > > > > diff --git a/include/net/cfg802154.h b/include/net/cfg802154.h > > > > > index e1481f9cf049..8d67d9ed438d 100644 > > > > > --- a/include/net/cfg802154.h > > > > > +++ b/include/net/cfg802154.h > > > > > @@ -260,6 +260,26 @@ struct ieee802154_addr { > > > > > }; > > > > > }; > > > > > > > > > > +/** > > > > > + * struct ieee802154_coord_desc - Coordinator descriptor > > > > > + * @coord: PAN ID and coordinator address > > > > > + * @page: page this coordinator is using > > > > > + * @channel: channel this coordinator is using > > > > > + * @superframe_spec: SuperFrame specification as received > > > > > + * @link_quality: link quality indicator at which the beacon was received > > > > > + * @gts_permit: the coordinator accepts GTS requests > > > > > + * @node: list item > > > > > + */ > > > > > +struct ieee802154_coord_desc { > > > > > + struct ieee802154_addr *addr; > > > > > > > > Why is this a pointer? > > > > > > No reason anymore, I've changed this member to be a regular structure. > > > > > > > ok. > > > > > > > > > > > + u8 page; > > > > > + u8 channel; > > > > > + u16 superframe_spec; > > > > > + u8 link_quality; > > > > > + bool gts_permit; > > > > > + struct list_head node; > > > > > +}; > > > > > + > > > > > struct ieee802154_llsec_key_id { > > > > > u8 mode; > > > > > u8 id; > > > > > diff --git a/include/net/nl802154.h b/include/net/nl802154.h > > > > > index 145acb8f2509..cfe462288695 100644 > > > > > --- a/include/net/nl802154.h > > > > > +++ b/include/net/nl802154.h > > > > > @@ -58,6 +58,9 @@ enum nl802154_commands { > > > > > > > > > > NL802154_CMD_SET_WPAN_PHY_NETNS, > > > > > > > > > > + NL802154_CMD_NEW_COORDINATOR, > > > > > + NL802154_CMD_KNOWN_COORDINATOR, > > > > > + > > > > > > > > NEW is something we never saw before and KNOWN we already saw before? > > > > I am not getting that when I just want to maintain a list in the user > > > > space and keep them updated, but I think we had this discussion > > > > already or? Currently they do the same thing, just the command is > > > > different. The user can use it to filter NEW and KNOWN? Still I am not > > > > getting it why there is not just a start ... event, event, event .... > > > > end. and let the user decide if it knows that it's new or old from its > > > > perspective. > > > > > > Actually we already discussed this once and I personally liked more to > > > handle this in the kernel, but you seem to really prefer letting the > > > user space device whether or not the beacon is a new one or not, so > > > I've updated both the kernel side and the userspace side to act like > > > this. > > > > > > > I thought there was some problem about when the "scan-op" is running > > and there could be the case that the discovered PANs are twice there, > > but this looks more like handling UAPI features as separate new and > > old ones? I can see that there can be a need for the first case? > > I don't think there is a problem handling this on one side or the > other, both should work identically. I've done the change anyway in v2 > :) > ok. > > > > > /* add new commands above here */ > > > > > > > > > > #ifdef CONFIG_IEEE802154_NL802154_EXPERIMENTAL > > > > > @@ -133,6 +136,8 @@ enum nl802154_attrs { > > > > > NL802154_ATTR_PID, > > > > > NL802154_ATTR_NETNS_FD, > > > > > > > > > > + NL802154_ATTR_COORDINATOR, > > > > > + > > > > > /* add attributes here, update the policy in nl802154.c */ > > > > > > > > > > #ifdef CONFIG_IEEE802154_NL802154_EXPERIMENTAL > > > > > @@ -218,6 +223,45 @@ enum nl802154_wpan_phy_capability_attr { > > > > > NL802154_CAP_ATTR_MAX = __NL802154_CAP_ATTR_AFTER_LAST - 1 > > > > > }; > > > > > > > > > > +/** > > > > > + * enum nl802154_coord - Netlink attributes for a coord > > > > > + * > > > > > + * @__NL802154_COORD_INVALID: invalid > > > > > + * @NL802154_COORD_PANID: PANID of the coordinator (2 bytes) > > > > > + * @NL802154_COORD_ADDR: coordinator address, (8 bytes or 2 bytes) > > > > > + * @NL802154_COORD_CHANNEL: channel number, related to @NL802154_COORD_PAGE (u8) > > > > > + * @NL802154_COORD_PAGE: channel page, related to @NL802154_COORD_CHANNEL (u8) > > > > > + * @NL802154_COORD_PREAMBLE_CODE: Preamble code used when the beacon was received, > > > > > + * this is PHY dependent and optional (u8) > > > > > + * @NL802154_COORD_MEAN_PRF: Mean PRF used when the beacon was received, > > > > > + * this is PHY dependent and optional (u8) > > > > > + * @NL802154_COORD_SUPERFRAME_SPEC: superframe specification of the PAN (u16) > > > > > + * @NL802154_COORD_LINK_QUALITY: signal quality of beacon in unspecified units, > > > > > + * scaled to 0..255 (u8) > > > > > + * @NL802154_COORD_GTS_PERMIT: set to true if GTS is permitted on this PAN > > > > > + * @NL802154_COORD_PAYLOAD_DATA: binary data containing the raw data from the > > > > > + * frame payload, (only if beacon or probe response had data) > > > > > + * @NL802154_COORD_PAD: attribute used for padding for 64-bit alignment > > > > > + * @NL802154_COORD_MAX: highest coordinator attribute > > > > > + */ > > > > > +enum nl802154_coord { > > > > > + __NL802154_COORD_INVALID, > > > > > + NL802154_COORD_PANID, > > > > > + NL802154_COORD_ADDR, > > > > > + NL802154_COORD_CHANNEL, > > > > > + NL802154_COORD_PAGE, > > > > > + NL802154_COORD_PREAMBLE_CODE, > > > > > > > > Interesting, if you do a scan and discover pans and others answers I > > > > would think you would see only pans on the same preamble. How is this > > > > working? > > > > > > Yes this is how it is working, you only see PANs on one preamble at a > > > time. That's why we need to tell on which preamble we received the > > > beacon. > > > > > > > But then I don't know how you want to change the preamble while > > scanning? > > Just to be sure: here we are talking about reporting the beacons that > were received and the coordinators they advertise. Which means we > _need_ to tell the user on which preamble code it was, but we don't yet > consider any preamble code changes here on the PHY. > but there is my question, how coordinators can advertise they are running on a different preamble as they sent on the advertisement. And what I thought was that the preamble is a non changeable thing, more specifically 4 octet all zero (preamble) followed by 0xA7 (SFD)). I know there are transceivers to change at least the SFD value, but then I was assuming you were running out of spec (some people doing that to ehm... "fake secure" their 802.15.4 communication as I heard). > > I know there are registers for changing the preamble and I > > thought that is a vendor specific option. However I am not an expert > > to judge if it's needed or not, but somehow curious how it's working. > > I guess this is a problem that we must delegate to the drivers, very > much like channel changes, no? > yes. - Alex