https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092016-11-09T09:47:48ZOpen Source Mobile CommunicationsOsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=23802016-11-09T09:47:48Zlaforge
<ul><li><strong>Assignee</strong> set to <i>wirelesss</i></li><li><strong>Priority</strong> changed from <i>Low</i> to <i>Normal</i></li></ul> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=23812016-11-09T09:49:45Zlaforge
<ul><li><strong>Subject</strong> changed from <i>test OpenGGSN with new osmo-gtp-kernel code</i> to <i>test + document OpenGGSN with osmo-gtp-kernel code</i></li></ul><p>please try to find a linux distribution/version that already has the kernel support for GTP-U included, i.e. let's avoid you having to re-build the linux kernel for this task. Once you have the required kernel, you will need to compile libgtpnl, and rebuild openggsn to link against the libgtpnl for supporting the GTP-u in the kernel plane.</p>
<p>Please also make sure that the process of building + using OpenGGSN with kernel-gtp is properly documented in the OpenGGSN project wiki here on osmocom.org.</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=25252016-12-02T14:13:58Zwirelesss
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=25362016-12-02T18:42:01Zwirelesss
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul><p>Looking for a linux distribution/version, which already has the kernel support for GTP-U included.<br />Installing of kernel 4.8.</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=25372016-12-04T08:53:25Zlaforge
<ul></ul><p>On Fri, Dec 02, 2016 at 06:42:01PM +0000, wirelesss [REDMINE] wrote:</p>
<blockquote>
<p>Looking for a linux distribution/version, which already has the kernel support for GTP-U included.<br />Installing of kernel 4.8.</p>
</blockquote>
<p>"debian unstable" has 4.8.0 kernel, but unfortunately doesn't seem to<br />activate the GTP kernel module during build :(</p>
<p>It would be great if somebody could request that from the debian<br />developer in charge of pcakaging the kernel, together with an<br />explanation.</p>
<p>-- <br />- Harald Welte <<a class="email" href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a class="external" href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a>
============================================================================<br />"Privacy in residential applications is a desirable marketing option." <br />(ETSI EN 300 175-7 Ch. A6)</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=25382016-12-04T10:45:02Zlaforge
<ul></ul><p>I just requested Debian to enable CONFIG_GTP in Debian bug report<br />846913: <a class="external" href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846913">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846913</a></p>
<p>This of couse doesn't anwer your question on which distribution <strong>right<br />now</strong> ships a 4.8.0 kernel or later. But at least it should make sure<br />that future users of the next stable debian release will have the<br />feature from day one.</p>
<p>Ubuntu 16.10 has kernel 4.8, and according to config.common.ubuntu in<br /><a class="external" href="https://launchpad.net/ubuntu/+archive/primary/+files/linux_4.8.0-27.29.diff.gz">https://launchpad.net/ubuntu/+archive/primary/+files/linux_4.8.0-27.29.diff.gz</a><br />they do enable CONFIG_GTP</p>
<p>OpenSUSE Tumbleweed (stable) also seems to have 4.8 (.12), and also<br />seems to have it enabled:<br /><a class="external" href="https://github.com/openSUSE/kernel-source/blob/stable/config/x86_64/default">https://github.com/openSUSE/kernel-source/blob/stable/config/x86_64/default</a></p>
<p>Fedora 25 also seems to use 4.8, and according to<br /><a class="external" href="http://pkgs.fedoraproject.org/cgit/rpms/kernel.git/tree/config-generic?h=f25">http://pkgs.fedoraproject.org/cgit/rpms/kernel.git/tree/config-generic?h=f25</a><br />CONFIG_GTP is enabled!</p>
<p>-- <br />- Harald Welte <<a class="email" href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a class="external" href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a>
============================================================================<br />"Privacy in residential applications is a desirable marketing option." <br />(ETSI EN 300 175-7 Ch. A6)</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=25712016-12-07T16:17:47Zwirelesss
<ul><li><strong>% Done</strong> changed from <i>10</i> to <i>20</i></li></ul><p>After installation of Ubuntu 16.10 (4.8.0-30-generic) on a virtual machine, <code>libgtpnl libsomsocore</code> were compiled and OpenGGSN was rebuild.</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=25922016-12-09T12:28:26Zwirelesss
<ul></ul><p>wiki page of building + using OpenGGSN with kernel-gtp is drafted and it is under construction.</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26082016-12-13T18:02:20Zwirelesss
<ul><li><strong>% Done</strong> changed from <i>20</i> to <i>30</i></li></ul><p>Starting OpenGGSN with option --gtp-linux leads to following:</p>
<p>from OpenGGSN the following messages are to be seen:</p>
<p>gtp.c:701 GTP: gtp_newgsn() started<br />gtp-kernel.c:156 GTP kernel configured</p>
<p>length: 12 content: 32 1a 00 04 00 00 00 00 00 00 00 00 : Unknown PDP context</p>
<p>from SGSN : length: 52 content: 38 ff 00 2c 00 00 00 00 45 00 00 2c 03 bb 00 00 6c 06 ad 69 0c 9b d0 61 c0 a8 00 03 52 08 04 05 f5 19 a2 62 04 40 61 02 60 12 20 00 87 f2 00 00 02 04 05 64 : Unknown PDP context.</p>
<p>Having that circumstance, it is not possible to run PS traffic and to load web site on the test mobile station.</p>
<p>Addinng to wiki site command for starting OpenGGSN<br />sudo ggsn --gtp-linux -c ggsn.conf -f</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26102016-12-13T23:26:00Zlaforge
<ul></ul><p>Hi,</p>
<p>On Tue, Dec 13, 2016 at 06:02:20PM +0000, wirelesss [REDMINE] wrote:</p>
<blockquote>
<p>Starting OpenGGSN with option --gtp-linux leads to following:</p>
<p>[...]</p>
<p>from SGSN : length: 52 content: 38 ff 00 2c 00 00 00 00 45 00 00 2c 03<br />bb 00 00 6c 06 ad 69 0c 9b d0 61 c0 a8 00 03 52 08 04 05 f5 19 a2 62<br />04 40 61 02 60 12 20 00 87 f2 00 00 02 04 05 64 : Unknown PDP context.</p>
<p>Having that circumstance, it is not possible to run PS traffic and to<br />load web site on the test mobile station.</p>
</blockquote>
<p>so you have discovered a problem. But where is the comprehensive bug<br />report? Where are the protocol traces (pcap files) of the Gb and<br />Gp interface while the above log lines of OpenGGSN where observed.</p>
<p>As somebody who receives bug reports from others, you should understand<br />how important it is to first collect all the relevant information and<br />then post it together. This is very important in terms of efifciency.</p>
<p>It might even make sense to raise all this ina separate bug ticket and<br />mark that related to this ticket on whcih you are working on.</p>
<p>-- <br />- Harald Welte <<a class="email" href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a class="external" href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a>
============================================================================<br />"Privacy in residential applications is a desirable marketing option." <br />(ETSI EN 300 175-7 Ch. A6)</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26132016-12-14T09:51:35Zwirelesss
<ul></ul><p>laforge wrote:</p>
<blockquote>
<p>Hi,</p>
<p>On Tue, Dec 13, 2016 at 06:02:20PM +0000, wirelesss [REDMINE] wrote:</p>
<blockquote>
<p>Starting OpenGGSN with option --gtp-linux leads to following:</p>
<p>[...]</p>
<p>from SGSN : length: 52 content: 38 ff 00 2c 00 00 00 00 45 00 00 2c 03<br />bb 00 00 6c 06 ad 69 0c 9b d0 61 c0 a8 00 03 52 08 04 05 f5 19 a2 62<br />04 40 61 02 60 12 20 00 87 f2 00 00 02 04 05 64 : Unknown PDP context.</p>
<p>Having that circumstance, it is not possible to run PS traffic and to<br />load web site on the test mobile station.</p>
</blockquote>
<p>so you have discovered a problem. But where is the comprehensive bug<br />report? Where are the protocol traces (pcap files) of the Gb and<br />Gp interface while the above log lines of OpenGGSN where observed.</p>
<p>As somebody who receives bug reports from others, you should understand<br />how important it is to first collect all the relevant information and<br />then post it together. This is very important in terms of efifciency.</p>
<p>It might even make sense to raise all this ina separate bug ticket and<br />mark that related to this ticket on whcih you are working on.</p>
<p>-- <br />- Harald Welte <<a class="email" href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a class="external" href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a>
============================================================================<br />"Privacy in residential applications is a desirable marketing option." <br />(ETSI EN 300 175-7 Ch. A6)</p>
</blockquote>
<p>Hi,</p>
<p>Yes. I agree. I have sent this post / note a bit earlier without complete troubleshooting information.<br />I thought it would be valuable just as a progress of this Ticket. I do understand that in this case it was just useless.</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26172016-12-14T19:21:57Zwirelesss
<ul><li><strong>File</strong> <a href="/attachments/2464">openbsc.log</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2464/openbsc.log">openbsc.log</a> added</li><li><strong>File</strong> <a href="/attachments/2465">sgsn.log</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2465/sgsn.log">sgsn.log</a> added</li><li><strong>File</strong> <a href="/attachments/2466">ggsn.log</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2466/ggsn.log">ggsn.log</a> added</li></ul><p>After building and compiling of openbsc, libgtpnl and OpenGGSN on a virtual machine running Ubuntu 16.10 with kernel 4.8.0-30-generic following was observed:</p>
<p>from SGSN console (time stamps:08:55:23 - 08:56:57) it is to be seen that GPRS attach is accepted and PDP CONTEXT activation is acknowledged. Please refer to sgsn.log file</p>
<p>at time stamp: 08:57:05 following message is present:</p>
<pre>
gtp.c:2619 Packet from 127.0.0.1:2152, length: 82 content: 38 ff 00 4a 00 00 00 00 45 00 00 4a 51 d5 00 00 2b
11 6d 14 08 08 08 08 c0 a8 00 02 00 35 40 01 00 36 74 a4 0d ce 81 80 00 01 00 01 00 00 00 00 03 77 77 77 04 7a
6f 63 6b 03 63 6f 6d 00 00 01 00 01 c0 0c 00 01 00 01 00 00 17 64 00 04 55 0d 93 d7 : Unknown PDP context
Wed Dec 14 08:57:05 2016
<0025> gtp.c:213 Unknown packet flag: 56
</pre>
<p>Output from the GGSN console is:<br /><pre>
gtp.c:2581 Packet from 127.0.0.2:2152, length: 12 content: 32 1a 00 04 00 00 00 00 00 00 00 00 : Unknown PDP context
</pre></p>
<p>The pcap file from Gb interface to be attached.</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26182016-12-15T11:26:21Zlaforge
<ul></ul><p>On Wed, Dec 14, 2016 at 07:21:57PM +0000, wirelesss [REDMINE] wrote:</p>
<blockquote>
<p>The pcap file from Gb interface to be attached.</p>
</blockquote>
<p>As the problem is on the Gp interface, does it also include Gp?<br />-- <br />- Harald Welte <<a class="email" href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a class="external" href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a>
============================================================================<br />"Privacy in residential applications is a desirable marketing option." <br />(ETSI EN 300 175-7 Ch. A6)</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26192016-12-15T11:28:18Zlaforge
<ul></ul><p>... and, as raised severla times, what is the output of the "gtp-tunnel<br />list" after the pdp context is established?</p>
<p>Are you running openggsn with the "-d" flage to get debug lots?</p>
<p>-- <br />- Harald Welte <<a class="email" href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a class="external" href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a>
============================================================================<br />"Privacy in residential applications is a desirable marketing option." <br />(ETSI EN 300 175-7 Ch. A6)</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26222016-12-15T15:27:29Zwirelesss
<ul><li><strong>File</strong> <a href="/attachments/2468">gtp0.pcapng</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2468/gtp0.pcapng">gtp0.pcapng</a> added</li></ul> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26232016-12-15T18:02:50Zwirelesss
<ul><li><strong>File</strong> <a href="/attachments/2469">Gp_trace.pcapng</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2469/Gp_trace.pcapng">Gp_trace.pcapng</a> added</li></ul><p>It was found that communication between SGSN and GGSN is running, but at certain point GGSN switches Reserved bit to 1. This can be seen from the GGSN standard query response. In the attach Gp_trace.pcapng file we can see that in the frame no: 1082, 1889 etc.</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26282016-12-15T19:52:02Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-3 priority-high3 closed" href="/issues/1879">Bug #1879</a>: reserved bit in GTPv1 header set wrong</i> added</li></ul> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26302016-12-15T19:52:15Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-2 priority-default closed" href="/issues/1880">Bug #1880</a>: handling of reserved bit in flag octet broken</i> added</li></ul> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26412016-12-16T17:20:07Zwirelesss
<ul><li><strong>% Done</strong> changed from <i>30</i> to <i>60</i></li></ul><p>Test that relates to OpenGGSN with osmo-gtp-kernel code has been executed.<br />As conclusion: so-called "reserved" bit in the flags octet of the GTPv1 header is set to value '1'. This is done in the existing Linux Kernel GTP code. This operation is incorrect. As per 3GPP TS 129.060 (ETSI TS 129 060 V13.5.0), Chapter 6, bit 4 in octet 1, should be equal to value '0'.</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26422016-12-17T09:18:12Zlaforge
<ul></ul><p>On Fri, Dec 16, 2016 at 05:20:07PM +0000, wirelesss [REDMINE] wrote:</p>
<blockquote>
<p>Test that relates to OpenGGSN with osmo-gtp-kernel code has been<br />executed. As conclusion: so-called "reserved" bit in the flags octet<br />of the GTPv1 header is set to value '1'. This is done in the existing<br />Linux Kernel GTP code. This operation is incorrect. As per 3GPP TS<br />129.060 (ETSI TS 129 060 V13.5.0), Chapter 6, bit 4 in octet 1, should<br />be equal to value '0'.</p>
</blockquote>
<p>please note that this is <strong>not</strong> the actual error cause. The invalid<br />reserved bit is just noted/complained about when constructing the GTP<br />error messge in response to the downlink message (icmp echo reply in<br />your tests).</p>
<p>The real cause seems to be some invalid / non-synchronized TEI/TID (tunnel<br />ID) for the GTP-U in downlink direction (GGSN->SGSN).</p>
<p>Please compare the TEI GTP-C negotiates/establishes for the user plane<br />in both directions at PDP CTX ACT time with those you see on the wire.<br />-- <br />- Harald Welte <<a class="email" href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a class="external" href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a>
============================================================================<br />"Privacy in residential applications is a desirable marketing option." <br />(ETSI EN 300 175-7 Ch. A6)</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=26832016-12-22T11:20:40Zwirelesss
<ul><li><strong>File</strong> <a href="/attachments/2478">ggsn_log_22Dec.log</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2478/ggsn_log_22Dec.log">ggsn_log_22Dec.log</a> added</li><li><strong>File</strong> <a href="/attachments/2479">sgsn_log_22Dec.log</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2479/sgsn_log_22Dec.log">sgsn_log_22Dec.log</a> added</li><li><strong>File</strong> <a href="/attachments/2480">Lo_trace.pcapng</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2480/Lo_trace.pcapng">Lo_trace.pcapng</a> added</li><li><strong>File</strong> <a href="/attachments/2481">gtp0_22dec.pcapng</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2481/gtp0_22dec.pcapng">gtp0_22dec.pcapng</a> added</li><li><strong>File</strong> <a href="/attachments/2482">gtp_tunnel_list.log</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2482/gtp_tunnel_list.log">gtp_tunnel_list.log</a> added</li><li><strong>File</strong> <a href="/attachments/2483">osmso_sgsn_vty_22Dec.log</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2483/osmso_sgsn_vty_22Dec.log">osmso_sgsn_vty_22Dec.log</a> added</li></ul><p>TEID for GTP-C has been compared. SonyEricsson K790i mobile has been used.</p>
<p>In file lo_trace.pcapng next information can be seen.</p>
<p>In message "create PDP context request" (MS to Network direction - Uplinik), TEIDs have the following values:<br />Frame No.: 2569<br />TEID:0x00000000<br />TEID Data I: 0x00000001<br />TEID Control Plane: 0x00000001</p>
<p>In message "create PDP context response message" (Network to MS direction - Downlink) shows next TEIDs:<br />Frame No.: 2570<br />TEID:0x00000001<br />TEID Data I: 0x00000001<br />TEID Control Plane: 0x00000001</p>
<p>Message Standard query 0x0dce A wap.sonyericsson.com, includes TEIDs as presented below:<br />Frame No.: 2579<br />TEID:0x00000001</p>
<p>Frame No.: 2584 which is Standart query response message to frame no. 2579.<br />TEID:0x00000000</p>
<p>The output from gtp-tunnel list command is:<br /><pre>
version 1 tei 1/0 ms_addr 192.168.0.2 sgsn_addr 127.0.0.2
</pre></p>
<p>OpenGGSN log shows: teid 1. Part of this log is presented in the next lines:</p>
<pre>
<000c> gtp.c:701 GTP: gtp_newgsn() started
<0002> gtp-kernel.c:123 Using the GTP kernel mode (genl ID is 27)
<0002> gtp-kernel.c:156 GTP kernel configured
<000b> control_if.c:693 CTRL at 127.0.0.1 4257
version 1
teid 1
address (6)
f1 21 c0 a8 0 2
sgsn-addr (4)
7f 0 0 2
<000c> gtp.c:2581 Packet from 127.0.0.2:2152, length: 12 content: 32 1a 00 04 00 00 00 00 00 00 00 00 : Unknown PDP context
<000c> gtp.c:2581 Packet from 127.0.0.2:2152, length: 12 content: 32 1a 00 04 00 00 00 00 00 00 00 00 : Unknown PDP context
<000c> gtp.c:2581 Packet from 127.0.0.2:2152, length: 12 content: 32 1a 00 04 00 00 00 00 00 00 00 00 : Unknown PDP context
version 1
teid 1
address (6)
f1 21 c0 a8 0 2
sgsn-addr (4)
7f 0 0 2
</pre>
<p>TEIDs are different or non-synchronized.</p>
<p>TEID in Frame No.: 2584 or Standard query response message shall be equal to 1.</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=27452017-01-09T07:41:41Zlaforge
<ul></ul><p>laforge wrote:</p>
<blockquote>
<p>I just requested Debian to enable CONFIG_GTP in Debian bug report<br />846913: <a class="external" href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846913">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846913</a></p>
</blockquote>
<p>FYI, Debian has just activated the kernel GTP module in their latest experimental build "linux 4.9.1-1~exp1"</p>
<p>From the change log:<br /><pre>
* net: Enable GTP as module (Closes: #846913)
</pre></p>
<p>Would be good to collect all the information here about which distribution has kernel GTP and which not to a wiki page in the OpenGGSN project.</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=27602017-01-10T11:46:09Zwirelesss
<ul></ul><p>Information about which distribution has GTP kernel is collected and added in wiki site.</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=31092017-02-23T20:15:39Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>wirelesss</i> to <i>laforge</i></li></ul> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=31192017-02-23T21:21:10Zlaforge
<ul><li><strong>% Done</strong> changed from <i>60</i> to <i>80</i></li></ul><p>with the recent patches merged ahead of the openggsn 0.93 release, the kernel-gtp integration with GTPv1 is finally working in OpenGGSN. I could establish PDP contexts between sgsnemu and openggsn and route bi-directional IP packets through them.</p>
<p>I've also been playing around with using different TEI values on both side of the tunnels, to make sure there are no mistakes in the local/remote TEI value handling.</p>
<p>I'll be documenting the test setup shortly and put it on an OpenGGSN wiki page.</p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=31312017-02-24T18:00:22Zlaforge
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li></ul><p>the setup is documented (and has been verified) in the wiki. see <a class="wiki-page" href="https://projects.osmocom.org/projects/linux-kernel-gtp-u/wiki/Basic_Testing">Basic_Testing</a> and <a class="wiki-page" href="https://projects.osmocom.org/projects/openggsn/wiki/Kernel_GTP">Kernel_GTP</a></p> OsmoGGSN (former OpenGGSN) - Feature #1621: test + document OpenGGSN with osmo-gtp-kernel codehttps://projects.osmocom.org/issues/1621?journal_id=31772017-02-28T17:32:55Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>