pespin has uploaded this change for review.

View Change

osmux: Lower log level when osmux batch received for unknown CID

This is actually quite common, since our peer may be sending some osmux
packets to us a while after we have closed the conn on our side,
specially if latency is high in the network (eg satellite links).

Related: SYS#598

Change-Id: I102047685b9b9f4cba43970945f955c4fe9c4c95
---
M src/common/osmux.c
1 file changed, 1 insertion(+), 1 deletion(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-bts refs/changes/73/29573/1
diff --git a/src/common/osmux.c b/src/common/osmux.c
index e178e0c..8a5d1ee 100644
--- a/src/common/osmux.c
+++ b/src/common/osmux.c
@@ -265,7 +265,7 @@
if (!lchan) {
char addr_str[64];
osmo_sockaddr_to_str_buf(addr_str, sizeof(addr_str), &rem_addr);
- LOGP(DOSMUX, LOGL_NOTICE,
+ LOGP(DOSMUX, LOGL_DEBUG,
"Cannot find lchan for %s CID=%d\n",
addr_str, osmuxh->circuit_id);
continue;

To view, visit change 29573. To unsubscribe, or for help writing mail filters, visit settings.

Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: I102047685b9b9f4cba43970945f955c4fe9c4c95
Gerrit-Change-Number: 29573
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin@sysmocom.de>
Gerrit-MessageType: newchange