Closed ghost closed 1 year ago
There are 16385 "z", not 16383. Therefore, it goes through a PER string fragmentation process, which may be buggy ?! Investigation is required...
The issue should have been solved in the last series of commits. Thanks for reporting the bug.
I have forged a NGAP frames (NGSetupRequest) with RANNodeName field set to 16384 "z" chars. But the APER encoding of this payload has a length of 51 bytes, only ...
With 16383 "z" chars, the APER encoding of the same NGSetupRequest has a size of 16436 bytes.
Do you have any explanation/idea ?