Hi Archie, > When receiving an L2CAP_CONFIGURATION_REQ with an unknown config > type, currently we will reply with L2CAP_CONFIGURATION_RSP with > a list of unknown types as the config param. However, this is not > a correct format of config param. > > As described in the bluetooth spec v5.2, Vol 3, Part A, Sec 5, > the config param should consists of type, length, and optionally > data. > > This patch copies the length and data from the received > L2CAP_CONFIGURATION_REQ and also appends them to the config param > of the corresponding L2CAP_CONFIGURATION_RSP to match the format > of the config param according to the spec.
any chance you could add btmon traces to the commit message to show the wrong behavior? Regards Marcel
