Project

General

Profile

Bug #1880

handling of reserved bit in flag octet broken

Added by laforge almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
12/15/2016
Due date:
% Done:

100%

Estimated time:
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

Related to Linux Kernel GTP-U - Bug #1879: reserved bit in GTPv1 header set wrongClosed2016-12-15

Related to OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codeClosed2016-02-23

History

#1 Updated by laforge almost 2 years ago

  • Related to Bug #1879: reserved bit in GTPv1 header set wrong added

#2 Updated by laforge almost 2 years ago

  • Related to Feature #1621: test + document OpenGGSN with osmo-gtp-kernel code added

#3 Updated by laforge over 1 year ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

#4 Updated by laforge over 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)