cellular-infrastructure
/
osmo-hnbgw
mirror of https://gerrit.osmocom.org/osmo-hnbgw
9
0
Fork 0
Code Issues Releases Wiki Activity
Osmocom Home NodeB Gateway, for attaching femtocells to the 3G CN (OsmoMSC, OsmoSGSN) https://osmocom.org/projects/osmohnbgw
74 Commits 20 Branches 6 Tags 4.4 MiB
C 94.5%
M4 1.9%
Shell 1.8%
Makefile 1.6%
Python 0.2%
Go to file
Pau Espin 5f19597b02 Close conn when receiving SCTP_ASSOC_CHANGE notification 
It was seen on a real pcap trace (sctp & gsmtap_log) that the kernel
stack may decide to kill the connection (sending an ABORT) if it fails
to transmit some data after a while:
ABORT Cause code: "Protocol violation (0x000d)",
      Cause Information: "Association exceeded its max_retrans count".
When this occurs, the kernel sends the
MSG_NOTIFICATION,SCTP_ASSOC_CHANGE,SCTP_COMM_LOST notification when
reading from the socket with sctp_recvmsg(). This basically signals that
the socket conn is dead, and subsequent writes to it will result in
send() failures (and receive SCTP_SEND_FAILED notification upon follow
up reads).
It's important to notice that after those events, there's no other sort
of different event like SHUTDOWN coming in, so that's the time at which
we must tell the user to close the socket.
Hence, let's signal the caller that the socket is dead by returning 0,
to comply with usual recv() API.

Related: SYS#6113
Change-Id: If35efd404405f926a4a6cc45862eeadd1b04e08c
 		2022-10-01 21:21:06 +02:00
contrib Set working directory in systemd service file 2022-08-30 19:48:37 +07:00
debian debian,RPM: package with PFCP support 2022-08-27 16:02:51 +00:00
doc example cfg: tweak logging 2022-08-18 16:17:53 +02:00
include hnbgw_rx_hnb_deregister: Don't call hnb_context_release() 2022-09-13 12:59:57 +02:00
src Close conn when receiving SCTP_ASSOC_CHANGE notification 2022-10-01 21:21:06 +02:00
tests tests/ranap_rab_ass: fix potential NULL pointer dereferences 2022-07-30 05:48:41 +07:00
.gitignore Initial structure + import code from osmo-iuh.git 2022-01-04 19:48:52 +01:00
.gitreview Initial structure + import code from osmo-iuh.git 2022-01-04 19:48:52 +01:00
AUTHORS Initial structure + import code from osmo-iuh.git 2022-01-04 19:48:52 +01:00
COPYING Initial structure + import code from osmo-iuh.git 2022-01-04 19:48:52 +01:00
Makefile.am Initial structure + import code from osmo-iuh.git 2022-01-04 19:48:52 +01:00
README.md update URLs (git -> https; gitea) 2022-06-18 14:02:41 +02:00
TODO-RELEASE Initial structure + import code from osmo-iuh.git 2022-01-04 19:48:52 +01:00
configure.ac do not depend on libosmo-gtlv 2022-09-14 13:27:27 +02:00
git-version-gen Initial structure + import code from osmo-iuh.git 2022-01-04 19:48:52 +01:00
osmoappdesc.py Initial structure + import code from osmo-iuh.git 2022-01-04 19:48:52 +01:00

README.md

osmo-hnbgw - Osmocom hNodeB Implementation

This repository contains a C-language implementation of a 3G Home NodeB Gateway (OsmoHNBGW). It is part of the Osmocom Open Source Mobile Communications project.

You can use it to interface Iuh-speaking Home NodeB (HnodeB), such as osmo-hnodeb or ip.access nano3g, to Iu-speaking MSCs and SGSNs.

Homepage

The official homepage of the project is https://osmocom.org/projects/osmohnbgw/wiki

GIT Repository

You can clone from the official osmo-hnbgw.git repository using

git clone https://gitea.osmocom.org/cellular-infrastructure/osmo-hnbgw

There is a web interface at https://gitea.osmocom.org/cellular-infrastructure/osmo-hnbgw

Documentation

User Manuals and VTY reference manuals are [optionally] built in PDF form as part of the build process.

Pre-rendered PDF version of the current "master" can be found at User Manual as well as the VTY Reference Manual

Mailing List

Discussions related to osmo-hnbgw are happening on the openbsc@lists.osmocom.org mailing list, please see https://lists.osmocom.org/mailman/listinfo/openbsc for subscription options and the list archive.

Please observe the Osmocom Mailing List Rules when posting.

Contributing

Our coding standards are described at https://osmocom.org/projects/cellular-infrastructure/wiki/Coding_standards

We us a gerrit based patch submission/review process for managing contributions. Please see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit for more details

The current patch queue for osmo-hnbgw can be seen at https://gerrit.osmocom.org/#/q/project:osmo-hnbgw+status:open