This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Osmocom code for Iuh interface".

The branch, stsp/destroy_conn_with_zero_msg has been created
        at  50fb6f9d64db5a8695cd793d9378eb4c90adf6d2 (commit)

- Log -----------------------------------------------------------------

commit 50fb6f9d64db5a8695cd793d9378eb4c90adf6d2
Author: Stefan Sperling <>
Date:   Thu Feb 22 17:20:16 2018 +0100

    destroy hnb context by sending a zero-len msgb after rejecting a HNB
    These are the osmo-iuh changes corresponding to the libosmo-netif
    branch 'destroy_conn_with_zero_msg'.
    Change-Id: I15f90a2e899789320e9329e33b3d294a65cc16b6

commit cc6ed397a63df49316dde1fd5e2385ca83f51aaf
Author: Stefan Sperling <>
Date:   Mon Feb 19 17:02:12 2018 +0100

    ensure unique CellIDs in HNB-GW
    If we receive a HNB-REGISTER-REQ with a cell ID which is already used
    by another registered NNB, log an error and send HNB-REGISTER-REJECT.
    Tested manually by running two 'hnb-test' programs concurrently (they
    need to listen on different telnet ports; this port is hard-coded so
    I compiled two different hnb-test binaries).
    Then I issued the 'hnbap hnb register' command on the telnet interface
    of each, and verified that the correct action is logged by osmo-hnbgw.
    Both hnb-test programs can connect, but only one of them can register
    at a time. Killing a registered 'hnb-test' program terminates its
    connection and allows the previously rejected one to register.
    The new rejection log message looks like this:
     hnbgw_hnbap.c:429 rejecting HNB-REGISTER-REQ with duplicate cell
     identity MCC=901,MNC=99,LAC=49406,RAC=66,SAC=43947,CID=182250155
     from (r=<->l=
    Change-Id: Iffd441eb2b6b75dfbe001b49b01bea015ca6e11c
    Related: OS#2789


Osmocom code for Iuh interface

Reply via email to