Age | Commit message (Collapse) | Author | Files | Lines |
|
Upon authentication response, initiate integrity protection for Iu by sending a
Security Mode Command (IK), with hardcoded auth tuple so far.
Implement RANAP event handling to receive Security Mode Complete message,
adding stubs for the other events; in new files osmo-cscn/iucs_ranap.[hc] to
keep RANAP dependencies separate, and particularly out of libmsc.
Upon receiving Security Mode Complete, call the security operation callback
(conn->sec_operation->cb) to complete the Location Update.
Introduce enum integrity_protection_state constants to indicate integrity
protection, record in gsm_subscriber_conn.iu.integrity_protection.
Make subscr_conn_lookup_iu() non-static and declare in iu_cs.h to be able to
call from iucs_ranap.c's Security Mode Complete event.
Implement dummy iu_tx_sec_mode_cmd() to allow tests to build without RANAP
dependencies.
In cscn_main.c, call iucs_rx_ranap_event(), to populate the struct gsm_network
struct with cscn_network explicitly (don't share cscn_network across
compilation scopes because it's ugly).
|
|
libbsc and libmsc have conflicting definitions of gsm_subscriber_connection
and do no longer belong together anyway.
Create libxsc, meaning 'lib[bm]sc', to hold all code used by both libmsc
and libbsc, and make sure gsm_subscriber_connection isn't used there.
In various binaries and tests, do not link libbsc and libmsc.
(Note: this commit was reshaped out of a large wip chunk, it may not
compile properly without the subsequent commits)
|
|
|
|
Add noinst-header iu_cs.h and move the gsm0408_rcvmsg_iucs() declaration
there.
|
|
Add libiu to contain the parts used by both Iu-CS (in osmo-cscn) and Iu-PS (in
gprs) into libiu. It's rather thin and may make sense to move to osmo-iuh
altogether, eventually.
iu.c is half moved to libiu/, and half to osmo-cscn/iu_cs.c.
|
|
|
|
CSCN means "Circuit Switched Core Network" (-in-the-box) and will become a
NITB-without-BSC, so that it talks Iu-cs to the HNBGW and talks 'A' to an
external BSC.
Copying NITB is debatable: on the one hand, we've agreed on the name Osmo-CSCN
for the end result (without internal BSC). On the other hand, I will probably
add Iu-cs into the NITB code incrementally, in such a way that theoretically,
both Iu-cs and the internal BSC functionality could be used at the same time.
So Osmo-CSCN will be a NITB plus Iu-cs for a while. Instead of adding to NITB,
I prefer to work on a copy, so that the original NITB remains more or less
unchanged.
Only a later step will clearly distinguish CSCN from NITB: when the BSC part is
split off for the benefit of a proper A-interface, and CSCN talks to an
external BSC.
|