Advertising and Performing a Connection Over 2MPHY (2Mbps)

RE: Advertising and Performing a Connection Over 2MPHY (2Mbps)

Youssif — Wed, 05 Sep 2018 08:44:55 GMT

Oh I see, that makes sense. Thank you for your answer.

RE: Advertising and Performing a Connection Over 2MPHY (2Mbps)

Susheel Nuguru — Wed, 05 Sep 2018 08:39:19 GMT

What I mean't was about the feature to say explicitly disallow connection or reject connections based on PHY. Disallowing or restricting 1 PHY .explicitly is not possible right now, does not mean that you can only establish connections on 1M PHY

What you wanted was to allow connection on specific PHY, they are two different features.

RE: Advertising and Performing a Connection Over 2MPHY (2Mbps)

Youssif — Tue, 04 Sep 2018 13:27:01 GMT

Thanks a lot, I was able to establish a connection over 2MPHY and verified with a sniffer. However, from your sentence:- "For 6.1 there is no way for the application to disallow to create a connection on 1M" it seems that you are implying that a connection will always occur on 1MPHY?

RE: Advertising and Performing a Connection Over 2MPHY (2Mbps)

Susheel Nuguru — Fri, 31 Aug 2018 09:34:55 GMT

Hi,

The stack team noticed that this could be caused do to some null parameters in the arguments in connect request.

I believe the workaround for 6.1 is to set scan_phys = 1M | 2M

Note: For 6.1, there is no way for the application to disallow to create a connection on 1M. The behavior may remain the same or change is a possible 6.2 or 6.1.1 (if such a SoftDevice is released).

To disallow establishing connections on CODED: Do not use extended scanning
To disallow establishing connections on 2M: Do not use extended scanning