https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-07-16T07:51:13ZOpen Source Mobile CommunicationsOsmoGGSN (former OpenGGSN) - Bug #3381: osmo-ggsn does not react properly when the PDP CTX ACT PCO contains primary and secondary DNS in separate IPCP https://osmocom.org/issues/3381?journal_id=103102018-07-16T07:51:13Zdexter
<ul><li><strong>Assignee</strong> changed from <i>dexter</i> to <i>pespin</i></li></ul> OsmoGGSN (former OpenGGSN) - Bug #3381: osmo-ggsn does not react properly when the PDP CTX ACT PCO contains primary and secondary DNS in separate IPCP https://osmocom.org/issues/3381?journal_id=103122018-07-16T08:02:33Zdexter
<ul></ul><p>Note: <a class="issue tracker-1 status-3 priority-1 priority-lowest closed" title="Bug: osmo-ggsn does not react properly when the PDP CTX ACT PCO contains primary and secondary DNS in... (Resolved)" href="https://osmocom.org/issues/3381">#3381</a> <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: also handle PCOs that contain primary and secondary DNS in two separate IPCP containers (Resolved)" href="https://osmocom.org/issues/3319">#3319</a> are duplicates</p> OsmoGGSN (former OpenGGSN) - Bug #3381: osmo-ggsn does not react properly when the PDP CTX ACT PCO contains primary and secondary DNS in separate IPCP https://osmocom.org/issues/3381?journal_id=139872019-04-15T13:43:42Zpespin
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/3319">Bug #3319</a>: also handle PCOs that contain primary and secondary DNS in two separate IPCP containers</i> added</li></ul> OsmoGGSN (former OpenGGSN) - Bug #3381: osmo-ggsn does not react properly when the PDP CTX ACT PCO contains primary and secondary DNS in separate IPCP https://osmocom.org/issues/3381?journal_id=139892019-04-15T13:44:20Zpespin
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>This is a duplicate, and the related ticket was resolved already.</p>