libosmocore/include/osmocom
Harald Welte dda70fca79 Add osmo_sock_init2() function, allowing both BIND *and* CONNECT
The old osmo_sock_init() function allows only either a bind (for a
server socket), or a connect (for a client socket), but not both
together.  So there's no way to have a client socket that is bound to a
specific local IP and/or port, which is needed for some use cases.

Change-Id: Idab124bcca47872f55311a82d6818aed590965e6
2017-04-09 21:46:21 +02:00
..
codec Mark inline header function as static 2016-09-30 12:31:50 +00:00
coding libosmocoding: migrate transcoding routines from OsmoBTS 2017-03-07 01:06:38 +07:00
core Add osmo_sock_init2() function, allowing both BIND *and* CONNECT 2017-04-09 21:46:21 +02:00
crypt osmo_auth_gen_vec: UMTS auth: fix SQN as SEQ || IND 2017-03-15 12:46:08 +00:00
ctrl ctrl_type_vals: explicitly terminate 2017-03-15 13:47:20 +00:00
gprs logging: centrally define ctx and filter indexes 2017-02-22 16:08:38 +00:00
gsm gsm0808: Add create functions for BSS_MAP_MSG_ASSIGMENT_RQST 2017-04-08 07:44:47 +00:00
sim sim: make osim_reader_ops public 2016-03-19 21:18:40 +01:00
vty add VTY port number for osmo-stp 2017-04-08 09:34:04 +02:00