netdev - Re: pull-request: wireless-next-2023-03-30

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZEkvbvIZiUnbK45N@hoboy.vegasvil.org>
Date:   Wed, 26 Apr 2023 07:04:30 -0700
From:   Richard Cochran <richardcochran@...il.com>
To:     "Stern, Avraham" <avraham.stern@...el.com>
Cc:     "Greenman, Gregory" <gregory.greenman@...el.com>,
        "kuba@...nel.org" <kuba@...nel.org>,
        "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
        "johannes@...solutions.net" <johannes@...solutions.net>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: pull-request: wireless-next-2023-03-30

On Tue, Apr 25, 2023 at 07:43:40PM -0700, Richard Cochran wrote:
> Your design might touch upon a number of points...

I forgot the most important point, IMO:

How will you handle time distribution across a wireless network?

Consider the following simple case.

GPS Radio ------> Station-A ~~~~~~ AP ~~~~~~ Station-B
           1PPS              WiFi      WiFi

Here Station-A should become the PTP server, and Station-B should
become a PTP client.  In 1588, this is accomplished by forming a
spanning tree over the wired network, based on time quality fields
advertised.

AFAICT, the standards provide almost no hint how this is supposed to
work over WiFi.  I'd like to know your plans for solving this aspect.
Just exposing FTM to user space doesn't help all.

It gets even better.

Replace that "AP" with "mesh network" and image Station-B moves around...
What happens next?

Thanks,
Richard