https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092017-03-09T17:01:35ZOpen Source Mobile CommunicationsOsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=33052017-03-09T17:01:35Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-2 priority-default" href="/issues/1818">Bug #1818</a>: IuPS: CN should Iu Release in certain situations</i> added</li></ul> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=33072017-03-09T17:01:47Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>may or may not be related to <a class="issue tracker-1 status-1 priority-2 priority-default" title="Bug: IuPS: CN should Iu Release in certain situations (New)" href="https://projects.osmocom.org/issues/1818">#1818</a></p> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=50662017-08-17T06:51:55Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>118</i> to <i>4368</i></li></ul> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=52492017-08-30T22:39:10Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>See <a class="issue tracker-1 status-1 priority-2 priority-default" title="Bug: IuPS: CN should Iu Release in certain situations (New)" href="https://projects.osmocom.org/issues/1818#note-4">#1818#note-4</a> (and #1818's attached pcap) indicating a likely solution to this issue: mismatching keystatus.</p> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=52512017-08-30T23:36:14Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>hmm, it doesn't seem so easy to reproduce a situation where the new_key flag reflects the wrong value.<br />I do get unreliable behavior, like web browser page failing to load, failing DNS lookups on-and-off, but all the while the new_key flag reflects the actual key status that is transmitted.<br />It doesn't seem to be as quick a fix as I thought.</p> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=67002017-12-10T20:10:18Zlaforge
<ul><li><strong>Category</strong> set to <i>Iu interface</i></li></ul> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=96642018-05-30T15:01:04Zlaforge
<ul><li><strong>Tags</strong> set to <i>3G</i></li></ul> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=139002019-04-13T11:26:15Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-3 status-2 priority-2 priority-default" href="/issues/3920">Support #3920</a>: PCAPs files of 3G PS for Osmocom network and Commercial one</i> added</li></ul> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=158502019-09-04T09:33:43Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>4368</i> to <i>lynxis</i></li></ul><p>Do we still consider this to be the case? Or has this meanwhile been resolved?</p> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=159792019-09-16T16:58:30Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>I tried to quickly test IuPS to see how it fares, but hit a crash: <a class="issue tracker-1 status-6 priority-2 priority-default closed" title="Bug: crash: libosmocore/src/gsm/gsm48.c:788:18: runtime error: load of null pointer of type 'const uin... (Rejected)" href="https://projects.osmocom.org/issues/4208">#4208</a><br />I haven't yet seen a really reliable 3G data connection. Possibly problems are fixed, but let's consider this unresolved until osmo-sgsn works again.</p> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=159832019-09-16T19:37:17Zlynxis
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>80</i></li></ul><p>So far I see the following problems<br />- ran changes 2g/3g (patches in gerrit, but WIP)<br />- Iu release (patches needs to be merged)<br />- synchronize PDP Context: MS state with SGSN state (already merged)</p> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=159842019-09-16T19:38:14Zlynxis
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-3 priority-high3 closed" href="/issues/3727">Bug #3727</a>: SGSN segfaults on network type change</i> added</li></ul> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=159862019-09-16T19:38:27Zlynxis
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-2 priority-default closed" href="/issues/3995">Bug #3995</a>: OsmoSGSN doesn't close SCCP connection after successful LU over IuPS</i> added</li></ul> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=159912019-09-17T01:00:38Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>So, I learned that the crash is known and comes from changing from 2G to 3G.<br />Taking care not to do that, I tried the 3G IuPS successfully.</p>
<p>I actually don't see the weird behavior that made me create this issue originally.<br />It seems that the cause making the IuPS data uplink hickup has indeed been fixed.<br /><a class="user active" href="https://projects.osmocom.org/users/1741">lynxis</a> from my side it seems that we can close this, and track the remaining known IuPS problems in their own issues each. Agree?</p> OsmoSGSN - Bug #1977: 3G IuPS is unreliablehttps://projects.osmocom.org/issues/1977?journal_id=161192019-09-28T21:41:47Zlynxis
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li></ul>