https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092021-03-24T12:31:50ZOpen Source Mobile Communicationslibosmocore - Bug #5026: ns2: ensure link states are loggedhttps://projects.osmocom.org/issues/5026?journal_id=217062021-03-24T12:31:50Zlaforge
<ul><li><strong>Category</strong> set to <i>libosmogb</i></li><li><strong>Assignee</strong> set to <i>lynxis</i></li></ul> libosmocore - Bug #5026: ns2: ensure link states are loggedhttps://projects.osmocom.org/issues/5026?journal_id=218012021-03-30T09:20:24Zlaforge
<ul></ul><p>So far we only perform link monitoring within gprs_ns2_fr.c for the frame relay devices. I think there it also makes sense as those are basically "single use devices" where the entire FR/... stack is implemented by us.</p>
<p>For ethernet devices, this is somewhat more questionable. Ethernet, IP and TCP/UDP are implemented in the kernel. We don't even know whcih ethernet devices exist, what kind of routes there are, etc.</p>
<p>Shouldn't it be sufficient if those kind of events are logged in syslog/journald?</p>
<p>Do other "IP server prograns" customaril log the link state of ethernet interfaces?</p> libosmocore - Bug #5026: ns2: ensure link states are loggedhttps://projects.osmocom.org/issues/5026?journal_id=225112021-09-03T23:36:35Zlynxis
<ul></ul><p>We already log the link change (for fr interfaces).</p>
<p><a class="external" href="https://gerrit.osmocom.org/c/libosmocore/+/22638">https://gerrit.osmocom.org/c/libosmocore/+/22638</a></p> libosmocore - Bug #5026: ns2: ensure link states are loggedhttps://projects.osmocom.org/issues/5026?journal_id=225122021-09-03T23:36:43Zlynxis
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul>