1 OpenGGSN - Open Source GGSN
2 ===========================
4 This repository contains a C-language implementation of a GGSN (Gateway
5 GPRS Support Node), a core network element of ETSI/3GPP cellular
6 networks such as GPRS, EDGE, UMTS or HSPA.
8 OpenGGSN is part of the [Osmocom](https://osmocom.org/) Open Source
9 Mobile Communications projects, even thogh it was previously developed
15 The official homepage of the project is
16 https://osmocom.org/projects/openggsn/wiki
21 You can clone from the official libosmocore.git repository using
23 git clone git://git.osmocom.org/openggsn.git
25 There is a cgit interface at http://git.osmocom.org/openggsn/
30 There currently is no other documentation other than the wiki on the
31 homepage. It would be great if somebody would work towards a user
32 manual that can become part of the osmo-gsm-manuals project.
37 Discussions related to openggsn are happening on the
38 osmocom-net-gprs@lists.osmocom.org mailing list, please see
39 https://lists.osmocom.org/mailman/listinfo/osmocom-net-gprs for
40 subscription options and the list archive.
42 Please observe the [Osmocom Mailing List
43 Rules](https://osmocom.org/projects/cellular-infrastructure/wiki/Mailing_List_Rules)
49 Our coding standards are described at
50 https://osmocom.org/projects/cellular-infrastructure/wiki/Coding_standards
52 We us a gerrit based patch submission/review process for managing
53 contributions. Please see
54 https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit for
57 The current patch queue for OpenGGSN can be seen at
58 https://gerrit.osmocom.org/#/q/project:openggsn+status:open
70 OpenGGSN was originally developed and tested using Redhat 8.0 and 9.0
71 and is these days mostly developed on Debian GNU/Linux. It should run
72 also on other Linux distributions as well as FreeBSD, but this is
73 untested. Compilation on Solaris 2.8 has also been verified.
76 The tun driver is required for proper operation of openggsn. For Linux
77 kernels later than 2.4.7 the driver is typically included, but might
78 need to be configured for automatic loading:
80 1. Add the following line to /etc/modules.conf: alias char-major-10-200 tun
84 Installation from binary
85 ------------------------
87 OpenGGSN is built for common versions of Debian and Ubuntu as part of
88 the [Osmocom Nightly Builds](https://osmocom.org/projects/cellular-infrastructure/wiki/Nightly_Builds)
89 project. If you don't want to do development, it is suggested to simply
90 use those binary packages, rather than building yourself from source.
93 Installation from source
94 ------------------------
100 You need to be root in order to install the package, but not in order
108 Start the emulator as root using the command:
110 sgsnemu -l 10.0.0.50 -r 10.0.0.40 --createif --defaultroute
112 This will cause the sgsn emulator to bind to local address 10.0.0.50
113 and connect to the ggsn found at 10.0.0.40. It will first send off an
114 ECHO_REQUEST message. After this it will attempt to establish a pdp
115 context. If successful it will create a local interface and set up
116 routing. Now you should be able to ping through the connection. Use a
117 network analysator such as ethereal to monitor the traffic.
119 sgsnemu -h will show a list of available options.
121 sgsnemu -c sgsnemu.conf will use sgsnemu.conf as a configuration
122 file. A sample file is provided in examples/sgsnemu.conf.
125 Edit the configuration file ggsn.conf found under openggsn/examples.
126 Start the ggsn as root using the command:
128 ggsn --fg -c examples/ggsn.conf -l 10.0.0.40 --statedir ./
130 This will run the ggsn in foreground using the local interface
131 10.0.0.40. If you don't have a GSM network available for testing you
132 can use sgsnemu to test the GGSN.
138 Please contact the Mailing List above for community-based support.
144 OpenGGSN is an open source implementation of GPRS Support Nodes
145 (GSNs). It implements the GPRS tunneling protocol (GTP) version 0 and
148 OpenGGSN provides 3 components:
154 This library contains all functionality relating to the GTP
155 protocol. Use this library if you want to implement your own
156 GSN. gtplib supports both GTPv0 (GSM 09.60) and GTPv1 (3GPP
157 29.060). At the moment no interface documentation is available for
161 The ggsn implements a Gateway GPRS Support Node. The GGSN is a small
162 application which is provided in order to test and demonstrate the use
163 of gtplib. It is fully compliant to the 3GPP standards, but lacks
164 important functionality such as charging and management. Use this
165 application as a starting point if you want to build your own GGSN
166 with your own fancy VPN, management and charging functionality.
169 This application emulates a Serving GPRS Support Node (SGSN). sgsnemu
170 enables you to test your 3GPP core network without the need to invest
171 in a 3G radio access network. An important application of sgsnemu is
172 the testing of roaming connectivity through a GPRS roaming
173 exchange. sgsnemu will first attempt to use GTPv1. If unsuccessful it
174 will fallback to GTPv0.
180 Two experiments were performed in order to test the performance of
181 sgsnemu and ggsn. The ggsn used a 550 MHz Athlon with 384 MB of
182 RAM. sgsnemu used a 1 GHz Athlon with 256 MB of RAM. Both machines had
183 100 Mb/s NICs (RTL-8139) and were connected through a crossed patch
184 cable. Both tests were performed by sending ICMP echo packets from
187 89.5 Mb/s IP throughput when sending 10000 ICMP ping packets with a
188 payload of 1400 bytes. Transfer time 1.27 sec, no packets lost.
190 71.4 Mb/s IP throughput when sending 10000 ICMP ping packets with a
191 payload of 1000 bytes. Transfer time 1.15 sec, no packets lost.
193 12,1 Mb/s IP throughput when sending 10000 ICMP ping packets with a
194 payload of 100 bytes. Transfer time 0.84 sec, no packets lost.
203 Both ggsn and sgsnemu uses the tun package. You need at least tun
204 version 1.1. With Linux tun is normally included from kernel version
205 2.4.7. To configure automatic loading:
207 1. Add the following line to /etc/modules.conf: alias char-major-10-200 tun
210 Alternatively you can execute "modprobe tun" on the commandline.
212 For Solaris the tun driver needs to be installed manually. For general
213 information about tun see http://vtun.sourceforge.net/tun/
218 Gengetopt is required if you want to change the options defined in the
219 cmdline.ggo source file. You need at least gengetopt version 2.8. If
220 you are just going to compile the programs you don't need gengetopt.
222 To use gengetopt for the ggsn do the following:
224 gengetopt < cmdline.ggo --conf-parser
226 To use gengetopt for the sgsnemu do the following:
228 gengetopt < cmdline.ggo --conf-parser
230 For more information about gengetopt see
231 http://www.gnu.org/software/gengetopt/gengetopt.html
234 Compilation and Installation
235 ============================
241 You do not need to perform this step if you are only going to compile
244 1. Get version from somewhere: Script to extract version from configure.in
245 2. Copy the latest config.guess and config.sub from ftp://ftp.gnu.org/gnu/config
246 3. Run autoscan and copy configure.scan to configure.in
247 4. Add/edit the following lines in configure.in:
248 - AC_INIT(openggsn, 0.70, jj@openggsn.org)
249 - AC_CONFIG_SRCDIR([gtp/gtp.c])
250 - AM_CONFIG_HEADER([config.h])
254 5. libtoolize --automake --copy
255 (ads copy of ltmain.sh)
258 8. automake --add-missing --copy
259 (Ads copy of mkinstalldirs missing, install-sh, depcomp)
263 The above will initialise the project to the current version of
264 autotools (As installed in RedHat 8.0). See
265 http://sources.redhat.com/autobook/autobook/autobook_25.html#SEC25
266 for details on autotools.
269 Checking out from CVS
270 ---------------------
272 To download the latest source code from anonymous CVS:
274 cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/ggsn login
275 cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/ggsn co openggsn
277 Or to download from developer CVS:
280 cvs -z3 -d:ext:developername@cvs.sourceforge.net:/cvsroot/ggsn co openggsn
282 Both the above sets of commands creates a new directory called openggsn.
285 Compilation and installation
286 ----------------------------
288 If compiling under Solaris you need to edit the following line in
289 ggsn/Makefile.in and sgsnemu/Makefile.in:
291 LDFLAGS = -Wl,--rpath -Wl,/usr/local/lib @EXEC_LDFLAGS@
293 should be changed to:
295 LDFLAGS = -lresolv -lsocket -lnsl @EXEC_LDFLAGS@
297 Note that the above is not necessary on other platforms. Compilation
298 and installation is performed by the following steps:
304 5. make install (as root)
306 (Step 3 to 6 you only need to run the first time to install libgtp)
308 8. make install (as root)
309 9. Add /usr/local/lib to /etc/ld.so.conf
312 (Steps 9 and 10 are not required as path to libgtp is included in Makefile)
314 Documentation can be converted to html by issuing:
316 1. txt2html -pm -tf README > README.html
317 2. txt2html -pm -tf NEWS > NEWS.html
318 3. man2htm ggsn.8 > ggsn.html
319 4. man2htm sgsnemu.8 > sgsnemu.html
322 Installation from binary
323 ------------------------
325 1. rpm -i openggsn-<version>.rpm
327 This will install binaries, man pages, configuration files as well as
328 a Sys V init script for the ggsn.
334 Use ggsn -h for a list of available options. All options available on
335 the command line can also be given in a configuration file. See
336 examples/ggsn.conf for the format of this file.
338 Start the ggsn as root using the command:
340 ggsn -c examples/ggsn.conf --fg -l 10.0.0.40 --net 192.168.0.0/24 --dynip 192.168.0.0/24
342 First a tun network interface will be created. In the above example
343 the network interface address is 192.168.0.0 and the mask is
344 255.255.255.0. You can check that this interface is up by using
347 After tun has been successfully established the ggsn will wait for GTP
348 create PDP context requests on the local interface
349 10.0.0.40. Currently all requests are accepted, and no password,
350 username or APN validation is performed.
352 When receiving a create PDP context request a dynamic IP address will
353 be allocated from the address pool determined by --dynip. In the above
354 example the first allocated address will be 192.168.0.1, followed by
355 192.168.0.2 and so on. The request is confirmed by sending a create
356 PDP context response message to the peer (SGSN).
358 Now IP packets will be forwarded between the tun network interface and
359 the established GTP tunnel. In order to allow users to access the
360 external network routing needs to be set up. If private addresses are
361 used you need to configure network address translation. See the Linux
362 Networking HOWTO for details.
364 Remember to enable routing:
366 echo 1 > /proc/sys/net/ipv4/ip_forward
368 If you installed using a binary RPM package it is possible to start
369 ggsn by using the Sys 5 script:
371 /etc/init.d/ggsn start
377 Use sgsnemu -h for a list of available options. All options available
378 on the command line can also be given in a configuration file. See
379 examples/sgsnemu.conf for the format of this file.
381 If you want to test a GRX roaming connection you will need to do the
384 1. Install sgsnemu on a Linux Box. See under installation above.
385 2. Connect your Linux box with sgsnemu installed to the GPRS core
386 network. Use the same LAN switch as the one your SGSN is connected
387 to. You also need a free IP address that can be used by sgsnemu.
388 3. You need to configure networking in terms of interface address,
389 subnet mask and default route. See the Linux Networking HOWTO for
391 4. Launch sgsnemu with something like:
393 sgsnemu --listen 10.0.0.50 --remote 10.0.0.40 --dns 10.20.38.51 --timelimit 10 --contexts 0
395 sgsnemu will print something like the following on the screen:
398 Using DNS server: 10.20.38.51 (10.20.38.51)
399 Local IP address is: 10.0.0.50 (10.0.0.50)
400 Remote IP address is: 10.0.0.40 (10.0.0.40)
401 IMSI is: 240011234567890 (0x98765432110042)
403 Using MSISDN: 46702123456
405 Initialising GTP library
406 OpenGGSN[1823]: GTP: gtp_newgsn() started
407 Done initialising GTP library
409 Sending off echo request
410 Waiting for response from ggsn........
412 Received echo response. Cause value: 0
414 This is quite good. It means that you managed to send off an echo
415 request to a remote GGSN, and it was friendly enough to answer you. If
416 you did not get an echo response it means that something is wrong
417 either with your setup OR with the GRX connection OR with your roaming
420 If the above went well you might want to try to establish a PDP
421 context to the remote GGSN. Note that you should be careful when
422 establishing PDP contexts using sgsnemu as each established PDP
423 context will result in a Charge Detail Record (CDR) being generated by
424 the GGSN. You should use real IMSI and MSISDN from a valid test SIM
425 card. Otherwise some poor customer might get charged for your
426 testing. Also note that you are establishing a connection to the Gi
427 network, so please be carefull not to route internet traffic onto the
428 GPRS core network! Assuming you know what you are doing:
430 sgsnemu --listen 10.0.0.50 --remote 10.0.0.40 --dns 10.20.38.51 --timelimit 10 --contexts 1 --apn internet --imsi 240011234567890 --msisdn 46702123456 --createif --defaultroute
432 sgsnemu will print something like the following on the screen:
434 Using DNS server: 10.20.38.51 (10.20.38.51)
435 Local IP address is: 10.0.0.50 (10.0.0.50)
436 Remote IP address is: 10.0.0.40 (10.0.0.40)
437 IMSI is: 240011234567890 (0x98765432110042)
439 Using MSISDN: 46702123456
441 Initialising GTP library
442 OpenGGSN[1838]: GTP: gtp_newgsn() started
443 Done initialising GTP library
445 Sending off echo request
446 Setting up PDP context #0
447 Waiting for response from ggsn........
449 Received echo response. Cause value: 0
450 Received create PDP context response. Cause value: 128
451 Setting up interface and routing
452 /sbin/ifconfig tun0 192.168.0.1
453 /sbin/route add -net 192.168.0.0 netmask 255.255.255.0 gw 192.168.0.1
456 Now a context is established to the remote GGSN. The IP address of the
457 context is 192.168.0.1. You should be able to ping a known address on
458 the Gi network of the roaming partner. You should even be able to do
459 web browsing through the PDP context.
461 Note however that you probably need to adjust your routing tables, so
462 that you make sure that all GRX traffic is routed to the GPRS core
463 network and everything else through the PDP context. The proper way to
464 do this is to use policy routing. Also note that you are effectively
465 connecting the same computer to both the Gn and Gi network, so please
466 be carefull not to route internet traffic onto the GPRS core network
467 and please protect yourself against hackers! For this reason it is
468 advised to always use --contexts 0 when testing a live network.
470 After --timelimit seconds the PDP context is disconnected with the
471 following messages from sgsnemu:
474 Disconnecting PDP context #0
475 Received delete PDP context response. Cause value: 128
476 Deleting tun interface