Actions
Bug #2836
closedlog filter doesn't work for stderr when gsmtap is configured
Start date:
01/18/2018
Due date:
% Done:
100%
Spec Reference:
Description
Contrary to what's documented, there's no log filter imsi 262020123456789
command for log stderr
target.
The only available log filter
option is all
but it doesn't work either: setting it to filter all messages (which should be default action as well) have no visible effect.
OsmoBTS# conf t OsmoBTS(config)# log stderr OsmoBTS(config-log)# OsmoBTS(config-log)# logging filter imsi 111 % Unknown command. OsmoBTS(config-log)# log filter all 0
Test configuration:
log stderr logging color 1 logging timestamp 0 logging filter all 0 log gsmtap logging timestamp 0 logging level rsl error logging level oml error logging level rll error logging level pcu error logging level lctrl notice logging level llapd notice logging level rr notice logging level meas error logging level pag error logging level l1c error logging level l1p error logging level linp error logging level dsp error logging level abis error logging level trx error ! line vty no login ! phy 0 osmotrx rts-advance 10 instance 0 osmotrx rx-gain 25 osmotrx tx-attenuation 25 bts 0 band 1800 ipa unit-id 6969 0 oml remote-ip 127.0.0.1 gsmtap-sapi ccch gsmtap-sapi rach gsmtap-sapi agch gsmtap-sapi pdtch trx 0 phy 0 instance 0
Related issues
Updated by msuraev over 6 years ago
- Related to Bug #71: Log target of everything is broken added
Updated by msuraev over 6 years ago
Not sure if it's related but show logging vty
reports that Logging was not enabled.
although we have both stderr
and gsmtap
targets set.
Updated by laforge over 6 years ago
- Assignee set to msuraev
I don't think OsmoBTS ever had a "log filter imsi" at all. They only program I know that implemented this was OsmoNITB.
Updated by msuraev over 6 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Appropriate clarification has been merged to osmo-gsm-manuals already.
Actions