https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-04-10T17:34:31ZOpen Source Mobile CommunicationsOsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=88102018-04-10T17:34:31Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>4368</i> to <i>lynxis</i></li></ul> OsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=91062018-05-02T18:16:02Zlynxis
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> OsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=95852018-05-29T16:40:20Zlynxis
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Stalled</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>50</i></li></ul><p>I've started to refactor the whole GMM Attach Request handling into one fsm.<br />This issue is already fixed in the new fsm implementation.<br />I've created the ttcn3 testcase <pre>SGSN_Tests.TC_attach_second_attempt</pre> for this.</p> OsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=95872018-05-29T16:40:36Zlynxis
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-5 priority-highest closed parent" href="/issues/3302">Bug #3302</a>: implement a FSM for GMM Attach Request</i> added</li></ul> OsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=96292018-05-30T14:18:27Zlaforge
<ul><li><strong>Tags</strong> set to <i>TTCN3</i></li></ul> OsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=98592018-06-12T13:18:19Zlynxis
<ul></ul> OsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=106512018-08-07T18:28:05Zlynxis
<ul></ul><p><del>The test is failing again, even under the new FSM.</del><br /><del>The HLR integration into the test must be rewritten.</del></p>
<p>At the moment, the TTCN test case <strong>SGSN_Tests.TC_attach_second_attempt</strong> still fails, but this is fails, because the<br />second attach does not proceed, because TTCN explicit expect to see an <strong>Insert Subscriber Data Request</strong>.<br />This request will be never sent from the SGSN, because it has still valid key data.</p> OsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=139382019-04-15T07:37:14Zlaforge
<ul></ul> OsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=140402019-04-18T11:20:18Zlynxis
<ul><li><strong>Status</strong> changed from <i>Stalled</i> to <i>In Progress</i></li></ul> OsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=140522019-04-18T15:30:04Zlynxis
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Normal</i></li></ul><p>It's not only the SGSN Tests. The SGSN does not behave correctly. The sgsn_authentication have to be rewritten as well the integration of Auth Req/Response to fix the real problem.</p> OsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=152092019-07-18T05:11:22Zlaforge
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Stalled</i></li></ul> OsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=170912020-01-08T22:49:37Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>lynxis</i> to <i>4368</i></li></ul> OsmoSGSN - Bug #2958: OsmoSGSN doesn't authenticate on second/further ATTACH REQUESThttps://osmocom.org/issues/2958?journal_id=271942023-06-28T13:18:35Zfixeria
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/4221">Bug #4221</a>: create ttcn testcase for T3350 in combination with a PDP context</i> added</li></ul>