Osmocom code for the Iuh interface (HNBAP, RUA, RANAP)
https://osmocom.org/projects/libosmo-ranap
Neels Hofmeyr
135bc06c35
For IPv4 addresses, only 56bit of X.213 NSAP are used. The sysmocell5000 accepts such a field that is 56bits long, but the ip.access nano3G does not (and crashes instead). Both work when zero-padded to 160bits size. So far we used to send the IPv4 address as "raw" 32bits to the nano3G to avoid the crash. With this zero padding we no longer need such a workaround and can use identical config for both cells. Change-Id: I070bbfe887ab93d08322df30571050a381d082d5 |
||
---|---|---|
asn1 | ||
contrib | ||
doc | ||
include | ||
pcap | ||
specs | ||
src | ||
.gitignore | ||
COPYING | ||
Makefile.am | ||
README | ||
configure.ac | ||
git-version-gen | ||
libosmo-ranap.pc.in | ||
move-asn1-header-files.sh |
README
Osmocom Iuh experimentation code (C) 2015 by Harald Welte <laforge@gnumonks.org> This code is a playground for implementing something along the lines of the an Iuh interface of a HNB-GW. The intent is to later integrate this with OsmoNITB + OsmoSGSN, in order to have 3G capable 'network in the box'. h1. Building As external library dependencies, you will need * libosmocore from git://git.osmocom.org/libosmocore * libasn1c from git://git.osmocom.org/libasn1c * libsctp-dev (this is the package name in Debian) * libosmo-netif from git://git.osmocom.org/libosmo-netif (sysmocom/sctp branch) * libosmo-sccp from git://git.osmocom.org/libosmo-sccp (sysmocom/iu branch) To bootstrap the build, in the root directory, run: autoreconf --install After that, run the usual ./configure [options] make [sudo] make install h1. Using Note: osmo-iuh is in active development (December 2015, January 2016) so below statements may outdate rapidly. there's not much to use yet. But if you run the 'hnbgw' executable, it will open a listening SCTP socket and wait for incoming Iuh connections. It will accept any HNB-REGISTER-REQUEST, so the homeNodeB should start to establish RUA and RANAP (which we haven't implemented yet). h1. Regenerating C code from ASN.1 source In order to re-generate the C source code from the ASN.1 source, you will need a modified asn1c which has the following features: * APER support (the patch from Eurecom, or its forward-ported version from the aper branch of git://git.osmocom.org/asn1c) * support for prefixing the generated types (aper-prefix branch of git://git.osmocom.org/asn1c)