Feature #2519
closedGTP-U sequence numbers are enabled unconditionally
80%
Description
In order to support and test all possible configuration, it should be possible to disable GTP-U sequence numbers on both the GGSN as well as the sgsnemu side.
Updated by laforge over 6 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 20
first had to clean up the manually edited gengetopt-generated option parser, but now actually working on this.
Updated by laforge over 6 years ago
- % Done changed from 20 to 80
See https://gerrit.osmocom.org/#/q/project:osmo-ggsn+topic:gpdu-seq and specifically
pending some automatic testing for with/without seq-nr on both sgsnemu and ggsn side.
Updated by laforge over 6 years ago
patches merged to master, manually verified both with and without g-pdu sequence numbers onboth sgsnemu and osmo-ggsn.
Updated by laforge over 6 years ago
- Checklist item ttcn-3 testing added
- Checklist item possibly some automatic testing for sgsnemu side added
leaving this open as related tests are not written yet
Updated by laforge about 6 years ago
- Assignee changed from laforge to stsp
assigning to stsp for adding related test cases to the GGSN_Tests.ttcn test suite.
Updated by stsp almost 6 years ago
Above test case has been merged.
Does this test provide sufficient coverage?
It seems sgsnemu shares its GTP code with osmo-ggsn.
Do we need a separate test for it?
Updated by stsp almost 6 years ago
- Status changed from In Progress to Resolved
No response to my above question yet.
Closing this issue since as far as I can tell we are done here. Please re-open if that is not the case.