Actions
Bug #4861
closedframe_relay: logging needs context
Start date:
11/14/2020
Due date:
% Done:
100%
Spec Reference:
Description
When running a Gb interface based on the frame_relay.c code, I get log messages like
<0024> frame_relay.c:729 DLCI 18 is not active (yet), discarding <0024> frame_relay.c:729 DLCI 19 is not active (yet), discarding <0024> frame_relay.c:729 DLCI 16 is not active (yet), discarding <0024> frame_relay.c:729 DLCI 17 is not active (yet), discarding
Those are only useful if the DLCI is globally unique - for which there is no requirment. Every frame relay bearer (E1 line) could very well use the same DLCI numbers, and at which point it would be impossible to distinguish them in the logs.
Updated by laforge over 3 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Implemented in I57cae1fd6c25bf2a7a017186b352adfcbd34a21c of laforge/wip-fr:
<0024> frame_relay.c:748 hdlcnet4: Link is not reliable (yet), discarding Tx <0024> frame_relay.c:748 hdlcnet3: Link is not reliable (yet), discarding Tx <0024> frame_relay.c:748 hdlcnet2: Link is not reliable (yet), discarding Tx <0024> frame_relay.c:748 hdlcnet1: Link is not reliable (yet), discarding Tx
Actions
