Project

General

Profile

Actions

Bug #5026

closed

ns2: ensure link states are logged

Added by lynxis 9 months ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
libosmogb
Target version:
-
Start date:
02/16/2021
Due date:
% Done:

100%

Spec Reference:

Description

when a ethernet device go down, ensure this is logged by osmocom as well a link recovery.

Actions #1

Updated by laforge 8 months ago

  • Category set to libosmogb
  • Assignee set to lynxis
Actions #2

Updated by laforge 8 months ago

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.

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.

Shouldn't it be sufficient if those kind of events are logged in syslog/journald?

Do other "IP server prograns" customaril log the link state of ethernet interfaces?

Actions #3

Updated by lynxis 3 months ago

We already log the link change (for fr interfaces).

https://gerrit.osmocom.org/c/libosmocore/+/22638

Actions #4

Updated by lynxis 3 months ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)