Actions
Bug #1880
closedhandling of reserved bit in flag octet broken
Start date:
12/15/2016
Due date:
% Done:
100%
Spec Reference:
Description
When we receive a GTP1U message whose processing fails for some reason (e.g. unknown TEID), we send an error message in response. This error message is generated by gtp_error_ind_resp() which unconditionall uses get_seq() to determine the sequence number. However, GTP-U packets don't have sequence numbers, and thus an error message like "Unknown packet flags: 56" is printed.
This is misleading, as the respective flags without a sequence number is perfectly legal for GTP1U, but not GTP1C
Related issues
Updated by laforge over 7 years ago
- Related to Bug #1879: reserved bit in GTPv1 header set wrong added
Updated by laforge over 7 years ago
- Related to Feature #1621: test + document OpenGGSN with osmo-gtp-kernel code added
Updated by laforge about 7 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Actions
