Kernel GTP » History » Version 5
laforge, 04/25/2018 12:11 PM
half-way migration to osmo-ggsn, more work needed
1 | 5 | laforge | h1. OsmoGGSN and Linux Kernel accelerated GTP-U |
---|---|---|---|
2 | 2 | laforge | |
3 | 5 | laforge | {{>toc}} |
4 | 1 | laforge | |
5 | 5 | laforge | OsmoGGSN has support to use the Linux kernel GTP-U code to accelerate the data/user plane while still implementing the control plane (GTP-C) in userspace in OpenGGSN. |
6 | |||
7 | 2 | laforge | For more information about the Linux kernel GTP-U code, please see [[linux-kernel-gtp-u:]] |
8 | |||
9 | 5 | laforge | h2. Building OsmoGGSN with kernel which has GTP-U support |
10 | 1 | laforge | |
11 | At the time of writing (2017-01-09) of this wiki, below listed distributions have support of GTP kernels : |
||
12 | |||
13 | * Debian 4.9.1-1~exp1 - Debian's latest experimental build |
||
14 | * Ubuntu 16.10 kernel 4.8 |
||
15 | * OpenSUSE Tumbleweed (stable) 4.8 (.12) |
||
16 | * Fedora 25 kernel 4.8 |
||
17 | |||
18 | Following two Debian kernels do not activate GTP kernel module during build: 4.8.0 and 4.9.0. |
||
19 | |||
20 | Check if package @libc-ares-dev@ is installed and if not please add it. |
||
21 | |||
22 | Ubuntu 16.10, kernel 4.8.0-30-generic is used. |
||
23 | |||
24 | 5 | laforge | h3. Installing dependencies and build library @libosmocore@ |
25 | 1 | laforge | |
26 | 5 | laforge | You can install required dependency packages with: |
27 | 1 | laforge | |
28 | <pre> |
||
29 | 5 | laforge | sudo apt install libtalloc-dev libpcsclite-dev |
30 | 1 | laforge | </pre> |
31 | |||
32 | 5 | laforge | Please follow instructions provided at [[cellular-infrastructure:Build from source]] in order to install libosmocore |
33 | 1 | laforge | |
34 | |||
35 | 5 | laforge | h3. Installing dependencies and build library @libgtpnl@ |
36 | 1 | laforge | |
37 | 5 | laforge | You can install dependencies with: |
38 | |||
39 | 1 | laforge | <pre> |
40 | 5 | laforge | sudo apt install libmnl-dev |
41 | 1 | laforge | </pre> |
42 | |||
43 | 5 | laforge | Then build libgtpnl like this |
44 | <pre> |
||
45 | git clone git://git.osmocom.org/libgtpnl.git |
||
46 | cd libgtpnl |
||
47 | autoreconf -fi |
||
48 | ./configure |
||
49 | make |
||
50 | sudo make install |
||
51 | sudo ldconfig |
||
52 | </pre> |
||
53 | 1 | laforge | |
54 | 5 | laforge | h3. osmo-ggsn |
55 | |||
56 | Build OsmoGGSN like this: |
||
57 | |||
58 | 1 | laforge | <pre> |
59 | 5 | laforge | git clone git://git.osmocom.org/osmo-ggsn.git |
60 | cd osmo-ggsn |
||
61 | 1 | laforge | ./configure --enable-gtp-linux |
62 | 5 | laforge | make |
63 | 1 | laforge | sudo make install |
64 | sudo ldconfig |
||
65 | </pre> |
||
66 | |||
67 | Following message is shown at end of the command: @ ./configure --enable-gtp-linux@ |
||
68 | |||
69 | <pre> |
||
70 | 5 | laforge | OsmoGGSN Configuration: |
71 | 1 | laforge | GTP Linux kernel support: yes |
72 | </pre> |
||
73 | |||
74 | This means that appropriate header files are available. |
||
75 | |||
76 | h2. Using OpenGGSN with kernel which has GTP-U support |
||
77 | |||
78 | In order to find out whether gtp.ko module is available we can enter following command: |
||
79 | |||
80 | <pre> |
||
81 | find /lib/modules/`uname -r` -name gtp.ko |
||
82 | </pre> |
||
83 | |||
84 | Output below shows that gtp.ko module is present: |
||
85 | |||
86 | <pre> |
||
87 | /lib/modules/4.8.0-30-generic/kernel/drivers/net/gtp.ko |
||
88 | </pre> |
||
89 | |||
90 | |||
91 | 5 | laforge | We are loading module gtp from kernel issuing command: <pre>sudo modprobe gtp</pre> |
92 | 1 | laforge | |
93 | when you enter: |
||
94 | <pre> |
||
95 | lsmod | grep gtp |
||
96 | </pre> |
||
97 | |||
98 | then more information about gtp and related udp tunnel can be obtained: |
||
99 | |||
100 | <pre> |
||
101 | gtp 28672 0 |
||
102 | udp_tunnel 16384 1 gtp |
||
103 | </pre> |
||
104 | |||
105 | |||
106 | Some helpful tools are available in: @libgtpnl/tools@ |
||
107 | |||
108 | you can get more details about gtp-tunnel, entering command from the OpenGGSN shell: |
||
109 | |||
110 | <pre> |
||
111 | sudo ./gtp-tunnel list |
||
112 | </pre> |
||
113 | |||
114 | Output will be similar to: |
||
115 | <pre> |
||
116 | version 1 tei 1/0 ms_addr 192.168.0.2 sgsn_addr 127.0.0.2 |
||
117 | </pre> |
||
118 | |||
119 | 5 | laforge | Note: OsmoGGSN is started by: |
120 | 1 | laforge | <pre> |
121 | 5 | laforge | sudo osmo-ggsn -c osmo-ggsn.conf |
122 | 1 | laforge | </pre> |
123 | |||
124 | Related output should be similar to the one shown below: |
||
125 | |||
126 | <pre> |
||
127 | 5 | laforge | FIXME |
128 | 1 | laforge | </pre> |
129 | |||
130 | 5 | laforge | You can now start to establish PDP contexts to your new osmo-ggsn instance, from [[OsmoSGSN:]], @sgsnemu@ or third-party SGSNs |