https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092020-10-12T14:24:30ZOpen Source Mobile CommunicationsOsmoHLR - Bug #4312: GSUP keepalives / connection loss detectionhttps://projects.osmocom.org/issues/4312?journal_id=199012020-10-12T14:24:30Zpespin
<ul></ul><p>I confirm there's currently no keepalive being used or possibility to configure it in GSUP client connections, as we already do in OML/RSL conns.</p>
<p>In OML/RSL IPA conns, we have all those already in place (IPA ping/pong and TCP keepalive), see e1_input_vty.c, vty commands like:<br />"e1_line <0-255> keepalive <1-300> <1-20> <1-300>" <br />"e1_line <0-255> ipa-keepalive <1-300> <1-300>"</p>
<p>Those values are applied in libosmo-abis/src/input/ipaccess.c in update_fd_settings() called during updown cb in ipa client and during listen cb in servers.</p>
<p>The ipaccess.c code uses the lower layer ipa_client_conn and ipa_server_conn APIs fom libosmo-abis/src/input/ipa.c.</p>
<p>So in GSUP we are basically missing doing the same that's done in ipaccess.c, that is, during updown cb and listen callback, use something like update_df_settings() to set params configured previously thoguh VTY comands provided by libgsupclient/server.</p> OsmoHLR - Bug #4312: GSUP keepalives / connection loss detectionhttps://projects.osmocom.org/issues/4312?journal_id=199022020-10-12T14:42:18Zpespin
<ul></ul><p>See <a class="external" href="https://gerrit.osmocom.org/c/osmo-hlr/+/20577">https://gerrit.osmocom.org/c/osmo-hlr/+/20577</a> fore reference on where to add the bits to be applied on the sockets (this commit only sets TCP_NODELAY on them).</p>