https://osmocom.org/https://osmocom.org/favicon.ico?16647414092021-01-19T16:20:10ZOpen Source Mobile Communicationsosmo-gbproxy - Bug #4958: NSVC still makred as ALIVE even minutes after peer is gonehttps://osmocom.org/issues/4958?journal_id=208662021-01-19T16:20:10Zlaforge
<ul></ul><p>so the problem seems to be that we print the FSM state name, while "ALIVE" suggests to the user that this relates to the NSVC being ALIVE, i.e. able to carry traffic.</p>
<p>Do we change the FSM state name to "OPERATIONAL" or something else that doesn't already have a meaning?</p>
<p>Do we keep the name ALIVE but transition into a different state when we see Tnsalive/Tnstest timeouts?</p>
<p>Do we not print the FSM state anymore, but something else?</p> osmo-gbproxy - Bug #4958: NSVC still makred as ALIVE even minutes after peer is gonehttps://osmocom.org/issues/4958?journal_id=208672021-01-19T16:21:31Zlynxis
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> osmo-gbproxy - Bug #4958: NSVC still makred as ALIVE even minutes after peer is gonehttps://osmocom.org/issues/4958?journal_id=208692021-01-19T16:59:01Zlynxis
<ul></ul><ol>
<li>For block/reset we have the following state transitions:</li>
<ul>
<li>Unconfigured -> Reset -> Blocked -> Unblocked.<br />The test procedure is started in the Blocked state.</li>
</ul></li>
</ol>
<ol>
<li>For UDP</li>
<ul>
<li>Unconfigured -> Alive -> Unblocked.<br />The test procedure is started in Unblocked state. Because Alive is doing the test procedure to know if the link is really alive.</li>
</ul></li>
</ol>
<p>I could rename the Alive into Test. We should add another flag to `show ns` which show the dead or alive state of the NSVC.</p> osmo-gbproxy - Bug #4958: NSVC still makred as ALIVE even minutes after peer is gonehttps://osmocom.org/issues/4958?journal_id=208722021-01-19T17:27:06Zlaforge
<ul></ul><p>Related we are constantely getting ERROR messages as we attempt ALIVE->ALIVE state transitions in the NS-VC FSM:<br /><pre>
Tue Jan 19 18:05:57 2021 DLNS fsm.c:322 GPRS-NS2-VC(UDP-NSE00101-remote-127_0_0_10:7777)[0x6120000036a0]{ALIVE}: Timeout of T0
Tue Jan 19 18:05:57 2021 DLNS gprs_ns2_vc_fsm.c:460 GPRS-NS2-VC(UDP-NSE00101-remote-127_0_0_10:7777)[0x6120000036a0]{ALIVE}: transition to state ALIVE not permitted!
</pre></p> osmo-gbproxy - Bug #4958: NSVC still makred as ALIVE even minutes after peer is gonehttps://osmocom.org/issues/4958?journal_id=208732021-01-19T17:29:24Zlaforge
<ul></ul><p>lynxis wrote:</p>
<blockquote>
<p>I could rename the Alive into Test. We should add another flag to `show ns` which show the dead or alive state of the NSVC.</p>
</blockquote>
<p>I think "RECOVERY" or "RECOVERING" might be the most easy understandable word for this situation. "ALIVE" can mean the link is alive, but it also relates to Tns-alive, the alive procedure, ... and Test likewise may be confusing.</p> osmo-gbproxy - Bug #4958: NSVC still makred as ALIVE even minutes after peer is gonehttps://osmocom.org/issues/4958?journal_id=208742021-01-19T17:31:37Zlynxis
<ul></ul><p>laforge wrote:</p>
<blockquote>
<p>Related we are constantely getting ERROR messages as we attempt ALIVE->ALIVE state transitions in the NS-VC FSM:<br />[...]</p>
</blockquote>
<p>I fixed this one already in my branch.</p> osmo-gbproxy - Bug #4958: NSVC still makred as ALIVE even minutes after peer is gonehttps://osmocom.org/issues/4958?journal_id=210602021-02-03T10:21:50Zlynxis
<ul></ul><p><a class="external" href="https://gerrit.osmocom.org/c/libosmocore/+/22643">https://gerrit.osmocom.org/c/libosmocore/+/22643</a></p> osmo-gbproxy - Bug #4958: NSVC still makred as ALIVE even minutes after peer is gonehttps://osmocom.org/issues/4958?journal_id=210612021-02-03T10:22:41Zlynxis
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>80</i></li></ul> osmo-gbproxy - Bug #4958: NSVC still makred as ALIVE even minutes after peer is gonehttps://osmocom.org/issues/4958?journal_id=210702021-02-03T15:25:18Zdaniel
<ul></ul> osmo-gbproxy - Bug #4958: NSVC still makred as ALIVE even minutes after peer is gonehttps://osmocom.org/issues/4958?journal_id=213492021-02-19T12:46:19Zdaniel
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li></ul>