Conversation
|
Thanks for your pr. could you please revert all changes introduced from your code formatter. |
|
@polydroi sorry for that, should be good now |
|
Added relevant tests to bluetooth.uts I did not add tests for, e.g., HCI_Cmd_LE_Set_Extended_Scan_Parameters, as the original version did not have them either. |
| ByteEnumField("patype", 0, {0: "public", 1: "random"}), | ||
| LEMACField("paddr", None), | ||
| ByteEnumField("atype", 0, {0: "public", 1: "random"}), | ||
| ByteEnumField("peer_addr_type", 0, {0: "public", 1: "random"}), |
There was a problem hiding this comment.
What is the reason for all the name changes. Are the old names incorrect?
The change of a field name might break existing applications.
There was a problem hiding this comment.
@polybassa, the latest versions of the standard refer to these fields as *_address or *_address_type. I changed them because in Scapy, some packets used the standard terminology, while others did not. So it is mostly about coherence across all packets, but yes, the "correct" field name would be the longer one.
We can also stick with atype, patype, ... for all I care, as long as all packets use the same names. If this is the preferred direction I can update the PR, but it will still break some existing applications probably.
There was a problem hiding this comment.
Could you use
Line 109 in ed0707e
Thanks !
Introduces various stuff from Bluetooth 5.0+ plus some standardized field naming across packets for clarity and interoperability. Additionally covers an edge case in the HCI command handling.
What was added:
What was modified:
r.code in (0x0e, 0x0f)to cope with commands such as "Create Connection" which is async and returns a "Pending" status.I also added and executed the tests in bluetooth.uts